[gentoo-user] gnome not working

[gentoo-user] gnome not working

[covici]

When I start gdm, I get a message on the screen which says oh no,
something has gone wrong.  The log file is at
http://pastebin.com/qwNE7ee6   -- I would appreciate any help.

I am running gentoo testing with the 3.8 unmasked.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

[gentoo-user] Re: gnome not working

[walt]

On 05/13/2013 04:06 AM, covici@ccs.covici.com wrote:
> When I start gdm, I get a message on the screen which says oh no,
> something has gone wrong. 

If I had a bitcoin for every time I've seen that message I could buy
all of us a beer.  Maybe two :)

> The log file is at
> http://pastebin.com/qwNE7ee6   -- I would appreciate any help.

There are no obvious problems in your Xorg log, so the real error
is not logged there.  I don't use gdm so I'm not sure where those
errors are logged.  Anyone?

The main reason I don't like using one of the *dm display managers
is exactly to avoid this sort of PITA where you can't even see the
real error messages.  That's why I use startx instead.

Anyway, the trick *I* would try is to add the gentoo=nox kernel
option to the grub boot prompt (assuming you use grub) to prevent
gentoo from even trying to start an X session, thus avoiding gdm
and allowing you to use startx so you can read the gnome error
messages on the console while X starts up.

If you can ssh into that machine you could also try removing xdm
from your /etc/runlevels/default directory, assuming it's there.
I'm not at all sure how the *dms are usually started during boot,
so someone else could give you a better answer.

[gentoo-user] Re: gnome not working

[Hartmut Figge]

walt:

>Anyway, the trick *I* would try is to add the gentoo=nox kernel
>option to the grub boot prompt (assuming you use grub) to prevent
>gentoo from even trying to start an X session, thus avoiding gdm
>and allowing you to use startx so you can read the gnome error
>messages on the console while X starts up.

I am also using startx and have no experience with *dm. For a test, how
about renaming gdm to gdm-old and creating a script with the name gdm
instead?

----- gdm -----
#!bin/bash
gdm-old 2>&1 | tee ~/gdm.log
---------------

Hartmut

Re: [gentoo-user] Re: gnome not working

[covici]

walt <w41ter@gmail.com> wrote:

> On 05/13/2013 04:06 AM, covici@ccs.covici.com wrote:
> > When I start gdm, I get a message on the screen which says oh no,
> > something has gone wrong. 
> 
> If I had a bitcoin for every time I've seen that message I could buy
> all of us a beer.  Maybe two :)
> 
> > The log file is at
> > http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
> 
> There are no obvious problems in your Xorg log, so the real error
> is not logged there.  I don't use gdm so I'm not sure where those
> errors are logged.  Anyone?
> 
> The main reason I don't like using one of the *dm display managers
> is exactly to avoid this sort of PITA where you can't even see the
> real error messages.  That's why I use startx instead.
> 
> Anyway, the trick *I* would try is to add the gentoo=nox kernel
> option to the grub boot prompt (assuming you use grub) to prevent
> gentoo from even trying to start an X session, thus avoiding gdm
> and allowing you to use startx so you can read the gnome error
> messages on the console while X starts up.
> 
> If you can ssh into that machine you could also try removing xdm
> from your /etc/runlevels/default directory, assuming it's there.
> I'm not at all sure how the *dms are usually started during boot,
> so someone else could give you a better answer.
> 

Well, I don't boot right into gdm or any display manager, I started gdm
by hand.  I did try startx, but got the same result, but I can get the
.xsessionerrors, so maybe someone can figure that out. 
Its at http://pastebin.com/JJrdxWHB .


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] Re: gnome not working

[Canek Peláez Valdés]

On Mon, May 13, 2013 at 8:40 PM, <covici@ccs.covici.com> wrote:
[ snip ]
> Well, I don't boot right into gdm or any display manager, I started gdm
> by hand.

And by that you mean "/etc/init.d/gdm start"?

>  I did try startx, but got the same result, but I can get the
> .xsessionerrors, so maybe someone can figure that out.
> Its at http://pastebin.com/JJrdxWHB .

Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] gnome not working

[J. Roeleveld]

On Mon, May 13, 2013 13:06, covici@ccs.covici.com wrote:
> When I start gdm, I get a message on the screen which says oh no,
> something has gone wrong.  The log file is at
> http://pastebin.com/qwNE7ee6   -- I would appreciate any help.

Please attach logfiles to the list.
Using sites like pastebin makes archives useless.

--
Joost

Re: [gentoo-user] gnome not working

[covici]

[-- Attachment #1: Type: text/plain, Size: 524 bytes --]

J. Roeleveld <joost@antarean.org> wrote:

> On Mon, May 13, 2013 13:06, covici@ccs.covici.com wrote:
> > When I start gdm, I get a message on the screen which says oh no,
> > something has gone wrong.  The log file is at
> > http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
> 
> Please attach logfiles to the list.
> Using sites like pastebin makes archives useless.

OK, I didn't know that.  I also had the same problem when using startx,
so I will attach my .xsession-errors along with the Xorg.0.log file.


[-- Attachment #2: xorg.0.log --]
[-- Type: text/plain, Size: 21935 bytes --]

[ 79107.259] 
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 79107.260] X Protocol Version 11, Revision 0
[ 79107.260] Build Operating System: Linux 3.6.2-gentoo x86_64 Gentoo
[ 79107.261] Current Operating System: Linux ccs.covici.com 3.6.2-gentoo #4 SMP PREEMPT Sat Mar 2 02:33:27 EST 2013 x86_64
[ 79107.261] Kernel command line: BOOT_IMAGE=3.6.2-gentoo ro root=100 init=/linuxrc ramdisk=8192 real_root=/dev/mapper/linux--files-64--root udev video=uvesafb:1280x1024 speakup.synth=spkout vmalloc=256M dolvm rootfstype=ext4
[ 79107.262] Build Date: 11 May 2013  07:28:12PM
[ 79107.262]  
[ 79107.263] Current version of pixman: 0.30.0
[ 79107.264] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 79107.264] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 79107.266] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 13 06:28:19 2013
[ 79107.266] (==) Using config file: "/etc/X11/xorg.conf"
[ 79107.267] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 79107.267] (==) ServerLayout "Default Layout"
[ 79107.267] (**) |-->Screen "Default Screen" (0)
[ 79107.267] (**) |   |-->Monitor "Generic Monitor"
[ 79107.267] (**) |   |-->Device "NVIDIA Corporation NV34 [GeForce FX 5500]"
[ 79107.267] (**) |-->Input Device "Generic Keyboard"
[ 79107.267] (**) |-->Input Device "Configured Mouse"
[ 79107.267] (==) Automatically adding devices
[ 79107.267] (==) Automatically enabling devices
[ 79107.267] (==) Automatically adding GPU devices
[ 79107.267] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/misc" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/100dpi/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/75dpi/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/Type1" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/X11/CID" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/CID" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/100dpi" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/lib/X11/fonts/75dpi" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/misc/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/100dpi/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (WW) The directory "/usr/share/fonts/75dpi/" does not exist.
[ 79107.267] 	Entry deleted from font path.
[ 79107.267] (**) FontPath set to:
	unix/:7100
