[RESOLVED] X11 awol after launching gl-117 game

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
swarfendor437
Posts: 30
Joined: Fri Sep 16, 2022 5:23 pm

[RESOLVED] X11 awol after launching gl-117 game

#1 Post by swarfendor437 »

Hi,

My machine specs:

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_wayland vt: 8 dm: SDDM Distro: MX-23.1_KDE_x64 Libretto
    October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 5861 date: 08/10/2021
CPU:
  Info: model: AMD Ryzen 7 1700X bits: 64 type: MT MCP arch: Zen level: v3 note: check
    built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 1 stepping: 1 microcode: 0x8001138
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 768 KiB
    desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 2160 high: 2200 min/max: 2200/3400 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1883 2: 2200 3: 2200 4: 2200 5: 2200 6: 2200
    7: 2200 8: 2200 9: 2200 10: 1884 11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200
    bogomips: 108592
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ZOTAC driver: nouveau v: kernel
    non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s ports:
    active: HDMI-A-1 empty: DP-1 bus-ID: 0b:00.0 chip-ID: 10de:1d01 class-ID: 0300 temp: 35.0 C
  Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_wayland
    driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: 0
  Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
  API: OpenGL v: 4.3 Mesa 23.1.2-1~mx23ahs renderer: NV138 direct-render: Yes
