Application: knotify4 (4.0) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.31.12-0.2-desktop x86_64 Distribution: "openSUSE 11.2 (x86_64)" -- Information about the crash: KNotify crashed when my machine woke up from its S3 state. -- Backtrace: Application: KNotify (knotify4), signal: Bus error [KCrash Handler] #5 0x00007f071225df5e in pa_shm_create_rw () from /usr/lib64/libpulsecommon-0.9.21.so #6 0x00007f0712252676 in pa_mempool_new () from /usr/lib64/libpulsecommon-0.9.21.so #7 0x00007f07152a8958 in pa_context_new_with_proplist () from /usr/lib64/libpulse.so.0 #8 0x00007f0718c33d08 in Phonon::PulseSupport::PulseSupport (this=0x6de530) at /usr/src/debug/phonon-4.4/phonon/pulsesupport.cpp:712 #9 0x00007f0718c3403f in Phonon::PulseSupport::getInstance () at /usr/src/debug/phonon-4.4/phonon/pulsesupport.cpp:668 #10 0x00007f0718c1bd89 in Phonon::AudioOutputPrivate::init (this=0x741200, c=<value optimized out>) at /usr/src/debug/phonon-4.4/phonon/audiooutput.cpp:102 #11 0x000000000040d231 in Player (this=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.4.2/knotify/notifybysound.cpp:59 #12 PlayerPool::getPlayer (this=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.4.2/knotify/notifybysound.cpp:99 #13 0x000000000040d76e in NotifyBySound::notify (this=0x70d4f0, eventId=1096, config=0x7fff94409140) at /usr/src/debug/kdebase-runtime-4.4.2/knotify/notifybysound.cpp:243 #14 0x0000000000408d83 in KNotify::emitEvent (this=0x7fff9440a400, e=0x734980) at /usr/src/debug/kdebase-runtime-4.4.2/knotify/knotify.cpp:179 #15 0x0000000000409042 in KNotify::event (this=0x7fff9440a400, event=<value optimized out>, appname=<value optimized out>, contexts=<value optimized out>, title=<value optimized out>, text=<value optimized out>, image=..., actions=..., timeout=-1, winId=0) at /usr/src/debug/kdebase-runtime-4.4.2/knotify/knotify.cpp:128 #16 0x000000000040937f in KNotifyAdaptor::event (this=0x6db700, event=..., fromApp=..., contexts=<value optimized out>, title=..., text=<value optimized out>, image=..., actions=..., timeout=-1, winId=0) at /usr/src/debug/kdebase-runtime-4.4.2/knotify/knotify.cpp:236 #17 0x000000000040a05b in KNotifyAdaptor::qt_metacall (this=0x6db700, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff94409690) at /usr/src/debug/kdebase-runtime-4.4.2/build/knotify/knotify.moc:227 #18 0x00007f071851828e in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:904 #19 0x00007f07185190ab in QDBusConnectionPrivate::activateCall (this=<value optimized out>, object=0x6db700, flags=273, msg=...) at qdbusintegrator.cpp:816 #20 0x00007f0718519b2d in QDBusConnectionPrivate::activateObject (this=<value optimized out>, node=<value optimized out>, msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1364 #21 0x00007f0718519dc8 in QDBusActivateObjectEvent::placeMetaCall (this=0x7382b0) at qdbusintegrator.cpp:1477 #22 0x00007f07181ee6c9 in QObject::event (this=0x7fff9440a400, e=0x7382b0) at kernel/qobject.cpp:1248 #23 0x00007f071759ae1c in QApplicationPrivate::notify_helper (this=0x64bf10, receiver=0x7fff9440a400, e=0x7382b0) at kernel/qapplication.cpp:4300 #24 0x00007f07175a13fb in QApplication::notify (this=0x7fff9440a430, receiver=0x7fff9440a400, e=0x7382b0) at kernel/qapplication.cpp:4183 #25 0x00007f071900c506 in KApplication::notify (this=0x7fff9440a430, receiver=0x7fff9440a400, event=0x7382b0) at /usr/src/debug/kdelibs-4.4.2/kdeui/kernel/kapplication.cpp:302 #26 0x00007f07181de98c in QCoreApplication::notifyInternal (this=0x7fff9440a430, receiver=0x7fff9440a400, event=0x7382b0) at kernel/qcoreapplication.cpp:704 #27 0x00007f07181e1107 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215 #28 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1345 #29 0x00007f0718208373 in sendPostedEvents () at kernel/qcoreapplication.h:220 #30 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276 #31 0x00007f0713a2cdee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #32 0x00007f0713a307b8 in ?? () from /usr/lib64/libglib-2.0.so.0 #33 0x00007f0713a308e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #34 0x00007f0718207eb3 in QEventDispatcherGlib::processEvents (this=0x627bc0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #35 0x00007f071764951e in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #36 0x00007f07181dd2a2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #37 0x00007f07181dd67c in QEventLoop::exec (this=0x7fff9440a350, flags=) at kernel/qeventloop.cpp:201 #38 0x00007f07181e13cb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #39 0x0000000000407f5f in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-runtime-4.4.2/knotify/main.cpp:73 Reported using DrKonqi
Bus errors generally happen when bad things happen with SHM. It seems that the SHM region is not setup properly after suspend and that subsequently causes this problem. I'll ask around and see if anyone else has had this problem before (not seem it before) and what do to about it.
*** Bug 241488 has been marked as a duplicate of this bug. ***
With root user I can do anything on shm: szotsaki:/dev/shm # ls -lh összesen 2,0G -rw-r--r-- 1 root root 2,0G jún 28 22.26 preloadtrace.log -r-------- 1 aki users 65M jún 28 23.41 pulse-shm-99266583 -rw-r--r-- 1 root root 0 jún 27 21.19 warpclock szotsaki:/dev/shm # du -h 2,0G . szotsaki:/dev/shm # df -h Fájlrendszer Méret Fogl. Szab. Fo.% Csatl. pont /dev/sda6 483G 174G 285G 38% / szotsaki:/dev/shm # touch tempFile szotsaki:/dev/shm # echo "temptemptemptemptemptemptemp" > tempFile szotsaki:/dev/shm # cat tempFile temptemptemptemptemptemptemp With a normal user I can create files there but then I cannot write into them (I don't know if it's normal): aki@szotsaki:/dev/shm> touch temp2 aki@szotsaki:/dev/shm> echo "temptemptemptemp" > temp2 bash: echo: write error: No space left on device
That 2 gig file looks suspicious. What puts that there and why? Whatever the problem is, abusing SHM like that is probably the root cause. There is likely an upper limit or a similar concept to root-reserved blocks in SHM mounts. Either way that's the problem. Try and work out how to avoid that massive file and the problem will likely go away.
Hmm, I simply deleted the 2 GB file. It contained something like this: 0.028 384 boot.startprelo fork 405 0.028 405 boot.startprelo stat . 0.028 405 boot.startprelo stat /bin/pidof 0.028 405 boot.startprelo stat /bin/pidof 0.028 405 boot.startprelo stat /bin/pidof 0.028 405 boot.startprelo stat /bin/pidof 0.028 405 boot.startprelo stat /bin/pidof 0.028 405 boot.startprelo stat /bin/pidof 0.028 405 boot.startprelo execve /bin/pidof 0.028 405 pidof open 3 /etc/ld.so.cache ... 53.050 3364 plasma-desktop stat /etc/localtime 53.053 3467 kontact stat /etc/localtime 53.053 3467 kontact stat /etc/localtime 53.058 3358 kwin stat /etc/localtime 53.058 3358 kwin stat /etc/localtime 53.065 3358 kwin stat /etc/localtime 53.065 3358 kwin stat /etc/localtime 53.065 3358 kwin stat /etc/localtime 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.066 3363 knotify4 fstat 14 53.069 3358 kwin stat /etc/localtime 53.069 3358 kwin stat /etc/localtime 53.069 3358 kwin stat /etc/localtime 53.070 3467 kontact stat /etc/localtime 53.070 3467 kontact stat /etc/localtime 53.071 3364 plasma-desktop stat /etc/localtime ... But it has been created again. Interestingly, after a day usage its size is 1 GB. I haven't experienced KNotify crash, but at the time the file reaches its upper limit (probably 2 GB) I'll write here.
*** This bug has been marked as a duplicate of bug 246448 ***
Don;t think the duplicates stuff is right... I'll reopen this one and remark another bug as a dupe of this in a moment :)
*** Bug 246762 has been marked as a duplicate of this bug. ***
*** Bug 254609 has been marked as a duplicate of this bug. ***
*** Bug 260298 has been marked as a duplicate of this bug. ***
Are there some people who noticed this crash lately? On openSUSE 12.1 there's nothing interesting in /dev/shm (almost empty). In the meantime I switched to phonon-mplayer and maybe because of that I don't experience this bug any more.
Is this still relevant?
I think this bug got fixed in the meantime.