Azazel Gad changed bug 956068
What Removed Added
CC   azazel_2011@yahoo.com.mx

Comment # 6 on bug 956068 from
Hi all,

I'm having a similar issue.
I originally installed KDE with a fresh openSUSE Leap install. Then I decided
to try out GNOMEand installed it from YaST software install or delete /
patterns / gnome basic system and gnome desktop environment. 

After installation had finished I decided to reboot the computer and chose
GNOME from SDDM login screen. I got a something went wrong Logout screen which
sent me back to SDDM login screen. I thought the issue may be related to sddm
so I installed and changed my display manager to lightdm and got same result as
sddm after rebooting computer. Finally I changed my display manager to GDM.
After rebooting the computer I only got a black screen and no login at all.

I used a virtual console (ctrl + alt + F1) to change my display manager back to
sddm so I could start KDE at least.

I'm using a AMD Radeon GPU with proprietary driver installed from repos.

this is what I got from journalctl:

dic 12 21:36:51 jarvis gnome-session[2028]: ** (gnome-session-failed:2282):
WARNING **: Could not open X display
dic 12 21:36:51 jarvis gnome-session[2028]: Unable to init server: No se pudo
conectar: Conexi�n rehusada
dic 12 21:36:51 jarvis gnome-session[2028]: ** (gnome-session-failed:2282):
WARNING **: No se puede abrir el visor:
dic 12 21:36:55 jarvis gnome-session[2317]: X Error of failed request: 
BadValue (integer parameter out of range for operation)
dic 12 21:36:55 jarvis gnome-session[2317]: Major opcode of failed request: 
141 (RANDR)
dic 12 21:36:55 jarvis gnome-session[2317]: Minor opcode of failed request:  13
(RRChangeOutputProperty)
dic 12 21:36:55 jarvis gnome-session[2317]: Value in failed request:  0x75
dic 12 21:36:55 jarvis gnome-session[2317]: Serial number of failed request: 
320
dic 12 21:36:55 jarvis gnome-session[2317]: Current serial number in output
stream:  322
dic 12 21:37:02 jarvis gnome-session[2317]: gnome-session[2317]: WARNING: Lost
name on bus: org.gnome.SessionManager
dic 12 21:37:02 jarvis gnome-session[2317]: WARNING: Lost name on bus:
org.gnome.SessionManager
dic 12 21:37:02 jarvis gnome-session[2317]: g_dbus_connection_real_closed:
Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an
async read (g-io-error-quark, 0). Exiting.
dic 12 21:37:03 jarvis gnome-session[2317]: ** (gnome-session-failed:2376):
WARNING **: Could not open X display
dic 12 21:37:03 jarvis gnome-session[2317]: Unable to init server: No se pudo
conectar: Conexi�n rehusada
dic 12 21:37:03 jarvis gnome-session[2317]: ** (gnome-session-failed:2376):
WARNING **: No se puede abrir el visor:
dic 12 21:37:07 jarvis gnome-session[2411]: X Error of failed request: 
BadValue (integer parameter out of range for operation)
dic 12 21:37:07 jarvis gnome-session[2411]: Major opcode of failed request: 
141 (RANDR)
dic 12 21:37:07 jarvis gnome-session[2411]: Minor opcode of failed request:  13
(RRChangeOutputProperty)
dic 12 21:37:07 jarvis gnome-session[2411]: Value in failed request:  0x75
dic 12 21:37:07 jarvis gnome-session[2411]: Serial number of failed request: 
320
dic 12 21:37:07 jarvis gnome-session[2411]: Current serial number in output
stream:  322
dic 12 21:39:28 jarvis gnome-session[2411]: WARNING: Lost name on bus:
org.gnome.SessionManager
dic 12 21:39:28 jarvis gnome-session[2411]: gnome-session[2411]: WARNING: Lost
name on bus: org.gnome.SessionManager
dic 12 21:40:42 jarvis gnome-session[1152]: X Error of failed request: 
BadValue (integer parameter out of range for operation)
dic 12 21:40:42 jarvis gnome-session[1152]: Major opcode of failed request: 
141 (RANDR)
dic 12 21:40:42 jarvis gnome-session[1152]: Minor opcode of failed request:  13
(RRChangeOutputProperty)
dic 12 21:40:42 jarvis gnome-session[1152]: Value in failed request:  0x75
dic 12 21:40:42 jarvis gnome-session[1152]: Serial number of failed request: 
320
dic 12 21:40:42 jarvis gnome-session[1152]: Current serial number in output
stream:  322

Hope you can help me.

Thank you


You are receiving this mail because: