Gnome starts instead of Plasma

Support System Updates
1

Hi, I’m very confused right now.
After running updates last night, I’ve started Manjaro this morning and to my unpleasant surprise it started with Gnome instead of KDE. I’m not sure what happened so I’m unsure how to proceed. I could try to use:
sudo systemctl disable gdm
and then
sudo systemctl enable sddm

But as I’m unsure about the cause I might accidentally wreck my system.
Using BRTFS I could also use the last snapshot which should be from before the update to rollback, but I also never used that, so the outcome is also not clear.

I did not include any information about my system in order not to clutter the thread with to much unnecessary information and will happily provide all information needed (e.g. system logs, system information, etc. ) to solve the issue.
I’m unsure which is the better method: posting all information I can and “clutter” the thread or provide needed information to faster pinpoint the issue. So I apologise in advance if I did this wrong.

Best,
Edward

2

That appears rather impossible. I can think of rather obscure scenarios but those are quite unlikely to happen overnight.

If you installed Plasma there is no Gnome.

An update doesn’t change that either.

Have you ever installed Gnome on the system before you installed Plasma ?

Have you ever had a dual-boot system where a Gnome based distribution was part of the setup ?

3

Hi @EdwardHyde

Please provide all relevant information, including system information as descibed (below). Also ensure to present all code and command output as pre-formatted text according to forum guidelines (link below).

I’m sure someone will help as soon as they are able.

Regards.

What follows is from a standard template.

Welcome back to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading
Highly Recommended

Work with us, not against us

It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.

Simply waiting for others to ask you questions is counter-productive – typically, nobody has a :crystal_ball: at their disposal – and your clear, concise and accurate input is often relied upon in order to help you.

Please help others to make informed suggestions based on information you provide.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):
inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)
inxi man pages (manual)
If running `inxi` within a `chroot` environment
  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0
Your privacy is respected

Update Announcements

Technical Resources

7

TBH I have no clue what happened.
I’ve installed Manjaro quite a while ago and installed it with KDE Plasma only.
I have installed some tools native to the GNOME environment (GNOME drive?), but that’s about it.
Never tried any dual boot with another desktop environment.

I’ll provide all system information as requested within a separate answer.
If you need something more specific, please let me know.

inxi -zv8:

System: 
  Kernel: 6.17.11-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 
    clocksource: tsc avail: hpet,acpi_pm 
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.17-x86_64 
    root=UUID=6bdc1c79-9feb-41c8-b987-c2d415b63d82 rw rootflags=subvol=@ 
    quiet splash acpi=force apm=power_off 
  Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell 
    tools: gsd-screensaver-proxy, xscreensaver, xscreensaver-systemd dm: SDDM 
    Distro: Manjaro base: Arch Linux 
Machine: 
  Type: Desktop Mobo: MSI model: Z97-G45 GAMING (MS-7821) v: 1.0 
    serial: <superuser required> uuid: <superuser required> Firmware: UEFI 
    vendor: American Megatrends v: 2.4 date: 09/19/2014 
Battery: 
  Message: No system battery data found. Is one present? 
Memory: 
  System RAM: total: 16 GiB available: 15.56 GiB used: 3.37 GiB (21.7%) 
  Message: For most reliable report, use superuser + dmidecode. 
  Array-1: capacity: 32 GiB slots: 4 modules: 2 EC: None 
    max-module-size: 8 GiB note: est. 
  Device-1: ChannelA-DIMM0 type: no module installed 
  Device-2: ChannelA-DIMM1 type: DDR3 detail: synchronous size: 8 GiB speed: 
    spec: 1600 MT/s actual: 1333 MT/s volts: curr: 2 min: 2 max: 2 width (bits): 
    data: 64 total: 64 manufacturer: Corsair part-no: CML16GX3M2A1600C10 
    serial: N/A 
  Device-3: ChannelB-DIMM0 type: no module installed 
  Device-4: ChannelB-DIMM1 type: DDR3 detail: synchronous size: 8 GiB speed: 
    spec: 1600 MT/s actual: 1333 MT/s volts: curr: 2 min: 2 max: 2 width (bits): 
    data: 64 total: 64 manufacturer: Corsair part-no: CML16GX3M2A1600C10 
    serial: N/A 
PCI Slots: 
  Permissions: Unable to run dmidecode. Root privileges required. 
