You are not logged in.

#1 2016-10-04 12:58:56

ratcheer
Member
Registered: 2011-10-09
Posts: 665

Re: Pacman update caused crash/hang

I replied Y to removing the qtchooser. Then, my system crashed (dropping me to an unresponsive system console) during the completion of the -Syu updates. When I got the system back up, I reran the -Syu, and it said, "There is nothing to do." I examined the pacman log, and maybe the updates did complete before the system crash, but I feel unsure about it.

Tim

Offline

#2 2016-10-04 15:09:53

sinek
Member
Registered: 2016-10-04
Posts: 3

Re: Pacman update caused crash/hang

ratcheer wrote:

I replied Y to removing the qtchooser. Then, my system crashed (dropping me to an unresponsive system console) during the completion of the -Syu updates. When I got the system back up, I reran the -Syu, and it said, "There is nothing to do." I examined the pacman log, and maybe the updates did complete before the system crash, but I feel unsure about it.

Tim

The exact same thing happened to me. I thought it had something to do with having updated systemd and/or linux but as for your comment it looks like it's not related.

Offline

#3 2016-10-04 15:20:28

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 491

Pacman update caused crash/hang

WorMzy wrote:

ratcheer, you should probably open a new topic about your issue, I doubt it's related to removing qtchooser. Be sure to include you journal from the affected session.

The issue may still be the removal of qtchooser, or the update to systemd. I was paying close attention to the pacman output and at the exact stage where it removes qtchooser (in my case right after the dkms hook to remove DKMS kernel modules), KDE and X crash, dropping me back to the systemd console output. I was still able to switch to a different TTY and top shows that pacman is continuing with the install, even though KDE/X is dead.

If this happens to you: don't panic and let pacman finish - it will continue to run. Once finished, I rebooted and everything is back to normal.

Pacman log output doesn't show anything out of the ordinary.

However, the journal log does seem to indicate a possible problem with the update to systemd (notice what happens around the same time in pacman.log and journal log) - too bad the pacman.log doesn't have the seconds resolution in my case. I believe at Oct 04 07:45:35 is when KDE/X crashed/terminated. You can see that at Oct 04 07:46:40 is when I switched to tty4 and waiting for pacman to finish before rebooting.

Journal:

