Bug 127110 - If Kontact is started, starting it again causes it to die
Summary: If Kontact is started, starting it again causes it to die
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 1.2
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 120373 129070 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-05-10 23:49 UTC by Jeff Mitchell
Modified: 2007-08-02 22:02 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
besaid backtrace (3.13 KB, text/plain)
2007-08-02 22:02 UTC, Elmar Stellnberger (AT/K)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Mitchell 2006-05-10 23:49:17 UTC
Version:           1.2 (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
OS:                Linux

I don't know if this is a crash or something else.  If Kontact has been started, and I press Alt+F2, type kontact, and hit Enter to start it (forgetting I already have it open), the existing Kontact instance closes.  Usual behavior for apps is to bring the existing instance to the front or maximize it.
Comment 1 Thiago Macieira 2006-05-17 17:59:01 UTC
It crashes here.

Backtrace:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1246877472 (LWP 20570)]
[New Thread -1286308944 (LWP 20586)]
[New Thread -1277916240 (LWP 20585)]
[New Thread -1269523536 (LWP 20584)]
[New Thread -1261130832 (LWP 20583)]
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb6404e91 in raise () from /lib/tls/libc.so.6
#8  0xb640682b in abort () from /lib/tls/libc.so.6
#9  0xb63fdee5 in __assert_fail () from /lib/tls/libc.so.6
#10 0xb71780d3 in KCmdLineArgs::isSet (this=0x1, _opt=0x806795c "module")
    at /home/tjmaciei/src/kde3/KDE/kdelibs/kdecore/kcmdlineargs.cpp:1191
#11 0x08058f41 in KontactApp::newInstance ()
#12 0xb7168a61 in KUniqueApplication::processDelayed (this=0xbfcca890)
    at /home/tjmaciei/src/kde3/KDE/kdelibs/kdecore/kuniqueapplication.cpp:444
#13 0xb7168bd8 in KUniqueApplication::qt_invoke (this=0xbfcca890, _id=18, 
    _o=0x0) at ./kdecore/kuniqueapplication.moc:86
#14 0xb6929313 in QObject::activate_signal (this=0x8142f08, clist=0x8d19888, 
    o=0xbfcca288)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qobject.cpp:2356
#15 0xb6d40f99 in QSignal::signal (this=0x8142f08, t0=@0x8142f30)
    at /home/tjmaciei/src/kde3/qt-copy/src/.moc/debug-shared-mt/moc_qsignal.cpp:100
#16 0xb694bf81 in QSignal::activate (this=0x8142f08)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qsignal.cpp:212
#17 0xb695638a in QSingleShotTimer::event (this=0x8142ee0)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qtimer.cpp:286
#18 0xb68b102b in QApplication::internalNotify (this=0xbfcca890, 
    receiver=0x8142ee0, e=0xbfcca5b8)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qapplication.cpp:2635
#19 0xb68b1281 in QApplication::notify (this=0xbfcca890, receiver=0x8142ee0, 
    e=0xbfcca5b8)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qapplication.cpp:2358
#20 0xb70bfdc9 in KApplication::notify (this=0xbfcca890, receiver=0x8142ee0, 
    event=0xbfcca5b8)
    at /home/tjmaciei/src/kde3/KDE/kdelibs/kdecore/kapplication.cpp:550
#21 0xb7b7ca6e in QApplication::sendEvent (receiver=0x6, event=0xbfcca5b8)
    at /home/tjmaciei/src/kde3/qt-copy/include/qapplication.h:496
#22 0xb68a008d in QEventLoop::activateTimers (this=0x80c08d0)
    at kernel/qeventloop_unix.cpp:556
#23 0xb684b60c in QEventLoop::processEvents (this=0x80c08d0, flags=4)
    at kernel/qeventloop_x11.cpp:389
#24 0xb68cd26a in QEventLoop::enterLoop (this=0x80c08d0)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qeventloop.cpp:198
#25 0xb68cd193 in QEventLoop::exec (this=0x80c08d0)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qeventloop.cpp:145
#26 0xb68af99d in QApplication::exec (this=0xbfcca890)
    at /home/tjmaciei/src/kde3/qt-copy/src/kernel/qapplication.cpp:2758
#27 0x080596f6 in main ()
Comment 2 Thiago Macieira 2006-05-18 09:34:29 UTC
Actually, the bug must be in KontactApplication::newInstance(), since KUniqueApplication is working fine in many other applications.
Comment 3 Albert Astals Cid 2006-10-28 22:58:49 UTC
*** Bug 120373 has been marked as a duplicate of this bug. ***
Comment 4 Bram Schoenmakers 2006-12-23 20:27:08 UTC
*** Bug 129070 has been marked as a duplicate of this bug. ***
Comment 5 Stanley Jones 2007-01-08 12:06:15 UTC
same happens to me if first instance started at kde logon
steps to reproduce :
1) logon to kde with kontact autostart
2) start new instance
3) I will get message "Kontact already started on another desktop... would you like to start new instance ?" Pressing "yes" leads both instances to exit

I will attach log file produced by strace.
log "kont1" is for instance, which is startede at kde startup, and kont2 is for second one.
Comment 6 Stanley Jones 2007-01-08 12:10:14 UTC
Here are logfiles. I was unable to upload them to bugzilla because of size.

http://tornadodrive.com/download.php/1772/kont1.html
http://tornadodrive.com/download.php/1773/kont2.html
Note : wait for a 15 seconds and press "download" button to download it.
Comment 7 Tobias Koenig 2007-02-12 17:17:48 UTC
Hi,

I can't reproduce it here on a vanilla KDE 3.5.6 installation.
Please test with current version and report again.

Ciao,
Tobias
Comment 8 Nicolas L. 2007-02-12 20:14:22 UTC
yes, just tryed and it seems fixed. i will tell if it come back on the future

thanks
Comment 9 Elmar Stellnberger (AT/K) 2007-08-02 22:01:46 UTC
happened again with kontact 1.2.5.
previously loaded in the background to enable quicker startup (sometimes has taken up to 15s to start):
kstart --skiptaskbar --iconify -windowclass kontact kontact
First relaunch of Kontact has worked fine.
Then on another relaunch a crash occured:
drkonqi -display :0.0 --appname kontact --signal 11 --pid xxxxx --appversion 1.2.5 --programname Kontact
backtrace: see attachement

Comment 10 Elmar Stellnberger (AT/K) 2007-08-02 22:02:27 UTC
Created attachment 21320 [details]
besaid backtrace