Unicode error when trying to tick or delete an unticked item

Bug #1186523 reported by Marion Zepf
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Invalid
Low
Unassigned
alacarte (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

What I did:
I marked an unticked menu item in alacarte and clicked the checkbox to tick it. The error also occurs when I mark it and click the 'delete' button.

What happened:
Nothing happens in alacarte. The blue background that marks the item as selected disappears, as if it had lost the GUI focus. When I start alacarte from the command line and try to reproduce the bug, I see tracebacks of Python Unicode errors on the command line (see attached file).

What's strange:
When I mark an unticked item and click 'New separator', 'Move up', or 'Move down', the item gets ticked again (in addition to the separator being inserted, or the item being moved). This works most of the time, but not always.
The 'Properties' button works insofar as it brings up the correct dialog box, but all entry fields are empty. This problem remains after the item has been re-ticked by one of the 'New separator', 'Move up', and 'Move down' buttons.

Ubuntu release: 13.04 Raring Ringtail (just upgraded from 12.10 Quantal Quetzal)
Alacarte version: 3.7.90-0ubuntu1~raring1

Purging and re-installing alacarte did not fix the issue.

Tags: gnome3 raring
Revision history for this message
Marion Zepf (marion-zepf) wrote :
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in alacarte (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in ubuntu-gnome:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Tim Lunn (darkxst) wrote :

Marion, can you copy the output from 'locale' command

Revision history for this message
Marion Zepf (marion-zepf) wrote :

Here is the output of the 'locale' command:
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

In the meantime, I have fixed the issue temporarily by downgrading to version 3.6.1-0ubuntu3, which is from the official Ubuntu repositories. The version that was causing problems was from this PPA:
http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ raring/main
But I can't find the 'Report a bug' button at the Gnome3 Team's Launchpad site.

Revision history for this message
Bruce Pieterse (octoquad) wrote :

Thank you for reporting this bug to Ubuntu. Raring Ringtail reached EOL on January 27, 2014 .
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Utopic Unicorn and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.

alacarte:
  Installed: 3.11.91-1
  Candidate: 3.11.91-1
  Version table:
 *** 3.11.91-1 0
        500 http://za.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
        100 /var/lib/dpkg/status

Changed in ubuntu-gnome:
status: Triaged → Invalid
importance: Medium → Low
Changed in alacarte (Ubuntu):
status: Triaged → Invalid
Revision history for this message
Marion Zepf (marion-zepf) wrote :

Thank you for the reminder, Bruce! I've upgraded to Trusty Tahr in the meantime and now I can't reproduce the bug any more. It seems to have been fixed at some point.

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.