[ 79107.267] (**) ModulePath set to "/usr/lib64/xorg/modules,/usr/lib64/xorg/modules/extensions,/usr/lib64/xorg/opengl/xorg-x11,/usr/lib64/xorg/opengl/xorg-x11/extensions"
[ 79107.267] (**) Extension "Composite" is disabled
[ 79107.267] (**) Extension "RENDER" is enabled
[ 79107.267] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 79107.267] (WW) Disabling Generic Keyboard
[ 79107.267] (WW) Disabling Configured Mouse
[ 79107.267] (II) Loader magic: 0x7fdc00
[ 79107.267] (II) Module ABI versions:
[ 79107.267] 	X.Org ANSI C Emulation: 0.4
[ 79107.267] 	X.Org Video Driver: 14.1
[ 79107.267] 	X.Org XInput driver : 19.1
[ 79107.267] 	X.Org Server Extension : 7.0
[ 79107.269] (--) PCI:*(0:1:0:0) 10de:0de1:3842:1335 rev 161, Mem @ 0xfa000000/16777216, 0xd0000000/134217728, 0xd8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 79107.269] Initializing built-in extension Generic Event Extension
[ 79107.270] Initializing built-in extension SHAPE
[ 79107.270] Initializing built-in extension MIT-SHM
[ 79107.271] Initializing built-in extension XInputExtension
[ 79107.271] Initializing built-in extension XTEST
[ 79107.272] Initializing built-in extension BIG-REQUESTS
[ 79107.272] Initializing built-in extension SYNC
[ 79107.273] Initializing built-in extension XKEYBOARD
[ 79107.273] Initializing built-in extension XC-MISC
[ 79107.274] Initializing built-in extension XINERAMA
[ 79107.274] Initializing built-in extension XFIXES
[ 79107.275] Initializing built-in extension RENDER
[ 79107.275] Initializing built-in extension RANDR
[ 79107.276] Initializing built-in extension COMPOSITE
[ 79107.276] Initializing built-in extension DAMAGE
[ 79107.277] Initializing built-in extension MIT-SCREEN-SAVER
[ 79107.277] Initializing built-in extension DOUBLE-BUFFER
[ 79107.277] Initializing built-in extension RECORD
[ 79107.278] Initializing built-in extension DPMS
[ 79107.278] Initializing built-in extension X-Resource
[ 79107.279] Initializing built-in extension XVideo
[ 79107.279] Initializing built-in extension XVideo-MotionCompensation
[ 79107.279] Initializing built-in extension XFree86-VidModeExtension
[ 79107.280] Initializing built-in extension XFree86-DGA
[ 79107.280] Initializing built-in extension XFree86-DRI
[ 79107.281] Initializing built-in extension DRI2
[ 79107.281] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 79107.281] (II) LoadModule: "i2c"
[ 79107.281] (II) Module "i2c" already built-in
[ 79107.281] (II) LoadModule: "ddc"
[ 79107.281] (II) Module "ddc" already built-in
[ 79107.281] (II) LoadModule: "extmod"
[ 79107.281] (II) Module "extmod" already built-in
[ 79107.281] (II) LoadModule: "glx"
[ 79107.281] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 79107.287] (II) Module glx: vendor="NVIDIA Corporation"
[ 79107.287] 	compiled for 4.0.2, module version = 1.0.0
[ 79107.287] 	Module class: X.Org Server Extension
[ 79107.287] (II) NVIDIA GLX Module  319.17  Thu Apr 25 21:41:50 PDT 2013
[ 79107.288] Loading extension GLX
[ 79107.288] (II) LoadModule: "int10"
[ 79107.288] (II) Loading /usr/lib64/xorg/modules/libint10.so
[ 79107.288] (II) Module int10: vendor="X.Org Foundation"
[ 79107.288] 	compiled for 1.14.1, module version = 1.0.0
[ 79107.288] 	ABI class: X.Org Video Driver, version 14.1
[ 79107.288] (II) LoadModule: "vbe"
[ 79107.288] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[ 79107.288] (II) Module vbe: vendor="X.Org Foundation"
[ 79107.288] 	compiled for 1.14.1, module version = 1.1.0
[ 79107.288] 	ABI class: X.Org Video Driver, version 14.1
[ 79107.288] (II) LoadModule: "nvidia"
[ 79107.288] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[ 79107.288] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 79107.288] 	compiled for 4.0.2, module version = 1.0.0
[ 79107.288] 	Module class: X.Org Video Driver
[ 79107.288] (II) NVIDIA dlloader X Driver  319.17  Thu Apr 25 21:23:57 PDT 2013
[ 79107.288] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 79107.288] (--) using VT number 12

