You are not logged in.
Pages: 1
Hello all. The issue is that upon logging into Gnome using "startx" it will load the GUI but once loaded it begins to flicker sporadically, especially when the mouse is moved. Also, I am unable to actually click or interact with widgets or any other desktop objects. Located in my ~/.xinitrc file is "exec gnome-session". I've tried updating the system and other window managers but to no avail. The attached log files may be of some use. Thank you all and please let me know about any other pertinent information.
dmesg: https://pastebin.com/XBFRYQX7
journalctl -b: https://pastebin.com/fkqjteGJ
Xorg: https://pastebin.com/Y8cTMMK7
Last edited by golden_boyy (2018-06-03 22:21:28)
Offline
I had that. Try
$ sudo pacman -S xf86-video-intelthen give us the log from xorg (if that doesn't work).
Last edited by nattynattynat (2018-06-03 10:27:01)
Offline
Here is the requested Xorg log after installing xf86-video-intel. I will say that I am using an r9 390 graphics card, so I'm not sure if that is the correct driver? Also, it starts the GUI and upon interaction with the desktop environment it still flickers, eventually crashing.
Xorg log: https://pastebin.com/mPXTxDs1
Offline
In the thread title you state Window Manager Crashes Upon Login but that seems to contradict the content of your posts where you give no evidence of any window manager crashing but experiencing issues under gnome.
Offline
Also looks like some reverse prime setup, please elaborate on your hybrig GPU configuration and see https://wiki.archlinux.org/index.php/PR … erse_PRIME
Online
@Loqs Thread title has been changed to better reflect subject matter, my apologies. @seth I wasn't even aware that I was running a "Hybrid GPU" configuration. I think my lspci would be relevant? Also, I fixed the power management error by appending "radeon runpm=0" to the kernel parameters, though the freezing/lockup and flickering still persists.
Updated Xorg: https://pastebin.com/NQ0rKtiA
lspci: https://pastebin.com/PfxQvW8G
Last edited by golden_boyy (2018-06-03 23:07:35)
Offline
Okay, that got rid of the intel module error. Now try
$ sudo pacman -S xf86-video-vesaHopefully that should work. It worked for me. If it doesn't, again send an updated xorg log.
Last edited by nattynattynat (2018-06-04 01:01:27)
Offline
Unfortunately that didn't work. I used lspci to figure out which kernel driver is currently being used for my graphics card and it appears to be radeon. I went into the .conf file for xorg to force the use of the vesa driver and it fails to recognize any monitor (I have a dual setup). Attached is the xorg log and the .conf file for xorg.
xorg log: https://pastebin.com/Y1KvPpR5 before attempting to force vesa drivers
.conf: https://pastebin.com/pqb8Cuej
xorg log after trying to force vesa drivers: https://pastebin.com/u3DCMNgQ
Also, the bus ID from the .conf file came from the following location. https://pastebin.com/tEEvf0d7
Last edited by golden_boyy (2018-06-04 03:18:23)
Offline
@nattynattynat, please stop suggesting to install random packages, there has been no "intel error" to begin with - the driver was considered, not found and skipped, that is not a critical error because the driver is unmaintained anyway and (kinda) succeeded by the modesetting driver.
golden_boyy, remove the vesa driver again. It's a very basic driver providing the VESA standard and nothing else. You don't want to use that by any means. Any combination of intel, radeon and modesetting driver is a viable option.
To learn about your prime setup, run
xrandr --listproviders
glxinfo | grep "OpenGL renderer"
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"Other than that follow https://wiki.archlinux.org/index.php/PR … erse_PRIME - you could also try to run an uncomposited WM (eg. openbox) to see whether the problem stems from the compositor.
Online
Pages: 1