Recent changes to bugs

crash

linedubeth — Fri, 03 Jul 2009 21:14:59 -0000

Hello,

i 'm computer user and i have some crash with ubuntu

compile errors on newer G++

Anonymous — Fri, 27 Jun 2008 02:08:43 -0000

Copied from an old debian bug report. The issue still exists. Link: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355986

In ./src/nntpthreadsocket.h:
"char * NntpThreadSocket::m_findEndLine( char * start, char * end );"

The "NntpThreadSocket::" part needs to go. Like this:
"char * m_findEndLine( char * start, char * end );"

The same issue in ./src/yydecoder.h:
"inline void yyDecoder::charCRC(const unsigned char *c);"
needs to change to:
"inline void charCRC(const unsigned char *c);"

This is confirmed with 2.5.0. This isn't your fault, GCC went and changed something (other packages have had this issue as well, with the same fix)

This is with g++ (GCC) 4.2.3

repeated crashes with SIGSEGV and SIGABRT errors

Anonymous — Mon, 24 Dec 2007 15:52:44 -0000

When downloading from an NZB file a posting of several GB, the app has crashed a dozen times or more before even reaching 50% of the download. Usually the KDE crash handler reports a SIGSEGV code, but the most recent was SIGABRT. With the former, no backtrace was available. For the latter, the backtrace is as follows:
(no debugging symbols found)
Using host libthread_db library "/lib64/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)
[Thread debugging using libthread_db enabled]
[New Thread 46912496409968 (LWP 17860)]
[New Thread 1189128528 (LWP 17875)]
[New Thread 1178638672 (LWP 17874)]
[New Thread 1168148816 (LWP 17873)]
[New Thread 1157658960 (LWP 17872)]
[New Thread 1147169104 (LWP 17871)]
[New Thread 1136679248 (LWP 17870)]
[New Thread 1126189392 (LWP 17869)]
[New Thread 1115699536 (LWP 17868)]
[New Thread 1105209680 (LWP 17867)]
[New Thread 1094719824 (LWP 17866)]
(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)
0x00000034d4ee0e4e in __lll_lock_wait_private () from /lib64/libc.so.6
#0 0x00000034d4ee0e4e in __lll_lock_wait_private () from /lib64/libc.so.6
#1 0x00000034d4e770f7 in _L_lock_14679 () from /lib64/libc.so.6
#2 0x00000034d4e75f21 in free () from /lib64/libc.so.6
#3 0x00000034d6e4abe0 in QWidget::setUpdatesEnabled ()
from /usr/lib64/libX11.so.6
#4 0x00000034d6e4b0b8 in _XReply () from /usr/lib64/libX11.so.6
#5 0x00000034d6e40d34 in XTranslateCoordinates () from /usr/lib64/libX11.so.6
#6 0x00000034dc0cc66e in QWidget::mapFromGlobal ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#7 0x00000034dc298f0c in QTipManager::eventFilter ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#8 0x00000034dc10296a in QApplication::internalNotify ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#9 0x00000034dc103e50 in QApplication::notify ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#10 0x0000003b057c3678 in KApplication::notify ()
from /usr/lib64/libkdecore.so.4
#11 0x00000034dc0a1b5a in QETWidget::translateMouseEvent ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#12 0x00000034dc0a0f49 in QApplication::x11ProcessEvent ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#13 0x00000034dc0b0ea4 in QEventLoop::processEvents ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#14 0x00000034dc11a151 in QEventLoop::enterLoop ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#15 0x00000034dc11a032 in QEventLoop::exec ()
from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#16 0x000000000041fada in QWidget::setUpdatesEnabled ()
#17 0x00000034d4e1e074 in __libc_start_main () from /lib64/libc.so.6
#18 0x000000000041f7f9 in QWidget::setUpdatesEnabled ()
#19 0x00007fffb2b68d28 in ?? ()
#20 0x0000000000000000 in ?? ()

barrybham@gmail.com

download speed reported by Klibido is way too high

Anonymous — Sat, 22 Dec 2007 01:30:35 -0000

for example, on a download with a (verified) 10 mbit speed cap, klibido will report download speeds to vary (even when the actual speed is stable/constant) anywhere between 1700 and 10000+ KB/s, while averaging about 2000-2500 KB/s.
Screenshot available for your viewing pleasure at http://www.spunge.org/~yamal/klibido.jpg