[ 79107.290] (II) Loading sub module "fb"
[ 79107.290] (II) LoadModule: "fb"
[ 79107.290] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 79107.290] (II) Module fb: vendor="X.Org Foundation"
[ 79107.290] 	compiled for 1.14.1, module version = 1.0.0
[ 79107.290] 	ABI class: X.Org ANSI C Emulation, version 0.4
[ 79107.290] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 79107.290] (II) Loading sub module "wfb"
[ 79107.290] (II) LoadModule: "wfb"
[ 79107.290] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[ 79107.290] (II) Module wfb: vendor="X.Org Foundation"
[ 79107.290] 	compiled for 1.14.1, module version = 1.0.0
[ 79107.290] 	ABI class: X.Org ANSI C Emulation, version 0.4
[ 79107.290] (II) Loading sub module "shadow"
[ 79107.290] (II) LoadModule: "shadow"
[ 79107.290] (II) Loading /usr/lib64/xorg/modules/libshadow.so
[ 79107.290] (II) Module shadow: vendor="X.Org Foundation"
[ 79107.290] 	compiled for 1.14.1, module version = 1.1.0
[ 79107.290] 	ABI class: X.Org ANSI C Emulation, version 0.4
[ 79107.290] (II) Loading sub module "ramdac"
[ 79107.290] (II) LoadModule: "ramdac"
[ 79107.290] (II) Module "ramdac" already built-in
[ 79107.290] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 79107.290] (==) NVIDIA(0): RGB weight 888
[ 79107.290] (==) NVIDIA(0): Default visual is TrueColor
[ 79107.290] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 79107.290] (**) NVIDIA(0): Enabling 2D acceleration
[ 79107.654] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-1)) does not support NVIDIA
[ 79107.654] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 79107.656] (II) NVIDIA(0): NVIDIA GPU GeForce GT 430 (GF108) at PCI:1:0:0 (GPU-0)
[ 79107.656] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 79107.656] (--) NVIDIA(0): VideoBIOS: 70.08.29.00.38
[ 79107.656] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 79107.660] (--) NVIDIA(0): Valid display device(s) on GeForce GT 430 at PCI:1:0:0
[ 79107.660] (--) NVIDIA(0):     CRT-0
[ 79107.660] (--) NVIDIA(0):     Samsung SyncMaster (CRT-1) (boot, connected)
[ 79107.660] (--) NVIDIA(0):     DFP-0
[ 79107.660] (--) NVIDIA(0):     DFP-1
[ 79107.660] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 79107.660] (--) NVIDIA(0): Samsung SyncMaster (CRT-1): 320.0 MHz maximum pixel clock
[ 79107.660] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
[ 79107.660] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
[ 79107.660] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 79107.660] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 79107.660] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79107.660] (**) NVIDIA(0):     device Samsung SyncMaster (CRT-1) (Using EDID frequencies
[ 79107.660] (**) NVIDIA(0):     has been enabled on all display devices.)
[ 79107.661] (II) NVIDIA(0): Validated MetaModes:
[ 79107.661] (II) NVIDIA(0):     "CRT-1:1280x1024{}"
[ 79107.661] (II) NVIDIA(0):     "CRT-1:1024x768{}"
[ 79107.661] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
[ 79107.697] (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
[ 79107.697] (--) NVIDIA(0):     option
[ 79107.697] (--) Depth 24 pixmap format is 32 bpp
[ 79107.697] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 79107.697] (II) NVIDIA:     access.
[ 79107.699] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 79107.699] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 79107.699] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 79107.699] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 79107.699] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 79107.699] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 79107.699] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 79107.699] (II) NVIDIA(0):     Config Options in the README.
[ 79107.702] (II) NVIDIA(0): Setting mode "CRT-1:1280x1024{}"
[ 79107.733] Loading extension NV-GLX
[ 79107.786] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 79107.786] (==) NVIDIA(0): Backing store disabled
[ 79107.786] (==) NVIDIA(0): Silken mouse enabled
[ 79107.786] (**) NVIDIA(0): DPMS enabled
[ 79107.786] Loading extension NV-CONTROL
[ 79107.786] Loading extension XINERAMA
[ 79107.786] (II) Loading sub module "dri2"
[ 79107.786] (II) LoadModule: "dri2"
[ 79107.786] (II) Module "dri2" already built-in
[ 79107.786] (II) NVIDIA(0): [DRI2] Setup complete
[ 79107.786] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[ 79107.786] (--) RandR disabled
[ 79107.789] (II) Initializing extension GLX
[ 79107.790] [dix] Could not init font path element unix/:7100, removing from list!
[ 79107.808] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 79107.808] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 79107.808] (II) LoadModule: "evdev"
[ 79107.808] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[ 79107.808] (II) Module evdev: vendor="X.Org Foundation"
[ 79107.808] 	compiled for 1.14.1, module version = 2.8.0
[ 79107.808] 	Module class: X.Org XInput Driver
[ 79107.808] 	ABI class: X.Org XInput driver, version 19.1
[ 79107.808] (II) Using input driver 'evdev' for 'Power Button'
[ 79107.808] (**) Power Button: always reports core events
[ 79107.808] (**) evdev: Power Button: Device: "/dev/input/event5"
[ 79107.808] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 79107.808] (--) evdev: Power Button: Found keys
[ 79107.808] (II) evdev: Power Button: Configuring as keyboard
[ 79107.808] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event5"
[ 79107.808] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 79107.808] (**) Option "xkb_rules" "evdev"
[ 79107.808] (**) Option "xkb_model" "evdev"
[ 79107.808] (**) Option "xkb_layout" "us"
[ 79107.821] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 79107.821] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 79107.821] (II) Using input driver 'evdev' for 'Power Button'
[ 79107.821] (**) Power Button: always reports core events
[ 79107.821] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 79107.821] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 79107.821] (--) evdev: Power Button: Found keys
[ 79107.821] (II) evdev: Power Button: Configuring as keyboard
[ 79107.821] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4/event4"
[ 79107.821] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 79107.821] (**) Option "xkb_rules" "evdev"
[ 79107.821] (**) Option "xkb_model" "evdev"
[ 79107.821] (**) Option "xkb_layout" "us"
[ 79107.821] (II) config/udev: Adding input device HID 0c16:0001 (/dev/input/event2)
[ 79107.821] (**) HID 0c16:0001: Applying InputClass "evdev keyboard catchall"
[ 79107.821] (II) Using input driver 'evdev' for 'HID 0c16:0001'
[ 79107.821] (**) HID 0c16:0001: always reports core events
[ 79107.821] (**) evdev: HID 0c16:0001: Device: "/dev/input/event2"
[ 79107.821] (--) evdev: HID 0c16:0001: Vendor 0xc16 Product 0x1
[ 79107.821] (--) evdev: HID 0c16:0001: Found keys
[ 79107.821] (II) evdev: HID 0c16:0001: Configuring as keyboard
[ 79107.821] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input2/event2"
[ 79107.821] (II) XINPUT: Adding extended input device "HID 0c16:0001" (type: KEYBOARD, id 8)
[ 79107.821] (**) Option "xkb_rules" "evdev"
[ 79107.821] (**) Option "xkb_model" "evdev"
[ 79107.821] (**) Option "xkb_layout" "us"
[ 79107.822] (II) config/udev: Adding input device HID 0c16:0001 (/dev/input/event3)
[ 79107.822] (**) HID 0c16:0001: Applying InputClass "evdev pointer catchall"
[ 79107.822] (**) HID 0c16:0001: Applying InputClass "evdev keyboard catchall"
[ 79107.822] (II) Using input driver 'evdev' for 'HID 0c16:0001'
[ 79107.822] (**) HID 0c16:0001: always reports core events
[ 79107.822] (**) evdev: HID 0c16:0001: Device: "/dev/input/event3"
[ 79107.822] (--) evdev: HID 0c16:0001: Vendor 0xc16 Product 0x1
[ 79107.822] (--) evdev: HID 0c16:0001: Found 13 mouse buttons
[ 79107.822] (--) evdev: HID 0c16:0001: Found scroll wheel(s)
[ 79107.822] (--) evdev: HID 0c16:0001: Found relative axes
[ 79107.822] (--) evdev: HID 0c16:0001: Found x and y relative axes
[ 79107.822] (--) evdev: HID 0c16:0001: Found absolute axes
[ 79107.822] (II) evdev: HID 0c16:0001: Forcing absolute x/y axes to exist.
[ 79107.822] (--) evdev: HID 0c16:0001: Found keys
[ 79107.822] (II) evdev: HID 0c16:0001: Configuring as mouse
[ 79107.822] (II) evdev: HID 0c16:0001: Configuring as keyboard
[ 79107.822] (II) evdev: HID 0c16:0001: Adding scrollwheel support
[ 79107.822] (**) evdev: HID 0c16:0001: YAxisMapping: buttons 4 and 5
[ 79107.822] (**) evdev: HID 0c16:0001: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 79107.822] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.1/input/input3/event3"
[ 79107.822] (II) XINPUT: Adding extended input device "HID 0c16:0001" (type: KEYBOARD, id 9)
[ 79107.822] (**) Option "xkb_rules" "evdev"
[ 79107.822] (**) Option "xkb_model" "evdev"
[ 79107.822] (**) Option "xkb_layout" "us"
[ 79107.822] (II) evdev: HID 0c16:0001: initialized for relative axes.
[ 79107.822] (WW) evdev: HID 0c16:0001: ignoring absolute axes.
[ 79107.822] (**) HID 0c16:0001: (accel) keeping acceleration scheme 1
[ 79107.822] (**) HID 0c16:0001: (accel) acceleration profile 0
[ 79107.822] (**) HID 0c16:0001: (accel) acceleration factor: 2.000
[ 79107.822] (**) HID 0c16:0001: (accel) acceleration threshold: 4
[ 79107.822] (II) config/udev: Adding input device HID 0c16:0001 (/dev/input/mouse0)
[ 79107.822] (II) No input driver specified, ignoring this device.
[ 79107.822] (II) This device may have been added with another device file.
[ 79107.822] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event1)
[ 79107.822] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 79107.822] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 79107.822] (**) AT Translated Set 2 keyboard: always reports core events
[ 79107.822] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event1"
[ 79107.822] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 79107.822] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 79107.822] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 79107.822] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input1/event1"
[ 79107.822] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[ 79107.822] (**) Option "xkb_rules" "evdev"
[ 79107.822] (**) Option "xkb_model" "evdev"
[ 79107.822] (**) Option "xkb_layout" "us"
[ 79107.823] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[ 79107.823] (II) No input driver specified, ignoring this device.
[ 79107.823] (II) This device may have been added with another device file.
[ 79107.823] (II) config/udev: Adding input device Speakup (/dev/input/event0)
[ 79107.823] (**) Speakup: Applying InputClass "evdev keyboard catchall"
[ 79107.823] (II) Using input driver 'evdev' for 'Speakup'
[ 79107.823] (**) Speakup: always reports core events
[ 79107.823] (**) evdev: Speakup: Device: "/dev/input/event0"
[ 79107.823] (--) evdev: Speakup: Vendor 0 Product 0
[ 79107.823] (--) evdev: Speakup: Found keys
[ 79107.823] (II) evdev: Speakup: Configuring as keyboard
[ 79107.823] (**) Option "config_info" "udev:/sys/devices/virtual/input/input0/event0"
[ 79107.823] (II) XINPUT: Adding extended input device "Speakup" (type: KEYBOARD, id 11)
[ 79107.823] (**) Option "xkb_rules" "evdev"
[ 79107.823] (**) Option "xkb_model" "evdev"
[ 79107.823] (**) Option "xkb_layout" "us"
[ 79136.802] (II) NVIDIA(0): Setting mode "CRT-1:1280x1024{}"
[ 79136.898] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 79136.898] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 79136.898] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 79136.898] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 79136.898] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 79136.898] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 79136.898] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 79136.898] (II) NVIDIA(0):     Config Options in the README.
[ 79136.930] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-1)) does not support NVIDIA
[ 79136.930] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 79136.930] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 79136.930] (**) NVIDIA(0):     device Samsung SyncMaster (CRT-1) (Using EDID frequencies
[ 79136.930] (**) NVIDIA(0):     has been enabled on all display devices.)
[ 79223.689] (II) evdev: Speakup: Close
[ 79223.689] (II) UnloadModule: "evdev"
[ 79223.689] (II) evdev: AT Translated Set 2 keyboard: Close
[ 79223.689] (II) UnloadModule: "evdev"
[ 79223.690] (II) evdev: HID 0c16:0001: Close
[ 79223.690] (II) UnloadModule: "evdev"
[ 79223.690] (II) evdev: HID 0c16:0001: Close
[ 79223.690] (II) UnloadModule: "evdev"
[ 79223.690] (II) evdev: Power Button: Close
[ 79223.690] (II) UnloadModule: "evdev"
[ 79223.690] (II) evdev: Power Button: Close
[ 79223.690] (II) UnloadModule: "evdev"
[ 79223.862] Server terminated successfully (0). Closing log file.

