SliTaz Forum
You are not logged in.
Pages: 1
Put the package pcmanfm2 (version 0.9.8).
As a result, received a black desktop. No wallpaper and no icons. Trash does not work (operation not supported). The terminal emulator will not start (the menu).
How is all this correct?
Offline
For the terminal, go to Edit > Preferences > Advanced tab, and define it.
Offline
Thank you! The terminal is now running.
Desktop brown. But no wallpaper or icons are not visible.
Files can get out of the basket ([c]/home/tux/.local/share/Trash[/c]). But the basket is still not working.
Offline
I don't use myself wallpaper or icons, but this package seems quite buggy (and no idea if it's pcmanfm bugs or slitaz-packages bugs)
The ones I stumble upon :
- No ui for managing wallpaper or icons, despite having a /usr/share/pcmanfm/ui/desktop-pref.ui installed
- details view freeze at best, or crash (bug already in 0.5.2.)
- no properties window when you click on it
I'll stay with mc 
Good luck
Offline
I upgraded pcmanfm as well, but haven't faced any freeze/crash yet, though on right click of a file/folder and selecting Properties doesn't show anything.
Wallpaper support is not there, maybe that's because latest version of pcmanfm doesn't support it, may not be a slitaz issue. You can still setup wallpaper using "nitrogen" which is available in the repo. And in $HOME/.config/openbox/autostart.sh of the user, add "nitrogen --restore &" after selecting your initial wallpaper. It works even after you've rebooted your machine.
Offline
I removed the package pcmanfm 0.9.8 and got the same black desktop.
The previous version of pcmanfm 0.5.2 has not recovered. Restored through the package manager.
Pcmanfm 0.5 version is no longer growing. I should lubuntu with pcmanfm 0.9.9. Wallpaper support, a trash, the desktop icons can be moved, automounting works.
It is a pity that slitaz does not work. 
Offline
The thing is pcmanfm 0.9.9 uses gnome-vfs to make it's mounting and trash can work. The downside to this? You have to drag half of GNOME with it to make things work.
You're also wrong about PCManFM 0.5.2 series not being worked on anymore. Check out http://igurublog.wordpress.com/downloads/mod-pcmanfm/ if you don't believe me 
Offline
@Trixar_za
Thanks for the explanation.
Please do not be offended. I just do not understand programming. I am a simple user. Sometimes I read various articles on them and compose their own opinion (perhaps often not correct:)).
Offline
Hello!
If my memory is not completely bugged... It seems to me that between the two versions a change has been made by pcman to how the desktop is launched. Now you have to use
pcmanfm --desktopinstead of launching the desktop on the first launch and the file manager the next.
So Openbox is launching a file manager, instead of the desktop, because somewhere the command lacks a "--desktop" option 
I cannot find a config file to change the default behaviour of openbox in slitaz for this...
If I find it, I'll post again
Offline
It's called Auto started applications in "Start"--> Preferences and if you right clicked on the desktop it would be under Openbox--> Autostart script.
It's funny that they mentioned the change where you read it, but not how to change it in Openbox (which has always been part of LXDE like pcmanfm). The default that is used by SliTaz is [c]pcmanfm -d &[/c] which probably is also the flag for the new option. Also, use < code> (without the space) not [code].
Offline
Mumble...
I'm used to openbox and pcmanfm, but I am new to Slitaz.
I had noticed the autostart file... But it's empty. The line which starts pcmanfm as desktop manager must be somewhere else, I hope it's not hardcoded! -_-
Offline
It's a bad sign if the autostart file is empty... 
Here's mine though (no, you don't need all this, nor do you have everything I do):
[c]# This shell script is run before Openbox launches.
# Environment variables set here are passed to the Openbox session.
# DBUS message bus (automount removable devices)
dbus-launch --exit-with-session &
# Handle Hal events with Ivman (notification with desktopbox).
ivman &
# Start PCmanFM as daemon for Wallpaper and desktop icons.
pcmanfm -d &
# Start the Freedesktop panel standard menu.
lxpanel &
# Start Parcellite clipboard manager.
parcellite &
# Launch Xpad desktop notes utility.
#xpad &
# Desktop effects composer.
#xcompmgr -c -r 10 &
# Set a background image using hsetroot (depends on imlib2).
#hsetroot -fill /usr/share/images/slitaz-background.png &
# Background color with xsetroot.
#xsetroot -solid "#222222" &
# Screensaver
xautolock -time 10 -locker "xlock -nolock -mousemotion +enablesaver" &[/c]
Offline
OK, we're completely OT 
What I cannot understand is why my autostart is empty, but (i.e.) dbus, pcmanfm and lxpanel are launched at startup 
<edit>
There's no autostart file at all O_O
</edit>
Offline
What does ~/.config/openbox show you? Do you see a autostart.sh file?
Also, dbus, hal and slim is started by SliTaz at boot, while slim starts Openbox. Openbox however should start lxpanel and pcmanfm. So if they show, it means you must have some autostart script.
Offline
The only file in ~/.config/openbox is rc.xml.
I did search:
[c]find / -iname *.* -type f -exec grep --files-with-matches --fixed-strings pcmanfm[/c]
But find nothing.
I'll call an exorcist for this computer!
<edit>
I did an upgrade and at the reboot the desktop has magically appeared, but still without any autostart file O_o
Offline
@black dog @notte
I had similiar expiriences sometimes, mostly after adding a new user. So I had to start pcmanfm and suddenly the Desktop was there. Some times I had to start via the konsole ,,openbox-sessions &" the panel.
What about creating this file autostart.sh manually?
Offline
No problem in creating it, I am only wondering how things are being loaded
Offline
You and me both
Offline
Hi. I have replaced the 0.5.x build of pcmanfm with the so called pcmanfm2 (0.9.x build), and I have similar issues to those reported in the O.P. .
I don't see my USB stick in the left panel, and any of my Windows partitions, mounted or unmounted.
If I click the Trash icon, the "Operation not supported" popup appears; the same happens if I select My Computer from PCManFM menu.
Installing gnome-vfs didn't help at all.
I also had the issue with the desktop - it was not being managed, but I fixed that by replacing 'pcmanfm -d &' with 'pamanfm --desktop &' in autostart.sh .
Looking for solutions on the internet didn't reveal anything useful for Slitaz, the only relevant solutions were for Arch, as I recall.
Did anyone have any success with pcmanfm2 and can share some informations on how I can fix my issues ?
Offline
It's because our udev rules are non-existent. There are plans to create and implement them because we want to move away from using HAL completely.
Offline
Thanks for clearifying this, Trixar_za.
On the same note, are there any plans to package the new written from scratch PCManFM 1.0 ?
Offline
As Trixar_za said if we go thru [Start]->[Preferences]->[Auto started App] we'll get a window of stated applications with buttons Add|Configure|Exit. And click on [Configure] button opens [c]autostart.sh[/c] in Leafpad and Ctrl+O shows its location in [c]~/.config/openbox[/c].
But i'm confused as OpenBox wiki references to config files in [c]/etc/xdg/openbox[/c] and on my LiveUSB there's identical [c]autostart.sh[/c] in [c]/etc/xdg/openbox[/c]. If we modify any of those files which of them will be used in during SliTaz GUI startup? And does modifying default [c]autostart.sh[/c] in [c]/etc/xdg/openbox[/c] influence openbox autostart in Slitaz or it's simply ignored/overridden?
Also i'm looking if there's any manual/list of options for PCmanFM conf file located in [c][TazUSB]/tux/.config/pcmanfm/main[/c].
tux is default user files saved on USB (dont know if they're created with [c]tazusb gen-liveusb[/c] or on user logout. And how changing this files will affect user/all. If they're created on logout, then they in fact won't be included in next [c]tazusb writefs[/c] creation, aren't they? So where does real PCmanFM that will be included in [c]rootfs.gz[/c] reside?
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]