djemos wrote:about mount a usb stick.
insert a usb stick while on X. Then a window will appear saying "a removable media has plunged in". Clicking on OK, pcmanfm will mount and open the usb. Does this happen? What is the message appeared?
Look at /etc/polkit-1/rules.d/49-nopasswd_global.rules If the file exists.
Otherwise create it
Code: Select all
cat <<EOF >> "$RDIR/etc/polkit-1/rules.d/49-nopasswd_global.rules"
/* Allow members of the wheel group to execute any actions
...
EOF
Sorry, I should provide more information about this problem in the first place:
pcmanfm does see that a USB stick was inserted. However, when I try to mount it I get this message:
Code: Select all
Not authorized to perform operation (polkit authority not available and caller is not uid 0)
I can mount the USB if I run pcmanfm as root. The exact same things happen when using Worker (my favorite file manager). It clearly has to do with polkit. I tried to reinstall polkitd - no luck. Please note this happens with any user, including the first one, or new ones.
The file 49-nopasswd_global.rules was there already, and its contents is exactly the same as yours, except that "EOF" in the end is missing (apparently, an end-of-file signal). In a desperate attempt to fix the problem, I even tried to add that "EOF", and I would be surprised if it would work - It didn't.
djemos wrote:About exit. wm-logout has deps ConsoleKit2,dbus,python,upower.
Create a new user and try to log in and log out with this user. Also put user in wheel group so it will have root privileges.This is not done automatically at creation time since it is not the first user.
Maybe openbox settings file is broken. also try to reinstall wm-logout.
I tried all the above, and the problem persists.
All the dependencies for wm-logout were there, since I never touched them. I tried reinstalling wm-logout - problem persists. I tried to run wm-logout with the first user and new users, all members of the following groups:
Code: Select all
pap[~]$ groups
users lp wheel floppy audio video cdrom pulse plugdev power netdev polkitd scanner
No change - problem persists. It doesn't matter which user is trying to run wm-logout. It doesn't work for all of them. Please note that both my 32- and 64-bit Slackel systems were installed from scratch when version 7.2 was released, and everything worked flawlessly for quite some time. No change was made to the system by me since then, just the regular system updates.
My work on Slackel is mainly programming with gcc and Emacs, and secondary browsing the internet on trusty websites and with privacy measures. I don't mess with the system files. The only changes I did were completely harmless, namely I modified ~/.config/fbpanel/default and changed symlink /usr/share/icons/default to point to my favorite cursor theme (and those changes were made long before I started to have issues). The two problems started to appear after a slapt-get -u, slapt-get --upgrade, sometime ago (and that upgrade went normally as all other upgrades). In other words, the two problems I mention here happened all of a sudden and without me doing anything special.
djemos wrote:Also check your ~/.xinitrc file.
It has to be the same with /etc/X11/xinit/xinitrc which is a link to /etc/X11/xinit/xinitrc.openbox
.xinitrc was untouched by me, its content is the same as yours, and identical to /etc/X11/xinit/xinitrc.openbox:
Code: Select all
pap[~]$ diff ~/.xinitrc /etc/X11/xinit/xinitrc.openbox
(no output - files are identical)
Surprisingly, the symbolic link /etc/X11/xinit/xinitrc was broken (and I am sure I didn't touch it). I restored it to point to /etc/X11/xinit/xinitrc.openbox.
djemos wrote:There are new files added on slackware current and others have been dropped. Look at slackware current ChangeLog.txt search for ADD and see what files added and replaced.
Now, this is the most tricky part. The
changelog for 32-bit, for example, is huge, and I'm not sure how I can extract any useful information from it.
Since everything worked before, and I never did any change to the system myself other than normal updates, I am surprised I am the only one reporting this. It clearly happened after a system update, so I would expect most (if not all) Slackel users should be affected. The issues are not severe, so I kept doing my work for some time since I were busy. But even though they are not severe problems, they are still really annoying inconveniences, so I decided to do something to fix them. Judging from the error messages, my best bet is (a) the USB issue is related to a recent Slackware-Current change to polkit, and (b) the wm-logout issue is related to a change to DBus. Both are essential system components, and I never messed with them.