FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian KDE

 
 
LinkBack Thread Tools
 
Old 07-06-2012, 07:57 AM
Jacopo Nespolo
 
Default kde daemon crashes

Dear All,
I'm running on Sid with all the latest upgrades. Kde Daemon often
crashes on me, sometimes randomly, sometimes as I open Amarok or
resume from screen lock or sleep. I wasn't really able to link the
crash to a specific series of events.

Unfortunately, when I try to generate a report, I can't get any
backtrace whatsoever. Can anyone point out which packages I should
install to at least try to understand what's going on?
Has anyone else got this problem?

I used to run on testing up until about a month ago and wasn't having
this issue back then. I moved to sid via a fresh install, so it
shouldn't be an upgrade issue, but rather a regression.

Any help is most welcome.
Thanks all,
Jacopo


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAPRP9-un9j2T909gTgbnfEQGva6dYNBhwBR9Fzk_sjpUrnBKEA@mail. gmail.com">http://lists.debian.org/CAPRP9-un9j2T909gTgbnfEQGva6dYNBhwBR9Fzk_sjpUrnBKEA@mail. gmail.com
 
Old 07-06-2012, 08:28 AM
Xavier Brochard
 
Default kde daemon crashes

Jacopo Nespolo wrote:
> Unfortunately, when I try to generate a report, I can't get any
> backtrace whatsoever. Can anyone point out which packages I should
> install to at least try to understand what's going on?

You need to install corresponding kde debug packages. They have name ending
in "-dbg" (it will install also qt and libc6 debug packages).

xavier


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/jt67lq$ps$1@dough.gmane.org
 
Old 07-06-2012, 09:05 AM
Sune Vuorela
 
Default kde daemon crashes

On 2012-07-06, Jacopo Nespolo <j.nespolo@gmail.com> wrote:
> Dear All,
> Unfortunately, when I try to generate a report, I can't get any
> backtrace whatsoever. Can anyone point out which packages I should
> install to at least try to understand what's going on?

Finding the right bits here is a bit convoluted, since 'other people'
can plug in bits to the kde daemon.

But the first place to start is to install kdelibs5-dbg and get a
backtrace. From there, we can hopefully get a idea on where to go next.

/Sune


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: slrnjvdaie.d1u.nospam@sshway.ssh.pusling.com">http ://lists.debian.org/slrnjvdaie.d1u.nospam@sshway.ssh.pusling.com
 
Old 07-06-2012, 09:45 AM
Martin Steigerwald
 
Default kde daemon crashes

Am Freitag, 6. Juli 2012 schrieb Jacopo Nespolo:
> Dear All,
> I'm running on Sid with all the latest upgrades. Kde Daemon often
> crashes on me, sometimes randomly, sometimes as I open Amarok or
> resume from screen lock or sleep. I wasn't really able to link the
> crash to a specific series of events.
>
> Unfortunately, when I try to generate a report, I can't get any
> backtrace whatsoever. Can anyone point out which packages I should
> install to at least try to understand what's going on?
> Has anyone else got this problem?
>
> I used to run on testing up until about a month ago and wasn't having
> this issue back then. I moved to sid via a fresh install, so it
> shouldn't be an upgrade issue, but rather a regression.

On my ThinkPad T520 I have one crash per login. But AFAIR only for one of
my KDE users. I didn愒 take time to research on this.

--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207061145.48884.Martin@lichtvoll.de">http://lists.debian.org/201207061145.48884.Martin@lichtvoll.de
 
Old 07-07-2012, 08:21 AM
Jacopo Nespolo
 
Default kde daemon crashes

Hi,
Following Sune's answer, I got a rudimentary backtrace. It seems to me that kde
daemon is crashing every first time i open amarok.

Can anyone suggest against which packet i should file the bug?
Also, the crash handler reports that the backtrace is uncomplete and
of little use. Can anyone suggest which other debugging packages i
could use?
Following is a reduced version of the backtrace.
Thanks a lot,
j

Application: KDE Daemon (kdeinit4), signal: Aborted
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[Current thread is 1 (Thread 0xb56bd710 (LWP 3050))]

Thread 3 (Thread 0xacdffb70 (LWP 3066)):
#0 timerSourcePrepare (source=0x8b86898, timeout=0xacdff06c) at
kernel/qeventdispatcher_glib.cpp:157
#1 0xb59b3102 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2 0xb59b384f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0xb59b3ab1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4 0xb6d6c91f in QEventDispatcherGlib:rocessEvents (this=0x8be3e58,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5 0xb6d390dc in QEventLoop:rocessEvents
(this=this@entry=0xacdff1f8, flags=...) at kernel/qeventloop.cpp:149
#6 0xb6d393d1 in QEventLoop::exec (this=0xacdff1f8, flags=...) at
kernel/qeventloop.cpp:204
#7 0xb6c25b2c in QThread::exec (this=0x8b90438) at thread/qthread.cpp:501
#8 0xb6d177dd in QInotifyFileSystemWatcherEngine::run
(this=0x8b90438) at io/qfilesystemwatcher_inotify.cpp:248
#9 0xb6c28ef0 in QThreadPrivate::start (arg=0x8b90438) at
thread/qthread_unix.cpp:307
#10 0xb0c8d251 in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1
#11 0x5c8b0824 in ?? ()

[... many more of these lines ...]

#81 0x0f910485 in ?? ()
#82 0xb60fc095 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 0xac4a1b70 (LWP 3151)):
#0 0xb5a88524 in __pthread_mutex_unlock_usercnt () from
/lib/i386-linux-gnu/i686/cmov/libpthread.so.0
#1 0xb5f6a576 in pthread_mutex_unlock () from
/lib/i386-linux-gnu/i686/cmov/libc.so.6
#2 0xb59f36e0 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0xb59b383f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0xb59b3e2b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5 0xac574bda in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6 0xb59d7d93 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7 0xb0c8d251 in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1
#8 0x5c8b0824 in ?? ()

[... and yet more ...]

#78 0x0f910485 in ?? ()
#79 0xb60fc095 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0xb56bd710 (LWP 3050)):
[KCrash Handler]
#7 0xb7730424 in __kernel_vsyscall ()
#8 0xb5eb7941 in raise () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#9 0xb5ebad72 in abort () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#10 0xb5eb0b58 in __assert_fail () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#11 0xab9d4491 in snd_hctl_handle_events () from
/usr/lib/i386-linux-gnu/libasound.so.2
#12 0xab9e1e19 in snd_mixer_handle_events () from
/usr/lib/i386-linux-gnu/libasound.so.2
#13 0xabac8b18 in ?? () from /usr/lib/kde4/kded_kmixd.so
#14 0xabac0904 in ?? () from /usr/lib/kde4/kded_kmixd.so
#15 0xabac04e0 in ?? () from /usr/lib/kde4/kded_kmixd.so
#16 0xb6d4c83a in QMetaCallEvent:laceMetaCall (this=0x8d42e70,
object=0x8cc96d0) at kernel/qobject.cpp:525
#17 0xb6d50d7b in QObject::event (this=0x8cc96d0, e=0x8d42e70) at
kernel/qobject.cpp:1195
#18 0xb622449c in QApplicationPrivate::notify_helper (this=0x8a4bb68,
receiver=0x8cc96d0, e=0x8d42e70) at kernel/qapplication.cpp:4556
#19 0xb6228e9f in QApplication::notify (this=0x8d42e70,
receiver=0x8cc96d0, e=0x8d42e70) at kernel/qapplication.cpp:3938
#20 0xb74bf581 in KApplication::notify (this=0xbfcd2a8c,
receiver=0x8cc96d0, event=0x8d42e70) at
../../kdeui/kernel/kapplication.cpp:311
#21 0xb6d3a60e in QCoreApplication::notifyInternal (this=0xbfcd2a8c,
receiver=0x8cc96d0, event=0x8d42e70) at
kernel/qcoreapplication.cpp:915
#22 0xb6d3e81d in sendEvent (event=<optimized out>,
receiver=<optimized out>) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0,
event_type=0, data=0x895aa40) at kernel/qcoreapplication.cpp:1539
#24 0xb6d3ea9c in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1432
#25 0xb6d6c784 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#26 postEventSourceDispatch (s=0x8a4d830) at
kernel/qeventdispatcher_glib.cpp:279
#27 0xb59b3633 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#28 0xb59b39d0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0xb59b3ab1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#30 0xb6d6c901 in QEventDispatcherGlib:rocessEvents (this=0x895bd98,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#31 0xb62d71fa in QGuiEventDispatcherGlib:rocessEvents
(this=0x895bd98, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0xb6d390dc in QEventLoop:rocessEvents
(this=this@entry=0xbfcd28f8, flags=...) at kernel/qeventloop.cpp:149
#33 0xb6d393d1 in QEventLoop::exec (this=0xbfcd28f8, flags=...) at
kernel/qeventloop.cpp:204
#34 0xb6d3eb4a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#35 0xb62222f4 in QApplication::exec () at kernel/qapplication.cpp:3817
#36 0xb553a68a in kdemain (argc=1, argv=0x89e8728) at ../../kded/kded.cpp:924
#37 0x0804fdbe in launch (argc=argc@entry=1,
_name=_name@entry=0x8052827 "kded4", args=<optimized out>,
args@entry=0x0, cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized
out>, envs@entry=0x0, reset_env=reset_env@entry=false,
tty=tty@entry=0x0, avoid_loops=avoid_loops@entry=false,
startup_id_str=startup_id_str@entry=0x80526ae "0") at
../../kinit/kinit.cpp:746
#38 0x0804cec0 in main (argc=4, argv=0xbfcd30f4, envp=0xbfcd3108) at
../../kinit/kinit.cpp:1861


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAPRP9-tTikPmzwtrHw0Z8tE-h0emsCQPOSng_OZB7fJ_U+VMAw@mail.gmail.com">http://lists.debian.org/CAPRP9-tTikPmzwtrHw0Z8tE-h0emsCQPOSng_OZB7fJ_U+VMAw@mail.gmail.com
 
