Bug 328155

Summary:	gnome-main-menu does not launch yast2
Product:	[openSUSE] openSUSE 11.0	Reporter:	JP Rosevear <jpr>
Component:	GNOME	Assignee:	Scott Reeves <sreeves>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	federico, ro
Version:	Alpha 2plus
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:	gnome-function-does-not-work
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	341831

Description JP Rosevear 2007-09-25 13:07:18 UTC

I dragged yast2 from the alt-f2 menu after entering "yast2".  It does not launch from the main menu, the error on the command line is:

** (slab:1956): WARNING **: error launching file:///tmp/yast2-4.desktop [The location or file could not be found.]

Comment 1 Mark Gordon 2007-09-26 18:41:18 UTC

This is working for me in RC2.

Comment 2 JP Rosevear 2007-10-02 20:55:55 UTC

Dragging from the icon in the alt-f2 run dialog seems to be the key.  Dragging from the app browser/cc worked fine.  Gedit worked fine dragging from the same place.

Perhaps its related to the yast2 binary not being in the path.

Comment 3 James Krehl 2007-10-29 21:27:53 UTC

Yeah, because "yast2" is not in the standard user's path, the .desktop file that the run-dialog creates is of type "Link" not of type "Application".  "Link" types do not have an Exec field and the main-menu doesn't know what to do with them.  I have a fix ready which makes the main-menu ignore non-"Application" .desktop types.  This will not allow you to drag yast2 from the run-dialog to the main-menu, but it will also not let main-menu create a useless item in the "Favorites" list.

Comment 4 James Krehl 2007-10-29 23:25:03 UTC

I submitted this to autobuild.

Comment 5 Ruediger Oertel 2007-11-20 00:09:37 UTC

just submitting makes the package sit there forever.
for any update for a released product we need a SWAMPID and a patchinfo
file.

Anja: update approved ?

Comment 11 Scott Reeves 2008-03-08 00:41:59 UTC

Jimmy committed this to svn awhile ago. The latest svn tarball has recently been submited to factory so - this is fixed in 11.0.