ksystemlog crashes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ksystemlog (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: ksystemlog
After watching kern-log a while, when i try to change to another log the app just disappear.
if i start it again a 11 sigsev message appears
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1208887616 (LWP 30277)]
(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 0x42f240be in QListViewPrivat
from /usr/lib/
#7 0x42f240ea in QListViewPrivat
from /usr/lib/
#8 0x42f240ea in QListViewPrivat
from /usr/lib/
#9 0x42f240ea in QListViewPrivat
from /usr/lib/
#10 0x42f16b1a in QListViewItem:
#11 0x4cdcab5d in KListViewItem:
#12 0x0806cd2c in QValueList<
#13 0x42f18ae7 in QListView::clear () from /usr/lib/
#14 0x0807727e in QPtrList<
#15 0x0806361c in endl ()
#16 0x08066d95 in endl ()
#17 0x0807ff9f in QValueListPriva
#18 0x08080262 in QValueListPriva
#19 0x42e1a3c9 in QObject:
#20 0x4cdc82fd in KAction::activated () from /usr/lib/
#21 0x4cdc8606 in KAction:
#22 0x4cde4070 in KAction::qt_invoke () from /usr/lib/
#23 0x4cde441e in KToggleAction:
#24 0x42e1a3c9 in QObject:
#25 0x4cdcf4bd in KToolBarButton:
#26 0x4cdcf679 in KToolBarButton:
from /usr/lib/
#27 0x42e54b9d in QWidget::event () from /usr/lib/
#28 0x4ce25add in KToolBarButton:
#29 0x42db0366 in QApplication:
#30 0x42db08f0 in QApplication:
#31 0x4cb40d7d in KApplication:
#32 0x42d416fd in QApplication:
from /usr/lib/
#33 0x42d3cdab in QETWidget:
from /usr/lib/
#34 0x42d3b291 in QApplication:
#35 0x42d54a13 in QEventLoop:
#36 0x42dc8e57 in QEventLoop:
#37 0x42dc8d7a in QEventLoop::exec () from /usr/lib/
#38 0x42daee75 in QApplication::exec () from /usr/lib/
#39 0x0806dc75 in QListViewItem:
#40 0x425d8ea2 in __libc_start_main () from /lib/tls/
#41 0x0805c7f1 in ?? ()
it has happened several times since i've started to use this application (just a few hours ago)
dpkg -l | grep ksystem
ii ksystemlog 0.3.2-0ubuntu3 log viewin g application
this is the sigsev message that appears if i wait after the application dissapears
Este trazado inverso parece inútil.
Probablemente se deba a que sus paquetes están generados de forma que eviten la creación de trazados inversos adecuados, o la pila se ha corrompido seriamente durante el fallo de la aplicación.
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
(sorry but it's in spanish)
This is happening to me too, in latest feisty.
I can reproduce it here every time - all I need to do is change the type of logs being viewed to anything except the kernel log, then change it back to kernel log. If I do this once it tends to happen most of the time. if I change to EVERY different type of view before coming back to the kernel log, it will ALWAYS crash while populating the kernel log view.
Note that there are two different outputs below.
I could paste more, but it seems to crash in a different place every time.
---------- i686/cmov/ libc.so. 6
... blah blah same thread stuff as the original poster...
...
[KCrash handler]
#6 0x0806d935 in ?? ()
#7 0x080875d0 in ?? ()
#8 0x000001a6 in ?? ()
#9 0xbfbf3ef0 in ?? ()
#10 0x08075671 in ?? ()
#11 0xb79ef60e in malloc () from /lib/tls/
#12 0x0806dc59 in ?? ()
#13 0x081621c8 in ?? ()
#14 0xbfc0a3d7 in ?? ()
#15 0x00000000 in ?? ()
--- e::ItemColumnIn fo::~ItemColumn Info () libqt-mt. so.3 :~QListViewItem () from /usr/lib/ libqt-mt. so.3 :~KListViewItem () from /usr/lib/ libkdeui. so.4 libqt-mt. so.3 libqt-mt. so.3
... blah blah same thread stuff...
...
[KCrash handler]
#6 0xb70c735e in QListViewPrivat
from /usr/lib/
#7 0xb70b4634 in QListViewItem:
#8 0xb794323d in KListViewItem:
#9 0x0806d928 in ?? ()
#10 0x0825e9b0 in ?? ()
#11 0xb7483ab0 in ?? () from /usr/lib/
#12 0xbfbab078 in ?? ()
#13 0xb70c4611 in QListView::clear () from /usr/lib/
Backtrace stopped: frame did not save the PC
--------- yet another backtrace ----- libqt-mt. so.3 :operator< () from /usr/lib/ libqt-mt. so.3
... blah blah same thread stuff...
...
[KCrash handler]
#6 0xb7187cb4 in QDate::operator< () from /usr/lib/
#7 0xb72f814c in QDateTime:
#8 0x0806d871 in ?? ()
#9 0x00000004 in ?? ()
#10 0x0841f20c in ?? ()
#11 0x080ac2f4 in ?? ()
#12 0x00000000 in ?? ()