Version: (using KDE 4.1.0) Installed from: Debian testing/unstable Packages OS: Linux knotes crashed on close (clicking on "X") - it happened to me several times, but i cannot reproduce it. The only thing i can provide: $ knotes -v Qt: 4.4.0 KDE: 4.1.00 (KDE 4.1.0) KNotes: 3.9 Application: KNotes (knotes), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb5370720 (LWP 3179)] [KCrash handler] #6 ~QObject (this=0x8b65618) at kernel/qobject.cpp:780 #7 0x0805e09f in ~KNotesApp (this=0x8afe8e0) at /usr/include/qt4/QtCore/qalgorithms.h:352 #8 0x0805d03f in ~Application (this=0xbff8cbd0) at /tmp/buildd/kdepim-4.1.0/knotes/application.cpp:34 #9 0x0805ce5c in main (argc=3, argv=0xbff8ccd4) at /tmp/buildd/kdepim-4.1.0/knotes/main.cpp:70 #0 0xb7f73424 in __kernel_vsyscall ()
SVN commit 844844 by guisson: Cast before division otherwise percentage is 0, also fix some other bugs in the percentage patch BUG: 168082 M +54 -12 libktcore/torrent/torrentfiletreemodel.cpp M +1 -0 libktcore/torrent/torrentfiletreemodel.h M +10 -19 plugins/infowidget/iwfiletreemodel.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=844844
Oops, entered the wrong bug number, my appologies, so this bug isn't closed.
*** Bug 174153 has been marked as a duplicate of this bug. ***
I have almost the same trace: # knotes -v Qt: 4.4.3 KDE: 4.1.3 (KDE 4.1.3) KNotes: 3.9 Application: KNotes (knotes), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb8012770 (LWP 8241)] [KCrash handler] #6 0x00000028 in ?? () #7 0x0805c7bf in qDeleteAll<QMap<QString, KNote*>::const_iterator> () at /usr/include/QtCore/qalgorithms.h:346 #8 qDeleteAll<QMap<QString, KNote*> > () at /usr/include/QtCore/qalgorithms.h:354 #9 ~KNotesApp (this=0x8d7fc10) at /usr/src/debug/kdepim-4.1.3/knotes/knotesapp.cpp:231 #10 0x0805bbaf in ~Application (this=0xbf846230) at /usr/src/debug/kdepim-4.1.3/knotes/application.cpp:34 #11 0x0805b9cc in main (argc=1, argv=0xbf846334) at /usr/src/debug/kdepim-4.1.3/knotes/main.cpp:70
Not reproducible with KDE 4.10, this is most likely solved since quite some time. Please feel free to reopen if you can reproduce this with KDE 4.10 or later.