/lib/tls/i686/cmov/libthread_db.so.1

Bug #189965 reported by lolo80
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235740992 (LWP 13494)]
(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 0xffffe410 in __kernel_vsyscall ()
#7 0xb65dc875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb65de201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb67e86e0 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb67e5f65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb67e5fa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb67e60ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x0812b916 in ?? ()
#14 0x0812be8a in ?? ()
#15 0x0812bee8 in ?? ()
#16 0x0812c735 in ?? ()
#17 0x0812a22d in ?? ()
#18 0x08114379 in ?? ()
#19 0x080951ed in ?? ()
#20 0x0807378d in ?? ()
#21 0x0807408e in ?? ()
#22 0xb6e2c893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb71b88ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6e4c842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6e54258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6dc3af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6dc591f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7589cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6d56209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6db653b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6d6ad49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6dde1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6dddfde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6dc5699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x0806f75e in ?? ()
#36 0xb65c8050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x0806f401 in ?? ()

Revision history for this message
lolo80 (laurenthamadi) wrote :

merci de votre aide

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please attach the crash file in /var/crash? This is not a bug in update-manager as update-manager does not link against libqt :)

Cheers,
 Michael

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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