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 671859 - Startup notification doesn't always work for nautilus
Startup notification doesn't always work for nautilus
Status: RESOLVED DUPLICATE of bug 660577
Product: nautilus
Classification: Core
Component: general
3.2.x
Other Linux
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-12 00:39 UTC by xuedi
Modified: 2012-03-12 19:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description xuedi 2012-03-12 00:39:26 UTC
Hello,

I run gnome 3.2 in fallback mode. the system is extrem reactive, only when i start nautilus via the gnome-menue its takes 10 to 15 seconds to open.

Starting nautilus from the terminal its opening instantly, i found this error description on a few other websites, but not here in the bug tracker.

Same reports:
http://ubuntuforums.org/showthread.php?p=11622709
https://bbs.archlinux.org/viewtopic.php?id=127645

The started nautilus is, while the 15 seconds opening, usable... just the cursor keeps showing the loading animation, and there is a second tab in the window-panel saying [opening xxx]. So its not to bad, but the opening of two tab in the panel and closing one is irritating in a fast work-flow.

**unimportant extra question**
I could not debug this myself, nothing in the log files and i could not find a 'gnome-menue-lauch-command' in the gconf editor also and i did not even know where to start to look in the gnome source code.

Is there a overview about the components of gnome that helps to navigate and debug gnome3, i came only as far as projects.gnome.org ?

Cheers
xuedi
Comment 1 Vincent Untz 2012-03-12 08:43:42 UTC
You need to identify the .desktop file used to launch nautilus and attach it here. The best way to do this is to drag the launcher to a terminal.

It's likely that there's some startup notification issue there.
Comment 2 xuedi 2012-03-12 12:18:27 UTC
If a drag the places launcher in a terminal, he is just giving me the path, i made a 'locate nautilus.desktop' and i found two:

/home/<user>/.config/autostart/nautilus.desktop
http://pastebin.com/jLtG9Mj2

/usr/share/applications/nautilus.desktop
http://pastebin.com/ZbVFH0Xz
Comment 3 Vincent Untz 2012-03-12 12:29:54 UTC
(In reply to comment #2)
> If a drag the places launcher in a terminal, he is just giving me the path, i

Which path? :-)

> made a 'locate nautilus.desktop' and i found two:
> 
> /home/<user>/.config/autostart/nautilus.desktop
> http://pastebin.com/jLtG9Mj2

Hrm, autostart, shouldn't matter.

> /usr/share/applications/nautilus.desktop
> http://pastebin.com/ZbVFH0Xz

So that seems to be the one from the package.

Just for reference, I don't see this here.
Comment 4 Vincent Untz 2012-03-12 12:31:45 UTC
Ah, so something you didn't mention: you start nautilus by clicking on Home in the Places menu, not by clicking the nautilus launcher. I can reproduce in this case.
Comment 5 Vincent Untz 2012-03-12 12:49:52 UTC
I just did several launches this way and sometimes it works, sometimes it doesn't. For reference, the way we start nautilus in this case is with gtk_show_uri().

It just feels like nautilus is not completing its startup notification. I'm moving over to nautilus, but I'm surprised that this happens like this. I wonder if something weird could be happening here because of the use of GtkApplication or something similar...
Comment 6 Cosimo Cecchi 2012-03-12 19:37:36 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 660577 ***