Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
I think I almost installed xubuntu for the 10th time and I'm fed up. The problem is that cant login to xfce. I thought I had solved it by configuring the auto login but no. I have the login window, I enter the password, and then, it seems to proceed to the desktop but after a while, it gives again the login window and so on.
The last time, thanks to auto login, I could use it for 3 or 4 times (3/4 reboots) but at the last one (although I didn't modify any parameter), it didn't login automatically and I can't use it anymore. Sometimes, I could succeed by login as a terminal and making different operations I can't even remember. Now, I can't even get a term login.
ok, I removed $HOME/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml and could login. But when I modified th screen resolution (as I have an LCD screen connected to the eeepc), the file went back. When I reboot, I still have the problem but I found an easy way to bypass it (which is very simple indeed and documented in the link above) : I unplugg the screen and no problem to login ...
I'm still in problems with login. I still have to unplug and replug my external monitor each time I boot xubuntu. Anyone knows if there is a patch or update for this problem ? Is there a way to bypass it ? I tried with a script that deletes the diplays.xml file but I didn't manage to make it work. Anyone has a bypass trick ?
Hi, could you please describe your problem with more details?
I understand that you can login after unplugging/plugging the monitor. So this means, that the screenresolution is not adequate set, or not automatically adapted respectively. And therefore the loginfield of the screen is not visible, but while plugging the monitor in it resets it detects the proper resolution, is this correct?
Do you use an /etc/X11/xorg.conf file? if yes, look at the screenresolution in that file.
Well, not exactly.
I configured xubuntu in automatic login. When everything was right, I powered up my eeepc, on which is connected a monitor, and I got the desktop without any other action.
With resolution set to 1280x1024 with my external monitor, when I boot, I get the graphical login screen (which is unattended), I then enter my login name and password. After a while, I get the login screen again and so on and I can never login. No error message. Found nothing in the logs.
I was given one solution to bypass : go to console prompt with Ctrl+Alt+F1, login and delete $HOME/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml, logout and back to the graphical login screen and login.
This solution is way too long to boot up.
I found two solutions by myself :
1 . Unplug the external monitor to boot, then, at the desktop screen, replug it and change the resolution.
2 . Yesterday, I tried another one that works : before shutdown, switch back to 640x480 (which is the max resolution of eeepc screen). When I boot up, at the desktop screen, I get back to 1280x1024. This way, I don't need any plug/unpug action.
Of course, I have no problem without external monitor.
I had this issue once, it is afaik a permissionproblem anywhere in the configuration.
Actually I did not solve it but changed the loginmanager from xdm to gdm. I'd recommend to check if you're using xdm, if you can use gdm (of Gnome) or kdm (of KDE) instead, maybe that would be a solution.
If you want to examine the problem in more depth, I'd recommend to explore the /var/log/Xorg.0.log logfile.