[-- Attachment #3: .xsession-errors --]
[-- Type: text/plain, Size: 7265 bytes --]

/etc/gdm/Xsession: Beginning session setup...
which: no keychain in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/local/freeswitch/bin)
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/dbus-launch --exit-with-session /usr/bin/ssh-agent -- gnome-session
** Message: couldn't access conrol socket: /tmp/keyring-tfVQ9R/control: Permission denied
** Message: couldn't access conrol socket: /tmp/keyring-tfVQ9R/control: Permission denied
** Message: couldn't access conrol socket: /tmp/keyring-tfVQ9R/control: Permission denied
** Message: couldn't access conrol socket: /tmp/keyring-tfVQ9R/control: Permission denied
GNOME_KEYRING_CONTROL=/tmp/keyring-0PUqc5
GPG_AGENT_INFO=/tmp/keyring-0PUqc5/gpg:0:1
GNOME_KEYRING_PID=25718
GNOME_KEYRING_CONTROL=/tmp/keyring-0PUqc5
GPG_AGENT_INFO=/tmp/keyring-0PUqc5/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-0PUqc5
GPG_AGENT_INFO=/tmp/keyring-0PUqc5/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-0PUqc5/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-0PUqc5
GPG_AGENT_INFO=/tmp/keyring-0PUqc5/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-0PUqc5/ssh

