Application that crashed: knotify4 Version of the application: 4.0 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: bug experienced when opening an kde app from Gnome desktop -- Backtrace: Application: KNotify (knotify4), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 strlen () at ../sysdeps/x86_64/strlen.S:31 #6 0x00007fd319660116 in *__GI___strdup (s=0x0) at strdup.c:42 #7 0x00007fd30663cb21 in ?? () from /usr/lib/libxine.so.1 #8 0x00007fd30663e6f9 in ?? () from /usr/lib/libxine.so.1 #9 0x00007fd30663ea7b in _x_scan_plugins () from /usr/lib/libxine.so.1 #10 0x00007fd306631c69 in xine_init () from /usr/lib/libxine.so.1 #11 0x00007fd3068bb4d1 in XineEngineData (this=0x24a4f40) at ../../xine/xineengine.cpp:58 #12 0x00007fd3068bb8f5 in Phonon::Xine::XineEngine::create (this=0x275f638) at ../../xine/xineengine.cpp:83 #13 0x00007fd3068d9769 in Backend (this=0x275f5f0, parent=<value optimized out>) at ../../xine/backend.cpp:77 #14 0x00007fd3068d9e73 in qt_plugin_instance () at ../../xine/backend.cpp:53 #15 0x00007fd30700c392 in Phonon::KdePlatformPlugin::createBackend (this=<value optimized out>, newService=) at ../../../phonon/platform_kde/kdeplatformplugin.cpp:155 #16 0x00007fd30700d56b in Phonon::KdePlatformPlugin::createBackend (this=0x25d4e70) at ../../../phonon/platform_kde/kdeplatformplugin.cpp:204 #17 0x00007fd31ba6e066 in Phonon::FactoryPrivate::createBackend (this=0x2744df0) at ../3rdparty/phonon/phonon/factory.cpp:118 #18 0x00007fd31ba6fc8f in Phonon::Factory::backend (createWhenNull=<value optimized out>) at ../3rdparty/phonon/phonon/factory.cpp:416 #19 0x00007fd31ba6a7c2 in Phonon::GlobalConfig::audioOutputDeviceListFor (this=<value optimized out>, category=<value optimized out>, override=<value optimized out>) at ../3rdparty/phonon/phonon/globalconfig.cpp:159 #20 0x00007fd31ba6ade5 in Phonon::GlobalConfig::audioOutputDeviceFor (this=<value optimized out>, category=<value optimized out>, override=<value optimized out>) at ../3rdparty/phonon/phonon/globalconfig.cpp:178 #21 0x00007fd31ba6599a in Phonon::AudioOutputPrivate::init (this=0x2744cf0, c=<value optimized out>) at ../3rdparty/phonon/phonon/audiooutput.cpp:94 #22 0x00007fd31ba66658 in AudioOutput (this=0x2478800, category=Phonon::NotificationCategory, parent=0x0) at ../3rdparty/phonon/phonon/audiooutput.cpp:67 #23 0x000000000040d531 in Player (this=0x260a8b8) at ../../knotify/notifybysound.cpp:59 #24 PlayerPool::getPlayer (this=0x260a8b8) at ../../knotify/notifybysound.cpp:99 #25 0x000000000040dc55 in NotifyBySound::notify (this=0x26e8370, eventId=2, config=<value optimized out>) at ../../knotify/notifybysound.cpp:243 #26 0x0000000000408a13 in KNotify::emitEvent (this=0x7fffa387ae10, e=0x2482ce0) at ../../knotify/knotify.cpp:179 #27 0x0000000000408e7d in KNotify::event (this=0x7fffa387ae10, 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 ../../knotify/knotify.cpp:128 #28 0x00000000004092ef in KNotifyAdaptor::event (this=0x26c5560, event=..., fromApp=..., contexts=<value optimized out>, title=..., text=<value optimized out>, image=..., actions=..., timeout=-1, winId=0) at ../../knotify/knotify.cpp:236 #29 0x000000000040a72b in KNotifyAdaptor::qt_metacall (this=0x26c5560, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa387a210) at ./knotify.moc:215 #30 0x00007fd31b362ad4 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:891 #31 0x00007fd31b363cc3 in QDBusConnectionPrivate::activateCall (this=<value optimized out>, object=0x26c5560, flags=273, msg=...) at qdbusintegrator.cpp:803 #32 0x00007fd31b364547 in QDBusConnectionPrivate::activateObject (this=<value optimized out>, node=..., msg=<value optimized out>, pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1347 #33 0x00007fd31b3647c8 in QDBusActivateObjectEvent::placeMetaCall (this=0x2489fc0) at qdbusintegrator.cpp:1464 #34 0x00007fd31b05b0f9 in QObject::event (this=0x7fffa387ae10, e=0x2489fc0) at kernel/qobject.cpp:1111 #35 0x00007fd31a29befc in QApplicationPrivate::notify_helper (this=0x245eb50, receiver=0x7fffa387ae10, e=0x2489fc0) at kernel/qapplication.cpp:4056 #36 0x00007fd31a2a31ce in QApplication::notify (this=0x7fffa387ae40, receiver=0x7fffa387ae10, e=0x2489fc0) at kernel/qapplication.cpp:4021 #37 0x00007fd31beb0ab6 in KApplication::notify (this=0x7fffa387ae40, receiver=0x7fffa387ae10, event=0x2489fc0) at ../../kdeui/kernel/kapplication.cpp:302 #38 0x00007fd31b04bc2c in QCoreApplication::notifyInternal (this=0x7fffa387ae40, receiver=0x7fffa387ae10, event=0x2489fc0) at kernel/qcoreapplication.cpp:610 #39 0x00007fd31b04c80a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x2434230) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #40 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x2434230) at kernel/qcoreapplication.cpp:1247 #41 0x00007fd31b074533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #42 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210 #43 0x00007fd31721ebce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #44 0x00007fd317222598 in ?? () from /lib/libglib-2.0.so.0 #45 0x00007fd3172226c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #46 0x00007fd31b0741a6 in QEventDispatcherGlib::processEvents (this=0x2433a80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #47 0x00007fd31a3304be in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #48 0x00007fd31b04a532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #49 0x00007fd31b04a904 in QEventLoop::exec (this=0x7fffa387ad60, flags=) at kernel/qeventloop.cpp:201 #50 0x00007fd31b04cab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #51 0x0000000000407f8f in main (argc=<value optimized out>, argv=<value optimized out>) at ../../knotify/main.cpp:73 Reported using DrKonqi
- When was the first time you experienced this crash ? - Did you had packages updates recently ? May be the "libxine" package was updated ? Thanks
*** Bug 221048 has been marked as a duplicate of this bug. ***
This could be related to bug 212867 too.. It seems to be a Xine error...
*** Bug 221229 has been marked as a duplicate of this bug. ***
- If you can reproduce the crash at will (or you experience this regularly), can you install the "libxine1-dbg" package and generate a complete backtrace (you can get more information at http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting ) to later report this issue at http://bugs.xine-project.org/. (do not forget to mention the version of your "libxine1" package. Thanks
my libxine1 (presently 1.1.16.3-0ubuntu4) package has been updated maybe when upgrading to KDE 4.3.85 fot test ; this I cannot confirm ; I have installed the libxine1-dbg ; my next report will include dbg info ; thanks for your help.
*** Bug 221768 has been marked as a duplicate of this bug. ***
*** Bug 221929 has been marked as a duplicate of this bug. ***
I did everything that was demanded to diagnos the bug but then I never received any procedure to resume proper functioning of KDE 4.3.2 (as reinstalled after failure of installation of KDE 4.3.85 for test); please can you telle me what I need to reinstall as wouls be installed whithe a fresh installation of KDE 4.3.2 (I have just installed KDE 4.3.2 on a new machine and I don not have the bug with KNotify then what ?
The bug is not caused by KDE, but by an external library "Xine". If the new machine is working properly, and it is using the same distribution, try using the same packages versions of "libxine" and "phonon"-related packages that you have in your working-machine. You may need to "move out"/delete your ~/.xine directory Regards
I compared both installations for libxine and phonon packages ; they are of same versions ; I removed extra xine packages in the buggy system just to make sur : still the same bug. I removed ~/.xine directory and even ~/.pulse directory : still no way to log into KDE session. I created an entirely dummy user just to make sure old KDE settings was not the problem : in this cas an akonadi window appears in front of a black screen and that is it. I just recall that now I have to uses KDE apps with Gnome which I did as well when testing KDE 4.3.85 I do not know what to do because there is nothiing really usable to simply re-install KDE from Gnome for example. Regards.
*** Bug 222472 has been marked as a duplicate of this bug. ***
*** Bug 215497 has been marked as a duplicate of this bug. ***
This was also reported in (K)Ubuntu at https://bugs.launchpad.net/ubuntu/+source/xine-lib/+bug/420686 .
Reported upstream: http://bugs.xine-project.org/show_bug.cgi?id=299 (I asked for workarounds too)
According to http://bugs.xine-project.org/show_bug.cgi?id=299#c1 , this could be caused by a full partition issue, truncating the contents of a xine config file. Removing ~/.xine/catalog.cache and restarting should fix that case. - Could the people experiencing the crash check it ? Thanks
Removing ~/.xine/catalog.cache appears to have solved the issue for now for me. However, I am dubious about the "full partition issue"... None of the partitions on my PC are anywhere close to being full, so I can't see why that file would get truncated due to lack of space. On 13/01/2010, Dario Andres <andresbajotierra@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=221045 > > > > > > --- Comment #16 from Dario Andres <andresbajotierra gmail com> 2010-01-14 > 00:32:09 --- > According to http://bugs.xine-project.org/show_bug.cgi?id=299#c1 , this > could > be caused by a full partition issue, truncating the contents of a xine > config > file. > Removing ~/.xine/catalog.cache and restarting should fix that case. > - Could the people experiencing the crash check it ? > Thanks > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. >
Apparently my bug though related is different : - Everything strated when upgrading from KDE 4.3.2 to KDE 3.2.85 for test : when upgrade was terminated no way to open a KDE session with a bug notification from KDE (Knotify4 segmentation fault). - I tried to remove all packages of KDE 3.2.85 and reinstall KDE 4.3.2 which is not really easy to do as not anticipated by the system really set for upgrade and not downgrade but the same bug was there with a crash with a Knotify4, so basically same as before. In both cases KDE 3.2.85 or KDE 4.3.2 I have to open a Gnome session to work where all KDE applications are available. Lately I have reinstalled all the xine and phonon and then phonon related packages ; now some improvement as the Knotify4 has desapeard but I end-up with a black screen which another dead end. I tried also to login with a new user just to make sure but no progress at all. Apparentlty the bug is still realted with sound as sound is all the time muted when loggin. I do not know what to do except reinstalling everingthing as there is no proper way to simply re-install KDE (Which should be investigated for user anyways). Any idee ? Thanks.
Eventually I reinstalled the whole distro ; now Kde 4.3.2 works fine I mean I can open a KDE session with no problems ; I even installed KDE 4.3.95 for test with no problem ; so the syndrom of the blackscreen after the KNotify4 bug that finally no more popped-up is behind me but I wished I could have got help in time.
*** Bug 225278 has been marked as a duplicate of this bug. ***
*** Bug 233957 has been marked as a duplicate of this bug. ***
*** Bug 236631 has been marked as a duplicate of this bug. ***