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 655235 - Desktop icons disappear when middle-clicked
Desktop icons disappear when middle-clicked
Status: RESOLVED DUPLICATE of bug 655576
Product: nautilus
Classification: Core
Component: Desktop
3.0.x
Other Linux
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-25 05:43 UTC by Cullan Whitaker
Modified: 2012-02-06 21:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cullan Whitaker 2011-07-25 05:43:53 UTC
I originally filed this for gnome-tweak-tool, and was pointed in this direction.
I'm very new to bug finding/submitting, so I'm sorry in advance if this is out of place or somehow irrelevant. 

I can only confirm this for my current rig.

I'm running Archlinux with GNOME 3 on an ASUS N61jv x-4 laptop which has a
multi-touch enabled trackpad. Using gnome-tweak-tool I have "Have file manager handle the desktop" set
to "ON" so I can use my desktop like I'm so used to from GNOME 2. I've found
that if I accidentally middle-click a desktop icon with my touch pad (the same
gesture is a right-click in Windows, which I frequently use), all the icons on
the desktop disappear. I also tried this with an external USB mouse with the same result.

This effect is 100% reproducable on my system. If I open the gnome-tweak-tool
after this happens, I can see that the file manager is still set to handle the
desktop. If I set it to "off" and then back to "on", or if I open the file
manager from the main menu, my desktop icons reappear.


I figure the problem is either from some rookie mis-configuration on my part, incompatibility with gnome-tweak-tool, or just because GNOME 3 is so new. I looked over my log files and didn't find any relevant information. Beyond that, I don't really have a whole lot of know-how in diagnosing graphical problems like this.
Comment 1 Marcel Stimberg 2012-01-29 18:16:19 UTC
Hi Cullan,
the same issue is present on Ubuntu (11.10 and 12.4) with nautilus 3.2.0 respectively 3.2.1. The fact the the "desktop icons disappear" is actually a symptom of nautilus crashing with a segmentation fault. I filed a bug in the Ubuntu bug tracker containing additional debug information:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/923432

Here an excerpt from the stacktrace:
g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x511ac0 "nautilus_window_slot_open_location_full", message=0x7f7a700c1fa0 "assertion failed: (target_window == window)") at /build/buildd/glib2.0-2.31.12/./glib/gtestutils.c:1860
 g_assertion_message_expr (domain=0x0, file=0x5113b0 "nautilus-window-manage-views.c", line=507, func=0x511ac0 "nautilus_window_slot_open_location_full", expr=<optimized out>) at /build/buildd/glib2.0-2.31.12/./glib/gtestutils.c:1871
 nautilus_window_slot_open_location_full (slot=0x1f618c0, location=0x2462b00, flags=NAUTILUS_WINDOW_OPEN_FLAG_NEW_TAB, new_selection=0x0, callback=0, user_data=0x0) at nautilus-window-manage-views.c:507
 activate_files (parameters=0x22b5800) at nautilus-mime-actions.c:1754
 activate_callback (files=<optimized out>, callback_data=0x22b5800) at nautilus-mime-actions.c:1976

[@Cullan: Unfortunately I do not have the permissions to mark the bug as confirmed...]
Comment 2 Marcel Stimberg 2012-01-30 10:20:53 UTC
This bug can also be triggered by opening two folders on the desktop at once (e.g. by selecting them and pressing the return key). It seems to be the same issue that has already been reported as bug 655576 and should probably marked as a duplicate.
Comment 3 Cosimo Cecchi 2012-02-06 21:06:55 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 655576 ***