| Summary: | Konqueror crashes when using Fish protocol | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Dave Burkholder <dave> |
| Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | dave, frank78ac |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Dave Burkholder
2010-03-13 16:43:32 UTC
Thanks for the bug report! Unfortunately, some important information is missing in the backtrace. Could you install the kdebase4-debuginfo package (e.g., by running "sudo zypper install kdebase4-debuginfo" in a terminal), reproduce the crash and post an updated backtrace here? Thanks! The visible parts of the backtrace look like it might be related to bug 205888 which is supposed to be fixed. Created attachment 41595 [details]
New crash information added by DrKonqi
Here is the same crash issue with kdebase4-debuginfo installed. Thank you.
Thank you for your very prompt reply. I installed kdebase4-debuginfo and attached a new crash report to the same bug report. Let me know if there is anything more I can do. I use Fish / Konqueror alot..... ---------------------------------------- Sender: bugzilla_noreply@kde.org To: dave@thinkwelldesigns.com Reply-To: bug-control@bugs.kde.org Subject: SPAM-LOW: [Bug 230590] Konqueror crashes when using Fish protocol https://bugs.kde.org/show_bug.cgi?id=230590 Frank Reininghaus <frank78ac@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |frank78ac@googlemail.com --- Comment #1 from Frank Reininghaus <frank78ac googlemail com> 2010-03-13 17:21:49 --- Thanks for the bug report! Unfortunately, some important information is missing in the backtrace. Could you install the kdebase4-debuginfo package (e.g., by running "sudo zypper install kdebase4-debuginfo" in a terminal), reproduce the crash and post an updated backtrace here? Thanks! The visible parts of the backtrace look like it might be related to bug 205888 which is supposed to be fixed. Thanks for the update, but it seems I got the package wrong - sorry! The one we need here is "dolphin-debuginfo". Could you please run sudo zypper install dolphin-debuginfo and post a new backtrace here? I would guess that this is related to bug 229505 which was reported recently and which looks similar to bug 205888. Hi Frank, I posted a new bug report with the dolphin-debuginfo package installed. It didn't find the other bug report as a duplicate. :-( Thanks, Dave ---------------------------------------- From: Frank Reininghaus <frank78ac@googlemail.com> Sender: bugzilla_noreply@kde.org To: dave@thinkwelldesigns.com Reply-To: bug-control@bugs.kde.org List-Post: <mailto:bug-control@bugs.kde.org> https://bugs.kde.org/show_bug.cgi?id=230590 --- Comment #4 from Frank Reininghaus <frank78ac googlemail com> 2010-03-13 18:01:22 --- Thanks for the update, but it seems I got the package wrong - sorry! The one we need here is "dolphin-debuginfo". Could you please run sudo zypper install dolphin-debuginfo and post a new backtrace here? I would guess that this is related to bug 229505 which was reported recently and which looks similar to bug 205888. Created attachment 41599 [details]
New crash information added by DrKonqi
Hi Frank,
Missed the "manually enter a bug report ID" option before. So here's the report attached to my first bug report.
*** Bug 230607 has been marked as a duplicate of this bug. *** Dave, thanks for the new backtrace! It shows that it's really a duplicate of the other bug (which does not mean that the steps needed to get the crash are the same, but that the same error in the code is responsible for both crashes). I hope we can fix the issue soon. Thanks for your help! *** This bug has been marked as a duplicate of bug 229505 *** |