Created attachment 55066 [details] Triggers a segmentation fault inaccessible to DrKonqi Version: unspecified (using KDE 4.4.4) OS: Linux When DrKonqi is unable to retrieve the backtrace, it does not allow the operator to submit the bug report. Instead, it offers the operator a possibility to report the bug herself using the Web interface. However, the hyperlink embedded in the interface cannot be visited easily. Reproducible: Always Steps to Reproduce: 0. Make sure Kaffeine is not running. 1. xdg-open 'KRS–W3.mng' 2. Agree to be contacted by the developers. 3. Press [Next] and [No] until you come to the last screen where you are told DrKonqi cannot report the bug. 4. Follow the hyperlink. Actual Results: 1. Kaffeine, DrKonqi 2. DrKonqi is unable to retrieve the backtrace. 3. "You can report the bug manually at http://.." 4. Nothing happens. Expected Results: 2. DrKonqi should be able to retrieve the backtrace and proceed as usual. 4. The Web browser should display to the KDE bug reporting interface. This bug is actually two: item #2 and item #4. Workaround for #2:: select the Developer Information pane in the first crash notification screen. Workaround for #4:: the context-sensitive menu allows to copy the URL to X Clipboard.
The triggering crash is tracked as Bug 260698.
SVN commit 1207738 by darioandres: - The external links on the Conclusion page should be opened on click CCBUG: 260696 M +3 -0 assistantpage_conclusions.ui WebSVN link: http://websvn.kde.org/?view=rev&revision=1207738
The https://bugs.kde.org link is now clickable (fixed for KDE SC 4.6.0 and 4.5.5) If the backtrace can't be fetched during the report assistant but it can be fetched previously on the main dialog using the Developers Information tab.. then something weird is happening. @George: can you check/analyze it ? Regards
OK, item #4 is solved. Then for #item2 : Steps to Reproduce: 3. Press [Next] and [No] until you come to the last screen where you are told DrKonqi cannot report the bug. Actual Results: 2. DrKonqi is unable to retrieve the backtrace. Expected Results: 2. DrKonqi should be able to retrieve the backtrace and proceed as usual. The real problme is DrKonqi doesn't think this crash is worth for reporting. That decision is not only based upon whether the backtrace is available and its usefulness , but also other information users have provided: whether it is reproducible, whether the user remember what happens, etc. So you problem of "Drkonqi won't let you report the crash" doesn't directly means that DrKonqi fails to get the backtrace. Actually, your workaround itself has proven that DrKonqi has no problem in gettting the backtrace. It is just that drkonqi doesn't think that crash is worth for reporting.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Actually change state as per earlier questions.
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!
It seems that we lost MNG rendering altogether when we switched the engine to VLC.
Comment #9 is unrelated to the state of this bug; changing status.
(In reply to Christoph Feck from comment #10) > Comment #9 is unrelated to the state of this bug; changing status. It is related in the following way: the crash occurred playing MNG but it is not possible any more, so unreproducible until fixed.