Discombobulating update matrix... stuck?
abc-mikey opened this issue · 2 comments
abc-mikey commented
When trying to view to update in the solus software center it remains stuck on Discombobulating...
There is one error I can see when launched from the terminal, but it doesn't look to trigger when viewing the updates tab:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/solus_sc/updates_view.py", line 429, in init_view
model.set(item, 0, False)
UnboundLocalError: local variable 'item' referenced before assignment
System info:
inxi -Fx
System:
Host: foobar Kernel: 5.10.1-162.current x86_64 bits: 64 compiler: N/A
Desktop: Budgie 10.5.2 Distro: Solus 4.1
Machine:
Type: Kvm System: QEMU product: Standard PC (i440FX + PIIX, 1996)
v: pc-i440fx-4.2 serial: <superuser/root required>
Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: 1.13.0-2.fc32
date: 04/01/2014
CPU:
Topology: Dual Core model: Intel Core i7-7600U bits: 64 type: MT MCP
arch: Amber Lake rev: 9 L2 cache: 16.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 23232
Speed: 2904 MHz min/max: N/A Core speeds (MHz): 1: 2904 2: 2904 3: 2904
4: 2904
Graphics:
Device-1: Red Hat QXL paravirtual graphic card driver: qxl v: kernel
bus ID: 00:02.0
Display: x11 server: X.Org 1.20.9 driver: qxl note: display driver n/a
unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: llvmpipe (LLVM 10.0.1 256 bits) v: 4.5 Mesa 20.2.3
direct render: Yes
Audio:
Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio
vendor: Red Hat QEMU Virtual Machine driver: snd_hda_intel v: kernel
bus ID: 00:04.0
Sound Server: ALSA v: k5.10.1-162.current
Network:
Device-1: Intel 82371AB/EB/MB PIIX4 ACPI
vendor: Red Hat Qemu virtual machine type: network bridge
driver: piix4_smbus v: N/A port: c1e0 bus ID: 00:01.3
Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
vendor: Red Hat QEMU Virtual Machine driver: 8139cp v: 1.3 port: c000
bus ID: 00:03.0
IF: ens3 state: up speed: 100 Mbps duplex: full mac: 52:54:00:a5:c0:44
Drives:
Local Storage: total: 27.91 GiB used: 9.29 GiB (33.3%)
ID-1: /dev/sda vendor: QEMU model: HARDDISK size: 27.91 GiB
Partition:
ID-1: / size: 26.43 GiB used: 9.02 GiB (34.1%) fs: ext4 dev: /dev/sda2
Swap:
ID-1: swap-1 type: partition size: 954.0 MiB used: 285.2 MiB (29.9%)
dev: /dev/sda1
Sensors:
Message: No sensors data was found. Is sensors configured?
Info:
Processes: 182 Uptime: 41m Memory: 1.93 GiB used: 1.32 GiB (68.5%)
Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.11
inxi: 3.1.03
abc-mikey commented
There aren't actually any packages to update, when I do an update with eopkg
Solus repository information is up-to-date.
No packages to upgrade.
Which may be related but in this case I would expect it to finish fairly quickly and let me know that there aren't any updates.
JoshStrobl commented
This is already fixed in git at the actual upstream, https://github.com/getsolus/solus-sc