SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Upgraded my current to the default changelog. Noticed any attached
usb thumbdrives or my Sansa Fuze no longer automount. Went into systemsettings and chose the appropriate choices under removeable devices. Anyone else experience anything of the sort? Of course we are talking the -current KDE 4.8.2.
Yes, rebooted to no avail but didn't try mounting manually as it was late & I needed to get to sleep.
Going to try deleting & re-adding my user and groups tonight when I get back from work..perhaps
that will clear things up.
Hmmmm...can't quite figure this one out. Dmesg offers no red flags. However upon bootup it appears I might have a problem with udev. Get a line to the effect of udevadmin trigger --type failed. This one is going to be fun to unravel.
I had similar problems with recent kde versions from AlienBob. For me polkit-1 default settings seem to be the cause.
I think there may be a bug in the SystemSettings Actions Policy, whereby changes are not registered, as changes made there don't seem to stick.
After some investigation I found that manually editing /usr/share/polkit-1/actions/org.freedesktop.udisks.policy (I think it was filesystem-mount) change to allow any=YES restored the previous behavior.
I had similar issues with mounting luks volumes.
I have since upgraded to 'official' current without any problems
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.