I have no more removable devices, other partitions and trash in pcmanfm. I have gvfs and udisk2 installed, I guess I edited something...
[slitaz 5.0 RC2]
I have no more removable devices, other partitions and trash in pcmanfm. I have gvfs and udisk2 installed, I guess I edited something...
[slitaz 5.0 RC2]
maybe the pcmanfm configuration?
Hi brainlessmutant,
I rarely use USB Flash. A few days ago I noticed that PCManFM had stopped to mount USB sticks. I thought that this behavior is inherent only my system. Seems that it is not.
Please, execute next commands and post output here:
grep -e "UDisks2.*failed" /var/log/daemon.log
I get many lines and the last is:
Sep 16 03:34:29 (none) daemon.notice dbus[1232]: [system] Activated service 'org.
freedesktop.UDisks2' failed: Failed to execute program /usr/lib/dbus/dbus-daemon-
launch-helper: Success
And please, post output of this command:
ls -l /usr/lib/dbus/dbus-daemon-launch-helper
Seems it is a permissions issue. What permissions comes from package?
http://cook.slitaz.org/cooker.cgi?files=dbus-helper
-rwsr-x--- 1 root 25 356042 Aug 5 14:03 /usr/lib/dbus/dbus-daemon-launch-helper
And how to make this permissions and ownersheep we can read in the receipt:
http://cook.slitaz.org/cooker.cgi?receipt=dbus-helper
chown root.25 /usr/lib/dbus/dbus-daemon-launch-helper
chmod 4750 /usr/lib/dbus/dbus-daemon-launch-helper
Before reading this I set ownersheep to root:root and permissions to rwsr-xr-x, and it worked (after reboot), but it is not right. Finally I set permissions and ownersheep like it described in the receipt.
Now it works for me, fine! But it is interesting what the permissions was set to this file when it was broken?
PS. Strange. I reinstall package. And everithing is already here.
tazpkg -gi dbus-helper --forced
ls -l /usr/lib/dbus/dbus-daemon-launch-helper
-rwsr-x--- 1 root messagebus 356042 Aug 5 15:03 /usr/lib/dbus/dbus-daemon-launch-helper
Hi guys,
@ kultex :
do you talk about some file(s) in /etc/ ? if yes I didn't edited anything there.
@ Aleksej :
it's not only my usb devices, also all other partitions on my hard disk. Anyway, I tried what you suggest :
# grep -e "UDisks2.*failed" /var/log/daemon.log
« returns nothing »
#ls -l /usr/lib/dbus/dbus-daemon-launch-helper
-rwsr-x--- 1 root messageb 356042 Aug 5 08:03 /usr/lib/dbus/dbus-daemon-launch-helper
I reinstalled dbus-helper->reboot->still no devices
I exectuted :
chown root.25 /usr/lib/dbus/dbus-daemon-launch-helper
chmod 4750 /usr/lib/dbus/dbus-daemon-launch-helper
reboot->still no devices
actualy yesterday I uninstalled some packages some wich belong to lx* (lxde) and openbox. I had to change something after that because slim failed to execute jwm. My guess is, there is something related to the trash and devices who is started when lxde is started that I don't start when I start jwm. I will try to figure what with my slitaz-eeepc
Now I just want to notice something about tazweb, I like it, I use it a lot, but sometime it fails very badly to render some webpages, here I have a good example. your link :
http://cook.slitaz.org/cooker.cgi?receipt=dbus-helper
show me :
as you can see, there is no text between the brackets "{ }", and if i COPY+PASTE :
genpkg_rules()
{
mkdir -p $fs/usr/lib
cp -a $install/usr/lib/dbus $fs/usr/lib
chown root.25 $fs/usr/lib/dbus/dbus-daemon-launch-helper
chmod 4750 $fs/usr/lib/dbus/dbus-daemon-launch-helper
}
still nothing. With firefox I have no problem.
EDIT :: that's weird!! I can read the text in my post, but not in edit mode, and look what happen when I select some text :
I guess there is some black-magic-char
ok it's definitely related to lxde-session/openbox
if I edit /usr/bin/lxde-session :
1) comment the last line
2) adding at the end of the file : exec jwm
then I got the trash and devices (usb too) in pcmanfm. It would be great if this could work without having openbox , lxpanel etc. installed. I don't know if it's possible but I would like to know that, I mean is it necesseray to have lxde installed ?
Hi brainlessmutant,
Here lxde-session script for reference: http://cook.slitaz.org/cooker.cgi?stuff=lxde/stuff/lxde-session
All the magic in the dbus-launch command. I think you can copy these lines to your script which launches jwm. And you need no LXDE nor PCManFM itself.
Few words about «invisible ink» in the TazWeb.
Yes, it's weird. And you can see some similar lines in the TazPanel too (default web browser for TazPanel is TazWeb) when you install packages. As far as I remember it's partially invisible lines with bold font.
But...
It is only on a fresh SliTaz installation. And all gone when I customize my SliTaz (install locale, few fonts, few apps, etc.) Not sure, maybe we miss something?
I am running all my slitaz frugal - this I get after tazlito writeiso in boot.log with current rolling (I did not have this problem with my iso from last year)
tux@slitaz:~$ uname -a
Linux slitaz 3.2.53-slitaz #4 SMP Tue May 13 21:58:01 CEST 2014 i586 GNU/Linux
tux@slitaz:~$ cat /var/log/boot.log | grep dbus
Starting message bus daemon: DBUS... Failed to start message bus: The pid file "/var/run/dbus/pid" exists, if the message bus is not running, remove this file
tux@slitaz:~$ pidof dbus
tux@slitaz:~$
maybe it helps....
EDIT: I forgot to say, that in justX there is no dbus-daemon-launch-helper installed - only dbus
@kultex
> Linux slitaz 3.2.53-slitaz #4 SMP Tue May 13
This is RC1 or RC2, not rolling.
root@slitaz:~$ uname -a
Linux slitaz 3.2.53-slitaz #4 SMP Tue Aug 19
With rolling dbus-pid was fixed. in tazlito 5.2.4
Always check for updates before.
strange - I always update before I start working and I started 2 weeks ago.... I cannot say from when the iso was, because I updated my SliTaz CD yesterday...
but who knows, which rolling they are using?
You must log in to post.