Bug 144646 - Cannot login via xdm after update to 10.1
Summary: Cannot login via xdm after update to 10.1
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Beta 1
Hardware: i386 SuSE Linux 10.0
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-22 10:58 UTC by Gerd Bavendiek
Modified: 2006-01-23 10:08 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerd Bavendiek 2006-01-22 10:58:10 UTC
I just updated my testpartition from 10.0 to 10.1. Now I'm no longer able to login via xdm. Basically I get this in my .xsession-errors:

lulu:/newroot/root>>> cat .xsession-errors.1st 
/etc/X11/xim: Checking wether an input method should be started.
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US ...
There is no default input method for the current locale.

After I searched around I put
lulu:/newroot/etc/sysconfig>>> grep INPUT language 
INPUT_METHOD="none"

and got this:

lulu:/newroot/root>>> cat .xsession-errors
/etc/X11/xim: Checking wether an input method should be started.
INPUT_METHOD is set to none.
Trying  to start this user selected input method first ...
sourcing /etc/X11/xim.d/none
Dummy input method "none" (do not use any input method at all by default)
Start of none succeeded.

Still not able to log in. xdm login screen simply pops up again.

Just to make the picture complete: During installation I hit an issue that I described in BugId # 144645.

Kind regards

Gerd
Comment 1 Stefan Dirsch 2006-01-22 19:06:27 UTC
Does using "startx" work?
Comment 2 Gerd Bavendiek 2006-01-23 08:15:33 UTC
Yes, it does. I just bootet 10.1 to verify this.

And I happened to find a little bit more info which may be helpful:

The described error only happens if there is a .xsession looking like this:

/root# cat .xsession
###exec startxfce4

Before the update I used xfce4. Due to unsolved dependencies I had to agree to remove these packages when starting the upgrade. So my old .xsession no longer made sense.

So I commented out the line.

Obviously this triggered the bug.
Comment 3 Stefan Dirsch 2006-01-23 08:45:23 UTC
Ok. I propose to rename all your existing .xsession/.xinitrc files for now. This should fix the xdm setup. Then diff your .xsession/.xinitrc files with 
/etc/X11/xinit/xinitrc to see what you wanted to make different. Then copy /etc/X11/xinit/xinitrc to $HOME/.xsession and adjust it to your needs.
Let me know, whether this helps. Thanks.
Comment 4 Gerd Bavendiek 2006-01-23 09:45:32 UTC
Oops, seems a major user brain bug ...
I changed my .xinitrc to read

exec twm

and all is fine. 

I was confused by

/etc/X11/xim: Checking wether an input method should be started.
INPUT_METHOD is set to none.
Trying  to start this user selected input method first ...
sourcing /etc/X11/xim.d/none
Dummy input method "none" (do not use any input method at all by default)
Start of none succeeded.

which I still do not understand.

Anyway, my apologies for my real dumb bug report. 
Comment 5 Stefan Dirsch 2006-01-23 10:08:27 UTC
You're complaining about a informational message. It's not even a warning ...
Closing as INVALID.