Gnome 3.14 oh no! (gdm & gnome won't start)

I'm quite stumped about why I'm getting a "Gnome - oh no! Something has gone wrong" message. I try logging in but Gnome 3 doesn't work.
I am able to startx, but when I then try to do gnome-session I get:
Xlib: extension "GLX" missing on display ":0"
gnome-session-is-accelerated: No hardware 3D support
gnome-session-check-accelerated: Helper exited with code 256
gdm just hangs, as does lightdm.
I have nvidia-340xx installed.
I've been googling around without much luck.
I use gnome 3.14!
Help?

FYI For sure I'm not using a test environment and I can't think of any reason I would be running wayland. I believe wayland is installed on my system -- are you saying I should remove it?
When I run htop I certainly don't see anything mentioning wayland when I filter by gdm. And mutter isn't running. I do see a coredump today from /usr/bin/gdm, but no signs of it using wayland.
By the way, I saw on another thread that it might be worth investigating a possible interference from libvdpau with nvidia-settings. But I don't see any sign that libvdpau is running when I do systemctl -a | grep vd or systemctl -a | grep pau
Also, "glxinfo | grep rendering" and "glxinfo | grep NVIDIA" give the message: "(Error: unable to open display)"
Here's what I'm getting when I open gnome-shell --replace --debug
gnome-shell --replace
hand written notes:
Glib critical g_environ setenv assertion 'value!=NULL' failed
Cannot open display
Unable to init server: Could not connect: connection refused
Helllp? Also, would it help to uninstall mesa or wayland?

Similar Messages

[SOLVED] GDM/Gnome won't start after update

Today after I run pacman -Suy, GDM/Gnome won't start anymore after reboot. The error message I get after GDM starts is:
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. Please contact a system administrator
Does anyone have any idea what happened and how can I recover the system?
Here is the complete log for the update:
http://bpaste.net/show/209520/
Here is the journalctl -u gdm log:
http://sprunge.us/LEOU
Here is tail -2000 /var/log/messages.log:
http://sprunge.us/ObWY
And here is the /var/log/Xorg.0.log:
http://bpaste.net/show/209549/
I can't imagine any other log file that might help figure out what happened, let me know if there's anything else.
Any help is appreciated. Thanks.
Edit: I stopped gdm, created a ~/.xinitrc and could successfully start Gnome with startx. The problem remains with GDM.
Edit: The last update solved my problem: http://sprunge.us/RKWA
Last edited by falmp (2014-04-22 20:38:20)

I'm not sure my issue is really the same one, but am hoping for some guidance here if possible. Trying to start GDM gives me the same error message/screen. After tdm fails I can switch to a console,
sudo systemctl stop gdm.service
then
sudo systemctl start lightdm.service
and lightdm starts fine. However, trying to log in to gnome-session gives me the very same error as I had with GDM. I can log into XFCE just fine. Attempting to start gnome-ession via startx also gives me the error screen. Does anyone know how I can diagnose the problem? Thanks,
Matt

[SOLVED] GDM/Gnome won't start

It's been more than a month now that my computer started to give me an error after booting. Before GDM starts, I get the following message:
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. Please contact a system administrator
This is not always, I suppose it happens 70% of the time (I need to keep restarting it a few times to get it working). I'm not sure it's a GDM problem because if I CTRL+ALT+F5, login and startx, it'll give me the same error message.
Does anyone have any idea what happened and how can I fix it? I'm running the latest packages.
I don't know which log files might help, let me know and I'll post them.
Any help is appreciated. Thanks.
Edit: here are some logs that might help:
Here you can see at least one failed reboot (the last lines was a sucessful boot ):
$ sudo journalctl -n 1000 -u gdm | curl -F 'sprunge=<-' sprunge.us
http://sprunge.us/KfSf
On this one there's a promising line Sep 18 20:53:07 localhost gdm[400]: Failed to give slave programs access to the display. Trying to proceed.:
$ sudo tail -1000 /var/log/messages.log | curl -F 'sprunge=<-' sprunge.us
http://sprunge.us/fOZU
Am I right to assume Xorg.0.log is from the current session? So I'm pasting the Xorg.1.log, which should be the previous failed one:
$ cat /var/log/Xorg.1.log | curl -F 'sprunge=<-' sprunge.us
http://sprunge.us/OaXL
Hell, it won't hurt if I provide the current one too:
$ cat /var/log/Xorg.0.log | curl -F 'sprunge=<-' sprunge.us
http://sprunge.us/HVPc
Edit 2: I noticed the error only occurs when I get the following message on the boot screen:
[drm:init:ring:common] *ERROR* render ring initialization failed ctl 0001f001 (valid? 1) head 0000b174 tail 00000000 start 00303000 [expected 00303000]
[drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged
I could not find this message on the log files, so here is a picture:
http://imgur.com/Wf4mhXv
Last edited by falmp (2014-09-18 22:53:10)

Well, seems to be a problem with the kernel 3.16.x:
https://bbs.archlinux.org/viewtopic.php?id=185650
I solved it installing the kernel from repo-ck (http://repo-ck.com/), it's all good now.

Gnome won't start after update

Hey, so after I've updated gnome to 3.14 it refuses to start. The moment I get past the login screen (that works - I use lightdm), gnome will just tell me that "something has gone wrong" and it won't launch the session. For the past two hours or so I've been trying to identify the issue with no good results. What I think might be relevant is that I use the catalyst driver and also this part of journalctl -e /usr/bin/gnome-shell:
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: Could not parse desktop file screensaver-settings.desktop or it references a not found TryExec binary
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: WARNING: Could not parse desktop file screensaver-settings.desktop or it references a not found TryExec binary
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: ** (gnome-settings-daemon:626): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: ** (gnome-settings-daemon:626): WARNING **: Ignoring unknown module 'org.gnome.settings-daemon.plugins.updates'
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: X Error of failed request: BadValue (integer parameter out of range for operation)
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Major opcode of failed request: 141 (RANDR)
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Minor opcode of failed request: 13 (RRChangeOutputProperty)
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Value in failed request: 0x99
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Serial number of failed request: 280
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: Current serial number in output stream: 282
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:28 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: X Error of failed request: BadValue (integer parameter out of range for operation)
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Major opcode of failed request: 141 (RANDR)
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Minor opcode of failed request: 13 (RRChangeOutputProperty)
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Value in failed request: 0x99
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Serial number of failed request: 280
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Current serial number in output stream: 282
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: gnome-session[602]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Oct 16 23:19:29 snowy-laptop-arch gnome-session[602]: Unrecoverable failure in required component gnome-shell.desktop
Any ideas? ^^
Last edited by SnowyMan95 (2014-10-17 19:44:43)

Same problem here, and I think that it's all Catalyst fault.
Many people are reporting GNOME 3.14 / Catalyst compatibility issue in AMD Bar & Grill thread (https://bbs.archlinux.org/viewtopic.php?id=57084&p=272) and I totally agree with Vi0l0 (unofficial Catalyst packages maintainer):
Vi0l0 wrote:As for the GNOME 3.14 - wish I have more time to look at this closer, I catched problems with GNOME latelly (but before 3.14) - it started to crash before start - I spent not much time on it, but didn't find solution. Fixing it is not that important for me right now, since im planning to install arch on btrfs 2xSSD smile. Its just the time... Wish I had some kind of clone of myself with shared awareness tongue.
But anyhow I think that GNOME 3.14 support could be real problem atm (at least with unmodified gnome packages), afaik 3.14 is really close to wayland and catalyst doesn't even have egl.
EDIT: if confirmed seems to be a display manager issue:
Vi0L0 wrote:BTW I installed new arch on new drives, and all seems to work fine, GDM didn't start so I used KDM. All problems are gone and GNOME 3.14 works pretty nice.
Last edited by IVIonty (2014-10-19 20:13:20)

[SOLVED] Gnome-won't start

Dear archies,
I using fluxbox right now but I wanted migrate to Gnome 3.2.1 but I have problem with start. I used lxdm as login manager (becase there I can chooose session - but I tried gdm also with the same result). Login was OK but then I got just gnome default "blue-zebra" background and that's all... No gnome-shell, no gnome-panel, nothing. Computer doesn't freeze but no desktop. Fluxbox starts normal.
Here is my etc/rc.conf
[zrebec@bella ~]$ cat /etc/rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# See 'man 5 rc.conf' for more details
# LOCALIZATION
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Bratislava"
KEYMAP="sk-qwertz"
CONSOLEFONT="lat2-16"
CONSOLEMAP="8859-2"
LOCALE="sk_SK.UTF8"
DAEMON_LOCALE="yes"
USECOLOR="yes"
# HARDWARE
MODULES=(fuse vboxdrv)
USEDMRAID="no"
USEBTRFS="no"
USELVM="no"
# NETWORKING
HOSTNAME="bella"
interface=
address=
netmask=
broadcast=
gateway=
NETWORK_PERSIST="no"
NETWORKS=(eth0 eth1)
# DAEMONS
DAEMONS=(syslog-ng network crond gpm alsa dbus net-profiles avahi-daemon lxdm httpd postgresql)
I using proprietary nvidia driver but drivers works very fine.
Last edited by Nelly (2012-02-19 16:42:01)

It also sounds a lot like this issue.
The solution there seemed to be (re)installing gnome-shell and libltdl.
Also, have you tried gdm? I don't know the ins-and-outs but it seems gdm is becoming more important for a functional gnome session.
Last edited by Trilby (2012-02-17 01:18:13)

[SOLVED] GNOME won't start properly

Hello,
I have just started with Arch and already encountered a newbie problem I installed Arch ok using the beginner's guide, the base system is ok, I got up to the point of installing desktop environment (GNOME3 is my choice). I installed mesa, drivers, X etc and Gnome ofc. I added "... dbus gdm..." into DAEMONS array and rebooted. The blue Gnome wallpaper shows normally but the login window is not the usual black Shell one, but grey old-looking instead (fallback mode?). I've got only the ugly X's clock cursor but I can click on my user's name and login. However, nothing appears, just the same blue background and the clock cursor
Anyone has an idea what I might be doing wrong? Thanks
Last edited by phobossion (2012-02-11 09:29:09)

phobossion wrote:
Hello,
I have just started with Arch and already encountered a newbie problem I installed Arch ok using the beginner's guide, the base system is ok, I got up to the point of installing desktop environment (GNOME3 is my choice). I installed mesa, drivers, X etc and Gnome ofc. I added "... dbus gdm..." into DAEMONS array and rebooted. The blue Gnome wallpaper shows normally but the login window is not the usual black Shell one, but grey old-looking instead (fallback mode?). I've got only the ugly X's clock cursor but I can click on my user's name and login. However, nothing appears, just the same blue background and the clock cursor
Anyone has an idea what I might be doing wrong? Thanks
Please post your rc.conf. Also, which video card and drivers and how did you install Gnome?

GNOME won't start

When I start GDM it just displays.
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. Please contact a system administrator
What am I supposed to do? I re installed gnome but the problem still persists.

JS ERROR: !!! Exception was: Error: Failed to convert UTF-8 string to JS string: Invalid byte sequence in conversion input
JS ERROR: !!! lineNumber = '0'
JS ERROR: !!! fileName = '"gjs_throw"'
JS ERROR: !!! stack = '"("Failed to convert UTF-8 string to JS string: Invalid byte sequence in conversion input")@gjs_throw:0
have you set correctly the locale? https://wiki.archlinux.org/index.php/Locale

Gnome won't start: Oh no! Something has gone wrong.

Hello,
after a week holyday i installed all new updates on my Notebook (Asus UX31). During shutdown it freezed and i had to switch off the Notebook. Now if i start i can login with Slim and than gnome starts with an error display: "Oh no! Something has gone wrong. A problem has occured and the system can't recover. All extensions have been disabled as precaution." I can klick on a Log Out Button but if i log in again, the same is happening. It's funny that there appear reminders from evolution and the dialog to unlock the keyring.
Any suggestions?
Here are some logs:
/var/log/Xorg.0.log
[ 16.074]
X.Org X Server 1.14.2
Release Date: 2013-06-25
[ 16.074] X Protocol Version 11, Revision 0
[ 16.074] Build Operating System: Linux 3.9.7-1-ARCH x86_64
[ 16.074] Current Operating System: Linux oliver-zen 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64
[ 16.074] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=cd85b266-a33f-4abf-93d6-7ac918f8ff26 ro quiet add_efi_memmap i915.i915_enable_rc6=1 drm.vblankoffdelay=1 i915.semaphores=1
[ 16.074] Build Date: 01 July 2013 10:48:42AM
[ 16.074]
[ 16.074] Current version of pixman: 0.30.0
[ 16.074] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 16.074] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 16.074] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 3 19:37:30 2013
[ 16.075] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 16.075] (==) No Layout section. Using the first Screen section.
[ 16.075] (==) No screen section available. Using defaults.
[ 16.075] (**) |-->Screen "Default Screen Section" (0)
[ 16.075] (**) | |-->Monitor "<default monitor>"
[ 16.076] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 16.076] (**) | |-->Device "Card0"
[ 16.076] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 16.076] (==) Automatically adding devices
[ 16.076] (==) Automatically enabling devices
[ 16.076] (==) Automatically adding GPU devices
[ 16.076] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 16.076] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 16.076] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 16.076] (II) Loader magic: 0x7fdc20
[ 16.076] (II) Module ABI versions:
[ 16.076] X.Org ANSI C Emulation: 0.4
[ 16.076] X.Org Video Driver: 14.1
[ 16.076] X.Org XInput driver : 19.1
[ 16.076] X.Org Server Extension : 7.0
[ 16.077] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 16.079] (--) PCI:*(0:0:2:0) 8086:0116:1043:1427 rev 9, Mem @ 0xddc00000/4194304, 0xc0000000/268435456, I/O @ 0x0000e000/64
[ 16.079] Initializing built-in extension Generic Event Extension
[ 16.079] Initializing built-in extension SHAPE
[ 16.079] Initializing built-in extension MIT-SHM
[ 16.079] Initializing built-in extension XInputExtension
[ 16.079] Initializing built-in extension XTEST
[ 16.079] Initializing built-in extension BIG-REQUESTS
[ 16.079] Initializing built-in extension SYNC
[ 16.079] Initializing built-in extension XKEYBOARD
[ 16.079] Initializing built-in extension XC-MISC
[ 16.079] Initializing built-in extension SECURITY
[ 16.079] Initializing built-in extension XINERAMA
[ 16.079] Initializing built-in extension XFIXES
[ 16.079] Initializing built-in extension RENDER
[ 16.079] Initializing built-in extension RANDR
[ 16.079] Initializing built-in extension COMPOSITE
[ 16.079] Initializing built-in extension DAMAGE
[ 16.079] Initializing built-in extension MIT-SCREEN-SAVER
[ 16.079] Initializing built-in extension DOUBLE-BUFFER
[ 16.079] Initializing built-in extension RECORD
[ 16.079] Initializing built-in extension DPMS
[ 16.079] Initializing built-in extension X-Resource
[ 16.079] Initializing built-in extension XVideo
[ 16.079] Initializing built-in extension XVideo-MotionCompensation
[ 16.079] Initializing built-in extension XFree86-VidModeExtension
[ 16.079] Initializing built-in extension XFree86-DGA
[ 16.080] Initializing built-in extension XFree86-DRI
[ 16.080] Initializing built-in extension DRI2
[ 16.080] (II) LoadModule: "glx"
[ 16.080] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 16.080] (II) Module glx: vendor="X.Org Foundation"
[ 16.081] compiled for 1.14.2, module version = 1.0.0
[ 16.081] ABI class: X.Org Server Extension, version 7.0
[ 16.081] (==) AIGLX enabled
[ 16.081] Loading extension GLX
[ 16.081] (II) LoadModule: "intel"
[ 16.081] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 16.081] (II) Module intel: vendor="X.Org Foundation"
[ 16.081] compiled for 1.14.2, module version = 2.21.13
[ 16.081] Module class: X.Org Video Driver
[ 16.081] ABI class: X.Org Video Driver, version 14.1
[ 16.082] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
HD Graphics 4600, Iris(TM) Pro Graphics 5200,
Haswell CRW Server (GT1), Haswell CRW Server (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, ValleyView PO board
[ 16.084] (++) using VT number 7
[ 16.096] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 16.096] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 16.096] (==) intel(0): RGB weight 888
[ 16.096] (==) intel(0): Default visual is TrueColor
[ 16.096] (--) intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2)
[ 16.096] (**) intel(0): Relaxed fencing enabled
[ 16.096] (**) intel(0): Wait on SwapBuffers? enabled
[ 16.096] (**) intel(0): Triple buffering? enabled
[ 16.096] (**) intel(0): Framebuffer tiled
[ 16.096] (**) intel(0): Pixmaps tiled
[ 16.096] (**) intel(0): 3D buffers tiled
[ 16.096] (**) intel(0): SwapBuffers wait enabled
[ 16.096] (==) intel(0): video overlay key set to 0x101fe
[ 16.096] (II) intel(0): Output eDP1 has no monitor section
[ 16.097] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video0
[ 16.098] (II) intel(0): Output VGA1 has no monitor section
[ 16.098] (II) intel(0): Output HDMI1 has no monitor section
[ 16.099] (II) intel(0): Output DP1 has no monitor section
[ 16.099] (II) intel(0): EDID for output eDP1
[ 16.099] (II) intel(0): Manufacturer: COR Model: 17db Serial#: 0
[ 16.099] (II) intel(0): Year: 2011 Week: 20
[ 16.099] (II) intel(0): EDID Version: 1.4
[ 16.099] (II) intel(0): Digital Display Input
[ 16.099] (II) intel(0): 6 bits per channel
[ 16.099] (II) intel(0): Digital interface is DisplayPort
[ 16.099] (II) intel(0): Max Image Size [cm]: horiz.: 29 vert.: 16
[ 16.099] (II) intel(0): Gamma: 2.20
[ 16.099] (II) intel(0): No DPMS capabilities specified
[ 16.099] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 16.099] (II) intel(0): First detailed timing is preferred mode
[ 16.099] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 16.099] (II) intel(0): redX: 0.574 redY: 0.341 greenX: 0.352 greenY: 0.564
[ 16.099] (II) intel(0): blueX: 0.162 blueY: 0.118 whiteX: 0.313 whiteY: 0.329
[ 16.099] (II) intel(0): Manufacturer's mask: 0
[ 16.099] (II) intel(0): Supported detailed timing:
[ 16.099] (II) intel(0): clock: 97.8 MHz Image Size: 293 x 164 mm
[ 16.099] (II) intel(0): h_active: 1600 h_sync: 1648 h_sync_end 1680 h_blank_end 1760 h_border: 0
[ 16.099] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 908 v_blanking: 926 v_border: 0
[ 16.099] (II) intel(0): Supported detailed timing:
[ 16.099] (II) intel(0): clock: 97.8 MHz Image Size: 293 x 164 mm
[ 16.099] (II) intel(0): h_active: 1600 h_sync: 1648 h_sync_end 1680 h_blank_end 1760 h_border: 0
[ 16.099] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 908 v_blanking: 926 v_border: 0
[ 16.099] (II) intel(0): CPT
[ 16.099] (II) intel(0): Unknown vendor-specific block 0
[ 16.099] (II) intel(0): EDID (in hex):
[ 16.099] (II) intel(0): 00ffffffffffff000df2db1700000000
[ 16.099] (II) intel(0): 14150104951d10780a129593575a9029
[ 16.099] (II) intel(0): 1e505400000001010101010101010101
[ 16.099] (II) intel(0): 010101010101322640a060841a303020
[ 16.099] (II) intel(0): 350025a410000018322640a060841a30
[ 16.099] (II) intel(0): 3020350025a410000018000000fe0043
[ 16.099] (II) intel(0): 50542020202020202020202000000000
[ 16.099] (II) intel(0): 004e4c41413133335541303241200044
[ 16.100] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 16.100] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 16.100] (II) intel(0): Printing probed modes for output eDP1
[ 16.100] (II) intel(0): Modeline "1600x900"x60.0 97.78 1600 1648 1680 1760 900 903 908 926 -hsync -vsync (55.6 kHz eP)
[ 16.100] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 16.100] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 16.100] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 16.100] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 16.101] (II) intel(0): EDID for output VGA1
[ 16.102] (II) intel(0): EDID for output HDMI1
[ 16.102] (II) intel(0): EDID for output DP1
[ 16.102] (II) intel(0): Output eDP1 connected
[ 16.102] (II) intel(0): Output VGA1 disconnected
[ 16.102] (II) intel(0): Output HDMI1 disconnected
[ 16.102] (II) intel(0): Output DP1 disconnected
[ 16.102] (II) intel(0): Using exact sizes for initial modes
[ 16.102] (II) intel(0): Output eDP1 using initial mode 1600x900
[ 16.102] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 16.102] (II) intel(0): Kernel page flipping support detected, enabling
[ 16.102] (==) intel(0): DPI set to (96, 96)
[ 16.102] (II) Loading sub module "fb"
[ 16.102] (II) LoadModule: "fb"
[ 16.102] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 16.103] (II) Module fb: vendor="X.Org Foundation"
[ 16.103] compiled for 1.14.2, module version = 1.0.0
[ 16.103] ABI class: X.Org ANSI C Emulation, version 0.4
[ 16.103] (II) Loading sub module "dri2"
[ 16.103] (II) LoadModule: "dri2"
[ 16.103] (II) Module "dri2" already built-in
[ 16.103] (==) Depth 24 pixmap format is 32 bpp
[ 16.103] (II) intel(0): [DRI2] Setup complete
[ 16.103] (II) intel(0): [DRI2] DRI driver: i965
[ 16.103] (II) intel(0): Allocated new frame buffer 1600x900 stride 6656, tiled
[ 16.105] (II) UXA(0): Driver registered support for the following operations:
[ 16.105] (II) solid
[ 16.105] (II) copy
[ 16.105] (II) composite (RENDER acceleration)
[ 16.105] (II) put_image
[ 16.105] (II) get_image
[ 16.105] (==) intel(0): Backing store disabled
[ 16.105] (==) intel(0): Silken mouse enabled
[ 16.105] (II) intel(0): Initializing HW Cursor
[ 16.105] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 16.107] (==) intel(0): DPMS enabled
[ 16.107] (==) intel(0): Intel XvMC decoder enabled
[ 16.107] (II) intel(0): Set up textured video
[ 16.108] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 16.108] (II) intel(0): direct rendering: DRI2 Enabled
[ 16.108] (==) intel(0): hotplug detection: "enabled"
[ 16.130] (--) RandR disabled
[ 16.144] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/i965_dri.so failed (/usr/lib/xorg/modules/dri/i965_dri.so: invalid ELF header)
[ 16.144] (EE) AIGLX: reverting to software rendering
[ 16.144] (II) AIGLX: Screen 0 is not DRI capable
[ 16.174] (II) AIGLX: Loaded and initialized swrast
[ 16.174] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 16.175] (II) intel(0): Setting screen physical size to 423 x 238
[ 16.402] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[ 16.402] (**) Video Bus: Applying InputClass "system-keyboard"
[ 16.402] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 16.402] (**) Video Bus: Applying InputClass "keyboard"
[ 16.402] (II) LoadModule: "evdev"
[ 16.403] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 16.403] (II) Module evdev: vendor="X.Org Foundation"
[ 16.403] compiled for 1.14.2, module version = 2.8.1
[ 16.403] Module class: X.Org XInput Driver
[ 16.403] ABI class: X.Org XInput driver, version 19.1
[ 16.403] (II) Using input driver 'evdev' for 'Video Bus'
[ 16.403] (**) Video Bus: always reports core events
[ 16.403] (**) evdev: Video Bus: Device: "/dev/input/event11"
[ 16.403] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 16.403] (--) evdev: Video Bus: Found keys
[ 16.403] (II) evdev: Video Bus: Configuring as keyboard
[ 16.403] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11/event11"
[ 16.403] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 16.403] (**) Option "xkb_rules" "evdev"
[ 16.404] (**) Option "xkb_model" "pc104"
[ 16.404] (**) Option "xkb_layout" "de"
[ 16.464] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 16.464] (**) Power Button: Applying InputClass "system-keyboard"
[ 16.464] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 16.464] (**) Power Button: Applying InputClass "keyboard"
[ 16.464] (II) Using input driver 'evdev' for 'Power Button'
[ 16.464] (**) Power Button: always reports core events
[ 16.464] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 16.464] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 16.464] (--) evdev: Power Button: Found keys
[ 16.464] (II) evdev: Power Button: Configuring as keyboard
[ 16.464] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event2"
[ 16.464] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 16.464] (**) Option "xkb_rules" "evdev"
[ 16.464] (**) Option "xkb_model" "pc104"
[ 16.464] (**) Option "xkb_layout" "de"
[ 16.466] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 16.466] (II) No input driver specified, ignoring this device.
[ 16.466] (II) This device may have been added with another device file.
[ 16.466] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 16.466] (**) Sleep Button: Applying InputClass "system-keyboard"
[ 16.466] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 16.466] (**) Sleep Button: Applying InputClass "keyboard"
[ 16.466] (II) Using input driver 'evdev' for 'Sleep Button'
[ 16.466] (**) Sleep Button: always reports core events
[ 16.466] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[ 16.466] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 16.466] (--) evdev: Sleep Button: Found keys
[ 16.466] (II) evdev: Sleep Button: Configuring as keyboard
[ 16.467] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event3"
[ 16.467] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 16.467] (**) Option "xkb_rules" "evdev"
[ 16.467] (**) Option "xkb_model" "pc104"
[ 16.467] (**) Option "xkb_layout" "de"
[ 16.467] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 16.468] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event5)
[ 16.468] (II) No input driver specified, ignoring this device.
[ 16.468] (II) This device may have been added with another device file.
[ 16.469] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event6)
[ 16.469] (II) No input driver specified, ignoring this device.
[ 16.469] (II) This device may have been added with another device file.
[ 16.469] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
[ 16.469] (II) No input driver specified, ignoring this device.
[ 16.469] (II) This device may have been added with another device file.
[ 16.470] (II) config/udev: Adding input device USB2.0 VGA Webcam (/dev/input/event9)
[ 16.470] (**) USB2.0 VGA Webcam: Applying InputClass "system-keyboard"
[ 16.470] (**) USB2.0 VGA Webcam: Applying InputClass "evdev keyboard catchall"
[ 16.470] (**) USB2.0 VGA Webcam: Applying InputClass "keyboard"
[ 16.470] (II) Using input driver 'evdev' for 'USB2.0 VGA Webcam'
[ 16.470] (**) USB2.0 VGA Webcam: always reports core events
[ 16.470] (**) evdev: USB2.0 VGA Webcam: Device: "/dev/input/event9"
[ 16.470] (--) evdev: USB2.0 VGA Webcam: Vendor 0x13d3 Product 0x5719
[ 16.470] (--) evdev: USB2.0 VGA Webcam: Found keys
[ 16.470] (II) evdev: USB2.0 VGA Webcam: Configuring as keyboard
[ 16.470] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9/event9"
[ 16.470] (II) XINPUT: Adding extended input device "USB2.0 VGA Webcam" (type: KEYBOARD, id 9)
[ 16.470] (**) Option "xkb_rules" "evdev"
[ 16.470] (**) Option "xkb_model" "pc104"
[ 16.470] (**) Option "xkb_layout" "de"
[ 16.471] (II) config/udev: Adding input device Asus WMI hotkeys (/dev/input/event8)
[ 16.472] (**) Asus WMI hotkeys: Applying InputClass "system-keyboard"
[ 16.472] (**) Asus WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 16.472] (**) Asus WMI hotkeys: Applying InputClass "keyboard"
[ 16.472] (II) Using input driver 'evdev' for 'Asus WMI hotkeys'
[ 16.472] (**) Asus WMI hotkeys: always reports core events
[ 16.472] (**) evdev: Asus WMI hotkeys: Device: "/dev/input/event8"
[ 16.472] (--) evdev: Asus WMI hotkeys: Vendor 0 Product 0
[ 16.472] (--) evdev: Asus WMI hotkeys: Found keys
[ 16.472] (II) evdev: Asus WMI hotkeys: Configuring as keyboard
[ 16.472] (**) Option "config_info" "udev:/sys/devices/platform/asus-nb-wmi/input/input8/event8"
[ 16.472] (II) XINPUT: Adding extended input device "Asus WMI hotkeys" (type: KEYBOARD, id 10)
[ 16.472] (**) Option "xkb_rules" "evdev"
[ 16.472] (**) Option "xkb_model" "pc104"
[ 16.472] (**) Option "xkb_layout" "de"
[ 16.473] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 16.473] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[ 16.473] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 16.473] (**) AT Translated Set 2 keyboard: Applying InputClass "keyboard"
[ 16.473] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 16.473] (**) AT Translated Set 2 keyboard: always reports core events
[ 16.473] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 16.473] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 16.473] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 16.473] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 16.473] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 16.473] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 16.474] (**) Option "xkb_rules" "evdev"
[ 16.474] (**) Option "xkb_model" "pc104"
[ 16.474] (**) Option "xkb_layout" "de"
[ 16.475] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event10)
[ 16.475] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchpad catchall"
[ 16.475] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[ 16.475] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default clickpad buttons"
[ 16.475] (II) LoadModule: "synaptics"
[ 16.475] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 16.475] (II) Module synaptics: vendor="X.Org Foundation"
[ 16.475] compiled for 1.14.1, module version = 1.7.1
[ 16.475] Module class: X.Org XInput Driver
[ 16.475] ABI class: X.Org XInput driver, version 19.1
[ 16.475] (II) Using input driver 'synaptics' for 'ETPS/2 Elantech Touchpad'
[ 16.475] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 16.475] (**) Option "Device" "/dev/input/event10"
[ 16.596] (II) synaptics: ETPS/2 Elantech Touchpad: found clickpad property
[ 16.597] (--) synaptics: ETPS/2 Elantech Touchpad: x-axis range 0 - 3260 (res 32)
[ 16.597] (--) synaptics: ETPS/2 Elantech Touchpad: y-axis range 0 - 2119 (res 32)
[ 16.597] (--) synaptics: ETPS/2 Elantech Touchpad: pressure range 0 - 255
[ 16.597] (--) synaptics: ETPS/2 Elantech Touchpad: finger width range 0 - 15
[ 16.597] (--) synaptics: ETPS/2 Elantech Touchpad: buttons: left double triple
[ 16.597] (--) synaptics: ETPS/2 Elantech Touchpad: Vendor 0x2 Product 0xe
[ 16.597] (**) Option "TapButton1" "1"
[ 16.597] (**) Option "TapButton2" "2"
[ 16.597] (**) Option "TapButton3" "3"
[ 16.597] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 16.597] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 16.597] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 16.631] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input10/event10"
[ 16.631] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 12)
[ 16.631] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[ 16.631] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MaxSpeed is now 1.75
[ 16.631] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) AccelFactor is now 0.051
[ 16.632] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
[ 16.632] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 1
[ 16.632] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[ 16.632] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[ 16.632] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 16.633] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse0)
[ 16.633] (**) ETPS/2 Elantech Touchpad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 16.633] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 16.633] (II) No input driver specified, ignoring this device.
[ 16.633] (II) This device may have been added with another device file.
[ 30.465] (II) UnloadModule: "synaptics"
[ 30.465] (II) evdev: AT Translated Set 2 keyboard: Close
[ 30.465] (II) UnloadModule: "evdev"
[ 30.465] (II) evdev: Asus WMI hotkeys: Close
[ 30.465] (II) UnloadModule: "evdev"
[ 30.465] (II) evdev: USB2.0 VGA Webcam: Close
[ 30.465] (II) UnloadModule: "evdev"
[ 30.465] (II) evdev: Sleep Button: Close
[ 30.465] (II) UnloadModule: "evdev"
[ 30.465] (II) evdev: Power Button: Close
[ 30.465] (II) UnloadModule: "evdev"
[ 30.465] (II) evdev: Video Bus: Close
[ 30.466] (II) UnloadModule: "evdev"
[ 30.480] (EE) Server terminated successfully (0). Closing log file.
~/.xsession-errors
Tracker-Message: Setting up monitor for changes to config file:'/home/oliver/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/oliver/.config/tracker/tracker-store.cfg'
gnome-session[1818]: WARNING: Failed to start app: Unable to start application: Kindprozess »dropboxd« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden)
Tracker-Message: Setting up monitor for changes to config file:'/home/oliver/.config/tracker/tracker-miner-fs.cfg'
** Message: applet now removed from the notification area
** Message: using fallback from indicator to GtkStatusIcon
(tracker-miner-fs:1925): Tracker-WARNING **: Invalid desktop file: 'file:///usr/share/desktop-directories/X-Unity-All-Applications.directory'
(tracker-miner-fs:1925): Tracker-WARNING **: Couldn't get name, missing key (Name)
JS ERROR: !!! WARNING: 'anonymous function does not always return a value'
JS ERROR: !!! WARNING: file '/home/oliver/.local/share/gnome-shell/extensions/[email protected]/extension.js' line 597 exception 0 number 157
JS ERROR: !!! WARNING: 'anonymous function does not always return a value'
JS ERROR: !!! WARNING: file '/home/oliver/.local/share/gnome-shell/extensions/[email protected]/extension.js' line 1012 exception 0 number 157
(gnome-shell:1897): Clutter-CRITICAL **: clutter_actor_insert_child_at_index: assertion `child->priv->parent == NULL' failed
** Message: applet now embedded in the notification area
Fensterverwalter-Warnung:CurrentTime used to choose focus window; focus window may not be correct.
Fensterverwalter-Warnung:Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
(gnome-shell:1897): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'.
Individuals will not be linked properly and creating new links between Personas will not work.
The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.
gnome-session[1818]: WARNING: Could not launch application 'gdu-notification-daemon.desktop': Unable to start application: Kindprozess »/usr/lib/gnome-disk-utility/gdu-notification-daemon« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden)
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Bilder/Bildschirmfoto%20von%20%C2%BB2013-06-18%2022:43:01%C2%AB.png" was not found, exec: gnome-settings-daemon, mime_type: image/png
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/yi.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/Mabu.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/Sommerlager.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/MabuChongquan.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/basketball/klein/Basketball1.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/basketball/klein/Basketball2.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
(gnome-settings-daemon:1878): GLib-CRITICAL **: g_variant_get_int32: assertion `g_variant_is_of_type (value, G_VARIANT_TYPE_INT32)' failed
** (update-notifier:2110): WARNING **: log file empty (logrotate?) /var/log/dpkg.log
** (update-notifier:2110): WARNING **: log file empty (logrotate?) /var/log/apt/term.log
WARNING:root:timeout reached, exiting
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Bilder/Bildschirmfoto%20von%20%C2%BB2013-06-18%2022:43:01%C2%AB.png" was not found, exec: gnome-settings-daemon, mime_type: image/png
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/yi.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/Mabu.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/Sommerlager.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/Kung%20Fu/MabuChongquan.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/basketball/klein/Basketball1.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
** (zeitgeist-datahub:2032): WARNING **: recent-manager-provider.vala:133: Desktop file for "file:///home/oliver/Tempel%20Steyr/Kindersportmesse/Fotos/basketball/klein/Basketball2.jpg" was not found, exec: plugin-container, mime_type: image/jpeg
Fensterverwalter-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Rhythmbox)
Fensterverwalter-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Fensterverwalter-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Rhythmbox)
Fensterverwalter-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Fensterverwalter-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Rhythmbox)
Fensterverwalter-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(gnome-settings-daemon:1878): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(gnome-settings-daemon:1878): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:1933): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
(update-notifier:2110): Gdk-WARNING **: update-notifier: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
(evolution-alarm-notify:2061): Gdk-WARNING **: evolution-alarm-notify: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
(gnome-screensaver:2031): Gdk-WARNING **: gnome-screensaver: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
Fensterverwalter-Warnung:Log level 16: gnome-shell: Fatal IO error 0 (Erfolg) on X server :0.
(gnome-shell-calendar-server:1967): Gdk-WARNING **: gnome-shell-calendar-server: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
** (zeitgeist-datahub:2032): WARNING **: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
(tracker-miner-fs:1925): Tracker-CRITICAL **: Could not execute sparql: Verbindung ist geschlossen
(tracker-miner-fs:1925): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Verbindung ist geschlossen
(tracker-miner-fs:1925): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Verbindung ist geschlossen
(tracker-miner-fs:1925): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Verbindung ist geschlossen
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 1788 requests (1788 known processed) with 0 events remaining.

