Bug 173474 - Starting kontact during login automatically (kontact did run during the previous session). Second attempt to start works fine.
Summary: Starting kontact during login automatically (kontact did run during the previ...
Status: RESOLVED DUPLICATE of bug 164265
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 173410 173925 174021 174036 174041 174236 174333 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-10-24 23:08 UTC by moosgeist
Modified: 2008-11-05 17:46 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description moosgeist 2008-10-24 23:08:02 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    SuSE RPMs

Login to OpenSuSE 11.0 and KDE 4.1.2
Kontact Version 1.3

Starting kontact during login automatically (kontact did run during the previous session). 

Second attempt to start works fine.

Kontact delivers the following information:
Anwendung: Kontact (kontact), Signal SIGSEGV
[?1034h(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 0x7fc00a03d700 (LWP 5371)]
(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)
[KCrash handler]
#5  0x00007fbfeffe8151 in Akregator::FeedList::findByID ()
   from /usr/lib64/kde4/akregatorpart.so
#6  0x00007fbff000641f in ?? () from /usr/lib64/kde4/akregatorpart.so
#7  0x00007fbff0006762 in ?? () from /usr/lib64/kde4/akregatorpart.so
#8  0x00007fc004748274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#9  0x00007fc00474e59f in ?? () from /usr/lib64/libQtCore.so.4
#10 0x00007fc004742ba3 in QObject::event () from /usr/lib64/libQtCore.so.4
#11 0x00007fc000b6217d in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#12 0x00007fc000b69f2a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#13 0x00007fc00648edcb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#14 0x00007fc004733e71 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#15 0x00007fc0047600c0 in ?? () from /usr/lib64/libQtCore.so.4
#16 0x00007fc00475c43d in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007fbffda2493a in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#18 0x00007fbffda28040 in g_main_context_iterate ()
   from /usr/lib64/libglib-2.0.so.0
#19 0x00007fbffda281dc in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#20 0x00007fc00475c39f in QEventDispatcherGlib::processEvents ()
   from /usr/lib64/libQtCore.so.4
#21 0x00007fc000bf2ccf in ?? () from /usr/lib64/libQtGui.so.4
#22 0x00007fc004732772 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#23 0x00007fc0047328fd in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#24 0x00007fc004734ded in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#25 0x0000000000404a7b in _start ()
#0  0x00007fbffef41230 in nanosleep () from /lib64/libc.so.6
Comment 1 Pino Toscano 2008-10-24 23:50:12 UTC
Related to bug #164265?
Comment 2 Frank Osterfeld 2008-10-27 21:01:02 UTC
Looks strongly like a dupe of 164265 indeed. Please reopen with a full backtrace if not.

*** This bug has been marked as a duplicate of bug 164265 ***
Comment 3 Oliver Putz 2008-10-30 22:10:01 UTC
*** Bug 173410 has been marked as a duplicate of this bug. ***
Comment 4 Oliver Putz 2008-10-30 22:16:44 UTC
*** Bug 173925 has been marked as a duplicate of this bug. ***
Comment 5 Oliver Putz 2008-11-02 11:15:34 UTC
*** Bug 174036 has been marked as a duplicate of this bug. ***
Comment 6 Oliver Putz 2008-11-02 11:23:12 UTC
*** Bug 174021 has been marked as a duplicate of this bug. ***
Comment 7 Oliver Putz 2008-11-02 11:53:24 UTC
*** Bug 174041 has been marked as a duplicate of this bug. ***
Comment 8 Thomas McGuire 2008-11-05 17:45:53 UTC
*** Bug 174333 has been marked as a duplicate of this bug. ***
Comment 9 Thomas McGuire 2008-11-05 17:46:02 UTC
*** Bug 174236 has been marked as a duplicate of this bug. ***