Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOL]Can't login using kdm, console login works - dbus error
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
kaTiezei
n00b
n00b


Joined: 10 Mar 2013
Posts: 24

PostPosted: Wed May 01, 2013 6:39 pm    Post subject: [SOL]Can't login using kdm, console login works - dbus error Reply with quote

Hello,

I can't login on kdm using a normal user account. I have already changed the keyboard layout to the right one and checked the signs that appear in the username field - this works now.
The login of this user works on the console. Since there is an error about the connection to dbus, I reinstalled dbus, but I still can't login on kdm.
What I do is I type the username and the password, but the password is highlighted red.
I also tried to find the file .dmrc since changing it helped somebody on the forum, but I didn't find the file.
If I try to start kdm from the console using the normal user it says that only root would want to start it, so I think it's in the PATH (FAQ).
consolekit is running, dbus as well.
This is my first gentoo setup, so it never worked before.

part of kdm.log :
Code:
Server terminated successfully (0). Closing log file.
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
klauncher(2165) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2159)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"

kdmgreet(2159)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
Server terminated successfully (0). Closing log file.



rc-update show:
Code:

  bootmisc | boot                         
           consolekit |      default                 
                 dbus |      default                 
                devfs |                       sysinit
                dmesg |                       sysinit
                fcron |      default                 
                 fsck | boot                         
             hostname | boot                         
              hwclock | boot                         
              keymaps | boot                         
            killprocs |              shutdown       
                local |      default                 
           localmount | boot                         
              metalog | boot                         
              modules | boot                         
             mount-ro |              shutdown       
                 mtab | boot                         
               net.lo | boot                         
            net.wlan0 | boot default                 
             netmount |      default                 
               procfs | boot                         
                 root | boot                         
            savecache |              shutdown       
                 swap | boot                         
            swapfiles | boot                         
               sysctl | boot                         
                sysfs |                       sysinit
         termencoding | boot                         
       tmpfiles.setup | boot                         
                 udev |                       sysinit
           udev-mount |                       sysinit
              urandom | boot                         
                  xdm |      default               



Xorg.0.log:
http://pastebin.com/dbB3mKQR


Last edited by kaTiezei on Sat May 04, 2013 1:50 pm; edited 1 time in total
Back to top
View user's profile Send private message
kaTiezei
n00b
n00b


Joined: 10 Mar 2013
Posts: 24

PostPosted: Fri May 03, 2013 4:59 pm    Post subject: Reply with quote

Maybe I found the reason, but not the solution. I ran python-updater, since it helped somebody else on the web with another problem in kdm (http://www.gossamer-threads.com/lists/gentoo/user/270796). Even if I execute python-updater a second and third time, it wants to repair these packages, including dev-util/gdbus-codegen:


Code:
*   Adding to list: dev-libs/boost:0
 *   Adding to list: dev-libs/libgamin:0
 *   Adding to list: dev-libs/libxml2:2
 *   Adding to list: dev-util/gdbus-codegen:0
 *   Adding to list: media-libs/lcms:0
 *   Adding to list: sys-apps/file:0
 *   Adding to list: sys-libs/cracklib:0
 * emerge -Dv1 --keep-going dev-libs/boost:0 dev-libs/libgamin:0 dev-libs/libxml2:2 dev-util/gdbus-codegen:0 media-libs/lcms:0 sys-apps/file:0 sys-libs/cracklib:0



And it emerges everything successfully. But the next time I run python-updater, it wants to repair it again. How do I come out of this?
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2160
Location: The Peanut Gallery

PostPosted: Fri May 03, 2013 11:12 pm    Post subject: Reply with quote

Ouch what a bummer to hit something like that on install. Don't be discouraged: I don't know this problem, but I know 900 people who do, all of whom will help you live (well they'll let 2 or 3 fix the problem with you;) Just use an IRC client like xchat from an Ubuntu or Knoppix live disk and connect to IRC chat.freenode.net (which I think is default in xchat and in Konversation.) Then type:
Code:
/join #gentoo
and hit Enter, and wait a few minutes so you get used to the channel. Another good place is #gentoo-chat which is not quite as busy, and where you can talk about whatever, as well as occasionally get some tips.

If you want you can
Code:
emerge irssi
in the running gentoo install and use irssi, a text based browser instead. I advise you to read the manpage however, and setup a minimal config (nickname etc.)
Back to top
View user's profile Send private message
kaTiezei
n00b
n00b


Joined: 10 Mar 2013
Posts: 24

PostPosted: Sat May 04, 2013 1:47 pm    Post subject: Reply with quote

Thank you for your empathy, steveL!

I think I have found the solution. Leaving this dbus thing unrepaired, I created a new user with a very easy password and could login. I changed the password of the first one to an easier one and could log in. I also changed the password of the newly created account to the password that didn't work and it doesn't work with that account, either. It had some special characters in it.
In the username field I checked again whether the right special characters appear: yes.

Now I found a another one, again including a special character and this works; I can login.
So it seems you can't use every password with kdm.
Back to top
View user's profile Send private message
critikaster
n00b
n00b


Joined: 12 Feb 2014
Posts: 6

PostPosted: Wed Feb 12, 2014 7:40 pm    Post subject: Reply with quote

kaTiezei wrote:
So it seems you can't use every password with kdm.


Confirmed.

Quote:
xdm/kdm will refuse any login attempts if the user has a weak password.


From:
https://forums.gentoo.org/viewtopic-p-7499190.html#7499190
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum