Description of problem: When the slide show screen saver comes on, it throws this error & causes cpu usage & temps to spike. Never happened with kde 4.9, only now in kde 4.10 Fedora 18. Happens on multiple computers. Version-Release number of selected component: kdeartwork-screensavers-4.10.1-1.fc18 Additional info: backtrace_rating: 4 cmdline: kslideshow.kss -window-id 79691828 crash_function: qt_message_output executable: /usr/bin/kslideshow.kss kernel: 3.8.3-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 qt_message_output at global/qglobal.cpp:2323 #7 ~QDebug at /usr/include/QtCore/qdebug.h:85 #8 xErrorHandler at /usr/src/debug/kde-workspace-4.10.1/kscreensaver/libkscreensaver/main.cpp:120 #10 handle_error at xcb_io.c:212 #11 handle_response at xcb_io.c:324 #12 _XEventsQueued at xcb_io.c:363 #13 XEventsQueued at Pending.c:43 #14 x11EventSourcePrepare at kernel/qguieventdispatcher_glib.cpp:77 #15 g_main_context_prepare at gmain.c:2986 #17 g_main_context_iteration at gmain.c:3351
Created attachment 712267 [details] File: backtrace
Created attachment 712268 [details] File: build_ids
Created attachment 712269 [details] File: cgroup
Created attachment 712270 [details] File: core_backtrace
Created attachment 712271 [details] File: dso_list
Created attachment 712272 [details] File: environ
Created attachment 712273 [details] File: limits
Created attachment 712274 [details] File: maps
Created attachment 712275 [details] File: open_fds
Created attachment 712276 [details] File: proc_pid_status
Created attachment 712277 [details] File: var_log_messages
I found that Nepomuk Semantic Desktop was the cause of cpu usage & temps spiking after approximately 2 minutes of inactivity. Disabling Nepomuk Semantic Desktop, under Desktop Search in System Settings, fixed that problem. However, screen saver still throws error.
I have the same problem, screen saver "asciquarium" crashes (was killed by signal 6) on my laptop, fedora 18, after the last update that brought down kde4.10: kdeartwork-kxs-4.10.1-1.fc18.i686
Every time the machine is left unattended for long enough for the screensaver to kick in, pressing any key to dismiss the screensaver immediately pops up a box saying there has been a crash in the KDE artwork package. This happens every single time and is therefore reproducible on demand. backtrace_rating: 4 cmdline: keuphoria.kss -window-id 146800692 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.8.4-202.fc18.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) uid: 1001 ureports_counter: 1 xsession_errors:
Appears every time the screensaver is deactivated. Have not tried another screensaver. backtrace_rating: 4 cmdline: keuphoria.kss -window-id 54526020 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.8.4-202.fc18.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1
unlocking screen with keuphria screensaver running backtrace_rating: 4 cmdline: keuphoria.kss -window-id 94371895 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.8.4-202.fc18.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1 xsession_errors: keuphoria.kss(1042): Got X error after loss of parent process. Terminating.
I'll try to poke upstream when I get a chance, though do be aware this is mostly harmless and cosmetic (something is crashing instead of exiting cleanly on screensaver close, and we're only noticing this because abrt catches it)
Happens after coming out of screensaver backtrace_rating: 4 cmdline: kslideshow.kss -window-id 169869364 crash_function: qt_message_output executable: /usr/bin/kslideshow.kss kernel: 3.8.4-202.fc18.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc18 reason: Process /usr/bin/kslideshow.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1
1.) Wait for the screensaver to start 2.) Move the mouse or press a key to disable screensaver 3.) ABRT says that the screensaver was killed by SIGABRT backtrace_rating: 4 cmdline: kdeasciiquarium.kss -window-id 106954804 crash_function: qt_message_output executable: /usr/bin/kdeasciiquarium.kss kernel: 3.8.5-201.fc18.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc18 reason: Process /usr/bin/kdeasciiquarium.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 2
Hitting a key to resume session when screen-saver is running skips the password prompt and goes straight to desktop with this error message. backtrace_rating: 4 cmdline: keuphoria.kss -window-id 62914628 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.7.5-201.fc18.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1 xsession_errors:
An error occurs if you disable the screen saver backtrace_rating: 4 cmdline: kflux.kss -window-id 88080437 crash_function: qt_message_output executable: /usr/bin/kflux.kss kernel: 3.8.9-200.fc18.x86_64 package: kdeartwork-screensavers-4.10.2-1.fc18 reason: Process /usr/bin/kflux.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1
Screen saver crashes on exit. backtrace_rating: 4 cmdline: kdeasciiquarium.kss -window-id 111149147 crash_function: qt_message_output executable: /usr/bin/kdeasciiquarium.kss kernel: 3.8.9-200.fc18.x86_64 package: kdeartwork-screensavers-4.10.2-1.fc18 reason: Process /usr/bin/kdeasciiquarium.kss was killed by signal 6 (SIGABRT) uid: 500 ureports_counter: 2
I didn't even know there had been a crash until abrt showed up in the systray. backtrace_rating: 4 cmdline: kwave.kss -window-id 65011877 crash_function: qt_message_output executable: /usr/bin/kwave.kss kernel: 3.8.11-200.fc18.x86_64 package: kdeartwork-screensavers-4.10.2-1.fc18 reason: Process /usr/bin/kwave.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1 xsession_errors: case kwave.kss(14418): Got X error after loss of parent process. Terminating.
Looks like this may be fixed in kde-4.10.3 ... headed to updates-testing now. (at least I used to be able to reproduce this problem quite easily, now can't ... but only tried 2-3 times)
If abrt didn't show up in systray, I wouldn't even know there had been a crash. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: kflux.kss -window-id 65011877 crash_function: qt_message_output executable: /usr/bin/kflux.kss kernel: 3.9.2-200.fc18.x86_64 package: kdeartwork-screensavers-4.10.3-1.fc18 reason: Process /usr/bin/kflux.kss was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 xsession_errors: kflux.kss(1997): Got X error after loss of parent process. Terminating.
run screensaver reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: klines.kss -window-id 77594676 crash_function: qt_message_output executable: /usr/bin/klines.kss kernel: 3.8.9-200.fc18.i686 package: kdeartwork-screensavers-4.10.2-1.fc18 reason: Process /usr/bin/klines.kss was killed by signal 6 (SIGABRT) uid: 1000 xsession_errors:
I thought this had been fixed in 4.10.3, I guess not :( reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: kdeasciiquarium.kss -window-id 109051995 crash_function: qt_message_output executable: /usr/bin/kdeasciiquarium.kss kernel: 3.9.4-200.fc18.x86_64 package: kdeartwork-screensavers-4.10.3-1.fc18 reason: Process /usr/bin/kdeasciiquarium.kss was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 500
Screensaver is still crashing on exit with KDE 4.10.4. kdeartwork-screensavers-4.10.4-1.fc18.x86_64
Not fixed in Fedora 19. Why?
Because 1. this really needs to be filed with the upstream KDE developers at bugs.kde.org (which unfortunately ABRT cannot do, so somebody needs to go and file the bug) and 2. there is not enough information to fix the bug (the backtrace tells me there's an X error getting triggered, but I have no idea what kind of X error nor where; for all I know it could be a graphics driver bug, or a bug really ANYWHERE in the screensaver code; heck, in principle, all the crashes in the comments could even be DIFFERENT bugs which result in the same backtrace, because the backtrace really only tells us there was an X error at some place, though I doubt it).
*** Bug 981992 has been marked as a duplicate of this bug. ***
Bumping Version as per the duplicate (and comment #29).
*** Bug 984222 has been marked as a duplicate of this bug. ***
It appears related to coming out of the screensaver. Screensaver activated, but I interrupted before it had a chance to look. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: kslideshow.kss -window-id 20971588 crash_function: qt_message_output executable: /usr/bin/kslideshow.kss kernel: 3.9.9-302.fc19.x86_64 package: kdeartwork-screensavers-4.10.5-1.fc19 reason: Process /usr/bin/kslideshow.kss was killed by signal 6 (SIGABRT) runlevel: 3 5 uid: 1000 xsession_errors:
Computer went to screen saver after approximately 9 hours of uptime. A yum update had run which included a glibc updates since the last reboot (seems the most likely to cause odd issues. Upon screen unlock, the bug reporting tool showed this issue. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: kclock.kss -window-id 29360180 crash_function: qt_message_output executable: /usr/bin/kclock.kss kernel: 3.10.7-200.fc19.x86_64 package: kdeartwork-screensavers-4.10.5-1.fc19 reason: Process /usr/bin/kclock.kss was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
Not sure - package installation dependency errors due to rooted tertiary dependencies and mismatching/missing metadata. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: kdeasciiquarium.kss -window-id 67108916 crash_function: qt_message_output executable: /usr/bin/kdeasciiquarium.kss kernel: 3.10.7-100.fc18.i686.PAE package: kdeartwork-screensavers-4.10.5-1.fc18 reason: Process /usr/bin/kdeasciiquarium.kss was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
I set screensever to start after 1 minute. The screensaver locks the session and it requires password to unlock. If I move mouse before that screensaver locks the session the problem presents. This bug is present from Fedora 17 after a kdeartwork update. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: kslideshow.kss -window-id 92274756 crash_function: qt_message_output executable: /usr/bin/kslideshow.kss kernel: 3.10.10-200.fc19.x86_64 package: kdeartwork-screensavers-4.10.5-1.fc19 reason: Process /usr/bin/kslideshow.kss was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
Happens nearly every time the screen saver wakes up. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: kclock.kss -window-id 29360180 crash_function: qt_message_output executable: /usr/bin/kclock.kss kernel: 3.10.10-200.fc19.x86_64 package: kdeartwork-screensavers-4.10.5-1.fc19 reason: Process /usr/bin/kclock.kss was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
No idea. screen time out I guess reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: kblob.kss -window-id 33554484 crash_function: qt_message_output executable: /usr/bin/kblob.kss kernel: 3.10.9-100.fc18.i686.PAE package: kdeartwork-screensavers-4.10.5-1.fc18 reason: Process /usr/bin/kblob.kss was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
This happened while I was away from my desk. Running user programs were: VLC Firefox Dolphin Konsole - all sesions at prompt not running anything. Ksensors reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: kclock.kss -window-id 75497563 crash_function: qt_message_output executable: /usr/bin/kclock.kss kernel: 3.11.1-200.fc19.x86_64 package: kdeartwork-screensavers-4.11.1-1.fc19 reason: Process /usr/bin/kclock.kss was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
did a system update and during the update the screensaver start and I closed it after the update/reboot got the error mesage about the screensaver error and sent the error log to you reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: keuphoria.kss -window-id 60817460 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.10.6-100.fc18.i686 package: kdeartwork-screensavers-4.10.5-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
happens when screen saver becomes active reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: klines.kss -window-id 33554484 crash_function: qt_message_output executable: /usr/bin/klines.kss kernel: 3.11.6-200.fc19.x86_64 package: kdeartwork-screensavers-4.11.2-1.fc19 reason: Process /usr/bin/klines.kss was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
It's a screen saver. I saw the failure indication when I unlocked my screen. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: keuphoria.kss -window-id 85983284 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.11.4-101.fc18.x86_64 package: kdeartwork-screensavers-4.10.5-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) reported_to: uReport: BTHASH=412afdb496365792c863dd7ae1ee38819e331a5d runlevel: N 5 type: CCpp uid: 502
Screen saver error shown when the computer returned from the Sleep mode. Whether it occured before or after entering sleep is not known. I have the screensaver that looks like the "aura borealis". reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: keuphoria.kss -window-id 92274740 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.11.4-101.fc18.x86_64 package: kdeartwork-screensavers-4.10.5-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
The screen saver is disabled and power management enabled. During power management a screen saver (that looks like the aura borealis - not accessed via the screensaver options) is shown. Every time this ends and returns to standard operation whether in sleep mode or simply closing it after a keyboard or mouse event this error occurs. It does not affect the system and ignoring the error has no negative effects. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: keuphoria.kss -window-id 18874410 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.11.4-101.fc18.x86_64 package: kdeartwork-screensavers-4.10.5-1.fc18 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
(In reply to Kevin Kofler from comment #30) > Because 1. this really needs to be filed with the upstream KDE developers at > bugs.kde.org (which unfortunately ABRT cannot do, so somebody needs to go > and file the bug) and 2. there is not enough information to fix the bug (the > backtrace tells me there's an X error getting triggered, but I have no idea > what kind of X error nor where; for all I know it could be a graphics driver > bug, or a bug really ANYWHERE in the screensaver code; heck, in principle, > all the crashes in the comments could even be DIFFERENT bugs which result in > the same backtrace, because the backtrace really only tells us there was an > X error at some place, though I doubt it). Potential match in upstream bug tracker: https://bugs.kde.org/show_bug.cgi?id=323881
Another user experienced a similar problem: Screensaver (Euphoria) starts, and when interrupted after a while, I get "kdeartwork crashed" "keuphoria.kss killed by SIGABRT" messages about kdeartwork (CCpp). I have this same issue on multiple Fedora 19 installs on different systems. All F19 systems are fully updated. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: keuphoria.kss -window-id 62914612 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.11.10-200.fc19.x86_64 package: kdeartwork-screensavers-4.11.3-1.fc19 reason: keuphoria.kss killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: no specific action. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: kslideshow.kss -window-id 75497524 crash_function: qt_message_output executable: /usr/bin/kslideshow.kss kernel: 3.11.10-200.fc19.x86_64 package: kdeartwork-screensavers-4.11.3-1.fc19 reason: kslideshow.kss killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: not sure, interrupted screen saver reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: kclock.kss -window-id 71303220 crash_function: qt_message_output executable: /usr/bin/kclock.kss kernel: 3.12.5-200.fc19.x86_64 package: kdeartwork-screensavers-4.11.4-1.fc19 reason: kclock.kss killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Same problem here with kslideshow.kss in f20. See the ABRT after screensaver exits by moving mouse etc but only if more than one picture has appeared and maybe only if no password required (I think). Seems to be specific to recent fedora releases since don't find this in KDE bugzilla or for other OS's via google: "sigabrt kdeartwork". Since this is probably innocuous, can ABRT be set to ignore this error?
Well, given that KCrash/DrKonqi is apparently unable to catch this, only distros which have ABRT or something similar will get it reported in the first place. That said, there could also be an X11 or driver bug here. Without knowing the true source of the X error (which the backtrace cannot tell us, because it's caught and rethrown), there's no way to tell where the problem really is.
(In reply to gene smith from comment #50) > Same problem here with kslideshow.kss in f20. See the ABRT after screensaver > exits by moving mouse etc but only if more than one picture has appeared and > maybe only if no password required (I think). Seems to be specific to recent > fedora releases since don't find this in KDE bugzilla or for other OS's via > google: "sigabrt kdeartwork". Since this is probably innocuous, can ABRT be > set to ignore this error? Set-up same screensaver so that password is required to return to session (configured as a "screen locker"). Let session timeout (45m) and let screensaver run for a while (>5m since time with no password required set to 300s). After moving mouse and entering p/w, Abrt did not appear. So it appears exiting screensaver via a password does a clean shutdown somehow while exiting w/o the password does a less-clean shutdown (using SIGABRT?) of the screensaver, at least that's what I see. Also similar problem seen in Ubuntu and reported upstream at https://bugs.kde.org/show_bug.cgi?id=323881 (sorry, missed this link referenced above). Here's how I'm setting the screen-locker for normal usage with kde 4.11.4 shipped with fedora 20: (checked) Start automatically after 45m (checked) Require password after 300s Screen locker type: Screen saver Banners & Pictures/Slide Show
Another user experienced a similar problem: Stop solarwind screensaver. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: ksolarwinds.kss -window-id 16777284 crash_function: qt_message_output executable: /usr/bin/ksolarwinds.kss kernel: 3.13.6-100.fc19.x86_64 package: kdeartwork-screensavers-4.11.5-1.fc19 reason: ksolarwinds.kss killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.