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 663657 - Ctrl+T on desktop shows empty white tab in fullscreen (except for panel)
Ctrl+T on desktop shows empty white tab in fullscreen (except for panel)
Status: RESOLVED DUPLICATE of bug 655256
Product: nautilus
Classification: Core
Component: Tabs
3.2.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-08 22:46 UTC by Yi Yao
Modified: 2012-02-06 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Yi Yao 2011-11-08 22:46:00 UTC 
This is my first bug filed for the Gnome project, so please tell me if I put it in the wrong category or if I missed some conventions.

Pressing Ctrl+T (new tab) while the desktop has focus will cause the desktop to create a new blank tab while opening a new Nautilus file browser window.

To reproduce:
1 - Set Forced Fallback Mode to ON
2 - Log out and back in
3 - Click on the desktop
4 - Press Ctrl+T

Notice the desktop went blank and a new tab appeared on your desktop. Notice also that a new Nautilus file browser window appeared.
Comment 1 Yi Yao 2011-11-08 22:48:35 UTC 
I should have mentioned I am running:
- Arch Linux x86_64
- Nautilus 3.2.1
Comment 2 André Klapper 2012-01-16 15:14:17 UTC 
Confirming on Fedora 16.
Comment 3 Jon Dowland 2012-02-03 09:41:13 UTC 
You can reproduce this w/o fallback mode by enabling the Desktop in gnome-tweak-tool (or doing whatever gconf/dconf/gsettings/something-else tweaking in the background).

Reproducible with 3.2.1 (Debian package version -2+b1)
Comment 4 Cosimo Cecchi 2012-02-06 19:01:43 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 655256 ***