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.
I had the same problem with /dev/shm as Andersen wrote: permissions, strange date (my version: Slackware -current, kernel 4.4.3). In my case the problem disappeared after removing the obsolete udev package. I forgot to do it during upgrade. Maybe this could explain also the case mentioned earlier in this thread by Pat.
I had the same problem with /dev/shm as Andersen wrote: permissions, strange date (my version: Slackware -current, kernel 4.4.3). In my case the problem disappeared after removing the obsolete udev package. I forgot to do it during upgrade. Maybe this could explain also the case mentioned earlier in this thread by Pat.
Thanks lecho! I can confirm that was the case here, I forgot to remove old udev package . Problem solved, thank you guys!
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Rep:
FWIW, I don't remember seeing anything about removing udev, but maybe I just didn't know where to look? Manually removing udev fixed quite a few problems I was experiencing. Chrome works, Steam works, and I'm about to have a go at the current nVidia driver because up to now I'm still using 352.63 because 361.28 was causing weird problems.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,640
Rep:
Quote:
Originally Posted by Ook
FWIW, I don't remember seeing anything about removing udev, but maybe I just didn't know where to look? Manually removing udev fixed quite a few problems I was experiencing. Chrome works, Steam works, and I'm about to have a go at the current nVidia driver because up to now I'm still using 352.63 because 361.28 was causing weird problems.
For Slackware current you have to look in the official ChangeLog, see the entry from 20th November 2015
Once it becomes stable you should find this info in the CHANGES_AND_HINTS.TXT on the DVD or in the root folder of any Slackware mirror.
FWIW, I don't remember seeing anything about removing udev, but maybe I just didn't know where to look? Manually removing udev fixed quite a few problems I was experiencing. Chrome works, Steam works, and I'm about to have a go at the current nVidia driver because up to now I'm still using 352.63 because 361.28 was causing weird problems.
Well, because in reality udev wasn't removed per se, it was replaced with eudev.
Code:
Fri Nov 20 05:25:18 UTC 2015
(...)
a/eudev-3.1.5-x86_64-3.txz: Added.
This replaces the udev package.
(...)
a/udev-182-x86_64-7.txz: Removed.
This is replaced by the eudev and libgudev packages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.