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.