More information concerning this issue is available at https://bugs.edge.launchpad.net/ubuntu/+source/klibido/+bug/55080

Thank you.

header entries in .xsession-errors

Anonymous — Sun, 11 Nov 2007 20:49:08 -0000

I had an issue with my /home partition filling up. I noticed I had a 24Gb .xsession-errors file.
I just found part of the problem for my .xsession-errors file size.
here is the size before I ran klibido
pbc@paulandcilla:~$ ls -laSr .xse*
-rw------- 1 pbc pbc 55452 2007-11-11 08:10 .xsession-errors.1

and after I ran klibido and just clicked on one newsgroup:
pbc@paulandcilla:~$ ls -laSr .xse*
-rw------- 1 pbc pbc 97919 2007-11-11 08:12 .xsession-errors.1

and klibido, just selecting ONE newsgroup added 1108 lines of this:
Header date: Tue Oct 16 12:56:20 2007
Header date: Tue Oct 16 12:56:28 2007
Header date: Tue Oct 16 12:57:06 2007
Header date: Tue Oct 16 12:57:43 2007
Header date: Tue Oct 16 12:57:50 2007

If it does that for every newsgroup, every time I run it... can those header entries go somehwere other than .xsession-errors??

Crash during download - anotherone

Anonymous — Sun, 11 Nov 2007 11:14:43 -0000

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1239877936 (LWP 21797)]
[New Thread -1319142512 (LWP 31553)]
[New Thread -1310749808 (LWP 21809)]
[New Thread -1302357104 (LWP 21808)]
[New Thread -1293964400 (LWP 21807)]
[New Thread -1285571696 (LWP 21806)]
[New Thread -1277178992 (LWP 21805)]
[New Thread -1268786288 (LWP 21804)]
[New Thread -1260393584 (LWP 21803)]
[New Thread -1252000880 (LWP 21802)]
[New Thread -1242510448 (LWP 21801)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb625b4ce in __lll_mutex_lock_wait () from /lib/libc.so.6
#2 0xb61fb98f in _L_lock_4996 () from /lib/libc.so.6
#3 0xb61f8e1e in *__GI___libc_free (mem=0x8418448) at malloc.c:3620
#4 0xb639a519 in operator delete ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6
#5 0xb639a565 in operator delete[] ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6
#6 0xb6fd7732 in ~QStringData (this=0x8418458) at tools/qstring.h:363
#7 0xb6fce2c5 in QStringData::deleteSelf (this=0x8418458)
at tools/qstring.cpp:1558
#8 0xb6ca66f6 in __tcf_2 () at kernel/qrichtext.cpp:7376
#9 0xb61be90c in *__GI_exit (status=1) at exit.c:75
#10 0xb6605361 in _IceDefaultIOErrorHandler (iceConn=0x8170a50) at error.c:621
#11 0xb747d576 in KApplication::iceIOErrorHandler (this=0xbfe0fff4,
conn=0x8170a50) at kapplication.cpp:756
#12 0xb747d5b5 in kde_ice_ioerrorhandler (conn=0x8170a50)
at kapplication.cpp:193
#13 0xb660cc76 in _IceWrite (iceConn=0x8170a50, nbytes=24, ptr=0x815b9e0 "")
at misc.c:435
#14 0xb660ccac in IceFlush (iceConn=0x8170a50) at misc.c:82
#15 0xb6605b84 in _IceErrorBadMajor (iceConn=0x8170a50, offendingMajor=65,
offendingMinor=25, severity=0) at error.c:363
#16 0xb661185e in IceProcessMessages (iceConn=0x8170a50, replyWait=0x0,
replyReadyRet=0x0) at process.c:321
#17 0xb6b4d238 in QSmSocketReceiver::socketActivated (this=0x8170dd0)
at kernel/qapplication_x11.cpp:6236
#18 0xb6b4d293 in QSmSocketReceiver::qt_invoke (this=0x8170dd0, _id=2,
_o=0xbfe0fa18) at .moc/debug-shared-mt/qapplication_x11.moc:83
#19 0xb6c4aedf in QObject::activate_signal (this=0x8170c30, clist=0x815c008,
o=0xbfe0fa18) at kernel/qobject.cpp:2356
#20 0xb6c4ba5e in QObject::activate_signal (this=0x8170c30, signal=2, param=4)
at kernel/qobject.cpp:2449
#21 0xb704a8bf in QSocketNotifier::activated (this=0x8170c30, t0=4)
at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#22 0xb6c723ce in QSocketNotifier::event (this=0x8170c30, e=0xbfe0fd6c)
at kernel/qsocketnotifier.cpp:258
#23 0xb6bd68ff in QApplication::internalNotify (this=0xbfe0fff4,
receiver=0x8170c30, e=0xbfe0fd6c) at kernel/qapplication.cpp:2635
#24 0xb6bd8877 in QApplication::notify (this=0xbfe0fff4, receiver=0x8170c30,
e=0xbfe0fd6c) at kernel/qapplication.cpp:2358
#25 0xb747e8f1 in KApplication::notify (this=0xbfe0fff4, receiver=0x8170c30,
event=0xbfe0fd6c) at kapplication.cpp:550
#26 0xb7ebf6a1 in QApplication::sendEvent (receiver=0x8170c30,
event=0xbfe0fd6c) at /usr/qt/3/include/qapplication.h:496
#27 0xb6bc6fde in QEventLoop::activateSocketNotifiers (this=0x815bde8)
at kernel/qeventloop_unix.cpp:578
#28 0xb6b76d1c in QEventLoop::processEvents (this=0x815bde8, flags=4)
at kernel/qeventloop_x11.cpp:383
#29 0xb6bf471d in QEventLoop::enterLoop (this=0x815bde8)
at kernel/qeventloop.cpp:198
#30 0xb6bf453e in QEventLoop::exec (this=0x815bde8)
at kernel/qeventloop.cpp:145
#31 0xb6bd85c3 in QApplication::exec (this=0xbfe0fff4)
at kernel/qapplication.cpp:2758
#32 0x0806824d in main (argc=135575920, argv=0x81866d0) at main.cpp:87