(gnome-settings-daemon:25714): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'
gnome-session[25679]: GLib-GObject-WARNING: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (gnome-settings-daemon:25714): WARNING **: Invalid signal type text-insert


(gnome-settings-daemon:25714): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (gnome-settings-daemon:25714): WARNING **: Invalid signal type text-remove

gnome-session[25679]: WARNING: Invalid signal type text-insert

gnome-session[25679]: GLib-GObject-WARNING: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'
gnome-session[25679]: WARNING: Invalid signal type text-remove


(metacity:25729): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (metacity:25729): WARNING **: Invalid signal type text-insert


(metacity:25729): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (metacity:25729): WARNING **: Invalid signal type text-remove

Window manager warning: Failed to load theme "Clearlooks": Failed to find a valid file for theme Clearlooks


(gnome-panel:25751): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (gnome-panel:25751): WARNING **: Invalid signal type text-insert


(gnome-panel:25751): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (gnome-panel:25751): WARNING **: Invalid signal type text-remove


(nautilus:25758): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (nautilus:25758): WARNING **: Invalid signal type text-insert


(nautilus:25758): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (nautilus:25758): WARNING **: Invalid signal type text-remove


(canberra-gtk-play:25763): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (canberra-gtk-play:25763): WARNING **: Invalid signal type text-insert


(canberra-gtk-play:25763): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (canberra-gtk-play:25763): WARNING **: Invalid signal type text-remove

Failed to play sound: Sound disabled

(polkit-gnome-authentication-agent-1:25775): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (polkit-gnome-authentication-agent-1:25775): WARNING **: Invalid signal type text-insert


(polkit-gnome-authentication-agent-1:25775): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (polkit-gnome-authentication-agent-1:25775): WARNING **: Invalid signal type text-remove


(xdg-user-dirs-gtk-update:25769): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (xdg-user-dirs-gtk-update:25769): WARNING **: Invalid signal type text-insert


(xdg-user-dirs-gtk-update:25769): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (xdg-user-dirs-gtk-update:25769): WARNING **: Invalid signal type text-remove


(gdu-notification-daemon:25765): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'

** (gdu-notification-daemon:25765): WARNING **: Invalid signal type text-insert


(gdu-notification-daemon:25765): GLib-GObject-WARNING **: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'

** (gdu-notification-daemon:25765): WARNING **: Invalid signal type text-remove

Unable to open desktop file epiphany.desktop for panel launcher
Unable to open desktop file evolution.desktop for panel launcher
/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:54: Warning: gsignal.c:1149: unable to lookup signal "text-insert" for non instantiatable type `AtkText'
  _gtk.init_check()

** (orca:25815): WARNING **: Invalid signal type text-insert

/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:54: Warning: gsignal.c:1149: unable to lookup signal "text-remove" for non instantiatable type `AtkText'
  _gtk.init_check()

** (orca:25815): WARNING **: Invalid signal type text-remove

Initializing nautilus-gdu extension

(nautilus:25758): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
/usr/lib64/python2.7/site-packages/gi/types.py:44: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  return info.invoke(*args)
Another Orca process is already running for this session.
Run "orca --replace" if you want to replace the current
process with a new one.
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0'.
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-session[25679]: GLib-WARNING: Failed to read from child watch wake up pipe: Interrupted system call

(polkit-gnome-authentication-agent-1:25775): Gdk-WARNING **: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(gdu-notification-daemon:25765): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

[-- Attachment #4: Type: text/plain, Size: 150 bytes --]


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] gnome not working

[Michael Hampicke]

[-- Attachment #1: Type: text/plain, Size: 414 bytes --]

Am 13.05.2013 13:06, schrieb covici@ccs.covici.com:
> When I start gdm, I get a message on the screen which says oh no,
> something has gone wrong.  The log file is at
> http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
> 
> I am running gentoo testing with the 3.8 unmasked.
> 

Today I spotted some updated gnome (3.8) packages in the tree. Maybe the
updated versions will work for you.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] gnome not working

[covici]

Michael Hampicke <mh@hadt.biz> wrote:

> Am 13.05.2013 13:06, schrieb covici@ccs.covici.com:
> > When I start gdm, I get a message on the screen which says oh no,
> > something has gone wrong.  The log file is at
> > http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
> > 
> > I am running gentoo testing with the 3.8 unmasked.
> > 
> 
> Today I spotted some updated gnome (3.8) packages in the tree. Maybe the
> updated versions will work for you.

OK, thanks. Maybe I will just try that, but it would be better to know
what is the matter.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] gnome not working

[waltdnes]

On Mon, May 13, 2013 at 07:06:02AM -0400, covici@ccs.covici.com wrote
> When I start gdm, I get a message on the screen which says oh no,
> something has gone wrong.  The log file is at
> http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
> 
> I am running gentoo testing with the 3.8 unmasked.

  Direct from the "Making systemd more accessible to "normal" users"
flamewar on gentoo-dev...

> And now that GNOME 3.8 is out, the game starts over again: logind
> is a hard requirement, logind is part of systemd, starting logind
> (which replaces consolekit) is not that trivial as you may think
> (and is the thing I started to work on anyway).
> 
> And if this wasn't enough, it means that if you want GNOME 3.8,
> you need to get logind, which may or not may get included in our
> udev ebuild and if it won't, it means that you will be forced to use
> systemd as device manager if you want GNOME 3.8, which is believe
> it or not, the thing that Ubuntu did.

  Do you have systemd/logind installed?

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] gnome not working

[Michael Hampicke]

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

Am 15.05.2013 20:27, schrieb waltdnes@waltdnes.org:
> 
>   Direct from the "Making systemd more accessible to "normal" users"
> flamewar on gentoo-dev...
> 
>> And now that GNOME 3.8 is out, the game starts over again: logind
>> is a hard requirement, logind is part of systemd, starting logind
>> (which replaces consolekit) is not that trivial as you may think
>> (and is the thing I started to work on anyway).
>>
>> And if this wasn't enough, it means that if you want GNOME 3.8,
>> you need to get logind, which may or not may get included in our
>> udev ebuild and if it won't, it means that you will be forced to use
>> systemd as device manager if you want GNOME 3.8, which is believe
>> it or not, the thing that Ubuntu did.
> 
>   Do you have systemd/logind installed?
> 

I read that too on gentoo-dev. I have systemd installed, but currently I
do not use it as init. I have tried it with systemd as init, but it has
problems with mounting my lvm volumes (after failing it's stuck,
ctrl+alt+del has no effect, and magic sysrq seems to be deactived?). I
think a saw a bug report regarding systemd/lvm.

I may try it again in a few days. There have been some updates to
systemd lately.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] gnome not working

[Canek Peláez Valdés]

On Wed, May 15, 2013 at 4:44 PM, Michael Hampicke <mh@hadt.biz> wrote:
>
> Am 15.05.2013 20:27, schrieb waltdnes@waltdnes.org:
> >
> >   Direct from the "Making systemd more accessible to "normal" users"
> > flamewar on gentoo-dev...
> >
> >> And now that GNOME 3.8 is out, the game starts over again: logind
> >> is a hard requirement, logind is part of systemd, starting logind
> >> (which replaces consolekit) is not that trivial as you may think
> >> (and is the thing I started to work on anyway).
> >>
> >> And if this wasn't enough, it means that if you want GNOME 3.8,
> >> you need to get logind, which may or not may get included in our
> >> udev ebuild and if it won't, it means that you will be forced to use
> >> systemd as device manager if you want GNOME 3.8, which is believe
> >> it or not, the thing that Ubuntu did.
> >
> >   Do you have systemd/logind installed?
> >
>
> I read that too on gentoo-dev. I have systemd installed, but currently I
> do not use it as init. I have tried it with systemd as init, but it has
> problems with mounting my lvm volumes (after failing it's stuck,
> ctrl+alt+del has no effect, and magic sysrq seems to be deactived?). I
> think a saw a bug report regarding systemd/lvm.
>
> I may try it again in a few days. There have been some updates to
> systemd lately.

systemd 201 is targeted to be stabilized soon:

https://bugs.gentoo.org/show_bug.cgi?id=465870

The LVM issue is mentioned, but it's not yet on the block list.

Regards.


--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] gnome not working

[Stefan G. Weichinger]

Am 16.05.2013 00:28, schrieb Canek Peláez Valdés:

> systemd 201 is targeted to be stabilized soon:
> 
> https://bugs.gentoo.org/show_bug.cgi?id=465870
> 
> The LVM issue is mentioned, but it's not yet on the block list.

I didn't read all this thread ... but I still face issues with lvm2 &
systemd here.
Sometimes the VG is activated, sometimes not ...

Using overlay "systemd-love" here and I am already in contact with the
dev there.

(and right now, after booting w/ systemd-204, the LVs are there as they
should be)

Stefan

Re: [gentoo-user] gnome not working

[covici]

waltdnes@waltdnes.org wrote:

> On Mon, May 13, 2013 at 07:06:02AM -0400, covici@ccs.covici.com wrote
> > When I start gdm, I get a message on the screen which says oh no,
> > something has gone wrong.  The log file is at
> > http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
> > 
> > I am running gentoo testing with the 3.8 unmasked.
> 
>   Direct from the "Making systemd more accessible to "normal" users"
> flamewar on gentoo-dev...
> 
> > And now that GNOME 3.8 is out, the game starts over again: logind
> > is a hard requirement, logind is part of systemd, starting logind
> > (which replaces consolekit) is not that trivial as you may think
> > (and is the thing I started to work on anyway).
> > 
> > And if this wasn't enough, it means that if you want GNOME 3.8,
> > you need to get logind, which may or not may get included in our
> > udev ebuild and if it won't, it means that you will be forced to use
> > systemd as device manager if you want GNOME 3.8, which is believe
> > it or not, the thing that Ubuntu did.
> 
>   Do you have systemd/logind installed?

Nope, sure don't.   None of the ebuilds pulled it in.  But what about
startx?  Would I need logind to do that?

> 
> -- 
> Walter Dnes <waltdnes@waltdnes.org>
> I don't run "desktop environments"; I run useful applications

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] gnome not working

[Canek Peláez Valdés]

On Wed, May 15, 2013 at 8:10 PM,  <covici@ccs.covici.com> wrote:
> waltdnes@waltdnes.org wrote:
>
>> On Mon, May 13, 2013 at 07:06:02AM -0400, covici@ccs.covici.com wrote
>> > When I start gdm, I get a message on the screen which says oh no,
>> > something has gone wrong.  The log file is at
>> > http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
>> >
>> > I am running gentoo testing with the 3.8 unmasked.
>>
>>   Direct from the "Making systemd more accessible to "normal" users"
>> flamewar on gentoo-dev...
>>
>> > And now that GNOME 3.8 is out, the game starts over again: logind
>> > is a hard requirement, logind is part of systemd, starting logind
>> > (which replaces consolekit) is not that trivial as you may think
>> > (and is the thing I started to work on anyway).
>> >
>> > And if this wasn't enough, it means that if you want GNOME 3.8,
>> > you need to get logind, which may or not may get included in our
>> > udev ebuild and if it won't, it means that you will be forced to use
>> > systemd as device manager if you want GNOME 3.8, which is believe
>> > it or not, the thing that Ubuntu did.
>>
>>   Do you have systemd/logind installed?
>
> Nope, sure don't.   None of the ebuilds pulled it in.  But what about
> startx?  Would I need logind to do that?

