You are not logged in.
Hi all,
This is the first time I've run an update,
I ran:-
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
# pacman -Su
but now on restart the console displays this message:-
[ 14.851747] systemd-udevd[209]: specified group 'plugdev' unknown
The Gnome gui doesn't start, but I can see a mouse pointer. The fan is whirring, I think some infinite loop must be spinning.
I can log in on another console terminal.
Can anyone explain how I can get going with gnome again?
If you need extra diagnostic info please let me know what commands to run :-/ I'm an arch noob.
Cheers.
Karl
Offline
I ran:-
# pacman -Syu --ignore filesystem,bash
# pacman -S bash
# pacman -Su
So you also checked for offending packages before running those commands as advised in the latest news, I assume.
I have no precise solution in mind. Look for abnormalities in the logs since the upgrade occurred:
Login, acquire user privileges and then
cd /var/log/
ls #to list directory contents.Use cat or any text editor to read their contents. I suggest taking a look into boot, errors.log, Xorg.0.log and maybe inside gdm/ like this:
cat bootIs there a way for you to copy those logs?, and maybe posting them here using [ code][/code ] tags or preferably in a pastebin if they are huge. That would help us help you. A CLI web browser like links and a mouse pointer with simple copy/paste capabilities working from text mode thanks to gpm ease the job if you don't wanna run a different operating system just to mount and read the Arch partition(s).
Offline
OK here is some more information...
I was able to login on another console (<ctrl><alt>F2)
from there I can start gnome using `xinit gnome-session`
there are no /var/log/boot messages.
On trying to start my wireless network I notices that the network device is called "wlan0" (like it used to be) and not "wlp1s0" as it is now supposed to be with consistent network naming.
given that I can start gnome I think that gdm screwed up.
following is the /var/log/gdm/\:0-greeter.log file
** (gnome-settings-daemon:388): WARNING **: Failed to connect context: OK
(gnome-shell:462): Gvc-WARNING **: Failed to connect context: OK
failed to create drawable
JS LOG: GNOME Shell started at Sun Jul 07 2013 14:15:02 GMT+1000 (EST)
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
failed to create drawable
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
Window manager warning: Log level 8: g_source_remove: assertion `tag > 0' failed
gnome-session[366]: WARNING: Detected that screensaver has left the bus
gnome-session[366]: CRITICAL: gsm_manager_set_phase: assertion `GSM_IS_MANAGER (manager)' failed
(gnome-settings-daemon:388): GLib-GIO-WARNING **: Error releasing name org.gnome.SettingsDaemon: The connection is closed
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:388): GLib-GIO-WARNING **: Error releasing name org.freedesktop.ScreenSaver: The connection is closedhope you can help
thanks
Karl
Offline
As for you first error:
systemd-udevd[209]: specified group 'plugdev' unknownhttps://bugzilla.redhat.com/show_bug.cgi?id=815093
Check if you have /etc/udev/rules.d/99-libftdi.rules, I checked my 2 Arch installs, and don't have it,
so you probably are free to remove it when it exist.
the network device is called "wlan0" and not "wlp1s0" as it is now supposed to be with consistent network namingThis happens when you have '80-net-name-slot.rules' in /etc/udev/rules.d/ . It maskes persistent renaming rules for network devices
for
gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failedcheck https://bbs.archlinux.org/viewtopic.php?id=156331
and https://bbs.archlinux.org/viewtopic.php?pid=1210993\
Last edited by henk (2013-07-08 05:42:48)
Offline
Hi,
I do have some kind of similar problems...
I just did an upgrade. I can log in, then gdm starts(I can see briefly the background image), then the screen goes blank. I can interact with the keyboards, but that's all.
I do have this "plugdev" unknown error too (no call to libftdi that I can find however).
In my upgrade the following packages were upgraded :
xz
xterm
xorg-server
xorg-server-common
xf86-video-intel
transmission-gtk
subversion
qt4
python2-gobjects2
python-gobejcts
pygobject2-devel
opencv
man-pages
make
linux (3.9.8-1 -> 3.9.9-1)
libtheora
libpwquality
libgpg-error4ldb
tbd
lcms2
intel-dri
mesa-libgl
mesa
libvdpau
libdrm
gvim
vim-runtime
gvfs-obexftp
gvfs-afc
gvfs
gtksourceview3
gnome-terminal
vte3
vte-common
gnome-shell
libsecret
gnome-settings-daemon
ibus
gtk2
libxi
gnome-screensaver
gmime
gigi
giflib
filezilla
fille-roller
cluter-gtk
cifs-uutils
libwbclient
cfitsio
bluez-utils
bluez_libs
bleachbit
gnome-update-icon-cacheI'm thinking about downgrading some packages to see if it helps, but which one ? the gnome's ones ? gtk's ? xorg's ?
with journalctl I can see some errors maybe useful :
/usr/bin/dbus-launch[1390]: Window manager warning: CurrentTime used to choose focus window: focus window may not be correct
/usr/bin/dbus-launch[1390]: Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
gnome-session[1646]: Gdk-Warning: gnome-session: Fatal IO error 2 (no such file or directory) on X server :0
gdm(919): Glib-GObject: g_object_ref : assertion 'object->ref_count >0' failed
gdm(919): Glib-GObject: g_object_unref : assertion 'object->ref_count >0' failedany help welcome !
thanks
Offline
@henk, just FYI:
% grep plugdev /usr/lib/udev/rules.d/*
60-openobex.rules:ACTION=="add", SUBSYSTEM=="usb", PROGRAM="/usr/sbin/obex-check-device $attr{idVendor} $attr{idProduct}", MODE="660", GROUP="plugdev"Offline
While looking at the solution to this error (that I have too) :
gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failedI found that my problem was coming from "gnome-settings-daemon", when it's called my gnome session goes blank.
I tried to downgraded it from 3.8.3-2 to 3.8.3-1 but still it doesn't work..
I tried to downgrade most of my packages from today's upgrade (all of them expect gvfs, make, linux) ... nothing new...
Last edited by olivarch (2013-07-08 21:39:27)
Offline
I upgraded back everything, obviously nothing special happened.
Then, in front of the persistent blank screen, instead of shutting down my computer my I closed the laptop lid... It suspends my computer.
Then I opened it again, and I was hugely surprised to see in front of my eyes a working gnome session...
The problem is still here but I have a kind of work around for the (hopefully short) time being...
Offline
OK I just checked my /etc/udev/rules.d directory to "fix up the wlan0 stuff" and discovered that I have no rules!
None at all! /etc/udev/rules.d is empty!
I'm guessing this is the root of my problems.... any idea what I need to install to get the base rules back?
Offline
@henk, just FYI:
% grep plugdev /usr/lib/udev/rules.d/* 60-openobex.rules:ACTION=="add", SUBSYSTEM=="usb", PROGRAM="/usr/sbin/obex-check-device $attr{idVendor} $attr{idProduct}", MODE="660", GROUP="plugdev"
Thank you for the hint/correction!
@karlroberts, my excuses for pointing you in the wrong direction. WonderWoofy's post lead me to
https://bbs.archlinux.org/viewtopic.php?id=164676
which linked to
https://bugs.archlinux.org/task/35602
I think you should check this, and when neccesary act accordingly.
As for the changing of the device names, if there is no '80-net-name-slot.rules' in /etc/udev/ruled.d/
you might want to take a look at this thread,
and the the wiki.
Offline