Oct 04 07:44:30 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:44:30 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:45:35 cirdan dbus-daemon[788]: Reloaded configuration
Oct 04 07:45:35 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:45:35 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:45:35 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:45:35 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:45:35 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:45:36 cirdan systemd[1]: Reexecuting.
Oct 04 07:45:36 cirdan systemd[1]: systemd 231 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +
Oct 04 07:45:36 cirdan systemd[1]: Detected architecture x86-64.
Oct 04 07:45:36 cirdan systemd[1]: Received SIGHUP from PID 1 (systemd).
Oct 04 07:45:36 cirdan systemd[1]: Reloading.
Oct 04 07:45:54 cirdan kdeinit5[826]: Reusing existing ksycoca
Oct 04 07:45:54 cirdan kdeinit5[826]: Recreating ksycoca file ("/home/twelveeighty/.cache/ksycoca5_en_5i1yY4rVv10miw3J7SmeHfYiGMM=", version 303)
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "packages/libreoffice.xml"
Oct 04 07:45:54 cirdan kdeinit5[826]: Still in the time dict (i.e. deleted files) ("apps")
Oct 04 07:45:54 cirdan kdeinit5[826]: kf5.kservice.sycoca: Parse error in  "/home/twelveeighty/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line  1 , 
Oct 04 07:45:54 cirdan kdeinit5[826]: Menu "applications-kmenuedit.menu" not found.
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-draw.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-base.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-xsltfilter.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/chromium.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-math.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-impress.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/hplip.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-calc.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-writer.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: modified: "/usr/share/applications/libreoffice-startcenter.desktop"
Oct 04 07:45:54 cirdan kdeinit5[826]: Saving
Oct 04 07:45:54 cirdan kwin_x11[896]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59480, resource id: 56623105, major code: 18 (ChangeProperty), minor code: 0
Oct 04 07:45:54 cirdan kwin_x11[896]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59484, resource id: 56623106, major code: 18 (ChangeProperty), minor code: 0
Oct 04 07:46:09 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:46:09 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:46:09 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:46:09 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:46:09 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:46:09 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:46:10 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:46:10 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:46:10 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:46:14 cirdan dbus-daemon[788]: Reloaded configuration
Oct 04 07:46:14 cirdan dbus-daemon[788]: Reloaded configuration
Oct 04 07:46:14 cirdan at-spi-bus-launcher[2571]: Reloaded configuration
Oct 04 07:46:14 cirdan dbus-daemon[788]: Reloaded configuration
Oct 04 07:46:14 cirdan dbus[500]: [system] Reloaded configuration
Oct 04 07:46:25 cirdan kwin_x11[896]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59488, resource id: 56623105, major code: 18 (ChangeProperty), minor code: 0
Oct 04 07:46:25 cirdan kwin_x11[896]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59492, resource id: 56623106, major code: 18 (ChangeProperty), minor code: 0
Oct 04 07:46:25 cirdan kdeinit5[826]: Reusing existing ksycoca
Oct 04 07:46:25 cirdan kdeinit5[826]: Recreating ksycoca file ("/home/twelveeighty/.cache/ksycoca5_en_5i1yY4rVv10miw3J7SmeHfYiGMM=", version 303)
Oct 04 07:46:26 cirdan kdeinit5[826]: Still in the time dict (i.e. deleted files) ("apps")
Oct 04 07:46:26 cirdan kdeinit5[826]: kf5.kservice.sycoca: Parse error in  "/home/twelveeighty/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line  1 , 
Oct 04 07:46:26 cirdan kdeinit5[826]: Menu "applications-kmenuedit.menu" not found.
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/assistant.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/designer-qt4.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/qdbusviewer.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/linguist-qt4.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/designer.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/qtconfig-qt4.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/assistant-qt4.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/linguist.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: modified: "/usr/share/applications/qdbusviewer-qt4.desktop"
Oct 04 07:46:26 cirdan kdeinit5[826]: Saving
Oct 04 07:46:30 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:46:30 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:46:30 cirdan plasmashell[915]: No metadata file in the package, expected it at: "/home/twelveeighty/Pictures/Wallpapers/Photos/"
Oct 04 07:46:34 cirdan kdeinit5[826]: powerdevil: ACTIVE SESSION PATH CHANGED: "/"
Oct 04 07:46:34 cirdan kdeinit5[826]: powerdevil: Switched to inactive session - leaving unchanged
Oct 04 07:46:34 cirdan systemd[1]: Started Getty on tty4.
Oct 04 07:46:38 cirdan NetworkManager[535]: <info>  [1475588798.1920] device (wlp2s0): supplicant interface state: inactive -> scanning
Oct 04 07:46:40 cirdan login[24745]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Oct 04 07:46:40 cirdan systemd[1]: Created slice User Slice of root.
Oct 04 07:46:40 cirdan systemd[25164]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Oct 04 07:46:40 cirdan systemd[1]: Starting User Manager for UID 0...
Oct 04 07:46:40 cirdan login[24745]: ROOT LOGIN ON tty4
Oct 04 07:46:40 cirdan systemd-logind[506]: New session c3 of user root.
Oct 04 07:46:40 cirdan systemd[1]: Started Session c3 of user root.

pacman log:

[2016-10-04 07:38] [PACMAN] Running 'pacman -Syu'
[2016-10-04 07:38] [PACMAN] synchronizing package lists
[2016-10-04 07:38] [PACMAN] starting full system upgrade
[2016-10-04 07:45] [ALPM] running '70-dkms-remove.hook'...
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> dkms remove -m vboxhost -v 5.1.6_OSE -k 4.7.5-1-ARCH
[2016-10-04 07:45] [ALPM] transaction started
[2016-10-04 07:45] [ALPM] removed qtchooser (53-2)
[2016-10-04 07:45] [ALPM] upgraded iana-etc (20160921-1 -> 20160927-1)
[2016-10-04 07:45] [ALPM] upgraded babl (0.1.16-1 -> 0.1.18-1)
[2016-10-04 07:45] [ALPM] upgraded libsystemd (231-1 -> 231-3)
[2016-10-04 07:45] [ALPM] upgraded systemd (231-1 -> 231-3)
[2016-10-04 07:45] [ALPM] upgraded mesa (12.0.3-1 -> 12.0.3-2)
[2016-10-04 07:45] [ALPM] upgraded mesa-libgl (12.0.3-1 -> 12.0.3-2)
[2016-10-04 07:45] [ALPM] upgraded chromium (53.0.2785.116-1 -> 53.0.2785.143-1)
[2016-10-04 07:45] [ALPM] upgraded libx264 (2:148.20160613-2 -> 2:148.20160920-1)
[2016-10-04 07:45] [ALPM] upgraded x265 (2.0-1 -> 2.1-1)
[2016-10-04 07:45] [ALPM] upgraded ffmpeg (1:3.1.3-2 -> 1:3.1.4-2)
[2016-10-04 07:45] [ALPM] installed jbig2dec (0.13-1)
[2016-10-04 07:45] [ALPM] upgraded ghostscript (9.19-3 -> 9.20-2)
[2016-10-04 07:45] [ALPM] upgraded hplip (3.16.8-2 -> 3.16.9-1)
[2016-10-04 07:45] [ALPM] upgraded libfbclient (2.5.5.26952-2 -> 2.5.6.27020-1)
[2016-10-04 07:45] [ALPM] upgraded libnm-glib (1.4.1dev+33+gc87b89b-1 -> 1.4.2-1)
[2016-10-04 07:45] [ALPM] upgraded mpfr (3.1.4.p5-1 -> 3.1.5-1)
[2016-10-04 07:45] [ALPM] upgraded libreoffice-fresh (5.2.1-2 -> 5.2.2-1)
[2016-10-04 07:45] [ALPM] upgraded linux (4.7.5-1 -> 4.7.6-1)
[2016-10-04 07:45] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2016-10-04 07:45] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> Starting build: 4.7.6-1-ARCH
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> Starting build: 4.7.6-1-ARCH
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-10-04 07:45] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2016-10-04 07:45] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2016-10-04 07:46] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2016-10-04 07:46] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-10-04 07:46] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-10-04 07:46] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-10-04 07:46] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-10-04 07:46] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2016-10-04 07:46] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-10-04 07:46] [ALPM] upgraded linux-headers (4.7.5-1 -> 4.7.6-1)
[2016-10-04 07:46] [ALPM] upgraded networkmanager (1.4.1dev+33+gc87b89b-1 -> 1.4.2-1)
[2016-10-04 07:46] [ALPM] upgraded openssh (7.3p1-1 -> 7.3p1-2)
[2016-10-04 07:46] [ALPM] upgraded python-setuptools (1:28.0.0-1 -> 1:28.1.0-1)
[2016-10-04 07:46] [ALPM] upgraded python2-setuptools (1:28.0.0-1 -> 1:28.1.0-1)
[2016-10-04 07:46] [ALPM] upgraded qt4 (4.8.7-9 -> 4.8.7-10)
[2016-10-04 07:46] [ALPM] upgraded qca-qt4 (2.1.1-5 -> 2.1.1-6)
[2016-10-04 07:46] [ALPM] upgraded qt5-base (5.7.0-2 -> 5.7.0-3)
[2016-10-04 07:46] [ALPM] upgraded qca-qt5 (2.1.1-5 -> 2.1.1-6)
[2016-10-04 07:46] [ALPM] upgraded qt5-xmlpatterns (5.7.0-1 -> 5.7.0-2)
[2016-10-04 07:46] [ALPM] upgraded qt5-declarative (5.7.0-2 -> 5.7.0-3)
[2016-10-04 07:46] [ALPM] upgraded qt5-tools (5.7.0-1 -> 5.7.0-2)
[2016-10-04 07:46] [ALPM] upgraded systemd-sysvcompat (231-1 -> 231-3)
[2016-10-04 07:46] [ALPM] upgraded telepathy-gabble (0.18.3-3 -> 0.18.3+5+gfe084b7-1)
[2016-10-04 07:46] [ALPM] upgraded xf86-input-evdev (2.10.3-1 -> 2.10.4-1)
[2016-10-04 07:46] [ALPM] transaction completed
[2016-10-04 07:46] [ALPM] running '70-dkms-install.hook'...
[2016-10-04 07:46] [ALPM-SCRIPTLET] ==> dkms install -m vboxhost -v 5.1.6_OSE -k 4.7.6-1-ARCH
[2016-10-04 07:46] [ALPM] running 'gtk-update-icon-cache.hook'...
[2016-10-04 07:46] [ALPM] running 'texinfo-install.hook'...
[2016-10-04 07:46] [ALPM] running 'udev-hwdb.hook'...
[2016-10-04 07:46] [ALPM] running 'update-desktop-database.hook'...
[2016-10-04 07:46] [ALPM] running 'update-mime-database.hook'...
[2016-10-04 07:46] [ALPM-SCRIPTLET] Unknown media type in type 'all/all'
[2016-10-04 07:46] [ALPM-SCRIPTLET] Unknown media type in type 'all/allfiles'

Offline

#4 2016-10-04 16:42:59

quiqueck
Member
Registered: 2013-04-15
Posts: 56

Re: Pacman update caused crash/hang

I had the same issue as twelveeighty.

Switched to TTY2 worked, switching back to TTY1 worked also (all windows are shown) and i could see pacman is working, but no mouse and keyboard anymore. So i couldn't switch back to TTY2 anymore... the only thing i could do was to hit the power button after pacman was ready to shutdown. After restart it seems all is working again.

Linux 4.7.6-1-ARCH

Qt: 5.7.0
KDE Frameworks: 5.26.0

Offline

#5 2016-10-04 16:46:53

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,628

Re: Pacman update caused crash/hang

The tty issue has nothing to do with qtchooser, please stop the off-topic posts

Offline

#6 2016-10-04 17:14:48

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 8,913
Website

Re: Pacman update caused crash/hang

Mod note: Splitting off the off-topic posts to a new thread.


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#7 2016-10-04 17:41:46

responsys
Member
Registered: 2016-10-04
Posts: 1

Re: Pacman update caused crash/hang

Hello everyone,

I'm reporting the same weird behaviours as ratcheer and sinek.
Also something else: I then exited the Xorg server (falling back to TTY1) but when I tried to run `startx` again, it failed. I uploaded the log here: http://pastebin.com/LyE9uV20
I then switched to TTY 2, logged in, ran `startx` and it worked.
I never had any problem with my Xorg server, so that's likely not a coincidence.

Now I'm afraid to reboot for not being able to start a Xorg server again...

Offline

#8 2016-10-04 17:52:02

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 27,694
Website

Re: Pacman update caused crash/hang

This is just the systemd update re-execing: switching back to the original TTY where X is running should be sufficient.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#9 2016-10-04 20:10:47

mpan
Member
Registered: 2012-08-01
Posts: 494
Website

Re: Pacman update caused crash/hang

Unfortunately, it isn’t. We’ve been discussing the issue with people on IRC today, as mine system has become unstable during the update too. It’s not related to one of the qt* packages, but probably to linux or systemd. After switching back to X it may be impossible to leave it and X itself is unstable — for example closing windows may cause it to stop updating display unless the users attempts to switch to a console (unsuccessfully) and then back to X. Also journal contained nothing suspicious in my case.

Someone has suggested doing

systemctl daemon-reload

I was in hurry and have chosen YOLO solution (a reboot) instead this, so someone may still check if this works.


Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB

Offline

#10 2016-10-04 21:21:10

ratcheer
Member
Registered: 2011-10-09
Posts: 665

Re: Pacman update caused crash/hang

I also believe it was the systemd update, rather than removing qtchooser. The only relevant messages I see in the journal are:

Oct 04 07:42:49 tim-arch-ssd dbus-daemon[436]: Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd dbus[351]: [system] Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd dbus[351]: [system] Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd dbus[351]: [system] Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd dbus[351]: [system] Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd dbus[351]: [system] Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd dbus[351]: [system] Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd dbus[351]: [system] Reloaded configuration
Oct 04 07:42:49 tim-arch-ssd systemd[1]: Reexecuting.
Oct 04 07:42:49 tim-arch-ssd systemd[1]: systemd 231 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +U
Oct 04 07:42:50 tim-arch-ssd systemd[1]: Received SIGHUP from PID 1 (systemd).
Oct 04 07:42:50 tim-arch-ssd systemd[1]: Reloading.
-- Reboot --

Since everything seems to be fine, I can mark the thread solved, unless you want to keep it open for others with similar occurrences.

Thanks,
Tim

Offline

#11 2016-10-05 15:27:17

Trinakrian
Member
From: Acushnet, MA
Registered: 2014-10-13
Posts: 26
Website

Re: Pacman update caused crash/hang

