[Stable Update] 2024-01-13 - Kernels, Systemd, Qt5, Mesa, Dbus, Firefox, Thunderbird

@philm, does this update change anything about gpu hardware acceleration? I told you this because after the update, Brave browser and Chromium show strange artifacts on screen while browsing as I shown before in this thread:

Even appear weird images as seen here:

2cr

Disabling hardware acceleration in browser (Settings → Systems → Disable hardware acceleration when available) the problems disappear.

And Videolan VLC before the update played AVI (xvid codec) or MKV (264 or 265 codec) files without problem. Hardware acceleration was set in “Auto”. After the update plays MKV files but not AVI, there’s sound but only a black screen.

Disabling hardware acceleration in Tools → Preferences → Input & Codecs → Codecs → Hardware-accelerated decoding plays AVI files again.

And seems I’m not the only one with this issue:

All this happen after the update. Brave, Chromium or VLC weren’t updated, so must be caused by another package. If I restore the timeshift snapshot made before the update, browsers work without problems and VLC plays all files as usual.

@Arrababiski seems mesa is not your friend. What GPU you’re using?


Graphics:
  Device-1: AMD Caicos PRO [Radeon HD 7450] driver: radeon v: kernel
  Display: x11 server: X.Org v: 21.1.10 driver: X: loaded: radeon
    unloaded: modesetting dri: r600 gpu: radeon resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,r600,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.5 vendor: mesa v: 23.1.9-manjaro1.1 renderer: AMD CAICOS
    (DRM 2.50.0 / 6.6.10-1-MANJARO LLVM 16.0.6)
  API: Vulkan Message: No Vulkan data available.

> 0000:01:00.0 (0300:1002:677b) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> 0000:04:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2023.09.12                true            PCI

I restored again the timeshift snapshot made before the update and worked fine again. Repeated the update choosing dbus-daemon instead of dbus-broker (only for testing) but the artifacts reappear.

Copying data from USB stick via dolphin to the system is also very slow …
I guess there is a problem with the new kernel, I’ll test the LTS straight away also because of the shutdown issue.

edit

Yes, the issue with copying from usb stick is caused by the new kernel, the problem does not occur with 6.6.10.
The shutdown problem is probably caused by a systemd thing …

Worked for me as well. On my side dual-boot was broken as well, but sudo grub-mkconfig fixed that too.

2 Likes

You’re right. I restored again the timeshift snapshot from before the update, repeat all the update except these ten packages and after the reboot had no problem, no artifacts, VLC plays AVI again.

lib32-libva-mesa-driver-1:23.3.3-1
lib32-mesa-1:23.3.3-1
lib32-mesa-vdpau-1:23.3.3-1
lib32-vulkan-intel-1:23.3.3-1
lib32-vulkan-radeon-1:23.3.3-1
libva-mesa-driver-1:23.3.3-1
mesa-1:23.3.3-1
mesa-vdpau-1:23.3.3-1
vulkan-intel-1:23.3.3-1
vulkan-radeon-1:23.3.3-1

So I’ll include these packages in IgnorePkg from pacman.conf and wait for the next mesa release to see if works well. Thanks!

You could do that. See Manjaro Kernels.

Or, if kernel 6.6.10 was actually installed, you might just need to select it from the Grub boot menu.

There is weird issue when saving files from web browsers (firefox, chrome) on smb share… files are corrupted or fail when saving. I don’t see such issues outside web browsers for now. Also there are no problems with nfs shares or local disks.

Hi,

After the update, the reboot was ok. Just a little issue: after few second any icons disappeared in the desktop. The background image is like before the update, at the moment any programs works well…but no icon (trash bin, shortcut to programs, files) are presents. My desktop is completely empty.
Below some details, that I hope could help you to help me.
Thank’s in advance.

inxi -v7azy

System:
  Kernel: 6.6.10-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=f25908b5-1f7f-457d-b5af-7d47c201faf8 rw quiet splash apparmor=1
    security=apparmor udev.log_priority=3 ibt=off
    resume=/dev/disk/by-uuid/92a30798-9f6e-4f81-a5f8-f72c784e1019
  Desktop: GNOME v: 45.3 tk: GTK v: 3.24.39 wm: gnome-shell dm: GDM v: 45.0.1
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: PCSpecialist product: Standard v: Standard
    serial: <superuser required>
  Mobo: TongFang model: GM7AG0P v: Standard serial: <superuser required>
    UEFI: American Megatrends LLC. v: N.1.05A04 date: 02/25/2022
Battery:
  ID-1: BAT0 charge: 65.0 Wh (100.0%) condition: 65.0/91.6 Wh (70.9%)
    volts: 12.5 min: 11.6 model: standard type: Li-ion serial: <filter>
    status: full
