I have a crash on every startup but the backtrace it is nt usefull for a bug report How could i make it usefull ? Application: Nepomuk Service Stub (nepomukservicestub), signal: Floating point exception Application: nepomukservicestub (0.2) KDE Platform Version: 4.6.3 (4.6.3) Qt Version: 4.7.3 Operating System: Linux 2.6.38.7-desktop-1.mga x86_64 Distribution: "Mageia 1" -- Information about the crash: <Îε λεÏÏομÎÏειεÏ, ÏεÏιγÏάÏÏε Ïι κάναÏε ÏÏαν η εÏαÏμογή καÏÎÏÏεÏÏε.> The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generated ÎναÏοÏά Ïε https://bugs.kde.org
Assignee: bugsquad => balcaen.johnSource RPM: (none) => kdebase4-runtime
You can probably install some debug packages like kdebase4-runtime-debug kdelibs4-debug kdepimlibs4-debug
i have allready all of these installed. Today i did nt have the crash; i will try to investigate it better ... i will be back
i have it again but after a little more time after the startup this time. Maybe there are nt debug package for this?
May be this output during the crash can help to find which debug package i dont have ? [dglent@localhost ~]$ rpm -q -a | egrep 'nepomuk|kdebase' | sort kdebase4-common-4.6.3-3.mga1 kdebase4-debug-4.6.3-3.mga1 kdebase4-runtime-4.6.3-2.mga1 kdebase4-runtime-debug-4.6.3-2.mga1 kdebase4-workspace-4.6.3-7.mga1 kdebase4-workspace-debug-4.6.3-7.mga1 kdebase4-workspace-devel-4.6.3-7.mga1 kdebase4-workspace-googlegadgets-4.6.3-7.mga1 lib64nepomuk4-4.6.3-3.mga1 lib64nepomukquery4-4.6.3-3.mga1 lib64nepomuksync4-4.6.3-2.mga1 lib64nepomukutils4-4.6.3-3.mga1 [dglent@localhost ~]$ gdb --args nepomukservicestub nepomukfilewatch GNU gdb (GDB) 7.1-6.mga1 (Mageia release 1) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/nepomukservicestub...Reading symbols from /usr/lib/debug/usr/bin/nepomukservicestub.debug...done. done. (gdb) run Starting program: /usr/bin/nepomukservicestub nepomukfilewatch [Thread debugging using libthread_db enabled] warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libstdc++.so.6.0.14.debug warning: no loadable sections found in added symbol-file /usr/lib/debug/lib64/libgcc_s-4.5.2.so.1.debug warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libssl.so.1.0.0.debug warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libcrypto.so.1.0.0.debug "/usr/bin/nepomukservicestub(3248)" Soprano: "org.freedesktop.DBus.Error.UnknownObject - No such object path '/org/soprano/Server'" "/usr/bin/nepomukservicestub(3248)" Soprano: "QLocalSocket::connectToServer: Invalid name" "/usr/bin/nepomukservicestub(3248)" Soprano: "org.freedesktop.DBus.Error.UnknownObject - No such object path '/org/soprano/Server'" "/usr/bin/nepomukservicestub(3248)" Soprano: "QLocalSocket::connectToServer: Invalid name" [New Thread 0x7fffe729a710 (LWP 3265)] [New Thread 0x7fffe688c710 (LWP 3291)] [Thread 0x7fffe688c710 (LWP 3291) exited]
I confirm the bug and the lack of debugging information after installation kdebase4-runtime-debug kdelibs4-debug kdepimlibs4-debug
CC: (none) => kubmod
Just in case are you eventually using nepomuk with digikam too?
There is this bug upstream ( https://bugs.kde.org/show_bug.cgi?id=267666 ) & a possible workaround described here : http://forum.sabayon.org/viewtopic.php?t=23386
No, I do not use Nepomuk in digiKam. Much to the chagrin, the link https://bugs.kde.org/show_bug.cgi?id=267666 - "Not Found" Thanks, I'll try to take advice on the forum Sabayon.
(In reply to comment #8) > No, I do not use Nepomuk in digiKam. :/ > Much to the chagrin, the link https://bugs.kde.org/show_bug.cgi?id=267666 - > "Not Found" Kde bugzilla is now using a new host, so it's probably just a temporary error (it's working here)
Have to wait fix a bug in KDE. : ( The method described in forum Sabayon, unfortunately, did not correct the error. I need to try again. Bug appears when the change list of folders indexed Nepomuk.
i replugged my computer after 2 months today, i dont have this bug anymore (i did 3-5 reboots)
Closing as worksforme than.
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME