Bug 185156 - KGet crashes sometimes on exiting after startup
Summary: KGet crashes sometimes on exiting after startup
Status: RESOLVED NOT A BUG
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-02-21 20:27 UTC by Alexey Chernov
Modified: 2018-09-19 14:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Chernov 2009-02-21 20:27:19 UTC
Version:            (using KDE 4.2.0)
Compiler:          GCC 4.3.2 Target: x86_64-unknown-linux-gnu Configured with:  ../gcc-4.3.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,fortran,objc,treelang --disable-multilib --enable-c99 --enable-long-long Thread model: posix
OS:                Linux
Installed from:    Compiled From Sources

After exiting KGet to fix situation described in bug #185155 it crashes. Crash report will follow.
Comment 1 Alexey Chernov 2009-02-21 20:29:35 UTC
Oops, unfortunately it wasn't saved, maybe I mixed up buttons. I'll try to get a backtrace as soon as the bug will reproduce (i think in 2-3 days).
Comment 2 Alexey Chernov 2009-02-21 20:31:05 UTC
Well, no, that's it:
Приложение: KGet (kget), сигнал SIGSEGV
Using host libthread_db library "/lib/libthread_db.so.1".
0x00007f1e6c764640 in __nanosleep_nocancel () from /lib/libc.so.6

Thread 1 (Thread 0x7f1e708a8700 (LWP 3661)):
[KCrash Handler]
#5  0x00007f1e6bfe1290 in XSync () from /usr/lib/libX11.so.6
#6  0x00007f1e6bfc039f in XCloseDisplay () from /usr/lib/libX11.so.6
#7  0x00007f1e6d21a233 in qt_cleanup () at kernel/qapplication_x11.cpp:2652
#8  0x00007f1e6d19e654 in ~QApplication (this=0x7fff788e5e80) at kernel/qapplication.cpp:1055
#9  0x00007f1e70377777 in ~KApplication (this=0x7fff788e5e80) at /usr/src/packages/kde4/4.2.0/kdelibs-4.2.0/kdeui/kernel/kapplication.cpp:928
#10 0x00007f1e7037eebe in ~KUniqueApplication (this=0x7fff788e5e80) at /usr/src/packages/kde4/4.2.0/kdelibs-4.2.0/kdeui/kernel/kuniqueapplication.cpp:372
#11 0x000000000045da02 in ~KGetApp (this=0x7fff788e5e80) at /usr/src/packages/kde4/4.2.0/kdenetwork-4.2.0/kget/main.cpp:39
#12 0x000000000045cff7 in main (argc=3, argv=0x7fff788e6428) at /usr/src/packages/kde4/4.2.0/kdenetwork-4.2.0/kget/main.cpp:153

Sorry for extra flood here :)
Comment 3 Lukas Appelhans 2009-03-05 12:57:14 UTC
This seems not like a KDE bug... anyone has a clue where to assign it?

Lukas
Comment 4 Urs Wolfer 2009-06-07 18:07:44 UTC
Please comment on this bug if you can provide a more complete backtrace or a way to reproduce it.
Comment 5 Andrew Crouthamel 2018-09-19 04:36:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-09-19 14:26:19 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.