Ubuntu
alacarte package

When copying does not escape special characters

Bug #96727 reported by luc.levain on 2007-03-26

This bug report is a duplicate of: Bug #205463: alacarte crashed with IOError in copyItem() (when copying item with / in name). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	Alacarte Menu Editor	Invalid	Undecided	Unassigned
	alacarte (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Binary package hint: alacarte

alacarte crashed when moving aplication launchers to a subfolder - specifically, KDevelop: C/C++ and KDevelop: KDE/C++ to a folder named "KDevelop" under "Applications"->"Programming". As this does not happen with other launchers from the KDevelop packages, the error might be in alacarte not handling nonalphanumeric characters ("/" or "++") correctly.

ProblemType: Crash
Architecture: i386
Date: Tue Mar 27 01:20:23 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/alacarte
InterpreterPath: /usr/bin/python2.5
Package: alacarte 0.11.3-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
ProcCwd: /home/lukasz
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/alacarte']
SourcePackage: alacarte
Uname: Linux pimpus 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message

luc.levain (luc-levain) wrote on 2007-03-26:

Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (29.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (670 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (426 bytes, text/plain; charset="utf-8")

Chris Rose (chris-vault5) on 2007-03-27

Changed in alacarte:
importance:	Undecided → Medium
status:	Unconfirmed → Confirmed

Revision history for this message

Travis Watkins (amaranth) wrote on 2007-03-27:

'/home/lukasz/.local/share/applications/KDevelop: C/C++.desktop'

As you can see the / is messing it up. Oops. :/

Also, you don't have to upstream alacarte bugs. I'm responsible for alacarte bugs in Ubuntu and GNOME. :)

Changed in alacarte:
assignee:	nobody → amaranth

Revision history for this message

Chris Rose (chris-vault5) wrote on 2007-03-27:

Rejected the upstream bug :-)

Changed in alacarte:
status:	Unconfirmed → Rejected

Revision history for this message

Philip Paquette (pcpaquette) wrote on 2007-05-31:

Logs of ~/.config/menus and ~/.local/share Edit (4.3 KiB, application/octet-stream)

Travis,

IMO bug #64264 (gnome-menus doesn't send notification for new .desktop files), bug #96727 (When copying does not escape special characters), and bug #113652 (Alacarte still doesn't handle spaces properly) are all the same bug.

Here are steps to reproduce:

1) Revert
2) Create folder in "Sound&Video"
--> Name: test
--> Comment: (blank)

3) Create item in Sound&Video
--> Name: test<special character>test
--> Command: test
--> Comment: (blank)

4) Move item from Sound&Video to subfolder test

<special character> tested: /\ "#$%&+,:;<=>?@[]`{|}¢£±é*_-!()~'.
<special character> working: *_-!()~'.
<special character> not working: /\ "#$%&+,:;<=>?@[]`{|}¢£±é

Travis Watkins (amaranth) on 2008-06-10

Changed in alacarte:
assignee:	amaranth → nobody

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-07-11:

Thanks for the report luc.levain , It has been a long time without any comment or a duplicate in this bug report and It is possible that the bug has been fixed. May you please try to reproduce it with the latest Stable Release of Ubuntu the Natty Narwhal and add the respective comments to the report? You can learn how to get that release at http://www.ubuntu.com/download . Thanks again and we appreciate your help.

Revision history for this message

Vadim Rutkovsky (roignac) wrote on 2012-03-05:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 205463, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.