I use udiskie and udisks for auto-mounting devices in Fluxbox. It however stopped working on one laptop, while still works with exactly same configurations on other. Both machines run up-to-date current, only difference is one run 32 bit slackware, other 64 bit. On 64 bit slack (with multilib) it works fine, on 32 bit this error occurs:

I set PolicyKit permission according to udiskie readme in /etc/polkit-1/localauthority/50-local.d/10-udiskie.pkla and change group to plugdev (designated group in slackware) so it look like this:
Although my user is in plugdev group, udisks and udiskie still fails to mount any device.

Hi

sorry for not being a slacker

can you install udisks-glue?

I am 32 bit, don't have your polkit file but use pcmanfm and kernel polling with udisks

I assume you have checked your config file for whatever file manager you are using
a number of them, define if auto mounting is to be used or not

good luck

otherwise you might like post 9

https://bbs.archlinux.org/viewtopic....908792#p908792

Thanks for suggestions, although I don't think they will help in this case.

Actually, problem lies in PolicyKit itself. I can't tell what went wrong and when, but permissions for this particular user are now completely broken. Now I also can't suspend/hibernate as regular user anymore.

I'll try to create new user to see what's changed (if anything) and report back.

Unfortunately it didn't work even with new user. It seems to be similar problem like http://www.linuxquestions.org/questi...el-4175469935/.
I didn't tried these solutions (sudo, fine-grain tweaking with polkit configuration), because I don't think these changes should be necessary. I'm still puzzled, how it is possible that exactly same configuration sometimes works and sometimes don't.

I'm going to reinstall slack and see if there really is bug in 32 bit version or it's just some another broken package, which broke ConsoleKit (and it's friends). I know it might not be the best solution, but I was going to do clean install of Slackware anyway.

then grab system rescue cd and take an image using fsarchiver

I have a system partition and a swap and a data.....all primary traditional bios .....no GPT/UEFI stuff

after image created burn it to a dvdrw

total data for me is around 3g

I don't put any data into home

data is a separate entry in fstab and I move all stuff out of home to there
and it has its own backup.....simple copy to dvdrw or usb stick

good luck

back on theme

your link links to a arch post

notice they are talking about startx issues due to WM/DE and using .xinitrc

I have seen reference to this before.....

then pls look at your login manager as well in case you don't use .xinitrc

I use lightdm

Hello again, I'm typing this from fresh installation of Slackware

Strangely enough these problems are gone and I'll probably never know what caused them in first place. So I'm marking this thread as solved.

And about reinstalling. With separate /home and all important data outside root fs (on NFS server) it was almost no-brainer. Well, almost, LUKS encrypted LVM is quite complex beast and it took me only three reboots & chrooting to get initrd and LILO config right :-)

I use SLiM, which basically launch .xinitrc, which in turn start Fluxbox within ConsoleKit session. As long as everything starts in same CK session, permissions should be ok. So far, with exception of this hiccup, everything works like a charm.

Once again... when i switch runlevel to 4 and logged in via SLiM, udiskie suddenly stopped working. But if I started Xorg from console, it worked fine.

So bug is actually regression in SLiM itself (I just have to find out where and write bugreport), First I upgraded SLiM to latest version (1.3.6) and things went south. I just reverted to previous "stable" version from SlackBuilds and it works again!

Well, I didn't had to reinstall whole system, but on the other hand now I got rid of many unused packages which I forgot about during last few years, so it was worth it.