LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-15-2013, 02:18 PM   #1
ssslackw
Member
 
Registered: Aug 2005
Posts: 61

Rep: Reputation: 2
Cool Login Problem


Hi,
I have a login problem for all users. I installed 14.0 recently. Not only did the screen freeze so many times, but now all users can not login:

"A critical error is occurred. Please looks at KDM's logfile(s) for more
information or contact your system administrator."

1. Where is the KDM's logfile(s)?
2. How can I fix it?

Thanks for your help in advance.

Best,
 
Old 07-15-2013, 02:30 PM   #2
itsgregman
Member
 
Registered: Jan 2008
Location: North Carolina
Distribution: Slackware 14.1
Posts: 211

Rep: Reputation: 77
KDM log file is in /var/log, there may also bo something useful in /var/log/syslog, post the contents.

Last edited by itsgregman; 07-15-2013 at 02:36 PM.
 
Old 07-15-2013, 02:36 PM   #3
ssslackw
Member
 
Registered: Aug 2005
Posts: 61

Original Poster
Rep: Reputation: 2
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.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x49) [0x81b54b9]
1: /usr/bin/X (mieqEnqueue+0x22b) [0x819400b]
2: /usr/bin/X (0x8048000+0x44a05) [0x808ca05]
3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0x80c64ab]
4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb5fae000+0x3d1d) [0xb5fb1d1d]
5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb5fae000+0x53c6) [0xb5fb33c6]
6: /usr/bin/X (0x8048000+0x6dd11) [0x80b5d11]
7: /usr/bin/X (0x8048000+0x9355a) [0x80db55a]
8: linux-gate.so.1 (__kernel_sigreturn+0x0) [0xffffe400]
9: /lib/libc.so.6 (ioctl+0x14) [0xb73eed24]
10: /usr/lib/libdrm.so.2 (drmIoctl+0x34) [0xb720aa74]
11: /usr/lib/libdrm.so.2 (drmCommandWrite+0x3c) [0xb720d63c]
12: /usr/lib/libdrm_nouveau.so.1 (0xb7233000+0x2d6f) [0xb7235d6f]
13: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0x11e) [0xb723647e]
14: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map+0x32) [0xb7236562]
15: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0xb71d3000+0x442f) [0xb71d742f]
16: /usr/lib/xorg/modules/libexa.so (0xb7215000+0x884a) [0xb721d84a]
17: /usr/bin/X (0x8048000+0xfa254) [0x8142254]
18: /usr/bin/X (0x8048000+0x2c25f) [0x807425f]
19: /usr/bin/X (0x8048000+0x2fad5) [0x8077ad5]
20: /usr/bin/X (0x8048000+0x1d765) [0x8065765]
21: /lib/libc.so.6 (__libc_start_main+0xf5) [0xb732a5a5]
22: /usr/bin/X (0x8048000+0x1daa9) [0x8065aa9]

