https://bugs.kde.org/show_bug.cgi?id=489547

--- Comment #2 from Dominick <dominick.allen1...@gmail.com> ---
(In reply to David Jarvie from comment #1)
> I wonder if this problem is a KAlarm bug, or something else. I don't see why
> the screen lock status would have any effect on alarms being triggered. To
> check this, could you please try two things: 
> 
> 1) Set up a KAlarm command alarm which triggers at the same time as your
> audio command alarm, and which does something not audio related - for
> example writing something to a file. Check whether this runs successfully
> after the screen locks. Ideally, make a command alarm which first writes to
> a file and then plays the audio file. You can then see if the alarm has
> triggered, and whether only the audio part fails.
> 
> 2) Set up a little script which executes a "sleep" for long enough for the
> bug to occur, and then executes the same command as the KAlarm alarm.
> Execute the script in a terminal window (not in KAlarm) and leave it
> running. Check whether it plays the audio file after your screen has locked.
> 
> On a separate note, can you please raise a separate bug report about KAlarm
> no longer playing audio files other than .ogg ones, and attach an example of
> an audio file which does not work. Mention any error messages which are
> shown. This isn't something which has previously been reported.

For the audio file one, I have submitted a bug report:
https://bugs.kde.org/show_bug.cgi?id=489597. To summarize, kalarm now uses
libcanberra to play audio files, but because canberra does not support flac or
mp3 codecs, those cannot be used for audio alarms now.

I will set a command alarm that executes a script which first writes a message
to a file, then plays an audio file. It will be interesting to see if this
doesn't impact file IO. I believe the root cause of the problem is some funky
interaction with wayland.

When the screen wakes up, I get these messages in journalctl: "kalarm[4487]:
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash"  - this
applies to all my kde apps and components like kactivitymanagerd.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to