[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#380577: marked as done (kontact crashing on startup)



Your message dated Thu, 10 Aug 2006 18:37:17 -0700
with message-id <20060811013717.GA8265@radio.m-a-g.net>
and subject line kontact crashing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: kontact
Version: 4:3.5.3-3
Severity: grave
Justification: renders package unusable

kontact is crashing on startup.  Attached is the backtrace.



-- System Information:
Debian Release: by Linux-Systeme
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-beyond2.2
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=UTF-8)

Versions of packages kontact depends on:
ii  kdelibs4c2a                   4:3.5.3-1  core libraries and binaries for al
ii  libc6                         2.3.6-16   GNU C Library: Shared libraries
ii  libgcc1                       1:4.1.1-9  GCC support library
ii  libkcal2b                     4:3.5.3-3  KDE calendaring library
ii  libkdepim1a                   4:3.5.3-3  KDE PIM library
ii libkpimidentities1 4:3.5.3-3 KDE PIM user identity information ii libqt3-mt 3:3.3.6-3 Qt GUI Library (Threaded runtime v
ii  libstdc++6                    4.1.1-9    The GNU Standard C++ Library v3

Versions of packages kontact recommends:
ii  kaddressbook                  4:3.5.3-3  KDE NG addressbook application
ii  kitchensync                   4:3.5.3-3  Synchronization framework
ii  kmail                         4:3.5.3-3  KDE Email client
ii  knode                         4:3.5.3-3  KDE news reader
ii  knotes                        4:3.5.3-3  KDE sticky notes
ii  korganizer                    4:3.5.3-3  KDE personal organizer
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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 -1208768192 (LWP 28400)]
[KCrash handler]
#6  0x00000000 in ?? ()
#7  0x08060408 in ?? ()
#8  0xbfb3946c in ?? ()
#9  0x0806584e in _IO_stdin_used ()
#10 0xbfb39488 in ?? ()
#11 0x483d9787 in KApplication::setStartupId () from /usr/lib/libkdecore.so.4
#12 0x484673d8 in KUniqueApplication::processDelayed ()
   from /usr/lib/libkdecore.so.4
#13 0x48468c7c in KUniqueApplication::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#14 0x48a61127 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0x48dea16b in QSignal::signal () from /usr/lib/libqt-mt.so.3
#16 0x48a80caa in QSignal::activate () from /usr/lib/libqt-mt.so.3
#17 0x48a8867c in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#18 0x489f908a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#19 0x489faea7 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0x4845532e in KApplication::notify () from /usr/lib/libkdecore.so.4
#21 0x4898c971 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#22 0x489eba87 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#23 0x489a0cbf in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#24 0x48a135dd in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#25 0x48a133fe in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#26 0x489fac23 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#27 0x0805ac3f in ?? ()
#28 0xbfb39bec in ?? ()
#29 0x00000001 in ?? ()
#30 0x00000001 in ?? ()
#31 0x00000000 in ?? ()

Attachment: pgpLuAmgDmfyF.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
I think the key is the message upon crash which can be found at the end of a
strace when executing it from commandline:

read(3, QLayout::addChildLayout: layout already has a parent
"\2\4\0\2\0\0\0\0", 8)          = 8
read(3, "\1\0\0\0", 4)                  = 4
write(2, "ERROR: Communication problem wit"..., 64ERROR: Communication problem
with kontact, it probably crashed.
) = 64
) close(3)                                = 0
) exit_group(255)

The bit about layout already having a parent when QLayout tries to execute the
function addChildLayout.

Any idea why there would already be a parent?  Of course I've made sure that
there is no kontact or zombie processes running when executing kontact.

Attachment: pgpGqwNvOY6hs.pgp
Description: PGP signature


--- End Message ---

Reply to: