Bug 184698 - crash when using non-existing key binding
Summary: crash when using non-existing key binding
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-02-17 19:44 UTC by Vedran Sego
Modified: 2018-10-21 04:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vedran Sego 2009-02-17 19:44:13 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Fedora RPMs

When konsole is started and a session using non-existing key binding is started, kosnole crashes.

This has happened when I upgraded to KDE 4.2. It removed few key bindings and one of them was used by one of my profiles. When I started that profile, konsole crashed. When I started default profile and changed it to that broken profile, it stopped accepting keyboard input, but konsole did not crash.

This repairs easily: one has to edit the profile in question. Might be problem if all profiles are broken.
Comment 1 Dario Andres 2009-02-17 23:34:56 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Vedran Sego 2009-02-21 19:11:25 UTC
Sorry, I cannot reconstruct it since I've repaired it. Maybe it would be possible with multiple restarts of my konsole, but I cannot "afford" that at the moment.

The way I see it, this is a matter of a minor if() somewhere in the startup of a new tab. If it's not easy to find it, it doesn't matter. I think my response is enough to help anyone who stumbles upon this problem and Googles it.

Sorry I cannot be more useful.
Comment 3 Christophe Marin 2009-04-24 11:07:48 UTC
No backtrace was provided (Comment #1). Changing this bug status.
Comment 4 Andrew Crouthamel 2018-09-19 04:33:21 UTC
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!
Comment 5 Andrew Crouthamel 2018-10-21 04:59:17 UTC
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!