editing locations to the clock applet, keyboard navigation closes the dialog unexpectedly

Bug #529233 reported by Oren_B on 2010-02-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

When I edit the locations in the clock applet preferences and I navigate the dialog with the keyboard, pressing Enter on any button causes the dialog to close, as if I pressed the Close button. The Close button actually stays highlighted all the time, even when I highlight a different button. If I activate a highlighted button using the space bar instead of the Enter key, it works as expected.
This bug is very similar to a bug I filed against update-manager a few months ago:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/422673
Maybe they are both caused by the same underlying bug?

ProblemType: Bug
Architecture: i386
Date: Sun Feb 28 00:07:52 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
Package: gnome-panel 1:2.29.91-0ubuntu1
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SourcePackage: gnome-panel
Uname: Linux 2.6.32-14-generic i686

Oren_B (oren.barnea) wrote :
Pedro Villavicencio (pedro) wrote :

Thanks for the report, may you take an screenshot of that dialog and attach it to the report? Thanks in advance.

Changed in gnome-panel (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Oren_B (oren.barnea) wrote :

Screenshot attached.

Pedro Villavicencio (pedro) wrote :

Thanks Oren, could you attach gdb to that process ? the name should be something like /usr/lib/gnome-panel/gnome-clock-applet-mechanism ; for instructions on how to use gdb please read http://wiki.ubuntu.com/DebuggingProgramCrash ; thanks in advance.

Oren_B (oren.barnea) wrote :
Download full text (4.2 KiB)

First I have to say that I get the impression that the program doesn't really crash, but simply closes due to some error in the default action linked to pressing the Enter key.

I tried to follow the instructions and didn't really succeed. I'm not sure I was doing it correctly. Here's what I did, maybe you can find what I did wrong:
Installed the gnome-panel-dbgsym package, navigated to
/usr/lib/gnome-panel/
and from that location I ran gdb. Here's the outpou of the first try:

############################################################################
oren@lucky:/usr/lib/gnome-panel$ gdb gnome-clock-applet-mechanism 2>&1 | tee ~/gdb-gnome-clock-applet-mechanism.txt
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib/gnome-panel/gnome-clock-applet-mechanism...Reading symbols from /usr/lib/debug/usr/lib/gnome-panel/gnome-clock-applet-mechanism...done.
done.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/lib/gnome-panel/gnome-clock-applet-mechanism
[Thread debugging using libthread_db enabled]

** (process:31912): WARNING **: Failed to acquire org.gnome.ClockApplet.Mechanism: Connection ":1.132" is not allowed to own the service "org.gnome.ClockApplet.Mechanism" due to security policies in the configuration file

** (process:31912): WARNING **: Could not acquire name; bailing out

Program exited with code 01.
(gdb) exit
Undefined command: "exit". Try "help".
(gdb) quit
############################################################################

So I tried the same thing with sudo, but that didn't seem to work either:

############################################################################
oren@lucky:/usr/lib/gnome-panel$ sudo gdb gnome-clock-applet-mechanism 2>&1 | tee ~/gdb-gnome-clock-applet-mechanism.txt
[sudo] password for oren:
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib/gnome-panel/gnome-clock-applet-mechanism...Reading symbols from /usr/lib/debug/usr/lib/gnome-panel/gnome-clock-applet-mechanism...done.
done.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/lib/gnome-panel/gnome-...

Read more...

Sebastien Bacher (seb128) wrote :

the issue seems to be the default action binded to enter use

Oren_B (oren.barnea) wrote :

The current theme in Maverick shows that indeed there is some ambiguity regarding the selected button when navigating this dialog using the keyboard: the Close button is constantly highlighted in bright orange color on it all the time, and stays highlighted when the Tab key is pressed. Other buttons get highlighted with an orange frame around them, that moves from one button to the next upon pressing Tab. The bright orange button face seems to be associated to pressing Enter, and the orange frame seems to be associated to pressing Space Bar.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers