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)

Similar Messages

  • 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)

  • Adobe Reader crashes a few seconds or minutes after start. After uninstalling I cannot manage to install it anymore

    Hello. Since several days Adobe Reader XI crashes a few minutes or seconds after start. I tried to get an update but the computer does not react after the click on the setup-file. Finally I uninstalled Adobe Reader and Flash Player in order to install it new. The download from the Adobe Page worked but the setup does not start so I cannot install it. I also tried to it with Reader X but it does not work either.
    I have a Windows 8.1 notebook, Mozilla Firefox.
    Would be nice if anyone could give me some advice!

    Uninstall the current Reader using http://labs.adobe.com/downloads/acrobatcleaner.html
    then reinstall with the offline installer from http://get.adobe.com/reader/enterprise/
    If the crash still occurs; try disabling Protected Mode in Adobe Reader [Edit | Preferences | Security (Enhanced)].

  • Can't uninstall Lenovo Power Manager in Windows 8 - upgraded from Windows 7

    Hi all, I recently purchased a Lenovo X230. It was preloaded with Windows 7 Home Premium. I upgraded this system to Windows 8 Pro without any problems.
    I noticed that Windows 8 Pro has some issues with the Lenovo Power Manager, which after perusing this forum seems to be pretty incompatible with Windows 8. I am trying to uninstall the Power Manager in the Control Panel, but I can't find the application to install. I only see an option to uninstall the Lenovo Power Management Driver. Does anyone know how I can uninstall the entire Lenovo Power Manager from my system?

    Backstory: I installed the Power Manager on a clean installation of Windows 8 by setting it to Windows 7 Compatibility Mode.  It seemed to be working swimmingly, until the next day when I tried to use it and discovered that it would always crash on start-up.  Unfortunate.  I naively attempted to correct this problem by uninstalling and reinstalling the application.  Strangely, I was able to successfully uninstall the program using the Add/Remove Programs Control Panel and then reinstall the program.  But, despite the reinstallation the problem persisted and I tried to uninstall the program again.  It would not uninstall, claiming the installer wasn't compatible with my system.
    Fix: Run "C:\Program Files (x86)\InstallShield Installation Information\{DAC01CEE-5BAE-42D5-81FC-B687E84E8405}\Setup.exe" -l0x9 -AddRemove from an administrative command prompt.  This should completely remove Power Manager and it's entry in the Add/Remove Programs console.  The GUID may be different if you were not using the most recent version of Power Manager, I installed 6.36.  The additional power plans that it originally installed are still in the Windows Power control panel.
    I am still wrestling with the Power Manager to get it working somewhat reliably on Windows 8.  I am very disappointed that this level of effort is required on a new system that is Windows 8 compliant.

  • 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

  • After updating to Windows 8.1 the Webcam in my Inspiron is gone and Imaging devices missing in Device Manager

    my webcam in my Dell Inspiron 3521 was working fine with Windows 8.  After updating to Windows 8.1 the Webcam in my computer is gone and the 'Imaging devices' is  missing in the Device Manager.  how can I get the Webcam back? 
    thank you very much.

    I don't see anything specific to your webcam issue but there are a number of Windows 8.1 related drivers listed on the Support site.
    http://www.dell.com/support/home/us/en/04/product-support/product/inspiron-15-3521/drivers
    The Dell Update utility will recommend drivers that are needed specific to your model.
    http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=860YD&fileId=3374847033&osCode=WB64A&productCode=inspiron-15-3521&languageCode=EN&categoryId=AP
    Good luck!
    bill
    Regards, Bill Moore @BMooreAtDell

  • Windows 7 startup error after uninstall of Photosmart 6510

    After uninstalling Photosmart 6510 and software, get error message: "There was a problem starting C:\Program Files\HP\HP Photosmart 6510 series\bin\HPStatusBL.dll" when Windows 7 starts up.

    Sounds like the software was not completely removed (or atleast Windows still is looking for something). Microsoft make a tool that should be able to help, it is called FixIt. Click the link below for more details:
    http://support.microsoft.com/mats/Program_Install_and_Uninstall/
    If I have helped in any way, just click the Kudos star on the left. Also, if your issue has been resolved, don't forget to select Accept as Solution

  • TS1369 My computer (Win 7) recognises my ipod but when Itunes is automatically started the ipod is removed from "my Computer" and is not recognised in itunes, my device manager states he device is being "uninstalled by window" error 21, what is happpening

    My computer (Win 7) recognises my ipod but when Itunes is automatically started the ipod is removed from "my Computer" and is not recognised in itunes, my device manager states he device is being "uninstalled by window" error 21, what is happpening.

    Are you plugging the iPod into a high powered USB 2.0 port on the back of your PC? Have you tried a different USB cable?
    What happens if you try to reset the device with it still connected to the PC?
    How to reset iPod
    Has this iPod ever worked on this PC or is this the first time you have time you have tried connecting it?
    Have you carefully worked through each and every single suggestion in this Apple support document?
    iPod not recognized in 'My Computer' and in iTunes for Windows
    B-rock

  • Error when opening itunes : iTunes has stopped working ''A problem caused the program to stop working correctly''. When I repaired damaged files the problem still exists and also after uninstalling and redownloading and installing itunes. I have windows 8

    Error when opening iTunes : iTunes has stopped working '' A problem caused the program to stop working correctly''.
    When I repaired damaged files the problem still exists and also after uninstalling, redownloading and reinstalling iTunes.
    My pc is working with windos 8.
    Is there a solution?

    Hey there Rodney274,
    It sounds like you are getting an error from iTunes when you launch it. I would try the troubleshooting in this article named:
    iTunes for Windows Vista, Windows 7, or Windows 8: Fix unexpected quits or launch issues
    http://support.apple.com/kb/ts1717
    Start with troubleshooting for 3rd party plug ins section, then the rest of the article if needed:
    Start iTunes in Safe Mode
    Open iTunes in Safe Mode to isolate any interference from plug-ins or scripts not manufactured by Apple.
    Hold down Shift–Control while opening iTunes. You should see a dialog that says "iTunes is running in safe mode" before iTunes finishes starting up.
    Click Continue.
    See if the issue you're experiencing persists in Safe Mode.
    If you have the same issue while iTunes is in Safe Mode, proceed to the "Create a new user account" section. If you don't experience the same issue, follow these steps to remove third-party plug-ins.
    Thank you for using Apple Support Communities.
    Take care,
    Sterling

  • Can't connect to the Hyper-V manager after upgrading to Windows Hyper-V 2012 R2

    I have some Hyper-V server based on the free version (Windows Hyper-V 2012). I want to upgrade to the new version (Windows Hyper-V 2012 R2). So I begin to test it with
    an already working server (aka I was able to totally manager the server remotely without problem) and so upgrade it to the R2.
    After the upgrade, remote management and Hyper-V manager does not work anymore. So I redo my usual configuration steps (enable remote management, open firewall, uses
    latest hvremote.wsf, etc.). I was able to regain access to Computer Manager but not the Hyper-V manager which still can't connect at all. I can't access the Task Scheduler too without having a lot of XML error like "The task XML contains a value which
    is incorrectly formatted or out of range" (see below for screenshot).
    Is there a new step to do to be able to manage Hyper-V 2012 R2 from a Windows 7 computer?
    It's not a network problem as I can access RDP and MMC Computer Manager.
    To be sure the problem is coming from the R2, I have taken an old computer, install Windows Hyper-V 2012, do my usual configuration step, and
    tada: it works perfectly. I can access the Hyper-V manager from my client.
    Technical details:
    - Client is a Windows 7 SP1 x64 English member of a domain with latest RSAT (Windows6.1-KB958830-x64-RefreshPkg.msu).
    - Servers are in a workgroup (not a domain's member). And no, I can't add them to the same domain as the client.

    HI,
    Can we upgrade HyperV 2012 to hyper v 2012 R2.
    Thanks
    Atul

  • Adobe reader shows a horizontal empty window in OSX 10.9.3 after uninstalling Acrobat 8. How to get rid of it?

    Adobe reader shows a horizontal empty window in OSX 10.9.3 after uninstalling Acrobat 8. How to get rid of it?

    Macintosh HD > Library > Internet Plug-ins
    Look for these two files.
    AdobePDFViewerNPAPI.plugin
    AdobePDFViewer.plugin
    Right click on those and select “Move To Trash”.
    Restart the computer.

  • Upgrade broke window manager :(

    Hi,
    I had installed xfce 4.8 with liquorix kernel, everything was working smoothly until i got notification about some packages available for upgrade which also included linux kernel (though not sure if it was liquorix or stock kernel that came with arch). I upgraded and on reboot found everything behaving weirdly, no border for any window, also minimize, maximize, close buttons were missing. Mouse cursor had turned into a black x. When i launched terminal it mentioned window manager was not found.
    Can anyone please help me in reverting back to my old desktop session or how can i fix these issues?
    Any help is highly appreciated as my desktop is broke :-'(
    Thanks.

    @Murray_B - I did have xfce working fine until i upgraded and that seemed to have borked something on xfce, since lxde & e17 works fine.
    I usually start xfce with this command -> exec ck-launch-session dbus-launch --sh-syntax --exit-with-session startxfce4
    @stqn - will try your suggestion, however not sure if i can boot into the normal Arch kernel as i had installed liquorix kernel since the original one gave me kernel panic issues quite often and this is how my boot dir look like -
    -rw-r--r-- 1 root root 2038064 Jan 29 14:42 vmlinuz26.orig
    -rw-r--r-- 1 root root 1687004 Feb  5 09:43 kernel26.img.orig
    -rw-r--r-- 1 root root 2852224 Feb 16 21:58 vmlinuz26-lqx
    -rw-r--r-- 1 root root 1435139 Feb 16 21:58 System.map26-lqx
    -rw-r--r-- 1 root root 8501861 Feb 16 22:07 kernel26-lqx-fallback.img
    lrwxrwxrwx 1 root root      16 Feb 16 22:10 kernel26.img.priorLink -> kernel26-lqx.img
    -rw-r--r-- 1 root root 2039392 Feb 18 12:00 vmlinuz26
    -rw-r--r-- 1 root root 1156042 Feb 18 12:00 System.map26
    -rw-r--r-- 1 root root 1687004 Feb 23 20:38 kernel26-lqx.img
    -rw-r--r-- 1 root root 8362292 Feb 23 20:39 kernel26-fallback.img
    lrwxrwxrwx 1 root root      21 Feb 23 21:07 kernel26.img -> kernel26-fallback.img
    I can try copying *.orig back and try to load through them, let me if that works fine.
    Also in E17 when i open up settings->settings panel all i get is a big window spanning the entire screen with just a close button, all other options are not available :-(. Any idea what the issue could be?
    Thanks for your suggestions.

  • After uninstalling/installing itunes  I get this  window   16 bit MS-DOS Subsystem  The NTVDM CPU has encountered an illegal instruction CS:05aa IP:0480 OP: 6300 72006f Choose close to terminate. Neither ignore or close works

    After uninstalling/installing itunes ( there was a problem with an upgrade) the following window appears on my account page
    16 MS-DOS Subsystem
    The NTVDM CPU has encountered an illegal instruction CS:05aa IP: 0480 OP:6300 72006f Choose close to terminate application. Neither close or ignore works. I don't know where to turn for help I'm using Windows 7. Thx

    Hi there,
    I am also experiencing this problem, but with 1.4.2_06. Last week (late Jan 2005) the dynamic versioning was working fine, downloading and installing the latest version of Java as required.
    However now (early Feb 2005), I am finding that after downloading the latest version of Java and beginning the install, I am getting this error.
    I was hoping that you may have heard of a cause or solution for this problem?
    Many thanks

  • After uninstalling iTunes and re-installing, I cannot download the update. I have Windows Vista.

    After uninstalling iTunes and re-installing, I cannot download the update. I have Windows Vista. Should I un-install again, and if so, where are the instructions for windows vista?

    Have you tried to use another browser?
    This may help you out -> iTunes: Downloading iTunes for Windows using Internet Explorer

  • Can I still uninstall any windows updates after clean up the winsxs folder by dism on Win2008 R2 SP1?

    Hi,
    Just a general question about Dism, does the cmd below only focus on serivce pack clearn up or I wont able to uninstall any windows updates at all after the clean up?
    dism.exe /online /cleanup-image /spsuperseded
    Regards
    Anders

    Hi,
    The service pack cannot be uninstalled after this command is completed.
    Clean Up the WinSxS Folder
    http://technet.microsoft.com/en-us/library/dn251565.aspx
    How to reclaim space after applying Windows 7/2008 R2 Service Pack 1
    http://blogs.technet.com/b/joscon/archive/2011/02/15/how-to-reclaim-space-after-applying-service-pack-1.aspx
    Hope this helps.

Maybe you are looking for

  • How to manipulate the recipient adress of a notification mail?

    Hi, when a task is assigned to a user, LC can send nice notification eMails. Meanwhile the content (mail body and subject) can be freely formatted through custom eMail templates. I need exactly this but in addition to that, I would need to change the

  • Saving a PowerPoint Presentation as a pdf from With Outlook Code

    I'm trying to write a macro in Outlook that will open a Powerpoint Presentation (that part works) then save it as a pdf.  The code I've seen does not seem to work when running the code from Outlook.  Here's what I've got so far, all the commented lin

  • Best Way to migrate Planning application from 11.1.1.3 to 11.1.2.2

    Hello Gurus, What is the best way to move or upgrade the planning applications from EPM 11.1.1.3 to EPM 11.1.2.2 ? Is there an option to use LCM to move the planning application by exporting it from EPM 11.1.1.3 and then importing it in EPM 11.1.2.2

  • Getting special character while saving adobe form from portal

    Hi All, I am getting Special character while saving adobe form. I am using webdynpro java application, in which I am using download file UI element.We are facing this issue after support packs were implemented in staging system. Kindly advise. Regard

  • Can't open document in KM

    Hi, I've created a document in KM (in EP7) with a Web Dynpro application using the Java KM API. No exceptions are thrown while creating the content. The document is shown in the portal (Content administration - KM content). I can view the details of