After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 535230 - Can't edit icon launcher properties
Can't edit icon launcher properties
Product: nautilus
Classification: Core
Component: Desktop
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Reported: 2008-05-28 10:35 UTC by Andrew Clayton
Modified: 2010-07-04 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Description Andrew Clayton 2008-05-28 10:35:33 UTC
Please describe the problem:
If you have an application icon on the desktop and goto properties --> launcher, the window will just disappear after a second. 

Steps to reproduce:
1. Drag an application from the menu onto the desktop
2. Right click the icon on the desktop and select properties
3. Select the launcher tab

Actual results:
The properties window closes.

Expected results:
The properties window should remain open so the application launcher details can be edited.

Does this happen every time?

Other information:
Comment 1 Baptiste Mille-Mathias 2008-05-28 11:22:51 UTC

From what I read, it seems the application responsible to display the properties is crashing. Do you have a dialog that warnin you Nautilus crashed ?
Could you confirm that ?

If it crash, could you install debug packages (glib, gtk+, gvfs, libeel and nautilus at least), refer to for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Andrew Clayton 2008-05-28 11:31:28 UTC
AFAICT, it isn't crashing, no crash dialogue and no error in dmesg.

Comment 3 Baptiste Mille-Mathias 2008-05-28 13:07:52 UTC
Just to ensure this is not a crash, please do the following

Could you install the debug packages I listed above and launch nautilus inside a debuger to see what happen; to do so just open a terminal and type gdb `pidof nautilus`.
Now do the action you described and see if it report a crash.

Comment 4 Andrew Clayton 2008-05-28 13:52:07 UTC
OK, I installed the following packages


Then did

$ killall nautilus # To restart it, dunno if that was needed.
$ gdb /usr/bin/nautilus `pgrep nautilus`

then this

(gdb) cont

Reproduced the problem and got this

[New Thread 0x4264e950 (LWP 35789)]
[New Thread 0x41485950 (LWP 35790)]
[Thread 0x4264e950 (LWP 35789) exited]
[New Thread 0x4264e950 (LWP 35794)]
[New Thread 0x41c86950 (LWP 35795)]
[Thread 0x41485950 (LWP 35790) exited]
[Thread 0x41c86950 (LWP 35795) exited]
[New Thread 0x41c86950 (LWP 35797)]
[New Thread 0x41485950 (LWP 35798)]
[Thread 0x41c86950 (LWP 35797) exited]
[Thread 0x4264e950 (LWP 35794) exited]
Comment 5 Andrew Clayton 2008-05-28 14:22:31 UTC
Hmm, I should probably mention that my home directory is mounted over NFS.
Comment 6 Joe Marcus Clarke 2008-06-09 23:06:36 UTC
I can reproduce this in GNOME 2.22.2 on FreeBSD i386 and amd64.  Nautilus is not crashing, and there are no errors in the .xsession-errors log.  It looks like a GUI programming mistake where the window is just destroyed.  Other FreeBSD users report the same thing.  The version of Nautilus is 2.22.3.
Comment 7 Baptiste Mille-Mathias 2008-06-10 06:21:58 UTC

Are you using FreeBSD too ? do you have any message in .xsession-errors?

on Ubuntu hardy, it works fine, (I'm using x86 though).
Comment 8 Andrew Clayton 2008-06-10 08:42:57 UTC
I'm using Linux (Fedora 9) on x86_64

No errors appear in .xsession-errors
Comment 9 Joe Marcus Clarke 2008-06-10 15:05:42 UTC
I personally see the error on i386 and amd64.  My home directories are mounted locally.  It doesn't work properly in Ubuntu for everyone.  See .
Comment 10 Marcus Carlson 2010-07-04 18:48:13 UTC
Is this still a problem in a recent version of nautilus? Tried in 2.30 and cannot reproduce.
Comment 11 Andrew Clayton 2010-07-04 19:54:28 UTC
Heh, I'd totally forgotten about this.

Running GNOME 2.28.2 / Nautilus 2.28.4 on Fedora 12 64bit. I no longer see this issue.
Comment 12 A. Walton 2010-07-04 20:07:16 UTC
Thank you for letting us know.