| Summary: | Kget crashes | ||
|---|---|---|---|
| Product: | [Applications] kget | Reporter: | Richard Llom <richard.llom> |
| Component: | general | Assignee: | KGet authors <kget> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | alex.zauzolkov, angelbravo, cyrond, d.tullemans, feichong.zgbl, fhj52.info, f_fouad, ghzooooon, guvenbaykan2013, jdogzilla, mcut17198, nicolas.fella, rabota.pmr, savemore99.sm, shekeinespere, wbauer1 |
| Priority: | VHI | Keywords: | drkonqi |
| Version: | 18.08 | ||
| Target Milestone: | --- | ||
| Platform: | Chakra | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Richard Llom
2014-03-15 18:37:57 UTC
*** Bug 337009 has been marked as a duplicate of this bug. *** *** Bug 337220 has been marked as a duplicate of this bug. *** *** Bug 343414 has been marked as a duplicate of this bug. *** *** Bug 352556 has been marked as a duplicate of this bug. *** *** Bug 376947 has been marked as a duplicate of this bug. *** *** Bug 377288 has been marked as a duplicate of this bug. *** *** Bug 383085 has been marked as a duplicate of this bug. *** *** Bug 383085 has been marked as a duplicate of this bug. *** *** Bug 383584 has been marked as a duplicate of this bug. *** *** Bug 386413 has been marked as a duplicate of this bug. *** *** Bug 388189 has been marked as a duplicate of this bug. *** *** Bug 401640 has been marked as a duplicate of this bug. *** I'm not able to reproduce this crash, even though it apparently still can happen in the latest version. Can somebody affected please try to rename the file ~/.local/share/kget/transfers.kgt and report back if it helps? (in earlier versions it would be ~/.kde(4)/share/apps/kget/transfers.kgt) If yes, please attach the problematic file. Thanks. *** Bug 401799 has been marked as a duplicate of this bug. *** I noticed something today, when I started KGet and got the KDE crash report dialog I clicked restart (to restart kget) Telegram (which was running minimized in system tray) windows appeared. I repeated that several times with the same result. after that I closed Telegram (eight click tray icon -> quit) and tried to start kget and it started normally. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! Sorry, it wasn't my intention to have this auto-closed... :-/ I still cannot reproduce it though. Regarding comment#13: the crash happens when kget creates the entries to hide columns in the list header's right-click context menu. So transfers.kgt shouldn't be relevant here. It might be somehow related to ~/.config/kgetrc (or ~/.kde(4)/share/config/kgetrc) though, so it might be worth a try to delete/rename that one. Judging from the backtrace, this crash must have been introduced by https://cgit.kde.org/kget.git/commit/?h=KDE/4.12&id=c6531c0334a7cab9d37cc921fb5792b4727b0611 (and it seems to fit that this originally has been reported against 4.12.2, which is the first version that includes that change). Calling populateHeaderActions() more than once (which happens since that change) is not really great, as it allocates the actions on the heap and never frees them... (but that shouldn't cause a crash) But just reverting that is probably not a good idea either, as it was a fix for another crash (bug#329957). I'll have to think more about it, not being able to reproduce makes it hard to investigate what really goes wrong though... Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! *** Bug 463476 has been marked as a duplicate of this bug. *** *** Bug 457873 has been marked as a duplicate of this bug. *** *** Bug 463909 has been marked as a duplicate of this bug. *** |