Got nailed by this on three computers. All three borked out. Two of them I multi-boot on, but one of them is only Arch. I can't access the desktop on any of them. I get the "Can you call qdbus?" message.

Seems related to systemd - that's where it dropped on all three. None of the suggestions on this thread have resolved the issue.


If you're coming on, come on!!!

Offline

#12 2016-10-05 15:40:46

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 21,881
Website

Re: Pacman update caused crash/hang

FWIW X restarted here in the update of these packages for me as well.  I use tmux and reattach to the same session every time X starts, and X starts automatically at login.  During the update, X did exit, I was back at tty1 briefly with Xorg output shown, then (due to an 'exec startx` in bashrc) I was logged out when X was done, autologin kicked in, X restarted, tmux reconnected, and I saw the complete pacman output which finished without error.

I've had no other symptoms and no problems at all since this happened.  I run a very minimal system (custom WM, no DE).  So whatever triggers this is not limited to big DE packages - though I do have some qt packages for qutebrowser: qt5-chooser was replaced by qt5-base in the update.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Online

#13 2016-10-05 21:55:19

Miblo
Member
From: Manchester, UK
Registered: 2010-07-05
Posts: 160
Website

Re: Pacman update caused crash/hang

Trilby wrote:

[…]I've had no other symptoms and no problems at all since this happened.[…]

I think I had the same experience as you, Trilby, although upon being returned to X I found I couldn't switch to a different tty. To get my six ttys back I had to exit fluxbox to tty1 (no display manager). But then in that state, although I could switch to and startx from tty2, I could no longer startx from that same tty1. In order to get that back I had to logout and in again. Not sure if this could be any help for a possible package fix (if we need it).

Also, it was certainly the systemd update, because I'd previously had the qt one in the previous update.


@archun: Intel® Core™ i5-4210M • [GPU] Intel® HD Graphics 4600 • [Kernel] linux-ck-haswell
Handmade.NetworkGitLab
The Life and Times of Miblo del Carpio

Offline

#14 2017-01-29 17:25:56

dvh
Member
Registered: 2007-10-06
Posts: 40

Re: Pacman update caused crash/hang

I wish that I had read this before...

I had the exact same desktop crash during a system update, but I was not patient enough, nor was I wise enough to switch to another TTY to see if pacman was still running.  instead, I rebooted my machine the hard way, and it now appears I have problems.

first of all, I cannot boot.  grub seems to run and select the right image, but from there my screen goes dark and next thing I see is the machine logo, indicating it is rebooting again.  this repeats continuously.  I am using an arch install USB to boot, and I can mount the system drive and see all of the files.  I tried to chroot into the old system, but i get an error that /usr/bin/zsh cannot be found, and it appears that the chroot has failed.

I then tried to use pacman with the --root option to update my system, and I get a message that several databases are locked, so I know I killed the pacman session before it completed.  I removed the lock and retried the system update (pacman -Syu) and after syncing the databases, pacman reports that gt5-declarative cannot be found, and it asks if I should replace it with a render2 version??  I tried to --force the update, but pacman says it cannot complete due to a missing dependency...gt5-xmlpatterns.  tried to force that one also, but it also has a missing dependency...gt5-base, which has MANY missing dependencies.  strangely, examining var/cache/pacman/pkg shows all of the "missing" dependency packages appear there and appear to be intact.

all in all it looks like i have messed up my package database in some way, or terminated half way through the qt5chooser swapout.  is there a recommended way to recover?  can I somehow rebuild my package database?   what if I removed all packages from the cache and forced download of all new?

please help.

-dvh

Offline

#15 2017-01-29 20:55:10

dvh
Member
Registered: 2007-10-06
Posts: 40

Re: Pacman update caused crash/hang

fixed.  I think.

1) cleared the pacman cache  "pacman Scc"
2) forced reinstall of all packages with "pacman -Qnq | pacman -S -".  this could not complete because /var/local/pacman/Qt5-declarative.../desc could not be found, so I
3) removed "rm -r /var/local/pacman/Qt5-..." the strangely messed up file
4) removed "pacman -R Qt5-declarative"
5) repeated step 2.  had to work one other dependecy issue (can't recall what that was)
6) repeated step 2 again...

Success!

I can now boot from my native install, and all seems well.   crossing my fingers.

-dvh

Offline

Board footer

Powered by FluxBB