CPU: 
  Info: model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell 
    gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm 
    family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28 
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2 
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB 
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB 
  Speed (MHz): avg: 800 min/max: 800/4000 scaling: driver: intel_cpufreq 
    governor: schedutil cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 
    8: 800 bogomips: 57596 
  Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2 
    bts clflush cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 
    dtherm dts ept ept_ad erms est f16c flexpriority flush_l1d fma fpu 
    fsgsbase fxsr ht ibpb ibrs ida invpcid lahf_lm lm mca mce md_clear mmx 
    monitor movbe msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq 
    pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdtscp 
    rep_good sdbg sep smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp 
    syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi 
    vpid x2apic xsave xsaveopt xtopology xtpr 
  Vulnerabilities: 
  Type: gather_data_sampling status: Not affected 
  Type: ghostwrite status: Not affected 
  Type: indirect_target_selection status: Not affected 
  Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT 
    vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: mmio_stale_data status: Not affected 
  Type: old_microcode status: Not affected 
  Type: reg_file_data_sampling status: Not affected 
  Type: retbleed status: Not affected 
  Type: spec_rstack_overflow status: Not affected 
  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; IBRS_FW; 
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not 
    affected 
  Type: srbds mitigation: Microcode 
  Type: tsa status: Not affected 
  Type: tsx_async_abort status: Not affected 
  Type: vmscape mitigation: IBPB before exit to userspace 
