Isssue with gdm

I apologze if this issue has been discussed before
May load without automatic login enabled , does not show or prompt the user for password but displays anything but.
No viisible errors. Happened after updating last night.
Gdm will load but the actual "box" for logging in is not displayed and gdm seems frozen.
Last edited by Invie (2012-10-09 14:57:57)

I hadn't succeeded in installing this virtual driver It never installs and always displays "Not installed" (even after activating GPS).
I have Windows 7 Starter still and my main guess is that this version is lacking some Sensors functionality. Does anyone have more info?
Nokia Booklet 3G upgraded with Intel x18-m SSD and Fedora 13 (Linux) as main OS

Similar Messages

GNOME 3.16: Crash after login with GDM

Hi all,
I've just upgraded to GNOME 3.16, but unfortunately it wasn't completely successful. After I login with GDM, I get the "Oh no! something has gone wrong" screen, with logout the only option. Funny thing is: when I press the super-key, I have a working GNOME shell. I can even start programs like nautilus and firefox. But the error screen is in my view.
The full log can be viewed here:
https://dl.dropboxusercontent.com/u/52318319/log.txt
Notable things:
- GNOME settings daemon crashes
- After that nautilus
But I can't find any obvious solution in the log. Anyone who could help me here?
Thanks in advance!
Last edited by sh4wn (2015-04-10 20:51:06)

Welcome to the club, https://bbs.archlinux.org/viewtopic.php?id=195880 and https://bbs.archlinux.org/viewtopic.php?id=195866 i guess just have patience...

Compiz starting with GDM allowing multiple users

When i start compiz after login I've got slow GDM when changing user and
white screen after second login.
So there's no way to launch compiz and support two different sessions?
Or can I start compiz together with gdm and not individually for each user?

RAGHAVENDRA HARI N wrote:
Allowing multiple users to receive Ibot in OBIEE-11g with out specifying email addresses.
How to use S A System subject area in OBIEE-11g
How to specify condition in Ibot of OBIEE-11GYou can use the SA System subject area after you set it up by following the documentation link provided below. It could be used in OBIEE Delivers which enables contact information, such as e-mail addresses to be retrieved from a database and used as delivery devices in Delivers instead of having the user's manually setup their own delivery device.
Here is the link to the documentation on how to setup SA system subject area in OBIEE 11g:
http://docs.oracle.com/cd/E14571_01/bi.1111/e10541/sa_system.htm
You can set the condition in the condition tab which is the 3rd one I suppose.

Help setting up Compiz Fusion standalone with gdm, inittab, and tint

Hello!
I'd like to set up my fresh Arch install with Compiz Fusion standalone, using twim, and gdm as the login manager. This all with the inittab method of booting with gdm. Openbox is nice, but I have a fast PC - while I like minimalism, effects are nice.
I've looked at the wiki instructions, and a few forum threads, but haven't so far got it working.
Could someone please explain the different config files I will be working with, and how they mesh together? As in, what process does the system follow through them? Does ~/.xinitrc factor in, or is it only called through startx? That sort of thing.
And, does anyone know if Compiz Fusion will 'mesh' with tint, and provide the same mouse-over image previews of windows available in GNOME?
Thanks
Last edited by Ranguvar (2008-10-20 23:40:59)

If you'll be using gdm create a file called fusion.desktop ("fusion" can be anything you want to name your session and will appear in gdm session listing). Place this file in /etc/X11/sessions.
Mine for reference:
/etc/X11/sessions/fusion.desktop
[Desktop Entry]
Encoding=UTF-8
Name=Fusion
Comment=Compiz Fusion Standalone
Exec=/usr/local/bin/start-fusion.sh
TryExec=/usr/local/bin/start-fusion.sh
Type=Application
Then you need to create a script and place it in /usr/local/bin. As you can see from my fusion.desktop file I've named the script start-fusion.sh. Here's mine for reference:
/usr/local/bin/start-fusion.sh
#!/bin/sh
# Avoid relying on autolaunch to improvise D-Bus sessions for each process
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
#compiz ccp &
#emerald &
sleep 6 && cairo-dock &
sleep 12 && mplayer /usr/share/archlinux/arch-anim.mov &
exec fusion-icon
Make the script executable (do all above as root or use sudo) and you should be able to use gdm to login.
Does ~/.xinitrc factor in, or is it only called through startx?
Well, that would be the case if starting from runlevel 3. You would then want to add a line like this to it:
exec start-fusion.sh
btw: fusion-icon is used rather than the #'ed out method in start-fusion.sh as it provides a way to exit out of the session.
You can also use compiz-deskmenu from aur to provide you with a menu in your fusion session.
As far as tint is concerned, I haven't used it. I use cairo-dock which has a systray plugin. Advantage being I can use it as a widget and hide it away.
Last edited by my0pic (2008-10-16 03:06:49)

