Page 1 of 3
(fixed) Xorg all over the place (read before posting!)
Posted: Fri Oct 09, 2015 10:09 pm
by twodogs
I have installed Smoothie to hd of my laptop. I logged in as root and changed root password. Then, I ran 'setup' and created new user.
I rebooted computer (how do I just log out?) and then logged in as user. Everything is great! I can reboot, shutdown etc and desktop is great! But..
Once I open a terminal and 'upg' or 'sudo apt-get update and sudo apt-get dist-upgrade' everything appears good until I reboot. I can't log in.
I enter user name and password and just sits there. Never loads desktop.
I go to tty2 and try to log in there as the user. I get to the desktop but no mouse whatsoever. I see cursor, but nothing.
Anyone, have an idea of what is going on?
Just for kicks I thought 'I'll log in as root.' I got to the desktop but had white terminal. I copied xcolors and various other files (.Xresources etc) to root home folder and looks awesome (like it should look!) but, I'm logged in as root and that's a no-no. Anyway, thanks for your help. I really appreciate it.
-Dave.
Re: Smoothie no likey upg
Posted: Sat Oct 10, 2015 4:51 am
by machinebacon
SOLVED: X broken with ati (open drivers)
Posted: Sat Oct 10, 2015 7:18 pm
by tenkainen
I'm at my wits end. Some upgrade, or at least so I think, broke X. Cannot startx as user, but with sudo it does work, perfectly. Haven't rebooted in weeks before today, so the culprit will be as elusive as Bigfoot.
I have HD5450 for what it's worth. Open sauce drivers for it.
Here's the tail of xorg.log:
Code: Select all
[ 368.757] (==) Depth 24 pixmap format is 32 bpp
[ 368.757] (EE) modeset(0): drmSetMaster failed: Permission denied
[ 368.757] (EE)
Fatal server error:
[ 368.757] (EE) AddScreen/ScreenInit failed for driver 0
[ 368.757] (EE)
[ 368.757] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 368.757] (EE) Please also check the log file at "/home/tenkainen/.local/share/xorg/Xorg.0.log" for additional information.
[ 368.757] (EE)
[ 368.762] (EE) Server terminated with error (1). Closing log file.
I can't find anything relevant with some googles, so I'm hoping one of you could be of assistance. Please. I miss Conkeror and all the bloat.
4.20 kernel too.
Re: X broken with ati (open drivers)
Posted: Sat Oct 10, 2015 7:37 pm
by machinebacon
please always check upgrade warnings before upgrading
http://linuxbbq.org/bbs/viewtopic.php?f=9&t=2282
Re: X broken with ati (open drivers)
Posted: Sat Oct 10, 2015 7:44 pm
by tenkainen
I did, but I was quite sure my problem wasn't related. I guess I'll try downgrading some packages.
To clarify, I was on openrc. And 64bit kernel.
And after one hell of downgrading, no dice.
I'm still not convinced I have the same problem, as I had nothing to do with logind.
Well, I guess I'll just have to wait and see.
Re: X broken with ati (open drivers)
Posted: Sat Oct 10, 2015 9:06 pm
by pidsley
What exactly did you downgrade, and what was recently upgraded? "Some upgrade" and "one hell of downgrading" doesn't tell us much. Did you do a web search for the exact text of the drm error?
Is your user in the "video" group? If not, try adding your user to that group.
Finally, as a last resort, try this command (WARNING! I have not tested this and it may cause further damage, and if it does work it is an ugly hack workaround.)
After the chmod, try startx again.
Re: X broken with ati (open drivers)
Posted: Sat Oct 10, 2015 9:42 pm
by tenkainen
As I said, my desktop had an uptime of couple weeks, so I've upgraded massive amount of packages since last X restart, so I have no idea what it was that broke it exactly.
I tried downgrading X, mainly xserver-xorg-core and it's million dependencies, but to no avail. Makes an enormous mess, that.
Tried searching for few hours, the drmSetMaster failed seems to be the main problem, but got nowhere. And I couldn't even get a decent grasp what the error is about specifically.
I am in the video group.
And I could try the chmod-trick later.
Another option is to wait this out, if it'll ever get fixed.
Re: X broken with ati (open drivers)
Posted: Sat Oct 10, 2015 9:57 pm
by pidsley
The error indicates that your user does not have permission to call "drmSetMaster" (but root does.) This is why I asked if you were in the video group, and suggested to chmod the card. It appears that recent changes to systemd have enabled it to allow normal users to call drmSetMaster (so it is related to logind after all) and because you are not using systemd, this breaks your system.
Following machinebacon's instructions
exactly might help.
http://linuxbbq.org/bbs/viewtopic.php?f=9&t=2282#p46339
This kind of crap is why I no longer use sid.
Re: X broken with ati (open drivers)
Posted: Sun Oct 11, 2015 6:57 am
by tenkainen
Okay, I'll try. Thanks!
I even switched to systemd already, openrc had couple of annoying bugs.
Also, sorry machinebacon for not listening to you the first time, I really thought my problem wasn't related.
The mess came, when I didn't have the proper versions in archive folder. Apparently the debs from stretch repos work together. Can now boot to X, and this thread can be purged.
Re: X broken with ati (open drivers)
Posted: Sun Oct 11, 2015 3:45 pm
by ivanovnegro
Just mark it solved.
Re: Smoothie no likey upg
Posted: Sun Oct 11, 2015 3:50 pm
by ivanovnegro
You should have read the upgrade warnings in first place before upgrading. ;)
How to avoid the autologin loop
Posted: Mon Oct 19, 2015 12:13 pm
by Snap
I think in English you call it respawn or something.
Autologin is fine, but whenever I close an Xsession (quit a wm) in bbq spins, it automagically relogs-in again instead of remaining in the tty. Of course, I can disable it in .bash_profile, but it also stops the autologin altogether. Any tips on how to keep autologin into X and stopping the loop?
Thanks.
Re: How to avoid the autologin loop
Posted: Mon Oct 19, 2015 1:27 pm
by wuxmedia
I think the only way is inside .bash_profile
Code: Select all
[[ -z $DISPLAY && $TERM = "linux" && `tty` = "/dev/tty1" ]] && exec startx
So just removing the "&& exec startx" doesn't do what you need?
not 100% sure what is looping TBH.
Re: How to avoid the autologin loop
Posted: Mon Oct 19, 2015 1:31 pm
by dkeg
Ha, that's one of the first things I axe.
Re: How to avoid the autologin loop
Posted: Mon Oct 19, 2015 2:57 pm
by wuxmedia
Shows how much I'm out of X, these days :)
Re: How to avoid the autologin loop
Posted: Mon Oct 19, 2015 5:44 pm
by machinebacon
The autologin loop is exactly the xserver-xorg bug.
Re: How to avoid the autologin loop
Posted: Mon Oct 19, 2015 7:56 pm
by Snap
^ Oh boy...
Xorg all over the place
Posted: Mon Oct 19, 2015 9:02 pm
by ivanovnegro
If you encounter problems with X, auto login or you simply get always kicked out of your graphical environment. Please read the upgrade warnings and if you have anything worthwhile to share, this is the place. I will merge all the useless threads into this one.
Do not open new ones, they will end up in the bin.
Re: Xorg all over the place (read before posting!)
Posted: Sat Oct 31, 2015 11:31 am
by Snap
The fix seems to work. I can run the X, but still cannot get rid of "the loop". I haven't managed to stop the xserver to restart over and over again, or in other words, staying on a tty for at least a second. The thing is I want to install the Nvidia drivers for my new GPU and there's no f***ing way to kill the damned xserver to install them. Any tips on that? Thanks.
Re: Xorg all over the place (read before posting!)
Posted: Sat Oct 31, 2015 12:12 pm
by machinebacon
Please check from a live system that the installed system's /etc/profile.d/ folder only contains bash_completion and no file starting with "zzz" (this is an autostarter script from Debian's live-config which unfortunately gets dropped into the live system via bootscripts -- in the meanwhile I fixed this on newer BBQ versions, don't quite remember which edition you are running)
Secondly, edit ~/.bash_profile and comment the line that contains startx. This breaks the loop (but drops you back to TTY again)
Thirdly, to be sure, check /etc/inittab and disable automatic login there, if applicable. (usually the line contains "login -a USERNAME" for automatic login). Usually it's not affected.
You can definitely always go to TTY2 and let xserver loop in TTY1 until it stops respawning for 5 minutes.
Just to make it clear: did you install systemd?