Summary: | KNotify crashed when I tried to sleep my machine | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Phonon | Reporter: | Unknown <null> |
Component: | Xine backend | Assignee: | Matthias Kretz <kretz> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | colin, martin.sandsmark, myriam, null |
Priority: | NOR | ||
Version: | 4.4.1 (KDE 4.4.4) | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Unknown
2010-06-12 02:14:35 UTC
Created attachment 48445 [details]
New crash information added by DrKonqi
knotify4 (4.0) on KDE Platform 4.4.90 (KDE 4.4.90 (KDE 4.5 RC1)) "release 2" using Qt 4.6.3
- What I was doing when the application crashed:
I was logging into KDE when KNotify crashed.
Although the backtrace is the same, DrKonqui didn't find any reports when it was searching.
-- Backtrace (Reduced):
#6 0x00007f274fa11cb2 in pa_shm_cleanup () from /usr/lib64/libpulsecommon-0.9.21.so
#7 0x00007f274fa11e75 in pa_shm_create_rw () from /usr/lib64/libpulsecommon-0.9.21.so
#8 0x00007f274fa06676 in pa_mempool_new () from /usr/lib64/libpulsecommon-0.9.21.so
#9 0x00007f2752817958 in pa_context_new_with_proplist () from /usr/lib64/libpulse.so.0
#10 0x00007f275669590f in Phonon::PulseSupport::PulseSupport (this=0x89d760) at /usr/src/debug/phonon-4.4.2/phonon/pulsesupport.cpp:718
This generally means that some process has filled up SHM space or for some other reason the SHM space is not currently writable/available. The file sizes reported in /dev/shm are generally bogus (ls -l). du should give you accurate usage. (e.g. I have ~20 64meg files in /dev/shm, but du reports only 5.8megs used). If possible try to work out what other files are in /dev/shm or why you are not allowed to write there. It could be that during part of the resume process your user does not have write permission in /dev/shm? Also you've reported this bug before: #236524 *** This bug has been marked as a duplicate of bug 236524 *** |