Hi I was pasting some details in a PM to Remmy when quassel segfaulted I reconnected and pasted a few more lines. It seemed as if the pasting should have finished but some moments later it segfaulted again. I installed debug packages and generated a backtrace.
Created attachment 1809 [details] backtrace
CC: (none) => lmenut, remcoAssignee: bugsquad => balcaen.john
Better to have the backtrace in the bugreport instead of attachment ( help for research in bugzilla ) Thread 1 (Thread 0xb323c6d0 (LWP 1999)): [KCrash Handler] #7 operator!= (this=0x9db9f7c, key=...) at ../../src/corelib/thread/qbasicatomic.h:75 #8 detach (this=0x9db9f7c, key=...) at ../../src/corelib/tools/qhash.h:299 #9 find (this=0x9db9f7c, key=...) at ../../src/corelib/tools/qhash.h:865 #10 QNetworkAccessCache::releaseEntry (this=0x9db9f7c, key=...) at access/qnetworkaccesscache.cpp:325 #11 0xb69825e6 in QNetworkAccessFtpBackend::disconnectFromFtp (this=0x9c9b580) at access/qnetworkaccessftpbackend.cpp:213 #12 0xb698268d in QNetworkAccessFtpBackend::~QNetworkAccessFtpBackend (this=0x9c9b580, __in_chrg=<value optimized out>) at access/qnetworkaccessftpbackend.cpp:110 #13 0xb6982702 in QNetworkAccessFtpBackend::~QNetworkAccessFtpBackend (this=0x9c9b580, __in_chrg=<value optimized out>) at access/qnetworkaccessftpbackend.cpp:111 #14 0xb767f233 in qDeleteInEventHandler (o=0x9c9b580) at kernel/qobject.cpp:3986 #15 0xb7681b78 in QObject::event (this=0x9c9b580, e=0x9d92398) at kernel/qobject.cpp:1200 #16 0xb6b7f7a4 in QApplicationPrivate::notify_helper (this=0x91f9638, receiver=0x9c9b580, e=0x9d92398) at kernel/qapplication.cpp:4481 #17 0xb6b84787 in QApplication::notify (this=0xbfa1fef0, receiver=0x9c9b580, e=0x9d92398) at kernel/qapplication.cpp:3881 #18 0xb4cbb801 in KApplication::notify (this=0xbfa1fef0, receiver=0x9c9b580, event=0x9d92398) at /usr/src/debug/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:311 #19 0xb766bf0e in QCoreApplication::notifyInternal (this=0xbfa1fef0, receiver=0x9c9b580, event=0x9d92398) at kernel/qcoreapplication.cpp:787 #20 0xb766fcac in sendEvent (receiver=0x0, event_type=0, data=0x91dde98) at kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x91dde98) at kernel/qcoreapplication.cpp:1428 #22 0xb766fdfc in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321 #23 0xb769ac64 in sendPostedEvents (s=0x91fbc90) at kernel/qcoreapplication.h:220 #24 postEventSourceDispatch (s=0x91fbc90) at kernel/qeventdispatcher_glib.cpp:277 #25 0xb459d4d9 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #26 0xb459dce0 in ?? () from /lib/libglib-2.0.so.0 #27 0xb459df9a in g_main_context_iteration () from /lib/libglib-2.0.so.0 #28 0xb769adeb in QEventDispatcherGlib::processEvents (this=0x91ddc00, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #29 0xb6c372fa in QGuiEventDispatcherGlib::processEvents (this=0x91ddc00, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #30 0xb766b11d in QEventLoop::processEvents (this=0xbfa1fe54, flags=...) at kernel/qeventloop.cpp:149 #31 0xb766b399 in QEventLoop::exec (this=0xbfa1fe54, flags=...) at kernel/qeventloop.cpp:201 #32 0xb766fed0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #33 0xb6b7d524 in QApplication::exec () at kernel/qapplication.cpp:3755 #34 0x0807674d in main (argc=1, argv=0xbfa201f4) at /usr/src/debug/quassel-0.7.2/src/common/main.cpp:139
CC: (none) => nicolas.lecureuil
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX