Hello all. I upgraded and, of course, didn’t read about it before doing it. I get the Gnome login screen and them all goes blank. I can ping google, but I cant download devtools to try the solution buying me time with X11 until gnome 50.
Is my system too far gone to salvage?
Your posts have been moved to a dedicated topic.
Reinstalling might certainly be the fastest way back to a working machine.
This may indicate other issues are in play. The successful update should have automatically placed you in a Wayland session; that being the new default. The fact that it didn’t leaves unanswered questions.
It’s possible that your system was already in an “unsupported state” before the update was applied – this can often lead to unpredictable consequences.
Without knowing what other factors might be in play, I would suggest this only be considered once you do have a guaranteed working system using Wayland.
However, if you wish to disregard the warning, and try it anyway, it may be possible via a chroot environment. Note that this can potentially lead to deeper complication, if it fails for any reason.
Information on entering chroot can be found here:
If you do decide to reinstall the system, I can offer the following:
1. It’s preferable to install using the latest available ISO. However, the ISOs on the Manjaro “Download” page are still the old ones. The currently recommended Stable ISO can be downloaded from Anh-Linh 25.1-pre1:
- Look for the ISO link under the heading “Anh-Linh 25.1-pre1 (2025-12-08)”
- The new stable release is expected soon; this ISO is recommended right now.
2. Also recommended – Create a Ventoy USB (A new bootable USB solution)
- If the system doesn’t support UEFI, look for the BIOS/MBR instructions in the guide.
3. Important – Read through the Stable Update Announcement thread – particularly the Known Issues and Solutions section – before installing:
4. A final note – Manjaro now defaults to the btrfs filesystem:
You might prefer to still use the ext4 filesystem, in which case you must pay careful attention during install, and make sure to manually select ext4. Likewise with your preferred swap.
Regards.
2 Likes
5 posts were merged into an existing topic: Random banter here
Do you have a Timeshift Snapshot ready to restore your system again?
Maybe manually switch to wayland then before you update again. At Login in SDDM and see what happen.
Posting your system settings could help also:
inxi -zv5
If i remember correctly this could be also a problem related to nvidia GPU hooks, which comes in my mind.
@Kobold
(I keep seeing such ᐸOTᐳ-type “answers” by quiet a few helpers rather often and use to ignore them, but I really wonder why that happens so often.)
A user of one desktop Plasma may forget that Gnome uses a different display manager and vice-versa - I write it of as a typo.
Years ago it was even worse - you would have to remember to ask which display manager was configured - I remember I used lightdm on Gnome because GDM created duplicate sessions.
Today I use lightdm for Plasma because lightdm supports Wayland better than SDDM but I am likely the only one.
A little off-topic here, but the Plasma developers are allegedly working on a display manager of their own — one that looks and feels similar to sddm but would be better integrated, and developed completely under their control. 
I’m going to continue trying to get a working desktop working under wayland this weekend and if I destroy more than I create I’ll do the reinstall option.
1 Like
System:
Kernel: 6.12.61-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Console: tty 2 Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: 970 Extreme3 R2.0 serial: <superuser required>
uuid: <superuser required> Firmware: BIOS vendor: American Megatrends v: P1.60 date: 06/05/2014
Memory:
System RAM: total: 16 GiB available: 15.58 GiB used: 1.41 GiB (9.1%)
Array-1: capacity: 32 GiB slots: 4 modules: 2 EC: None max-module-size: 8 GiB note: est.
Device-1: A1_DIMM0 type: DDR3 size: 8 GiB speed: spec: 1600 MT/s actual: 800 MT/s
Device-2: A1_DIMM1 type: no module installed
Device-3: A1_DIMM2 type: DDR3 size: 8 GiB speed: spec: 1600 MT/s actual: 800 MT/s
Device-4: A1_DIMM3 type: no module installed
CPU:
Info: 8-core model: AMD FX-8320E bits: 64 type: MCP arch: Piledriver rev: 0 cache: L1: 384 KiB
L2: 8 MiB L3: 8 MiB
Speed (MHz): avg: 3200 min/max: 1400/3200 boost: enabled cores: 1: 3200 2: 3200 3: 3200
4: 3200 5: 3200 6: 3200 7: 3200 8: 3200 bogomips: 51104
Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Micro-Star MSI driver: nvidia v: 470.256.02
arch: Turing bus-ID: 01:00.0
Display: unspecified server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9 driver: X:
loaded: N/A failed: nvidia gpu: nvidia,nvidia-nvswitch note: X driver n/a, try sudo/root
tty: 170x48 resolution: 1: 1440x900 2: 1920x1080
API: EGL v: 1.5 drivers: kms_swrast,nvidia,swrast platforms: active: gbm,surfaceless,device
inactive: wayland,x11,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 25.3.1-arch1.2 note: console (EGL sourced)
renderer: llvmpipe (LLVM 21.1.6 256 bits), NVIDIA GeForce GTX 1650/PCIe/SSE2
API: Vulkan v: 1.4.328 drivers: nvidia surfaces: N/A devices: 1
Info: Tools: api: eglinfo, glxinfo, vulkaninfo gpu: nvidia-smi x11: xprop,xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia vendor: ASRock driver: snd_hda_intel
v: kernel bus-ID: 00:14.2
Device-2: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 01:00.1
Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series BlasterX AE-5
Plus] driver: snd_hda_intel v: kernel bus-ID: 04:00.0
API: ALSA v: k6.12.61-1-MANJARO status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.4.9 status: active
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: ASRock
driver: r8169 v: kernel port: d000 bus-ID: 06:00.0
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: mpqemubr0 state: down mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb v: 0.8 type: USB
bus-ID: 1-2:2
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 4.08 TiB used: 387.65 GiB (9.3%)
ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 480GB size: 447.13 GiB
ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD10EADS-00M2B0 size: 931.51 GiB
ID-4: /dev/sdd vendor: Seagate model: BUP Slim size: 1.82 TiB type: USB
Message: No optical or floppy data found.
Partition:
ID-1: / size: 439.04 GiB used: 387.65 GiB (88.3%) fs: ext4 dev: /dev/sda1 label: N/A
uuid: 356e6e75-475f-46d0-8dfe-d1a86c061ab1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 37.4 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 253 Uptime: 13m Init: systemd
Packages: 2632 Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash v: 5.3.8 inxi: 3.3.40
Mod edit: Added inxi output here to keep things in one place.
Since you have a nvidia card like me, i would actually thinking to switch from Gnome to XFCE.
If you don’t plan to replace your Nvidia GPU with a AMD GPU, because Wayland just sucks on Nvidia.
If you rely on Nvidia X Server Settings which i found out today after the update which forced me (luckily) only “temporary” to use Wayland, then you will have no option’s to control your GPU anymore under Wayland.