$ garuda-inxi
System:
Kernel: 6.6.33-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=3caa4a96-5787-457b-817a-8117f05250c4 rw rootflags=subvol=@
cryptdevice=UUID=ec3ee267-8732-4cc4-8960-c39fbbf5c306:luks-ec3ee267-8732-4cc4-8960-c39fbbf5c306
root=/dev/mapper/luks-ec3ee267-8732-4cc4-8960-c39fbbf5c306
rd.udev.log_priority=3 vt.global_cursor_default=0
resume=/dev/mapper/luks-22d6ffdc-91a9-4c97-ac75-1f30bca3e10c loglevel=1
quiet ibt=off
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
with: xfce4-panel tools: xfce4-screensaver avail: xautolock vt: 7
dm: LightDM v: 1.32.0 Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: MSI product: MS-7917 v: 1.0
serial: <superuser required>
Mobo: MSI model: Z97 GAMING 5 (MS-7917) v: 1.0
serial: <superuser required> uuid: <superuser required>
UEFI: American Megatrends v: 1.13 date: 02/16/2016
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
Info: model: Intel Core i7-4790K 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 cores: 4 tpc: 2 threads: 8 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: 3012 high: 4000 min/max: 800/4000 scaling:
driver: intel_cpufreq governor: schedutil cores: 1: 3998 2: 3998 3: 4000
4: 800 5: 4000 6: 4000 7: 800 8: 2500 bogomips: 64030
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD RV790 [Radeon HD 4890] vendor: ASUSTeK driver: radeon
v: kernel alternate: amdgpu arch: TeraScale code: R6xx/RV6xx/RV7xx
process: TSMC 55-65nm built: 2005-13 pcie: gen: 2 speed: 5 GT/s lanes: 16
ports: active: HDMI-A-1 off: DVI-I-1 empty: DIN-1,VGA-1 bus-ID: 01:00.0
chip-ID: 1002:9460 class-ID: 0300 temp: 65.0 C
Display: x11 server: X.Org v: 21.1.13 compositor: xfwm4 v: 4.18.0 driver:
X: loaded: radeon unloaded: modesetting alternate: fbdev,vesa dri: r600
gpu: radeon display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
s-diag: 583mm (22.95")
Monitor-1: DVI-I-1 mapped: DVI-0 note: disabled model: HP E243i
serial: <filter> built: 2019 res: N/A dpi: 94 gamma: 1.2
size: 518x324mm (20.39x12.76") diag: 611mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-0 pos: primary model: ViewSonic VX2858Sml
serial: <filter> built: 2014 res: 1920x1080 hz: 60 dpi: 79 gamma: 1.2
size: 621x341mm (24.45x13.43") diag: 708mm (27.9") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: Vulkan v: 1.3.279 layers: 9 device: 0 type: cpu name: llvmpipe (LLVM
17.0.6 256 bits) driver: mesa llvmpipe v: 24.1.1-arch1.1 (LLVM 17.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib
API: OpenGL Message: Unable to show GL data. glxinfo is missing.
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: AMD RV770 HDMI Audio [Radeon HD 4850/4870] vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 1002:aa30 class-ID: 0403
API: ALSA v: k6.6.33-1-lts status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack 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: 02:00.0 chip-ID: 1969:e091 class-ID: 0200
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f020
bus-ID: 00:1f.2 chip-ID: 8086:2822 rev: class-ID: 0104
Supported mdraid levels: raid1
Device-1: md124 maj-min: 9:124 type: mdraid level: mirror status: active
size: 931.51 GiB
Info: report: 2/2 UU blocks: 976759808 chunk-size: N/A
Components: Online:
0: sdd maj-min: 8:48 size: 931.51 GiB
1: sdc maj-min: 8:32 size: 931.51 GiB
Device-2: md125 maj-min: 9:125 type: mdraid level: N/A status: inactive
size: N/A
Info: report: N/A blocks: 5552 chunk-size: N/A
Components: Online: N/A Spare:
0: sdc maj-min: 8:32 size: 931.51 GiB state: S
1: sdd maj-min: 8:48 size: 931.51 GiB state: S
Device-3: md126 maj-min: 9:126 type: mdraid level: mirror status: active
size: 931.51 GiB
Info: report: 2/2 UU blocks: 976759808 chunk-size: N/A
Components: Online:
0: sdb maj-min: 8:16 size: 931.51 GiB
1: sda maj-min: 8:0 size: 931.51 GiB
Device-4: md127 maj-min: 9:127 type: mdraid level: N/A status: inactive
size: N/A
Info: report: N/A blocks: 5552 chunk-size: N/A
Components: Online: N/A Spare:
0: sdb maj-min: 8:16 size: 931.51 GiB state: S
1: sda maj-min: 8:0 size: 931.51 GiB state: S
Drives:
Local Storage: total: raw: 3.86 TiB usable: -1719099656 used: 156.08 GiB
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-75ZF5A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZEX-00WN4A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A01
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD10EZEX-75ZF5A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital
model: WD1002FAEX-00Z3A0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: 1D05
ID-5: /dev/sde maj-min: 8:64 vendor: Seagate model: ST240HM000-1G5152
size: 223.57 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: C675 scheme: GPT
Partition:
ID-1: / raw-size: 206.14 GiB size: 206.14 GiB (100.00%)
used: 156.08 GiB (75.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-ec3ee267-8732-4cc4-8960-c39fbbf5c306
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 728 KiB (0.2%) fs: vfat dev: /dev/sde1 maj-min: 8:65
ID-3: /home raw-size: 206.14 GiB size: 206.14 GiB (100.00%)
used: 156.08 GiB (75.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-ec3ee267-8732-4cc4-8960-c39fbbf5c306
ID-4: /var/log raw-size: 206.14 GiB size: 206.14 GiB (100.00%)
used: 156.08 GiB (75.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-ec3ee267-8732-4cc4-8960-c39fbbf5c306
ID-5: /var/tmp raw-size: 206.14 GiB size: 206.14 GiB (100.00%)
used: 156.08 GiB (75.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-ec3ee267-8732-4cc4-8960-c39fbbf5c306
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 17.13 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-1 maj-min: 254:1
mapped: luks-22d6ffdc-91a9-4c97-ac75-1f30bca3e10c
ID-2: swap-2 type: zram size: 15.57 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 42.0 C mobo: N/A gpu: radeon temp: 65.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.57 GiB used: 1.16 GiB (7.4%)
Processes: 280 Power: uptime: 1m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.2 GiB services: upowerd,xfce4-power-manager
Init: systemd v: 255 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1782 libs: 507 tools: pamac,paru,yay Compilers:
clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi default: Bash v: 5.2.26
running-in: yakuake inxi: 3.3.34
Garuda (2.6.26-1):
System install date: 2023-02-21
Last full system update: 2024-06-16 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager mkinitcpio
Windows dual boot: No/Undetected
Failed units: cups.path mdmonitor.service cups.socket
I have an old HP 1012 printer that has always worked fine with the generic drivers despite needing the occasional reboot. I did notice a few CUPS errors on shutdown starting a couple weeks ago but I don’t print that often so I didn’t investigate. Well now my printer is not working at all after attempting to print something so I would like to figure it out.
I did follow through this thread no-way-to-add-printers and could not resolve my issue.
I have installed HPLIP and it finds my printer on USB and says it was installed but it never shows up on the list of printers. I am assuming this has to do with CUPS not working correctly?
I have attempted to start my CUPS service and it fails with this output:
$ systemctl start cups.service
Job for cups.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status cups.service" and "journalctl -xeu cups.service" for details.
What is it’s “unit configuration”?
journals return expected errors
$ systemctl status cups.service
○ cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; preset: disabled)
Active: inactive (dead) (Result: protocol) since Sun 2024-06-16 03:10:11 EDT; 1min 39s ago
TriggeredBy: × cups.path
× cups.socket
Docs: man:cupsd(8)
Process: 3075 ExecStart=/usr/bin/cupsd -l (code=killed, signal=TERM)
Main PID: 3075 (code=killed, signal=TERM)
CPU: 4ms
Jun 16 03:10:11 GarudaMS7917 systemd[1]: cups.service: Scheduled restart job, restart counter is at 15.
Jun 16 03:10:11 GarudaMS7917 systemd[1]: Stopped CUPS Scheduler.
Jun 16 03:10:11 GarudaMS7917 systemd[1]: Dependency failed for CUPS Scheduler.
Jun 16 03:10:11 GarudaMS7917 systemd[1]: cups.service: Job cups.service/start failed with result 'dependency'.
“inactive (dead)”
and
$ journalctl -xeu cups.service
░░ A start job for unit cups.service has begun execution.
░░
░░ The job identifier is 4998.
Jun 16 03:10:10 GarudaMS7917 systemd[1]: cups.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit cups.service has entered the 'failed' state with result 'protocol'.
Jun 16 03:10:10 GarudaMS7917 systemd[1]: Failed to start CUPS Scheduler.
░░ Subject: A start job for unit cups.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cups.service has finished with a failure.
░░
░░ The job identifier is 4998 and the job result is failed.
Jun 16 03:10:10 GarudaMS7917 systemd[1]: cups.service: Scheduled restart job, restart counter is at 14.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit cups.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 16 03:10:10 GarudaMS7917 systemd[1]: Stopped CUPS Scheduler.
░░ Subject: A stop job for unit cups.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit cups.service has finished.
░░
░░ The job identifier is 5142 and the job result is done.
Jun 16 03:10:10 GarudaMS7917 systemd[1]: Starting CUPS Scheduler...
░░ Subject: A start job for unit cups.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cups.service has begun execution.
░░
░░ The job identifier is 5142.
Jun 16 03:10:10 GarudaMS7917 systemd[1]: cups.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit cups.service has entered the 'failed' state with result 'protocol'.
Jun 16 03:10:10 GarudaMS7917 systemd[1]: Failed to start CUPS Scheduler.
░░ Subject: A start job for unit cups.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cups.service has finished with a failure.
░░
░░ The job identifier is 5142 and the job result is failed.
Jun 16 03:10:11 GarudaMS7917 systemd[1]: cups.service: Scheduled restart job, restart counter is at 15.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit cups.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 16 03:10:11 GarudaMS7917 systemd[1]: Stopped CUPS Scheduler.
░░ Subject: A stop job for unit cups.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit cups.service has finished.
░░
░░ The job identifier is 5286 and the job result is done.
Jun 16 03:10:11 GarudaMS7917 systemd[1]: Dependency failed for CUPS Scheduler.
░░ Subject: A start job for unit cups.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cups.service has finished with a failure.
░░
░░ The job identifier is 5286 and the job result is dependency.
Jun 16 03:10:11 GarudaMS7917 systemd[1]: cups.service: Job cups.service/start failed with result 'dependency'.
‘failed’ state with result ‘protocol’
So I am a bit confused why this would just stop working? I am sure some of you experts might be able to point me in the right direction. Nothing significant (that I know of) has changed on my system other than normal updating.
Thank you for any help in advance.