Summary: | KAlarm crashes | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | Cesar Alba <cesar.alba+kdebugs> |
Component: | sound | Assignee: | David Jarvie <djarvie> |
Status: | REPORTED --- | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/108562/events/5d2c2a5220394cc0b08a2954dae91d1e/ | ||
Attachments: | Backtrace |
Description
Cesar Alba
2024-12-21 09:29:18 UTC
The crash occurs in pipewire when libvlc attempts to set the audio volume. There is a crash report for amarok/phonon (https://bugs.kde.org/show_bug.cgi?id=486468) which looks very similar (although not identical), where the fault disappeared after Fedora 40 packages were updated. It seems likely that this crash is due to a bug in vlc or pipewire, and that updating one or both of these packages might fix it. Please report if this crash is still present after updating your system. Hi, Thanks for quick response. I didn't realize that. System is updated almost daily. You reply raises some questions on how we got here: * How (and where and when) got kalarm linked to VLC? * How can the user control that association? I mean, I have VLC installed but as far as I am aware it is not my default player of choice and it seems failure happens everytime I run the command and it tries "get graphical" (after your response I checked on kalarm options and it seems to have survived "kalarm --list"). About the ticket: if you want me to provide extra information, just request it to me. If not, should I open the request to Fedora (this used to work until some update on QT6)? Thanks KAlarm used to use Phonon to play audio, but there were always some crash reports, which eventually turned out to be due to Phonon not being thread safe. Canberra was then adopted in KAlarm version 3.8.0 (KDE Gear 24.02.1), but although this was more stable, it didn't recognise some recent audio file formats, so it was replaced by VLC in KAlarm version 3.9.0 (KDE Gear 24.08). Since KAlarm version 3.10 (KDE Gear 24.12), there has also been a build option to use MPV instead of VLC. Whether this is used in packages depends of course on each distribution. There is currently no way that a user can switch to MPV except by rebuilding KAlarm. However, your bug report raises the question of whether KAlarm should allow the user to choose, if the distribution builds both backends as options. I think that it could be useful to raise this issue with Fedora, since it does seem that the problem comes from a library rather than KAlarm itself. To avoid marking the bug as RESOLVED, I set the its status to NEEDSINFO. The only information needed is hopefully that the crash will have been fixed by some library update. Thanks for explanation Bug created at Fedora. I will keep you updated. Kalarm version 3.11 (KDE Gear 25.04) will allow the user to select either the VLC or MPV audio backend (assuming that the distro builds both backends for KAlarm). šš§¹ ā ļø This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Created attachment 177917 [details]
Backtrace
Comment on attachment 177917 [details]
Backtrace
I can confirm that kalarm crash with a segmentation fault after a full system update today. It occurs just after logon, but only for one time, since another instance of kalarm is running later.
Operating System: Arch Linux
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.12.10-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 6 à Intel® Core⢠i5-9400 CPU @ 2.90GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa IntelĀ® UHD Graphics 630
Can you please attach a copy of your KAlarm calendar file, which will be ~/.local/share/kalarm/calendar.ics unless you have changed it's location. Feel free to edit it to change any message texts for privacy of you wish. Thank you for taking care of the problem. After further testing, I found out that it has something to do with session restoration. When I end a session, the sessions from the last logout are saved in "ksmserverrc" and restored when I log in; and that's when it happens. When I set the option "Start with an empty session", the problem no longer occurred. As a workaround, I added the application "kalarm" to the list of "Ignored applications" and after that the problem also no longer occurred. I looked in older backups and it was always the case that the application "kalarm" was in "ksmserverrc" as a session to be restored, so this is not new. However, I still don't understand why the application is not terminated when the user logs off so that it is not included as an application to be restored, because "kalarm" would be started in a new session via the autostart mechanism anyway. Conversely, it would be wrong to restore and run it if it was previously removed from autostart by the user. During the last system update, "kalarm" was not updated, but "qt6-base" and related components were, among others. The cause of the behavior may be found there. The crash reported in Comment 7 and Comment 8 is not related to the original bug report. It is in fact the same crash as reported in Bug 499859. If you (Martin) have any further comments on your crash, enter them in https://bugs.kde.org/show_bug.cgi?id=499859 instead. In future, please raise a new bug report for a bug/crash which is unrelated to the original bug report. |