Autologin with gdm

What must I do in order to have autologin with gdm?

In tab "security" I select: active autologin and when I'd written my name of user a message tells me.
"Usuario no permitido"
El UID del usuario <<ricardo>> es menor que el MinimalUID permitida.
Manual translate:
"User is not let" (is ban)
The UID of the user <<ricardo>> is a little than the MinimalUID let.
Also if I use active temporized login.

Set up openbox with gdm

I am trying to set up openbox with gdm, but whenever X starts up I see the nvidia logo screen and then a blue screen for a few seconds and it dies and tries again.
This is the basic order of what I did to set it up:
pacman -S xorg
pacman -S nvidia-beyond
nvidia-xconfig
pacman -S gdm
# edit /etc/inittab
pacman -S openbox menumaker obconf gtk-theme-switch2 feh
cp /etc/xdg/openbox/* /home/james/.config/openbox/
# Then I made a openbox.desktop in /etc/X11/sessions

here you go:
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux arch 2.6.17-beyond #1 SMP PREEMPT Mon Sep 18 12:24:35 EST 2006 i686
Build Date: 19 September 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Wed Oct 4 23:49:44 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Mouse0"
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/100dpi").
(**) FontPath set to:
/usr/share/fonts/misc
(**) RgbPath set to "/usr/lib/X11/rgb"
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.0
X.Org XInput driver : 0.6
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(++) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2570 card 1028,0151 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,2571 card 0000,0000 rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,24d2 card 1028,0151 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24d4 card 1028,0151 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,24d7 card 1028,0151 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:3: chip 8086,24de card 1028,0151 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,24dd card 1028,0151 rev 02 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev c2 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,24d0 card 0000,0000 rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,24db card 1028,0151 rev 02 class 01,01,8a hdr 00
(II) PCI: 00:1f:2: chip 8086,24d1 card 1028,0151 rev 02 class 01,01,8f hdr 00
(II) PCI: 00:1f:3: chip 8086,24d3 card 1028,0151 rev 02 class 0c,05,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,24d5 card 1028,0151 rev 02 class 04,01,00 hdr 00
(II) PCI: 01:00:0: chip 10de,00f5 card 10de,037c rev a2 class 03,00,00 hdr 00
(II) PCI: 02:0c:0: chip 8086,100e card 1028,0151 rev 02 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Intel Bridge workaround enabled
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xfc000000 - 0xfeafffff (0x2b00000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xd8000000 - 0xefffffff (0x18000000) MX[B]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[B]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xfbf00000 - 0xfbffffff (0x100000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation unknown chipset (0x00f5) rev 162, Mem @ 0xfc000000/24, 0xe0000000/28, 0xfd000000/24, BIOS @ 0xfea00000/17
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xd0000000 from 0xd7ffffff to 0xcfffffff
(II) Active PCI resource ranges:
[0] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B]
[1] -1 0 0xfebff900 - 0xfebff9ff (0x100) MX[B]
[2] -1 0 0xfebffa00 - 0xfebffbff (0x200) MX[B]
[3] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[4] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[5] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[6] -1 0 0xfea00000 - 0xfea1ffff (0x20000) MX[B](B)
[7] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[8] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[9] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[10] -1 0 0x0000df40 - 0x0000df7f (0x40) IX[B]
[11] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[12] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[13] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[14] -1 0 0x0000fea0 - 0x0000feaf (0x10) IX[B]
[15] -1 0 0x0000fe30 - 0x0000fe33 (0x4) IX[B]
[16] -1 0 0x0000fe20 - 0x0000fe27 (0x8) IX[B]
[17] -1 0 0x0000fe10 - 0x0000fe13 (0x4) IX[B]
[18] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[B]
[19] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[20] -1 0 0x00000374 - 0x00000374 (0x1) IX[B]
[21] -1 0 0x00000170 - 0x00000170 (0x1) IX[B]
[22] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[B]
[23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[24] -1 0 0x0000ff20 - 0x0000ff3f (0x20) IX[B]
[25] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[26] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[27] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B]
[1] -1 0 0xfebff900 - 0xfebff9ff (0x100) MX[B]
[2] -1 0 0xfebffa00 - 0xfebffbff (0x200) MX[B]
[3] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[4] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[5] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[6] -1 0 0xfea00000 - 0xfea1ffff (0x20000) MX[B](B)
[7] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[8] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[9] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[10] -1 0 0x0000df40 - 0x0000df7f (0x40) IX[B]
[11] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[12] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[13] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[14] -1 0 0x0000fea0 - 0x0000feaf (0x10) IX[B]
[15] -1 0 0x0000fe30 - 0x0000fe33 (0x4) IX[B]
[16] -1 0 0x0000fe20 - 0x0000fe27 (0x8) IX[B]
[17] -1 0 0x0000fe10 - 0x0000fe13 (0x4) IX[B]
[18] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[B]
[19] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[20] -1 0 0x00000374 - 0x00000374 (0x1) IX[B]
[21] -1 0 0x00000170 - 0x00000170 (0x1) IX[B]
[22] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[B]
[23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[24] -1 0 0x0000ff20 - 0x0000ff3f (0x20) IX[B]
[25] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[26] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[27] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B]
[5] -1 0 0xfebff900 - 0xfebff9ff (0x100) MX[B]
[6] -1 0 0xfebffa00 - 0xfebffbff (0x200) MX[B]
[7] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[8] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[9] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[10] -1 0 0xfea00000 - 0xfea1ffff (0x20000) MX[B](B)
[11] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[12] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[13] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[16] -1 0 0x0000df40 - 0x0000df7f (0x40) IX[B]
[17] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[18] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[19] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[20] -1 0 0x0000fea0 - 0x0000feaf (0x10) IX[B]
[21] -1 0 0x0000fe30 - 0x0000fe33 (0x4) IX[B]
[22] -1 0 0x0000fe20 - 0x0000fe27 (0x8) IX[B]
[23] -1 0 0x0000fe10 - 0x0000fe13 (0x4) IX[B]
[24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[B]
[25] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[26] -1 0 0x00000374 - 0x00000374 (0x1) IX[B]
[27] -1 0 0x00000170 - 0x00000170 (0x1) IX[B]
[28] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[B]
[29] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[30] -1 0 0x0000ff20 - 0x0000ff3f (0x20) IX[B]
[31] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[32] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[33] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts/libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Type1
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.1.1, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.9625
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.1
(II) Loading extension GLX
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.9625
Module class: X.Org Video Driver
(II) LoadModule: "keyboard"
(II) Loading /usr/lib/xorg/modules/input/keyboard_drv.so
(II) Module keyboard: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) NVIDIA dlloader X Driver 1.0-9625 Thu Sep 14 15:35:06 PDT 2006
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset NVIDIA GPU found
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib/xorg/modules/libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B]
[5] -1 0 0xfebff900 - 0xfebff9ff (0x100) MX[B]
[6] -1 0 0xfebffa00 - 0xfebffbff (0x200) MX[B]
[7] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[8] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[9] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[10] -1 0 0xfea00000 - 0xfea1ffff (0x20000) MX[B](B)
[11] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[12] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[13] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[16] -1 0 0x0000df40 - 0x0000df7f (0x40) IX[B]
[17] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[18] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[19] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[20] -1 0 0x0000fea0 - 0x0000feaf (0x10) IX[B]
[21] -1 0 0x0000fe30 - 0x0000fe33 (0x4) IX[B]
[22] -1 0 0x0000fe20 - 0x0000fe27 (0x8) IX[B]
[23] -1 0 0x0000fe10 - 0x0000fe13 (0x4) IX[B]
[24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[B]
[25] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[26] -1 0 0x00000374 - 0x00000374 (0x1) IX[B]
[27] -1 0 0x00000170 - 0x00000170 (0x1) IX[B]
[28] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[B]
[29] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[30] -1 0 0x0000ff20 - 0x0000ff3f (0x20) IX[B]
[31] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[32] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[33] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B]
[5] -1 0 0xfebff900 - 0xfebff9ff (0x100) MX[B]
[6] -1 0 0xfebffa00 - 0xfebffbff (0x200) MX[B]
[7] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[8] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[9] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[10] -1 0 0xfea00000 - 0xfea1ffff (0x20000) MX[B](B)
[11] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[12] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[13] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[14] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[15] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[16] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[17] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[18] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[19] -1 0 0x0000df40 - 0x0000df7f (0x40) IX[B]
[20] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[21] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[22] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[23] -1 0 0x0000fea0 - 0x0000feaf (0x10) IX[B]
[24] -1 0 0x0000fe30 - 0x0000fe33 (0x4) IX[B]
[25] -1 0 0x0000fe20 - 0x0000fe27 (0x8) IX[B]
[26] -1 0 0x0000fe10 - 0x0000fe13 (0x4) IX[B]
[27] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[B]
[28] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[29] -1 0 0x00000374 - 0x00000374 (0x1) IX[B]
[30] -1 0 0x00000170 - 0x00000170 (0x1) IX[B]
[31] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[B]
[32] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[33] -1 0 0x0000ff20 - 0x0000ff3f (0x20) IX[B]
[34] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[35] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[36] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
[37] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[38] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): NVIDIA GPU GeForce 7800 GS at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 05.71.22.21.09
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 7800 GS at PCI:1:0:0:
(--) NVIDIA(0): DELL 1703FP (CRT-0)
(--) NVIDIA(0): DELL 1703FP (CRT-0): 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(WW) NVIDIA(0): No valid modes for "1600x1200"; removing.
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1280x1024"
(II) NVIDIA(0): "1024x768"
(II) NVIDIA(0): "800x600"
(II) NVIDIA(0): "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B]
[1] 0 0 0xe0000000 - 0xefffffff (0x10000000) MX[B]
[2] 0 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B]
[3] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[7] -1 0 0xfbfe0000 - 0xfbffffff (0x20000) MX[B]
[8] -1 0 0xfebff900 - 0xfebff9ff (0x100) MX[B]
[9] -1 0 0xfebffa00 - 0xfebffbff (0x200) MX[B]
[10] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[11] -1 0 0xffa80800 - 0xffa80bff (0x400) MX[B]
[12] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O
[13] -1 0 0xfea00000 - 0xfea1ffff (0x20000) MX[B](B)
[14] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[15] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[16] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[21] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[22] -1 0 0x0000df40 - 0x0000df7f (0x40) IX[B]
[23] -1 0 0x0000edc0 - 0x0000edff (0x40) IX[B]
[24] -1 0 0x0000ee00 - 0x0000eeff (0x100) IX[B]
[25] -1 0 0x0000eda0 - 0x0000edbf (0x20) IX[B]
[26] -1 0 0x0000fea0 - 0x0000feaf (0x10) IX[B]
[27] -1 0 0x0000fe30 - 0x0000fe33 (0x4) IX[B]
[28] -1 0 0x0000fe20 - 0x0000fe27 (0x8) IX[B]
[29] -1 0 0x0000fe10 - 0x0000fe13 (0x4) IX[B]
[30] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[B]
[31] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[32] -1 0 0x00000374 - 0x00000374 (0x1) IX[B]
[33] -1 0 0x00000170 - 0x00000170 (0x1) IX[B]
[34] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[B]
[35] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[36] -1 0 0x0000ff20 - 0x0000ff3f (0x20) IX[B]
[37] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[38] -1 0 0x0000ff60 - 0x0000ff7f (0x20) IX[B]
[39] -1 0 0x0000ff80 - 0x0000ff9f (0x20) IX[B]
[40] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[41] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(II) NVIDIA(0): Setting mode "1280x1024"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(**) Option "Protocol" "auto"
(**) Mouse0: Device: "/dev/psaux"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 9
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Damage Notification Manager" (type: Other)
(II) XINPUT: Adding extended input device "NVIDIA Kernel RC Handler" (type: Other)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing.

[SOLVED] Problem with GDM and Gnome3

Okay, the Topic was more of a trick. Actually I'm havingt two seperate issues; I googled and such, but have not found anything that really answers my question.
First Issue:
I have my gdm.service enabled, so it starts on statup. I boot into runlevel 3. Now, whenever I type "startx" the screen becomes black, and after a while I come back into my TTY with something along the lines of "Stopping X server". But without any error, etc. It justs stops. When I know do a systemctl status on my gdm.service, I become that:
gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
Active: inactive (dead)
Feb 03 16:47:31 thunderlaptop gdm-simple-slave[475]: WARNING: Failed to give slave programs access to the display. Trying to proceed.
Feb 03 16:48:22 thunderlaptop gdm-password][623]: pam_unix(gdm-password:auth): authentication failure; logname=(unknown) uid=0 euid=0 tty=:0 ruser= rhost= user=thunderuser
Feb 03 16:48:33 thunderlaptop gdm-password][626]: pam_unix(gdm-password:session): session opened for user thunderuser by (unknown)(uid=0)
Feb 03 16:48:33 thunderlaptop gdm-simple-slave[475]: WARNING: Failed to remove slave program access to the display. Trying to proceed.
Feb 03 17:03:17 thunderlaptop systemd[1]: Stopping GNOME Display Manager...
Feb 03 17:03:17 thunderlaptop gdm-simple-slave[475]: GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed
Feb 03 17:03:17 thunderlaptop gdm-simple-slave[475]: WARNING: Child process 626 was already dead.
Feb 03 17:03:17 thunderlaptop gdm-simple-slave[475]: WARNING: Unable to kill session worker process
Feb 03 17:03:18 thunderlaptop gdm-simple-slave[475]: GLib-GObject-CRITICAL: g_object_unref: assertion `object->ref_count > 0' failed
Feb 03 17:03:18 thunderlaptop systemd[1]: Stopped GNOME Display Manager.
After I start it, it puts me into the login screen and I can work just fine with Gnome3. I have no clue where the issuse might be.
The second is simple to explain - I have no Network symbol in the upper right corner, and Gnome3 says the network service is not compatible with my system.
Oh, and another issue. When I type something too long, the text does not start a new line in my console resulting in some Visual problems.
Thanks in advance.
Last edited by ThunderRush (2013-02-04 12:36:57)

Blasphemist wrote:
Isn't GDM starting X and Gnome as it should for you? You shouldn't need to start X unless you want more than one X session. Is that what you are trying to do? After installing Gnome and Gnome-extra, I just use this command to enable GDM. systemctl enable gdm
What is your networking configuration. The beginners guide has been updated within the last week or two about this due to a change in network interface naming. Please give that a look.
Which console and shell are you using? Does it have a line wrap configuration option. This is normally automatic but those are my first questions.
Well, as I said, I start into runlevel 3 and want to start X by myself.
Yes, I realise that it is not wlan0 anymore, and I know the name of my wlan-interface. It works awesomely fine via wifi-menu <interface>, but gnome3 seems to have struggles? Have not found anything about that.
I'm using the gnome shell with bash. But the problem occours in a tty2 console as well. I guess it is a problem with .bashrc, but I have no idea what it might be.
Edit:
So, the fixes for the problems are...
1. Reinstall Linux. My Pam was fucked up somewhoe.
2. systemctl enable NetworkManager and not networkmanager. Please kill me.
3. I wrote the Colorcodes and escape-characters in a variable and used that in the actual PS1. That fixed it, and the guys over at bash suggest that too.
Last edited by ThunderRush (2013-02-04 12:36:42)

[solved] Plymouth fails with GDM

I am using plymouth-legacy from the AUR.
When I boot, the plymouth password prompt for my encrypted root partition comes up and I can enter the password. The next screen is the boot splash screen with the "spinfinity" spinning wheel. The screen flickers a few times but never goes away. Pressing escape shows the console that states the plymouth-quit-wait service failed. I can get to tty2 by pressing [Alt][F2] and login there. I think the plymouth-quit-wait service is actually working fine, but the problem is either gdm is failing or plymouth-quit is not running and plymouth-quit-wait times out waiting for something to happen. I am not really sure what the problem could be because it looks like (from the log below) that gdm has a problem with my graphics card, but it has no problem if plymouth isn't running.
Log snippet for plymouth-quit-wait service. (Full log pastebin below).
Sep 07 13:34:48 chrutabaga systemd[1]: plymouth-quit-wait.service start operation timed out. Terminating.
Sep 07 13:34:48 chrutabaga systemd[1]: Failed to start Wait for Plymouth Boot Screen to Quit.
-- Subject: Unit plymouth-quit-wait.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit plymouth-quit-wait.service has failed.
-- The result is failed.
Sep 07 13:34:48 chrutabaga systemd[1]: Unit plymouth-quit-wait.service entered failed state.
Log snippet for gdm failing. (Full log pastebin below).
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13].
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) intel(0): Failed to claim DRM device.
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Backtrace:
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593966]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197b69) [0x597b69]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 2: /usr/lib/libc.so.6 (0x7faf3b2d8000+0x33df0) [0x7faf3b30bdf0]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7faf36524000+0x6f320) [0x7faf36593320]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 4: /usr/bin/Xorg.bin (xf86DeleteScreen+0x5a) [0x480c3a]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 5: /usr/bin/Xorg.bin (InitOutput+0xaf7) [0x47a2b7]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 6: /usr/bin/Xorg.bin (0x400000+0x3b67a) [0x43b67a]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7faf3b2f8000]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) 8: /usr/bin/Xorg.bin (0x400000+0x25d0e) [0x425d0e]
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Segmentation fault at address 0x7faf366fa7a6
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: Fatal server error:
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: Please consult the The X.Org Foundation support
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: at http://wiki.x.org
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: for help.
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Please also check the log file at "/dev/null" for additional information.
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE)
Sep 07 13:34:30 chrutabaga gdm-Xorg-:0[529]: (EE) Server terminated with error (1). Closing log file.
mkinitcpio.conf
MODULES="i915"
BINARIES=""
FILES=""
HOOKS="base udev plymouth autodetect mdadm_udev lvm2 plymouth-encrypt modconf block filesystems keyboard"
Full log pastebin.
Things I have tried:
Switch to tty2, log in and restart services as below in that order. This brings up gdm, and I can log in without any issue.
sudo systemctl start plymouth-quit
sudo systemctl restart plymouth-quit-wait
sudo systemctl restart gdm-plymouth
Use SLIM as a display manager. This works for some reason, but I don't want to use slim. (Off topic, but I use more than one desktop manager and slim doesn't do a great job with remembering my last session.)
Don't use a display manager. Plymouth boots fine to a console. There are no errors. I can then start gdm with no problem.
sudo systemctl start gdm
Using lightdm has the same result as gdm.
Using the gdm.service instead of gdm-plymouth.service has the same result.
I tried this thread. I don't have an nvidia card and the modified gdm-plymouth service didn't change anything.
I also followed this thread on the fedora forums, which advised moving /var/journal to /var/journal.org. That seems pretty bizarre but I tried it anyways. No effect for me.
Last edited by jkav77 (2014-09-08 23:30:00)

markzz wrote:
flamusdiu wrote:I am the maintainer for the plymouth-legacy. I'll look into figuring out something. I don't use GDM though.
Doesn't matter if you don't use it, the package includes parts for GDM. Some testing for KDM or other login managers would be a good thing to do too.
I am aware of that. I don't have other login mangers installed but something changed between the two updates. As I said, I'll look into it. I know SLiM and LightDM work with this build. Let you know something soon.

Can't login with gdm and get error message

Hey, I had an arch install up and running last night. I was tinkering with gnome themes, and installed a bunch and eventually tried to mess with the login screen. I installed something, I think like gnome-settings-manager or something like that, and it basically never worked. I tried to change the login BG and some stuff, but couldn't do it, the program would freeze.
About an hour later, I realized chrome wouldn't run, and I had to use the default browser. I restarted and then when I logged back in, I have a black login screen with an error that says "Install Problem: the configuration defaults for gnome power manager have not been installed correctly please contact your computer administrator."
When I try to login, it starts like it's going to work, but then brings me back to the same screen.
So basically I can't login at the moment, I tried pacman -Runs gnome gdm gnome-setting-manager gamin gksu
and then pacman -S gnome gdm gksu gamin
but that still gives me the same screen.
Any ideas where to go from here?
Edit: Decided to install KDE as a workaround, I'll see where that gets me, opening a new thread as my root partition is now full... and IDK how to fix that atm
Last edited by B-80 (2011-01-10 23:31:10)

Just my 2 cents, seeing that nobody is replying...
You could try to create another user and see if it works well, just to understand if it's a problem in the user configuration files, or in the system configuration.
If the new user works well you could try to import your config files from your /home/user/ folder one by one and see which one messes up everything.
If the new user has the same problems, it's a more serious problem, maybe you could try to remove packages one by one (pacman -Rscn package), starting from the last one you installed (you can list packages by installation date using yaourt -Qe --date) until it works again (taking care of not removing essential packages).

XFCE4 with GDM - Login Screen Format Configuration?

How does one adjust/configure basic things like the size of the GDM login screen in this environment? As it stands, it is much wider than my initial video mode allows, causing the Login button, for instance, to be off the right of the screen. I can still log on using Tab to the button and such, but how does one fix the format problem? Where is the configuration for the GDM login screen kept when using XFCE4 as the desktop manager? All the suggestions so far presume you are using GNOME and not XFCE4. Thanks!
- Michael

I don't know how to tell which xorg video drivers are installed but will happily check if you tell me how to do so.
Adding vga=773 to the linux kernel cmdline (e/edit/f10 in grub) has no effect (no change in symptoms). My xfce4 desktop has an initial resolution of 800x600, but automatically adjusts correctly when I fullscreen the VMware session with Ctrl+Alt-Enter, so I would have to say that xfce4 is performing properly after login. The grub login menu acts as if the screen was perhaps 1024 wide, but it gets clipped to an actual 800x600 graphic window during login.
This is in a VMware Workstation 7.1 virtual machine installed using 'Other Linux 2.6.x kernel 64-bit' which seemed to be the closest match to Arch.
- Michael

[SOLVED] Error message with GDM 2.20-1

I got this error message with executing GDM 2.20-1 on Arch 64 bit:
gdm-binary[5740]: WARNING:Didn't understand ' ' (expected true or false
What does this error means? and how do in fix it? Thanks in advance for helping.
Last edited by zodmaner (2007-10-14 13:48:31)

About the gdm error:
jgc wrote:
This is caused by the empty values in defaults.conf:
TimedLogin=
I'll remove them from the default configuration file soon, they're harmless though.
About the firefox segfaulting, open a new topic with more information about your problem

Problems with GDM [given up]

I've been using KDM for a while now, but I'm not using KDE anymore and I wanted to uninstall it at all.
I installed GDM with all its dependencies via pacman but when I try to start X using it (either with the GDM command or the /etc/rc.d/gdm start), it crashes. Ocasionally this message appears: "The greeter application appears to be crashing. Attempting to use a different one."
Can someone help me please?
Last edited by andre.ramaciotti (2007-06-13 15:23:04)

Try to copy my gdm config to /etc/gdm/custom.conf. Also check /etc/gdm dir and files ownership and properties. And I forgotten to mention that you might just need to start GNOME from kdm and from *gnome menu* "Login Window" (or what it is) *OR* additionally reactivate-activate Chooser (Launch field).
# GDM Custom Configuration file.
# This file is the appropriate place for specifying your customizations to the
# GDM configuration. If you run gdmsetup, it will automatically edit this
# file for you and will cause the daemon and any running GDM GUI programs to
# automatically update with the new configuration. Not all configuration
# options are supported by gdmsetup, so to modify some values it may be
# necessary to modify this file directly by hand.
# This file overrides the default configuration settings. These settings
# are stored in the GDM System Defaults configuration file, which is found
# at the following location.
# /usr/share/gdm/defaults.conf.
# This file contains comments about the meaning of each configuration option,
# so is also a useful reference. Also refer to the documentation links at
# the end of this comment for further information. In short, to hand-edit
# this file, simply add or modify the key=value combination in the
# appropriate section in the template below this comment section.
# For example, if you want to specify a different value for the Enable key
# in the "[debug]" section of your GDM System Defaults configuration file,
# then add "Enable=true" in the "[debug]" section of this file. If the
# key already exists in this file, then simply modify it.
# Older versions of GDM used the "gdm.conf" file for configuration. If your
# system has an old gdm.conf file on the system, it will be used instead of
# this file - so changes made to this file will not take effect. Consider
# migrating your configuration to this file and removing the gdm.conf file.
# If you hand edit a GDM configuration file, you can run the following
# command and the GDM daemon will immediately reflect the change. Any
# running GDM GUI programs will also be notified to update with the new
# configuration.
# gdmflexiserver --command="UPDATE_CONFIG <configuration key>"
# e.g, the "Enable" key in the "[debug]" section would be "debug/Enable".
# You can also run gdm-restart or gdm-safe-restart to cause GDM to restart and
# re-read the new configuration settings. You can also restart GDM by sending
# a HUP or USR1 signal to the daemon. HUP behaves like gdm-restart and causes
# any user session started by GDM to exit immediately while USR1 behaves like
# gdm-safe-restart and will wait until all users log out before restarting GDM.
# For full reference documentation see the gnome help browser under
# GNOME|System category. You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
# NOTE: Lines that begin with "#" are considered comments.
# Have fun!
[daemon]
TimedLoginDelay=10
[security]
[xdmcp]
[gui]
GtkRC=
[greeter]
Browser=true
DefaultWelcome=false
Welcome=Welcome to Arch Linux %n
IncludeAll=true
Use24Clock=yes
BackgroundType=0
BackgroundImage=/usr/share/pixmaps/backgrounds/cosmos/earth-horizon.jpg
Logo=
TitleBar=false
SoundOnLoginFile=/opt/kde/share/sounds/KDE_Startup.wav
SoundOnLogin=false
[chooser]
[debug]
# Note that to disable servers defined in the GDM System Defaults
# configuration file (such as 0=Standard, you must put a line in this file
# that says 0=inactive, as described in the Configuration section of the GDM
# documentation.
[servers]
# Also note, that if you redefine a [server-foo] section, then GDM will
# use the definition in this file, not the GDM System Defaults configuration
# file. It is currently not possible to disable a [server-foo] section
# defined in the GDM System Defaults configuration file.
[server-Standard]
name=Standard server
command=/usr/bin/X -audit 0
chooser=false
handled=true
flexible=true
priority=0
#aris002 added below
[server-XGL]
name=Xgl server
command=/usr/bin/Xgl :1 -accel xv:pbuffer -accel glx:pbuffer
flexible=true
chooser=false
handled=true
priority=0

TOUCH ISSSUES WITH XPERIA Z1

im currently having a problem with the new update
im currently on 4.3 , build number 14.2.A.1.136 , with the recent update there is a problem with the sensitivity of the keyboard/touchscreen ,
when you are using it for text or games for a couple of minutes , it tends to click multiple times on the screen and most of the letters that you are trying to click are mostly mispelled or sometimes it goes crazy and will type automatically, and what i usually do to remove that from happening is i usually unlock it again and rest the phone for a couple of seconds and wipe the screen eventhough its clean and it will be fixed, but its somehow inconvenient that i have to do this everytime that happens, one thing i noticed though, when that happens the unit is already hot (10-15minutes)and it might be related to why the screen is very sensitive or somewhat insensitive,
Sony 1.) how can i fix this. 2) is there an update that i need to do so we can resolve this 3) give me your opinion
Solved!
Go to Solution.

Repair reference: - 13110-2943010001
Previous ref 13110-2845593001
So, back in March, I sent my phone to the Sony repair facility in the UK - SBE Ltd. The fault I Describes was that one position on the screen was acting as if being continuously touched, but there was absolutely nothing on the screen. The phone was sent back as "repaired", but the only work done was a software update. the phone still did this fault occasionally, but I was prepared to live with it, as I really need my phone!
So, over the Easter weekend, the fault came back on a constant basis, so that the phone was completely unusable. The phone is back at the repair facility, and once again, I am without the phone.
Please make sure it's fixed properly this time, guys, and please hurry up. I nned my phone!!!

Seems to be a isssue with DPM and a Volume that is formated ReFS (Resilient File System) on Server 2012

Hi
Here is the issue(s) I found in using DPM 2012 to Backup Server 2012 with Volumes are formated ReFS. (Short Answser - Looks like a Protection jobs fail if you make a volume on the priotected server that is ReFS, does not matter if its somthing
your protecting)
1. When creating Protecting groups for Volumes that are formated ReFS, they are not listed under all Volumes. All the NTFS volumes show up.
2. Hyper-V -- If Virtual serves is on a ReFS Volume, as soon as your done creating a protection group.    You get a Replica inconsitant.
3. If you modify a protection group where everything is working fine. Add a ReFS Volume put a new vm there and then added it to the protecion group it fails.   Every item comes back replica inconstant after you a consitency check.
What made this so much fun figuring out was I was using dpm 2012 to backup a VM Hosted on a Server 2012.    And and on a NTFS volume it worked fine until I converted one of the volumes to ReFS move my VM there and DPM jobs
stopped working.
DPM failed to stop protection for Microsoft Hyper-V \Backup Using Child Partition Snapshot\VMservertest on Someserve.test.test.com. (ID 3116)
An unexpected error occurred while the job was running. (ID 104 Details: Do not attach the filter to the volume at this time (0x801F000F))
So after some testing it looks like, If one volume on the target Server is ReFS the protection group fails.
Checked technet and I don't see Server 2012 under Supported DPM Agents yet.
http://technet.microsoft.com/en-us/library/hh758036
Has anyone played with the System Center RC Service Pack to see if that fixes the issue.
Eric (Trying to be truly Wise by leaning form the mistakes of others, my success rate says I need to work harder at that.)

Hi,
Please add feedback for that feature and let others vote on it to help prioritize future features.
http://feedback.azure.com/forums/258995-azure-backup-and-scdpm/filters/new
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Deployment Isssue with Jboss and Blazeds

Hi,
I was trying to deploy Blazeds over Jboss 4.0.5.GA , for that i copied blazeds.war, ds-console.war and samples.war to Jboss deploy folder and restarted my jboss server.
when i'm trying to access samples application by using url http://localhost:8180/samples it is throwing
The requested resource (/ds-console/) is not available. exception
at Jboss console i'm geeting below error with all the three wars i deployed earlier
status: Deployment FAILED reason: flex/messaging/MessageBrokerServlet (Unsupported major.minor version 49.0)
state: FAILED
watch: file:/C:/SabaWeb/JBoss_Tomcat/server/default/deploy/blazeds.war
altDD: null
lastDeployed: 1256250757909
lastModified: 1256250757878
I think that is because of i'm not using jdk 1.5 or jboss 5 insted i'm using jdk 1.4 because of some dependency for my existing application
Please let me know which version of blazeds should i use for the above configuration (jboss 4.05 with jdk 1.4) or blazeds is not supported for jdk 1.4 at all
the version i tried was blazeds-turnkey-3.2.0.3978
Thanks,
Anuj

Remove all spaces from the directory path of where jboss is installed.
E.g. change
"c:\my docs\my boss dir" to
"c:\mydocs\myjbossdir".Strange I know. It appears to be an Eclipse issue rather than a jboss issue.
Cheers
Steve
P.S. You might have to change the server timeout to > 50secs (double click on server entry from within Eclipse (Ganymede)).
Edited by: Steve-M on 16-Aug-2009 20:05

Isssue with gdm

Similar Messages

Maybe you are looking for