Salix Forums

I installed icewm and started it with 'startx' command after having 'exec icewm' in ~/.xinitrc. I started in console mode after entering 'single' on kernel line of grub bootloader entry.

Everything works all right except that the file manager 'caja' does not see other partitions present on the computer. It does so when run in Mate desktop. These partitions are not in /etc/fstab file but they are normally shown by caja file manager and get mounted on clicking (after password). How can I solve this problem? Thanks for your help.

You need to start it with dbus-launch. Preferably start your entire icewm session with it.

I started the session with 'dbus-launch icewm' in .xinitrc and then giving command startx, but still no other partitions are seen with caja or thunar file managers. The entry 'ck-launch-session dbus-launch --exit-with-session icewm' also did not work. I tried running 'dbus-launch' from commandline (both as root and as user) but still no partitions are seen on caja or thunar (started after giving dbus-launch command). Giving 'export $(dbus-launch)' command also did not help. Where is the problem?

For your first message in this discussion thread:
That reads, as you run all this in single user mode. If so, not all the necessary services are already running, which are required e.g. by the file manager? Just one example: the automounter is not yet operating. For your experiments and to avoid the lack of displaying of automountable partions, the clickability of related symbols, runlevel 3 is required.

rsal wrote:I started the session with 'dbus-launch icewm' in .xinitrc and then giving command startx, but still no other partitions are seen with caja or thunar file managers. The entry 'ck-launch-session dbus-launch --exit-with-session icewm' also did not work. I tried running 'dbus-launch' from commandline (both as root and as user) but still no partitions are seen on caja or thunar (started after giving dbus-launch command). Giving 'export $(dbus-launch)' command also did not help. Where is the problem?

About the second message:
You need to use exec in front of your ck-launch-session string. exec ck-launch-session dbus-launch ......
You should also think about to complete icewm with its path.

One more word, export $(dbus-launch) is completely absurd:
$(dbus-launch) is a command substitution. For that, the shell needs to run dbus-launch first, then replace the text $(dbus-launch) for the output of dbus-launch. You do not want that. But command substitution is only important without exec, because with exec at this point no command substitution takes place and the result would be just as nonsensical.

The export command makes its argument visible to sub-shells. With exec, no sub-shell would be launched at all. For executable objects / code, one can not export commands. Only shell sub-functions are exportable.

Please read the Bash manual.

@westms : Thanks for your answer. Runlevel 3 did the trick. Both exec ck-launch... and ck-launch... work.