the good thing: klibido remembers what was downloaded and starts where it stopped.
happens only with lots of data. (multiples of gbyte...)

Crash after trying to resume download

Gary Whetstone — Thu, 27 Sep 2007 05:14:18 -0000

My system crashed as part of an unexpected, unrelated shutdown of ksmserver, and as such klibido did not go through whatever usual shutdown procedure it has. When I brought the system back up and started klibido, I clicked yes to reload what was left to download, and it crashed. After I ran klibido a second time and loaded the files to download it did not crash.

(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235949888 (LWP 8317)]
[New Thread -1239581808 (LWP 8318)]
(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 0xb68e81fb in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb695bb3e in ?? () from /usr/lib/libX11.so.6
#3 0x00000003 in ?? ()
#4 0xbfbea1f0 in ?? ()
#5 0x00000020 in ?? ()
#6 0xb695b64f in _X11TransWrite () from /usr/lib/libX11.so.6
#7 0xb695b61f in _X11TransRead () from /usr/lib/libX11.so.6
#8 0xb6952bc9 in _XRead () from /usr/lib/libX11.so.6
#9 0xb6953654 in _XReply () from /usr/lib/libX11.so.6
#10 0xb6947570 in XQueryPointer () from /usr/lib/libX11.so.6
#11 0xb6e08f40 in QCursor::pos () from /usr/lib/libqt-mt.so.3
#12 0xb7020d57 in QTabBar::paint () from /usr/lib/libqt-mt.so.3
#13 0xb7020510 in QTabBar::paintEvent () from /usr/lib/libqt-mt.so.3
#14 0xb6f0ba79 in QWidget::event () from /usr/lib/libqt-mt.so.3
#15 0xb701ee39 in QTabBar::event () from /usr/lib/libqt-mt.so.3
#16 0xb6e6baf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#17 0xb6e6e4ba in QApplication::notify () from /usr/lib/libqt-mt.so.3
#18 0xb7632242 in KApplication::notify () from /usr/lib/libkdecore.so.4
#19 0xb6dfe209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#20 0xb6e384a5 in QWidget::repaint () from /usr/lib/libqt-mt.so.3
#21 0xb6f12955 in QWidget::repaint () from /usr/lib/libqt-mt.so.3
#22 0xb6f10a1c in QWidget::repaint () from /usr/lib/libqt-mt.so.3
#23 0xb701dd38 in QTab::setText () from /usr/lib/libqt-mt.so.3
#24 0xb75ab691 in KAcceleratorManagerPrivate::calculateAccelerators ()
from /usr/lib/libkdecore.so.4
#25 0xb75dd8e9 in KAcceleratorManagerPrivate::manage ()
from /usr/lib/libkdecore.so.4
#26 0xb75dd9be in KAcceleratorManager::manage () from /usr/lib/libkdecore.so.4
#27 0xb75dd9f5 in KAcceleratorManager::manage () from /usr/lib/libkdecore.so.4
#28 0xb75dda33 in KCheckAccelerators::checkAccelerators ()
from /usr/lib/libkdecore.so.4
#29 0xb75de00f in KCheckAccelerators::autoCheckSlot ()
from /usr/lib/libkdecore.so.4
#30 0xb75de0b8 in KCheckAccelerators::qt_invoke ()
from /usr/lib/libkdecore.so.4
#31 0xb6ed4893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#32 0xb6ed5338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#33 0xb72629ae in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#34 0xb6efc5ba in QTimer::event () from /usr/lib/libqt-mt.so.3
#35 0xb6e6baf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#36 0xb6e6d91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#37 0xb7632242 in KApplication::notify () from /usr/lib/libkdecore.so.4
#38 0xb6dfe209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#39 0xb6e5e53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#40 0xb6e12d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#41 0xb6e861ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#42 0xb6e85fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#43 0xb6e6d699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#44 0x08063e97 in ?? ()
#45 0xb6595050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#46 0x08063b71 in ?? ()

Cancel item in queue caused crash

Gary Whetstone — Thu, 13 Sep 2007 13:29:58 -0000

I was cancelling an item that was at the top of the queue yet for some reason was not downloading. It was supposed to be fetching headers for a group. I tried to cancel and was then going to hit update again to add it anew, but it crashed.

Crash when clicking group properties

Gary Whetstone — Wed, 12 Sep 2007 12:48:54 -0000

In 0.2.5, I clicked Subscribe to newsgroups. I was subscribing to a few newsgroups, and happened to try the group properties menu item, since I wasn't quite sure what it did (i usually use nzbs) and it crashed. I'm not sure what if any subscribed group was highlighted at the time.

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1235499328 (LWP 6497)]
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x080794ae in ?? ()
#7 0x0807df58 in ?? ()
#8 0xb6f42893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9 0xb6f43338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb7867a79 in KAction::activated () from /usr/lib/libkdeui.so.4
#11 0xb78a5202 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#12 0xb796d3fd in KAction::slotPopupActivated () from /usr/lib/libkdeui.so.4
#13 0xb796d6c1 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#14 0xb6f42893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb72ce8e8 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#16 0xb6f62842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#17 0xb7068fd3 in QPopupMenu::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#18 0xb786e8ce in KPopupMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.4
#19 0xb6f79681 in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb6ed9af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb6edbcae in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb76a0242 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb6e6c27d in QApplication::sendSpontaneousEvent ()
from /usr/lib/libqt-mt.so.3
#24 0xb6e6abbf in QETWidget::translateMouseEvent ()
from /usr/lib/libqt-mt.so.3
#25 0xb6e68fcc in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#26 0xb6e801a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#27 0xb6ef41ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#28 0xb6ef3fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#29 0xb6edb699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#30 0x08063e97 in ?? ()
#31 0xb6603050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#32 0x08063b71 in ?? ()

Error writing to disk, disk full

Anonymous — Mon, 13 Aug 2007 19:36:07 -0000

I ran into the following error which would pop up right after clicking on Oke when I wnated to download some files from a binary newsgroup.

At first I thought the nzb file was corrupt, but Pan downloaded the files without a hitch.

Annoyed as I was at having to do without my favorite downloader I did some searching (even tried stracing klibido) but to no availl.

Then I treid reinstalling it from the debian sources.
No go there either.

What I noticed what that after reinstalling, klibido would still say that I had files in the queue (and the nasty error on writing, disk fll error)??

So I tried deleting the klibidorc file and this fixed the problem in one go.

So for those of you who have ran into this problem, this will atleast get you on your way again.

But I suspect the problem to return at which time I'll add onto this bug report with more details.