[opensuse-kde3] 13.1 knotify crash - kills sounds - howto restart after crash?
All, Every so often knotify will crash. (sample kcrash attached). When this occurs all systems sounds stop. I still get the beep and I can still play sound files, but all desktop sounds (shade/unshade, minimize, etc..) stop. How can I restart knotify (or whatever crashed) to recover desktop sounds without having to shutdown and restart kde? -- David C. Rankin, J.D.,P.E.
On 08/01/2014 04:42 PM, David C. Rankin wrote:
All,
Every so often knotify will crash. (sample kcrash attached). When this occurs all systems sounds stop. I still get the beep and I can still play sound files, but all desktop sounds (shade/unshade, minimize, etc..) stop. How can I restart knotify (or whatever crashed) to recover desktop sounds without having to shutdown and restart kde?
Ilya, Here is another knotify kcrash. It looks similar to the first. Let me know if I can file or provide more information. Thanks. -- David C. Rankin, J.D.,P.E.
On 08/05/2014 01:36 AM, David C. Rankin wrote:
On 08/01/2014 04:42 PM, David C. Rankin wrote:
All,
Every so often knotify will crash. (sample kcrash attached). When this occurs all systems sounds stop. I still get the beep and I can still play sound files, but all desktop sounds (shade/unshade, minimize, etc..) stop. How can I restart knotify (or whatever crashed) to recover desktop sounds without having to shutdown and restart kde?
Ilya,
Here is another knotify kcrash. It looks similar to the first. Let me know if I can file or provide more information. Thanks.
Ilya, I have managed to correlate the .xsession output with the knotify crash. In .xsession-errors I get: KNotify::playTimeout KNotify::playTimeout jack_client_new: deprecated Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started akode: Guessed format: xiph KNotify::playTimeout KNotify::playTimeout KCrash: Application 'knotify' crashing... Everything above the KCrash: line seems to repeat on a regular basis. It looks like there is a named socket problem with jack (I don't know jack about jack other than it keeps crashing). On this laptop, I have the following jack installed: jack-1.9.9.5-5.1.2.x86_64 jackEQ-0.5.9-309.7.x86_64 jackmixdesk-0.4+r125-1.7.x86_64 jack_mixer-9-2.3.x86_64 libjack0-1.9.9.5-5.1.2.x86_64 libjack-devel-1.9.9.5-5.1.2.x86_64 mpg123-jack-1.18.0-1.6.x86_64 xmms2-plugin-jack-0.8-2.67.x86_64 Running jack_test kills all sound and produces another knotify kcrash: [New LWP 10992] [New LWP 10991] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f3758d8c913 in select () from /lib64/libc.so.6 #0 0x00007f3758d8c913 in select () from /lib64/libc.so.6 #1 0x00007f375c463bd3 in QEventLoop::processEvents(unsigned int) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #2 0x00007f375c4b88b9 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #3 0x00007f375c4b87e2 in QEventLoop::exec() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #4 0x00007f3757b5357a in kdemain () from /opt/kde3/lib64/libkdeinit_knotify.so #5 0x00000000004087bd in ?? () #6 0x0000000000409391 in ?? () #7 0x0000000000409932 in ?? () #8 0x0000000000405cf9 in ?? () #9 0x00007f3758ccdbe5 in __libc_start_main () from /lib64/libc.so.6 #10 0x00000000004065dd in ?? () This looks like there is code that does not work with the current libc in QEventLoop::processEvents that ultimately blows up libqt-mt.so.3. The jack_test output is also attached. Sound is now dead and I'll have to restart sound or the desktop to get it back. Any ideas what is causing this? -- David C. Rankin, J.D.,P.E.
On 08/09/2014 01:47 AM, David C. Rankin wrote:
On 08/05/2014 01:36 AM, David C. Rankin wrote:
On 08/01/2014 04:42 PM, David C. Rankin wrote: <snip> [New LWP 10992] [New LWP 10991] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f3758d8c913 in select () from /lib64/libc.so.6 #0 0x00007f3758d8c913 in select () from /lib64/libc.so.6 #1 0x00007f375c463bd3 in QEventLoop::processEvents(unsigned int) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #2 0x00007f375c4b88b9 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #3 0x00007f375c4b87e2 in QEventLoop::exec() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #4 0x00007f3757b5357a in kdemain () from /opt/kde3/lib64/libkdeinit_knotify.so #5 0x00000000004087bd in ?? () #6 0x0000000000409391 in ?? () #7 0x0000000000409932 in ?? () #8 0x0000000000405cf9 in ?? () #9 0x00007f3758ccdbe5 in __libc_start_main () from /lib64/libc.so.6 #10 0x00000000004065dd in ?? ()
This looks like there is code that does not work with the current libc in QEventLoop::processEvents that ultimately blows up libqt-mt.so.3. The jack_test output is also attached. Sound is now dead and I'll have to restart sound or the desktop to get it back.
Any ideas what is causing this?
I have also noticed, that when search/replace is run in kate/kwrite, the following error is generated: cannot create new client; akode_client already exists Cannot read socket fd = 13 err = No such file or directory Unknown request 0 This may play into some of the kate crashes I've seen. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 08/09/2014 05:47 PM, David C. Rankin wrote:
On 08/09/2014 01:47 AM, David C. Rankin wrote:
On 08/05/2014 01:36 AM, David C. Rankin wrote:
On 08/01/2014 04:42 PM, David C. Rankin wrote: <snip> [New LWP 10992] [New LWP 10991] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f3758d8c913 in select () from /lib64/libc.so.6 #0 0x00007f3758d8c913 in select () from /lib64/libc.so.6 #1 0x00007f375c463bd3 in QEventLoop::processEvents(unsigned int) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #2 0x00007f375c4b88b9 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #3 0x00007f375c4b87e2 in QEventLoop::exec() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #4 0x00007f3757b5357a in kdemain () from /opt/kde3/lib64/libkdeinit_knotify.so #5 0x00000000004087bd in ?? () #6 0x0000000000409391 in ?? () #7 0x0000000000409932 in ?? () #8 0x0000000000405cf9 in ?? () #9 0x00007f3758ccdbe5 in __libc_start_main () from /lib64/libc.so.6 #10 0x00000000004065dd in ?? ()
This looks like there is code that does not work with the current libc in QEventLoop::processEvents that ultimately blows up libqt-mt.so.3. The jack_test output is also attached. Sound is now dead and I'll have to restart sound or the desktop to get it back.
Any ideas what is causing this?
I have also noticed, that when search/replace is run in kate/kwrite, the following error is generated:
cannot create new client; akode_client already exists Cannot read socket fd = 13 err = No such file or directory Unknown request 0
This may play into some of the kate crashes I've seen.
Ilya, Here is an additional knotify kcrash regarding jack. It picks up with #5 so putting together the prior kcrash from Aug. 9 and this one, it should provide a complete backtrace. It is attached. Also, I need to know who is maintaining opensuse/kde3?? There are bugs that need looking into. We need to file them so they can be tracked and fixed. Who is building kde3? I don't mind helping pick through the code, but I do not have a build environment for kde3 and I don't have a complete source. Let me know who is building and where these bugs need to go. If we are not fixing the little one, they will ultimately grow until we have a real problem. -- David C. Rankin, J.D.,P.E.
participants (1)
-
David C. Rankin