Memory:
  System RAM: total: 64 GiB note: est. available: 62.54 GiB
    used: 4.98 GiB (8.0%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 12th Gen Intel Core i7-12700H bits: 64 type: MST AMCP
    arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 3
    microcode: 0x430
  Topology: cpus: 1x cores: 14 mt: 6 tpc: 2 st: 8 threads: 20 smt: enabled
    cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB
    L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB desc: 1x24 MiB
  Speed (MHz): avg: 424 high: 882 min/max: 400/4600:4700:3500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    15: 400 16: 400 17: 400 18: 882 19: 400 20: 400 bogomips: 107560
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts cat_l2 cdp_l2 clflush clflushopt clwb cmov constant_tsc cpuid
    cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est
    f16c flexpriority flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp
    hwp_act_window hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b
    movdiri msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pclmulqdq pdcm
    pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed
    rdt_a rdtscp rep_good sdbg sep serialize sha_ni smap smep smx
    split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip
    user_shstk vaes vme vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave
    xsavec xsaveopt xsaves xtopology xtpr
  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 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: Enhanced / Automatic IBRS, IBPB: conditional,
    RSB filling, PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: Tongfang Hongkong
    driver: i915 v: kernel arch: Gen-12.2 process: Intel 10nm built: 2021-22+
    ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:46a6
    class-ID: 0300
  Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q]
    vendor: Tongfang Hongkong driver: nvidia v: 545.29.06
    alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of
    2023-11; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2520 class-ID: 0300
  Device-3: Chicony FHD Webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:2 chip-ID: 04f2:b75c
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.10 with: Xwayland v: 23.2.3
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915 display-ID: :1
    screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: eDP-1 model: BOE Display 0x0a8f built: 2021 res: 2560x1440
    dpi: 171 gamma: 1.2 size: 381x214mm (15x8.43") diag: 437mm (17.2")
    ratio: 16:9 modes: 2560x1440
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: iris inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 23.3.3-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
    device-ID: 8086:46a6 memory: 61.08 GiB unified: yes
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio
    vendor: Tongfang Hongkong driver: snd_hda_intel v: kernel
    alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51c8
    class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio vendor: Tongfang Hongkong
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228e class-ID: 0403
  API: ALSA v: k6.6.10-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.0 status: off tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 2e:00.0 chip-ID: 8086:2725
    class-ID: 0280
  IF: wlp46s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Realtek RTL8125 2.5GbE vendor: Tongfang Hongkong driver: r8169
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 2f:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp47s0 state: down mac: <filter>
  IF-ID-1: vmnet20 state: unknown speed: N/A duplex: N/A mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:5 chip-ID: 8087:0032
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12 status: discoverable: no pairing: yes class-ID: 7c010c
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.64 TiB used: 2.25 TiB (61.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 3B2QGXA7 temp: 31.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 4B2QEXM7 temp: 29.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 195.18 GiB size: 191.05 GiB (97.89%)
    used: 76.22 GiB (39.9%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:3
    label: N/A uuid: f25908b5-1f7f-457d-b5af-7d47c201faf8
  ID-2: /boot/efi raw-size: 400 MiB size: 399.2 MiB (99.80%)
    used: 456 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:2 label: N/A
    uuid: 631A-EA79
  ID-3: /mnt/dati_pc raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 1.21 TiB (67.9%) fs: ext4 dev: /dev/nvme1n1p1 maj-min: 259:6 label: N/A
    uuid: 93d14898-6e42-4881-af15-e40434393393
  ID-4: /mnt/vm raw-size: 1.56 TiB size: 1.54 TiB (98.36%)
    used: 979.26 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:4
    label: N/A uuid: ec5f18a6-18df-4439-9075-ec61ba2791ae
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 67.05 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p4 maj-min: 259:5 label: N/A
    uuid: 92a30798-9f6e-4f81-a5f8-f72c784e1019
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 2-0:1 info: super-speed hub ports: 1 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 12 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: 3-5:2 info: Chicony FHD Webcam type: video driver: uvcvideo
    interfaces: 4 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 04f2:b75c class-ID: 0e02 serial: <filter>
  Device-2: 3-6:3 info: Integrated Express ITE Device(8291)
    type: keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 048d:6005 class-ID: 0300
  Device-3: 3-8:4 info: Integrated Express ITE Device(8291)
    type: keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 048d:ce00 class-ID: 0300
  Device-4: 3-10:5 info: Intel AX210 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0032 class-ID: e001
  Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 4-4:2 info: Realtek Card Reader type: mass storage
    driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 power: 800mA chip-ID: 0bda:0316 class-ID: 0806
    serial: <filter>
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 436 Uptime: 57m wakeups: 0 Init: systemd v: 255 default: graphical
  tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6 Packages: 1692
  pm: pacman pkgs: 1664 libs: 380 tools: gnome-software,pamac,yay pm: flatpak
  pkgs: 17 pm: snap pkgs: 11 Shell: Zsh v: 5.9 running-in: gnome-terminal
  inxi: 3.3.31

journalctl --boot=-1 --priority=3 --catalog --no-pager

gen 14 11:58:57 davide kernel: proc_thermal_pci 0000:00:04.0: error: proc_thermal_add, will continue
gen 14 11:58:58 davide kernel: 
gen 14 11:58:58 davide kernel: usbhid 3-6:1.0: couldn't find an input interrupt endpoint
gen 14 11:58:58 davide kernel: usbhid 3-8:1.0: couldn't find an input interrupt endpoint
gen 14 11:58:58 davide kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  545.29.06  Thu Nov 16 01:59:08 UTC 2023
gen 14 11:58:58 davide kernel: Bluetooth: hci0: No support for _PRR ACPI method
gen 14 11:58:58 davide kernel: iwlwifi 0000:2e:00.0: WRT: Invalid buffer destination
gen 14 11:58:59 davide kernel: iwlwifi 0000:2e:00.0: WRT: Invalid buffer destination
gen 14 11:58:59 davide kernel: iwlwifi 0000:2e:00.0: WRT: Invalid buffer destination
gen 14 11:59:00 davide systemd[1]: Failed to start pkgfile database update.
░░ Subject: A start job for unit pkgfile-update.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit pkgfile-update.service has finished with a failure.
░░ 
░░ The job identifier is 1259 and the job result is failed.
gen 14 11:59:06 davide dbus-broker-launch[1896]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.freedesktop.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.
gen 14 11:59:23 davide gdm-password][2491]: gkr-pam: unable to locate daemon control file
gen 14 11:59:23 davide dbus-broker-launch[2527]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.freedesktop.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.
gen 14 11:59:24 davide systemd[2499]: Failed to start Application launched by gnome-session-binary.
░░ 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 192 and the job result is failed.
gen 14 12:00:56 davide pulseaudio[2968]: Lost I/O connection in module "module-gsettings"
gen 14 12:00:59 davide dbus-broker-launch[4447]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.freedesktop.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.
gen 14 12:01:04 davide gdm-password][4838]: gkr-pam: unable to locate daemon control file
gen 14 12:01:04 davide dbus-broker-launch[4861]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.freedesktop.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.
gen 14 12:01:05 davide systemd[2499]: Failed to start Application launched by gnome-session-binary.
░░ 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 1256 and the job result is failed.

