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.

Similar Messages

  • Fingerprint upgrade broke Password Manager

    On my SL510, I let Lenovo “ThinkVantage System Update” load “Lenovo Fingerprint software for Windows 7 64-bit 5.9.4.6882”.
    Now the Password Manager/Password Vault says   “The requested operation requires fingerprint authentication, but the device is not installed.  Please make sure the device is connected and retry the operation”.
    Brilliant.
    The system logon process uses the fingerprint reader just fine, so it is “there”.  How do I update the PM to see it?
    Thanks.

    was not thinking when I hastily made my ID name. I do not work for Lenovo though I can now see it might look like/imply that with my goofed up ID.

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

  • Huge ntuser.dat.LOG1 since upgrade to Windows 8.1 prohibits roaming of user profile

    Hello,
    a few days ago my PC (part of our domain) first started to have problems with my user profile. Our domain uses roaming profiles with a size limit of 30MB. My user.dat has a size of 12.5MB. Up to now this did not cause any problems (and does not cause any for
    most users of our domain having a user.dat of similar size). However, after upgrading to Windows 8.1 I repeadly have problems with my profile exceeding its maximum size. After checking my profile, I found a ntuser.dat.LOG1 with 12,5MB in size and a ntuser.dat.LOG2
    of 2MB. As far as I know these files are used to store temporary transactions for the user.dat. But why are they this large? Together they almost completely fill the profile. As an interesting side node the last modification of ntuser.dat.LOG1 dates back more
    then seven days.
    What is further puzzling me: ntuser.dat.LOG1 and ntuser.dat.LOG2 are not synchronized with the roaming profile on the server. At least they are not on the server. However there used to be much smaller versions of these files which could have been transfered
    before the profile size exceeded its limit. Since these file seem not to be part of the roaming part of the profile, they should not count for the roaming profile size. However, they definitely do. Neglecting the registry files the largest file in my profile
    is less than 500kb and there are very few files of this size. I checked locally as well as on our server.
    Deleting the local profile and starting fresh using the roaming profile from our server does work for a day or two but then I run into the same problem. Especially, loosing all local profile data is inconvenient. I could start a new with a completely new
    profile, but I am not convinced that it is a profile issue. In our organisation my computer is one of the first to move to Windows 8.1. Since my profile worked without problems for years now, I am worried that I ran into a Windows 8.1 issue. As users normally
    start to complain about a roaming profile not synchronizing only after their local copy broke, I'd like to make sure that this is a isolated issue.
    Anyone else experiencing similar issues? Any hint on how to solve the problem?
    Regards,
    Oliver

    No, I did not find a solution. However, we moved away from roaming profiles and rely on folder redirection only. That works for us. Since we can redirect the most important folders there is no more need for roaming profiles (at least in our case).

  • Oracle upgrade in Solution Manager 10g to 11g

    Dear Expert team ,
    Our Solution Manager is running  in Windows 2003  with oracle 10g .
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Prod
    PL/SQL Release 10.2.0.2.0 - Production
    CORE    10.2.0.2.0      Production
    TNS for 32-bit Windows: Version 10.2.0.2.0 - Production
    NLSRTL Version 10.2.0.2.0 - Production
    SQL>
    Now I want to upgrade my Solution Manager 10 g to 11g .
    what oracle component  should I download  and how to upgrade 10.2.0.2.0  to  11.2.0.3.0.
    Please suggest.
    Regards
    Pooja

    Hi
    The upgrade is possible as stated in the here under note.
    Previous version (v15) of that note was even a bit more clear it is possible but version 10.2.0.4 is preferred.
    Direct upgrade from 10.2.0.2 should not be a problem, as it is even possible to have a direct upgrade from 9.2.0.8 to 11.2.0.4.
    1431793 - Oracle 11.2.0: Upgrade Scripts
    A database < 9.2.0.8 must be upgraded to 9.2.0.8 before it can be upgraded directly to 11.2.0.4.
    You should consider jumping directly to 11.2.0.4 that is the latest 11g version and the only one that will have a long term support.
    Regards
    1431797 - Oracle 11.2.0: Troubleshooting the Database Upgrade
    For a database upgrade from 10.2. to 11.2 the minimum release is 10.2.0.2. This release is not supported any more.
    1431797 - Oracle 11.2.0: Troubleshooting the Database Upgrade v15
    We strongly recommend a minimum release 10.2.0.4 for the following reasons:
    a) All SAP internal database upgrade tests have been performed with
    release 10.2.0.4. This upgrade path has been very well tested and
    is documented in the SAP Database Upgrade Guide for Oracle Release
    11.2.
    b) Oracle Database Release 10.2.0.2 is not supported any more.

  • Keyboard wireless key not working after upgrading to windows 8.1

    Hello,
    I am having hp pavilion dv6-6165tx notebook, where keyboard having a wireless button that turns ON and OFF all wireless devices, After upgrading to windows 8.1, HP Connection Manager is not getting installed, as well as Key is not working, key color turns red and white but no action is performed.
    Kindly suggest me some solution.
    Note: HP Doesn't provide drivers for windows 8/8.1 ONLY WINDOWS 7 for hp pavilion dv6-6165tx.
    Thanks.

    Hi @Jayesh_Bhadja ,
    Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion dv6-6165tx Notebook and the Wireless keyboard not working correctly. Here is a link to troubleshoot the keyboard.
    The HP Connection Manager is something that is for Windows 7 not Windows 8.1. I would uninstall this from your Notebook.  Here is a link to the HP Support Assistant if you need it. Just download and run the application and it will help with the software and drivers on your system that need updating. It has a troubleshooting tool in this.
    Make sure all your updates have been completed. I would try restarting my Notebook a few times.
    If that does not help I would uninstall the keyboard from the Device manager.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • Doly Audio driver cannot start after upgrading to Windows 8.1

    Upgrade to Windows 8.1 went flawlessly, but when I restart I get this message:
    I can't find any reference to Dolby Theater or Audio in any app or Device management.
    I can't find any drivers for Windows 8 64 bit  on the Lenovo site either.
    Can anyone help with this?
    Solved!
    Go to Solution.

    There is a possible solution in the following thread;
    http://forums.lenovo.com/t5/General-Discussion/Dolby-Home-Theater-v4-for-most-Lenovo-Laptops/m-p/126...
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • Ethernet LAN not working after upgrading to windows 8.1

    After upgrading from Windows 8 to 8.1, my Ethernet LAN is no longer working. Wireless LAN connectivity is OK. I have run the HP Support Assistant and downloaded the drivers for 8.1. Hovever, I do not see a 8.1 driver listed for the Ethernet LAN.

    You're very welcome. See if the recovery manager still works so you can roll back to W8. Please read this guide for how to use it. http://support.hp.com/us-en/document/c03489643 If it doesn't then you will have to order a set of recovery disks from HP, or you can install this plain W8 OEM software this guy has posted on a link. Lots of folks have used it successfully, which is why I posted it. https://docs.google.com/file/d/0B0W9PBigPy94aVJWSndyTFNFMzg/edit?pli=1 Then use this tool to make the iso file bootable to a DVD or 4+ GB USB flash drive. http://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool Yes, that really stinks why you and I could not upgrade without an issue. I disabled about 5 or 6 devices in the device manager and the code 12 would not go away. I have no clue why the PC works fine on W8 but not on W8.1. My notebook is a few years older than yours and it worked fine on W8.1 but not on W10. Go figure...

  • Lost External RAID 5 after upgrading to Windows 8.1

    I have a Proavio EB4FR External RAID 5 connected through the eSATA port. It worked with my Windows 7 Pro and Windows 8 Pro no problem, tonight I've upgraded to Windows 8.1. I can no longer see the RAID 5 drive.
    It is detected as an "Other" device with question mark. Cannot see it in Disk Management at all.
    Proavio is very bad in returning back to customers so I'm not expecting any response back from them, I was hoping that somebody here can suggest some good ideas that I can chase...
    Thanks in advance,
    Akin

    Hi Kate,
    Copying below from setupapi.dev.log;
    >>>  [Device Uninstall (Device Manager) - SCSI\DISK&VEN_&PROD_EXTERNALRAID\4&2F621F8A&0&050000]
    >>>  Section start 2014/02/02 12:54:07.432
          cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc
         dvi: {DIF_REMOVE} 12:54:07.447
         dvi:      No class installer for 'ExternalRAID'
         dvi:      No CoInstallers found
         dvi:      Default installer: Enter 12:54:07.447
         dvi:           {Remove DEVICE}
         dvi:                InstanceID = 'SCSI\DISK&VEN_&PROD_EXTERNALRAID\4&2F621F8A&0&050000'
         dvi:                Query-and-Remove succeeded
         dvi:           {Remove DEVICE exit (0x00000000)}
         dvi:      Default installer: Exit
         dvi: {DIF_REMOVE - exit(0x00000000)} 12:54:07.463
    <<<  Section end 2014/02/02 12:54:07.463
    <<<  [Exit status: SUCCESS]
    External drive still working when I boot from my Windows 7 drive. 
    Thanks a lot for looking into this...

  • Yoga 11 no wifi after upgrading to Windows 8.1

    I have a Yoga 11 which I have just upgraded to Windows 8.1.  I now have no wifi on the Yoga.  When I go to device manager and check "Broadcom 802.11bgn Wireless SDIO Adapter" it says "This device cannot start (Code 10)".
    Any ideas?  I'm about to toss this thing out the window.  I've had wifi connectivity issues since I bought it, and this update seems to have killed it.

    Salheureux, welcome to the forum.
    You should go into the Control Panel / Sound to assure that your sound device is set to Default.  Also, right click on the speaker icon in the Taskbar / Playback devices and check that your speakers are displayed.
    Please click the "Thumbs Up+ button" if I have helped you and click "Accept as Solution" if your problem is solved.
    Signature:
    HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
    HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
    HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
    HP Photosmart 7520 AIO
    ++++++++++++++++++
    **Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
    Intelligence is God given; Wisdom is the sum of our mistakes!
    I am not an HP employee.

  • U410 touch WiFi issues after upgrading to windows 8.1

    Hi all,
    I have a U410 touch and yesterday I upgraded to windows 8.1
    I have major WiFi issues.
    connection drops after a few minutes giving limited. troblesshooting resets the adapter saying ''the default gateway is not accessible '' is fixed. But after a few minutes the problem comes back. and it goes like this forever.
    I have the Intel Centrino N-2230 and I installed the driver I found here (15.10.3.2).
    I''ve tried to uncheck the power management option but the problem is still there.
    I also have other issues with the dolby system (I see others have the same problem )and my touch screen is not working.
    any help will be greatly appreciated
    thanks!

    Hi-
    I am also running into the same issue with my Lenovo U410 and it is really frustrating. I also have Centrino Wireless chip with driver version 15.10.3.2 and I have windows 8.1
    I bought the laptop from Costco and was having similar issues. I sent it back to Costco Concierge who apparently replaced the wireless chipset on this laptop but now I am getting this issue.
    Any help will be greatly appreciated.

  • Wifi problem of G560 after upgrading to windows 8.1

    Hi,
    I have a lenovo G560. After upgrading from windows 8 to windows 8.1, I cannot connect to wifi. I was wondering if someon else has the same problem.

    hi amardoukhi,
    Welcome to the Forums.
    Your issue might be similar to this thread. Try the solution that was posted to rollback to an older driver version.
    The solution was to:
    1. Open Device Manager (press WInkey+R > type devmgmt.msc)
    2. On the Device Manager, navigate to Network Adapters > right click on the wireless adapter and choose Update Driver Software
       - Link to picture
    3. On the Driver Update Window, choose Browse my computer for driver software >  Let me pick from a list of device drivers on my computer and choose the wireless card on the list.
       - Link to picture
       - Link to picture
       - Link to picture
    Regards
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • WiFi problem after upgrading to Windows 8.1 Lenovo R400 ThinkPad

     I have this problem after updating to 8 to 8.1
    Right after updating to 8 to 8.1, all of a sudden my wifi stops working. I used my philips external wifi usb stick and now I'm able to get the internet going.
    However if I disconnect my philips usb I no longer get the internet because the built in wifi that came with the R400 ThinkPad no longer works. I went through the device manager and under properties it tells me, 'Device not working properly' however it is up to date.
    Im Running Windows 8.1  64bit  Laptop Lenovo R400 ThinkPad

    Hi Matti,
    Thank you for replying back!
    I suggest you to reinstall the Windows 8.1, as all the windows driver will not update, if you have upgraded the Windows 8 to Windows 8.1.
    Please download Windows 8.1 separately and reinstall the OS, I hope this may resolve the issue.
    Note: I am not suggesting for clean installation, only reinstalling the same OS.
    Do not update the drivers from ThinkVantage system update utility. I suggest you to uninstall the current drivers and download the drivers manually for Windows 8.1 and install it.
    Below is the link to enter the downloads page and download updates accordingly, please click on "Select Product" then in "QUICK PATH" enter the MTM no. select the exact model.
    http://support.lenovo.com/en_US/downloads/default.page#
    Hope this helps!
    Best regards,
    Hemanth Kumar
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Networking Issues after Upgrading to Windows 8.1

    I have a Windows 8 desktop PC that is working fine with my network.  I can browse the Internet fine using all major browsers etc.  After upgrading to Windows 8.1 through the Windows Store I noticed that my wired networking was not working correctly.
     The status of the network does not change (i.e. it doesn't change to Limited Connectivity) however browsing to sites in Chrome, IE or Firefox doesn't work as well as Windows 8.
    IE11 gives me the error "This page can't be displayed, make sure the web address is correct" and other browsers give a similar error.  I normally have to refresh 2-3 times to get a new page to load, sometimes even more.  Everything works
    fine from a laptop connected at the same time so it isn't an network issue with my provider.
    I thought this might be a driver issue with the two on-board Marvell wired network adapters.   I wasn't able to rollback the driver to older versions I found on the Internet.  I then purchased another network card, Intel Desktop gigabit and the
    issue still persists with that adapter.  I then tried a USB wireless adapter and the issue still persists using wifi with the wired adapters disabled.  I tried a new network cable and no luck either.  I also tried resetting the IP stack using
    the various netsh commands.
    After that I thought I might try reset the Windows 8.1 PC, however that didn't work as I didn't have the restore image available as I upgraded from the Windows Store.  I then tried installing Windows 8.1 fresh using a ISO with my Windows 8 key using
    some of the recent guides that are available.  That all worked but it didn't fix the networking issues.
    I re-installed Windows 8.0 and the networking is now fixed and back to working normal again.  I'd like to try again but I think I will have the same problems.  I can't imagine why this would be a driver issue as I tried 3 different network adapters
    and two installs of Windows 8.1.  Any ideas what would be the cause of the Windows 8.1 issue?

    HI,
    Since this issue only occurred in the your desktop PC, and many network adapters you tried, failed, thus I think maybe we should focus on the model of your desktop PC, I suggest you update the BIOS and chipset from the manufacture to improve
    the performance of win8.1.
    Please also test this issue in safe mode with networking.
    Please refer to:
    Windows Startup Settings (including safe mode)
    http://windows.microsoft.com/en-in/windows-8/windows-startup-settings-including-safe-mode
    I’d like to share the following article with you:
    Wired and wireless network problems
    http://windows.microsoft.com/en-IN/windows/network-connection-problem-help#network-problems=windows-81&v1h=win81tab1&v2h=win7tab1&v3h=winvistatab1&v4h=winxptab1
    Regards,
    Yolanda
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.
    The issue occurs in safe mode as well under Windows 8.1.  The motherboard is an Asus P5B Premium, however it works on Windows 8.  How would I update the chipset when booted into Windows 8.1?  In Device Manager it wasn't allowing me to update
    the network drivers as they were newer versions already installed.
    Edit:  I also installed at Intel Chipset Device software dated 8/8/2013 with version 9.​4.​0.​1026 and the issue still occurs.  I am also running the latest BIOS that is available.

  • Dolby DIGItal HOME THEATER cannot be installed after upgrading to Windows 8.1

    Hi there,
    today i was forced by microsoft to upgrade from windows 8 to windows 8.1 I have problem with installing Dolby Digitial Theater Home app. I unistalled previous conexant drivers (windows 8) and installed new conexant (for windows8.1). I removed dolby. Then i went to C/Drivers/WIN/Audio/DolbyGUI/ there is setup.exe, dolbydigitalplusAA.msi and dolbydigitalplusHT.msi. THe setup.exe doesnt start installation, plusHT(home theater) gives message saying - cannot installed due to an error. However I can install dolby digital advanced audio, but I want my Home Theater back!!!! Can you please help me resolve this matter.... thank you
    I have lenovo edge E531 with 8gb ram, intel core i5-3230M 2.6GHz, GeForce 740M

    hi sotim01,
    Thanks for posting!
    1. Uninstall all components,
            Open Device Manager and Uninstall your Conexant audio under Sound and ganing controllers (make sure to place a check under delete driver software for this device)
    2. Open Control Panel Uninstall a program and highlight the dolby component and an Uninstall button will appear.
    3. Open your C: drive and Delete any folder that says drivers if non then continue with the next step
    4. Download this Driver for installation
            Conexant Audio Driver  
    Install it and continue
    5. Open Drive C: now and you should have the Drivers folder back.
          Open that, Open Connexant Open Dolby Gui,  then you should have Dolbyaa for Advanced audio.
    Restart your PC and there you go!
    Let me know your findings
    Cheers!
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

Maybe you are looking for

  • IOS6 WIFI bug, still not work now, exhausted,help...

    Been like this a week now, tried every possiable way still not any help at all, it can connect the wifi, internet works for 1or 2 minuts then will faile again, changed one router and tried all different settings as still not work, someone told me the

  • How to put a value from a V$ view into a variable?

    in my procedure, i use the following codes: SELECT v.VALUE INTO l_cputime FROM V$SYSSTAT v WHERE v.NAME ='CPU used by session'; But it always reports "table or view does not exist". Is anything wrong with my codes? I can SELECT * FROM V$SYSSTAT; in t

  • I have a new iPad and would like to have all my contacts in my address book hre how do I go about this

    Could I please get help having my email contacts on my iPad.   If they are already there how do I get them to be able to write to them.   I have them on the computer so do they automatically appear  on qmy iPad.  Thanks for any help.

  • In the market for a new laptop..

    Hi everyone, i am currently in the market for a new laptop and seeking some advice. I am debating between getting a basic rMBR 15' 2.4 GhZ 8/256 model and MBR 2.3 GhZ 4/500. The price for the basic rMBR 15' 2.4 GhZ 8/256 model is 1,867 euros with App

  • Third Party Application Crashes

    I've been an Apple owner since the first Apple IIe. I have never experienced so many problems with a software upgrade that I have recently experienced with both Lion and iCloud. I have two computers in my home as well as an iphone and iTV. I was happ