GNOME Bugzilla – Bug 499450
Launcher applet properties for document not persisted across sessions
Last modified: 2020-11-06 20:25:40 UTC
Please describe the problem: I have a file deep in a directory tree that I access frequently, so I've created a launcher applet from link file created with "Make Link". It launches the file correctly, but when I log out/in, the properties of the launcher are blank. Steps to reproduce: 1. Right-click on Panel, select "Add to Panel", from Add to Panel application, click "Custom Application Launcher". 2. Select "Location" from the drop-down 3. Browse to the file of interest, enter a name, etc. click Ok. 4. Test the launcher to verify, log out of Gnome. 5. Log in, launcher still there, but launcher properties are blank. Actual results: Launcher has no properties to launch anything. Expected results: A document would open. Does this happen every time? yes. Other information:
*** Bug 499679 has been marked as a duplicate of this bug. ***
I have had exactly the same problem : custom launcher properties turn blank when logging out+in. This is with gnome 2.22.3. Here is a workaround : 1. Create the launcher. Check it is working correctly. 2. Go to ~/.gnome2/panel2.d/default/launchers/ 3. The launcher file has a auto-generated name such as "%252522cd.desktop" : rename it, eg "my_launcher.desktop". 4. Go to gconf-editor. 5. Find the key corresponding to your launcher : it should have a name like "/apps/panel/objects/object_*", and its sub-key "launcher_location" should have the auto-generated filename ("%252522cd.desktop") as its value. 6. Modify the "launcher_location" value to the new name, "my_launcher.desktop". This appears to work. -- Bruno
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.