1 Like

“choose provider for dbus-units” prompt is empty (KDE)

3 Likes

Same here, with gnome. I just clicked on “choose” hoping to select the default…

System freezes after this update

Hi all,
after this update and select “dbus-broker” my system with kernel 6.7 freezes for about 20 seconds, then it works for about 3-5 seconds and then it freezes again for about 20 seconds and so on.

With kernel 6.6.x it works without any problems.
I see in journalctl this:

Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Loading theme configuration from "/usr/share/sddm/themes/breath/theme.conf"
Jan 14 17:45:45 manjaro64 systemd[1670]: Created slice User Core Session Slice.
Jan 14 17:45:45 manjaro64 systemd[1670]: Starting D-Bus User Message Bus...
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jan 14 17:45:45 manjaro64 systemd[1670]: Started D-Bus User Message Bus.
Jan 14 17:45:45 manjaro64 dbus-broker-launch[1684]: Ready
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Connected to the daemon.
Jan 14 17:45:45 manjaro64 sddm[635]: Message received from greeter: Connect
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Loading file:///usr/share/sddm/themes/breath/Main.qml...
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject: Cannot create children for a parent that is in a different thread.
                                              (Parent is QGuiApplication(0x7fffb71e5580), parent's thread is QThread(0x55ad054919c0), current thread is QThread(0x55ad056652d0)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject: Cannot create children for a parent that is in a different thread.
                                              (Parent is QGuiApplication(0x7fffb71e5580), parent's thread is QThread(0x55ad054919c0), current thread is QThread(0x55ad056652d0)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject: Cannot create children for a parent that is in a different thread.
                                              (Parent is QGuiApplication(0x7fffb71e5580), parent's thread is QThread(0x55ad054919c0), current thread is QThread(0x55ad056652d0)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Adding view for "DVI-I-1" QRect(0,0 1920x1080)
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Message received from daemon: Capabilities
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: Message received from daemon: HostName
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:45 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:46 manjaro64 sddm-greeter[1680]: file:///usr/share/sddm/themes/breath/Main.qml:465:13: Unable to assign [undefined] to QUrl
Jan 14 17:45:47 manjaro64 pipewire-media-session[1188]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner

System is the same with kernel 6.7

System:
  Kernel: 6.6.10-1-MANJARO arch: x86_64 bits: 64 Desktop: KDE Plasma
    v: 5.27.10 Distro: Manjaro Linux
Machine:
  Type: Desktop Mobo: MEDIONPC model: MS-7728 v: 2.0
    serial: <superuser required> BIOS: American Megatrends v: E7728MLN.208
    date: 08/15/2011
CPU:
  Info: quad core model: Intel Core i7-2600 bits: 64 type: MT MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 1893 min/max: 1600/3800 cores: 1: 3800 2: 1600 3: 1613
    4: 1600 5: 1736 6: 1600 7: 1600 8: 1600
Graphics:
  Device-1: NVIDIA GF116 [GeForce GT 545] driver: nouveau v: kernel
  Display: wayland server: X.org v: 1.21.1.10 with: Xwayland v: 23.2.3
    compositor: kwin_wayland driver: X: loaded: modesetting dri: nouveau
    gpu: nouveau resolution: 1920x1080
  API: EGL v: 1.5 drivers: nouveau,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 23.3.3-manjaro1.1
    renderer: NVCF
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    driver: snd_hda_intel
  Device-2: NVIDIA GF116 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.6.10-1-MANJARO status: kernel-api
  Server-1: PipeWire v: 1.0.0 status: active
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 465.77 GiB used: 79.87 GiB (17.1%)
  ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
  ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
Partition:
  ID-1: / size: 220.38 GiB used: 79.87 GiB (36.2%) fs: ext4 dev: /dev/sda1
Swap:
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 27.0 C mobo: N/A gpu: nouveau temp: 38.0 C
  Fan Speeds (rpm): N/A
Info:
  Processes: 255 Uptime: 0m Memory: total: 8 GiB available: 7.74 GiB
  used: 1.05 GiB (13.6%) Shell: Bash inxi: 3.3.31

can you help me, please

regards
caho

Update with no issues here, tho I selected dbus-daemon-units since it’s still supported.

hey @Rmano - did simply clicking ‘choose’ and proceeding with the update reveal any problems in pamac’s log?

also, can you check whether dbus-broker and/or dbus-daemon are installed?

ps: i just did sudo pacman -Syu to update and this prompts for the dbus choice

hmm, noticed something else unusual …
memory consumption has increased significantly since the update
system monitor → processes shows many processes which now use lots of memory e.g. Thunderbird 430 MiB, about 10 Chromium processes with 290 MiB each, Plasmashell 390MiB etc.

Hm. Can you please tell me where I can find the log?

pamac info dbus-broker say it’s installed (as a dependency of dbus-broker-units) so yes, it seems that it has chosen the default :wink:

As i said, i use MBR and i dont have EFI.

When i take a look at my Boot-Partition, i see the mkinitcpio.conf and also the fallback file is stored there.

I dont have enough space, even when i deactivate the fallback file. And im not sure if i want to disable it, because im not aware what the backstep is, i need atleast 180MB for only mkinitcpio.conf and this is a ridicules big size for such files.

Anyways i try to evade this problem as long as possible with the much smaller LTS Kernels… lucky that the previous Kernel 6.6 is LTS.

Having only 200MB for /boot is extremely bad idea. Don’t know where did you got this stupid idea from. Try to fix it if you want to have a working system. The best solution will be to move /boot back to the root / where it is by default in the first place instead of a separate partition.

2 Likes

Before i started Linux, I asked in a PC Forum (Computerbase.de) for tipps, how to install Manjaro and it was their suggestion how i should do to install Manjaro with custom install settings.

It was indeed a stupid idea/help and i regret it pretty soon… but i don’t wanted to reinstall my system after i realised it.

How can i archive this goal? Should i backup my files in /boot partition? And remove my partition after, and then i create a boot folder in root and just copy this and stuff into it?

Actually when i look into my root directory, at looks like a boot folder is already created in root, but i think its a mirror or something like that from my /boot partition… but when i click on my /boot partition in dolphin it leading me to the exact same path, its a little confusing for me.

Its the same story with my /home folder in root, it should be a partition, but it looks as a normal folder when i browse from root to home or boot it all looks like a folder.

I don’t get it, i normaly would expect a symlink in this situations.

Anyways in short, when i remove the /boot partition will / (root)>boot folder step in place and will instant boot from there or do i have to adjust some files (editing pathing) in Grub or Fstab maybe?

After the update I noticed audio drop outs on BlueTooth.

I rolled back from Kernel 6.6.10-1 to kernel 6.1.71-1 and the drop outs stopped.

System:

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12
Kernel Version: 6.1.71-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU N3540 @ 2.16GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics
Manufacturer: Notebook
Product Name: W54_W94_W955TU,-T,-C
System Version: Not Applicable