Grisbi crash (and then complete X server crash) when entering a category in a new operation with keyboard (not with mouse)
Bug #399295 reported by
dreamincoco
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grisbi (Ubuntu) |
Fix Released
|
Undecided
|
Stéphane Glondu | ||
Bug Description
Sorry if the terms are wrong, I use a french UI.
In the Operations tab, create a new operation.
Enter the date then click in the Category area
Enter the parent category with the keyboard (e.g. "Soins"), then try to switch to a child category with arrows/keyboard (e.g. "Habillement") : the application crashes and I must restart X server with Ctrl+Alt/Backspace.
Related branches
Revision history for this message
| Stéphane Glondu (glondu) wrote Re: [Bug 399295] [NEW] Grisbi crash | #1 |
Revision history for this message
| Stéphane Glondu (glondu) wrote | #2 |
| Changed in grisbi (Ubuntu): | |
| assignee: | nobody → Stéphane Glondu (glondu) |
| status: | New → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in grisbi (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
dreamincoco a écrit :
> In the Operations tab, create a new operation.
> Enter the date then click in the Category area
> Enter the parent category with the keyboard (e.g. "Soins"), then try to switch to a child category with arrows/keyboard (e.g. "Habillement") : the application crashes and I must restart X server with Ctrl+Alt/Backspace.
I can also observe the bug in Debian, but the X server doesn't
"completely crash". The graphical interface is indeed mostly
unresponsive, but the Gnome monitoring applets still work and everything
goes back to normal after killing grisbi (e.g. from a console via
Crtl-Alt-F1).
I had already experienced a similar bug once, but were unable to
reproduce it with such predictable way.
--
Stéphane