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.
gparted_polkit works here, and I see no such errors in the logs or the starting console.
I'll see what rworkman has to say about this, but it strikes me as a risky update.
Ok, It seems the login manager is the culprit. I switched to Xdm and downgraded consolekit and the error is gone.
Since the update seems risky and it works on a stock install, I guess its fine with 1.0.0. Although i havn't seen any problems with the new version.
Just a small touch. Could get-xf86-video-intel.sh produce tarball that contains commit date as opposed to packaging date? Patch attached. This could also be applied to other getters.
BTW, updating intel driver to head at b6917ec solved graphical issues I had in eagle. I still have artifacts in scilab, though (screen shot attached). As per this thread it's a bit of hit and miss with intel driver, but it's strange that some applications behave well and others not.
On behalf of Philippe Delavalade who tested the new version with a Braille display connected through USB (compiled for Slackware64-14.1 but this doesn't matter), I confirm that it works:
Brltty is started as soon as udev sees the device.
The display is correct using a Terminus font.
Thanks.
Last edited by Didier Spaier; 04-10-2016 at 01:02 PM.
Don't you have to amend the kernel command line to add the resume flag?
I'm pretty sure (based on reading another topic that spurred this request) that you would have to reference the actual device location (/dev/disk/by-uuid/$UUID) instead of just UUID=$UUID.
I'm pretty sure (based on reading another topic that spurred this request) that you would have to reference the actual device location (/dev/disk/by-uuid/$UUID) instead of just UUID=$UUID.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.