| Summary: | KGet Crashes after Altering Settings (& settings not applied too well either) | ||
|---|---|---|---|
| Product: | [Applications] kget | Reporter: | Frank James <ubuntu> |
| Component: | general | Assignee: | KGet authors <kget> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Frank James
2008-11-23 16:50:30 UTC
Do you have a backtrace? Can you please tell which settings you have exactly changed? Is there a way to reproduce it? (In reply to comment #1) > Do you have a backtrace? Can you please tell which settings you have exactly > changed? Is there a way to reproduce it? > Forgive my ignorance: How do I do a backtrace? Will be happy to supply any info. First couple of times it has crashed was changing the download limits, though as I mentioned, seems like the changes were recorded (just not actually acted upon, hehe). When I go into Settings and just cancel my way out, it does not crash. Oh, I see how you get a backtrace... as I just tried changing settings without having running downloads - had a suspicion that it did not crash if changing settings with no active downloads - but it indeed crashed and here is the info: Application: KGet (kget), signal SIGSEGV (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 0x7f5d51ef66f0 (LWP 29804)] (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) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #5 0x0000000100000001 in ?? () #6 0x00007f5d506cf724 in QObject::disconnect () from /usr/lib/libQtCore.so.4 #7 0x00007f5d50a9a406 in KJobTrackerInterface::unregisterJob () from /usr/lib/libkdecore.so.5 #8 0x00007f5d519327c1 in KWidgetJobTracker::unregisterJob () from /usr/lib/libkdeui.so.5 #9 0x00007f5d51501aa1 in ?? () from /usr/lib/libkgetcore.so.4 #10 0x000000000044ea78 in _start () #0 0x00007f5d4ec3e5f0 in nanosleep () from /lib/libc.so.6 Hope that makes some sense to someone! Cheers. *** This bug has been marked as a duplicate of bug 168006 *** |