Manage desktop with nautilus3?

[Fisch.666]

Hi!

Because i want to use a twin-panel filemanager i've replaced pcmanfm with nautilus2 on my debian testing system. For this i've replaced:

Code: Select all

@pcmanfm --desktop --profile LXDE

in the /etc/xdg/lxsession/LXDE/autostart with this:

Code: Select all

@nautilus -n

witch works as it should. After the update from nautilus 2 to nautilus 3 i can't get nautilus to manage my desktop. It just stopped drawing the icons and the background.

Anyone hat the same problem and found a solution? Thanks in advance for a reply.

[piotreks]

I'm pretty sure LXDE is based on GTK+ 2.X, whereas Nautilus 3 is using the GTK+ 3.0 API.
See here: http://live.gnome.org/Nautilus/News

You can verify by running ldd on the nautilus executable and checking the gtk version it is linked against...something like this (just substitute the nautilus executable path for /usr/bin/pcmanfm):

Code: Select all

# ldd /usr/bin/pcmanfm | grep -i gtk
	libfm-gtk.so.1 => /usr/lib64/libfm-gtk.so.1 (0x000000323e200000)
	libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x000000323da00000)

Note libgtk-x11-2.0.

If you don't have it installed, you can try to use your distribution update mechanism (yum/apt/whatever) to install gtk-3.0 and try running nautilus then (although I'm not 100% sure that will fix it for you).

P

[Fisch.666]

Hi!

Thanks for your reply

Yes, nautilus 3 is linked against libgtk-3:

Code: Select all

ldd /usr/bin/nautilus | grep -i gtk
	libgtk-3.so.0 => /usr/lib/i386-linux-gnu/libgtk-3.so.0 (0x4be5a000)

and libgtk-3-0 is installed on my system. And Nautilus 3 is working on my system, but it just doesn't draw / manage the desktop when starting.

[piotreks]

... and libgtk-3-0 is installed on my system. And Nautilus 3 is working on my system, but it just doesn't draw / manage the desktop when starting.

To the best of my knowledge most, if not all, components of LXDE are linked against gtk-2.0 (i.e. use gtk-2.0 API).
It is very possible that, since Nautilus 3 uses gtk-3.0 API, some of the calls it expects are not provided by the environment and therefore it cannot be guaranteed to work correctly with components using an older API.

I'm not familiar with the actual differences between the APIs, so please take the above as speculation.

P

[Fisch.666]

Hey,

thanks again for your reply. Nice to now the API 2.0 / 3.0 stuff, maybe i can find more infos about this on the web.