Octopi doesn’t start after update more

Issues & Assistance
1

I hope I’m in the right forum area, if not, please move.

After I updated my system this morning, I later discovered that Octopi could no longer be started.
What have I tried? First I uninstalled Octopi and reinstalled Octopi using the Garuda Setup Assistant, but Octopi still doesn’t want to start. Here is my inxi.

╰─λ garuda-inxi
System:
Kernel: 6.9.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=76d36b6c-d531-4de0-9a2c-d3ea38611f74 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.2.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 6203 date: 07/27/2023
CPU:
Info: model: AMD Ryzen 7 1800X bits: 64 type: MT MCP arch: Zen level: v3
note: check built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 1
stepping: 1 microcode: 0x8001138
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 2489 high: 3848 min/max: 2200/3850 boost: disabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3848 2: 2200
3: 3196 4: 2130 5: 2472 6: 2133 7: 2200 8: 2133 9: 3337 10: 2195 11: 3200
12: 2170 13: 2139 14: 2133 15: 2152 16: 2200 bogomips: 123201
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: ASUSTeK
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: DP-1,DP-2 empty: DP-3,HDMI-A-1,Writeback-1 bus-ID: 0b:00.0
chip-ID: 1002:73bf class-ID: 0300
Device-2: Logitech QuickCam Pro 9000 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-1:2
chip-ID: 046d:0990 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 23.2.7
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
s-diag: 1055mm (41.54")
Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,right model: VG248
serial: <filter> built: 2021 res: 1920x1080 dpi: 92 gamma: 1.2
size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: DP-2 mapped: DisplayPort-1 pos: left model: VG248
serial: <filter> built: 2021 res: 1920x1080 dpi: 92 gamma: 1.2
size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.7-arch1.3
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6900 XT (radeonsi
navi21 LLVM 17.0.6 DRM 3.57 6.9.1-zen1-1-zen) device-ID: 1002:73bf
memory: 15.62 GiB unified: no
API: Vulkan v: 1.3.279 layers: 9 device: 0 type: discrete-gpu name: AMD
Radeon RX 6900 XT (RADV NAVI21) driver: mesa radv v: 24.0.7-arch1.3
device-ID: 1002:73bf surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 17.0.6 256 bits) driver: mesa llvmpipe v: 24.0.7-arch1.3 (LLVM
17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0e:00.3
chip-ID: 1022:1457 class-ID: 0403
Device-3: Logitech QuickCam Pro 9000 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-1:2
chip-ID: 046d:0990 class-ID: 0102 serial: <filter>
API: ALSA v: k6.9.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.6 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: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: ASUSTek ASUS USB-BT500 driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:2 chip-ID: 0b05:190e
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 8.19 TiB used: 2.93 TiB (35.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST31000524AS
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: JC45 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM008-2UB102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 0001 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST2000DM008-2UB102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 0001 scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 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
scheme: MBR
ID-5: /dev/sde maj-min: 8:64 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 046 scheme: GPT
ID-6: /dev/sdf maj-min: 8:80 vendor: Seagate model: ST2000DM001-1CH164
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: CC27 scheme: MBR
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 756.52 GiB (81.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/sde1 maj-min: 8:65
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 756.52 GiB (81.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 756.52 GiB (81.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 756.52 GiB (81.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.5 C mobo: N/A gpu: amdgpu temp: 48.0 C
mem: 44.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 5.51 GiB (17.6%)
Processes: 475 Power: uptime: 15m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: 2008 pm: pacman pkgs: 1944 libs: 528 tools: gnome-software,
octopi, pamac, paru pm: flatpak pkgs: 64 Compilers: clang: 17.0.6
gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-05-17
Last full system update: 2024-05-18 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       No/Undetected
Failed units:

Since yesterday Skype couldn’t access the KDE Wallet password storage to log in, I was able to fix the problem by uninstalling SKype and installing it via Octopi’s AUR, then it worked, luckily I did this morning at 00:025 did.

Ther can see what an important tool Octopi is.
Wouldn’t have worked after that.

1 Like
2

octopi is having a lib issue should be updated in a day or so. octopi: error while loading shared libraries: libqtermwidget5.so.1: cannot open shared object file: No such file or directory
might be able to sudo downgrade <pkg name> it if you need it now or an use pacseek paru pacseek

3 Likes
3

The cause is the update of the qtermwidget. Either you wait for an update from octopi or you downgrade the qtermwidget to version 1.4.0.

sudo downgrade qtermwidget

At this point you answer with no [n]:

add qtermwidget to IgnorePkg? [y/n]

The next update will bring the package back to the latest version.

reboot your system btw:

5 Likes
4

Hello, thanks for the quick help, I see that new updates have come out.
I’ll install these now and see what happens.
If necessary, I will use your solutions.

Thank you very much.

5

Downgrade worked.
Still have a lot to learn and try when it comes to Linux.

6

If you get an issue with another application because of this, then update qtermwidget to the latest version:

sudo pacman -S qtermwidget

If you want, you can read the section on pacman in the arch-wiki to learn what you can do with it. For example, how to downgrade pakages or exclude packages from updates.

Keep it up :slight_smile:

1 Like
7

The problem is always the translation from English into
Germans, by long posts.
But I’ll still look into it.
Above all, it would be interesting to know how you can downgrade a graphics driver if you have problems with the new one.
When I moved from mesa 23.0.3 to 24.0.4. had moved up, I could no longer start Insurgency Sandstorm. Today I still get the error message: unexpected error.

unexpected error
unexpected error829×474 66.3 KB

But that was two weeks ago, now I use the standard/original Steam instead of Steam Runtime/Native, the game works there.
Steam for Insurgency Sandstorm

No unexpected error
No unexpected error847×489 50.3 KB

If a graphics driver wasn’t good under Windows, I used the previous one again.
Just need to know how to do it with Linux Arch.

8

This is a great opportunity / excuse for me to get to know pacseek a little, which I installed with this latest version of garuda. Seems super easy to use so far.

1 Like
9

I moved to Issues & Assistance

If you have any more issues, please put in that category (or a more precise subcategory) and follow the template.

3 Likes
10

Octopi is due to be dropped if a dependency isn’t updated, and the maintainer of octopi-git is missing for months too.

5 Likes
11

2 posts were split to a new topic: How do you install and uninstall a program in pacssek?

12

A post was merged into an existing topic: How do you install and uninstall a program in pacssek?

14

Please, one issue per topic… and if you have any more issues make a new topic in Issues & Assistance as I have already said and follow the template. Too many things have split into new a topic here already, closing this one up as already solved to avoid confusion.

3 Likes
15

Well, qt-sudo got updated so everything is fine.

https://aur.archlinux.org/cgit/aur.git/commit/?h=qt-sudo&id=3da895e7725c39cc46c6352ff886776131caf68a

Added the new dep and built the new octopi version as well, so people should be able to update.

16

Maybe a little bit less than fine.

It does work now, but the pkgver is bad, especially considering it’s from pinned commit… It ideally should have interfere applied if we are going to provide it. See comment: AUR (en) - qt-sudo and upstream issue: Req: Tag a new release · Issue #2 · aarnt/qt-sudo · GitHub for why this may be an issue in the future.

17

That’s true, I don’t get the reasoning behind that move either, but it does work around the issues everyone has while updating currently. The rest of the PKGBUILD seemed acceptable when I looked at it.

Edit: applied the interfere as proposed:

1 Like