Have been using tumbleweed as a new distro, coming from KUBUNTU. But since a week or so I have been having issues with spontaneous log offs. Can’t pinpoint it, first day I notices it would log off as soon as I opened a Console, after that it just happens when opening another application. Today it happens when I open Extensions.
Always the same: Screen freezes and everything goes black, after a few seconds the login screen pops up and I can login, but all apps that were open are closed. Also extensions have stopped working. I did a roll back which did help, but as soon as I update to a lates version I get the same behaviour.
AME=“openSUSE Tumbleweed”
VERSION=“20260717”
ID=“opensuse-tumbleweed”
ID_LIKE=“opensuse suse”
VERSION_ID=“20260717”
Just to restrict the search, what Desktop Environment (if any) are you using?
And what is the version you rolled back to and looks good?
And, BTW, Welcome to the openSUSE Forums!
Thanks! GNome desktop. I’ll have to check which roll back version worked.
Hello,
Did you recently edit ~/.profile or ~/.bashrc ? You can check these to see if a logout command (or other suspicious) lays there.
@arluijen What extensions do you have installed gnome-extensions list, they can be an issue at times…
Likewise, can you show the output from inxi -GSaz to see your boot and graphics setup.
Right now, extensions seem to work fine and keep working after latest log off occurence.
Result of inxi -GDSaz:
System:
Kernel: 7.1.3-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.3.0
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-7.1.3-1-default
root=UUID=89a9656d-131f-4d61-b757-ecfb570912f2 splash=silent
mitigations=auto quiet security=selinux selinux=1
Desktop: GNOME v: 50.3 tk: GTK v: 3.24.52 wm: gnome-shell
tools: gsd-screensaver-proxy dm: GDM v: 50.1 Distro: openSUSE Tumbleweed
20260717
Graphics:
Device-1: Intel Ivy Bridge mobile GT2 [HD Graphics 4000] vendor: CLEVO/KAPOK
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports:
active: DP-3,LVDS-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1
bus-ID: 00:02.0 chip-ID: 8086:0166 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Wimbledon XT [Radeon HD 7970M]
vendor: CLEVO/KAPOK driver: amdgpu v: kernel alternate: radeon arch: GCN-1
code: Southern Islands process: TSMC 28nm built: 2011-20 pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 1002:6800 class-ID: 0300
temp: 35.0 C
Device-3: Bison BisonCam NB Pro driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-1.6:4 chip-ID: 5986:0361
class-ID: 0e02
Display: wayland server: Xwayland v: 24.1.13 compositor: gnome-shell
driver: gpu: i915 display-ID: 0
Monitor-1: DP-3 model: LG (GoldStar) HDR 4K serial: <filter> built: 2019
res: 3840x2160 dpi: 163 gamma: 1.2 size: 600x340mm (23.62x13.39")
diag: 690mm (27.2") ratio: 16:9 modes: max: 3840x2160 min: 640x480
Monitor-2: LVDS-1 model: LG Display 0x0259 built: 2009 res: 1920x1080
dpi: 141 gamma: 1.2 size: 345x194mm (13.58x7.64") diag: 396mm (15.6")
ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.2 vendor: intel mesa v: 26.1.5 glx-v: 1.4 es-v: 3.0
direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
device-ID: 8086:0166 memory: 1.46 GiB unified: yes display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo x11: xprop
Cannot reproduce here, but I have no AMD graphics if that made a difference.
If a “logout” happens again, may I suggest that you switch to another VT (for instance by CTRL+ALT+F4), login as “root” and issue w to see if your other user was really logged off or if you are simply redirected to VT7 (where GDM lives) for whatever reason?
Just a shot in the dark, but try booting with the plymouth.enable=0 kernel option, in case you are seeing something similar to Sometimes the graphical session doesn’t come up, stays at tty1