[apport] kdeinit crashed with SIGSEGV

StacktraceTop:?? ()

Thanks for your bug report. Please try to obtain a backtrace <http://wiki.ubuntu.com/DebuggingProgramCrash> and attach the file to the bug report. This will greatly help us in tracking down your problem.

Hi,

Which the program to debug?
kdeinit? If yes, kdeinit-dbgsym doesn't exist.
Then I ran gdb kdeinit 2>&1 | tee gdb.kdeinit.txt and attached the file.

Regards,

On 5/3/07, Andrew Ash <email address hidden> wrote:
>
> Thanks for your bug report. Please try to obtain a backtrace
> <http://wiki.ubuntu.com/DebuggingProgramCrash> and attach the file to
> the bug report. This will greatly help us in tracking down your problem.
>
> ** Changed in: kdelibs (Ubuntu)
> Assignee: (unassigned) => Andrew Ash
> Status: Unconfirmed => Needs Info
>
> --
> [apport] kdeinit crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/111565
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--

GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/kdeinit
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233094432 (LWP 8299)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
kdeinit: Shutting down running client.
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/henry/.DCOPserver_kubuntu-laptop__0
and start dcopserver again.
---------------------------------

KDE Daemon (kded) already running.
kbuildsycoca running...
Reusing existing ksycoca
kio (KService*): WARNING: Invalid Service : bask...

I believe kdelibs is the one to install the -dbgsym package for. The problem with these sort of crashes is that they're sporadic and hard to reproduce. Let me know if you're able to make more progress on this one. Is it even still a recurring problem?

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.