Ubuntu
adept package

adept_manager crashed

Bug #115290 reported by Jofko
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: adept-manager

I just add repository trough adept, update database and after that I installed software from this repository. Software was installed successfully but after that adept crashed with signal 11(SIGSEGV).

this is error output

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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 -1233832240 (LWP 5605)]
[New Thread -1254786160 (LWP 5899)]
(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)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6813e66 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2 0xb684cc3c in usleep () from /lib/tls/i686/cmov/libc.so.6
#3 0x080e3495 in ?? ()
#4 0x080b35cb in ?? ()
#5 0x080f14d6 in ?? ()
#6 0xb6fe888b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#7 0xb7374ae0 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#8 0xb700881e in QSignal::activate () from /usr/lib/libqt-mt.so.3
#9 0xb7010234 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#10 0xb6f7fa60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#11 0xb6f8188f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#12 0xb7744ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#13 0xb6f121e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#14 0xb6f724ab in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#15 0xb6f26d25 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#16 0xb6f9a136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#17 0xb6f99f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#18 0xb6f81609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#19 0x0807375e in ?? ()
#20 0xb6799ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#21 0x08073471 in ?? ()

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Jofko,

Thanks for taking the time to report this bug. We need a bit more information to diagnose the problem fully. Sorry for all the questions. Which repository was it you added when the crash occurred and does the crash always occur if you remove that repository and add it back? Following on from this, what packages were you installing when the crash occurred?

If you can reproduce the crash it would be very helpful if you could install the package gdb that contains debugging symbols and induce a crash. This creates a crash report in /var/crash that would be very useful in fixing this problem.

Thanks for the feedback.
Rich

Changed in adept:
assignee: nobody → rbirnie
status: Unconfirmed → Needs Info
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Without the debugging symbols there isn't much that can be done with this. Closing report. If the extra information that was asked for can be supplied then this can be reopened and we can track it down.

Changed in adept:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.