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.
Once more I verified the md5sum to be correct.
I see the problem with VirtualBox as well as booted from a dd'ed-to USB stick, so no persistence and the like.
As I use english/USA as language and keyboard I tested with français as language and keyboard: problem persists.
I then found that the problem only occurs when logged-in as root, when logged-in as live things are ok.
I could not find something obvious in the log files.
I am pretty sure that with previous mate live CD's the problem did not occur. Alas I do not have a previous live CD any more, so I cannot verify ...
Booting the live CD to runlevel 3, logging in as root, executing xdg-user-dirs-update and then issuing startx did not have any discernable effect.
On my Slack64 Current XFCE + some Mate (caja etc) I downloaded the whole of slackware.uk/msb/current/1.17/x86_64/{deps,base,extra} and ran "upgradepkg --reinstall install-new" for the .txz files. Running "xinit /etc/X11/xinit/xinitrc.mate-session" for root and burdi01 shows the same symptoms.
I attached the resultant /var/log/messages file (which contains all logging done; just remove the .txt extension) -- I see some warnings but no relevant (to me) failures ...
You realize that it is not recommended to run an X session as root? There is no guarantee that things work like they are supposed to work when you login as a normal user.
This does not only count for Gnome but also for KDE desktop environments
You realize that it is not recommended to run an X session as root?
Dear Eric,
I was expecting someone to come up with that argument ...
I think that whether or not running an X session as root should be frowned upon should warrant a separate discussion -- something along the lines of running a single user workstation versus a multiuser server ...
Kind regards, Dick (burdi01, aka DLCBurggraaff)
Dear Eric,
I was expecting someone to come up with that argument ...
I think that whether or not running an X session as root should be frowned upon should warrant a separate discussion -- something along the lines of running a single user workstation versus a multiuser server ...
Kind regards, Dick (burdi01, aka DLCBurggraaff)
You got the meaning of my comment wrong. Just because it is not advised to run X as root, this scenario will not be among the test cases when developing software like Gnome or KDE, and if things break for root user, there will not be any incentive to fix the issue.
Your issue with missing icons is most likely a functional bug, but will it ever be solved? Probably not.
... was a bad idea to run as root... It must be avoided
Dear Willy:
For a single-user workstation system type (as opposed to a multi-user server one) I respectfully disagree.
Anyway, I rest my case.
Regards, Dick
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.