I recently saw a post with an all black login screen, except for asterisks that appeared as the password was typed. I remember going to the github page, where this specific configuration was shown as an example. I have been looking for this post and login manager for a while now, but I can't seem to find either.

Does anyone happen to know what I'm describing?

hi! i have been writing this wayland compositor for a while and its finally (nearly) ready for the 1.0 release! i want to package it for the aur so it is easier for others to install it. i am looking for someone that has some experience with packaging so i dont break anything. i am also using pretty primitive makefile and just copying files to /usr/bin etc. which is probably not that good, so looking for the best practices in that regard.

I've been using some software to optimize my battery life (powertop, auto-cpufreq and power-profile-daemon). I've found that using powertop gives me an additionnal 2h of battery life when I calibrate. The problem is that powertop isn't a service and I'm not sure how to use it.

Auto-cpufreq or power-profiles-daemon always runs as a service but powertop can't. If I reboot after a calibration, I lose it and go back to my old autonomy.

How is it supposed to be used?

Hey everyone!

I’m trying to configure my terminal so that when it opens, it shows only an **image (not ASCII)**, and when I run the `neofetch` command, I get my full system info.

I saw a video where the terminal shows only an image on startup, and when you run `neofetch`, it shows the regular system info. Here's the part I’m talking about:

[YouTube Video](https://youtu.be/RMViOyWbutE?feature=shared)

I’ve tried various methods, but whenever I open the terminal, it either doesn’t show the image or it shows both the image and the system info. What I want is for the terminal to only display the image at startup and then show the regular system info when I run `neofetch`.

Has anyone done this or know how to achieve this? Any help is greatly appreciated!

Thanks in advance!

My Desktop runs an i7-7700k and a GTX1080. I have an issue with suspend where it sometimes (to me, for no apparent reason) doesn't want to suspend and I can't figure out why. In those scenarios, the screen turns off, peripherals stop working, but the PC itself (fans, LEDs) keeps running and I have to turn off the PC by holding the power button.

Journal from an unsuccessful suspend action (stops at "Performing sleep operation 'suspend'...")

Dez 29 02:51:33 seid-pc systemd-sleep[73141]: Performing sleep operation 'suspend'...
Dez 29 02:51:33 seid-pc systemd-sleep[73141]: in suspend-then-hibernate operations or setups with encrypted home directories.
Dez 29 02:51:33 seid-pc systemd-sleep[73141]: This is not recommended, and might result in unexpected behavior, particularly
Dez 29 02:51:33 seid-pc systemd-sleep[73141]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Dez 29 02:51:33 seid-pc systemd[1]: Starting System Suspend...
Dez 29 02:51:33 seid-pc systemd[1]: nvidia-suspend.service: Consumed 913ms CPU time, 981.1M memory peak.
Dez 29 02:51:33 seid-pc systemd[1]: Finished NVIDIA system suspend actions.
Dez 29 02:51:33 seid-pc systemd[1]: nvidia-suspend.service: Deactivated successfully.
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "auto_null.monitor"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/opus_05
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSink/opus_05
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/faststream_duplex
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/faststream
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/sbc
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSink/sbc
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/opus_g
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSink/opus_g
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/aac
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSink/aac
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/aptx
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSink/aptx
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/aptx_hd
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSink/aptx_hd
Dez 29 02:51:32 seid-pc bluetoothd[1534]: Endpoint unregistered: sender=:1.215 path=/MediaEndpoint/A2DPSource/ldac
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kernel: snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 22
Dez 29 02:51:32 seid-pc kwin_wayland[1804]: kwin_core: Applying output config failed!
Dez 29 02:51:32 seid-pc plasmashell[1940]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kded6[1928]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc kdeconnectd[2144]: 2024-12-29T02:51:32 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"
Dez 29 02:51:32 seid-pc logger[73119]: <13>Dec 29 02:51:32 suspend: nvidia-suspend.service
Dez 29 02:51:32 seid-pc suspend[73119]: nvidia-suspend.service
Dez 29 02:51:32 seid-pc systemd[1]: Starting NVIDIA system suspend actions...
Dez 29 02:51:32 seid-pc systemd[1]: Reached target Sleep.
Dez 29 02:51:32 seid-pc wpa_supplicant[1595]: nl80211: deinit ifname=wlp5s0 disabled_11b_rates=0
Dez 29 02:51:32 seid-pc wpa_supplicant[1595]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 02:51:32 seid-pc wpa_supplicant[1595]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 02:51:32 seid-pc wpa_supplicant[1595]: nl80211: deinit ifname=p2p-dev-wlp5s0 disabled_11b_rates=0
Dez 29 02:51:32 seid-pc wpa_supplicant[1595]: p2p-dev-wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 02:51:32 seid-pc wpa_supplicant[1595]: p2p-dev-wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 02:51:32 seid-pc NetworkManager[1532]: <info>  [1735437092.3054] manager: NetworkManager state is now ASLEEP
Dez 29 02:51:32 seid-pc NetworkManager[1532]: <info>  [1735437092.3052] device (p2p-dev-wlp5s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dez 29 02:51:32 seid-pc NetworkManager[1532]: <info>  [1735437092.3024] device (wlp5s0): set-hw-addr: reset MAC address to 50:EB:71:F7:ED:97 (unmanage)
Dez 29 02:51:32 seid-pc NetworkManager[1532]: <info>  [1735437092.2702] device (wlp5s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dez 29 02:51:32 seid-pc NetworkManager[1532]: <info>  [1735437092.2700] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Dez 29 02:51:32 seid-pc systemd-logind[1537]: The system will suspend now!

Journal from a successful suspend action:

Dez 29 14:08:48 seid-pc systemd-logind[1051]: Operation 'suspend' finished.
Dez 29 14:08:48 seid-pc systemd[1]: Reached target Suspend.
Dez 29 14:08:48 seid-pc systemd[1]: Stopped target Sleep.
Dez 29 14:08:48 seid-pc systemd[1]: systemd-suspend.service: Consumed 1.894s CPU time, 48.1M memory peak.
Dez 29 14:08:48 seid-pc systemd[1]: Finished System Suspend.
Dez 29 14:08:48 seid-pc systemd[1]: systemd-suspend.service: Deactivated successfully.
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_input.usb-PreSonus_Studio_24c_SC1E20490905-00.analog-stereo"
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_input.usb-PreSonus_Studio_24c_SC1E20490905-00.analog-stereo"
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_input.usb-PreSonus_Studio_24c_SC1E20490905-00.analog-stereo"
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 14:08:48 seid-pc plasmashell[1464]: qml: 0
Dez 29 14:08:48 seid-pc plasmashell[1464]: qml: 0
Dez 29 14:08:48 seid-pc plasmashell[1464]: org.kde.pulseaudio: server_cb() called without info!
Dez 29 14:08:48 seid-pc systemd[1]: snapper-timeline.service: Deactivated successfully.
Dez 29 14:08:47 seid-pc systemd-helper[8727]: Running timeline for 'root'.
Dez 29 14:08:47 seid-pc systemd[1]: Started DBus interface for snapper.
Dez 29 14:08:47 seid-pc systemd[1]: Reached target Bluetooth Support.
Dez 29 14:08:47 seid-pc systemd[1229]: Reached target Bluetooth.
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Firmware Version: 132-3.24
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Boot Address: 0x24800
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Debug lock is disabled
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: API lock is enabled
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: OTP lock is enabled
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Secure boot is enabled
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Device revision is 1
Dez 29 14:08:46 seid-pc kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Dez 29 14:08:46 seid-pc systemd[1]: Starting DBus interface for snapper...
Dez 29 14:08:46 seid-pc systemd[1]: Stopped target Bluetooth Support.
Dez 29 14:08:46 seid-pc systemd[1]: Started Load/Save RF Kill Switch Status.
Dez 29 14:08:46 seid-pc bluetoothd[1048]: Battery Provider Manager destroyed
Dez 29 14:08:46 seid-pc systemd[1]: Starting Load/Save RF Kill Switch Status...
Dez 29 14:08:46 seid-pc systemd[1]: Started Timeline of Snapper Snapshots.
Dez 29 14:08:46 seid-pc systemd-sleep[8654]: System returned from sleep operation 'suspend'.
Dez 29 14:08:46 seid-pc dbus-broker[1045]: A security policy denied :1.5 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.35.
Dez 29 14:08:46 seid-pc kernel: PM: suspend exit
Dez 29 14:08:46 seid-pc kernel: random: crng reseeded on system resumption
Dez 29 14:08:46 seid-pc kernel: Restarting tasks ... done.
Dez 29 14:08:46 seid-pc kernel: OOM killer enabled.
Dez 29 14:08:46 seid-pc kernel: usb 1-14: reset full-speed USB device number 6 using xhci_hcd
Dez 29 14:08:46 seid-pc kernel: ata1.00: Enabling discard_zeroes_data
Dez 29 14:08:46 seid-pc kernel: ata1.00: configured for UDMA/133
Dez 29 14:08:46 seid-pc kernel: ata1.00: supports DRM functions and may not be fully accessible
Dez 29 14:08:46 seid-pc kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Dez 29 14:08:46 seid-pc kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Dez 29 14:08:46 seid-pc kernel: sd 0:0:0:0: [sda] Starting disk
Dez 29 14:08:46 seid-pc kernel: ata4.00: configured for UDMA/133
Dez 29 14:08:46 seid-pc kernel: ata4.00: supports DRM functions and may not be fully accessible
Dez 29 14:08:46 seid-pc kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Dez 29 14:08:46 seid-pc kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Dez 29 14:08:46 seid-pc kernel: sd 3:0:0:0: [sdc] Starting disk
Dez 29 14:08:46 seid-pc kernel: ata4.00: supports DRM functions and may not be fully accessible
Dez 29 14:08:46 seid-pc kernel: ata1.00: supports DRM functions and may not be fully accessible
Dez 29 14:08:46 seid-pc kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Dez 29 14:08:46 seid-pc kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Dez 29 14:08:46 seid-pc kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Dez 29 14:08:46 seid-pc kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Dez 29 14:08:46 seid-pc kernel: ata4.00: Entering active power mode
Dez 29 14:08:46 seid-pc kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dez 29 14:08:46 seid-pc kernel: ata5: SATA link down (SStatus 4 SControl 300)
Dez 29 14:08:46 seid-pc kernel: ata3: SATA link down (SStatus 4 SControl 300)
Dez 29 14:08:46 seid-pc kernel: ata1.00: Entering active power mode
Dez 29 14:08:46 seid-pc kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dez 29 14:08:46 seid-pc kernel: usb 1-11: reset full-speed USB device number 5 using xhci_hcd
Dez 29 14:08:46 seid-pc kernel: serial 00:01: activated
Dez 29 14:08:46 seid-pc kernel: ACPI: EC: event unblocked
Dez 29 14:08:46 seid-pc kernel: ACPI: EC: interrupt unblocked
Dez 29 14:08:46 seid-pc kernel: ACPI: PM: Waking up from system sleep state S3
Dez 29 14:08:46 seid-pc kernel: CPU7 is up
Dez 29 14:08:46 seid-pc kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Dez 29 14:08:46 seid-pc kernel: CPU6 is up
Dez 29 14:08:46 seid-pc kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Dez 29 14:08:46 seid-pc kernel: CPU5 is up
Dez 29 14:08:46 seid-pc kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Dez 29 14:08:46 seid-pc kernel: CPU4 is up
Dez 29 14:08:46 seid-pc kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Dez 29 14:08:46 seid-pc kernel: CPU3 is up
Dez 29 14:08:46 seid-pc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Dez 29 14:08:46 seid-pc kernel: CPU2 is up
Dez 29 14:08:46 seid-pc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Dez 29 14:08:46 seid-pc kernel: CPU1 is up
Dez 29 14:08:46 seid-pc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Dez 29 14:08:46 seid-pc kernel: Enabling non-boot CPUs ...
Dez 29 14:08:46 seid-pc kernel: ACPI: PM: Restoring platform NVS memory
Dez 29 14:08:46 seid-pc kernel: ACPI: EC: EC started
Dez 29 14:08:46 seid-pc kernel: ACPI: PM: Low-level resume complete
Dez 29 14:08:46 seid-pc kernel: smpboot: CPU 7 is now offline
Dez 29 14:08:46 seid-pc kernel: smpboot: CPU 6 is now offline
Dez 29 14:08:46 seid-pc kernel: smpboot: CPU 5 is now offline
Dez 29 14:08:46 seid-pc kernel: smpboot: CPU 4 is now offline
Dez 29 14:08:46 seid-pc kernel: smpboot: CPU 3 is now offline
Dez 29 14:08:46 seid-pc kernel: smpboot: CPU 2 is now offline
Dez 29 14:08:46 seid-pc kernel: smpboot: CPU 1 is now offline
Dez 29 14:08:46 seid-pc kernel: Disabling non-boot CPUs ...
Dez 29 14:08:46 seid-pc kernel: ACPI: PM: Saving platform NVS memory
Dez 29 14:08:46 seid-pc kernel: ACPI: EC: EC stopped
Dez 29 14:08:46 seid-pc kernel: ACPI: EC: event blocked
Dez 29 14:08:46 seid-pc kernel: ACPI: PM: Preparing to enter system sleep state S3
Dez 29 14:08:46 seid-pc kernel: ACPI: EC: interrupt blocked
Dez 29 14:08:46 seid-pc kernel: ata4.00: Entering standby power mode
Dez 29 14:08:46 seid-pc kernel: ata6.00: Entering standby power mode
Dez 29 14:08:46 seid-pc kernel: sd 5:0:0:0: [sdd] Synchronizing SCSI cache
Dez 29 14:08:46 seid-pc kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
Dez 29 14:08:46 seid-pc kernel: ata2.00: Entering standby power mode
Dez 29 14:08:46 seid-pc kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Dez 29 14:08:46 seid-pc kernel: ata1.00: Entering standby power mode
Dez 29 14:08:46 seid-pc kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dez 29 14:08:46 seid-pc kernel: e1000e: EEE TX LPI TIMER: 00000011
Dez 29 14:08:46 seid-pc kernel: serial 00:01: disabled
Dez 29 14:08:46 seid-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dez 29 14:08:46 seid-pc kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Dez 29 14:08:46 seid-pc kernel: Freezing remaining freezable tasks
Dez 29 14:08:46 seid-pc kernel: OOM killer disabled.
Dez 29 14:08:46 seid-pc kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Dez 29 14:08:46 seid-pc kernel: Freezing user space processes
Dez 29 13:54:07 seid-pc kernel: Filesystems sync: 1.255 seconds
Dez 29 13:54:06 seid-pc kernel: PM: suspend entry (deep)
Dez 29 13:54:06 seid-pc systemd-sleep[8654]: Performing sleep operation 'suspend'...
Dez 29 13:54:06 seid-pc systemd-sleep[8654]: in suspend-then-hibernate operations or setups with encrypted home directories.
Dez 29 13:54:06 seid-pc systemd-sleep[8654]: This is not recommended, and might result in unexpected behavior, particularly
Dez 29 13:54:06 seid-pc systemd-sleep[8654]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Dez 29 13:54:06 seid-pc systemd[1]: Starting System Suspend...
Dez 29 13:54:06 seid-pc systemd[1]: nvidia-suspend.service: Consumed 909ms CPU time, 1006M memory peak.
Dez 29 13:54:06 seid-pc systemd[1]: Finished NVIDIA system suspend actions.
Dez 29 13:54:06 seid-pc systemd[1]: nvidia-suspend.service: Deactivated successfully.
Dez 29 13:54:05 seid-pc kernel: [UFW BLOCK] IN=enp0s31f6 OUT= MAC= SRC=fe80:0000:0000:0000:ec8e:5188:1f21:0c8a DST=ff12:0000:0000:0000:0000:0000:0000:8384 LEN=318 TC=0 HOPLIMIT=1 FLOWLBL=440474 PROTO=UDP SPT=41778 DPT=21027 LEN=278 
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "auto_null.monitor"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Dez 29 13:54:05 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Dez 29 13:54:05 seid-pc wireplumber[1246]: wp-event-dispatcher: <WpAsyncEventHook:0x6081707536f0> failed: failed to activate item: Object activation aborted: proxy destroyed
Dez 29 13:54:05 seid-pc plasmashell[1464]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "alsa_input.usb-PreSonus_Studio_24c_SC1E20490905-00.analog-stereo"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "alsa_input.usb-PreSonus_Studio_24c_SC1E20490905-00.analog-stereo"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "alsa_input.usb-PreSonus_Studio_24c_SC1E20490905-00.analog-stereo"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "alsa_input.usb-PreSonus_Studio_24c_SC1E20490905-00.analog-stereo"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc kdeconnectd[1622]: 2024-12-29T13:54:05 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/opus_05
Dez 29 13:54:05 seid-pc kded6[1442]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink/opus_05
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/faststream_duplex
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/faststream
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/sbc
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink/sbc
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/opus_g
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink/opus_g
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/aac
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink/aac
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/aptx
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink/aptx
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/aptx_hd
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSink/aptx_hd
Dez 29 13:54:05 seid-pc bluetoothd[1048]: Endpoint unregistered: sender=:1.34 path=/MediaEndpoint/A2DPSource/ldac
Dez 29 13:54:05 seid-pc kernel: snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 0
Dez 29 13:54:05 seid-pc wpa_supplicant[1109]: nl80211: deinit ifname=wlp5s0 disabled_11b_rates=0
Dez 29 13:54:05 seid-pc wpa_supplicant[1109]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 13:54:05 seid-pc wpa_supplicant[1109]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 13:54:05 seid-pc logger[8631]: <13>Dec 29 13:54:05 suspend: nvidia-suspend.service
Dez 29 13:54:05 seid-pc suspend[8631]: nvidia-suspend.service
Dez 29 13:54:05 seid-pc wpa_supplicant[1109]: nl80211: deinit ifname=p2p-dev-wlp5s0 disabled_11b_rates=0
Dez 29 13:54:05 seid-pc wpa_supplicant[1109]: p2p-dev-wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 13:54:05 seid-pc wpa_supplicant[1109]: p2p-dev-wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dez 29 13:54:05 seid-pc systemd[1]: Starting NVIDIA system suspend actions...
Dez 29 13:54:05 seid-pc systemd[1]: Reached target Sleep.
Dez 29 13:54:05 seid-pc NetworkManager[1046]: <info>  [1735476845.1289] manager: NetworkManager state is now ASLEEP
Dez 29 13:54:05 seid-pc NetworkManager[1046]: <info>  [1735476845.1288] device (p2p-dev-wlp5s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dez 29 13:54:05 seid-pc NetworkManager[1046]: <info>  [1735476845.1261] device (wlp5s0): set-hw-addr: reset MAC address to 50:EB:71:F7:ED:97 (unmanage)
Dez 29 13:54:05 seid-pc NetworkManager[1046]: <info>  [1735476845.1002] device (wlp5s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dez 29 13:54:05 seid-pc NetworkManager[1046]: <info>  [1735476845.1001] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Dez 29 13:54:05 seid-pc systemd-logind[1051]: The system will suspend now!

I'm going to implement a snapshots/backup solution tomorrow and wanted to ask about options before I make my final decision. So far I'm thinking about going with timeshift + grub-btrfs for daily snapshots & clonding my SSD to an external using clonezilla.

Other options I've heard of here are snapper/btrfs-assistant, borg, restic, dd, rsync, etc.

With so many options what solution do you all go with and what made you choose it over the others?

I have a new laptop with the Mediatek MT7922 WiFi/Bluetooth card.

With this card i can't connect to a 5G network, which is a known problem.

According to this solution i put the latest firmware in /lib/firmware/mediatek/mt7922 to solve this...

Problem is the kernel (6.12.7-arch1-1) recognizes the card as mt7921e and loads the kerneldriver.

ethtool -i wlan0
driver: mt7921e
version: 6.12.7-arch1-1
firmware-version: ____000000-20241106163310
expansion-rom-version:  
bus-info: 0000:03:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Question; How to make this laptop use the firmware rather than the kernel driver?

On my t14 the mute switch works fine but the light never turns off unless i manually set the value 0. Is there a missing firmware or driver that i dont have which is causing this? Any help will be appreciated.

Sometimes when invoking the start menu, plasma freezes, it also (always) happens whenever I go to the "get new" menu for things like wallpapers or themes.
I'm 90% sure it's not a hardware problem, I'm on a pretty decent computer, the only potential problem might be Nvidia. The issue appears on both X11 and wayland
UPDATE:
After changing some things I do not remember, the freezing that happens when using the "get new" menu now affects only the settings and the menu itself, not the rest of the desktop, it still is a problem

Hi everyone,

I’m having a problem with DaVinci Resolve on my ArchLinux setup, and I hope someone can help me figure this out.

The issue happens when I try to import a video into DaVinci Resolve. As soon as I do, the monitors flicker a couple of times, and then everything freezes: the monitors stay static, and the PC stops responding entirely, forcing me to do a hard reset.

Here’s my setup:

• Ryzen 3 3200G with integrated Radeon Vega graphics.
• 16 GB RAM (HyperX Fury, two sticks).
• MSI B450M PRO-VDH MAX motherboard.

I’m using the open-source AMDGPU drivers along with OpenCL (rocm-opencl-runtime), and I launch DaVinci Resolve with the ROC_ENABLE_PRE_VEGA=1 environment variable. Additionally, I downgraded the following packages to version 24.2.7 to fix random freezes with Vega:

• mesa
• lib32-mesa
• vulkan-radeon
• lib32-vulkan-radeon

Has anyone experienced a similar issue or knows how to fix this? Could it be related to OpenCL, the drivers, or something else? Any advice or suggestions would be greatly appreciated.

- It looks like this: https://imgur.com/a/zgDSbwF

- The system is updated and using propietary drivers, with the following GPUs:

CPU: 13th Gen Intel(R) Core(TM) i5-13420H (12) @ 4.60 GHz

GPU 1: NVIDIA GeForce RTX 3050 6GB Laptop GPU [Discrete]

GPU 2: Intel UHD Graphics @ 1.40 GHz [Integrated]

- The secondary monitor: https://imgur.com/a/VLSmG9s (main one is 144hz)

- I wanted to switch to wayfire, but this issue is blocking me. It works normally in X11 thought, so is not urgent. If anything else is needed, don't mind bothering.

This commit adds the feature I'm looking for, but it's not been accepted for 3 whole years. Why?

Do I wait this out or there's a fix I need to do?

! Formatting /dev/sda in
5...4...3...2...1Wiping partitions and metadata: /dev/sda
Creating partition: /dev/sda
Starting installation...
Waiting for time sync (timedatectl show) to complete.)
Time synchronization not completing, while you wait - check the docs for workarounds: https://archinstall.readthedocs.io/

[SOLVED]
I used Chrony

Context:

I'm a new Arch user, I migrated from Mint after much thought and practice. Everything has been going smoothly so far, I was able to install 90% of the things I wanted without much issue (not everything yet). However there is this big glaring issue that I can't seem to resolve.

My CPU and GPU are Intel Core i5-4460, and Radeon R9 390.

I basically installed these packages in this order. I installed other things too, but they are unrelated to audio.

1. plasma-desktop
2. sddm
3. konsole
4. plasma-pa
5. firefox
6. pipewire-pulse

To my knowledge, all you have to do install Pipewire and enable pipewire-pulse.service, which is what I did.

Issue:

On reboot, my headphones that I plug into the "Line Out" port on the motherboard is not recognized, and consequently it also plays no sound. I did install KDE which does install some sound packages of its own, but I'm not sure if it's a KDE specific issue. Also to note, there is another device that gets recognized without issue (probably), my HDMI cable to my monitor, but it doesn't have a speaker attached anyway so it's pointless that it's recognized.

However, there is a weird workaround that "fixes" this issue. When I either restart the systemd wireplumber.service or pipewire.service, the problem fixes itself and my headphones start working as normal. When I restart Wireplumber, the sound comes back immediately. If I restart pipewire, it takes a second. I assume what's happening is that the Pipewire service also restarts Wireplumber on my behalf.

So my question is, how should I go about fixing or further diagnosing this issue? If I can't, how do I find a suitable workaround that deploys automatically? I tried creating a simple systemctl service that runs the command, but every script that I tried writing I guess runs it too fast to have any effect on the issue.

I could probably using some other audio setup, but I think this setup should work, because on Mint I think I also had pipewire-pulse set up. I'm only vaguely sure, because I never really touched it before.

The biggest clue that I have is this: When I run the command pactl list short, BEFORE Wireplumber is restarted, I get this output (truncated, I can post full if needed):

...
536870914       module-device-restore
536870915       module-stream-restore
50      alsa_output.pci-0000_01_00.1.hdmi-stereo-extra5 PipeWire        s32le 2ch 48000Hz       IDLE
50      alsa_output.pci-0000_01_00.1.hdmi-stereo-extra5.monitor PipeWire        s32le 2ch 48000Hz       IDLE
32      PipeWire        kwin_wayland
33      PipeWire        wireplumber
...

However, AFTER the issue is solved using systemctl --user restart wireplumber, this is its output (also truncated):

...
536870914       module-device-restore
536870915       module-stream-restore
109     alsa_output.pci-0000_01_00.1.hdmi-stereo-extra5 PipeWire        s32le 2ch 48000Hz       SUSPENDED
110     alsa_output.pci-0000_00_1b.0.analog-stereo      PipeWire        s32le 2ch 48000Hz       SUSPENDED
109     alsa_output.pci-0000_01_00.1.hdmi-stereo-extra5.monitor PipeWire        s32le 2ch 48000Hz       SUSPENDED
110     alsa_output.pci-0000_00_1b.0.analog-stereo.monitor      PipeWire        s32le 2ch 48000Hz       SUSPENDED
32      PipeWire        kwin_wayland
55      PipeWire        pipewire
...

Nothing else has given me anything substantial to work with, but that might be my inexperience with audio libraries talking.

What I tried already, but didn't work:

• Wiping all configuration files. Seeing this is a new install, this is expected.

• Scouring the wiki pages on the topic, both KDE and Pipewire. Most relevant entry seems to be 5.1.26, but I tried searching my system for the $XDG_RUNTIME_DIR env var and found nothing. On some Arch forum posts, I found some people who had this variable overridden by other packages (for some reason). Topic 5.1.27 also seemed vaguely related, but nothing happened after trying.

• Disabling the HDMI audio device through Wireplumber configuration JSON file. While disabling it works nicely, it seems to be unrelated.

• Checking to see if the regular Pulseaudio package was being used. It wasn't being used, it was properly running pipewire-pulse.

• Logging into Plasma using X instead of Wayland. Nothing changes.

If this can't be resolved, I need a way to run the command systemctl --user restart wireplumber command after EVERYTHING else has finished running and I've also logged in (I guess). Is there a good way to do that? I don't want to run this manually every time.

Thank you for reading if you did.

This has been driving me a little crazy and I don't know how to fix it. I need otf-font-awesome for the Waybar icons but it kinda messes up the asterisk font whenever a QT app asks for a password. Is there a way to revert back to normal?

Here's how it looks

Hi to all!

After updating the kernel to 6.12.7-arch1-1 I get the following trace event raised by the kernel. What should I do? Apparently the system works correctly ...

------------[ cut here ]------------

dic 28 21:19:48 D9330 kernel: WARNING: CPU: 3 PID: 193 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: Modules linked in: xe(+) drm_ttm_helper gpu_sched drm_suballoc_helper drm_gpuvm drm_exec spi_ljca usb_ljca uas usb_storage i915 i2c_algo_bit serio_raw drm_bud>

dic 28 21:19:48 D9330 kernel: CPU: 3 UID: 0 PID: 193 Comm: (udev-worker) Not tainted 6.12.7-arch1-1 #1 9e77c5d99557be92f482a3ac6317d887bb3ffaf9

dic 28 21:19:48 D9330 kernel: Hardware name: Dell Inc. Latitude 9330/0RN079, BIOS 1.25.0 11/12/2024

dic 28 21:19:48 D9330 kernel: RIP: 0010:trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: Code: 89 ea 0f 83 3b 04 00 00 e8 44 db ff ff 84 c0 74 10 8b 0c 24 48 c7 c0 fe ff ff ff 48 d3 c0 49 21 c6 4d 85 f6 0f 84 d6 fe ff ff <0f> 0b bb 01 00 00 00 41 >

dic 28 21:19:48 D9330 kernel: RSP: 0018:ffffa1ed80897990 EFLAGS: 00010206

dic 28 21:19:48 D9330 kernel: RAX: ffffffffffffffdf RBX: ffffffffc0db1731 RCX: 0000000000000005

dic 28 21:19:48 D9330 kernel: RDX: 0000000000000002 RSI: 0000000000000001 RDI: ffffffffc0db1727

dic 28 21:19:48 D9330 kernel: RBP: ffffffffc0db1640 R08: 0000000000000039 R09: 0000000000000000

dic 28 21:19:48 D9330 kernel: R10: 0000000000000076 R11: 000000000000004e R12: 00000000000000f2

dic 28 21:19:48 D9330 kernel: R13: ffffffffc0db2760 R14: 0000000000000018 R15: 0000000000000000

dic 28 21:19:48 D9330 kernel: FS: 000074348b53b880(0000) GS:ffff90a8bf580000(0000) knlGS:0000000000000000

dic 28 21:19:48 D9330 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

dic 28 21:19:48 D9330 kernel: CR2: 000074348bfb2de0 CR3: 00000001019b6000 CR4: 0000000000f50ef0

dic 28 21:19:48 D9330 kernel: PKRU: 55555554

dic 28 21:19:48 D9330 kernel: Call Trace:

dic 28 21:19:48 D9330 kernel: <TASK>

dic 28 21:19:48 D9330 kernel: ? trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: ? __warn.cold+0x93/0xf6

dic 28 21:19:48 D9330 kernel: ? trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: ? report_bug+0xff/0x140

dic 28 21:19:48 D9330 kernel: ? handle_bug+0x58/0x90

dic 28 21:19:48 D9330 kernel: ? exc_invalid_op+0x17/0x70

dic 28 21:19:48 D9330 kernel: ? asm_exc_invalid_op+0x1a/0x20

dic 28 21:19:48 D9330 kernel: ? trace_event_raw_init+0x159/0x660

dic 28 21:19:48 D9330 kernel: event_init+0x28/0x70

dic 28 21:19:48 D9330 kernel: trace_module_notify+0x1a4/0x260

dic 28 21:19:48 D9330 kernel: notifier_call_chain+0x5a/0xd0

dic 28 21:19:48 D9330 kernel: blocking_notifier_call_chain_robust+0x65/0xc0

dic 28 21:19:48 D9330 kernel: load_module+0x1822/0x1cf0

dic 28 21:19:48 D9330 kernel: ? vmap+0x83/0xe0

dic 28 21:19:48 D9330 kernel: ? __vunmap_range_noflush+0x325/0x470

dic 28 21:19:48 D9330 kernel: ? init_module_from_file+0x89/0xe0

dic 28 21:19:48 D9330 kernel: init_module_from_file+0x89/0xe0

dic 28 21:19:48 D9330 kernel: idempotent_init_module+0x11e/0x310

dic 28 21:19:48 D9330 kernel: __x64_sys_finit_module+0x5e/0xb0

dic 28 21:19:48 D9330 kernel: do_syscall_64+0x82/0x190

dic 28 21:19:48 D9330 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: ? do_sys_openat2+0x9c/0xe0

dic 28 21:19:48 D9330 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: ? do_syscall_64+0x8e/0x190

dic 28 21:19:48 D9330 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e

dic 28 21:19:48 D9330 kernel: RIP: 0033:0x74348bd321fd

dic 28 21:19:48 D9330 kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 >

dic 28 21:19:48 D9330 kernel: RSP: 002b:00007fffdcc10108 EFLAGS: 00000246 ORIG_RAX: 0000000000000139

dic 28 21:19:48 D9330 kernel: RAX: ffffffffffffffda RBX: 000059053b8b9980 RCX: 000074348bd321fd

dic 28 21:19:48 D9330 kernel: RDX: 0000000000000004 RSI: 000074348b53505d RDI: 0000000000000024

dic 28 21:19:48 D9330 kernel: RBP: 00007fffdcc101c0 R08: 0000000000000001 R09: 00007fffdcc10150

dic 28 21:19:48 D9330 kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 000074348b53505d

dic 28 21:19:48 D9330 kernel: R13: 0000000000020000 R14: 000059053b8ba300 R15: 000059053b8bafa0

dic 28 21:19:48 D9330 kernel: </TASK>

dic 28 21:19:48 D9330 kernel: ---[ end trace 0000000000000000 ]---

dic 28 21:19:48 D9330 kernel: event xe_bo_move has unsafe dereference of argument 4

dic 28 21:19:48 D9330 kernel: print_fmt: "move_lacks_source:%s, migrate object %p [size %zu] from %s to %s device_id:%s", REC->move_lacks_source ? "yes" : "no", REC->bo, REC->size, xe_mem_>

Is there any way to install mysql in arch? i dont want mariadb and other db forks

when i install latte-dock from the terminal, it says target not found. how to fix?

Hi there, relatively new to arch, looking for help plz.

My ultimate goal is to get to play a game called "Clonk". I found an AUR for LegacyClonk, here: https://aur.archlinux.org/packages/legacyclonk-git

As noted by the latest comment, the build file needed some editing, so i inserted the latest release and tried a simple "makpkg -si"

At first I got an error that sdl2_mixer was missing. "yay -S sdl2_mixer" solved that for me.

then came the following error:

[xxx@xxx clonk_rage-git]$ makepkg -si
==> Erstelle Paket: clonk_rage-git r1635.90570100-1 (So 29 Dez 2024 00:40:58 CET)
==> Prüfe Laufzeit-Abhängigkeiten...
==> Prüfe Buildtime-Abhängigkeiten...
==> Empfange Quellen...
  -> Aktualisiere das legacyclonk-git git Repo...
  -> lc_content.zip gefunden
==> Überprüfe source Dateien mit md5sums...
    legacyclonk-git ... Übersprungen
    lc_content.zip ... Übersprungen
==> Entpacke Quellen...
  -> Erstelle Arbeitskopie des legacyclonk-git git Repos...
Setze Branch 'makepkg' neu
  -> Entpacke lc_content.zip mit bsdtar
==> Beginne prepare()...
==> Beginne pkgver()...
==> Entferne existierendes $pkgdir/ Verzeichnis...
==> Beginne build()...
-- Build spdlog: 1.14.1
-- Build type: RelWithDebInfo
CMake Error at CMakeLists.txt:456 (find_package):
  Could not find a package configuration file provided by "miniupnpc" with
  any of the following names:

    miniupnpcConfig.cmake
    miniupnpc-config.cmake

  Add the installation prefix of "miniupnpc" to CMAKE_PREFIX_PATH or set
  "miniupnpc_DIR" to a directory containing one of the above files.  If
  "miniupnpc" provides a separate development package or SDK, be sure it has
  been installed.


-- Configuring incomplete, errors occurred!
==> FEHLER: Ein Fehler geschah in build().
    Breche ab...
[xxx@xxx clonk_rage-git]$ 

I thought that maybe also a simple "yay -S miniupnpc" would help, but nope, same error.

Couldn't find a miniupnpcConfig.cmake or miniupnpc-config.cmake on my machine.

Downloaded and compiled miniupnpc by hand and altered "miniupnpc_DIR" to that directory (which contained a miniupnpc-config.cmake), as per error-instructions, but still same error.

Any help would be apprechiated

I currently have a 240Gb NVME drive on my computer, which is currently partitioned as follows: / - 50Gb and /home - 190Gb. SWAP is in the 8Gb file on the / partition. The file system is ext4, unencrypted. The /home/user directory is managed by systemd-homed, which is encrypted and in turn formatted with the btrfs file system.

The plan is to add a 120Gb SSD. So the computer would have a total of 240Gb NVME and 120Gb SSD. In addition, the plan is to start using / partition snapshots (for Archlinux upgrades) and disk encryption. systemd-homed would continue to be used, the new size of the / partition could be 60Gb and the remaining 320Gb is used for /home.

Which file systems to use ? Would it make sense to use btrfs for the / partition ? Can the /home partition be used virtually over NVME and SSD at the same time ? Should I encrypt both physical disks separately or just the / partition, assuming systemd-homed uses encryption anyway ? Which methods could I use and in which order ? Thank you in advance !

Hi, I recently noticed that my USB drives weren't registering at all when plugged into either of my laptops USB A ports (USB C works, I tested with a different pen drive). I did some research and having recently been testing out tlp to try and improve my battery life I discovered that that is a common cause. I uninstalled TLP and reverted back to my default GRUB, rebooted and have still had no success.

I've tried to follow other peoples fixes but running dmesg -w or journalctl -f and inserting the drive shows no activity at all. If anyone has any ideas what this could be I'd be massively grateful!

On my t14 the mute switch works fine but the light never turns off unless i manually set the value 0. Is there a missing firmware or driver that i dont have which is causing this? Any help will be appreciated.