Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Budgie Desktop does not open after login since update on December 13 #4648

Open
2 tasks done
ChriA3 opened this issue Dec 22, 2024 · 9 comments
Open
2 tasks done

Budgie Desktop does not open after login since update on December 13 #4648

ChriA3 opened this issue Dec 22, 2024 · 9 comments
Labels
Bug Something isn't working Edition: Budgie Issues related to the Budgie Desktop Environment Priority: High High priority

Comments

@ChriA3
Copy link

ChriA3 commented Dec 22, 2024

Please confirm there isn't an open report for this issue

  • I have searched through bug reports

Summary

After the Solus Update on December 13th my Desktop shows a black screen after successful login.

Steps to reproduce

  1. Normal behavior before the update
  2. Installed updates on December 13th
  3. Updates run normally
  4. Shut down and restart computer
  5. Login mask appears as normally
  6. Login works as normally
  7. But then -> Monitor gets black, only mouse arrow remains on screen
  8. No further actions possible, just turning off computer by button is possible
  9. Downgrade history to before update -> resolves the problem

Expected result

At point 7 above -> I would expect to see my Desktop as normally

Actual result

As described points 7-8 above: After successful login:

  1. Monitor gets black, only mouse arrow remains on screen
  2. No further actions possible, just turning off computer by button is possible

Environment

  • Is system up to date?

Repo

Shannon (stable)

Desktop Environment

Budgie

System details

System:
Host: chri-desktop Kernel: 6.6.63-261.lts arch: x86_64 bits: 64
Desktop: Budgie v: 10.9.2 Distro: Solus 4.6 convergence
Machine:
Type: Desktop System: Gigabyte product: Z390 AORUS PRO WIFI v: N/A
serial:
Mobo: Gigabyte model: Z390 AORUS PRO WIFI-CF v: x.x
serial: UEFI-[Legacy]: American Megatrends v: F9a
date: 01/16/2019
CPU:
Info: 8-core Intel Core i9-9900K [MT MCP] speed (MHz): avg: 800
min/max: 800/5000
Graphics:
Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nouveau v: kernel
Device-2: Logitech HD Webcam C525 driver: snd-usb-audio,uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau
resolution: 1680x1050~60Hz
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.2.8 renderer: NV136
Network:
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi
Device-2: Intel Ethernet I219-V driver: e1000e
Drives:
Local Storage: total: 11.37 TiB used: 1.31 TiB (11.5%)
Info:
Memory: total: 32 GiB available: 31.28 GiB used: 2.91 GiB (9.3%)
Processes: 465 Uptime: 14m Shell: Bash inxi: 3.3.36

Other comments

I waited until last update, installed it yesterday. But problem remains...

@ChriA3 ChriA3 added the Bug Something isn't working label Dec 22, 2024
@github-project-automation github-project-automation bot moved this to Triage in Solus Dec 22, 2024
@ermo
Copy link
Contributor

ermo commented Dec 22, 2024

Any chance you could try installing the linux-current kernel instead of the linux-lts one you are using now, and then boot using the linux-current kernel instead of the linux-lts kernel...?

The current linux-current kernel will become the linux-lts kernel very soon, so you would essentially be helping us test the upcoming LTS kernel if you try what I suggest above.

@ChriA3
Copy link
Author

ChriA3 commented Dec 23, 2024

Hello Rune, As much as I see, the linux-current kernel is already installed on my system. Can you please give me some hints, how to boot with this kernel? On my grub startscreen I can only choose between Solus 4.6 Convergence (6.6.63-261.lts) and Solus 4.6 Convergence (alternative boot entries). I think it is none of both?

@TraceyC77 TraceyC77 added the Edition: Budgie Issues related to the Budgie Desktop Environment label Dec 31, 2024
@TraceyC77
Copy link
Contributor

You can check if you have linux-current installed through TTY with this command. If it's installed this is what you will see (Installed package):

❯ eopkg info linux-current
Installed package:
Name                : linux-current, version: 6.12.5, release: 311
Summary             : Linux kernel image and modules (current)
Description         : The Linux kernel and modules, the core of the operating system
Licenses            : GPL-2.0-only
Component           : kernel.image
Dependencies        : 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 218.56 MB
Reverse Dependencies: linux-current-dbginfo 

If that kernel is installed, at your bios screen, choose "alternate boot entries" and see if it's in there.

@ChriA3
Copy link
Author

ChriA3 commented Jan 5, 2025

Hi, thank you for your help, that worked. I now use linux-current version 6.12.5-311.

The problem remains the same.

Do you have any ideas how to fix this? Thanks for any help!

@Staudey
Copy link
Member

Staudey commented Jan 5, 2025

I think nouveau can be a bit buggy currently, for unknown reasons. One workaround would be to install the proprietary NVIDIA drivers.

@ChriA3
Copy link
Author

ChriA3 commented Jan 7, 2025

Hello, Thank you for your help. First I had to go back to November installation state to be able to install NVIDIA drivers. After installing the NVIDIA drivers, I got the following failure: "[FAILED] Failed to start postgresql.service - Postgre SQL database server." But after another update to actual software state it seems to work now. Thank you very much and have a nice day!

