Offlineimap giving error after recent update

Hi all!

I have been using offlineimap successfully for several weeks on my Garuda desktop.

Today, after a large-ish software update, I’m getting the following error when running offlineimap now:

OfflineIMAP 8.0.0
  Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
imaplib2 v3.06, Python v3.9.7, OpenSSL 1.1.1l  24 Aug 2021
ERROR: No module named 'commands'
ERROR: Exceptions occurred during the run!
ERROR: No module named 'commands'

I have both Python versions 2 (2.7.18) and 3 (3.9.7) installed.

Is anyone else using offlineimap successfully?
I didn’t seem to need to before, but is there a way to force offlineimap to use Python2?

Thanks!

Post your inxi -Faz, please, as it was also requested in the template.
If you maybe use Garuda Linux you can boot in last working snapshot before this big update.

Move it from #issues-assistance to #issues-assistance:aur-snaps-flatpaks-other

And check

Thanks and sorry about that. It is indeed Garuda. Output below:

❯ inxi -Faz                                                                                                                                                                                       585 Mbps  ─╯
System:    Kernel: 5.15.2-217-tkg-bmq x86_64 bits: 64 compiler: gcc v: 11.1.0
           parameters: intel_pstate=passive BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq
           root=UUID=0971afba-13f1-4f58-9dc9-2efda4002dba rw [email protected] quiet splash rd.udev.log_priority=3
           vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3
           Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux
           base: Arch Linux
Machine:   Type: Desktop System: System76 product: Thelio Major v: thelio-major-r2 serial: <filter>
           Mobo: System76 model: Thelio Major v: thelio-major-r2 serial: <filter> UEFI: System76 v: F4c Z5 date: 06/30/2020
Battery:   Device-1: hid-dc:2c:26:f6:8b:88-battery model: Keychron K2 serial: N/A charge: N/A status: Discharging
CPU:       Info: 24-Core (3-Die) model: AMD Ryzen Threadripper 3960X bits: 64 type: MT MCP MCM arch: Zen 2 family: 17 (23)
           model-id: 31 (49) stepping: 0 microcode: 8301025 cache: L2: 12 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 364464
           Speed: 4206 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 4206 2: 3704 3: 3579 4: 3596 5: 3899
           6: 3595 7: 3919 8: 3590 9: 3586 10: 3588 11: 3592 12: 3595 13: 3675 14: 3596 15: 3594 16: 3589 17: 3593 18: 3591
           19: 3982 20: 4303 21: 3781 22: 3598 23: 3586 24: 3863 25: 3583 26: 3586 27: 3580 28: 3812 29: 3592 30: 3590
           31: 3599 32: 3489 33: 3977 34: 3599 35: 3582 36: 3586 37: 3598 38: 3591 39: 3594 40: 3597 41: 3588 42: 3597
           43: 3593 44: 3586 45: 3594 46: 3592 47: 3588 48: 3593
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: eVga.com. driver: nvidia v: 495.44
           alternate: nouveau,nvidia_drm bus-ID: 21:00.0 chip-ID: 10de:1f06 class-ID: 0300
           Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver: loaded: nvidia display-ID: :0 screens: 1
           Screen-1: 0 s-res: 3840x2160 s-dpi: 162 s-size: 602x341mm (23.7x13.4") s-diag: 692mm (27.2")
           Monitor-1: HDMI-0 res: 3840x2160 hz: 60 dpi: 163 size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
           OpenGL: renderer: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 495.44 direct render: Yes
Audio:     Device-1: NVIDIA TU106 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus-ID: 21:00.1
           chip-ID: 10de:10f9 class-ID: 0403
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio driver: snd_hda_intel v: kernel bus-ID: 23:00.4
           chip-ID: 1022:1487 class-ID: 0403
           Device-3: C-Media Vanatoo T0 type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-2:3 chip-ID: 0d8c:0012
           class-ID: 0300
           Device-4: Giga-Byte USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-5:5 chip-ID: 0414:a002
           class-ID: 0300
           Sound Server-1: ALSA v: k5.15.2-217-tkg-bmq running: yes
           Sound Server-2: JACK v: 1.9.19 running: no
           Sound Server-3: PulseAudio v: 15.0 running: yes
           Sound Server-4: PipeWire v: 0.3.40 running: yes
Network:   Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel port: 9000 bus-ID: 43:00.0
           chip-ID: 8086:1539 class-ID: 0200
           IF: enp67s0 state: down mac: <filter>
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 44:00.0 chip-ID: 8086:2723 class-ID: 0280
           IF: wlo2 state: up mac: <filter>
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 9-5:6 chip-ID: 8087:0029 class-ID: e001
           Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: <filter>
Drives:    Local Storage: total: 1.82 TiB used: 394.14 GiB (21.2%)
           SMART Message: Unable to run smartctl. Root privileges required.
           ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size:
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXM7 temp: 44.9 C
           scheme: GPT
           ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size:
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXM7 temp: 47.9 C
           scheme: GPT
Partition: ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 394.14 GiB (42.3%) fs: btrfs dev: /dev/nvme1n1p2
           maj-min: 259:2
           ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 560 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1
           maj-min: 259:1
           ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 394.14 GiB (42.3%) fs: btrfs dev: /dev/nvme1n1p2
           maj-min: 259:2
           ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 394.14 GiB (42.3%) fs: btrfs
           dev: /dev/nvme1n1p2 maj-min: 259:2
           ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 394.14 GiB (42.3%) fs: btrfs
           dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
           ID-1: swap-1 type: zram size: 62.73 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 16.8 C mobo: N/A gpu: nvidia temp: 51 C
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:      Processes: 754 Uptime: 19h 32m wakeups: 1 Memory: 62.73 GiB used: 12.1 GiB (19.3%) Init: systemd v: 249
           tool: systemctl Compilers: gcc: 11.1.0 Packages: 2062 pacman: 2054 lib: 568 flatpak: 0 snap: 8 Shell: Zsh v: 5.8
           running-in: konsole inxi: 3.3.08

Did you try

and this too?

Nice specs :smiley: :slight_smile:

I have not booted using a previous snapshot. I guess in my head i see it as more of a recovery from a 'catastrophic' event. Primarily because the snapshot will show me the same updates again, and not sure when a 'more updated' version of offlineimap (or python3) or whatever caused the initial issue will be available

I found a reference (that I inadvertently introduced) to a file that was causing the issue.

Sorry for the noise

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.