When you use startx, what does your .xinitrc have? Try with only

exec gnome-session

Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] gnome not working

[covici]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, May 15, 2013 at 8:10 PM,  <covici@ccs.covici.com> wrote:
> > waltdnes@waltdnes.org wrote:
> >
> >> On Mon, May 13, 2013 at 07:06:02AM -0400, covici@ccs.covici.com wrote
> >> > When I start gdm, I get a message on the screen which says oh no,
> >> > something has gone wrong.  The log file is at
> >> > http://pastebin.com/qwNE7ee6   -- I would appreciate any help.
> >> >
> >> > I am running gentoo testing with the 3.8 unmasked.
> >>
> >>   Direct from the "Making systemd more accessible to "normal" users"
> >> flamewar on gentoo-dev...
> >>
> >> > And now that GNOME 3.8 is out, the game starts over again: logind
> >> > is a hard requirement, logind is part of systemd, starting logind
> >> > (which replaces consolekit) is not that trivial as you may think
> >> > (and is the thing I started to work on anyway).
> >> >
> >> > And if this wasn't enough, it means that if you want GNOME 3.8,
> >> > you need to get logind, which may or not may get included in our
> >> > udev ebuild and if it won't, it means that you will be forced to use
> >> > systemd as device manager if you want GNOME 3.8, which is believe
> >> > it or not, the thing that Ubuntu did.
> >>
> >>   Do you have systemd/logind installed?
> >
> > Nope, sure don't.   None of the ebuilds pulled it in.  But what about
> > startx?  Would I need logind to do that?
> 
> When you use startx, what does your .xinitrc have? Try with only
> 
> exec gnome-session

My startx is:
#!/bin/sh

#
# This is just a sample implementation of a slightly less primitive
# interface than xinit.  It looks for user .xinitrc and .xserverrc
# files, then system xinitrc and xserverrc files, else lets xinit choose
# its default.  The system xinitrc should probably do things like check
# for .Xresources files and merge them in, start up a window manager,
# and pop a clock and several xterms.
#
# Site administrators are STRONGLY urged to write nicer versions.
#

unset DBUS_SESSION_BUS_ADDRESS
unset SESSION_MANAGER


userclientrc=$HOME/.xinitrc
sysclientrc=/etc/X11/xinit/xinitrc


userserverrc=$HOME/.xserverrc
sysserverrc=/etc/X11/xinit/xserverrc
defaultclient=xterm
defaultserver=/usr/bin/X
defaultclientargs=""
defaultserverargs=""
defaultdisplay=":0"
clientargs=""
serverargs=""

enable_xauth=1


# Automatically determine an unused $DISPLAY
d=0
while true ; do
    [ -e /tmp/.X$d-lock ] || break
    d=$(($d + 1))
done
defaultdisplay=":$d"
unset d


whoseargs="client"
while [ x"$1" != x ]; do
    case "$1" in
    # '' required to prevent cpp from treating "/*" as a C comment.
    /''*|\./''*)
	if [ "$whoseargs" = "client" ]; then
	    if [ x"$client" = x ] && [ x"$clientargs" = x ]; then
		client="$1"
	    else
		clientargs="$clientargs $1"
	    fi
	else
	    if [ x"$server" = x ] && [ x"$serverargs" = x ]; then
		server="$1"
	    else
		serverargs="$serverargs $1"
	    fi
	fi
	;;
    --)
	whoseargs="server"
	;;
    *)
	if [ "$whoseargs" = "client" ]; then
	    clientargs="$clientargs $1"
	else
	    # display must be the FIRST server argument
	    if [ x"$serverargs" = x ] && \
		 expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1; then
		display="$1"
	    else
		serverargs="$serverargs $1"
	    fi
	fi
	;;
    esac
    shift
done

# process client arguments
if [ x"$client" = x ]; then
    client=$defaultclient

    # For compatibility reasons, only use startxrc if there were no client command line arguments
    if [ x"$clientargs" = x ]; then
        if [ -f "$userclientrc" ]; then
            client=$userclientrc
        elif [ -f "$sysclientrc" ]; then
            client=$sysclientrc






        fi
    fi
fi

# if no client arguments, use defaults
if [ x"$clientargs" = x ]; then
    clientargs=$defaultclientargs
fi

# process server arguments
if [ x"$server" = x ]; then
    server=$defaultserver

    # For compatibility reasons, only use xserverrc if there were no server command line arguments
    if [ x"$serverargs" = x -a x"$display" = x ]; then
	if [ -f "$userserverrc" ]; then
	    server=$userserverrc
	elif [ -f "$sysserverrc" ]; then
	    server=$sysserverrc
	fi
    fi
fi

# if no server arguments, use defaults
if [ x"$serverargs" = x ]; then
    serverargs=$defaultserverargs
fi

# if no display, use default
if [ x"$display" = x ]; then
    display=$defaultdisplay
fi

if [ x"$enable_xauth" = x1 ] ; then
    if [ x"$XAUTHORITY" = x ]; then
        XAUTHORITY=$HOME/.Xauthority
        export XAUTHORITY
    fi

    removelist=

    # set up default Xauth info for this machine
    case `uname` in
    Linux*)
        if [ -z "`hostname --version 2>&1 | grep GNU`" ]; then
            hostname=`hostname -f`
        else
            hostname=`hostname`
        fi
        ;;
    *)
        hostname=`hostname`
        ;;
    esac

    authdisplay=${display:-:0}

    mcookie=`/usr/bin/mcookie`







    if test x"$mcookie" = x; then
        echo "Couldn't create cookie"
        exit 1
    fi
    dummy=0

    # create a file with auth information for the server. ':0' is a dummy.
    xserverauthfile=$HOME/.serverauth.$$
    trap "rm -f '$xserverauthfile'" HUP INT QUIT ILL TRAP KILL BUS TERM
    xauth -q -f "$xserverauthfile" << EOF
add :$dummy . $mcookie
EOF




    serverargs=${serverargs}" -auth "${xserverauthfile}


    # now add the same credentials to the client authority file
    # if '$displayname' already exists do not overwrite it as another
    # server man need it. Add them to the '$xserverauthfile' instead.
    for displayname in $authdisplay $hostname$authdisplay; do
        authcookie=`xauth list "$displayname" \
        | sed -n "s/.*$displayname[[:space:]*].*[[:space:]*]//p"` 2>/dev/null;
        if [ "z${authcookie}" = "z" ] ; then
            xauth -q << EOF 