Graphics: 
  Device-1: Advanced Micro Devices \[AMD/ATI\] Baffin \[Radeon RX 460/560D / Pro 
    450/455/460/555/555X/560/560X\] vendor: ASUSTeK driver: amdgpu v: kernel 
    arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie: 
    gen: 3 speed: 8 GT/s lanes: 8 ports: active: DP-1,HDMI-A-1 empty: DVI-D-1 
    bus-ID: 01:00.0 chip-ID: 1002:67ef class-ID: 0300 temp: 49.0 C 
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9 
    compositor: gnome-shell driver: X: loaded: amdgpu unloaded: modesetting 
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0 
  Monitor-1: DP-1 model: LG (GoldStar) ULTRAGEAR serial: <filter> 
    built: 2023 res: mode: 2560x1440 hz: 165 scale: 100% (1) dpi: 108 gamma: 1.2 
    chroma: red: x: 0.686 y: 0.310 green: x: 0.263 y: 0.671 blue: x: 0.149 
    y: 0.055 white: x: 0.314 y: 0.329 size: 600x340mm (23.62x13.39") 
    diag: 690mm (27.2") ratio: 16:9 modes: 2560x1440, 1920x1200, 1920x1080, 
    1600x1200, 1680x1050, 1280x1024, 1440x900, 1280x800, 1280x720, 1024x768, 
    800x600, 720x480, 640x480 
  EDID-Warnings: 1: parse_edid: unknown tag 112 
  Monitor-2: HDMI-1 model: GSM LG ULTRAGEAR res: mode: 2560x1440 hz: 144 
    scale: 100% (1) dpi: 108 size: 600x340mm (23.62x13.39") diag: 690mm (27.15") 
    modes: N/A 
  Monitor-3: HDMI-A-1 model: LG (GoldStar) ULTRAGEAR serial: <filter> 
    built: 2023 res: 2560x1440 dpi: 108 gamma: 1.2 chroma: red: x: 0.686 
    y: 0.310 green: x: 0.263 y: 0.671 blue: x: 0.149 y: 0.055 white: x: 0.314 
    y: 0.329 size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9 
    modes: 2560x1440, 3840x2160, 1920x1200, 1920x1080, 1600x1200, 1680x1050, 
    1280x1024, 1440x900, 1280x800, 1280x720, 1024x768, 800x600, 720x576, 
    720x480, 640x480 
  EDID-Warnings: 1: parse_edid: unhandled CEA mode 93 2: parse_edid: 
    unhandled CEA mode 94 3: parse_edid: unhandled CEA mode 95 4: parse_edid: 
    unhandled CEA mode 96 5: parse_edid: unhandled CEA mode 97 
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi 
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi 
    wayland: drv: radeonsi x11: drv: radeonsi 
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.1-arch1.2 
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 560 Series (radeonsi 
    polaris11 ACO DRM 3.64 6.17.11-1-MANJARO) device-ID: 1002:67ef 
    memory: 3.91 GiB unified: no display-ID: :1.0 
  API: Vulkan v: 1.4.328 layers: 2 device: 0 type: discrete-gpu name: AMD 
    Radeon RX 560 Series (RADV POLARIS11) driver: mesa radv v: 25.3.1-arch1.2 
    device-ID: 1002:67ef surfaces: N/A 
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo 
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop 
Audio: 
  Device-1: Intel 9 Series Family HD Audio vendor: Micro-Star MSI 
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0 
    class-ID: 0403 
  Device-2: Advanced Micro Devices \[AMD/ATI\] Baffin HDMI/DP Audio \[Radeon 
    RX 550 640SP / 560/560X\] vendor: ASUSTeK driver: snd_hda_intel v: kernel 
    pcie: gen: 3 speed: 8 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 1002:aae0 
    class-ID: 0403 
  Device-3: Generalplus USB Audio Device 
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s 
    lanes: 1 mode: 1.1 bus-ID: 1-5:2 chip-ID: 1b3f:2008 class-ID: 0300 
  API: ALSA v: k6.17.11-1-MANJARO status: kernel-api with: aoss 
    type: oss-emulator tools: alsactl,alsamixer,amixer 
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl 
  Server-2: JACK v: 1.9.22 status: off tools: N/A 
  Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse 
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 
    tools: pactl,pw-cat,pw-cli,wpctl 
Network: 
  Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet 
    vendor: Micro-Star MSI driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s 
    lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 1969:e091 class-ID: 0200 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
    broadcast: <filter> 
  IP v6: <filter> type: dynamic noprefixroute scope: global 
  IP v6: <filter> type: noprefixroute scope: link 
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant 
  WAN IP: <filter> 
Bluetooth: 
  Message: No bluetooth data found. 
Logical: 
  Message: No logical block device data found. 
RAID: 
  Message: No RAID data found. 
Drives: 
  Local Storage: total: 834.67 GiB used: 78.04 GiB (9.3%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda maj-min: 8:0 vendor: Transcend model: TS256GSSD230S 
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
    tech: SSD serial: <filter> fw-rev: 7BNR scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SD8TB8U256G1001 
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
    tech: SSD serial: <filter> fw-rev: 3101 scheme: MBR 
  ID-3: /dev/sdc maj-min: 8:32 vendor: Intenso model: N/A size: 238.47 GiB 
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD 
    serial: <filter> fw-rev: 9A0 scheme: GPT 
  ID-4: /dev/sdd maj-min: 8:48 vendor: Intenso model: SSD Sata III 
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
    tech: SSD serial: <filter> fw-rev: 2A0 scheme: MBR 
  Message: No optical or floppy data found. 
Partition: 
  ID-1: / raw-size: 221.05 GiB size: 221.05 GiB (100.00%) 
    used: 43.55 GiB (19.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2 label: N/A 
    uuid: 6bdc1c79-9feb-41c8-b987-c2d415b63d82 
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) 
    used: 664 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: N/A 
    uuid: 1AB1-B2A2 
  ID-3: /home raw-size: 221.05 GiB size: 221.05 GiB (100.00%) 
    used: 43.55 GiB (19.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2 label: N/A 
    uuid: 6bdc1c79-9feb-41c8-b987-c2d415b63d82 
  ID-4: /ssds/exchange raw-size: 119.24 GiB size: 116.81 GiB (97.96%) 
    used: 34.49 GiB (29.5%) fs: ext4 dev: /dev/sdd1 maj-min: 8:49 
    label: shared-ssd uuid: ee8ac212-385b-4f57-bf73-4a9da03ba8dc 
  ID-5: /var/cache raw-size: 221.05 GiB size: 221.05 GiB (100.00%) 
    used: 43.55 GiB (19.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2 label: N/A 
    uuid: 6bdc1c79-9feb-41c8-b987-c2d415b63d82 
  ID-6: /var/log raw-size: 221.05 GiB size: 221.05 GiB (100.00%) 
    used: 43.55 GiB (19.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2 label: N/A 
    uuid: 6bdc1c79-9feb-41c8-b987-c2d415b63d82 
Swap: 
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes 
    compressor: zstd max-pool: 20% 
  ID-1: swap-1 type: partition size: 17.12 GiB used: 0 KiB (0.0%) 
    priority: -2 dev: /dev/sda3 maj-min: 8:3 label: N/A 
    uuid: 06579883-af9d-4e45-83b5-3802596fc605 
Unmounted: 
  ID-1: /dev/sdb1 maj-min: 8:17 size: 221.34 GiB fs: btrfs label: N/A 
    uuid: 4da7ea06-d8ac-48c7-a5c0-efef239777c4 
  ID-2: /dev/sdb2 maj-min: 8:18 size: 17.13 GiB fs: swap label: swap 
    uuid: f8911da4-1263-49e1-82e9-b668b9b6c78f 
  ID-3: /dev/sdc1 maj-min: 8:33 size: 1024 MiB fs: vfat label: N/A 
    uuid: 8187-3218 
  ID-4: /dev/sdc2 maj-min: 8:34 size: 220.34 GiB fs: btrfs 
    label: endeavouros uuid: 2685bd17-2585-44cb-bbcb-4f18e35f88f0 
  ID-5: /dev/sdc3 maj-min: 8:35 size: 17.12 GiB fs: swap label: swap 
    uuid: 816f90b3-f1b4-4a1a-b565-094c271c4a52 
USB: 
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 14 rev: 2.0 
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002 
    class-ID: 0900 
  Device-1: 1-5:2 info: Generalplus USB Audio Device type: audio,HID 
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA 
    chip-ID: 1b3f:2008 class-ID: 0300 
  Hub-2: 1-9:3 info: Terminus Hub ports: 4 rev: 2.0 
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA 
    chip-ID: 1a40:0101 class-ID: 0900 
  Device-1: 1-9.3:4 info: A4Tech XL-730K / XL-747H XL-750BK XL-755BK Mice 
    type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1 
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA 
    chip-ID: 09da:9090 class-ID: 0301 
  Device-2: 1-9.4:5 info: CHERRY Keyboard type: keyboard,HID 
    driver: cherry,usbhid interfaces: 2 rev: 2.0 speed: 1.5 Mb/s (183 KiB/s) 
    lanes: 1 mode: 1.0 power: 100mA chip-ID: 046a:0023 class-ID: 0300 
  Hub-3: 2-0:1 info: full speed or root hub ports: 2 rev: 2.0 
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002 
    class-ID: 0900 
  Hub-4: 2-1:2 info: Intel Integrated Hub ports: 8 rev: 2.0 
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8001 
    class-ID: 0900 
  Hub-5: 3-0:1 info: super-speed hub ports: 6 rev: 3.0 
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003 
    class-ID: 0900 
  Hub-6: 4-0:1 info: full speed or root hub ports: 2 rev: 2.0 
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002 
    class-ID: 0900 
  Hub-7: 4-1:2 info: Intel ports: 6 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) 
    lanes: 1 mode: 2.0 chip-ID: 8087:8009 class-ID: 0900 
Sensors: 
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: amdgpu temp: 50.0 C 
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 1226 
Repos: 
  Packages: 1547 pm: pacman pkgs: 1529 libs: 400 tools: pamac pm: flatpak 
    pkgs: 18 
  Active pacman repo servers in: /etc/pacman.d/mirrorlist 
    1: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch 
    2: https://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch 
    3: https://mirror.xenyth.net/manjaro/stable/$repo/$arch 
    4: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch 
    5: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch 
    6: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch 
    7: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch 
    8: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch 
Processes: 
  CPU top: 5 of 385 
  1: cpu: 36.3% command: firefox pid: 3670 mem: 900.7 MiB (5.6%) 
  2: cpu: 20.2% command: librewolf pid: 6178 mem: 411.6 MiB (2.5%) 
  3: cpu: 15.0% command: gnome-shell pid: 908 mem: 378.2 MiB (2.3%) 
  4: cpu: 14.1% command: librewolf pid: 6419 mem: 326.1 MiB (2.0%) 
  5: cpu: 4.7% command: librewolf pid: 6359 mem: 165.2 MiB (1.0%) 
  Memory top: 5 of 385 
  1: mem: 900.7 MiB (5.6%) command: firefox pid: 3670 cpu: 36.3% 
  2: mem: 411.6 MiB (2.5%) command: librewolf pid: 6178 cpu: 20.2% 
  3: mem: 378.2 MiB (2.3%) command: gnome-shell pid: 908 cpu: 15.0% 
  4: mem: 326.1 MiB (2.0%) command: librewolf pid: 6419 cpu: 14.1% 
  5: mem: 264.7 MiB (1.6%) command: firefox pid: 4838 cpu: 1.9% 
Info: 
  Processes: 385 Power: uptime: 3m states: freeze,mem,disk suspend: deep 
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot, 
    suspend, test_resume image: 6.2 GiB services: gsd-power, 
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical 
    tool: systemctl 
  Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.8 running-in: konsole 
    inxi: 3.3.40

Mod edit:- Tidied pre-formatted text display. No charge.

journalctl --boot=-1 --priority=3 --catalog --no-pager
Dez 15 08:25:51 fenris dbus-broker-launch[825]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Dez 15 08:26:04 fenris dbus-broker-launch[3101]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Dez 15 08:26:13 fenris systemd[3031]: Failed to start IBus Daemon for GNOME.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 643 and the job result is failed.
Dez 15 08:42:05 fenris systemd[1]: Failed unmounting /ssds/exchange.
░░ Subject: A stop job for unit ssds-exchange.mount has finished
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A stop job for unit ssds-exchange.mount has finished.
░░ 
░░ The job identifier is 5745 and the job result is failed.
Dez 15 08:42:05 fenris dbus-broker-launch[589]: Activation request for 'org.freedesktop.ColorManager' failed.
Dez 15 08:42:05 fenris dbus-broker-launch[589]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Dez 15 08:42:05 fenris systemd[1]: Failed unmounting /var/cache.
░░ Subject: A stop job for unit var-cache.mount has finished
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A stop job for unit var-cache.mount has finished.
░░ 
░░ The job identifier is 5826 and the job result is failed.
``

@linux-aarhus I have a timeshift snapshot from before the last upgrade/*hiccup*. 
That would be my go-to solution as of now tbh.
8

If you can easily reinstall this might be the better solution. You clearly experimented at some point adding another desktop environment without properly cleaning the other one. Which is bad and a mess. The update merely triggered this to appear again on the surface.

9

This seems to suggest otherwise:

10

I’ve got that possibility from a internet search, not because I ever used it.
Before I turn to the forum, I try to find a solution myself. But as I’m unsure what happened initially I’m more than reluctant to use this.

11

We don’t often encourage posting photos, but in this instance it might help, are you able to add a photo of what you see?

12

Sure I can, but what do you have in mind specifically? I can take a screenshot of the “empty” (meaning all apps either closed or minimised) desktop.
If you give me some directions to give as much information, I’ll be happy to oblige.
Or do you mean, that I should use timeshift first and then show how the upgrade looks like (would look like)?

13

The condition it’s in right now - at the login screen, and the desktop should be enough, thanks.

As mentioned earlier, an update will not / can not ever force an update to another DE – unless you have done it, purposely or without knowing it – a DE doesn’t magically change by itself :).

Something must have been inadvertantly done by either you or someone at your location, for another DE to be installed.

So, I have to ask, if it comes to that, is a complete reinstallation an option for you? Are you prepared for that?

14

Your system’s desktop identifies itself as Gnome

The display manager is sddm - that will work but it is unusual to see with Gnome.

The virtual terminal application appears as konsole - which it quite normal for Plasma system.

gds-power is part of gnome-settings-daemon - not common for a Plasma desktop.

thoughts

I think I have an idea of what happened.

You have been using a Plasma X11 session.

This have pulled a gnome-session - perhaps gnome-desktop as dependency.

The previous Plasma update removed the Plasma X11 session and because the display manager SDDM cannot find this session anymore it simply list the available sessions and because Gnome session comes before Plasma session - alphabetically - it has become the default, you have logged into a Gnome session.

Log out and in lower left corner select plasma session and login.

Plasma has announced the demise of x11 session by the time they reach Plasma 6.8.

In the meantime you can - if necessary - get the plasma x11 session back - at least for a short while

sudo pacman -Syu plasma-x11-session

logout and switch session and login

4 Likes
16

@linux-aarhus Wouldn’t it be better/cleaner to timeshift back to yesterday, remove all Gnome apps and make the update?
I have not changed any data, so there would be no loss.

I think linux-aarhus is on to something.
I would go that route (or using timeshift).

As I’m not a good user at all, therefore I have setup Manjaro in a way I can easily reinstall. Most data is on a NAS, Thunderbird/Firefox profiles on a separate drive.
fstab is saved and most stuff I need to do after a fresh install is written down in text files stored on the NAS too.

2 Likes
17

It sounds complex – but, as long as it works for you, all’s good. :wink:

18

sorry - this was intended to be a reply to @EdwardHyde
I can’t simply delete and make the same post to @EdwardHyde because the forum software will fight me, telling me that the post is “too similar” to the previous one … which would be the whole point (duh) :grimacing:

Before you try, simply confirm that both of these are installed.
If they are, switching between them will not damage anything beyond the slight mess that your system already is.

Simply check:

systemctl status sddm
systemctl status gdm

prepending sudo is not necessary - the systemctl command will ask for credentials when they are needed

The result should be that one of them is installed and active (enabled)
and one of them is installed and inactive (disabled).
or that one of the two is not installed at all (service could not be found or something similar).

To switch, disable the one that is active right now
and right after, enable the other one that wasn’t active - so it will be.

There can only be one active and enabled at any one time.

2 Likes
19

It is worth nothing that login manager (greeter) is not equal to desktop environment. Not that the OP thinks this will solve all problems. But might help find the right session in the menu.

1 Like
20

Thanks everyone!

I’ve rolled back using timeshift, removed all gnome apps (and any other GNOME desktop fragments), installed yesterdays updated and switched to Plasma (Wayland).
System seems to be running fine now.

You are the best!

2 Likes
21