Bug 187674 - i can't open adept installer because it crashes and causes the signal 6 SIGABRT
Summary: i can't open adept installer because it crashes and causes the signal 6 SIGABRT
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-03-20 04:17 UTC by vedo1117
Modified: 2009-03-31 04:23 UTC (History)
3 users (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 vedo1117 2009-03-20 04:17:17 UTC
Version:            (using KDE 4.1.3)
OS:                Linux

hey, when I open adept it crashes and I get this message:

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 0x7f58ee9f86f0 (LWP 6052)]
[New Thread 0x426d5950 (LWP 6060)]
(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]
#5  0x00007f58eb5e6015 in raise () from /lib/libc.so.6
#6  0x00007f58eb5e7b83 in abort () from /lib/libc.so.6
#7  0x00007f58ebe8af94 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#8  0x00007f58ebe89396 in ?? () from /usr/lib/libstdc++.so.6
#9  0x00007f58ebe893c3 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0x00007f58ebe89445 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#11 0x00007f58ecd768fd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#12 0x00007f58ecd78cbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#13 0x000000000048f40f in ?? ()
#14 0x00007f58eb5d1466 in __libc_start_main () from /lib/libc.so.6
#15 0x0000000000458059 in _start ()
#0  0x00007f58eb65b6e1 in nanosleep () from /lib/libc.so.6

I don't know what to do. can you help me please?
Comment 1 Dario Andres 2009-03-20 12:39:38 UTC
This is probably bug 175540 (Adept crashes with SIGABRT with invalid sources.list.) . What happens if you want to use apt-get on a shell ? May be you need to remove some invalid repo from your sources.list.
Thanks for reporting
Comment 2 Jonathan Thomas 2009-03-31 04:23:21 UTC

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