[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.


I hope it helps.

Best
 
Old 07-15-2013, 03:31 PM   #4
itsgregman
Member
 
Registered: Jan 2008
Location: North Carolina
Distribution: Slackware 14.1
Posts: 211

Rep: Reputation: 77
Have you tried logging in to another desktop like Fluxbox to see if it would load?

If neither work you could try whats suggested here

http://slackware.com/config/x.php

You could even try the vesa driver to see if the noueau driver is causing the issue.

Last edited by itsgregman; 07-15-2013 at 03:35 PM.
 
Old 07-15-2013, 03:34 PM   #5
ssslackw
Member
 
Registered: Aug 2005
Posts: 61

Original Poster
Rep: Reputation: 2
These are lines from syslog:
Jul 15 09:59:44 nmr last message repeated 3 times
Jul 15 09:59:47 nmr hp-systray: hp-systray[2034]: warning: hp-systray should not be run as root/superuser.
Jul 15 09:59:47 nmr hp-systray: hp-systray[2034]: error: hp-systray cannot be run as root. Exiting.
Jul 15 10:04:07 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:04:07 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:04:10 nmr kdm_greet[2091]: Cannot load /usr/share/apps/kdm/faces/.default.face.icon: Permission denied
Jul 15 10:04:24 nmr kdm: :0 '[2109]: Session "/usr/share/config/kdm/Xsession" execution failed: Permission denied
Jul 15 10:04:24 nmr kdm: :0 '[2109]: Failsafe client "/usr/bin/xterm" execution failed: Permission denied
Jul 15 10:04:33 nmr kdm_greet[2123]: Cannot load /usr/share/apps/kdm/faces/.default.face.icon: Permission denied
Jul 15 10:05:22 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:05:22 nmr last message repeated 3 times
Jul 15 10:05:23 nmr hp-systray: hp-systray[2207]: warning: hp-systray should not be run as root/superuser.
Jul 15 10:05:23 nmr hp-systray: hp-systray[2207]: error: hp-systray cannot be run as root. Exiting.
Jul 15 10:08:38 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:08:38 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:08:41 nmr kdm_greet[2381]: Cannot load /usr/share/apps/kdm/faces/.default.face.icon: Permission denied
Jul 15 10:08:54 nmr kdm: :0 '[2399]: Session "/usr/share/config/kdm/Xsession" execution failed: Permission denied
Jul 15 10:08:54 nmr kdm: :0 '[2399]: Failsafe client "/usr/bin/xterm" execution failed: Permission denied
Jul 15 10:09:01 nmr kdm_greet[2413]: Cannot load /usr/share/apps/kdm/faces/.default.face.icon: Permission denied
Jul 15 10:09:55 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:09:55 nmr last message repeated 3 times
Jul 15 10:09:56 nmr hp-systray: hp-systray[2497]: warning: hp-systray should not be run as root/superuser.
Jul 15 10:09:56 nmr hp-systray: hp-systray[2497]: error: hp-systray cannot be run as root. Exiting.
Jul 15 10:12:53 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:12:53 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 10:12:57 nmr kdm_greet[2712]: Cannot load /usr/share/apps/kdm/faces/.default.face.icon: Permission denied
Jul 15 10:13:11 nmr kdm: :0 '[2730]: Session "/usr/share/config/kdm/Xsession" execution failed: Permission denied
Jul 15 10:13:11 nmr kdm: :0 '[2730]: Failsafe client "/usr/bin/xterm" execution failed: Permission denied
Jul 15 10:13:29 nmr kdm_greet[2744]: Cannot load /usr/share/apps/kdm/faces/.default.face.icon: Permission denied
Jul 15 11:35:46 nmr kdm: :0 '[2769]: Session "/usr/share/config/kdm/Xsession" execution failed: Permission denied
Jul 15 11:35:46 nmr kdm: :0 '[2769]: Failsafe client "/usr/bin/xterm" execution failed: Permission denied
Jul 15 11:36:32 nmr kdm_greet[2784]: Cannot load /usr/share/apps/kdm/faces/.default.face.icon: Permission denied
Jul 15 11:36:43 nmr console-kit-daemon[1796]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Jul 15 11:36:44 nmr last message repeated 3 times
Jul 15 11:36:45 nmr hp-systray: hp-systray[2868]: warning: hp-systray should not be run as root/superuser.
Jul 15 11:36:45 nmr hp-systray: hp-systray[2868]: error: hp-systray cannot be run as root. Exiting.
 
Old 07-15-2013, 04:06 PM   #6
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,499

Rep: Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452Reputation: 8452
Bad filesystem permissions, somehow? You might try: chmod 755 /
 
Old 07-15-2013, 04:09 PM   #7
itsgregman
Member
 
Registered: Jan 2008
Location: North Carolina
Distribution: Slackware 14.1
Posts: 211

Rep: Reputation: 77
I just had a thought, you said you recently installed Slackware 14 and have experienced freezes and such since.

What was installed before? Did you try and upgrade from an earlier version of Slackware or replace another distro?

Also If you had a different distro before did you format your home partition as well as your root partition during the install?
 
Old 07-15-2013, 04:16 PM   #8
ssslackw
Member
 
Registered: Aug 2005
Posts: 61

Original Poster
Rep: Reputation: 2
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.

I will try chmod 755 /

Thanks for the suggestions.
 
Old 07-15-2013, 04:22 PM   #9
itsgregman
Member
 
Registered: Jan 2008
Location: North Carolina
Distribution: Slackware 14.1
Posts: 211

Rep: Reputation: 77
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.
 
Old 07-15-2013, 04:38 PM   #10
ssslackw
Member
 
Registered: Aug 2005
Posts: 61

Original Poster
Rep: Reputation: 2
I have deleted all the stuff in .config directory and tried chmod 755 /, but still does not work.
 
Old 07-15-2013, 04:50 PM   #11
itsgregman
Member
 
Registered: Jan 2008
Location: North Carolina
Distribution: Slackware 14.1
Posts: 211

Rep: Reputation: 77
run as root rm -Rf /home/"user"/.*

Replacing "user" with the name of your user.

Or if you'd rather in gui as root simply delete all directories and files in /home/"user"/ that have a . in front of them.

Last edited by itsgregman; 07-15-2013 at 04:52 PM.
 
Old 07-15-2013, 05:10 PM   #12
ssslackw
Member
 
Registered: Aug 2005
Posts: 61

Original Poster
Rep: Reputation: 2
I have deleted all the .* files, and could not login.
Well, I am going to reinstall the software.
 
Old 07-15-2013, 05:10 PM   #13
Z038
Member
 
Registered: Jan 2006
Location: Dallas
Distribution: Slackware
Posts: 910

Rep: Reputation: 174Reputation: 174
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.
 
Old 07-15-2013, 05:15 PM   #14
ssslackw
Member
 
Registered: Aug 2005
Posts: 61

Original Poster
Rep: Reputation: 2
Yes, I did a full install at the first time. Thanks for all your helps.

Best,
 
Old 07-15-2013, 05:21 PM   #15
itsgregman
Member
 
Registered: Jan 2008
Location: North Carolina
Distribution: Slackware 14.1
Posts: 211

Rep: Reputation: 77
Sorry we weren't more helpful.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with remote login (login from another machine) mamidi Linux - Newbie 5 07-20-2011 06:13 PM
[SOLVED] SSH login problem for additional users after password-less login setup uncle-c Linux - Newbie 3 02-10-2010 12:51 PM
SSH Problem - Can't login using Hostname, can login using ip address jqweezy Linux - Networking 7 01-26-2009 02:21 PM
login problem tulip4heaven Linux - Newbie 4 03-29-2005 09:57 PM
Login problem with RH 7.1 bildnisse Linux - Newbie 2 01-01-2002 10:05 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:47 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration