You are not logged in.
edit5: This isn't so much solved as has been worked around. The "solution", step I took to resolve the issue, are in edits three and four at the bottom. I still don't know what happened or how to fix this on a system without frequent backups or snapshots.
I let my system let out of date and have, for the last few weeks, been bringing it slowly up to date via ALA. Today, part of the update was the removal of qtchooser. however it's been stuck trying to remove it for about 15 minutes. The progress bar shows that no progress has been made. Dmesg |tail and journalctl don't show anything at all to indicate any thing regarding this.
[16433.607581] BTRFS info (device sde3): found 2 extents
[16436.990556] BTRFS info (device sde3): found 2 extents
[16437.337670] BTRFS info (device sde3): relocating block group 5175901159424 flags 20
[16450.177257] BTRFS info (device sde3): found 6437 extents
[16450.711910] BTRFS info (device sde3): relocating block group 5175867604992 flags 18
[16451.253884] BTRFS info (device sde3): found 19 extents
[16463.204195] EXT4-fs (sdc10): mounted filesystem with ordered data mode. Opts: (null)
[16489.224781] EXT4-fs (sdc5): mounted filesystem with ordered data mode. Opts: (null)
[17659.834479] nvidia-modeset: Freed GPU:0 (GPU-bbb711b5-aaf3-8abb-18f9-bc5f287ca379) @ PCI:0000:01:00.0
[17922.902120] nvidia-modeset: Allocated GPU:0 (GPU-bbb711b5-aaf3-8abb-18f9-bc5f287ca379) @ PCI:0000:01:00.0Also,
$ tail --lines=20 /var/log/pacman.log
[2016-10-11 15:22] [ALPM] upgraded xterm (325-1 -> 326-1)
[2016-10-11 15:22] [ALPM] transaction completed
[2016-10-11 15:22] [ALPM] running '70-dkms-install.hook'...
[2016-10-11 15:22] [ALPM-SCRIPTLET] ==> dkms install -m vboxhost -v 5.1.6_OSE -k 4.7.5-1-ARCH
[2016-10-11 15:23] [ALPM-SCRIPTLET] ==> dkms install -m vboxhost -v 5.1.6_OSE -k 4.7.5-1-ARCH
[2016-10-11 15:23] [ALPM] running 'glib-compile-schemas.hook'...
[2016-10-11 15:23] [ALPM] running 'gtk-query-immodules-2.0.hook'...
[2016-10-11 15:23] [ALPM] running 'gtk-update-icon-cache.hook'...
[2016-10-11 15:23] [ALPM] running 'texinfo-install.hook'...
[2016-10-11 15:23] [ALPM] running 'udev-hwdb.hook'...
[2016-10-11 15:23] [ALPM] running 'update-desktop-database.hook'...
[2016-10-11 15:23] [ALPM] running 'update-mime-database.hook'...
[2016-10-12 13:41] [PACMAN] Running 'pacman -Syyuuw'
[2016-10-12 13:41] [PACMAN] synchronizing package lists
[2016-10-12 13:41] [PACMAN] starting full system upgrade
[2016-10-13 14:59] [PACMAN] Running 'pacman -Su'
[2016-10-13 14:59] [PACMAN] starting full system upgrade
[2016-10-13 14:59] [ALPM] running '70-dkms-remove.hook'...
[2016-10-13 14:59] [ALPM-SCRIPTLET] ==> dkms remove -m vboxhost -v 5.1.6_OSE -k 4.7.5-1-ARCH
[2016-10-13 14:59] [ALPM] transaction startedI kind of want to ctrl+c out of pacman, but that seems like it could cause some real issues. I'd copy and paste the terminal output of pacman itself, but it's running in a getty. It's pretty much:
:: Processing package removal
(1/1) removing qtchooser [c o o o o ] 0%edit: Even if you don't know what is going on, could you answer if it's safe to terminate pacman at this phase?
edit2: The HDD activity lights on my drives were all lighting up for the last fourty minutes which was really starting to scare me, so I ctrl+c'ed it. I believe, in a default Arch installation, that is the gentle way to get a program to stop. I haven't touched anything like that, so I'm hoping everything is okay. Although it is now stuck on "interupt signal recieved". At least the HDD lights have stopped.
edit3: Ten minutes had gone by, and the interupt hadn't stop pacman so I killed it. I'm going to make a snapshot of this mornings snapshot, chroot into it, and try to run the upgrade from there, starting with pacman -Rns qtchooser. Then rename the subvolume so as to replace this current one which contains a potentially broken Arch install.
edit4: I couldn't remove qtchooser, but that's okay, ran pacman -Su from chroot without a problem. All that's left is to reboot into my maintanance installation and move subvolumes around.
Btrfs snapshots may not be a backup solution, but they sure are handy when things go wrong and you want a quick way to revert all changes.
Last edited by nstgc (2016-10-13 20:13:07)
Offline