| Summary: | konsole crashes when 'file - save output as...' is clicked | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Matti <math.eber> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | cfeck |
| Priority: | NOR | Keywords: | triaged |
| Version: | 4.10.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Matti
2013-04-23 18:47:20 UTC
Since this works here, please add the backtrace, ideally with debug symbols. For more information, please see http://techbase.kde.org/User:DarioAndres/How_to_provide_more_information_about_crash_reports I tried to, and installed konsole-debuginfo and konsole-debugsource. But all I get is the message: Application: Konsole (kdeinit4 (deleted)), signal: Segmentation fault [Current thread is 1 (process 25311)] Thread 1 (process 25311): #0 0x8bff958d in ?? () What else can I do to get a backtrace? btw; I just see that I have exactly the same behaviour when I open KWrite, enter some text and try to save it into a file. Application: KWrite (kdeinit4 (deleted)), signal: Segmentation fault [Current thread is 1 (process 25558)] Thread 1 (process 25558): #0 0x8bff958d in ?? () So, this issue is not restricted to konsole. Does the same issue happen on a freshly created user account? Did the crash also occur with KDE 4.10.0 from release repository, or only after updating KDE? The user account is fresh - it is a new machine, used just a few days. The crashes happened after closing the lid, s2disk and resuming for some days. Now, I rebooted the machine - and everything works as expected! After one s2disk and resuming it still is ok. So, this issue might be result of bad resuming (which doesn't work very well, anyway). I will have an eye on it and tell you if it happens again. 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 set the bug status 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! Dear Bug Submitter, 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! |