You are not logged in.
Hi all,
Just did pacman -Syu and now I can't use slim to login anymore. I searched the forum but I didn't see any other complaints with X and upgrades, lately.
This is the end of my pacman.log
[2010-08-26 08:33] synchronizing package lists
[2010-08-26 08:34] starting full system upgrade
[2010-08-26 08:34] upgraded bison (2.4.2-1 -> 2.4.3-1)
[2010-08-26 08:34] upgraded evince (2.30.3-1 -> 2.30.3-2)
[2010-08-26 08:34] upgraded glproto (1.4.11-2 -> 1.4.12-1)
[2010-08-26 08:34] upgraded kbproto (1.0.4-1 -> 1.0.5-1)
[2010-08-26 08:34] upgraded libfetch (2.32-1 -> 2.33-1)
[2010-08-26 08:34] upgraded libxau (1.0.5-1 -> 1.0.6-1)
[2010-08-26 08:34] upgraded libxcb (1.6-1 -> 1.7-1)
[2010-08-26 08:34] upgraded libx11 (1.3.4-1 -> 1.3.5-1)
[2010-08-26 08:34] upgraded libxi (1.3-2 -> 1.3.2-1)
[2010-08-26 08:34] upgraded mlocate (0.22.4-1 -> 0.22.4-2)
[2010-08-26 08:34] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2010-08-26 08:34] upgraded pacman-mirrorlist (20100808-1 -> 20100825-1)
[2010-08-26 08:34] upgraded renderproto (0.11-1 -> 0.11.1-1)
[2010-08-26 08:34] upgraded sqlite3 (3.7.0.1-1 -> 3.7.1-1)
[2010-08-26 08:35] upgraded tzdata (2010k-1 -> 2010l-1)
[2010-08-26 08:35] upgraded videoproto (2.3.0-1 -> 2.3.1-1)
[2010-08-26 08:35] upgraded xorg-server-utils (7.5-4 -> 7.5-6)
[2010-08-26 08:35] upgraded xorg-utils (7.6-2 -> 7.6-3)
[2010-08-26 08:35] upgraded xterm (259-1 -> 261-1)
Because of the xorg pkg. upgrades, I first thought X problems with my nvidia card but I found if I don't use slim, I can startx from console with no problem. I found if I changed to a different tty, killed x, etc. I could login and startx but the session would only last a couple of minutes and x would die. Seemed to do this even if I stopped slim with /etc/rc.d/slim stop but I was messing around with so many things that I can't be sure I actually stopped slim. As long as I didn't start it, everything seems to be fine.
The slim log isn't much help--it just mentions unable to connect to xserver, so for slim, it seems the upgrade to xorg-utils or xorg-server-utils is a problem.
Personally, I prefer to use no login manager anyway but this is on the main home computer and the wife likes to see a nice login screen (she doesn't like changes to the computer setup much).
Last edited by bgc1954 (2010-08-26 17:37:32)
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
Maybe try the inittab way to start slim and see if it works better? Info in the Wiki..
Offline
Nope, that won't help cause that's the way I've always started slim--never did like the daemon start method.
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
[2010-08-26 08:34] upgraded libxcb (1.6-1 -> 1.7-1)
i think this is the cause.
Offline
Hello!
I'm experiencing the same problem: since I updated my system with 'pacman -Syu' slim no longer works on my laptop. More precisely, in place of the usual login screen of slim I get a black screen without prompt, but I still can use Ctrl-Alt-F1 to login in on tty. I tried to start slim from rc.conf or from inittab, no difference.
This problem does not seem to be related to Xorg and my (trident) video driver, as I believed first: replacing slim by lxdm without changing anything else solved the problem completely. Nevertheless I was very fond of the simplicity of slim and I would prefer to use it again if possible, but I have absolutely no idea of what is going on.
@Iceman81: I followed your link without understanding how to use the information there.
@bgc1954: Did you eventually solve your problem?
@Everybody: Could anyone give me a hint? I'm an ordinary Arch user, not a "master of Kyudo".
Regards,
LuX.
Offline
here the same mysterious problem.
I use dwm on a Hp laptop and I thought it was a problem with the xorg packages, instead starting X from the console works just fine, only slim doesn't work, it produces a black screen with "failed to login".
Any advice? Thx!
EDIT: editing my .xinitrc solved the issue for me, I had to use the complete path to my script to launch dwm, i.e. /home/me/bin/dwmlaunch.sh and not just dwmlaunch.sh
I solved it by looking at /var/log/slim.log, it pointed out that the script was missing.
I guess why it worked until yesterday, if someone has some explanations to share I would love it.
Last edited by motmaos (2011-01-03 09:53:52)
Offline
I have the same problem except I use GDM w gnome. I have to remove the "quiet splash" line from grub kernel then it boots fine. Still DK what causes it thought.
If I don't remove the "quiet splash" from the grub kernel then I need to boot puppy linux(5.11) first before booting Arch, otherwise it'll just stop at the end of splash screen forever.
Offline