Bug 180024 - adept wont start after trying to install update for amarok whicw means cant put any thing new on computer
Summary: adept wont start after trying to install update for amarok whicw means cant p...
Status: RESOLVED DUPLICATE of bug 175540
Alias: None
Product: adept
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Rockai
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-08 14:13 UTC by Keith
Modified: 2009-01-18 20:40 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 Keith 2009-01-08 14:13:29 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Unspecified Other

went to adept third party source tab to put the URL in for the update version of amarok it didn't work so i quit out and tried to restart adept and it gave me a message signal 6 (SIGBRT)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 0xb5ebb6c0 (LWP 5556)]
[New Thread 0xb4765b90 (LWP 5603)]
(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  0xb7f8f430 in __kernel_vsyscall ()
#7  0xb674c880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb674e248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb69706f8 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb696e5d5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb696e612 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb696e6cb in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb7402de5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb74037e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7408db7 in ?? () from /usr/lib/libQtCore.so.4
#16 0xb7408edc in ?? () from /usr/lib/libQtCore.so.4
#17 0xb73fd53f in QObject::event () from /usr/lib/libQtCore.so.4
#18 0xb6ade8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#19 0xb6ae672e in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0xb78bcb2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0xb73ede61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#22 0xb741bd81 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb7418520 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb62346f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb6237da3 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb6237f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb7418478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb6b78ea5 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb73ec52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb73ec6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb73eeda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6ade767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0x080c80c6 in ?? ()
#34 0xb6737685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#35 0x08095ae1 in _start ()
#0  0xb7f8f430 in __kernel_vsyscall ()
Comment 1 Jonathan Thomas 2009-01-18 20:40:20 UTC

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