this post was submitted on 06 Jun 2024
20 points (95.5% liked)

Arch Linux

7763 readers
8 users here now

The beloved lightweight distro

founded 4 years ago
MODERATORS
[email protected]
20
Is it common for KDE to crash? (lemmy.dbzer0.com)
submitted 5 months ago by [email protected] to c/[email protected]
17 comments fedilink hide all child comments
 

I've been using linux mint cinnamon for a few months but a few days ago I decided to try endeavourOS. Since the switch I experienced a few crashes where the screen went black and then login page showed up and after getting back my opened apps were all closed. Today I also noticed that my apps pinned to the task manager/bar also got unpinned but I'm not sure at which point that happened. I heard that linux has problems with nvidia GPUs so maybe it has something to do with it?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 5 months ago* (last edited 5 months ago) (1 children)

The funny thing is I'm already on X11 because when it launched on wayland I couldn't do anything because of messed up resolution. It was very low and most of the interface was outside the screen and while trying to troubleshoot what's going on I found this switch on login page and was using X11 ever since. I have 4 monitors connected to my pc and my main one is a FullHDUW monitor and second one like that on top of it. For some reason the second monitor is always visible to the system even though it's turned off but I didn't knew at the time so I haven't tried disconnecting it to see if it was the fault.

[–] [email protected] 2 points 5 months ago (2 children)

Huh, pretty weird one then. What card model and driver version? Does nvidia-settings work? Is 3D performance about where it should?

[–] [email protected] 1 points 5 months ago

This is what I got from: "inxi -Fza"

Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: Gigabyte
    driver: nvidia v: 550.78 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-04; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 0b:00.0
    chip-ID: *REDACTED REDACTED REDACTED*
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
    compositor: kwin_x11 driver: X: loaded: N/A unloaded: modesetting
    failed: nvidia alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 2560x2160 s-dpi: 80 s-size: 813x686mm (32.01x27.01")
    s-diag: 1064mm (41.88")
  Monitor-1: DP-3 pos: top res: 2560x1080 hz: 60 dpi: 81
    size: 798x334mm (31.42x13.15") diag: 865mm (34.06") modes: N/A
  Monitor-2: HDMI-0 pos: primary,bottom res: 2560x1080 hz: 60 dpi: 81
    size: 798x334mm (31.42x13.15") diag: 865mm (34.06") modes: N/A
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
    memory: 5.86 GiB
  API: Vulkan v: 1.3.279 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 2060 driver: nvidia v: 550.78 device-ID: *REDACTED REDACTED REDACTED*
    surfaces: xcb,xlib
[–] [email protected] 1 points 5 months ago (1 children)

RTX 2060, will check drivers after getting home.

[–] [email protected] 2 points 5 months ago (1 children)

Few years back I had to fiddle with the kwin rendering backend and select egl for nvidia.

[–] [email protected] 1 points 5 months ago (1 children)

ELI5? What does that mean and how did you do it?