Old 07-07-2012, 09:52 AM
Martin Steigerwald
 
Default kde daemon crashes

Am Samstag, 7. Juli 2012 schrieb Jacopo Nespolo:
> Hi,
> Following Sune's answer, I got a rudimentary backtrace. It seems to me
> that kde daemon is crashing every first time i open amarok.
>
> Can anyone suggest against which packet i should file the bug?
> Also, the crash handler reports that the backtrace is uncomplete and
> of little use. Can anyone suggest which other debugging packages i
> could use?
> Following is a reduced version of the backtrace.
> Thanks a lot,
> j
>
> Application: KDE Daemon (kdeinit4), signal: Aborted
> Using host libthread_db library
> "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
> [Current thread is 1 (Thread 0xb56bd710 (LWP 3050))]
[因
> #10 0xb0c8d251 in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1
[因
> #81 0x0f910485 in ?? ()
> #82 0xb60fc095 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
[因
> /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb59b383f in ?? () from
> /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb59b3e2b in g_main_loop_run

Thanks. Seems there are still some debug packages missing like

libglib2.0-0-dbg

martin@merkaba:~> apt-cache search libgl1-mesa dbg | cut -c1-72
libgl1-mesa-dri-dbg - Debugging symbols for the Mesa DRI modules
libgl1-mesa-dri-experimental-dbg - Debugging symbols for the experimenta
libgl1-mesa-glx-dbg - Debugging symbols for the Mesa GLX runtime
libgl1-mesa-swx11-dbg - free implementation of the OpenGL API -- debuggi

martin@merkaba:~> locate libQtGui.so
/usr/lib/x86_64-linux-gnu/libQtGui.so
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8
/usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2
martin@merkaba:~> dpkg -S /usr/lib/x86_64-linux-gnu/libQtGui.so
libqt4-dev: /usr/lib/x86_64-linux-gnu/libQtGui.so
martin@merkaba:~> apt-cache search libqt4 dbg
libqt4-dbg - Debug-Symbole f羹r die Qt-4-Bibliothek
[因

Why dpkg report libQtGui.so to be in a "-dev" package is beyond me
currently.

--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207071152.07052.Martin@lichtvoll.de">http://lists.debian.org/201207071152.07052.Martin@lichtvoll.de
 
Old 07-07-2012, 10:19 AM
Diederik de Haas
 
Default kde daemon crashes

On Saturday 07 July 2012 10:21:28 Jacopo Nespolo wrote:
> Can anyone suggest against which packet i should file the bug?
> Also, the crash handler reports that the backtrace is uncomplete and
> of little use.

Not yet. You still need more debug info.
You'll have enough info when the crash handler gives you 3 stars and/or says
that you have enough.

> Can anyone suggest which other debugging packages i could use?

aptitude search <keyword>.*-dbg$
Where you get <keyword> from a line which contains ?? in it's backtrace, like:
#2 0xb59b384f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
In this case 'libglib' is a good candidate for <keyword>

> It seems to me that kde daemon is crashing every first time i open amarok.

In that case using amarok as <keyword> could also be usefull ;-)

HTH,
Diederik


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207071219.35629.didi.debian@cknow.org">http://lists.debian.org/201207071219.35629.didi.debian@cknow.org
 
Old 07-07-2012, 10:33 AM
hrvojes
 
Default kde daemon crashes

On Saturday 07 of July 2012 11:52:06 Martin Steigerwald wrote:
> Am Samstag, 7. Juli 2012 schrieb Jacopo Nespolo:
> > Hi,
> > Following Sune's answer, I got a rudimentary backtrace. It seems to me
> > that kde daemon is crashing every first time i open amarok.
> >
> > Can anyone suggest against which packet i should file the bug?
> > Also, the crash handler reports that the backtrace is uncomplete and
> > of little use. Can anyone suggest which other debugging packages i
> > could use?
> > Following is a reduced version of the backtrace.
> > Thanks a lot,
> > j
> >
> > Application: KDE Daemon (kdeinit4), signal: Aborted
> > Using host libthread_db library
> > "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
> > [Current thread is 1 (Thread 0xb56bd710 (LWP 3050))]
>
> [因
>
> > #10 0xb0c8d251 in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1
>
> [因
>
> > #81 0x0f910485 in ?? ()
> > #82 0xb60fc095 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
> > Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> [因
>
> > /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb59b383f in ?? () from
> > /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb59b3e2b in g_main_loop_run
>
> Thanks. Seems there are still some debug packages missing like
>
> libglib2.0-0-dbg
>
> martin@merkaba:~> apt-cache search libgl1-mesa dbg | cut -c1-72
> libgl1-mesa-dri-dbg - Debugging symbols for the Mesa DRI modules
> libgl1-mesa-dri-experimental-dbg - Debugging symbols for the experimenta
> libgl1-mesa-glx-dbg - Debugging symbols for the Mesa GLX runtime
> libgl1-mesa-swx11-dbg - free implementation of the OpenGL API -- debuggi
>
> martin@merkaba:~> locate libQtGui.so
> /usr/lib/x86_64-linux-gnu/libQtGui.so
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.2
> martin@merkaba:~> dpkg -S /usr/lib/x86_64-linux-gnu/libQtGui.so
> libqt4-dev: /usr/lib/x86_64-linux-gnu/libQtGui.so
> martin@merkaba:~> apt-cache search libqt4 dbg
> libqt4-dbg - Debug-Symbole f羹r die Qt-4-Bibliothek
> [因
>
> Why dpkg report libQtGui.so to be in a "-dev" package is beyond me
> currently.

Example:
ln -f -
s"libQtGui.so.4.8.2""/build/buildd/qt4x11-4.8.2/debian/tmp//usr/lib/i386-
linux-gnu/libQtGui.so"

ls -l /usr/lib/x86_64-linux-gnu/libQtGui.so
lrwxrwxrwx 1 root root 17 Jun 20 02:33 /usr/lib/x86_64-linux-gnu/libQtGui.so -
> libQtGui.so.4.8.2



--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/3300373.uv4qSZziya@shumarija
 
Old 07-07-2012, 10:35 AM
hrvojes
 
Default kde daemon crashes

On Friday 06 of July 2012 09:57:49 Jacopo Nespolo wrote:
> Dear All,
> I'm running on Sid with all the latest upgrades. Kde Daemon often
> crashes on me, sometimes randomly, sometimes as I open Amarok or
> resume from screen lock or sleep. I wasn't really able to link the
> crash to a specific series of events.
>
> Unfortunately, when I try to generate a report, I can't get any
> backtrace whatsoever. Can anyone point out which packages I should
> install to at least try to understand what's going on?
> Has anyone else got this problem?
>
> I used to run on testing up until about a month ago and wasn't having
> this issue back then. I moved to sid via a fresh install, so it
> shouldn't be an upgrade issue, but rather a regression.
>
> Any help is most welcome.
> Thanks all,
> Jacopo

You can install kde-runtime-dbg, it will pull other relevant debug (kdelibs
and qt) packages.


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/1445010.8p4RGX8IAr@shumarija
 
Old 07-07-2012, 12:08 PM
john Culleton
 
Default kde daemon crashes

On Sat, 7 Jul 2012 10:21:28 +0200
Jacopo Nespolo <j.nespolo@gmail.com> wrote:

> Hi,
> Following Sune's answer, I got a rudimentary backtrace. It seems to
> me that kde daemon is crashing every first time i open amarok.
>
> Can anyone suggest against which packet i should file the bug?
> Also, the crash handler reports that the backtrace is uncomplete and
> of little use. Can anyone suggest which other debugging packages i
> could use?
> Following is a reduced version of the backtrace.
> Thanks a lot,
> j


Amorak is horrid. My ultimate solution: Download and install
Trinity. Thet gives you a cloned version of KDE 3.5 with no
Amorak, no Neopemuk hooray! Your KDE4 is still a choice for those
few things like Okular not supported by KDE 3.5.

I find Trinity more reliable than XFCE, which is my other
alternative to KDE4.
--
John Culleton
Free list of books for self-publishers:
http://wexfordpress.net/shortlist.html
Police Procedural and Expose: "Death Wore Black"
"Create Book Covers with Scribus"
http://www.booklocker.com/books/4055.html


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120707080834.763292a9@sda3.wexfordpress.net">htt p://lists.debian.org/20120707080834.763292a9@sda3.wexfordpress.net
 

Thread Tools




All times are GMT. The time now is 05:03 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org