You are not logged in.
So, I'm having an issue that I have had before, which is Cinnamon getting in this Fallback loop. I remember the last time I had to solve this I had to reinstall a package. I came across a topic that described my issue, and the solve was to reinstall the gdk-pixbuf2 package. This go around I tired to do that and it's seg faulting:
section9% sudo pacman -S gdk-pixbuf2
[sudo] password for ishikawa:
warning: gdk-pixbuf2-2.32.3-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) gdk-pixbuf2-2.32.3-1
Total Installed Size: 3.84 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [------------------------------------------------------------] 100%
(1/1) checking package integrity [------------------------------------------------------------] 100%
(1/1) loading package files [------------------------------------------------------------] 100%
(1/1) checking for file conflicts [------------------------------------------------------------] 100%
(1/1) checking available disk space [------------------------------------------------------------] 100%
(1/1) reinstalling gdk-pixbuf2 [------------------------------------------------------------] 100%
/tmp/alpm_VSL5Wj/.INSTALL: line 1: 15429 Segmentation fault (core dumped) gdk-pixbuf-query-loaders --update-cache
error: command failed to execute correctly
Anyone else running into this?
Last edited by lifeafter2am (2016-01-23 14:06:11)
#binarii @ irc.binarii.net
Matrix Server: https://matrix.binarii.net
-------------
Allan -> ArchBang is not supported because it is stupid.
Offline
What are the contents of the coredump?
man coredumpctl
for more info. If this is a skylake system with propietary nvidia drivers (and the coredump contains mention of lock-elision), this is a known issue that's due to be resolved with the next update sitting in testing, see https://bugs.archlinux.org/task/46064 Workarounds would include installing from testing (with all the caveats that implies, like the new kernel and potentially unstable stuff), installing nvidia-beta from the AUR or recompiling glibc without --enable-lock-elision until the update lands in stable
Offline
I did a fresh install yesterday and have this issue too. I installed the intel-ucode but it didn't resolve the issue, I am now trying the beta drivers from nvidia.
And now it is working.
Last edited by ramirezterrix (2016-01-21 09:26:08)
Offline
What are the contents of the coredump?
man coredumpctl
for more info. If this is a skylake system with propietary nvidia drivers (and the coredump contains mention of lock-elision), this is a known issue that's due to be resolved with the next update sitting in testing, see https://bugs.archlinux.org/task/46064 Workarounds would include installing from testing (with all the caveats that implies, like the new kernel and potentially unstable stuff), installing nvidia-beta from the AUR or recompiling glibc without --enable-lock-elision until the update lands in stable
Yep, this was definitely the issue. I am running the beta NVIDIA drivers from the AUR and am now able to get into my window managers.
Thanks!
#binarii @ irc.binarii.net
Matrix Server: https://matrix.binarii.net
-------------
Allan -> ArchBang is not supported because it is stupid.
Offline
Neat, don't forget to mark the thread as SOLVED by editing your initial post
Last edited by V1del (2016-01-24 01:56:59)
Offline
Just reporting back that the newest nvidia packages (released on 2/2) fixed the problem for me and I no longer have to use the beta drivers from a the AUR.
#binarii @ irc.binarii.net
Matrix Server: https://matrix.binarii.net
-------------
Allan -> ArchBang is not supported because it is stupid.
Offline