Meanwhile i found out that tracker could be the source of this problem. If not, tracker has a problem. first i tried to reinstall tracker, output was a lot of lines with:
tracker: /usr/share/ tracker-concerning-files exist in filesystem
then i deinstalled it. now when i want to install it, a similar output like obove comes.
Last edited by meson11 (2013-08-05 16:29:52)

GNOME won't start as a user !! but start's as root

Hello,
There's a funny problem goin on my system.
When I type xinit /usr/bin/gnome-session as root, it works fine (posting this as root).
But when I do it from user account, gnome starts and immediately quits.
I am on a custom compiled kernel. (Although the problem is the same on arch's official kernel).
What could be the problem ? I think its related to D-Bus.
Here's what xinit echoed on the ttt0 when executed as user:
http://dpaste.com/111771/
Last edited by nilesh (2009-10-25 17:35:06)

Well, I've filed a bug on bugs.gnome.org, let's see what GNOME has to say for this.
I have observed something new-
If startx is run as root, the same behavior is found, but if xinit /usr/bin/gnome-session is run, it works.
What does this mean - GNOME buggy or X buggy ? any guesses ?
Last edited by nilesh (2009-10-26 12:12:58)

Gnome won't start for regular user

I've got Xorg installed, and KDE. These both work fine for regular users. I decided to put Gnome on the box and play with it, and it loads fine for root. When I log in as a regular user and try to start Gnome, it comes up with an ugly desktop, a splash screen, then just an X for the mouse on the ugly desktop.
I'm assuming this must be a permissions problem, but I'm not sure what needs to be changed. I checked out the gnome and kde directories, and everything seems to be owned by root, so I know I'm missing something somewhere.
If permissions, what needs to be changed? If not, then what?

I've upgraded to gnome 2.12, it still doesn't load
As it _tries_ to load, it brings up a message box saying "gnome-settings-handler could not be started" or something to that effect, which basically means nothing can run.
I tried deleting /tmp, didn't work.
I'm getting _really_ frustrated
I dont want to go back to XFCE (I dont want to open another terminal just to eject my dvd drive ever again), and I'm getting insanely sick of KDE.. it's just un-usable..
Sorry if anyone out there likes KDE.. no offence.. but I just find it un-usable..

After the last kernel update to 3.18, Gnome won't start!

I can still boot without any problems up to the GDM screen, but after entering the password, I get stuck with a black screen. No keyboard, no mouse, nothing.
If I start an i3 session instead, the whole system locks up if I try to launch Chromium or Epiphany for example.
I have an NVIDIA 9400M graphic card.
Last edited by kaixi (2015-01-17 09:25:51)

@christophwu Woah, you're right. It is caused by broadcom-wl. But I didn't see anything strange on the journal. I can confirm that after uninstalling the driver, I can login into my desktop.
As for now, I'll probably stay with the 3.14 LTS kernel. Can't work without wifi.
Last edited by kaixi (2015-01-18 12:12:51)

Gnome AND KDE won't start (i686 and 64bit)

http://bbs.archlinux.org/viewtopic.php?id=71991
I've had a rough time these past few days and I posted earlier on Arch64 forums thinking it was just architecture thing but as it turns out after my reinstallation of Arch to 64 bit again (First i686, then 64, then i686 and now 64 again) I finally got it to work but this time Gnome is a pain in the ass, it didn't work with KDE either but KDE never gave me an error or gave me an option to failsafe into the OS.
$HOME/.xsession-errors:
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
gnome-session[3898]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-session[3898]: CRITICAL: dbus_g_connection_get_connection: assertion `gconnection' failed
process 3898: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
gnome-session[3898]: ******************* START ********************************
gnome-session[3898]: Frame 0: gnome-session [0x4192d7]
gnome-session[3898]: Frame 1: gnome-session [0x419426]
gnome-session[3898]: Frame 2: /lib/libc.so.6 [0x7f3cbc493ec0]
gnome-session[3898]: Frame 3: /lib/libc.so.6(gsignal+0x35) [0x7f3cbc493e45]
gnome-session[3898]: Frame 4: /lib/libc.so.6(abort+0x19a) [0x7f3cbc4952aa]
gnome-session[3898]: Frame 5: /usr/lib/libdbus-1.so.3 [0x7f3cbef6ab95]
gnome-session[3898]: Frame 6: /usr/lib/libdbus-1.so.3 [0x7f3cbef66a5d]
gnome-session[3898]: Frame 7: /usr/lib/libdbus-1.so.3(dbus_connection_send_with_reply_and_block+0x198) [0x7f3cbef50a88]
gnome-session[3898]: Frame 8: gnome-session [0x41203c]
gnome-session[3898]: Frame 9: gnome-session [0x412140]
gnome-session[3898]: Frame 10: gnome-session [0x41a5b0]
gnome-session[3898]: Frame 11: gnome-session [0x41aa8f]
gnome-session[3898]: Frame 12: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f3cbc48055d]
gnome-session[3898]: Frame 13: gnome-session [0x40aef9]
gnome-session[3898]: ******************* END **********************************
/var/log/gdm/:0.log.3
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux deuklin 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 14:09:36 CEST 2009 x86_64
Build Date: 15 April 2009 11:01:49AM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 12 08:55:10 2009
(==) Using config file: "/etc/X11/xorg.conf"
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri.so
(EE) Failed to load module "dri" (loader failed, 7)
(EE) Failed to load module "freetype" (module does not exist, 0)
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri2.so
(EE) Failed to load module "dri2" (loader failed, 7)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Just a point here is that I've had the exact same software installed the same day that I reinstalled and this error did not occur but after formatting my partition with ext4 and testing Arch64 it did. But it did with 32bit as well, there were tons of errors.
I've read about this ConsoleKit error in a few posts here but nothing seems to indicate a fix or anything and since I'm using Gnome now I didn't find anything on it just about KDE.
I can safely use "Failsafe Gnome" without startup scripts but I want it to work without any problems and I don't know if the "dri" thing is related to the ConsoleKit thing with GDM.
I installed it via FTP and had the latest updates as soon as I've installed, so if this is just something that is happening to me right now or alot of other people, please give us hints or anything that could solve this?
If you read my Arch64 thread you know that stuff stopped working for me, first the network (it turns out I had to boot Windows inbetween installing Arch for my network even to start and that sounds ridicilous if it depends on another operating system starting the device because in Windows the network card was turned on with a green light wherein Arch after installing it didn't. I reformated my partitions and changed it again, installed Windows again and tried it out and then installed Arch. It worked, and then I mixed around with KDE and after five minutes of using "startx" (the only thing working) I decided to reinstall with Gnome, but then the network didn't start again (tried booting about ten times) and then I just thought "Let's start windows first so it turns on" and when I just booted Windows and immiedatiely restarted it and booted with the Arch CD, network was available again. Strange? Or is this a period of instability for Arch?
But when I got my network to start, appearantly Keyboard and mouse wasn't working because Xorg forgot to install the drivers when I installed the full group of Xorg so I had to fix that and now it's giving me this error.

Without a dbus socket, dbus probably isn't running. It's supposed to be started automatically when a program needs it. Check to see that it is installed and running:
pacman -Q dbus
pgrep -l dbus
Dbus won't run without hal, so hal should be in:
tail /etc/rc.conf
Are any of your partitions full?
df -h
For the other error, it looks like libdrm isn't installed, but I don't think you need it if you're running the nvidia driver.
Your xorg.conf and Xorg.0.log would also be useful. Also check dmesg for errors.
And see if /etc/rc.d/dbus is marked executable.
Last edited by fphillips (2009-05-12 18:27:41)

Gnome shell won't start

After I updated my system on Friday (24th), Gnome shell won't start.
Whether I open it with `startx` or GDM, it crashes with the "Oh, no! Something has gone wrong" message. With GDM, it seems the whole of GDM crashes, as it happens before I see anything of the UI, and I don't have auto login enabled. For `startx`, I don't see any UI there either.
Here is my Xorg.0.log: http://sprunge.us/hhZj
Here is my .xinitrc: http://sprunge.us/VjSJ
Here is the stderr from startx: http://sprunge.us/UCHj
I tried cleaning all gnome extensions, to no avail. I tried creating a new user, and run gnome with startx from there, and that worked. I tried cleaning my ~, and launching gnome with startx, but that didn't work.
Any ideas on what might be wrong, or how to further debug this?
Last edited by totokaka (2015-04-26 18:32:04)

here is my gdm log
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7664 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7664 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process -7690 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7679 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7679 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process -7705 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7694 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7694 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Could not start command '/usr/lib/gdm/gdm-session-worker': Muitos arquivos abertos
Abr 27 15:02:38 al-khowarizmi gdm[490]: GLib: g_child_watch_add_full: assertion 'pid > 0' failed
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process -7720 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7709 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7709 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:46 al-khowarizmi systemd[1]: Stopping GNOME Display Manager...
Abr 27 15:02:46 al-khowarizmi gdm[490]: Failed to contact accountsservice: Erro ao chamar StartServiceByName para org.freedesktop.Accounts: A conexão está fechada
Abr 27 15:02:46 al-khowarizmi gdm[490]: Tried to look up non-existent conversation gdm-launch-environment
Abr 27 15:02:46 al-khowarizmi gdm[490]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Abr 27 15:02:46 al-khowarizmi gdm[490]: (gdm-display.c:1141):gdm_display_dispose: runtime check failed: (self->priv->status != GDM_DISPLAY_PREPARED)
Abr 27 15:02:46 al-khowarizmi systemd[1]: Stopped GNOME Display Manager.

[NOT SOLVED] Gnome will not start

I'm editing this original message by way of summing up so that anyone coming here with a similar problem will know what to expect if they read further:
I believe the reason Gnome would not start on the machine in question was that it made too many demands on the available hardware (see desm0te's comments below).
For this reason I decided to switch to LXDE as Desktop Environment which works well on the restricted hardware. I did not investigate the Gnome related problem any further.
The original message follows:
After a successful installation of the basic command-line Arch according to the Beginner's Guide, I went on to install Gnome according to instructions in the Wiki.
I Did not want Gnome to start automatically but only when I type in the command startx.
This it does, but all I get is the nice blue "curtain" background - no black bar at top of screen with Actions, date , name etc...
and no cursor.
One funny thing was - this afternoon while I was concentrating on another machine - the black bar suddenly appeared (apparently for no reason) showing the date and my name but with the X cursor
from the X11 environment. However as soon as I moved this cursor to the bar and clicked, both dursor and bar disappeared never to return .
I decided to redirect the stderr of startx to a file in the hope that it would give a clue as to what was wrong.
X.Org X Server 1.11.4
Release Date: 2012-01-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.2-1-ARCH i686
Current Operating System: Linux pdv 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:28:27 UTC 2012 i686
Kernel command line: root=/dev/sda1 ro vga=773
Build Date: 29 January 2012 03:41:53PM
Current version of pixman: 0.24.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 3 21:13:19 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
[10f] 320 x 200, 70Hz
[134] 320 x 240, 72Hz
[144] 400 x 300, 72Hz
[154] 512 x 384, 70Hz
[11e] 640 x 400, 70Hz
[112] 640 x 480, 60Hz, 75Hz, 85Hz, 100Hz, 160Hz
[115] 800 x 600, 60Hz, 75Hz, 85Hz
[118] 1024 x 768, 60Hz, 70Hz, 75Hz, 85Hz, 100Hz, 130Hz
[17b] 1280 x 768, 60Hz
[16a] 1280 x 960, 60Hz, 85Hz
[11b] 1280 x 1024, 60Hz, 75Hz, 85Hz, 100Hz
[13e] 1400 x 1050, 60Hz, 75Hz
[124] 1600 x 1200, 60Hz
(gnome-shell:770): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to find suitable fbconfig for the GLX context: Failed to find any compatible fbconfigs
Window manager error: Unable to initialize Clutter.
Failed to play sound: File or data not found
Tracker-Message: Setting up monitor for changes to config file:'/home/dick/.config/tracker/tracker-miner-fs.cf** Message: applet now removed from the notification area
(nm-applet:789): libnotify-WARNING **: Failed to connect to proxy
** (nm-applet:789): WARNING **: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1.
** (nm-applet:789): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.
** (nm-applet:789): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown return code 1
Tracker-Message: Setting up monitor for changes to config file:'/home/dick/.config/tracker/tracker-store.cfg'
(tracker-store:791): Tracker-CRITICAL **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
(tracker-miner-fs:788): Tracker-CRITICAL **: Empty locale file found at '/home/dick/.cache/tracker/miner-applications-locale.txt'
(gnome-settings-daemon:668): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
(tracker-miner-fs:788): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/share/applications/brasero-nautilus.desktop': 'Desktop file doesn't contain type'
(tracker-miner-fs:788): Tracker-CRITICAL **: Empty locale file found at '/home/dick/.cache/tracker/miner-applications-locale.txt'
xinit: connection to X server lost
waiting for X server to shut down gnome-session[655]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Server terminated successfully (0). Closing log file.
(tracker-miner-fs:788): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
(tracker-miner-fs:788): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
(tracker-miner-fs:788): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
(tracker-miner-fs:788): GVFS-RemoteVolumeMonitor-WARNING **: cannot remove match rule 'type='signal',interface='org.gtk.Private.RemoteVolumeMonitor',sender='org.gtk.Private.GduVolumeMonitor',': org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(tracker-miner-fs:788): GVFS-RemoteVolumeMonitor-WARNING **: cannot remove match rule 'type='signal',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.gtk.Private.GduVolumeMonitor'': org.freedesktop.DBus.Error.Disconnected: Connection is closed
xinit: unexpected signal 2
If this gives clues could someone please point me in the right direction? Are the two EE messages significant (Failed to load modules "vesa" and "fbdev"). What is Clutter*? What should I do to get it initialized?
Thanks for any help.
Dick Summerfield (aka Battus).
* Sorry about that - it's an open source graphics library for creating hardware-accelerated user interfaces - but am I any the wiser for that
Last edited by Battus (2012-02-21 19:48:23)

desm0tes:
To take your points one by one:
1. I am now quite happy with LXDE too. The problems I mentioned last night seem to have gone (???!!!) and I can just start LXDE from my user account. Maybe later, I'll realize what I was doing wrong or rather what I did to make it work... . Now I just type:
startx
having put:
exec ck-launch-session startlxde
in .xinitrc.
2. Thanks for the tip about yaourt. I shall try that sooner or later.
3. Well as I said - I don't understand what I was doing wrong - which makes me feel a bit stupid and is rather annoying but looking on the bright side it's fine to be able to start-up, have a legible screen and logout successfully - which I couln't do before. I now have to figure out how to expand the contents of LXDE a bit but that's the fun of it!
LXDE starts up nicely with minimal possibilties but I can change look & feel and customize the panel settings.
"Menu" contains:
Accessories:
File Manager
Image Viewer
LXTerminal
Leafpad
Xarchiver
Internet:
Avahi SSH Server Browser
Avahi VNC Server Browser
Office:
ePDFViewer
System Tools:
Avahi Zerconf Browser
Task Manager
Preferences:
Customize Look and Feel
Monitor Settings
OPenbox Configuration Maanger
Preferred Applications
Run
Logout
All of these start up OK and work, on cursory examination, except the Avahi Browsers which I don't understand and which appear to do nothing as no window appears on screen.
4. I'm not quite sure I can yet see the use of a login manager such as SLiM, since I seem to get on quite nicely without it but since I've heard it mentioned a lot I'm sure I'm just missing the point.
Dick Summerfield (aka Battus)
Last edited by Battus (2012-02-06 19:56:30)

Xchat-gnome doesn't start

Hi,
I've just made a clean install and for some reason xchat-gnome doesn't start. The window doesn't even show only the notification that the program has crashed. I've tried to compile the package localy but that didn't help.
I realize this isn't much info to work with but what info would be useful and how do I gather it?
I would be really glad if someone could help me figure this one out.

DeepThoughts wrote:
Could it have something to with what repos we are using?
I'm using current, extra, community, testing and unstable.
nuopus, NeoEx and baze, what repos are you using?
i use those 5 aswell. the only thing from unstable is gimp-devel. from testing i use
alsa-lib
alsa-utils
ipw3945
kernel26
klibc-udev
openssl
udev
and then i use self-built avahi, libburn, nss-mdns and squeeze-svn. not really any packages which i think could cause this stuff to work here.
i use the hosteurope mirrors, maybe some packages are broken on your server, though i don't expect that.

Gnome 3.14 oh no! (gdm & gnome won't start)

Similar Messages

Maybe you are looking for