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 672110 - Nautilus crashens when zooming with <ctrl> + <mouse wheel>
Nautilus crashens when zooming with <ctrl> + <mouse wheel>
Status: RESOLVED DUPLICATE of bug 671650
Product: nautilus
Classification: Core
Component: Navigation
3.3.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-15 00:23 UTC by Adriano Moura
Modified: 2012-03-15 12:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adriano Moura 2012-03-15 00:23:24 UTC 
Nautilus seems to just crash every time I try the <ctrl> + <mouse wheel> shortcut (Using the menu or <ctrl> + <+>|<-> works fine).

This is what I see at the console:
$ nautilus
Gtk-DEBUG: Connecting to session manager
Tracker-DEBUG: Initializing tracker-tags extension

**
ERROR:nautilus-view.c:9486:nautilus_view_handle_scroll_event: code should not be reached
Abortado


I'm using ArchLinux with Gnome 3.3.91 from the gnome-unstable ropos and the recently updated xorg-server 1.12.0 from the extra repo. (System is fully updated)
Comment 1 André Klapper 2012-03-15 10:57:43 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Cosimo Cecchi 2012-03-15 12:41:56 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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