You are not logged in.
I've checked the dmesg and no errors there. USB is mounted correctly and I can view it after I re-login.
But basically everytime I stick a usb disk or unmount it from file manager, my session ends abruptly and I'm back to login screen.
I'm using Gnome.
Anybody having similar problems?
Offline
Disable your login manager and start the session manually. When it crashes, see if there are any error messages displayed that may provide clues.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
yes exact same problem. See "Segfault.." by Cbhihe at https://bbs.archlinux.org/viewtopic.php?id=233806 where I document the segfault.
Last edited by Cbhihe (2018-01-22 20:11:42)
I like strawberries, therefore I'm not a bot.
Offline
Duplicate of https://bbs.archlinux.org/viewtopic.php?id=233803
Offline
Anybody having similar problems?
Apparently so. Merged threads
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
@ewaller:
@Scimmia:
Oops ! you guys had merged the two threads. Sorry. I just gathered that. Bit slow at the uptake here.
I thought I had made a mistake and published it inside another thread by error. SIlly.
Should revert my new thread ? In any case it contains more details about the issue.
Last edited by Cbhihe (2018-01-22 20:15:44)
I like strawberries, therefore I'm not a bot.
Offline
Just like @cbhihe I thought this was due to latest updates so I tried to downgrade some culprits like: linux, linux-firmware and glib2 but so far no luck
PS: I'm also on a Dell machine: XPS 13 9360 8th gen i7
Last edited by cb951303 (2018-01-22 20:33:14)
Offline
Is a coredump produced when the session is closed? If so what is the backtrace from the coredump?
Offline
Is a coredump produced when the session is closed? If so what is the backtrace from the coredump?
Looks like it is. The crash happens for binary Xwayland and the coredump is as below
PID: 757 (Xwayland)
UID: 1000 (cosku)
GID: 986 (users)
Signal: 6 (ABRT)
Timestamp: Mon 2018-01-22 23:27:07 +03 (47min ago)
Command Line: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6
Executable: /usr/bin/Xwayland
Control Group: /user.slice/user-1000.slice/session-c2.scope
Unit: session-c2.scope
Slice: user-1000.slice
Session: c2
Owner UID: 1000 (cosku)
Boot ID: bb9456b2c07e431da3fdbf032c84828e
Machine ID: 0a6aa4d705864118984a26f0594d4f62
Hostname: collin
Storage: /var/lib/systemd/coredump/core.Xwayland.1000.bb9456b2c07e431da3fdbf032c84828e.757.1516652827000000.lz4
Message: Process 757 (Xwayland) of user 1000 dumped core.
Stack trace of thread 757:
#0 0x00007f3938a7d860 raise (libc.so.6)
#1 0x00007f3938a7eec9 abort (libc.so.6)
#2 0x00005565d6c7ae4a OsAbort (Xwayland)
#3 0x00005565d6c80963 n/a (Xwayland)
#4 0x00005565d6c81785 FatalError (Xwayland)
#5 0x00005565d6b0cc0f n/a (Xwayland)
#6 0x00005565d6c789c1 n/a (Xwayland)
#7 0x00005565d6c7186b WaitForSomething (Xwayland)
#8 0x00005565d6c3d673 n/a (Xwayland)
#9 0x00005565d6c41910 n/a (Xwayland)
#10 0x00007f3938a69f4a __libc_start_main (libc.so.6)
#11 0x00005565d6b0c26a _start (Xwayland)
Stack trace of thread 758:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Stack trace of thread 762:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Stack trace of thread 761:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Stack trace of thread 763:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Stack trace of thread 764:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Stack trace of thread 760:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Stack trace of thread 765:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Stack trace of thread 759:
#0 0x00007f3938e0d39d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f39326df514 n/a (swrast_dri.so)
#2 0x00007f39326df368 n/a (swrast_dri.so)
#3 0x00007f3938e0708c start_thread (libpthread.so.0)
#4 0x00007f3938b3ee1f __clone (libc.so.6)
Offline
Knowing what the following calls were would probably help determine the cause
#4 0x00005565d6c81785 FatalError (Xwayland)
#5 0x00005565d6b0cc0f n/a (Xwayland)
#6 0x00005565d6c789c1 n/a (Xwayland)
#7 0x00005565d6c7186b WaitForSomething (Xwayland)
Offline
@cb951303:
Not just on Wayland, also on xorg. (I am not running Wayland)
Working now on getting a traceback for my case.
Never done this before. Is it just a `$ coredumpctl list `in terminal ?
I like strawberries, therefore I'm not a bot.
Offline
`coredumpctl` wthout any argument will default to listing coredumps then `coredumpctl info $match` where match is the PID of an entry produced by the previous command.
More details covered by `man coredumpctl`
Offline
Knowing what the following calls were would probably help determine the cause
#4 0x00005565d6c81785 FatalError (Xwayland) #5 0x00005565d6b0cc0f n/a (Xwayland) #6 0x00005565d6c789c1 n/a (Xwayland) #7 0x00005565d6c7186b WaitForSomething (Xwayland)
No useful data on coredumps
#0 0x00007f3938a7d860 in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x00007f3938a7eec9 in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2 0x00005565d6c7ae4a in OsAbort ()
No symbol table info available.
#3 0x00005565d6c80963 in ?? ()
No symbol table info available.
#4 0x00005565d6c81785 in FatalError ()
No symbol table info available.
#5 0x00005565d6b0cc0f in ?? ()
No symbol table info available.
#6 0x00005565d6c789c1 in ?? ()
No symbol table info available.
#7 0x00005565d6c7186b in WaitForSomething ()
No symbol table info available.
#8 0x00005565d6c3d673 in ?? ()
No symbol table info available.
#9 0x00005565d6c41910 in ?? ()
No symbol table info available.
#10 0x00007f3938a69f4a in __libc_start_main () from /usr/lib/libc.so.6
No symbol table info available.
#11 0x00005565d6b0c26a in _start ()
No symbol table info available.
I can try to attach to Xwayland and produce a crash but how will I get the data?
Last edited by cb951303 (2018-01-22 21:37:22)
Offline
@cb951303 did you rebuild the xorg-server package but with the PKGBUILD altered to add the following line to the PKGBUILD before line 40
options=(debug !strip)
So the section would look like
# $Id$
# Maintainer: AndyRTR <andyrtr@archlinux.org>
# Maintainer: Jan de Groot <jgc@archlinux.org>
pkgbase=xorg-server
pkgname=('xorg-server' 'xorg-server-xephyr' 'xorg-server-xdmx' 'xorg-server-xvfb' 'xorg-server-xnest' 'xorg-server-xwayland' 'xorg-server-common' 'xorg-server-devel')
pkgver=1.19.6
pkgrel=2
arch=('x86_64')
license=('custom')
groups=('xorg')
options=(debug !strip)
url="http://xorg.freedesktop.org"
makedepends=('pixman' 'libx11' 'mesa' 'mesa-libgl' 'xf86driproto' 'xcmiscproto' 'xtrans' 'bigreqsproto' 'randrproto'
'inputproto' 'fontsproto' 'videoproto' 'presentproto' 'compositeproto' 'recordproto' 'scrnsaverproto'
'resourceproto' 'xineramaproto' 'libxkbfile' 'libxfont2' 'renderproto' 'libpciaccess' 'libxv'
'xf86dgaproto' 'libxmu' 'libxrender' 'libxi' 'dmxproto' 'libxaw' 'libdmx' 'libxtst' 'libxres'
'xorg-xkbcomp' 'xorg-util-macros' 'xorg-font-util' 'glproto' 'dri2proto' 'libgcrypt' 'libepoxy'
'xcb-util' 'xcb-util-image' 'xcb-util-renderutil' 'xcb-util-wm' 'xcb-util-keysyms' 'dri3proto'
'libxshmfence' 'libunwind' 'systemd' 'wayland-protocols')
source=(https://xorg.freedesktop.org/releases/individual/xserver/${pkgbase}-${pkgver}.tar.bz2{,.sig}
nvidia-add-modulepath-support.patch
xserver-autobind-hotplug.patch
xvfb-run
xvfb-run.1
revert-udev-changes.diff
xwrap-suid-race.patch)
validpgpkeys=('7B27A3F1A6E18CD9588B4AE8310180050905E40C'
'C383B778255613DFDB409D91DB221A6900000011'
'DD38563A8A8224537D1F90E45B8A2D50A0ECD0D3'
'995ED5C8A6138EB0961F18474C09DD83CAAA50B2')
sha256sums=('a732502f1db000cf36a376cd0c010ffdbf32ecdd7f1fa08ba7f5bdf9601cc197'
'SKIP'
'914a8d775b708f836ae3f0eeca553da3872727a2e4262190f4d5c01241cb14e8'
'fcaf536e4fc307958923b58f2baf3d3102ad694efc28506f6f95a9e64483fa57'
'ff0156309470fc1d378fd2e104338020a884295e285972cc88e250e031cc35b9'
'2460adccd3362fefd4cdc5f1c70f332d7b578091fb9167bf88b5f91265bbd776'
'ce9b235c053ac85a9da86fba3b60fcfc48d36a8bd789b94ed79d5d571bc7b0aa'
'bce0e105386d75239f473b867d8ea6bc60e5302d87e03fdc720f48f43f5454f1')
Edit:
options=(debug !strip) not OPTIONS+=(debug !strip)
Edit2:
Assumes system has base-devel and git installed
$ git clone git://git.archlinux.org/svntogit/packages.git --single-branch --branch "packages/xorg-server"
$ mv packages/trunk xorg-server
$ cd xorg-server/ #then edit the PKGBUILD to add options=(debug !strip)
$ gpg --fetch-keys 4C09DD83CAAA50B2 #fetch the sources signing key
$ makepkg -rs
# pacman -U xorg-server-xwayland-1.19.6-2-x86_64.pkg.tar.xz
Last edited by loqs (2018-01-22 21:56:08)
Offline
Oddly
$ codedumpctl info /usr/bin/nautilus
does not give me anything pertinent to the gdm crash. Trying again.
I like strawberries, therefore I'm not a bot.
Offline
Are you using the Places Status Indicator? I would disable it for now until the gnome-shell-extensions package gets updated. https://gitlab.gnome.org/GNOME/gnome-sh … /issues/48
Offline
Are you using the Places Status Indicator? I would disable it for now until the gnome-shell-extensions package gets updated. https://gitlab.gnome.org/GNOME/gnome-sh … /issues/48
I just tried that and it works for me so far.
Offline
Is the Places Status Indicator extension something that is packaged by Arch?
Offline
Yes it is part of the gnome-shell-extensions package.
Offline
After update of the `gnome-shell-extension` in the early hours of this morning:
- the gnome shell login session auto-mounts any usb-drive correctly and shows the drive's label in Nautilus
- ejecting (unmounting) from the nautilus window also works with no segfault/coredump
On first trial the screen flickered (twice) when ejecting from nautilus. The 2nd time around no flicker.
Looks like the issue was solved.
I like strawberries, therefore I'm not a bot.
Offline
Unfortunately, after updating the gnome-shell-extensions package, I was still having coredumps with both mounting a USB drive and with unmounting both from Nautilus and with the Removable Drive Menu extension...
Offline
I can confirm that the issue exists even after updating the package and disabling the places extension solves the issue.
A new extensions package with a bug fix will be the only thing that can solve this. Anyone filed a but report on that package?
Offline
Offline