Audio:
  Device-1: Creative Labs CA0108/CA10300 [Sound Blaster Audigy Series] driver: snd_emu10k1
    v: kernel bus-ID: 06:00.0 chip-ID: 1102:0008 class-ID: 0401
  Device-2: NVIDIA GP108 High Definition Audio vendor: ZOTAC driver: N/A alternate: snd_hda_intel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s bus-ID: 0b:00.1
    chip-ID: 10de:0fb8 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api with: apulse type: pulse-emulator
    tools: alsamixer,alsamixergui,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 09:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.42 TiB used: 18.73 GiB (1.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5003AZEX-00MK2A0 size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1A01 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD1005FBYZ-01YCBB3 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: RR09 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Ultra size: 57.28 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 465.51 GiB size: 457.13 GiB (98.20%) used: 18.73 GiB (4.1%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 29.2 C mobo: 30.0 C gpu: nouveau temp: 35.0 C
  Fan Speeds (RPM): cpu: 0 case-1: 744 case-2: 645 case-3: 683
  Power: 12v: 12.10 5v: N/A 3.3v: N/A vbat: N/A
Repos:
  Packages: pm: dpkg pkgs: 2638 libs: 1441 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
    2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm ahs
Info:
  Processes: 356 Uptime: 5m wakeups: 1 Memory: 15.52 GiB used: 2.2 GiB (14.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
After launching the game I get an out-of-range message on my monitor. Rebooting gets to login but after logging in get same error message. Able to boot into desktop with Wayland but not X11. How to fix?

My boot logs:

------------ Wed Nov 08 22:16:35 GMT 2023 ------------
rootMX23: recovering journal
rootMX23: Clearing orphaned inode 13151694 (uid=1000, gid=1000, mode=0100644, size=23612)
rootMX23: Clearing orphaned inode 13153584 (uid=1000, gid=1000, mode=0100644, size=68668)
rootMX23: Clearing orphaned inode 13153568 (uid=1000, gid=1000, mode=0100644, size=40348)
rootMX23: Clearing orphaned inode 13153541 (uid=1000, gid=1000, mode=0100644, size=59360)
rootMX23: Clearing orphaned inode 13153367 (uid=1000, gid=1000, mode=0100644, size=16100)
rootMX23: Clearing orphaned inode 13109509 (uid=1000, gid=1000, mode=0100644, size=38348)
rootMX23: Clearing orphaned inode 13273630 (uid=1000, gid=1000, mode=0100644, size=20612)
rootMX23: Clearing orphaned inode 13159413 (uid=1000, gid=1000, mode=0100644, size=4819)
rootMX23: Clearing orphaned inode 13157227 (uid=1000, gid=1000, mode=0100644, size=4819)
rootMX23: Clearing orphaned inode 13148333 (uid=1000, gid=1000, mode=0100644, size=23612)
rootMX23: Clearing orphaned inode 13156563 (uid=1000, gid=1000, mode=0100644, size=68668)
rootMX23: Clearing orphaned inode 13156523 (uid=1000, gid=1000, mode=0100644, size=40348)
rootMX23: Clearing orphaned inode 13153923 (uid=1000, gid=1000, mode=0100644, size=59360)
rootMX23: Clearing orphaned inode 13148905 (uid=1000, gid=1000, mode=0100644, size=16100)
rootMX23: Clearing orphaned inode 13109480 (uid=1000, gid=1000, mode=0100644, size=38348)
rootMX23: Clearing orphaned inode 13274006 (uid=1000, gid=1000, mode=0100644, size=20612)
rootMX23: clean, 654758/30515200 files, 7086704/122030592 blocks
INIT: version 3.06 booting

INIT: No inittab.d directory found

Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
------------ Wed Nov 08 22:19:29 GMT 2023 ------------
rootMX23: recovering journal
rootMX23: Clearing orphaned inode 13158551 (uid=1000, gid=1000, mode=0100644, size=23612)
rootMX23: Clearing orphaned inode 13158450 (uid=1000, gid=1000, mode=0100644, size=68668)
rootMX23: Clearing orphaned inode 13156501 (uid=1000, gid=1000, mode=0100644, size=40348)
rootMX23: Clearing orphaned inode 13156500 (uid=1000, gid=1000, mode=0100644, size=59360)
rootMX23: Clearing orphaned inode 13109478 (uid=1000, gid=1000, mode=0100644, size=16100)
rootMX23: Clearing orphaned inode 13109205 (uid=1000, gid=1000, mode=0100644, size=38348)
rootMX23: Clearing orphaned inode 13274009 (uid=1000, gid=1000, mode=0100644, size=20612)
rootMX23: clean, 654747/30515200 files, 7086786/122030592 blocks
INIT: version 3.06 booting

INIT: No inittab.d directory found

Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
------------ Wed Nov 08 22:43:38 GMT 2023 ------------
rootMX23: Clearing orphaned inode 13151694 (uid=1000, gid=1000, mode=0100644, size=23612)
rootMX23: Clearing orphaned inode 13156226 (uid=1000, gid=1000, mode=0100644, size=68668)
rootMX23: Clearing orphaned inode 13153923 (uid=1000, gid=1000, mode=0100644, size=40348)
rootMX23: Clearing orphaned inode 13153584 (uid=1000, gid=1000, mode=0100644, size=59360)
rootMX23: Clearing orphaned inode 13153568 (uid=1000, gid=1000, mode=0100644, size=16100)
rootMX23: Clearing orphaned inode 13109218 (uid=1000, gid=1000, mode=0100644, size=38348)
rootMX23: Clearing orphaned inode 13273630 (uid=1000, gid=1000, mode=0100644, size=20612)
rootMX23: clean, 654746/30515200 files, 7086868/122030592 blocks
INIT: version 3.06 booting

INIT: No inittab.d directory found

Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
------------ Wed Nov 08 22:50:36 GMT 2023 ------------
rootMX23: recovering journal
rootMX23: Clearing orphaned inode 13274006 (uid=1000, gid=1000, mode=0100644, size=20612)
rootMX23: clean, 654750/30515200 files, 7086949/122030592 blocks
INIT: version 3.06 booting

INIT: No inittab.d directory found

Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
------------ Wed Nov 08 23:13:08 GMT 2023 ------------
rootMX23: recovering journal
rootMX23: Clearing orphaned inode 13157280 (uid=1000, gid=1000, mode=0100644, size=23612)
rootMX23: Clearing orphaned inode 13156498 (uid=1000, gid=1000, mode=0100644, size=68668)
rootMX23: Clearing orphaned inode 13153621 (uid=1000, gid=1000, mode=0100644, size=40348)
rootMX23: Clearing orphaned inode 13156495 (uid=1000, gid=1000, mode=0100644, size=59360)
rootMX23: Clearing orphaned inode 13110250 (uid=1000, gid=1000, mode=0100644, size=16100)
rootMX23: Clearing orphaned inode 13109508 (uid=1000, gid=1000, mode=0100644, size=38348)
rootMX23: Clearing orphaned inode 13273630 (uid=1000, gid=1000, mode=0100644, size=20612)
rootMX23: Clearing orphaned inode 13110337 (uid=1000, gid=1000, mode=0100644, size=23612)
rootMX23: Clearing orphaned inode 13156500 (uid=1000, gid=1000, mode=0100644, size=68668)
rootMX23: Clearing orphaned inode 13156491 (uid=1000, gid=1000, mode=0100644, size=40348)
rootMX23: Clearing orphaned inode 13156226 (uid=1000, gid=1000, mode=0100644, size=59360)
rootMX23: Clearing orphaned inode 13109205 (uid=1000, gid=1000, mode=0100644, size=4819)
rootMX23: Clearing orphaned inode 13155883 (uid=1000, gid=1000, mode=0100644, size=16100)
rootMX23: Clearing orphaned inode 13109562 (uid=1000, gid=1000, mode=0100644, size=38348)
rootMX23: Clearing orphaned inode 13274006 (uid=1000, gid=1000, mode=0100644, size=20612)
rootMX23: clean, 654631/30515200 files, 7102454/122030592 blocks
INIT: version 3.06 booting

INIT: No inittab.d directory found

Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
Last edited by swarfendor437 on Sat Nov 11, 2023 5:17 pm, edited 1 time in total.

User avatar
CharlesV
Global Moderator
Posts: 7238
Joined: Sun Jul 07, 2019 5:11 pm

Re: X11 awol after launching gl-117 game

#2 Post by CharlesV »

In your home /.config/xfce4/xfconf/xfce-perchannel-xml/
( ~/.config/xfce4/xfconf/xfce-perchannel-xml/ )

there is a file named displays.xml which for me contains all of my monitor information, including refresh rates etc. You might try moving this file to a backup area ( dont delete it) and see if starting x11 will then recreate it properly. (It sounds like this file is possibly corrupt).
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

User avatar
swarfendor437
Posts: 30
Joined: Fri Sep 16, 2022 5:23 pm

Re: X11 awol after launching gl-117 game

#3 Post by swarfendor437 »

I'm running KDE not xfce.

User avatar
dolphin_oracle
Developer
Posts: 22193
Joined: Sun Dec 16, 2007 12:17 pm

Re: X11 awol after launching gl-117 game

#4 Post by dolphin_oracle »

did the game or you place any files in /etc/X11/xorg.conf.d or may in a /etc/X11/xorg.conf file?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
swarfendor437
Posts: 30
Joined: Fri Sep 16, 2022 5:23 pm

Re: X11 awol after launching gl-117 game

#5 Post by swarfendor437 »

There was something in a file somewhere which I deleted. No xorg.conf file, just xorg.conf.d folder which has this:
xorg.conf.d.png
You do not have the required permissions to view the files attached to this post.

User avatar
dolphin_oracle
Developer
Posts: 22193
Joined: Sun Dec 16, 2007 12:17 pm

Re: X11 awol after launching gl-117 game

#6 Post by dolphin_oracle »

swarfendor437 wrote: Fri Nov 10, 2023 2:02 pm There was something in a file somewhere which I deleted.
do you know what it was?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
swarfendor437
Posts: 30
Joined: Fri Sep 16, 2022 5:23 pm

Re: X11 awol after launching gl-117 game

#7 Post by swarfendor437 »

Can't remember exactly but spotted a gl-117 file after searching for anything labelled as such and deleted wherever it was. Having looked at Xorg.conf.d directory in terminal I spotted that 10-nvidia.conf was not present so created one in nano editor and used same structure as that for 10-amdgpu but replacing amdgpu with nvidia for each line - no joy. After "out of range" error message I used Ctrl+ Alt+ 4 to open a terminal, logged in and tried to run xrandr but got message can't open display. Then doing some searches I found this command:

Code: Select all

export DISPLAY=:0
This brought back all the available resolutions and indicated that it was set to 1024x768!

I attempted to follow various guides about how to add a new mode after using cvt and gtf with error message

Code: Select all

xrandr: configure crtc 0 failed
Just to add that in my initial search, gl-117 also caused the same issue for an Ubuntu user many years ago, so would suggest that gl-117 was OK in the day of Open SuSE 9x but not now! Needs to be removed from the Games section of Software and Synaptic Package Manager, but not checked to see if it is in Synaptic, because you can't use Synaptic in Wayland which is what I am using now - nothing critical on this rig, so will do a fresh install!

User avatar
swarfendor437
Posts: 30
Joined: Fri Sep 16, 2022 5:23 pm

Re: [RESOLVED] X11 awol after launching gl-117 game

#8 Post by swarfendor437 »

[RESOLVED] Reinstalled. Will remember to setup Timeshift!

Post Reply

Return to “MX KDE Official Release”