add $displayname . $mcookie
EOF
        removelist="$displayname $removelist"
        else
            dummy=$(($dummy+1));
            xauth -q -f "$xserverauthfile" << EOF
add :$dummy . $authcookie
EOF
        fi
    done
fi












xinit "$client" $clientargs -- "$server" $display $serverargs



retval=$?

if [ x"$enable_xauth" = x1 ] ; then
    if [ x"$removelist" != x ]; then
        xauth remove $removelist
    fi
    if [ x"$xserverauthfile" != x ]; then
        rm -f "$xserverauthfile"
    fi
fi



















exit $retval

And my .xinitrc is:
exec gnome-session



-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] gnome not working

[Mark David Dumlao]

[-- Attachment #1: Type: text/plain, Size: 5195 bytes --]

TLDR: because systemd replaces consolekit with logind,
programs that depend on consolekit to determine which "session"
they're in may fail to do so unless they are also built with systemd
support and the relevant pam session lines are enabled. This causes
several silent failures and may prevent your desktop from starting.

Possible Cause:
If you're using systemd, you may have built some gnome components with
systemd support. This _disables_ consolekit support on those
components, hence failures when booting outside of systemd. Try
rebuilding polkit-gnome and any other gnome components with systemd
support. This makes them use systemd-logind instead of consolekit.

I don't use my system without systemd, but I suspect that you also
have to start dbus and the (HORROR) systemd-logind service. _Someone
ought to write a systemd-logind init script for enterprising gentoo
users_. As it doesn't accept any arguments, I expect that it's as easy
as the _completely untested_ one I have attached. Have fun!

I can't wait to hear the excitement on this list on that, haha - but
logind, like udev, should be able to work without systemd, which is
why ubuntu is considering it.

- http://www.phoronix.com/scan.php?page=news_item&px=MTMyMDE




=== BEGIN ADVENTURES

I just recently fixed some woes I was having with starting an X
session from lightdm. I am also on systemd. I got similar errors to
the top post, X logs ending with "server terminator successfully"
immediately after I perform a login attempt. I _also_ noticed that my
X server died every time I switched virtual terminals, and I was
unable to go back.

This started a painstaking process of blind debugging, following this path:

1) start Xorg manually. is successful.
===
Xorg
===
note: dies when I VT switch back.


2) start Xorg manually and run a program in it. is successful.
===
export DISPLAY=:0
Xorg & terminator
===
note: also dies when I VT switch back.

I suspected that this had something to do with multiseat support. The
idea was that my system "does something" when I VT switch, and I
suspected that whatever it was killed my X.


3) start Xorg manually and run a session in it. is successful.
===
export DISPLAY=:0
Xorg & gnome-session --session=unity
===
notes:
- unity downloaded from unity-gentoo overlay.
- have not been able to completely emerge -uDNtv && emerge -ctav in a
week or so, so I expected problems.
- dies when I VT switch back
- mounting external hard disks fail with "Not authorized to perform action"
- changing settings on Network manager also failed. I expected there
to be a login prompt, but no prompt appeared.

I'd experienced "Not authorized to perform action" before. It was a
message that I got from policykit. So I suspected that my programs
were failing to connect to policykit. (Not really experienced with
polkit).

After reading some manual pages [1][2][3][4][5] in policykit, I
prepared another test.

[1] polkit(8)
[2] pkaction(1)
[3] pkcheck(1)
[4] pkexec(1)
[5] pkttyagent(1)


4) Try running the failing commands using pkcheck/pkexec. They still fail.
/usr/share/polkit-1/actions contains a list of actions available to
policykit. You can also get a list of actions by running "pkaction"

I determined that the relevant policy kit action to mount hard disks
was org.freedesktop.udisks2.filesystem-mount

To test the mount command, I used pkcheck, then pkexec. pkcheck tries
to perform a policykit action directly and reports success or failure
based on exit status. It needs a policykit action name and the PID of
the session.

===
pkcheck --action-id org.freedesktop.udisks2.filesystem-mount --process
$(pgrep gnome-session)
===

pkcheck complains that Authorization requires authentication and -u
wasn't passed. Upon passing -u, pkcheck then complains that no
authentication agent was available.

An authentication agent is the program that generates a popup requiring login.

I found this part suspicious, so I tried to activate an authentication agent.


5) Try running the failing commands with a dummy authentication agent.
They now succeed.

policykit comes with a builtin authentication agent. pkcheck has a
--enable-internal-agent option which automatically produces a password
prompt. Alternatively, you can run pkttyagent --process
PID_OF_SOME_BASH_SESSION in one terminal, and any pkexec'd commands in
that terminal will produce a login prompt on the pkttyagent terminal.

===
pkcheck --action-id org.freedesktop.udisks2.filesystem-mount --process
$(pgrep gnome-session) --enable-internal-agent
--allow-user-interaction
===

A login prompt appears, asking me what username I wish to login as.
This suggests that _policykit is working_, but _gnome's policykit
agent_ isn't.


6) Try to do everything again after emerging polkit-gnome is emerged
with systemd support. They now succeed.

I still can't get lightdm to work (still recompiling stuff)... but gdm
now works just fine, and now I have my desktop working.

Note that your /etc/pam.d/system-auth and system-session are expected
to have lines with pam_systemd rather than pam_ck_connector, as per
Gentoo wiki on systemd.

http://wiki.gentoo.org/wiki/Systemd



might I add that unity looks marvelous on Gentoo.

[-- Attachment #2: systemd-logind --]
[-- Type: application/octet-stream, Size: 572 bytes --]

#!/sbin/runscript
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License, v2 or later
# $Header: /var/cvsroot/gentoo-x86/sys-apps/dbus/files/dbus.initd,v 1.1 2011/11/05 13:56:10 ssuominen Exp $

depend() {
	need dbus
	after bootmisc
}

start() {
	ebegin "Starting systemd-logind"
	start-stop-daemon --start --pidfile /var/run/systemd-logind.pid --exec /usr/lib/systemd/systemd-logind
	eend $?
}

stop() {
	ebegin "Stopping D-BUS system messagebus"
	start-stop-daemon --stop --pidfile /var/run/systemd-logind.pid
	eend $?
}