@TraceyC77 TraceyC77 added the Priority: High High priority label Jan 7, 2025
@TraceyC77
Copy link
Contributor

Marking high priority since this has affected other users as reported in the forum and it makes the system non-usable

@TraceyC77 TraceyC77 moved this from Triage to Needs More Info in Solus Jan 7, 2025
@ASDTT-1
Copy link

ASDTT-1 commented Jan 8, 2025

Summary
Desktop shows a black screen after successful login.

Steps to reproduce

  1. Normal behaviour before the update
  2. Installed updates on December 13th
  3. Updates run normally
  4. Shut down and restart computer
  5. Login mask appears as normally
  6. Login works as normally
  7. But then -> Monitor gets black, only mouse arrow remains on screen
  8. Can open other tty, mouse can be moved on black screen.
  9. Downgrade history to before update -> cannot rollback pass where llvm-32bit 18.1.8-120-1x86_64 was eliminated (package it's not present in repo). Other rollbacks either fail or give the same issue.

Expected result

At point 7 above -> I would expect to see my Desktop as normally.

Actual result

As described points 7-8 above: After successful login:

  • Monitor gets black, only mouse arrow remains on screen

Environment

Systems is up to date.

Repo

Shannon (stable)

Desktop Environment
Budgie

System details

System: (`nomodeset` session)
  Kernel: 6.12.5-311.current arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
  Desktop: Budgie v: 10.9.2 tk: GTK v: 3.24.43 wm: budgie-wm dm: LightDM
    Distro: Solus 4.6 convergence
Machine:
  Type: Desktop Mobo: Gigabyte model: H61M-D2H-USB3
    serial: <superuser required> BIOS: Award v: F6 date: 06/01/2012
CPU:
  Info: quad core model: Intel Core i5-2500K bits: 64 type: MCP
    arch: Sandy Bridge rev: 7 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2731 min/max: 1600/3700 cores: 1: 2731 2: 2731 3: 2731
    4: 2731 bogomips: 26339
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GF116 [GeForce GTS 450 Rev. 2] vendor: Gigabyte driver: N/A
    arch: Fermi pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:1245
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.4
    compositor: budgie-wm driver: X: loaded: nouveau
    unloaded: fbdev,modesetting,vesa alternate: nv dri: nouveau gpu: N/A
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 63
  Monitor-1: default res: 1024x768 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
    x11: drv: swrast inactive: gbm,wayland
  API: OpenGL v: 4.5 vendor: mesa v: 24.3.3 glx-v: 1.4 direct-render: yes
    renderer: llvmpipe (LLVM 19.1.6 256 bits) device-ID: ffffffff:ffffffff
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1c20
  Device-2: NVIDIA GF116 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0bee
  API: ALSA v: k6.12.5-311.current status: kernel-api
  Server-1: sndiod v: N/A status: off
  Server-2: NAS v: 1.9.5 status: off
  Server-3: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active
  Server-4: PulseAudio v: 17.0 status: off (using pipewire-pulse)
Network:
  Device-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: Gigabyte
    driver: atl1c v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: df00
    bus-ID: 06:00.0 chip-ID: 1969:1083
  IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.83 TiB used: 69.62 GiB (3.7%)
  ID-1: /dev/sda vendor: Seagate model: ST2000DM006-2DM164 size: 1.82 TiB
    speed: 3.0 Gb/s serial: <filter>
  ID-2: /dev/sdb vendor: Generic model: Flash Disk size: 14.65 GiB type: USB
    rev: 2.0 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 95.59 GiB used: 69.62 GiB (72.8%) fs: ext4 dev: /dev/sda3
Swap:
  Alert: No swap data was found.
Info:
  Memory: total: 8 GiB available: 7.74 GiB used: 1.6 GiB (20.7%)
  Processes: 233 Power: uptime: 3m wakeups: 0 Init: systemd v: 254
    default: default
  Packages: 3108 pm: eopkg pkgs: 1554 pm: rpm pkgs: N/A note: see --rpm
    Compilers: gcc: 14.2.0 Shell: Bash v: 5.2.37 running-in: gnome-terminal
    inxi: 3.3.36

Other comments

  • No proprietary drivers available for nvidia GTS 450 (390 is the one recommended on nvidia webpage).
  • Nomodeset is the only way to get to desktop.
  • Journalctl gives a bunch of errors. I've tried eopkg check and everything is listed as ok. The most striking and persistent is budgie-session-binary[848]: Unrecoverable failure in required component org.buddiesofbudgie.BudgiePanel.desktop
  • Tried reinstalling mutter, budgie-session and desktop and nemo as there were some warning in journalctl, but problems persists. Tried booting without mouse connected (for the same reason as before and with the same result). Neither kernel (current or lts) works.
  • Subsequent updates have not resolved the issue.

@ermo
Copy link
Contributor

ermo commented Jan 9, 2025

@EbonJaeger could this perchance be related to anything to do with GSK_RENDERER=ngl vs. GSK_RENDERER=gl in GTK...?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Edition: Budgie Issues related to the Budgie Desktop Environment Priority: High High priority
Projects
Status: Needs More Info
Development

No branches or pull requests

5 participants