Custom color hangs in Conditional formatting

Bug #1008522 reported by Robert Spanjaard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gnumeric
Fix Released
Medium
gnumeric (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

When trying to select a custom color in Conditional Formatting, the Custom Color window is completely unresponsive. This happens with all types of conditional formatting where a color can be selected: font color, border color and background color.

Example:
Select a cell, and go to the menu Format -> Cells -> Conditional Formatting.
By default, Background is checked. This is fine for our test. Now, click Edit Style, then click the color selection button (the color square or the arrow, they work the same), and select Custom Color at the bottom of the selection box.
In the new window that appears, try to change anything. Or try to click Cancel or OK. It won't work. Trying to close the window won't work either.

A couple of notes that might make debugging easier:
- When you try to close a window (the cross in the title bar, or "Close" in a related menu), and the window stays open, you usually get a time-out window asking wether you want to wait for the window to close gracefully, or force it to close. In this case, that window doesn't appear at all.
- When you close the window that called the color selector (in this case, the window titled "Format Cells", the color selection window suddenly becomes responsive again, except for the Cancel and OK buttons.
- The color selector closes automatically when you close Gnumeric completely.

Versions:
- Ubuntu 12.04 LTS
- gnumeric 1.10.17-1ubuntu2

Revision history for this message
Andreas J Guelzow (aguelzow) wrote :
Revision history for this message
Andreas J Guelzow (aguelzow) wrote :

This problem is fixed in 1.11.4 and later.

Revision history for this message
Robert Spanjaard (spamtrap-arumes) wrote :

Will it be fixed in 1.10.17 for Ubuntu 12.04? I plan on using this OS for three years, so a fix in 1.11 won't help me unless it's going to be backported.

Changed in gnumeric:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Andreas J Guelzow (aguelzow) wrote :

@Robert. The problem has been fixed for 1.11.4 and later. Gnumeric 1.10.17 was released in July 2011. At that time nobody had reported the problem.

Whether 1.11.4 (or the current 1.11.5) is packaged for Ubuntu 12.04 is up to the Ubuntu team. I am an upstream Gnumeric developer and have nothing to do with Ubuntu.

Revision history for this message
Robert Spanjaard (spamtrap-arumes) wrote :

Thanks for the information. At least, with your comments I can set the bug to Confirmed, as you acknowledge that there is a bug in 1.11.3 and lower.

For the Ubuntu team: this should be easy to fix now...

Changed in gnumeric (Ubuntu):
status: New → Confirmed
Revision history for this message
Jeremy Bícha (jbicha) wrote :

This was fixed with gnumeric 1.12.1 which has been uploaded to the current development release of Ubuntu.

Changed in gnumeric (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Robert Spanjaard (spamtrap-arumes) wrote :

Oops... Accidentally set the status to Won't Fix, and only a superviser can set it back to Fix Released. My apologies.

But please note that my question regarding Ubuntu 12.04 is still unanswered. Do you really plan to leave this bug in 12.04 for the next 5 years?

Changed in gnumeric (Ubuntu):
status: Fix Released → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.