Composite windows manager window refresh problem

Hello, I'm a very satisfied user of Arch Linux, and I would like to say it is la creme de la creme (the best) distribution for users that wish to control their system (and not vice versa).
However, recently, I had some strange problems with compiz fusion, beryl, and even xcompmgr. I'm using xorg from testing, I do not have a xorg.conf, and I have a GMA 3100 IGP. Compiz fusion was working correctly, without xorg.conf, and after I did the upgrade to kernel 2.6.23 (the day the package was put online), compiz-fusion started to have quite weird problems. It is not kernel related, I compiled my own 2.6.23 kernel, then a 2.6.22.9, and it just did not work as expected.
When I move windows, decoration and the window is just fine. However, the windows stop refreshing (I have to shade the window to refresh it), and when I scale it (not the compiz plugin), the decoration and the window just stretches, and then it refreshes sometimes. I was not able to do a decent video capture of my screen, but I hope the description gives you an idea of the problem. I tried with a xorg.conf, setting xaa acceleration, setting "XAANoOffscreenPixmap" xorg.conf option, adding my user into the video group using gpasswd, and I must admit, it changes nothing.
xorg log:
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/noaarch:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X.Org X Server 1.4.0
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-rc1-ARCH i686
Current Operating System: Linux noaarch 2.6.23.1-rt11vk1 #2 SMP PREEMPT RT Fri Nov 9 16:42:08 EST 2007 i686
Build Date: 07 November 2007 11:19:12AM
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: Tue Nov 13 20:14:53 2007
(EE) Unable to locate/open config file
(II) Loader magic: 0x81d4540
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 2.0
X.Org XInput driver : 2.0
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(--) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,29c0 card 1458,5000 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 8086,29c2 card 1458,d000 rev 02 class 03,00,00 hdr 00
(II) PCI: 00:1a:0: chip 8086,2937 card 1458,5004 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1a:1: chip 8086,2938 card 1458,5004 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1a:2: chip 8086,2939 card 1458,5004 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1a:7: chip 8086,293c card 1458,5006 rev 02 class 0c,03,20 hdr 00
(II) PCI: 00:1b:0: chip 8086,293e card 1458,a002 rev 02 class 04,03,00 hdr 00
(II) PCI: 00:1c:0: chip 8086,2940 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1c:4: chip 8086,2948 card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1c:5: chip 8086,294a card 0000,0000 rev 02 class 06,04,00 hdr 81
(II) PCI: 00:1d:0: chip 8086,2934 card 1458,5004 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,2935 card 1458,5004 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,2936 card 1458,5004 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,293a card 1458,5006 rev 02 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 92 class 06,04,01 hdr 01
(II) PCI: 00:1f:0: chip 8086,2916 card 1458,5001 rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:2: chip 8086,2922 card 1458,b005 rev 02 class 01,06,01 hdr 00
(II) PCI: 00:1f:3: chip 8086,2930 card 1458,5001 rev 02 class 0c,05,00 hdr 00
(II) PCI: 02:00:0: chip 197b,2368 card 1458,b000 rev 00 class 01,01,85 hdr 00
(II) PCI: 03:00:0: chip 10ec,8168 card 1458,e000 rev 01 class 02,00,00 hdr 00
(II) PCI: 04:00:0: chip 1131,7130 card 18d0,2100 rev 01 class 04,80,00 hdr 00
(II) PCI: 04:01:0: chip 1274,5880 card 1274,8001 rev 02 class 04,01,00 hdr 00
(II) PCI: 04:07:0: chip 104c,8024 card 1458,1000 rev 00 class 0c,00,10 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,4), 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:28:0), (0,1,1), BCTRL: 0x0000 (VGA_EN is cleared)
(II) Bus 1 I/O range:
[0] -1 0 0x0000a000 - 0x0000afff (0x1000) IX[b]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:28:4), (0,2,2), BCTRL: 0x0000 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x0000b000 - 0x0000bfff (0x1000) IX[b]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xf0000000 - 0xf0ffffff (0x1000000) MX[b]
(II) PCI-to-PCI bridge:
(II) Bus 3: bridge is at (0:28:5), (0,3,3), BCTRL: 0x0000 (VGA_EN is cleared)
(II) Bus 3 I/O range:
[0] -1 0 0x0000c000 - 0x0000cfff (0x1000) IX[b]
(II) Bus 3 non-prefetchable memory range:
[0] -1 0 0xf1000000 - 0xf2ffffff (0x2000000) MX[b]
(II) Bus 3 prefetchable memory range:
[0] -1 0 0x20000000 - 0x200fffff (0x100000) MX[b]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 4: bridge is at (0:30:0), (0,4,4), BCTRL: 0x0000 (VGA_EN is cleared)
(II) Bus 4 I/O range:
[0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[b]
(II) Bus 4 non-prefetchable memory range:
[0] -1 0 0xf3100000 - 0xf31fffff (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:*(0:2:0) Intel Corporation 82G33/G31 Express Integrated Graphics Controller rev 2, Mem @ 0xf3200000/19, 0xe0000000/28, 0xf3000000/20, I/O @ 0xe100/3
New driver is "i810"
(==) Using default built-in configuration (55 lines)
(==) --- Start of built-in configuration ---
Section "Module"
Load "extmod"
Load "dbe"
Load "glx"
Load "freetype"
Load "type1"
Load "record"
Load "dri"
EndSection
Section "Monitor"
Identifier "Builtin Default Monitor"
EndSection
Section "Device"
Identifier "Builtin Default i810 Device 0"
Driver "i810"
EndSection
Section "Screen"
Identifier "Builtin Default i810 Screen 0"
Device "Builtin Default i810 Device 0"
Monitor "Builtin Default Monitor"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
Monitor "Builtin Default Monitor"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
Monitor "Builtin Default Monitor"
EndSection
Section "Device"
Identifier "Builtin Default vga Device 0"
Driver "vga"
EndSection
Section "Screen"
Identifier "Builtin Default vga Screen 0"
Device "Builtin Default vga Device 0"
Monitor "Builtin Default Monitor"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default i810 Screen 0"
Screen "Builtin Default fbdev Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default vga Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default i810 Screen 0" (0)
(**) | |-->Monitor "Builtin Default Monitor"
(**) | |-->Device "Builtin Default i810 Device 0"
(**) |-->Screen "Builtin Default fbdev Screen 0" (1)
(**) | |-->Monitor "Builtin Default Monitor"
(**) | |-->Device "Builtin Default fbdev Device 0"
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) | |-->Monitor "Builtin Default Monitor"
(**) | |-->Device "Builtin Default vesa Device 0"
(**) |-->Screen "Builtin Default vga Screen 0" (3)
(**) | |-->Monitor "Builtin Default Monitor"
(**) | |-->Device "Builtin Default vga Device 0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "<default keyboard>"
(==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
(II) Open ACPI successful (/var/run/acpid.socket)
(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) Active PCI resource ranges:
[0] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[b]
[1] -1 0 0xf3104000 - 0xf31047ff (0x800) MX[b]
[2] -1 0 0xf3105000 - 0xf31053ff (0x400) MX[b]
[3] -1 0 0xf2000000 - 0xf2000fff (0x1000) MX[b]
[4] -1 0 0xf3287000 - 0xf32870ff (0x100) MX[b]
[5] -1 0 0xf3286000 - 0xf32867ff (0x800) MX[b]
[6] -1 0 0xf3284000 - 0xf32843ff (0x400) MX[b]
[7] -1 0 0xf3280000 - 0xf3283fff (0x4000) MX[b]
[8] -1 0 0xf3285000 - 0xf32853ff (0x400) MX[b]
[9] -1 0 0xf3000000 - 0xf30fffff (0x100000) MX[b](B)
[10] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[b](B)
[11] -1 0 0xf3200000 - 0xf327ffff (0x80000) MX[b](B)
[12] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[13] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b]
[14] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[b]
[15] -1 0 0x0000b300 - 0x0000b303 (0x4) IX[b]
[16] -1 0 0x0000b200 - 0x0000b207 (0x8) IX[b]
[17] -1 0 0x0000b100 - 0x0000b103 (0x4) IX[b]
[18] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
[19] -1 0 0x00000500 - 0x0000051f (0x20) IX[b]
[20] -1 0 0x0000eb00 - 0x0000eb1f (0x20) IX[b]
[21] -1 0 0x0000ea00 - 0x0000ea03 (0x4) IX[b]
[22] -1 0 0x0000e900 - 0x0000e907 (0x8) IX[b]
[23] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[b]
[24] -1 0 0x0000e700 - 0x0000e707 (0x8) IX[b]
[25] -1 0 0x0000e500 - 0x0000e51f (0x20) IX[b]
[26] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[b]
[27] -1 0 0x0000e300 - 0x0000e31f (0x20) IX[b]
[28] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[29] -1 0 0x0000e600 - 0x0000e61f (0x20) IX[b]
[30] -1 0 0x0000e200 - 0x0000e21f (0x20) IX[b]
[31] -1 0 0x0000e100 - 0x0000e107 (0x8) IX[b](B)
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xf3100000 - 0xf3103fff (0x4000) MX[b]
[1] -1 0 0xf3104000 - 0xf31047ff (0x800) MX[b]
[2] -1 0 0xf3105000 - 0xf31053ff (0x400) MX[b]
[3] -1 0 0xf2000000 - 0xf2000fff (0x1000) MX[b]
[4] -1 0 0xf3287000 - 0xf32870ff (0x100) MX[b]
[5] -1 0 0xf3286000 - 0xf32867ff (0x800) MX[b]
[6] -1 0 0xf3284000 - 0xf32843ff (0x400) MX[b]
[7] -1 0 0xf3280000 - 0xf3283fff (0x4000) MX[b]
[8] -1 0 0xf3285000 - 0xf32853ff (0x400) MX[b]
[9] -1 0 0xf3000000 - 0xf30fffff (0x100000) MX[b](B)
[10] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[b](B)
[11] -1 0 0xf3200000 - 0xf327ffff (0x80000) MX[b](B)
[12] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[13] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b]
[14] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[b]
[15] -1 0 0x0000b300 - 0x0000b303 (0x4) IX[b]
[16] -1 0 0x0000b200 - 0x0000b207 (0x8) IX[b]
[17] -1 0 0x0000b100 - 0x0000b103 (0x4) IX[b]
[18] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
[19] -1 0 0x00000500 - 0x0000051f (0x20) IX[b]
[20] -1 0 0x0000eb00 - 0x0000eb1f (0x20) IX[b]
[21] -1 0 0x0000ea00 - 0x0000ea03 (0x4) IX[b]
[22] -1 0 0x0000e900 - 0x0000e907 (0x8) IX[b]
[23] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[b]
[24] -1 0 0x0000e700 - 0x0000e707 (0x8) IX[b]
[25] -1 0 0x0000e500 - 0x0000e51f (0x20) IX[b]
[26] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[b]
[27] -1 0 0x0000e300 - 0x0000e31f (0x20) IX[b]
[28] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[29] -1 0 0x0000e600 - 0x0000e61f (0x20) IX[b]
[30] -1 0 0x0000e200 - 0x0000e21f (0x20) IX[b]
[31] -1 0 0x0000e100 - 0x0000e107 (0x8) IX[b](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 0xf3100000 - 0xf3103fff (0x4000) MX[b]
[5] -1 0 0xf3104000 - 0xf31047ff (0x800) MX[b]
[6] -1 0 0xf3105000 - 0xf31053ff (0x400) MX[b]
[7] -1 0 0xf2000000 - 0xf2000fff (0x1000) MX[b]
[8] -1 0 0xf3287000 - 0xf32870ff (0x100) MX[b]
[9] -1 0 0xf3286000 - 0xf32867ff (0x800) MX[b]
[10] -1 0 0xf3284000 - 0xf32843ff (0x400) MX[b]
[11] -1 0 0xf3280000 - 0xf3283fff (0x4000) MX[b]
[12] -1 0 0xf3285000 - 0xf32853ff (0x400) MX[b]
[13] -1 0 0xf3000000 - 0xf30fffff (0x100000) MX[b](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[b](B)
[15] -1 0 0xf3200000 - 0xf327ffff (0x80000) MX[b](B)
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[18] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[19] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b]
[20] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[b]
[21] -1 0 0x0000b300 - 0x0000b303 (0x4) IX[b]
[22] -1 0 0x0000b200 - 0x0000b207 (0x8) IX[b]
[23] -1 0 0x0000b100 - 0x0000b103 (0x4) IX[b]
[24] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
[25] -1 0 0x00000500 - 0x0000051f (0x20) IX[b]
[26] -1 0 0x0000eb00 - 0x0000eb1f (0x20) IX[b]
[27] -1 0 0x0000ea00 - 0x0000ea03 (0x4) IX[b]
[28] -1 0 0x0000e900 - 0x0000e907 (0x8) IX[b]
[29] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[b]
[30] -1 0 0x0000e700 - 0x0000e707 (0x8) IX[b]
[31] -1 0 0x0000e500 - 0x0000e51f (0x20) IX[b]
[32] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[b]
[33] -1 0 0x0000e300 - 0x0000e31f (0x20) IX[b]
[34] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[35] -1 0 0x0000e600 - 0x0000e61f (0x20) IX[b]
[36] -1 0 0x0000e200 - 0x0000e21f (0x20) IX[b]
[37] -1 0 0x0000e100 - 0x0000e107 (0x8) IX[b](B)
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "type1" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.4.0, 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: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.4.0, 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: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(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 1.4.0, 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: "type1"
(II) Loading /usr/lib/xorg/modules/fonts//libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 1.4.0, 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: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "i810"
(II) Loading /usr/lib/xorg/modules/drivers//i810_drv.so
(II) Module i810: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 2.1.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 2.0
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.3.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 2.0
(II) LoadModule: "vga"
(WW) Warning, couldn't open module vga
(II) UnloadModule: "vga"
(EE) Failed to load module "vga" (module does not exist, 0)
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.2.3
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.2.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ,
965GM, 965GME/GLE, G33, Q35, Q33
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 00:02:0
(--) Assigning device section with no busID to primary device
(--) Chipset G33 found
(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 0xf3100000 - 0xf3103fff (0x4000) MX[b]
[5] -1 0 0xf3104000 - 0xf31047ff (0x800) MX[b]
[6] -1 0 0xf3105000 - 0xf31053ff (0x400) MX[b]
[7] -1 0 0xf2000000 - 0xf2000fff (0x1000) MX[b]
[8] -1 0 0xf3287000 - 0xf32870ff (0x100) MX[b]
[9] -1 0 0xf3286000 - 0xf32867ff (0x800) MX[b]
[10] -1 0 0xf3284000 - 0xf32843ff (0x400) MX[b]
[11] -1 0 0xf3280000 - 0xf3283fff (0x4000) MX[b]
[12] -1 0 0xf3285000 - 0xf32853ff (0x400) MX[b]
[13] -1 0 0xf3000000 - 0xf30fffff (0x100000) MX[b](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[b](B)
[15] -1 0 0xf3200000 - 0xf327ffff (0x80000) MX[b](B)
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[18] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[19] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b]
[20] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[b]
[21] -1 0 0x0000b300 - 0x0000b303 (0x4) IX[b]
[22] -1 0 0x0000b200 - 0x0000b207 (0x8) IX[b]
[23] -1 0 0x0000b100 - 0x0000b103 (0x4) IX[b]
[24] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
[25] -1 0 0x00000500 - 0x0000051f (0x20) IX[b]
[26] -1 0 0x0000eb00 - 0x0000eb1f (0x20) IX[b]
[27] -1 0 0x0000ea00 - 0x0000ea03 (0x4) IX[b]
[28] -1 0 0x0000e900 - 0x0000e907 (0x8) IX[b]
[29] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[b]
[30] -1 0 0x0000e700 - 0x0000e707 (0x8) IX[b]
[31] -1 0 0x0000e500 - 0x0000e51f (0x20) IX[b]
[32] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[b]
[33] -1 0 0x0000e300 - 0x0000e31f (0x20) IX[b]
[34] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[35] -1 0 0x0000e600 - 0x0000e61f (0x20) IX[b]
[36] -1 0 0x0000e200 - 0x0000e21f (0x20) IX[b]
[37] -1 0 0x0000e100 - 0x0000e107 (0x8) IX[b](B)
(--) Assigning device section with no busID to primary device
(--) Chipset vesa found
(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 0xf3100000 - 0xf3103fff (0x4000) MX[b]
[5] -1 0 0xf3104000 - 0xf31047ff (0x800) MX[b]
[6] -1 0 0xf3105000 - 0xf31053ff (0x400) MX[b]
[7] -1 0 0xf2000000 - 0xf2000fff (0x1000) MX[b]
[8] -1 0 0xf3287000 - 0xf32870ff (0x100) MX[b]
[9] -1 0 0xf3286000 - 0xf32867ff (0x800) MX[b]
[10] -1 0 0xf3284000 - 0xf32843ff (0x400) MX[b]
[11] -1 0 0xf3280000 - 0xf3283fff (0x4000) MX[b]
[12] -1 0 0xf3285000 - 0xf32853ff (0x400) MX[b]
[13] -1 0 0xf3000000 - 0xf30fffff (0x100000) MX[b](B)
[14] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[b](B)
[15] -1 0 0xf3200000 - 0xf327ffff (0x80000) MX[b](B)
[16] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[17] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[18] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[20] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[21] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[22] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b]
[23] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[b]
[24] -1 0 0x0000b300 - 0x0000b303 (0x4) IX[b]
[25] -1 0 0x0000b200 - 0x0000b207 (0x8) IX[b]
[26] -1 0 0x0000b100 - 0x0000b103 (0x4) IX[b]
[27] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
[28] -1 0 0x00000500 - 0x0000051f (0x20) IX[b]
[29] -1 0 0x0000eb00 - 0x0000eb1f (0x20) IX[b]
[30] -1 0 0x0000ea00 - 0x0000ea03 (0x4) IX[b]
[31] -1 0 0x0000e900 - 0x0000e907 (0x8) IX[b]
[32] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[b]
[33] -1 0 0x0000e700 - 0x0000e707 (0x8) IX[b]
[34] -1 0 0x0000e500 - 0x0000e51f (0x20) IX[b]
[35] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[b]
[36] -1 0 0x0000e300 - 0x0000e31f (0x20) IX[b]
[37] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[38] -1 0 0x0000e600 - 0x0000e61f (0x20) IX[b]
[39] -1 0 0x0000e200 - 0x0000e21f (0x20) IX[b]
[40] -1 0 0x0000e100 - 0x0000e107 (0x8) IX[b](B)
[41] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[42] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 2.0
(II) intel(0): Creating default Display subsection in Screen section
"Builtin Default i810 Screen 0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (==) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) G33
(--) intel(0): Chipset: "G33"
(--) intel(0): Linear framebuffer at 0xE0000000
(--) intel(0): IO registers at addr 0xF3200000
(II) intel(0): 2 display pipes available.
(==) intel(0): Using XAA for acceleration
(--) intel(0): Will try to allocate texture pool for old Mesa 3D driver.
(II) intel(0): Will try to reserve 32768 kiB of AGP aperture space
for the DRM memory manager.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module "i2c" already built-in
(II) intel(0): Output VGA using monitor section Builtin Default Monitor
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
(II) intel(0): No SDVO device found on SDVOB
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72.
(II) intel(0): No SDVO device found on SDVOC
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
(II) intel(0): Output VGA connected
(II) intel(0): Output VGA using initial mode 1360x768
(II) intel(0): detected 1024 kB GTT.
(II) intel(0): detected 7164 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Will not try to enable page flipping
(==) intel(0): Triple buffering disabled
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(==) intel(0): DPI set to (96, 96)
(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 1.4.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.4.0, module version = 1.2.0
ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
(II) intel(0): Comparing regs from server start up to After PreInit
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xf3000000 - 0xf30fffff (0x100000) MS[b]
[1] 0 0 0xe0000000 - 0xefffffff (0x10000000) MS[b]
[2] 0 0 0xf3200000 - 0xf327ffff (0x80000) MS[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 0xf3100000 - 0xf3103fff (0x4000) MX[b]
[8] -1 0 0xf3104000 - 0xf31047ff (0x800) MX[b]
[9] -1 0 0xf3105000 - 0xf31053ff (0x400) MX[b]
[10] -1 0 0xf2000000 - 0xf2000fff (0x1000) MX[b]
[11] -1 0 0xf3287000 - 0xf32870ff (0x100) MX[b]
[12] -1 0 0xf3286000 - 0xf32867ff (0x800) MX[b]
[13] -1 0 0xf3284000 - 0xf32843ff (0x400) MX[b]
[14] -1 0 0xf3280000 - 0xf3283fff (0x4000) MX[b]
[15] -1 0 0xf3285000 - 0xf32853ff (0x400) MX[b]
[16] -1 0 0xf3000000 - 0xf30fffff (0x100000) MX[b](B)
[17] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[b](B)
[18] -1 0 0xf3200000 - 0xf327ffff (0x80000) MX[b](B)
[19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
[20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
[21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
[22] 0 0 0x0000e100 - 0x0000e107 (0x8) IS[b]
[23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[24] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[25] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[26] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b]
[27] -1 0 0x0000b400 - 0x0000b40f (0x10) IX[b]
[28] -1 0 0x0000b300 - 0x0000b303 (0x4) IX[b]
[29] -1 0 0x0000b200 - 0x0000b207 (0x8) IX[b]
[30] -1 0 0x0000b100 - 0x0000b103 (0x4) IX[b]
[31] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[b]
[32] -1 0 0x00000500 - 0x0000051f (0x20) IX[b]
[33] -1 0 0x0000eb00 - 0x0000eb1f (0x20) IX[b]
[34] -1 0 0x0000ea00 - 0x0000ea03 (0x4) IX[b]
[35] -1 0 0x0000e900 - 0x0000e907 (0x8) IX[b]
[36] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[b]
[37] -1 0 0x0000e700 - 0x0000e707 (0x8) IX[b]
[38] -1 0 0x0000e500 - 0x0000e51f (0x20) IX[b]
[39] -1 0 0x0000e400 - 0x0000e41f (0x20) IX[b]
[40] -1 0 0x0000e300 - 0x0000e31f (0x20) IX[b]
[41] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[42] -1 0 0x0000e600 - 0x0000e61f (0x20) IX[b]
[43] -1 0 0x0000e200 - 0x0000e21f (0x20) IX[b]
[44] -1 0 0x0000e100 - 0x0000e107 (0x8) IX[b](B)
[45] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[46] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) intel(0): Kernel reported 109824 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 439292 kB available
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers and
large DRI memory manager reservation:
(II) intel(0): Allocating 5100 scanlines for pixmap cache
(II) intel(0): Success.
(II) intel(0): Increasing the scanline pitch to allow tiling mode (1408 -> 2048).
(II) intel(0): Memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB)
(II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB)
(II) intel(0): 0x00032000-0x00032fff: overlay registers (4 kB)
(II) intel(0): 0x00033000-0x00033fff: G33 hw status (4 kB)
(II) intel(0): 0x00040000-0x032b7fff: front buffer (51680 kB)
(II) intel(0): 0x006ff000: end of stolen memory
(II) intel(0): 0x032b8000-0x032c7fff: xaa scratch (64 kB)
(II) intel(0): 0x04000000-0x04ffffff: back buffer (10880 kB)
(II) intel(0): 0x05000000-0x05ffffff: depth buffer (10880 kB)
(II) intel(0): 0x06000000-0x07ffffff: DRI memory manager (32768 kB)
(II) intel(0): 0x08000000-0x09ffffff: textures (32768 kB)
(II) intel(0): 0x10000000: end of aperture
(II) intel(0): front buffer is not tiled
(II) intel(0): back buffer is tiled
(II) intel(0): depth buffer is tiled
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer handle = 0xe0040000
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(II) intel(0): Unable to use TTM-based memory manager with DRM version 1.6
(II) intel(0): [drm] Registers = 0xf3200000
(II) intel(0): [drm] ring buffer = 0xe0000000
(II) intel(0): [drm] init sarea width,height = 1360 x 1360 (pitch 2048)
(II) intel(0): [drm] Mapping front buffer
(II) intel(0): [drm] Front Buffer = 0x2c008000
(II) intel(0): [drm] Back Buffer = 0xe4000000
(II) intel(0): [drm] Depth Buffer = 0xe5000000
(II) intel(0): [drm] textures = 0xe8000000
(II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
(II) intel(0): [dri] visual configs initialized
(II) intel(0): Page Flipping disabled
(==) intel(0): Write-combining range (0xe0000000,0x10000000)
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) intel(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x006ff000 (pgoffset 1791)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x032b8000 (pgoffset 12984)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x04000000 (pgoffset 16384)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x05000000 (pgoffset 20480)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x08000000 (pgoffset 32768)
(WW) intel(0): ESR is 0x00000010, page table error
(WW) intel(0): PGTBL_ER is 0x00010000, overlay GTT PTE
(WW) intel(0): Existing errors found in hardware state.
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is on
(II) intel(0): Display plane A is now enabled and connected to pipe A.
(II) intel(0): Pipe B is off
(II) intel(0): Display plane B is now disabled and connected to pipe B.
(II) intel(0): Output VGA is connected to pipe A
(II) intel(0): Set up overlay video
(II) intel(0): [DRI] installation complete
(II) intel(0): [drm] dma control initialized, using IRQ 16
(II) intel(0): direct rendering: Enabled
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(--) RandR disabled
(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 XAccessControlExtension
(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
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i915_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) intel(0): Setting screen physical size to 359 x 203
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"
(==) <default pointer>: Protocol: "Auto"
(**) Option "CorePointer"
(**) <default pointer>: always reports core events
(==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
(**) <default pointer>: ZAxisMapping: buttons 4 and 5
(**) <default pointer>: Buttons: 9
(**) <default pointer>: Sensitivity: 1
(**) Option "CoreKeyboard"
(**) <default keyboard>: always reports core events
(**) Option "Protocol" "standard"
(**) <default keyboard>: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) <default keyboard>: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) <default keyboard>: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) <default keyboard>: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) <default keyboard>: CustomKeycodes disabled
(II) evaluating device (<default keyboard>)
(II) XINPUT: Adding extended input device "<default keyboard>" (type: KEYBOARD)
(II) evaluating device (<default pointer>)
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(--) <default pointer>: PnP-detected protocol: "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
Oh, I forgot to tell that compiz outputs no error messages.
Also, I find it weird that xorg uses the i810 driver, as I only have the "intel" driver installed.
Last edited by Synthetix (2007-11-14 01:21:15)

hmm dell would only launch X using the intel drivers and I"m having the same problem with compiz fusion that you had. My windows don't update themselves. It's quite frustrating.

Similar Messages

Looking for "Window Manager\Window Manager Group" SID

Hi. I am trying to find the SID for "Windows Manager\Window Manager Group". If anyone has that, I'd appreciate it. I am trying to build my "base build" Security Template for Server 2012, and I need to assign the default User Rights to that group, as it is
out-of-the-box. Problem is that the GUI does not accept that group name as valid, but I can see that the group is assigned user rights in the Local Security Policy. I typically just use a file ACL to do this (add the ACE and then run
icacls to get the SID), but that group name is not valid within that tool either. My guess if that this new "Windows Manager\Window Manager Group" group is a well-known SID. Thanks.

Ironically the SID is not listed on Microsoft's web page for well know
SIDs. I also noticed that when I dump the local users using powershell, every group and user is listed that I would expect to see, but this one is not in that list. It seems like it should be pretty easy for Microsoft to say what this does and when it can
be safely removed...
I figure one of two possibilities. Either this only matters when a specific feature is installed / active, or it is some remnant from development for a feature or implementation that didn't make it into the release to manufacturing. What ever the case it
would be nice if we could get clarification.

Windows manager\Window Manager Group

Hello - Do any one knows what is the purpose of windows manager\Window Manager Group? I cant find it on local windows group nor local accounts.
Im trying to add windows manager\Window Manager Group to security policy but the account cant be looked up
Thank you,
Adnan
ad

I guess my real question is where are you coming up with the windows manager account? There is no account with such a name by default in Windows, so I am guessing it is something that you have added to your environment or something being talked about
in some third party software install. As such, it would be pretty hard for us to explain its purpose.
.:|:.:|:. tim

Window Manager\Window Manager Group

Based on customer requirements we need to set Bypass traverse checking rights for our Server 2012 boxes. In doing so we noticed that there is a user or group named Window Manager\Window Manager Group. I have seen references in other threads to this user
pointing to the SID (S-1-5-90-0), but this is not documented anywhere on Microsoft website that I can find. I used Powershell to list all of the users, and I do not see a user or group on my Server 2012 box that matches this.
Given no response from Microsoft and no documentation, I cannot effectively decide what I should do with this.
It looks kind of shady that we are granting rights to a SID / Account that we cannot see, so I am wondering if this is some remnant for a part of Server 2012 that didn't get deployed when the code was released to manufacturing. Can some please confirm that
it is OK to drop this user or group (not even sure which one it is) from the Bypass Traverse Checking user right?

Hi，
Based on my research,it is not recommended to remove the group ‘Window manager\Windows manager group’ from Bypass traverse checking or Increase a process working set.
• Both the above user rights are utilized in windows 8/2012 for performance impacts.
• The above mentioned group cannot be added manually to any other groups or no user can be a part of it as it does not resolve in object picker. We cannot even add ACLs to this group.
• Due to above reasons, it is not a security breach in your environment.
This group is a virtual group that is present on every Windows 2012 machine. The DWM.EXE that is used to manage he desktop experience runs under the security context of an account under this group and this is used to provide less privilege to the DWM.EXE.
As such this is not documented anywhere in any of public documents. This is a design decision made by the product team which is part of the architecture of the OS. As such the practice is not to remove this group from both the user rights assignment mentioned.
How Bypass traverse checking affects performance:
When you try to access c:\foo\bar\baz\bletch\george.txt, “the rules” say that you need to confirm that the user has traverse access to:
          C:\foo
          C:\foo\bar
          C:\foo\bar\baz
          C:\foo\bar\baz\bletch
If you didn’t have the “bypass traverse checking” privilege, the system would have to open each of these directories in turn and do an access check to make sure you had access to all the intermediate nodes in the path to the file. With bypass traverse
checking, the filesystems skip all those checks and just check to make sure you have your desired access to the file you’re opening.
How increase a process working set affects performance:
This settings controls who can increase the working set of a process when in memory. Working set is the data that is resending in the Ram that is visible to the process. This helps in expanding the memory a process stores in RAM thereby reducing page faults
(paging out memory to virtual memory which will induce delays of copying the memory back to RAM).
Given the above reasons, I strongly recommend you not to remove ‘Windows manager\Windows manager group’ from Bypass traverse checking as well as increase a process working set user rights assignment.
Thanks.

Screen refresh problem with Windows 7

Hello all,
I've recently begun testing Oracle with Windows 7 on a new HP 2540p notebook computer. I've encountered a very strange issue so far. After logging into Oracle, and Windows switches to Windows Basic theme, I should be taken to the main Navigator screen. But instead, the screen is simply white. If I drag (or nudge) the title bar just a bit, the screen refreshes and I can see the menu items. Then if I click on something (or even use hotkeys - ALT+F to get the file menu, for example), I don't see anything happen. But if I move the window just a bit, the screen refreshes and I can see that it did actually take my input, it just didn't re-draw the screen. I'm wondering if this may be a graphics driver issue (I do have the latest driver for the Intel Graphics Media Accelerator HD adapter), or if someone could point me toward a resolution to this problem. Any help is much appreciated.

Dear All,
Same problem of REFRESH PROBLEM also faced by but only a single and specific Windows 7 client.
if you have resolved the issue , so please share with us.
Thanks
Eidy

CDE Window Manager configuration problem (Sol 8)

Hi
I have a strange problem with CDE. After having a proper PC instalation done, as I log in the CDE I get black background and only 2 windows ( a kind of help window and the File Manager) The windows don't have title bars, cannot be moved ot whatever. Now, I seems to me that the window manager failed to start. Since I'm new to Solaris, can anybody give me a hint where I can find the configuration scripts and error logs.
Thanks
Val

if it were me I'd check /var/dt/Xerrors (Xservers log file)
$HOME/.dt/errorlog & startlogs for clues ... this is where CDE would log
problems.
However you mentioned PC so I'll assume you are using ReflectionsX,
Exceed
or similar, all come with a log file and trace utility via the Xconfig
screen
which maybe worth your while looking into ?
As to the window manager failing to start .... the process is called
dtlogin
and on the Solaris server you should see one parent process + 1 child per
remote display if things are working correctly.
Gotcha's : most likely problems are caused by either Fonts - check PC
Xemulation log files or hostname resolution problems.

User Manager Window problem

Hi,
I'm logged ti TestStand as administrator but the "User Manager" window is dilled i can't acess.
Can you help me please
TestStand 13.0
Solved!
Go to Solution.

Do you have another system installed with TS which works as expected?
If so, copy the users.ini file from the working system over to the non-working. The users.ini is in the TS config directory (by default in ProgramData).
Norbert
EDIT: "dilled" is no english word. That's why i asked... replying "Yes, it is dilled" doesn't really answer my assumption....
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

[SOLVED] Odd window manager problem...

I have installed Arch and a full Gnome DE. However when I start gnome, I get an odd window manager. I tried metacity and metacity --replace in a terminal, but I just get "Window manager warning: Screen 0 on display ":0.0" already has a window manager"
Here is what it looks like:
Any way I can get some metacity going?
Edit: [SOLVED]
I just put metacity as startup application and restarted. Still not sure what that window manager was, but I'll be okay I guess...
Last edited by phohammer (2010-03-03 02:59:43)

sand_man wrote:
haha you had gnome running with twm as the window manager instead of metacity.
You need to put 'exec gnome-session' in your .xinitrc file.
twm huh? Well that's a new one for me!
I tried to do that but the .xinitrc file didn't exist yet and I wasn't sure if I should make it...I think I tried ~/.xinitrc . Would it be in another directory?

Window manager that can scale individual window or virtual desktop?

Xfig doesn't work well on high DPI screens, especially for users whose vision is not that great. The problem is that there is no configuration option to scale elements such as lines.
I see two ways to solve the problem:
Scale the Xfig window.
Scale the virtual desktop on which Xfig is running. Other applications would be running on virtual desktops that are not scaled.
Following a suggestion in the awesome mailing list, I looked into Wayland plus a compositing window manager. However, XWayland, the X compatibility layer, has issues with Xfig. So I guess that for now I’m stuck with X.org, and a window manager compatible with the X composite extension.

Possible solutions:
Pervert: Set up a virtual machine just for Xfig, then use xrandr to scale the desktop inside of the virtual machine.
Saner: Run Xfig in a VNC server (or NX), then connect with a client that supports scaling, e.g. gtk-vnc.
Could be nice: Run Xfig within Xephyr, an X server that runs in a window within X. However, scaling with xrandr doesn't work.
Untested: Use the Compiz Ezoom plugin to scale part of the screen. One would somehow need to prevent windows from being positioned outside of the zoomed area, and also restrict mouse movement.
Last edited by feklee (2015-04-06 11:27:07)

What do you value in a window manager?

I have discovered that Metacity (the default window manager for Gnome) has compositing. This compositing is very basic, mostly adding shadows to windows, but it makes the desktop look and feel very nice (at least to me). I find Compiz-Fusion or just plain Compiz too much, and this very refreshing. There is how ever some functionality that I find myself missing. The most notable is the ability to drag windows from one workspace to another. This got me thinking about what functionality I value in a window manager:
It looks pretty -- Inviting window dressing with shadowing and fading. The transparency effects I never found that interesting. I have tried Openbox numerous times (played with its themes and everything) and I always find it dull and never used it for long. This realization came as a bit of a surprise to me, I had no idea that I valued looks so much.
Fast and clear way of browsing and selecting open windows -- I like it when this is not limited to one workspace, but does give distinction between the workspaces. The window selector in the top right corner of the Gnome desktop or clicking the third button on the desktop in Xfce is prime examples of this. Also, I like to have the option of doing this with the mouse or keyboard and I am annoyed that Alt Tab is limited to one workspace in most cases.
The ability to drag windows from one workspace to another
Simplicity -- I find that Compiz is too much.
I am curious as to what functionality or aspects of window managers others value, and would appreciate any feedback.
Thank you
Last edited by Smith oo4 (2008-04-24 22:26:41)

I value speed and configurability. Consequently, I use Openbox.
Smith oo4 wrote:It looks pretty -- Inviting window dressing with shadowing and fading. The transparency effects I never found that interesting. I have tried Openbox numerous times (played with its themes and everything) and I always find it dull and never used it for long. This realization came as a bit of a surprise to me, I had no idea that I valued looks so much.
If all you need is shadows/fading, Xcompmgr will work inside Openbox and provide those 'features' (I personally dislike them).
Smith oo4 wrote:Fast and clear way of browsing and selecting open windows -- I like it when this is not limited to one workspace, but does give distinction between the workspaces. The window selector in the top right corner of the Gnome desktop or clicking the third button on the desktop in Xfce is prime examples of this. Also, I like to have the option of doing this with the mouse or keyboard and I am annoyed that Alt Tab is limited to one workspace in most cases.
Xfce can set the Alt-Tab window switcher to work on all workspaces (I think). My favorite option is the Openbox desktop menu (accessible by middle-clicking the desktop), which I have mapped to the desktop button on Pypanel (see attached screenshot).
Smith oo4 wrote:The ability to drag windows from one workspace to another
On Openbox, I just right-click the title bar and select 'Send to desktop...'. If you require the dragging functionality, most pagers (such as those in the GNOME or Xfce panels) allow you to drag windows. Bear in mind that more minimal WM's such as the *boxes and Pekwm can run any panel that you want (or no panel at all), so you can bring your GNOME panel along with you.

LightDM suddenly broke after uninstalling a window manager

I've been using LightDM with XFCE fine for months. I just installed the i3 window manager to try it out. I didn't like it, so I uninstalled it. All of the sudden, LightDM no longer works. When it starts, I see just a black screen with a black cursor. The screen flashes once, then comes back with the same black screen/cursor. If I switch to a TTY, I see that systemd-journal is using 100% CPU. I have no idea what went wrong.
I also tried using SLiM. It doesn't freeze like LightDM, but when I try to login, it says "failed to execute login command."
I tried reinstalling LightDM but that didn't make a difference. I know this is really little information, but does anyone know what I can do to fix it?
Last edited by corban (2013-05-12 03:48:43)

[ 131.232]
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 131.232] X Protocol Version 11, Revision 0
[ 131.232] Build Operating System: Linux 3.8.7-1-ARCH x86_64
[ 131.232] Current Operating System: Linux daz 3.8.11-1-ARCH #1 SMP PREEMPT Wed May 1 20:18:57 CEST 2013 x86_64
[ 131.232] Kernel command line: root=/dev/sda1 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
[ 131.232] Build Date: 17 April 2013 02:37:06PM
[ 131.232]
[ 131.232] Current version of pixman: 0.30.0
[ 131.232] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 131.232] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 131.232] (==) Log file: "/var/log/Xorg.0.log", Time: Sun May 12 11:24:05 2013
[ 131.232] (==) Using config file: "/etc/X11/xorg.conf"
[ 131.232] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 131.232] (==) No Layout section. Using the first Screen section.
[ 131.232] (==) No screen section available. Using defaults.
[ 131.232] (**) |-->Screen "Default Screen Section" (0)
[ 131.232] (**) | |-->Monitor "<default monitor>"
[ 131.232] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 131.232] (**) | |-->Device "Gfx card"
[ 131.232] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 131.232] (==) Automatically adding devices
[ 131.232] (==) Automatically enabling devices
[ 131.232] (==) Automatically adding GPU devices
[ 131.232] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 131.232] Entry deleted from font path.
[ 131.232] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 131.232] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 131.232] Entry deleted from font path.
[ 131.232] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 131.232] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 131.232] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 131.232] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 131.232] (II) Loader magic: 0x7fcc20
[ 131.232] (II) Module ABI versions:
[ 131.232] X.Org ANSI C Emulation: 0.4
[ 131.232] X.Org Video Driver: 14.1
[ 131.232] X.Org XInput driver : 19.1
[ 131.232] X.Org Server Extension : 7.0
[ 131.233] (--) PCI:*(0:1:0:0) 10de:1201:1043:83b4 rev 161, Mem @ 0xf6000000/33554432, 0xe0000000/134217728, 0xec000000/67108864, I/O @ 0x0000bf00/128, BIOS @ 0x????????/524288
[ 131.233] Initializing built-in extension Generic Event Extension
[ 131.233] Initializing built-in extension SHAPE
[ 131.233] Initializing built-in extension MIT-SHM
[ 131.233] Initializing built-in extension XInputExtension
[ 131.233] Initializing built-in extension XTEST
[ 131.233] Initializing built-in extension BIG-REQUESTS
[ 131.233] Initializing built-in extension SYNC
[ 131.233] Initializing built-in extension XKEYBOARD
[ 131.233] Initializing built-in extension XC-MISC
[ 131.233] Initializing built-in extension SECURITY
[ 131.233] Initializing built-in extension XINERAMA
[ 131.233] Initializing built-in extension XFIXES
[ 131.233] Initializing built-in extension RENDER
[ 131.233] Initializing built-in extension RANDR
[ 131.233] Initializing built-in extension COMPOSITE
[ 131.233] Initializing built-in extension DAMAGE
[ 131.234] Initializing built-in extension MIT-SCREEN-SAVER
[ 131.234] Initializing built-in extension DOUBLE-BUFFER
[ 131.234] Initializing built-in extension RECORD
[ 131.234] Initializing built-in extension DPMS
[ 131.234] Initializing built-in extension X-Resource
[ 131.234] Initializing built-in extension XVideo
[ 131.234] Initializing built-in extension XVideo-MotionCompensation
[ 131.234] Initializing built-in extension XFree86-VidModeExtension
[ 131.234] Initializing built-in extension XFree86-DGA
[ 131.234] Initializing built-in extension XFree86-DRI
[ 131.234] Initializing built-in extension DRI2
[ 131.234] (II) LoadModule: "glx"
[ 131.234] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 131.239] (II) Module glx: vendor="NVIDIA Corporation"
[ 131.239] compiled for 4.0.2, module version = 1.0.0
[ 131.239] Module class: X.Org Server Extension
[ 131.239] (II) NVIDIA GLX Module 313.30 Wed Mar 27 15:51:21 PDT 2013
[ 131.239] Loading extension GLX
[ 131.239] (==) Matched nouveau as autoconfigured driver 0
[ 131.239] (==) Matched nvidia as autoconfigured driver 1
[ 131.239] (==) Matched nv as autoconfigured driver 2
[ 131.239] (==) Matched vesa as autoconfigured driver 3
[ 131.239] (==) Matched modesetting as autoconfigured driver 4
[ 131.239] (==) Matched fbdev as autoconfigured driver 5
[ 131.239] (==) Assigned the driver to the xf86ConfigLayout
[ 131.239] (II) LoadModule: "nouveau"
[ 131.240] (WW) Warning, couldn't open module nouveau
[ 131.240] (II) UnloadModule: "nouveau"
[ 131.240] (II) Unloading nouveau
[ 131.240] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 131.240] (II) LoadModule: "nvidia"
[ 131.240] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 131.240] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 131.240] compiled for 4.0.2, module version = 1.0.0
[ 131.240] Module class: X.Org Video Driver
[ 131.240] (II) LoadModule: "nv"
[ 131.240] (WW) Warning, couldn't open module nv
[ 131.240] (II) UnloadModule: "nv"
[ 131.240] (II) Unloading nv
[ 131.240] (EE) Failed to load module "nv" (module does not exist, 0)
[ 131.240] (II) LoadModule: "vesa"
[ 131.240] (WW) Warning, couldn't open module vesa
[ 131.240] (II) UnloadModule: "vesa"
[ 131.240] (II) Unloading vesa
[ 131.240] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 131.240] (II) LoadModule: "modesetting"
[ 131.240] (WW) Warning, couldn't open module modesetting
[ 131.240] (II) UnloadModule: "modesetting"
[ 131.240] (II) Unloading modesetting
[ 131.240] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 131.240] (II) LoadModule: "fbdev"
[ 131.240] (WW) Warning, couldn't open module fbdev
[ 131.240] (II) UnloadModule: "fbdev"
[ 131.240] (II) Unloading fbdev
[ 131.240] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 131.240] (II) NVIDIA dlloader X Driver 313.30 Wed Mar 27 15:33:21 PDT 2013
[ 131.240] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 131.240] (++) using VT number 7
[ 131.243] (II) Loading sub module "wfb"
[ 131.243] (II) LoadModule: "wfb"
[ 131.243] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 131.243] (II) Module wfb: vendor="X.Org Foundation"
[ 131.243] compiled for 1.14.1, module version = 1.0.0
[ 131.243] ABI class: X.Org ANSI C Emulation, version 0.4
[ 131.243] (II) Loading sub module "ramdac"
[ 131.243] (II) LoadModule: "ramdac"
[ 131.243] (II) Module "ramdac" already built-in
[ 131.243] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 131.243] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 131.243] (==) NVIDIA(0): RGB weight 888
[ 131.243] (==) NVIDIA(0): Default visual is TrueColor
[ 131.243] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 131.243] (**) NVIDIA(0): Option "NoLogo" "1"
[ 131.243] (**) NVIDIA(0): Option "DamageEvents" "1"
[ 131.243] (**) NVIDIA(0): Option "OnDemandVBlankInterrupts" "1"
[ 131.243] (**) NVIDIA(0): Enabling 2D acceleration
[ 131.515] (II) NVIDIA(GPU-0): Display (Acer G235H (DFP-2)) does not support NVIDIA 3D Vision
[ 131.515] (II) NVIDIA(GPU-0): stereo.
[ 131.516] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 (GF114) at PCI:1:0:0 (GPU-0)
[ 131.516] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 131.516] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
[ 131.516] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 131.517] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 at PCI:1:0:0
[ 131.517] (--) NVIDIA(0): CRT-0
[ 131.517] (--) NVIDIA(0): CRT-1
[ 131.517] (--) NVIDIA(0): DFP-0
[ 131.517] (--) NVIDIA(0): DFP-1
[ 131.517] (--) NVIDIA(0): Acer G235H (DFP-2) (connected)
[ 131.517] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 131.517] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
[ 131.517] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
[ 131.517] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
[ 131.517] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 131.517] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 131.517] (--) NVIDIA(0): Acer G235H (DFP-2): 330.0 MHz maximum pixel clock
[ 131.517] (--) NVIDIA(0): Acer G235H (DFP-2): Internal Dual Link TMDS
[ 131.517] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 131.517] (**) NVIDIA(0): device Acer G235H (DFP-2) (Using EDID frequencies has been
[ 131.517] (**) NVIDIA(0): enabled on all display devices.)
[ 131.518] (==) NVIDIA(0):
[ 131.518] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 131.518] (==) NVIDIA(0): will be used as the requested mode.
[ 131.518] (==) NVIDIA(0):
[ 131.518] (II) NVIDIA(0): Validated MetaModes:
[ 131.518] (II) NVIDIA(0): "DFP-2:nvidia-auto-select"
[ 131.518] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 131.554] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
[ 131.554] (--) NVIDIA(0): option
[ 131.554] (--) Depth 24 pixmap format is 32 bpp
[ 131.554] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 131.554] (II) NVIDIA: access.
[ 131.556] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 131.556] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 131.556] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 131.556] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 131.556] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 131.556] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 131.556] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 131.556] (II) NVIDIA(0): Config Options in the README.
[ 131.557] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
[ 131.578] Loading extension NV-GLX
[ 131.630] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 131.630] (==) NVIDIA(0): Backing store disabled
[ 131.630] (==) NVIDIA(0): Silken mouse enabled
[ 131.630] (==) NVIDIA(0): DPMS enabled
[ 131.630] Loading extension NV-CONTROL
[ 131.630] Loading extension XINERAMA
[ 131.630] (II) Loading sub module "dri2"
[ 131.630] (II) LoadModule: "dri2"
[ 131.630] (II) Module "dri2" already built-in
[ 131.630] (II) NVIDIA(0): [DRI2] Setup complete
[ 131.630] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 131.630] (--) RandR disabled
[ 131.633] (II) Initializing extension GLX
[ 131.656] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 131.656] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 131.656] (II) LoadModule: "evdev"
[ 131.656] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 131.656] (II) Module evdev: vendor="X.Org Foundation"
[ 131.656] compiled for 1.14.0, module version = 2.8.0
[ 131.656] Module class: X.Org XInput Driver
[ 131.656] ABI class: X.Org XInput driver, version 19.1
[ 131.656] (II) Using input driver 'evdev' for 'Power Button'
[ 131.656] (**) Power Button: always reports core events
[ 131.656] (**) evdev: Power Button: Device: "/dev/input/event5"
[ 131.656] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 131.656] (--) evdev: Power Button: Found keys
[ 131.656] (II) evdev: Power Button: Configuring as keyboard
[ 131.656] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event5"
[ 131.656] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 131.656] (**) Option "xkb_rules" "evdev"
[ 131.656] (**) Option "xkb_model" "evdev"
[ 131.656] (**) Option "xkb_layout" "us"
[ 131.668] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 131.668] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 131.668] (II) Using input driver 'evdev' for 'Power Button'
[ 131.668] (**) Power Button: always reports core events
[ 131.668] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 131.668] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 131.668] (--) evdev: Power Button: Found keys
[ 131.668] (II) evdev: Power Button: Configuring as keyboard
[ 131.668] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4/event4"
[ 131.668] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 131.668] (**) Option "xkb_rules" "evdev"
[ 131.668] (**) Option "xkb_model" "evdev"
[ 131.668] (**) Option "xkb_layout" "us"
[ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event15)
[ 131.669] (II) No input driver specified, ignoring this device.
[ 131.669] (II) This device may have been added with another device file.
[ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
[ 131.669] (II) No input driver specified, ignoring this device.
[ 131.669] (II) This device may have been added with another device file.
[ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
[ 131.669] (II) No input driver specified, ignoring this device.
[ 131.669] (II) This device may have been added with another device file.
[ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 131.669] (II) No input driver specified, ignoring this device.
[ 131.669] (II) This device may have been added with another device file.
[ 131.669] (II) config/udev: Adding input device Saitek Cyborg R.A.T.7 Mouse (/dev/input/event0)
[ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: Applying InputClass "evdev pointer catchall"
[ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: Applying InputClass "Mouse Remap"
[ 131.669] (II) Using input driver 'evdev' for 'Saitek Cyborg R.A.T.7 Mouse'
[ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: always reports core events
[ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: Device: "/dev/input/event0"
[ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: ButtonMapping '1 2 3 4 5 6 7 8 9 10 11 12 0 0 0'
[ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Vendor 0x6a3 Product 0xcd7
[ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found 17 mouse buttons
[ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found scroll wheel(s)
[ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found relative axes
[ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found x and y relative axes
[ 131.669] (II) evdev: Saitek Cyborg R.A.T.7 Mouse: Configuring as mouse
[ 131.669] (II) evdev: Saitek Cyborg R.A.T.7 Mouse: Adding scrollwheel support
[ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: YAxisMapping: buttons 4 and 5
[ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 131.669] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input0/event0"
[ 131.669] (II) XINPUT: Adding extended input device "Saitek Cyborg R.A.T.7 Mouse" (type: MOUSE, id 8)
[ 131.669] (II) evdev: Saitek Cyborg R.A.T.7 Mouse: initialized for relative axes.
[ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) keeping acceleration scheme 1
[ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) acceleration profile 0
[ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) acceleration factor: 2.000
[ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) acceleration threshold: 4
[ 131.670] (II) config/udev: Adding input device Saitek Cyborg R.A.T.7 Mouse (/dev/input/mouse0)
[ 131.670] (II) No input driver specified, ignoring this device.
[ 131.670] (II) This device may have been added with another device file.
[ 131.670] (II) config/udev: Adding input device Corsair Corsair Vengeance K60 Keyboard (/dev/input/event1)
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: Applying InputClass "evdev keyboard catchall"
[ 131.670] (II) Using input driver 'evdev' for 'Corsair Corsair Vengeance K60 Keyboard'
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: always reports core events
[ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: Device: "/dev/input/event1"
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Vendor 0x1b1c Product 0xa60
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found keys
[ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as keyboard
[ 131.670] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input1/event1"
[ 131.670] (II) XINPUT: Adding extended input device "Corsair Corsair Vengeance K60 Keyboard" (type: KEYBOARD, id 9)
[ 131.670] (**) Option "xkb_rules" "evdev"
[ 131.670] (**) Option "xkb_model" "evdev"
[ 131.670] (**) Option "xkb_layout" "us"
[ 131.670] (II) config/udev: Adding input device Corsair Corsair Vengeance K60 Keyboard (/dev/input/event2)
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: Applying InputClass "evdev keyboard catchall"
[ 131.670] (II) Using input driver 'evdev' for 'Corsair Corsair Vengeance K60 Keyboard'
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: always reports core events
[ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: Device: "/dev/input/event2"
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Vendor 0x1b1c Product 0xa60
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found 1 mouse buttons
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found scroll wheel(s)
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found relative axes
[ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Forcing relative x/y axes to exist.
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found absolute axes
[ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Forcing absolute x/y axes to exist.
[ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found keys
[ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as mouse
[ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as keyboard
[ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Adding scrollwheel support
[ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: YAxisMapping: buttons 4 and 5
[ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 131.670] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input2/event2"
[ 131.670] (II) XINPUT: Adding extended input device "Corsair Corsair Vengeance K60 Keyboard" (type: KEYBOARD, id 10)
[ 131.670] (**) Option "xkb_rules" "evdev"
[ 131.670] (**) Option "xkb_model" "evdev"
[ 131.670] (**) Option "xkb_layout" "us"
[ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: initialized for relative axes.
[ 131.670] (WW) evdev: Corsair Corsair Vengeance K60 Keyboard: ignoring absolute axes.
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) keeping acceleration scheme 1
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) acceleration profile 0
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) acceleration factor: 2.000
[ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) acceleration threshold: 4
[ 131.671] (II) config/udev: Adding input device Corsair Corsair Vengeance K60 Keyboard (/dev/input/event3)
[ 131.671] (**) Corsair Corsair Vengeance K60 Keyboard: Applying InputClass "evdev keyboard catchall"
[ 131.671] (II) Using input driver 'evdev' for 'Corsair Corsair Vengeance K60 Keyboard'
[ 131.671] (**) Corsair Corsair Vengeance K60 Keyboard: always reports core events
[ 131.671] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: Device: "/dev/input/event3"
[ 131.671] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Vendor 0x1b1c Product 0xa60
[ 131.671] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found keys
[ 131.671] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as keyboard
[ 131.671] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/input/input3/event3"
[ 131.671] (II) XINPUT: Adding extended input device "Corsair Corsair Vengeance K60 Keyboard" (type: KEYBOARD, id 11)
[ 131.671] (**) Option "xkb_rules" "evdev"
[ 131.671] (**) Option "xkb_model" "evdev"
[ 131.671] (**) Option "xkb_layout" "us"
[ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event10)
[ 131.671] (II) No input driver specified, ignoring this device.
[ 131.671] (II) This device may have been added with another device file.
[ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[ 131.671] (II) No input driver specified, ignoring this device.
[ 131.671] (II) This device may have been added with another device file.
[ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event12)
[ 131.671] (II) No input driver specified, ignoring this device.
[ 131.671] (II) This device may have been added with another device file.
[ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
[ 131.671] (II) No input driver specified, ignoring this device.
[ 131.671] (II) This device may have been added with another device file.
[ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
[ 131.671] (II) No input driver specified, ignoring this device.
[ 131.671] (II) This device may have been added with another device file.
[ 131.671] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event7)
[ 131.671] (II) No input driver specified, ignoring this device.
[ 131.671] (II) This device may have been added with another device file.
[ 131.672] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event8)
[ 131.672] (II) No input driver specified, ignoring this device.
[ 131.672] (II) This device may have been added with another device file.
[ 131.672] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event9)
[ 131.672] (II) No input driver specified, ignoring this device.
[ 131.672] (II) This device may have been added with another device file.
[ 131.672] (II) config/udev: Adding input device PC Speaker (/dev/input/event14)
[ 131.672] (II) No input driver specified, ignoring this device.
[ 131.672] (II) This device may have been added with another device file.
Doesn't seem like there's anything wrong. Here's /var/log/lightdm/lightdm.log
[+0.47s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.47s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=255
[+0.47s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
[+0.47s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.87s] DEBUG: Registered seat module xlocal
[+0.87s] DEBUG: Registered seat module xremote
[+0.87s] DEBUG: Adding default seat
[+0.87s] DEBUG: Starting seat
[+0.87s] DEBUG: Starting new display for greeter
[+0.87s] DEBUG: Starting local X display
[+1.08s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+1.08s] DEBUG: Using VT 7
[+1.09s] DEBUG: Activating VT 7
[+1.09s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+1.16s] DEBUG: Writing X server authority to /run/lightdm/root/:0
[+1.16s] DEBUG: Launching X Server
[+1.19s] DEBUG: Launching process 263: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+1.19s] DEBUG: Waiting for ready signal from X server :0
[+1.19s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+1.19s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+7.12s] DEBUG: Got signal 10 from process 263
[+7.12s] DEBUG: Got signal from X server :0
[+7.12s] DEBUG: Connecting to XServer :0
[+7.13s] DEBUG: Starting greeter
[+7.13s] DEBUG: Started session 284 with service 'lightdm-greeter', username 'lightdm'
[+7.42s] DEBUG: Session 284 authentication complete with return value 0: Success
[+7.42s] DEBUG: Greeter authorized
[+7.42s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+7.47s] DEBUG: Session 284 running command /usr/sbin/lightdm-gtk-greeter
[+7.47s] DEBUG: org.freedesktop.Accounts does not exist, falling back to passwd file
[+9.12s] DEBUG: Greeter connected version=1.6.0
[+9.12s] DEBUG: Greeter connected, display is ready
[+9.12s] DEBUG: New display ready, switching to it
[+9.12s] DEBUG: Activating VT 7
[+11.04s] DEBUG: Greeter closed communication channel
[+11.04s] DEBUG: Session 284 exited with return value 139
[+11.04s] DEBUG: Greeter quit
[+11.04s] DEBUG: Failed to start greeter
[+11.04s] DEBUG: Stopping display
[+11.04s] DEBUG: Sending signal 15 to process 263
[+11.47s] DEBUG: Process 263 exited with return value 0
[+11.47s] DEBUG: X server stopped
[+11.47s] DEBUG: Removing X server authority /run/lightdm/root/:0
[+11.47s] DEBUG: Releasing VT 7
[+11.47s] DEBUG: Display server stopped
[+11.47s] DEBUG: Switching to greeter
[+11.47s] DEBUG: Starting new display for greeter
[+11.47s] DEBUG: Starting local X display
[+11.47s] DEBUG: Using VT 7
[+11.48s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+11.48s] DEBUG: Writing X server authority to /run/lightdm/root/:0
[+11.48s] DEBUG: Launching X Server
[+11.48s] DEBUG: Launching process 360: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+11.48s] DEBUG: Waiting for ready signal from X server :0
[+11.91s] DEBUG: Got signal 10 from process 360
[+11.91s] DEBUG: Got signal from X server :0
[+11.91s] DEBUG: Connecting to XServer :0
[+11.91s] DEBUG: Starting greeter
[+11.91s] DEBUG: Started session 372 with service 'lightdm-greeter', username 'lightdm'
[+11.92s] DEBUG: Session 372 authentication complete with return value 0: Success
[+11.92s] DEBUG: Greeter authorized
[+11.92s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+11.92s] DEBUG: Session 372 running command /usr/sbin/lightdm-gtk-greeter
[+12.07s] DEBUG: Greeter connected version=1.6.0
[+12.07s] DEBUG: Greeter connected, display is ready
[+12.07s] DEBUG: New display ready, switching to it
[+12.07s] DEBUG: Activating VT 7
[+12.39s] DEBUG: Greeter closed communication channel
[+12.39s] DEBUG: Session 372 exited with return value 139
[+12.39s] DEBUG: Greeter quit
[+12.39s] DEBUG: Failed to start greeter
[+12.39s] DEBUG: Stopping display
[+12.39s] DEBUG: Sending signal 15 to process 360
[+12.73s] DEBUG: Process 360 exited with return value 0
[+12.73s] DEBUG: X server stopped
[+12.73s] DEBUG: Removing X server authority /run/lightdm/root/:0
[+12.73s] DEBUG: Releasing VT 7
[+12.73s] DEBUG: Display server stopped
[+12.73s] DEBUG: Switching to greeter
[+12.73s] DEBUG: Starting new display for greeter
[+12.73s] DEBUG: Starting local X display
[+12.73s] DEBUG: Using VT 7
[+12.73s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+12.73s] DEBUG: Writing X server authority to /run/lightdm/root/:0
[+12.73s] DEBUG: Launching X Server
[+12.73s] DEBUG: Launching process 396: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+12.73s] DEBUG: Waiting for ready signal from X server :0
[+13.18s] DEBUG: Got signal 10 from process 396
[+13.18s] DEBUG: Got signal from X server :0
[+13.18s] DEBUG: Connecting to XServer :0
[+13.18s] DEBUG: Starting greeter
[+13.18s] DEBUG: Started session 401 with service 'lightdm-greeter', username 'lightdm'
[+13.18s] DEBUG: Session 401 authentication complete with return value 0: Success
[+13.18s] DEBUG: Greeter authorized
[+13.18s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+13.18s] DEBUG: Session 401 running command /usr/sbin/lightdm-gtk-greeter
[+13.28s] DEBUG: Greeter connected version=1.6.0
[+13.28s] DEBUG: Greeter connected, display is ready
[+13.28s] DEBUG: New display ready, switching to it
[+13.28s] DEBUG: Activating VT 7
[+36.01s] DEBUG: Greeter closed communication channel
[+36.01s] DEBUG: Session 401 exited with return value 139
[+36.01s] DEBUG: Greeter quit
[+36.01s] DEBUG: Failed to start greeter
[+36.01s] DEBUG: Stopping display
[+36.01s] DEBUG: Sending signal 15 to process 396
[+36.02s] DEBUG: Process 396 exited with return value 0
[+36.02s] DEBUG: X server stopped
[+36.02s] DEBUG: Removing X server authority /run/lightdm/root/:0
[+36.02s] DEBUG: Releasing VT 7
[+36.02s] DEBUG: Display server stopped
[+36.02s] DEBUG: Switching to greeter
[+36.02s] DEBUG: Starting new display for greeter
[+36.02s] DEBUG: Starting local X display
[+36.02s] DEBUG: Using VT 7
[+36.02s] DEBUG: Activating VT 7
[+36.02s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+36.02s] DEBUG: Writing X server authority to /run/lightdm/root/:0
[+36.02s] DEBUG: Launching X Server
[+36.02s] DEBUG: Launching process 440: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+36.02s] DEBUG: Waiting for ready signal from X server :0
[+36.48s] DEBUG: Got signal 10 from process 440
[+36.48s] DEBUG: Got signal from X server :0
[+36.48s] DEBUG: Connecting to XServer :0
[+36.48s] DEBUG: Starting greeter
[+36.48s] DEBUG: Started session 457 with service 'lightdm-greeter', username 'lightdm'
[+36.48s] DEBUG: Session 457 authentication complete with return value 0: Success
[+36.48s] DEBUG: Greeter authorized
[+36.48s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+36.48s] DEBUG: Session 457 running command /usr/sbin/lightdm-gtk-greeter
[+36.56s] DEBUG: Greeter connected version=1.6.0
[+36.56s] DEBUG: Greeter connected, display is ready
[+36.56s] DEBUG: New display ready, switching to it
[+36.56s] DEBUG: Activating VT 7
[+36.77s] DEBUG: Greeter closed communication channel
[+36.77s] DEBUG: Session 457 exited with return value 139
[+36.77s] DEBUG: Greeter quit
[+36.77s] DEBUG: Failed to start greeter
[+36.77s] DEBUG: Stopping display
[+36.77s] DEBUG: Sending signal 15 to process 440
[+37.10s] DEBUG: Process 440 exited with return value 0
[+37.10s] DEBUG: X server stopped
[+37.10s] DEBUG: Removing X server authority /run/lightdm/root/:0
[+37.10s] DEBUG: Releasing VT 7
[+37.10s] DEBUG: Display server stopped
[+37.10s] DEBUG: Switching to greeter
[+37.10s] DEBUG: Starting new display for greeter
[+37.10s] DEBUG: Starting local X display
[+37.10s] DEBUG: Using VT 7
[+37.10s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+37.10s] DEBUG: Writing X server authority to /run/lightdm/root/:0
[+37.10s] DEBUG: Launching X Server
[+37.10s] DEBUG: Launching process 482: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+37.10s] DEBUG: Waiting for ready signal from X server :0
[+37.52s] DEBUG: Got signal 10 from process 482
[+37.52s] DEBUG: Got signal from X server :0
[+37.52s] DEBUG: Connecting to XServer :0
[+37.52s] DEBUG: Starting greeter
[+37.52s] DEBUG: Started session 487 with service 'lightdm-greeter', username 'lightdm'
[+37.53s] DEBUG: Session 487 authentication complete with return value 0: Success
[+37.53s] DEBUG: Greeter authorized
[+37.53s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+37.53s] DEBUG: Session 487 running command /usr/sbin/lightdm-gtk-greeter
[+37.61s] DEBUG: Greeter connected version=1.6.0
[+37.61s] DEBUG: Greeter connected, display is ready
[+37.61s] DEBUG: New display ready, switching to it
[+37.61s] DEBUG: Activating VT 7
[+60.57s] DEBUG: Greeter closed communication channel
[+60.57s] DEBUG: Session 487 exited with return value 139
[+60.57s] DEBUG: Greeter quit
[+60.57s] DEBUG: Failed to start greeter
[+60.57s] DEBUG: Stopping display
[+60.57s] DEBUG: Sending signal 15 to process 482
[+60.59s] DEBUG: Process 482 exited with return value 0
[+60.59s] DEBUG: X server stopped
[+60.59s] DEBUG: Removing X server authority /run/lightdm/root/:0
[+60.59s] DEBUG: Releasing VT 7
[+60.59s] DEBUG: Display server stopped
[+60.59s] DEBUG: Switching to greeter
[+60.59s] DEBUG: Starting new display for greeter
[+60.59s] DEBUG: Starting local X display
[+60.59s] DEBUG: Using VT 7
[+60.59s] DEBUG: Activating VT 7
[+60.59s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+60.59s] DEBUG: Writing X server authority to /run/lightdm/root/:0
[+60.59s] DEBUG: Launching X Server
[+60.59s] DEBUG: Launching process 543: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+60.59s] DEBUG: Waiting for ready signal from X server :0
[+61.04s] DEBUG: Got signal 10 from process 543
[+61.04s] DEBUG: Got signal from X server :0
[+61.04s] DEBUG: Connecting to XServer :0
[+61.04s] DEBUG: Starting greeter
[+61.04s] DEBUG: Started session 548 with service 'lightdm-greeter', username 'lightdm'
[+61.04s] DEBUG: Session 548 authentication complete with return value 0: Success
[+61.04s] DEBUG: Greeter authorized
[+61.04s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+61.04s] DEBUG: Session 548 running command /usr/sbin/lightdm-gtk-greeter
[+61.12s] DEBUG: Greeter connected version=1.6.0
[+61.12s] DEBUG: Greeter connected, display is ready
[+61.12s] DEBUG: New display ready, switching to it
[+61.12s] DEBUG: Activating VT 7
[+61.34s] DEBUG: Greeter closed communication channel
[+61.34s] DEBUG: Session 548 exited with return value 139
[+61.34s] DEBUG: Greeter quit
[+61.34s] DEBUG: Failed to start greeter
[+61.34s] DEBUG: Stopping display
[+61.34s] DEBUG: Sending signal 15 to process 543
[+61.67s] DEBUG: Process 543 exited with return value 0
[+61.67s] DEBUG: X server stopped
[+61.67s] DEBUG: Removing X server authority /run/lightdm/root/:0
[+61.67s] DEBUG: Releasing VT 7
[+61.67s] DEBUG: Display server stopped
[+61.67s] DEBUG: Switching to greeter
[+61.67s] DEBUG: Starting new display for greeter
[+61.67s] DEBUG: Starting local X display
[+61.67s] DEBUG: Using VT 7
[+61.67s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+61.67s] DEBUG: Writing X server authority to /run/lightdm/root/:0
[+61.67s] DEBUG: Launching X Server
[+61.67s] DEBUG: Launching process 568: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+61.67s] DEBUG: Waiting for ready signal from X server :0
[+62.12s] DEBUG: Got signal 10 from process 568
[+62.12s] DEBUG: Got signal from X server :0
[+62.12s] DEBUG: Connecting to XServer :0
[+62.12s] DEBUG: Starting greeter
[+62.12s] DEBUG: Started session 573 with service 'lightdm-greeter', username 'lightdm'
[+62.13s] DEBUG: Session 573 authentication complete with return value 0: Success
[+62.13s] DEBUG: Greeter authorized
[+62.13s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+62.13s] DEBUG: Session 573 running command /usr/sbin/lightdm-gtk-greeter
[+62.22s] DEBUG: Greeter connected version=1.6.0
[+62.22s] DEBUG: Greeter connected, display is ready
[+62.22s] DEBUG: New display ready, switching to it
[+62.22s] DEBUG: Activating VT 7
[+65.92s] DEBUG: Got signal 15 from process 1
[+65.92s] DEBUG: Caught Terminated signal, shutting down
[+65.92s] DEBUG: Stopping display manager
[+65.92s] DEBUG: Stopping seat
[+65.92s] DEBUG: Stopping display
[+65.92s] DEBUG: Session 573: Sending SIGTERM
[+65.92s] DEBUG: Greeter closed communication channel
[+65.92s] DEBUG: Session 573 exited with return value 0
[+65.92s] DEBUG: Greeter quit
[+65.92s] DEBUG: Sending signal 15 to process 568
Looks like the greeter is repeatedly exiting, but I don't know how to diagnose the problem. Thanks for the help.
Last edited by corban (2013-05-12 16:50:57)

I get an error message when trying to install windows 7 on my macbook pro. The message says "windows has encountered a problem communicating with a device connected to your computer. I don't have anything connected to my computer. How do I fix this?

I'm trying to install windows 7 on my macbook pro. I went through the process of bootcamp telling it to install windows 7. Once the windows boot manager started an error message came up. The error message says " windows has encountered a problem communicating with a device connected to your computer. I don't have a usb connected to my computer. I am using windows 7 professional install disc. I can't figure out what i am doing wrong. The same message keeps coming up over and over. Am I doing something wrong or is it something else?

Well, shucks, i just spent almost 30 minutes trying to find your model user guide to explain it better, I guess they never got around to making it.....
I would just borrow another Windows disk and try installing it again and if it does it again then you might take it to an Apple Store and see if one of the "Genius' " can figure it out.
Make sure your internet is enabled and click on your blank desktop and at the top of your screen is a Help menu option, enter PRAM and it should give you a list of things relating to Pram. It may take a few seconds to list anything as it has to connect to Apples severs first. It should list the things you may have to fill back in when your done.
"P-ram" stores some common information that is used in the background, your date, time, startup disk, etc, that you don't have to re-fill when you restart, it's a little different for each computer.

WINDOWS MANAGEMENT FRAMEWORK 4.0 - A required certificate is not within its validity period

Hello,
I can't figure out if this is because the Root Certificates were updated in April 2014 then apparently expired by Microsoft or if the PowerShell installer signed this file with a bad software release signature??
We were deploying PowerShell 4.0 (Windows6.1-KB2819745-x64-MultiPkg.msu) with ConfigMgr 2012 with a dependency of .NET Framework 4.5.1. Everything was working fine until sometime around April 24 (exact date unknown). Now any
Win 7 SP1 machines I try to update will not install WMF 4.0. They installed .NET 4.5.1 without any trouble..
The digital signature on it it states it was signed Sept 27 2013 and the certificate expires 4/24/2014.
Even if we change the system clock to April 1 2014 it still will not install.. but this shouldn't matter anyway. They just can't sign new software with that certificate.. surely I can install it..
As for a log... If I run as C:\Windows\ccmcache\3>wusa.exe Windows6.1-KB2819745-x64-MultiPkg.msu /log:c:\windows\ccmcache\3\broken.txt
In the broken.txt I see:
Install Worker.01194: Operation Result Code of the installation: 0X4 HRESULT of the installation: 0X80240022 Operation
Result Code of the update:0X4 HRESULT of the update: 0X800b0101
Install Worker.01243: Failed install update Update for Windows (KB2819745)
Install Worker.01287: Exit with error code 0X800b0101 (A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.)
WINDOWS MANAGEMENT FRAMEWORK 4.0 FOR MICROSOFT OPERATING SYSTEM PRODUCTS
Windows6.1-KB2819745-x64-MultiPkg.msu
I also see this same event information in Setup event log..
I don’t know what to do here. Anyone else having this problem?

Hi,
Have you ever seen this article?
Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server
http://support.microsoft.com/kb/2328240/en-us
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

How do I re-enable showing the download files history in the download manager window?

System: Windows XP
I am trying to re-enable showing/retaining the list of downloaded files in the download manager window. I want to be able to drag and drop directly from that window into a folder of my choosing. (I used to be able to do this, but apparently I messed that up...)
I have tried the suggestions that could easily be found, including setting Firefox to remember all history in the Privacy tab of Options.
I also deleted the mimeTypes.rdf file to "reset" the browser defaults, but to no avail.
Any ideas/help?
Thanks.

By the way, a few other things you probably know:
(1) The setting to keep the downloads list displayed after a download is here:
orange Firefox button ''or'' classic Tools menu > Options > General
Check "Show the Downloads window..." and ''uncheck'' "Close it..."
(2) You can always show the list by pressing Ctrl+j
The mimeTypes.rdf file isn't particularly relevant to this problem; it affects what application Firefox uses to open a particular type of file.
However, there is a database file which stores your download history which might be corrupted. You could rename that file and have Firefox start building a new one.
(1) Open your personal settings (AKA Firefox profile) folder
Help (or Alt+h) > Troubleshooting Information > "Show Folder" button
(2) Switch back to Firefox and exit the program (e.g., File > Exit)
(3) Wait a few moments for Firefox to finish updating files in your settings folder, then rename '''downloads.sqlite''' to something else, like downloads.old. Alternately, you can delete the file.
(4) You're done with your profile folder and you can restart Firefox now.
Any improvement?

New window manager (with prototype!) [wmii-like] --- looking for help

I have a prototype for a new window manager in the style of wmii. It is called
cakewm. I currently have a prototype version implemented in pygame, and would
like help moving this to use X---making it a real window manager.
Disclaimer: I have a very limited knowledge of X11 and window manager
development. The most I've done is add a couple new features to wmfs.
To get the code
> git clone git://github.com/saikobee/cakewm.git
Then run main.py. cakewm depends on pygame.
Upon running, press Alt-Enter to fullscreen cakewm and intercept keybinds, or
Alt-Space to just intercept keybinds. Press Alt-Esc to quit. The window
manager related keybinds are listed in the file binds.conf.
Config note: <WSCA-x> means Windows-Shift-Control-Alt-x
Implementation note: pypixel.py is a large and mostly useless dependency. I
forked a library I made previously rather than coding straight in pygame.
cakewm's goals are to be similar to wmii, but with more functionality, easier
configurability, and saner defaults.
- cakewm is fully functional using the keyboard. Mouse support can come later.
- cakewm provides 9 workspaces per monitor.
- cakewm manages each workspace as a group of columns. Each column is like a
wmii default split, except each window can have other windows "stacked" on
top of or behind it.
- cakewm manages column sizes (and window sizes within columns) using a
master/slave paradigm, with the ability to adjust the size ratios.
- cakewm's configuration file is simple key=val pairs, with the ability to
include other files like in C.
- cakewm has a slightly larger emphasis on window decorations (adjustable
size---even in tiled mode) and themes (nothing bloated, like pixmaps or
gradients---it's all still simple colors).
- cakewm will have proper support for international text (Japanese text in
window titles or the wmii status bar generally render as boxes) through the
use of a more advanced text library such as Pango.
Please let me know if you have comments, questions, or concerns. If you are
interested in helping, get in touch with me. If you know somewhere better to
look for volunteers, please let me know.

m4co wrote:
Wow is this forum active. Makes me feel welcome here
The thing about wireless, I actually like command line, but there are a few things that are worth having a applet or something.
And wireless is one of those. I guess I can take a look on wicd.
It's a good idea to have compiz as the WM actually. Would it be lightweight to have it like that?
Is there anybody here that uses compiz as a WM?
For the xfce4-panel, is it possible to get transparency on it? That's probably the only thing holding me back with xfce4-panel.
If "able to run compiz" wasn't a requisite, what other WM would you suggest for my "profile" ?
I would like to hear other users opinions who like to customize everything on a WM.
I recommend running Compiz by itself. There is a good wiki page on it in the Arch wiki. Some apps you'll want to go with it are:
LXAppearance --change GTK/icon theme
Feh or Nitrogen --Set Wallpaper
Xfce4-panel --The lightest one that works with Compiz properly
Or, if you don't want a panel: stalonetray
Compiz-deskmenu --For a customizable right-click main menu
Gmrun --Run dialog (Alt+F2 in most DEs)
And this helped me a lot.
Thank you all for the replies. I appreciate.
Xfce4-panel can have transparency. The only problem is that everything become transparent: text, icons, everything.
I use Compiz as a standalone WM and it is much lighter than DE+Compiz. My Compiz setup uses about 30MB(out of 1GB) more RAM than my Openbox setup (which are both the same except for the WM).

Composite windows manager window refresh problem

Similar Messages

Maybe you are looking for