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.
Thanks for the reply. The file is large so I only copy the first "few" lines:
********************************************************************************
Note that your system uses syslog. All of kdm's internally generated messages
(i.e., not from libraries and external programs/scripts it uses) go to the
daemon.* syslog facility; check your syslog configuration to find out to which
file(s) it is logged.
********************************************************************************
resize called 1680 1050
klauncher(1925) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(1919)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
kdmgreet(1919)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
[mi] EQ overflowing. Additional events will be discarded until existing events are processed.
[mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
[mi] mieq is *NOT* the cause. It is a victim.
[mi] EQ overflow continuing. 100 events have been dropped.
The previous version of 13.1 and was installed few years ago.
I reinstalled everything. The previous version did not have any screen freeze problem.
I have tried to use startx in one of my user account, and it could not start anything.
The root does not have any problem, but all the user accounts have the same problem.
If the chmod command doesn't work just remove all config files from your users directories. It sounds like a damaged or conflicting config file/files there may possibly be your culprit.
I asked about formatting because sometimes when people keep their old home partition for a new install they end up with problems like the permission issue you have. I've only heard of it when people install a different distro but it can't hurt to remove the old config files as when you reboot into that user the system will create new ones for you.
Last edited by itsgregman; 07-15-2013 at 04:30 PM.
So you did a full install of 14.0? Did you retain any partitions from your previous system? I had some odd dbus messages from KDM at first too, but I don't recall now what I did to resolve them. I think I may have renamed the .kde folder in my home directory and let it create a new one, then merged in stuff I wanted to keep, like Kjots, Kalendar, and Kontact data.
You might consider just doing another full install, paying careful attention to the instructions in the Slackware-HOWTO file that is on the DVD / first CD.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.