| Summary: | Fallo inesperado | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Miguel <alejandrogroso> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | |
| Priority: | NOR | ||
| Version First Reported In: | 2.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Miguel
2013-06-26 20:33:15 UTC
Thanks for the bug report. I do understand a bit of Spanish, but is there any chance you could provide instructions to reproduce this in English? Moreover, it might help if you could install debugging packages for Dolphin and provide a new backtrace. Thanks. sorry thought I had to translate personnel...
with regard to doing a new trace, you mean that after installing the debugging packages dolphin "resend" the trace, or try to make the application crash and "regenerate" a new trace ...
PS: It pleases me that a foreigner knows Castilian / Spanish
> From: frank78ac@googlemail.com
> To: alejandrogroso@hotmail.com
> Subject: [dolphin] [Bug 321654] Fallo inesperado
> Date: Wed, 26 Jun 2013 20:37:17 +0000
>
> https://bugs.kde.org/show_bug.cgi?id=321654
>
> --- Comment #1 from Frank Reininghaus <frank78ac@googlemail.com> ---
> Thanks for the bug report. I do understand a bit of Spanish, but is there any
> chance you could provide instructions to reproduce this in English?
>
> Moreover, it might help if you could install debugging packages for Dolphin and
> provide a new backtrace. Thanks.
>
> --
> You are receiving this mail because:
> You reported the bug.
know my lack of experienced FE excuse is that I'm new to this for debugging and reverse traces ... I also use the "language" half, (in my case English), and to not take try the "Google", I'm not particularly translate very attached to that tool and present it well, usually handling technical language files , but given the simplicity of the message, the use ... ps: sorry for the delay, but I wanted to send the message as soon as I got your email, my connexion to the web was who prevented ... I was browsing the archives normally when closed unexpectedly, I thought I had accidentally closed the windows, immediately turned to open a window when I notice that opened another window and wizard to failures ... I have noticed that the system behaves in a somewhat unstable ... I really hope that in reviewing the report system to find the reason for the failure ... I usually run into these problems when I try to multitasking, the system becomes unstable and returns me these kinds of results ... by more than let it recover by closing everything and trying to do one thing, the system continues as if he was demanding, and only recover if reboot. hope this will serve from now thanks ... Thanks for the info. Unfortunately, the backtrace does not contain sufficient information to understand what the problem is. It would be good if you could install debugging packages and provide a new backtrace if you see the crash again. If you still have the crash report window open, you might be able to reload the backtrace. Thanks for your help! If you see the crash again in Dolphin 4.12.2 or later, and you can provide a more detailed backtrace (for that, you have to install the Dolphin debugging packages provided by your distro), please reopen this report. Thanks for your help! Closing this bug now, seems fixed. Thanks for reporting this bug! |