System hangs after leaving any window manager rebuild xorg?

Just did a full system upgrade and everything is working fine except when I leave ANY window manager like fluxbox or gnome, the systems hangs and will not drop back to console, the screen just goes black with a white horizontal line about the size of a cursor at the top of the screen. I also start my window managers from the console with startx. Anyone else had this problem? And now X is just freezing at random, very random and not all that often. Should i just rebuild Xorg?
Last edited by archgenix (2010-06-09 08:09:19)

This is weird. It's like it shuts down different functions one by one like the scroll, mouse, keyboard and other stuff that is related to gnome. It doesn't freeze, it just shuts down some functions that make it impossible to use desktop environment and now I've tried to turn off Compiz, Emerald and using the Clearlook theme but still it's the same thing.
SanskritFritz wrote:Snicko, are you using nvidia? http://www.nvnews.net/vbulletin/showthr … ?p=2426750
Yes, I'm using Nvidia but its not the same error. My computer doesn't freeze.
Last edited by Snicko (2011-05-02 14:14:05)

Similar Messages

Lion 10.7.1 system hangs after reboot

Strange, I have just updated to 10.7.1 (via SW update) on my Macbook Pro and now the system does not boot. It restarted and now hangs since minutes with the spinning wheel on a grey screen. Anyone experienced this, too? Any solutions?
Thanks a lot.
Tom

http://jrause.com/blog/?p=165http://jrause.com/blog/?p=165
bighugewhaledork wrote:
Regarding the occasional system hang on reboot people are experiencing. I have two troubleshooting suggestions to help you get to the login screen, but aren't solutions to the problem of whatever is causing the system hang. 1) I find my hangs are usually solved by removing my USB devices from the 2 USB ports (via USB hubs) and rebooting. 2) Furthermore, if I boot into verbose mode (holding command+v right before the chime) (sometimes after removing the USB devices, sometimes not), that usually helps the boot process along, either due to just chance (I don't know why booting into verbose mode would help it surmount the initial hang, but it seems to work sometimes) or some other reason.
Good luck.
Yeah that better be one big fat good luck there, because that advice is not going to help anyone that is having this problem. Not one little bit. Some kind of magic that Verbose Mode casts will fix it? Uh, no. That would be a figment of your over-eager imagination, Verbose Mode doesn't change anythig. Oh and by the way, in order to get to this stage in the probelm, you would have had to use verbose mode to get the error message. I can only assume that you sir are the real troll here, because our friend above asked a question that is worth merit and consideration, given the compatibility disaster that Apple has on their hands. To call it a disaster is not in the least bit an exaggeration.
We're going to have to ignore This is not an "occassional system hang", this is a serious problem affecting my MacBook Pro 17" and my iMac 27"., and it occured on both of them for me after installing Lion Server.
My blog post tracking the issue is here:
http://jrause.com/blog/?p=165

System Hangs after kernel update

Hi Experts,
Client side, they did kernel upgrade in production system . After this upgrade , they are not able to execute any RFCs. Whenever they are executing RFCs , it keep on running continuously (hangs long time).. Not able to get any results.
Please guide me how to handle this problem.
Thanks
Silviya

Hi,
Thanks for your reply.Just forget about kernel upgrade.In my client production, they are trying to execute RFC "RFC_ABAP_INSTALL_AND_RUN",,but the system continuously hanging for one week. They are not able to do anything with RFC. Other ABAP normal programs are working fine.
They creating invoice by RFCs. Whenever they running this RFC , system gets hanging continuously. what may be the reason..and how to correct it .please guide me ASAP. I couldnt get content of sapnote 1151775. If you have sapnote 1151775 details , please give me.
Thanks a lot
Silviya

PPC G5 system hangs after Leopard Install

Well I had been monitoring things with the new OSx for awhile before installing. I had upgraded my Macbook Pro (Intel first Gen model) and my newer Intel MacMini with no issues. So after using both of these machines for quite awhile, and with the release of 10.5.2, I decided to upgrade my PPC G5 from Tiger to Leopard.
Everything seemed to go fine. I installed all possible updates and have used several apps with no problems, such as Adobe PS and Dreamweaver, etc. But now I am starting to notice a serious problem.
Every time my system either goes into Screensaver mode or sleep, when I try and bring it back it is frozen. All I get is the beachball and the only thing to do is a hard shut down with the power button. My system never did anything like this under Tiger.
Has anyone experienced a system hang like this?

Do you have any external drives (especially Maxtor or Maxtor OneTouch Drives)?
I know on Tiger I had this same problem and it turned out that there was a problem between the Mac's Firewire drivers and Maxtor OneTouch drives. Maxtor had a patch that fixed the problem on Tiger, but I'm not sure if the patch is needed also for Leopard. Not sure if Maxtor drive support is continuing since Seagate bought them.
I'm currently having a problem on Leopard with hangs (not specifically the same as yours). I'm wondering if it is again a problem with compatibility between Leopard and the Maxtor drives.

System Hangs after adding Storage :(

First dont jump on me for mentioning a 4800 this is storage related.
Solaris 8
Brocade 3850(SUN Branded)
SUN Samfs(4.2.8, running 5 months)
EMC Clarion(Old existing and always seen in config)
Infortend FC-SATA array(Newly added)
I have added some FC-SATA drives to my 4800s. The process of adding these drives was done by a 'cfgadm -c configure <Controller #>'. Following this the disks are seen, striped and shared with SAMFS. All is good at this point.
During reboot the systems hangs just after the boot message of "System is coming up". I think it is at the point of finding mount points and doing an 'fsck', but the system never completes(+45 minutes).
When I drop back to the original configuration prior to the 'cfgadm' the system then boots just fine, but I then need to do 'cfgadm -c .....' to see the drives and mount my SAMFS partitions.
Any ideas?

SimonM
The disks can be seen when I attach the storage with a 'cfgadm -c configure <controller #>' and the system up and running. After dynamicly attaching the storage I can create filesystems, use SAMFS to share the filesystem out, and all is good across all machines.
I only have an issue later in life when a reboot(hate for a panic) occurs. Some sunsolve/goggle'ing found some old document that were very dated that pointed to the path_to_inst and fiber not playing well.
I am not 100% sure that the system has hit the mount/fsck processes or not but it is the next sequence in the boot process. I know it is storage/config related because (1) adding the new disks is the only thing that changed on the system, (2) returning the OS back to its original configuration before the disks being added allows everything to boot fine. I was just looking for some pointer of where to begin troubleshooting.
I will keep everyone updated. Like I said I only get a couple of hours every month if I am lucky.

System hangs after Leopard installed

First of all, I am using a Mac to try to avoid having to deal with tech-y things like kernals, whatever they are! I had an iMac for years which finally started giving out on me, so on October 1 I bought a new fancy iMac with max memory and features. I was worried about the impending upgrade to Leopard but wasn't certain how long it would be before it actually came out since the release had been delayed before.
Well, the machine with 10.4.x ran like a charm, but I just HAD to be the first on my block to upgrade to Leopard. I did a basic install and things seemed fine for a few days. I was having some real issues with Parallels so finally uninstalled that, and things worked OK for a while. The last two days, though, the thing will suddenly freeze and it seems to happen more and more!
It is freezing in a funny way---the cursor will still move, but you can't click anything, you can't move any windows, it's like the cursor is separated from what's on the screen by an invisible shield. I cannot use ALT-COMMAND-ESC to try to shut anything down, nothing happens when I try. SO, I have to use the power button to power down and then restart.
This can happen when I am browsing with Safari or when I'm reading my email and it has happened when the darn thing is just sitting there (I will find the screen saver on, nothing responds, and I have to repower the system)
I have tried to reinstall Leopard using the archive options, and have installed all the updates that have been found by Software Update.
I am using Time Machine to send backup data to a 300GB external HD and thought that that might be causing these hangups, but have disconnected the hard drive and it still happens. (How can I tell Time Machine to stop doing it's thing?? Is it possible that it is doing this?)
It is occurring to me that I may need to do the "erase everything" kind of reinstall of Leopard, and this seems pretty scary!
Can I use my Time Machine backups to restore my files after I erase and reinstall, or do I need to erase the time machine stuff on the external HD and then use something like Backup to get my files back?
I would certainly like to try everything else before I do something drastic like erase and start over! Remember, I bought a Mac to try to avoid all the messes they talk about with WIndows!
Is there any way to reinstall 10.4? I don't recall a system disk coming with the computer, so I'm not sure how to do this, but I would be perfectly happy never using Leopard again---all these problems began when I first installed it.
Sorry about the lengthy message, I am trying to be complete about describing what I've got going on.
Jim

Well, guess I didn't put my question too succinctly, or no one felt like answering, but here's what I've found in the last two days.
I had decided to do a clean reinstall of 10.5 so I erased my external HD (that I had hooked up to Time Machine) and then transferred all my important stuff to it.
I then waited until I could set aside the required 4-5 hours to reinstall the OS, pull out my hair, swear, etc.
Well, whaddaya know---since disabling Time Machine I have not had a single freeze. It was freezing 2-3 times per HOUR, but none in last 48 hours.
I'm not the expert all the others here appear to be (and apparently that is a requirement to get a question answered) but I am going to see what happens before I go any further. The day I give Time Machine another try will be a very, very cold day in August.

T430u hangs after upgrading to Windows 8.1

Hi, after upgrading to Windows 8.1 my Lenovo T430u started to freeze on some applications (specially ms Excel 2013). Sometimes the network connection was lost.
I did a clean install of Windows 8.0 and after downloading and reinstalling all drivers everything was working perfectly. Until I upgraded to Windows 8.1 again.
Now I'm having the exact same issues than I had when I first upgraded to Windows 8.1. I have installed all OS patches as suggested by Windows Update.
Is there any Windows 8.1 OS image that I can download from Lenovo that is tested for my machine? Or should I go back and reinstall Windows 8.0 and live with it?
Thanks
Adrián

I have the same problem - my data had better not be gone! Why won't Apple address this problem?

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)

System hangs after launching P2P

Hi,
I have just installed a K7N2 Delta MB with a 2500+ Athlon and a 3200 DDR (PQI) of 512 Mo. My OS is WinXP SP1.
Everything works very fine until I load a P2P (emule).
I had not this problem with my defunct Elite MB (with a 1800 Athlon and a 2100 DDR).
I have an ADSL connection via an ECI USB modem.
WinXP and the MB Bios and drivers are updated (using Win update and MSI Live monitor). I have also updated the VIA chipsets with VIAHyperion4in1446vp6 and updated the NVidia drivers/programs SINCE the USB host controller is an NVIDIA one (therefore the VIA USB 1.1 cannot be installed)
I have uninstalled/re-installed all my USB ports and also closed the LPT port.
The ADSL modem is connected to an hub while I have connected my optical mouse to a separate USB port (since MSI writes that the mouse consumes a lot of energy).
I have aloso enabled the USB in the Bios and even the KB USB whereas I do not have an USB KB (I had the same problem when the KB USB was not enabled).
The BIOS indicates an 100 FSB.
What should I do?
Thank you in advance.
(pardon my approximate English and technical languages).

Sharp,
I have re-installed WinXP, installed the Nvidia updates (and the MSI and Win XP ones) and installed a more recent and more efficient ADSL connection driver.
However, eMule hangs after less than 1 minute with a 166 mHz as well as with a 133 mHz FSB (this means: I cannot close it with the Task Manager and I am obliged to re-boot WinXP.
Moreover, the CPU temperature climbs quickly to 60°C at 166 mHz.
I know that I could solve the temperature problem by installing a new fan. However, I am not certain that this would solve the hanging one (although one may think that it's the temperature that leads to the hanging.
I have discovered in the eMule forum that other people with other configurations encounter the same difficulties as me. Therefore, their solutions will probably not be found on this site.
Thank you for your availability.

System hang after key in YF98 (Report for sales tax payable)

Hi all,
do u know wat is the problem of sys hang? i already terminate the transaction code, but sys hang also........
Thanks for helping

Dear V.Krishnan ,
I already told BASIS to restart the server, but they reject to restart the server cos they worry later they cannot up the server.
They keep asking me debug the program, but the problem is the sys hang after i key in the transaction code, i cant do nothing after that. In development server, the sys is OK after i enter the transaction code. Can u tell me wat to do now?
regards;
jee

Add ons manager hangs after doing a Windows 7 System Restore.

Firefox was restored from Version 23 back to Version 20. Now, none of my Extensions or PlugIns show up and when I click on "Get Add Ons" I just get a"Loading" and it hangs. I tried deleting the extension.ini and extensions.sqlite files and restarting Firefox but that did not work. It seems like the add ons and extensions are there, but just not accessible through the Add On Manager.

Note that using System Restore can cause your Firefox installation to get corrupted because not all files are restored (only files in a white-list), so be cautious with using System Restore.
*You may lose data in the Firefox profile folder like .js and .ini files.
*You may need to (re)install software that was affected.
Do a clean reinstall and delete the Firefox program folder before (re)installing a fresh copy of the current Firefox release.
Download a fresh Firefox copy and save the file to the desktop.
*Firefox 23.0: http://www.mozilla.org/en-US/firefox/all.html
Uninstall your current Firefox version, if possible, to cleanup the Windows registry and settings in security software.
*Do NOT remove personal data when you uninstall your current Firefox version, because all profile folders will be removed and you lose personal data like bookmarks and passwords from profiles of other Firefox versions.
Remove the Firefox program folder before installing that newly downloaded copy of the Firefox installer.
*(32 bit Windows) "C:\Program Files\Mozilla Firefox\"
*(64 bit Windows) "C:\Program Files (x86)\Mozilla Firefox\"
*It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
*http://kb.mozillazine.org/Uninstalling_Firefox
Your bookmarks and other personal data are stored in the Firefox profile folder and won't be affected by an uninstall and (re)install, but make sure that "remove personal data" is NOT selected when you uninstall Firefox.
If you keep having problems then also create a new profile.
*http://kb.mozillazine.org/Profile_folder_-_Firefox
*http://kb.mozillazine.org/Profile_backup
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall

System hangs running Server Backup - Windows Server 2012 R2 Essentials

I ran through the Backup Wizard, selected the System, OS, and my Data drives to backup. total output is probably about 400-500GB of data to be snapshot and backed up. It's set to automatically backup daily at 9:00pm, but upon the first backup it just sits
there. I figured I'd let it ride until the next day since I've seen backups take a couple hours before.
Well, It's more than 12 hours since it started the process, and I cannot access my server. It doesn't wake the screen, CTRL-Alt-Del doesn't do anything, and I can't remote in with RDP.
Any advice? I haven't shut it down or forced a reboot yet.

The server hangs when the backup starts, and I cannot see any error message other than after I hard reboot and see the error popup on reboot due to unscheduled shut down. Also, there is an error log in the Windows\Logs\WindowsServerBackup directory. The
log files are empty, though. They are named according to date.
e.g. "Backup_Error-07-01-2014_02-00-06"
I have reboot the system and the same happens when I try to backup again. I do have data in the backup HDD, as I have since disabled Server Backup. After disabling server backup, the designated drive is now mounted and I can see the log file created in the
only backup folder on it.
"Backup of volume C: has failed. The operation failed due to a device error encountered with either the source or the destination. If the source or destination volume is on a disk, run CHKDSK /R on the source or destination volume, and
then retry the operation."
"Backup of volume D: has failed. Server execution failed"
All drives are new, and CHKDSK /R doesn't resolve anything in terms of allowing backup to proceed.
I should also note that the C: HDD is a 512GB SSD with only 36GB of data on it including the OS. D: is a 2TB HDD with only 18GB of data on it. SQL server is active during the backup process, but even ending the SQL processes doesn't change the backup outcome.
Server Backup ends up hanging regardless of everything I've tried.
I imagine Server Backup would kill any processes that may prevent it from accessing data to snapshot/backup, no?
I will add the backup HDD does have 3 files in the F:\WindowsImageBackup\NESServer\Backup 2014-01-07 020006 directory.
@ 9:02pm 1/6/2014 (9:00pm was the scheduled start), a 2,550,784KB file
@ 12:45am 1/7/2014, a 11,264KB file
@ 10:49am 1/7/2014, a 272,384KB file
All three of those files were created from the same backup process. However, checking the Server Manager/Server Backup Tool, that drive doesn't qualify as containing any backup files. "The backup location does not contain any backup. Specify another
backup location."

Importing HDV Footage: System Hang After Indexing Finished

Running Premiere CS6 with updates.
Generally solid application, but the first time I crashed it this year, was during import of HDV footage. After the footage indexes, and the thumbnail pic changes from 'media pending' to the actual footage frame, the mouse pointer freezes. The keyboard is frozen too. Can't even bring up the Task Manager in Windows 7 64. Is HDV even supported anymore? Maybe it's an invalid format? The file plays fine in VLC, so I don't think it's corrupted. But egads, I've never seen an app hang Windows 7 before!

I've confirmed that the hang does not happen with Canon HV20 footage, only Sony HVR-V1U footage. Any footage shot by that camera will hang not only Premiere, but the entire OS. I have to power down the machine to regain control.
What's so different about Sony's implementation of HDV that it is incompatible with Premiere?

Portege M800 - System hangs after fingerprint login

I just got my Portege M800 weeks ago and frankly speaking, this model has been giving me much trouble. Earlier it is the heat problem at the palm rest and there is no solution to it.
Now I am facing another issue with the fingerprint login. I am running on WinXP. I set the system to be locked after 5 minutes idle. So normally after 5 minutes idle, the system will require me to scan my fingerprint to unlock the Windows. But there are times that, after scanning my fingerprint and successfully matched, the screen will just be blank (only showing the desktop wallpaper). No desktop icons, no windows task bar and nothing. Press Ctrl+Alt+Del bring up nothing and no response even any key press. I tried to bring the system to hibernate by press the power button once also bring no response.
So I finally have to press and hold the power button to hard-reset the laptop.
Anybody can help or give any clue what was happening? Thanks!

I found the Fingerprint software on the Toshiba European driver page.
At this time you can find a 7.10.1.2 version for Vista 32bit and Win XP
Check this!

System hang after clicking "Run" to launch "SBO_Welcome.hta"

Hi,
My client encounters a pop up window "Open File - Security Warning" upon logging into SAP.
It is a message to run "SBO_Welcome.hta" which is located on "
SERVER\B1_SHR\Help\EN".
When the "Run" button is clicked to launch the above mentioned file, the system will hang.
Also, the error below will be displayed when we force shut down the above pop up window from Task Manager.
Error:[NCM Main].[Main] The RPC server is unavailable. (Exception from HRESULT: 0x8007068A)
The above issue is encountered on a specific workstation only.
Kindly suggest if anyone knows how to resolve this.
Thank you.
Yadana

Hi,
Bala is correct. this installation is corrupt. Uninstall and install with Full administrator rights and doesr the use profile have acess to the shared folders like B1_SHR, check for the firewall setting .
Regards,
Rakesh N

System hangs after leaving any window manager rebuild xorg?

Similar Messages

Maybe you are looking for