Bug 177117 - Adept Crash on Launch
Summary: Adept Crash on Launch
Status: RESOLVED DUPLICATE of bug 175540
Alias: None
Product: adept
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Rockai
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-07 03:56 UTC by Greg Pearson
Modified: 2009-01-18 20:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Pearson 2008-12-07 03:56:10 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

After completing several updates (142) and restarting, Adept starts, accepts password, and then crashes. Here is the detailed crash report:

Application: Adept (adept), signal SIGABRT
(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 0xb5f5b8d0 (LWP 5728)]
[New Thread 0xb480fb90 (LWP 5734)]
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb802e430 in __kernel_vsyscall ()
#7  0xb67ec880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb67ee248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6a106f8 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb6a0e5d5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6a0e612 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb6a0e6cb in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb74a1de5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb74a27e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb74a7db7 in ?? () from /usr/lib/libQtCore.so.4
#16 0xb74a7edc in ?? () from /usr/lib/libQtCore.so.4
#17 0xb749c53f in QObject::event () from /usr/lib/libQtCore.so.4
#18 0xb6b7d8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#19 0xb6b8572e in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0xb795cb2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0xb748ce61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#22 0xb74bad81 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb74b7520 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb62d36f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb62d6da3 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb62d6f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb74b7478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb6c17ea5 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb748b52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb748b6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb748dda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6b7d767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0x080c80c6 in ?? ()
#34 0xb67d7685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#35 0x08095ae1 in _start ()
#0  0xb802e430 in __kernel_vsyscall ()
Comment 1 Peter Rockai 2008-12-07 08:12:23 UTC
Can you please run it from a terminal and paste the terminal output here? Thanks!
Comment 2 Greg Pearson 2008-12-13 16:25:32 UTC
Peter, sorry the problem is resolved. I had a bad repository source. I believe it was related to wicd hardy extras.

Thanks for responding.
Comment 3 Jonathan Thomas 2009-01-18 20:41:45 UTC

*** This bug has been marked as a duplicate of bug 175540 ***