Nautilus will not open in gnome 3.20

English Applications
1

Hello Folks,

I’m wondering if anyone is having this problem with the new iteration of gnome 3.20 in Tumbleweed. It seems that when I try to open Files (nautilus) it will not open when I press the icon. I can open it using the terminal, but get this message:

(nautilus:9009): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at ‘/org/gnome/libgd/tagged-entry/default.css’ does not exist

I realize that all the bugs are probably not worked out yet and a patch or update may be sent out. Any suggestions on a fix? I couldn’t really find any solutions during my searches.

Thanks.

2

Hi
That’s just a warning, shouldn’t stop nautilus from opening… If you fire up gnome-terminal and run the nautilus command, what output do you get?

Just tested here and see the warning, but it does open and work from either the overview icon or terminal.

3

Thanks malcolmlewis.

I hope I’m providing you with the correct response. I opened up the Terminal as root and entered the nautilus command.
This is what I got:

Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)

(nautilus:11082): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at ‘/org/gnome/libgd/tagged-entry/default.css’ does not exist

(nautilus:11082): dconf-WARNING **: failed to commit changes to dconf: The connection is closed

(nautilus:11082): dconf-WARNING **: failed to commit changes to dconf: The connection is closed

(nautilus:11082): dconf-WARNING **: failed to commit changes to dconf: The connection is closed

(nautilus:11082): GLib-GObject-CRITICAL **: g_object_set: assertion ‘G_IS_OBJECT (object)’ failed

(nautilus:11082): dconf-WARNING **: failed to commit changes to dconf: The connection is closed

4

Ahh, your trying to run as root (I did wonder…:wink: ), not as logging into the desktop, or just via a terminal, if via a terminal are you using su - why not just start with gnomesu?

Or are you after a desktop file for your user?

5

Actually, I hardly ever log in to nautilus as root and when I do I always use gnomesu. Nautilus won’t open as a regular user.

I have a feeling I’m not giving you the info you want or following your instructions properly.
How exactly do I give you the info you are asking for?..Sometimes I can be a little dense. :wink:

Anyway, here it is using gnomesu.

(gnomesu:11864): Gtk-WARNING **: gtk_window_set_titlebar() called on a realized window
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

(nautilus:11873): Gtk-WARNING **: Failed to register client: GDBus.Errororg.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

(nautilus:11873): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at ‘/org/gnome/libgd/tagged-entry/default.css’ does not exist

6

Hi
You comment “I opened up the Terminal as root …” confused me :wink:

OK, so just to confirm, you press the files icon (aka Nautilus) in the overview and it won’t start. You open a gnome-terminal and run the nautilus command and again it won’t start. Or is it in the terminal you see errors, but it does open?

If you create a test user and login, does the issue replicate? This will confirm either a system issue or a user issue.

7

Thanks malcolmlewis not a problem. I often, confuse myself. :slight_smile:

When I press the icon it will not open. If I use the terminal and type in “nautilus” it will open, and I will get the warning messages, which as you have mentioned are okay.

Is the Terminal different than gnome-terminal?

Thanks

8

Hi
gnome-terminal/terminal are the same thing :wink:

OK, so something funky with the desktop item. If you go into overview and in the search type nau and Files should pop up, click on that, does it work? If so then in overview right-click on the menu item and remove ‘Files’ from favorites and then re-add via the previous search.

If not, then sounds like something has not indexed, is /usr/share/applications/nautilus-classic.desktop present?

9

@malcolmlewis

Okay. Your suggestions to open nautilus made me think about the way**“I” **open Apps.

I usually open all my gnome Apps by right clicking on the App in the Dash and choosing “New Window”. For some reason Nautilus does not open up that way, but works just fine when I just left click on the App. So I guess
that my dilemma isn’t really that much of a dilemma and maybe not really on at all.:embarrassed:

It did used to work that way, I think…sorry. :frowning:

10

Hi
Ahh, OK, confirmed it’s not working with the new window method. Checking with my Gnome contacts…

11

On Mon 04 Apr 2016 12:16:01 AM CDT, malcolmlewis wrote:

