|
Bugzilla – Full Text Bug Listing |
| Summary: | Cannot login via xdm after update to 10.1 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Gerd Bavendiek <gerd.bavendiek> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED INVALID | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | gerd.bavendiek |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Gerd Bavendiek
2006-01-22 10:58:10 UTC
Does using "startx" work? 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. 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. 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. You're complaining about a informational message. It's not even a warning ... Closing as INVALID. |