Bug 684927 - alacarte needs to require gnome-panel
Summary: alacarte needs to require gnome-panel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: alacarte
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-14 20:08 UTC by Christoph Wickert
Modified: 2011-03-19 05:51 UTC (History)
3 users (show)

Fixed In Version: alacarte-0.13.2-3.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-14 21:33:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christoph Wickert 2011-03-14 20:08:40 UTC
Description of problem:
alacarte needs to require gnome-panel because it provides /usr/bin/gnome-desktop-item-edit.

Version-Release number of selected component (if applicable):
alacarte-0.13.2-1.fc14.noarch

How reproducible:
always

Steps to Reproduce:
1. start the LXDE, Xfce or KDE spin
2. yum install alacarte
3. start alacarte and try to edit a menu entry

Actual results:
$ alacarte 
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py", line 382, in on_edit_properties_activate
    process = subprocess.Popen(['gnome-desktop-item-edit', file_path], env=os.environ)
  File "/usr/lib64/python2.7/subprocess.py", line 672, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1201, in _execute_child
    raise child_exception
OSError: [Errno 2] Datei oder Verzeichnis nicht gefunden

Comment 1 Fedora Update System 2011-03-14 21:18:37 UTC
alacarte-0.13.2-3.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/alacarte-0.13.2-3.fc15

Comment 2 Fedora Update System 2011-03-19 05:50:56 UTC
alacarte-0.13.2-3.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.