Cuttlefish;2773200 Wrote:
> @malcolmlewis
>
> Okay. Your suggestions to open nautilus made me think about the
> way*“I” *open Apps.
>
> I usually open all my gnome Apps by right clicking on the App in the
> Dash and choosing “New Window”. For some reason Nautilus does not
> open up that way, but works just fine when I just left click on the
> App. So I guess
> that my dilemma isn’t really that much of a dilemma and maybe not
> really on at all.:embarrassed:
>
> It did used to work that way, I think…sorry. :frowning:
Hi
Ahh, OK, confirmed it’s not working with the new window method. Checking
with my Gnome contacts…

Hi
So this is what introduced the new logic;
https://bugzilla.gnome.org/show_bug.cgi?id=756370

Looks like we need to raise a new bug upstream, give me a day or so and
will post back the bug reference.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.53-60.30-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

12

On Sun 03 Apr 2016 09:46:02 PM CDT, Cuttlefish wrote:

@malcolmlewis

Okay. Your suggestions to open nautilus made me think about the way*“I”
*open Apps.

I usually open all my gnome Apps by right clicking on the App in the
Dash and choosing “New Window”. For some reason Nautilus does not open
up that way, but works just fine when I just left click on the App. So
I guess
that my dilemma isn’t really that much of a dilemma and maybe not really
on at all.:embarrassed:

It did used to work that way, I think…sorry. :frowning:

Hi
Can you do a couple of things to confirm we are seeing the same;

  • Open a gnome-terminal and run;

journalctl -f

Now try to open a New Window and you should see something like;


Apr 05 18:41:37 ernie.homelinux.org org.gnome.Nautilus[1693]: **
Apr 05 18:41:37 ernie.homelinux.org org.gnome.Nautilus[1693]:   ERROR:nautilus-window.c:2429:nautilus_window_get_active_slot:   assertion failed: (NAUTILUS_IS_WINDOW (window))
Apr 05 18:41:42   ernie.homelinux.org systemd-coredump[2487]: Process 2480 (nautilus) of user 1000 dumped core.

If this is the case, then it’s the new action, if you want a temporary
fix, just need to edit the desktop
file(/usr/share/applications/org.gnome.Nautilus.desktop) and remove
the actions entries (last 5 lines), or ignore the New Window for the
moment.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.53-60.30-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

13

If this is the case, then it’s the new action, if you want a temporary
fix, just need to edit the desktop
file(/usr/share/applications/org.gnome.Nautilus.desktop) and remove
the actions entries (last 5 lines), or ignore the New Window for the
moment.

Yep, that is what I see.

Apr 06 16:23:42 Tumbleweed org.gnome.Nautilus[1737]: **
Apr 06 16:23:42 Tumbleweed org.gnome.Nautilus[1737]: ERROR:nautilus-window.c:2429:nautilus_window_get_active_slot: assertion failed: (NAUTILUS_IS_WINDOW (window))
Apr 06 16:23:45 Tumbleweed systemd-coredump[2587]: Process 2581 (nautilus) of user 1000 dumped core.

Thank you for helping me out with this. I think I will dig into the code and learn something! :slight_smile: Much obliged!

14

Hi
New bug created, add yourself and comment if your inclined :wink:
https://bugzilla.gnome.org/show_bug.cgi?id=764702

15

On Wed 06 Apr 2016 11:06:01 PM CDT, malcolmlewis wrote:

Cuttlefish;2773616 Wrote:
> Yep, that is what I see.
>
> >
Code:

> > Apr 06 16:23:42 Tumbleweed org.gnome.Nautilus[1737]: **
> Apr 06 16:23:42 Tumbleweed org.gnome.Nautilus[1737]:
ERROR:nautilus-window.c:2429:nautilus_window_get_active_slot: assertion
failed: (NAUTILUS_IS_WINDOW (window)) > Apr 06 16:23:45 Tumbleweed
systemd-coredump[2587]: Process 2581 (nautilus) of user 1000 dumped
core. > --------------------
> >
>
> Thank you for helping me out with this. I think I will dig into the
> code and learn something! :slight_smile: Much obliged!
Hi
New bug created, add yourself and comment if your inclined :wink:
Bug 764702 – New window action not working unless Nautilus already running.

Hi
Looks like it’s been fixed in Bug 765045 – nautilus crashes on startup when launched by right clicking -> "New window" in gnome-shell

Just need to wait for the fix to appear :wink:

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.20-11-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

16

Thanks!

:slight_smile: