[SOLVED]Useless after set xfce4's Window Manager Tweaks
My xfwm4's theme is 'B5',when I opened a new window,the window always will pop-ups at the left top of the screen and I just want it to pop-up at the center of the screen.
Then I set the Window Manager Tweaks program, I chose the 'Placement' tag and click on whether 'At the center of the screen' or 'Under the mouse pointer' is useless.
How to fix the set?
Last edited by fool (2014-02-27 05:51:58)
https://wiki.archlinux.org/index.php/Fo … way_Street
Similar Messages
-
[Solved] systemd/user : how to exit window manager & stop X?
Solution: Jump to https://bbs.archlinux.org/viewtopic.php … 6#p1262166
I have set up my system to user systemd units to start my environment (roughly following the wiki).
My problem is that I cannot exit my window manager (using “io (exitWith ExitSuccess)” in Xmonad): the service file starting the WM (xmonad) stops/exits with success, but the xorg.service keeps
running. I need to switch to TTY2, systemctl --user stop xorg.service by hand, then switch to TTY1, execute Ctrl-C, and then I finally get my login
prompt back.
This is a bit annoying, and I don't know how to fix it.
Here are the relevant (I think) unit files:
# xmonad.target
[Unit]
Description=XMonad
Wants=xorg.target
Wants=xinit.target
Requires=dbus.socket
AllowIsolate=true
[Install]
Alias=default.target
# xmonad.service
[Unit]
Description=Starts Xmonad
Before=xinitrc.target
After=xorg.target
Requires=xorg.target
[Service]
ExecStart=/usr/bin/xmonad
Environment=DISPLAY=:0
Restart=no
[Install]
WantedBy=xmonad.target
RequiredBy=xorg.service
As you can see, I have added the RequiredBy=xorg.service line at the bottom, hoping that if xmonad.service exits, so should xorg.service - but to
no avail.
What do I have to do in order to completely stop X and get my login prompt on TTY1 back?
EDIT: I am of course using the user-session-units.
Last edited by Stalafin (2013-04-22 13:54:45)I know it's an old thread (not really old) but I have the same problem. The question is your solution doesnt work with me. It just give me an error like this:
Failed to issue method call: The name org.freedesktop.login1 was not provided by any .service files
Failed to issue method call: Process /bin/false exited with status 1 -
Problems on NW PI 7.1 after setting up a Windows Domain
Hello Experts,
we have had a SAP system running without a windows domain name. Everything works fine until we need to set up a windows domain because of the "full qualified domain name error".
Now after setting up the domain we have problems to access the PI system by SAP Logon from a client. Within the server everything works fine with SAP Logon.
Thanks for your answers in advance!!!
Regards, AlexanderHi Moog,
Check if server hostname and server IP is pingable from client.
If yes then check for dispatcher port connectivity using telnet
telnet server ip 32<instance number>
Paste the results , adding server to domain will not harm unless its pingable from client.
Regards, -
Error in xfce4-settings-manager When Click on Window Manager
Hello all,
I have a problem with the xfce4 environment.
First, I can't see any panel by default.
Second, the settings button near the shutdown button does not work.
Finally and more importantly, when I call from the terminal settings from terminal, settings start fine, but when I click on Window Manager or Window Manager Tweaks I get:
[jav@localhost ~]$ xfce4-settings-manager
These settings cannot work with your current window manager (GNOME Shell)
I already tried deleting sessions as mentioned in Arch wiki and also called startxfce4 again.
Any ideas?startxfce4 should be used to start xfce4-session. It can be run from the virtual terminal(the screen-filling terminal you see when you boot up a (fresh) machine) directly or can be called in your .xinitrc. Instead of
exec xfce4-session
you should have
exec startxfce4
in your .xinitrc.
It looks like you're running startxfce4 from an X session(probably Gnome). Xfce is a replacement for Gnome, it's not run inside of Gnome or any other window manager or desktop environment(well, some parts can, like the panel). What's in your .xinitrc, especially at the exec line? Note that there should be only one exec line.
Last edited by Steef435 (2014-01-03 14:26:09) -
[solved]screen borders and full sized window emerald compiz
hellos archers! i'm using XFCE and i have i little issue, when i maximize a windows in the bottom left and right sides the window borders disappear, (il also make hard to see the scroll bar) is there a way to set that when i maximize a window the borders does stay in the screen?
Last edited by kandros (2011-10-06 22:29:14)alphaniner wrote:In Settings -> Window Manager Tweaks -> Accessibility tab there's an option 'Hide frame of windows when maximized'. Uncheck it.
thank you but i use compiz as window manager instead of xfwm4
EDIT: because of your tip i finally remember that there is an option like this in emerald settings... shame on me that i didnt check it
Last edited by kandros (2011-10-06 22:27:49) -
[SOLVED!] KDE 4.11 - Window Manager seems not to be running?
Greetings,
I still seem unable to fix the fact that systemsettings will run. However it will run if you do kdesu systemsettings.
Doing so I started checking around in it and thought I'd look at the desktop effects, when I was greeted with this:
So, I am guessing that the window borders and buttons are a figment of my imagination....
This is after me pretty much starting over with KDE, removing the .kde and .kde4 folders.
Help?
Edit: That pic seems to not link right. Yay. Basically it says that effects can not be activated or whatever because a window manager seems not to be running. The irony of it is you can see the fact that there are window borders and buttons and such, evidence of a WM...
I wonder if there is something here that is related to me not being able to run systemsettings... yet systemsettings will run fine in any other environment - including Gnome Shell.
Another thing, KDE 4.11 ran great in testing and kde_unstable. Once it went to extra, things happened. I find that odd. Maybe something is missing on my end that most archers already have?
Edit2: fixed image link
Last edited by mythus (2013-08-25 20:49:38)No omeringen, Nvidia user.
I can try again Thaodan since I've had some updates come through (and weeded out some dot files). Last time I tried I saw OpenGL 2 selected. Trying to change to 3 or anything else also got the screenshot in my OP.
I'll log into KDE and see if it still does the same, after a brief check for last minute updates.
EDIT: OK, so I can mark this as solved. I found an odd dot file, who's name excapes me but deals with kde sessions, just sitting around in the home folder. Once I deleted it and restarted, I found that not only System Settings finally ran again as a user, but I could also change and apply desktop effects. Peculiar. I thought that maybe it was a dot file that was causing the problem, that wasn't in the .kde or .kde4 folder. It just took finding it and removing it.
I wish I knew more to tell, but this at least solves my issue, and the issue with the non-running-as-user system settings I had posted in another thread (thinking that they were separate events. Thanks again for all your help guys!
Last edited by mythus (2013-08-25 20:49:05) -
[Solved]Cannot execute i3 window manager
I installed i3 tiling window manager along with kde(kde could be executed),and follow the step written in i3's wiki:
Edit ~/.xinitrc and add:
exec i3
exec i3 -V >>~/.i3/i3log >&1
and cp /etc/i3/config ~/.i3/config,after these steps I still cannot execute i3 wm, could anyone tell me what I missed?
appreciate your reply.
Last edited by tomisacat (2012-07-20 05:14:29)hesse wrote:
tomisacat wrote:
I installed i3 tiling window manager along with kde(kde could be executed),and follow the step written in i3's wiki:
Edit ~/.xinitrc and add:
exec i3
exec i3 -V >>~/.i3/i3log >&1
You should add just one of the above exec statements by the way, and it should be on the last line in ~/.xinitrc. The second line is preferred if you want to log messages from i3 while it's running. To start a window manager manually from a console use
xinit /full/path/to/i3
Thank you,it seems worked. -
[solved] OpenGL apps in window do not obey window manager
Hello,
I have another X related problem, the first one resulted in downgrading my X
(see http://bbs.archlinux.org/viewtopic.php?id=44460 )
Now I am finally able to run both xv (video rendering) and dri (3d rendering), but
I have a problem, that when I run an opengl app in window (for example glxgears, but also game emulators and games in Wine), it does not move or resize when the window manager tells it to, e.g. when I move or resize the window. This makes 3D in window nearly unusable.
In my previous linux (suse) this worked normally; DRI was on and I was able to resize or move the 3D apps windows
card:
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01)
X version:
[danny@zdroj ~]$ X -version
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux zdroj 2.6.24-ARCH #1 SMP PREEMPT Wed Feb 27 01:15:32 CET 2008 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
xorg.conf:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "ServerFlags"
Option "IgnoreABI" "True"
Option "AIGLX" "False"
EndSection
Section "Extensions"
Option "XVideo" "enable"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/local"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/artwiz-fonts/"
EndSection
Section "Module"
Load "xtrap"
Load "dbe"
Load "GLcore"
Load "extmod"
Load "record"
Load "dri"
Load "glx"
Load "drm"
#Load "xv"
Load "freetype"
#Load "type1"
#Load "v4l"
#Load "drm"
#Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us,cz_qwerty"
Option "XkbModel" "pc104"
Option "XkbOptions" "grp:alt_shift_toggle,grp:switch,grp_led:scroll"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
DisplaySize 380 300 # mm
Identifier "Monitor0"
VendorName "BNQ"
ModelName "BenQ FP91G+"
### Comment all HorizSync and VertRefresh values to use DDC:
HorizSync 30.0 - 83.0
VertRefresh 43.0 - 76.0
Option "DPMS"
UseModes "Modes[0]"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "HWcursor" # [<bool>]
#Option "PciRetry" # [<bool>]
#Option "SyncOnGreen" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "Overlay" # [<str>]
#Option "MGASDRAM" # [<bool>]
#Option "ShadowFB" # [<bool>]
#Option "UseFBDev" # [<bool>]
#Option "ColorKey" # <i>
#Option "SetMclk" # <freq>
#Option "OverclockMem" # [<bool>]
#Option "VideoKey" # <i>
#Option "TexturedVideo" # [<bool>]
#Option "Int10" # [<bool>]
#Option "AGPMode" # <i>
#Option "AGPSize" # <i>
#Option "DRI" # [<bool>]
#Option "OldDmaInit" # [<bool>]
#Option "ForcePciDma" # [<bool>]
#Option "AccelMethod" # [<str>]
Identifier "Card0"
Driver "mga"
VendorName "Matrox Graphics, Inc."
BoardName "MGA G550 AGP"
BusID "PCI:1:0:0"
Option "HwCursor" "off" #protoze jinak tam neni
Option "DRI" "on"
Option "AGPMode" "4"
#Option "OldDmaInit" "true"
#Option "ShadowFB" "on" # 1
#Option "TexturedVideo" "on" # 2
#Option "VideoOverlay" "on"
#Option "AccelMethod" "EXA"
#Option "Overlay" "24,8"
#Option "NoAccel"
EndSection
Section "DRI"
Group "video"
Mode 0666
EndSection
Section "Modes"
Identifier "Modes[0]"
Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync
-vsync
ModeLine "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
EndSection
glxinfo:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_make_current_read,
GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig
OpenGL vendor string: VA Linux Systems Inc.
OpenGL renderer string: Mesa DRI G400 20061030 AGP 4x x86/MMX/SSE2
OpenGL version string: 1.2 Mesa 6.5.2
OpenGL extensions:
GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_texture_compression,
GL_ARB_texture_env_add, GL_ARB_texture_env_combine,
GL_ARB_texture_env_crossbar, GL_ARB_texture_rectangle,
GL_ARB_transpose_matrix, GL_ARB_vertex_program, GL_ARB_window_pos,
GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_logic_op, GL_EXT_clip_volume_hint,
GL_EXT_compiled_vertex_array, GL_EXT_copy_texture,
GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays,
GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal,
GL_EXT_secondary_color, GL_EXT_separate_specular_color,
GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D,
GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_object,
GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels,
GL_ATI_texture_env_combine3, GL_IBM_rasterpos_clip, GL_MESA_ycbcr_texture,
GL_MESA_window_pos, GL_NV_light_max_exponent, GL_NV_texture_rectangle,
GL_NV_texgen_reflection, GL_NV_vertex_program, GL_NV_vertex_program1_1,
GL_OES_read_format, GL_SGIS_generate_mipmap, GL_SGIS_texture_edge_clamp,
GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
0x23 16 tc 0 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 0 0 None
0x24 16 tc 0 16 0 r . . 5 6 5 0 0 16 0 0 0 0 0 0 0 None
0x25 16 tc 0 16 0 r y . 5 6 5 0 0 16 8 0 0 0 0 0 0 Slow
0x26 16 tc 0 16 0 r . . 5 6 5 0 0 16 8 0 0 0 0 0 0 Slow
0x27 16 tc 0 16 0 r y . 5 6 5 0 0 16 0 16 16 16 0 0 0 Slow
0x28 16 tc 0 16 0 r . . 5 6 5 0 0 16 0 16 16 16 0 0 0 Slow
0x29 16 tc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 Slow
0x2a 16 tc 0 16 0 r . . 5 6 5 0 0 16 8 16 16 16 0 0 0 Slow
0x2b 16 dc 0 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 0 0 None
0x2c 16 dc 0 16 0 r . . 5 6 5 0 0 16 0 0 0 0 0 0 0 None
0x2d 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 0 0 0 0 0 0 Slow
0x2e 16 dc 0 16 0 r . . 5 6 5 0 0 16 8 0 0 0 0 0 0 Slow
0x2f 16 dc 0 16 0 r y . 5 6 5 0 0 16 0 16 16 16 0 0 0 Slow
0x30 16 dc 0 16 0 r . . 5 6 5 0 0 16 0 16 16 16 0 0 0 Slow
0x31 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 Slow
0x32 16 dc 0 16 0 r . . 5 6 5 0 0 16 8 16 16 16 0 0 0 Slow
can anyone please help me?
Last edited by danielsoft (2008-03-04 16:22:32)solved with unofficial drivers http://forum.tuxx-home.at/viewtopic.php?t=153
-
Set Window Manager hints from Swing/AWT?
I was wondering if anyone knew of a way to set certain window manager hints, specifically to keep a window on the desktop (_NET_WM_STATE_BELOW) and out of the taskbar (_NET_WM_STATE_SKIP_TASKBAR). I've googled around but I haven't yet found anything useful. Anyone else have any ideas?
Sorry, I was referring to window manager hints ( http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#id2551694 ). To rephrase, I would like to position a window on the desktop instead of allowing other windows under it (such as the "keep below others" option in many window manager), to make something like a desktop widget. I've already looked in to using ab5k, but it seems to be dead now.
Sorry for any confusion. -
Windows 7 slow to boot after setting up windows backup to additional drive.
I have an issue with windows taking forever to boot after setting up Windows backup.
PC Setup:
2 Samsung SSD Mirrored for Hardware raid on (MOBO OS/Programs)
2 Seagate 4TB Mirrored for Hardware raid (Data storage)
1 Seagate 4tb HD used solely for Windows backup. (Have also tried with multiple other drives with same outcome.)
If I have all drives connected without setting up the Windows Backup, system will boot up in 37 seconds. As soon as I enable the backup to the additional drive, it kills the boot time. Brings boot time to over 2.5 mins. Brand new PC, clean
installation, no antivirus or any other software that could be slowing it down. If drive is just in PC as an extra drive there seems to be no issue, just as soon as I enable the Windows Backup to additional drive. Never noticed this issue on any other
PCLog booting process (set it in F8 menu).
Regards
Milos -
i have macbook pro 13.3 inch. I am installing window 7 in boot camp manager after copying file of window upto 67% it doesn't response and i had forcely shotdown my macbook. Now my macbook doesn't open and stop in black screen with cursor blinking. Now how could i open my macbook pro.
At startup hold down the Option/Alt key and from the screen that comes up select your OS X partition to start the computer from. Then use the Boot Camp Assistant app to Remove Windows and the partition you reated for it and it will Automatically place the space you allocated for the Windows install back into the OS X partition.
NOTE:
Do NOT use Disk Utility to erase the partition that was created for the Windows install. Use the Boot Camp Assistant app again to do that. -
[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? -
WADK components & setting used for power management with answer file for windows 8.1 ent
hello,
I have to deploy windows 8.1 ent device with MDT answer file related to power management with customized following settings:
High performances
sleep timeout settings
standby or sleep and hibernate setting
Enable critical battery task.
But don't know
1. how to manage power settings using answer file (WADK) for win8.1.
2. which OS Windows image component and setting used for power management in WADK.
Thanks
Richa KmThe way I do it with my task sequences (this works with MDT as well as SCCM) is to have an exported power plan using the POWERCFG -EXPORT command. I create a software package around the resulting *.POW file with a command do do an POWERCFG -IMPORT.
I then issue a POWERCFG -SETACTIVE command to the GUID of the *.POW file to enable that power scheme.
More information on the POWERCFG command can be found here:
https://technet.microsoft.com/en-us/library/cc748940%28v=ws.10%29.aspx
Hope that helps,
Darth.Mongo -
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) -
KDE Default Window Manager Setting File Location
I recently switched KDE to use Awesome instead of Kwin via the "Default Applications" configuration dialog. Unfortunately, using the same dialog to switch back to Kwin gives me a message stating that it can't start Kwin and it immediately reverts the setting back to Awesome.
I imagine somewhere under ~.kde4/share/config/ is a file that will allow me to select the window manager by hand, but I haven't been able to find it. Can someone point me in the right direction?That's what I would've expected too! It turns out it was in ksmserverrc
Maybe you are looking for
-
IPod detected by Windows but not by ipod apps; installation freezes
Hello As the installation CD felt out of the box I did not read the warning label that I first should install the drivers and then connect the ipod, probably this was a bad idea.. Now I cannot install the iPod nano software. The CD tries to detect th
-
I am using a windows 7 PC. Every time I try to update my Itune I am having a server error and I am not able to log in on my Icloud. I tried a network test a. below is the result: Microsoft Windows 7 Business Edition Service Pack 1 (Build 7601) Sony C
-
Transitions in Photoshop Elements 9
I'm using Photoshop Elements 9 to create a slideshow. I created a simple slideshow in Photoshop and then exported to Premiere Elements to do some additional editing and add audio. To some of the slides I've added text. However, the transitions don
-
I wrote this code to implement RANSAC (trying to find straight lines), but it seams that I have a problem with marking the line that I first found in order to exclude it and let the RANSAC to find the rest lines. Here is the code: public class RANSAC
-
How can i get that wallpaper picture in the new imac ad
The new Imac ad has this AMAZING picture of a multi-colored flower as it's wallpaper (maybe). Is that picture downloadable from Apple or is it part of an app/