Suddenly initramfs in kernelpanic

After a reboot last nigth I cannot start my MythTV server anymore.
I've tried booting in recover mode and allso as -s added to the bootline .
But during initramfs - it makes a long trace - whioch I cannot get over here in this windows - becaurse nothing is running on the server.
So how is the rigth procedure to recover from this crash Without having to reinstall the whole system!!

Boot with the install CD, or any live CD, chroot into your install, pacman -Syu, regenerate your initramfs image.

Similar Messages

My 2009 MBPro is suddenly Powering off

At very random occasions it will suddenly dim, then tell me to power off by holding the power for 5 sec-etc.
It has done this exactly 5 times now. When it happened 2 weeks ago, I ran Onyx thru its paces.
Today, it has happened twice. When I run the report on a reboot, it tells me it had a Kernel panic.
I sent the reports to Apple. Just wondering if there is an obvious fix I am missing?
Thanks, Rob

Welcome to Apple Discussions!
Kernel panics are a sign of a possibly much more serious condition. Backup your data*:
http://www.macmaps.com/backup.html
And try to use this guide as to what may be causing them*:
http://www.macmaps.com/kernelpanic.html
Also if you have any log files, the process it is panicking on, or kernel extension (kext file) mentioned first, may be where the problem resides.
They are found in the Console application.

LightDM suddenly broke after uninstalling a window manager

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

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

I am using Windows 8.1 i have an External Hard Disk and one drive is now inaccessible due to sudden power failure few days ago. Now it shows "Data error (Cyclic redundancy check)". I want all my important files and Pics. How ?

Hi,
I am using Windows 8.1
I have an External Hard Disk i have partitioned it to 4 parts.
One drive is now inaccessible due to sudden power failure while listening Music from that drive few days ago.
Now it shows "Data error (Cyclic redundancy check)".
I tried all the procedures provided here like
chkdsk /f, diskpart, rescan etc
but no result :( (i mean all processes failed. They could not detect the drive).
Please help me to get those data, pictures and project files.
thank you

Then why aren't you posting this in the Windows 8 forums found @
http://social.technet.microsoft.com/Forums/windows/en-US/home?category=w8itpro
This is a Windows 7 forum for discussion about Windows 7.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

I have files that have been on my computer for over a year and all of a sudden they wont open and an error message comes up saying they were improperly downloaded or came in an email attach which is not the case

I have files that have been on my computer for over a year and I have used them several times and all of a sudden they wont open. I received an error message saying they are improperly downloaded or came as an email attachement which is not the case. Please advise

They seem to be word files - they will open if I choose "open with" microsoft word, but if I double click they don't open they are appearing as PDF on my screen. I even opened one and then tried to "save as" making sure I chose .doc and they still appear as PDF
I just created a new document response.doc in word and when I saved to my desktop it appears as a PDF file and I absolutely did not create a PDF or save as PDF it was a simple word
doc.
The message says "Adobe reader could not open response.doc because it is either not a supported file type or because the file has been damaged (for example attached in an email and not properly decoded)
The reader version is I believe the most current, I always update when prompted. OS is Windows 8

Help! I am making an iPhoto book and all of a sudden it will not open and I get a huge error message which is supposedly sent to Apple. How do I access that site????

Mac osX 10.6.8
iBook - old version
can not access Safari - going through Chrome
All of a sudden my IBook would not open (100 pages and almost finished)
Error message sent to Apple - how do I access them??????
Thank you for any help you can give me
<Email Edited by Host>

Do you mean, you have been creating a Photo Book in iPhoto? Or an iBook in iBook Author?
If you are asking about a photo book in iPhoto, what was the last you did in iPhoto, before the crash happened? Did you add a page with a map?
Then you may have a problem with a bug, where adding a route to a map may render the book unreadable. In that case the best option is to restore the iPhoto library from the last backup you made, before you added the map to the book.
It is not possible to open the book and to delete the unreadable page. You can only delete the book and start over, if this bug is the reason for the crashes. See for example this link: Getting rid of problem photo book

I have been using Photoshop Elements 8 for years. All of a sudden, the cropping tool changed: I cannot crop vertically or horizontally anymore--only diagonally. This has made it impossible for me to get the photo I want. I hope someone knows how to fix th

I have been using Elements 8 ever since it came out, and all of a sudden the cropping tool has changed: I can no longer crop horizontally or vertically, only diagonally. The up/down/side arrows have disappeared! Please help if you can, I'm no longer able to make my photos look their best. Thank you in advance.

Quit the editor (Quit PSE on a mac). Then restart it while holding down ctrl+alt+shift (command+option+shift). Keep the keys down till you see a window asking if you want to delete the settings file. You do.

Excel Connection Manager suddenly can no longer connect to Excel from SSIS package

During the last 3 months, I used 32 bit SSIS 2008 (v 10.50.2500.0) on an WinXp machine (v 5.1.2600 SP3 Build 2600) to create a package that writes multiple query results (reports) to an excel spreadsheet. Each report is written to a different
tabbed sheet in the same spreadsheet. The package was working just fine until May 9 2013, when suddenly every single Data Flow task with an Excel Destination displayed error icons and raised the following
error message when opening the Advanced Editor:SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005 Description: "Unspecified error". Error at <DataFlow task name>: SSIS
error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager <Excel connection Manager> failed with error code 0xC0202009. There may be error messages posted before this with more
information on why the Acquire Connection method call failed. Exception from HRESULT: 0Xc020801c (Microsoft.SQlServer.DTSPipelineWrap)Originally the error message reported that the Error Code was "0x8000FFFF", but I can't seem
to reproduce that error code since. Now I am only getting the above error message.From the time I created the original package (when it worked fine) until now, I have been using the same computer, writing to a (32 bit) 2010 Excel file in
a local folder. The filename and location have not changed. The ConnectionString has not changed. The Connnection String I am using is Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Conversion\Conversion Results_dt01.xlsx;Extended Properties="EXCEL
12.0 XML;HDR=YES;". Now an attempt to create and test a NEW Connection Manager yields me this error. "Test connection failed because of an error in initializing provider. Unspecified error.",  whereas before I had
no problems creating a new connection manager.I checked a second SSIS package, which I also built during the past 3 months, which loads multiple sheets from multiple Excel files to a SQL Server 2008 database holding table. It uses the same
ACE OLE DB 12.0 connection to load the Excel speadsheets and this package continues to work fine on the same workstation.In desparation, wondering if the Microsoft ACE OLE DB 12.0 driver had become corrupt (even though the second package
was raising no errors), I did download and install the Microsoft ACE OLE DB 12.0 driver.  That did not solve my problems with the first package.I need to get this package running again ASAP as it is targeted for UAT testing in a
matter of days. Any help with this issue would be greatly appreciated!

I submitted this issue above and now I am having the same problem again. I am using the same local computer, the same operating system (WinXp v 5.1.2600 SP3 Build 2600) as originally described. I am working with the same SSIS package that
writes multiple query results (reports) to an excel spreadsheet. This package has been successfully executed multiple times, but now I am suddenly getting the same error as follows:
Error at 1ConversionContacts [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "Unspecified error".
Error at DFlow Write soft deleted duplicate claims to Excel sheet [Excel Destination - write duplicate claim nbrs that have been removed to Excel [61]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method
call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
The package will not run because of these multiple errors (multiple because it occurs on every single excel destination in the package).
I have Run64BitRuntime set to false on the project. I have triple checked that the excel file name (which I created and can access) exists with the correct name in the correct path, which is local on my machine. The file is the same file in the same
location as when the package worked. I am running the SSIS service under my own network login, as I was when the package worked. I have been consistently getting this same error whenever I change my network password without updating the password
in the SSIS service, but I have triple verified that the service is using my latest password. If I try to open and edit the Excel Destination in any DataFlow task I get the same error. I can successfully create a new Excel Connection Manager pointing
to the same excel file. However if I try to assign the newly created Excel Connection Manager in the data flow, I cannot activate the drop down to choose the Excel sheet without getting an 'Unspecified error' message. I then swapped out
the file with its template version, and ensured the name was updated as correct. I still get the same errors.
Oh, and the SSIS package is extracting data from a SQL Server 2008 database with an ADO.net Connection Manager using Windows authentication. I have no problems with the SQL Server connection, it has always worked and still does. It is only
the connection to excel output file which is locally stored on my machine.
Has anyone got any suggestions for me?

My time capsule all of a sudden disconnected from the wireless system and can no longer be fund by my MacBook Pro. The little lamp on the the capsules has turned off, but it still makes a noice inside,

My Time capsule did a backup yesterday in the morning without any problem. All of a sudden, it disconnected from the wireles system last night and the little indicator lamp turned off. It still makes a noice, as if a disc was turning inside. The Time Capsule was bought last year in June. Any suggestiom what to do? What happens if I press the little buttom (reset?), will I loose af my backup?

Do a reset.. power off the TC..
Hold in reset and power on.. keep holding in reset until it flashes rapidly.. if it turns on at all.
If you bought it in June.. take it back today.. it is broken.. at a guess.
Some Gen4 are failing this way.. get Apple to replace it.. even if it is a few days out of warranty it won't be much.

All of a sudden I can no longer toggle or clip angles in multiclip sequence

Hi,
I've got a project with a number of sequences, videos, angles, etc and all of a sudden I can no longer toggle between angles in the sequence timeline. It was working last night and then stopped and it's still unresponsive. Every time I click to switch an angle or cut to an angle I get the alert beep.
I am not out of disk space and haven't changed any settings as far as I am aware of.
Thanks

Not sure what the deal is...have you added any new software or upgraded/updated anything since this started?
Have you tried opening an autosave version, to see if it works there?
Trashed prefs, run disk utility?
I'm not sure I've ever heard an 'alert beep', so would wonder if the drive is failing.
Can you be a little more explicit about exactly how it 'stopped working'...were you right in the middle of working on it, or had you stepped away for a bit?
Have you tried shutting down, then rebooting after 15-20 minutes?

HELP?? Can't update my ipod all of the sudden??

I hooked my iPOD to my computer the other day to update some songs and walked away. Assuming all was well, I unhooked my iPOD and went through my music on the iPOD and suddenly, no songs AT ALL were there. Now, when I try to update my entire library again (over 900 songs), a box on my iTUNES pops up and states:
Songs on the iPOD cannot be updated because all of the playlists selected for updating no longer exist.
HELP??? I tried to change my drive letter and that didn't work - what should I do...any suggestions? PLEASE?

"Songs on the iPOD cannot be updated because all of the playlists selected for updating no longer exist."
You get this problem when the option 'Sync Music - Selected playlists' is being used to sync your iPod and then the playlist it has been updating from is deleted. Most people use this setting when the iPod is smaller than the iTunes library. If your library is larger than the capacity of your iPod, iTunes by default makes a new playlist called something along the lines of "Owner's iPod". If you for any reason delete it, you will not be able to sync your iPod.
Open iTunes and create a playlist to update your iPod from, call it -iPod to make it the first playlist in Sources. You can make this a normal playlist and drag whatever you want to it or you can make it a random Smart playlist. If you are making a smart playlist limit it to just less than the size of your iPod (for example 3700MB for a 4G iPod Nano). Now connect your iPod and when it appears in the Source list click on the iPod icon to bring up the preference tabs in the main pane. Go to the Music tab and choose Sync Music and the Selected playlists radio button. Choose the playlist you just made from the selection and click Apply. You can also sync from any existing playlists by choosing the same setting:
iTunes: Creating playlists of your favorite songs
How to create a Smart Playlist with iTunes

IPOD suddenly not seen by windows any more - I am desperate!

PLEASE HELP ME!
I have been using my 30Gb ipod happily since Xmas with no problems at all, until suddenly 1 week ago my main computer (through which I synch my ipod with itunes) stopped recognising the IPOD (not found in device manager or my computer etc), but continues to charge the ipod normally (ie the charging icon appears).
I have gone through document Knowledge Base Document #61711 and done everything to no avail.(When I say everything, that is except carry out the restore option which I can't do beacuse the updater doesnt see the ipod - why do they put this advice if windows not recognising ipod?)
I have tried plugging the ipod into other computers and the same happens - they charge the ipod but do not see it, even in disk mode.
I don't know what else to try. Is it possible to manually restore the ipod? I managed to get through to some diagnostic tool on the ipod manually (M25 diagnostic) by clicking left and select after the resetting, and the automatic diagnostic didnt find anything wrong??
Any ideas? Please help as this is now getting me down..

Try reading through this article:
http://docs.info.apple.com/article.html?artnum=93716
Hope this helps
rjl
( Jeff was my old account )
i have the exact same issue. this article doesnt help beucase windows can't see the ipod at all. i've done as much as i can but i can't do anything to the actual ipod becuase my computer can't see it! booooooooooooo
it worked perfectly until recently.

TS1369 iPod Classic suddenly not being recognized in iTunes on MacBook Pro

I just got a new MacBook Pro a few weeks ago, and have had no issues connecting my iPod Classic to it via iTunes. Yesterday, however, my iPod stopped registering in iTunes. I checked in the System Reports on my MacBook, and I can see that the USB Hub is acknowledging that the iPod is there, AND the iPod is charging when connected so I know it's not a connection issue with the cord, however the iPod still isn't registering in iTunes. If I plug up my iPhone, though, it shows up so it's likely not the computer either. My iPod is working fine and has been connecting fine until yesterday morning when it suddenly just didn't apear anymore. I need to fix it ASAP! Help!

Have you tried everything here?
iPod not recognized in iTunes and Mac desktop
B-rock

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any advice is helpful. This has never happened in 6 years

answered in your other thread LR 4 suddenly no longer recognizes files.

IPod suddenly no longer connects to any computer, hangs and clicks/pops

I recently (within the last two weeks) started using a program called PodUtil ( http://www.kennettnet.co.uk/software/podutil.php ) to manage my music library between my work and home computers. Everything seems to have gone off without a hitch, but as of Friday my iPod started behaving very strangely.
I was playing a song on it through iTunes on my work computer when all of the sudden the song cut out and iTunes froze up. I was forced to disconnect my iPod manually without disconnecting it through the computer, and when I hooked it back up my entire system locked up until the iPod was once again removed. I plugged it in again and left the system alone and finally fifteen minutes later I got an error message saying that an iPod was detected but the iPod software wasn't installed. Despite this not being true, I uninstalled iTunes and the iPod software, reinstalled them, and finally the iPod worked correctly.
Until I brought it home and plugged it into my home computer and the exact same problem occurred. I once again uninstalled iTunes and the iPod software but this time it didn't fix the problem. The iPod refuses to connect now to any of the computers I've tried it on (home, work, my roommate's PC and even a work mac) and every time it's plugged in the system hangs until it's disconnected. I have also noticed that when it's plugged in every few minutes there's a loud hum and a clicking/popping sound that reminds me of drive heads failing on a harddrive.
The iPod itself works fine, I can play everything and it gives me absolutely no trouble. It's when I connect it to a computer that the problems begin.
I'm at a loss for what to do. I've tried every single thing under the knowledge base including rebooting and reinstalling and nothing's helped. It almost seems like there's a physical problem with the iPod (from the clicking sound) but the clicks never happen during normal operation and I haven't dropped it or anything that would've broken it. It's out of warranty and I'd rather not pay the cost of a new iPod to get this one fixed. Furthermore I took my songs off of my computer to free up space and the last music backup I have isn't entirely recent. But I can't even get it to restore even if I wanted to because it doesn't respond when it's connected. Any help will be great. Thanks!

- See:
iPod touch: Hardware troubleshooting
iPhone and iPod touch: Charging the battery
- Try another cable. iOS 7 made the iPod/computer more sensiteve to cable problems
- Inspect the dock connector on the iPod for bent or missing contacts, foreign material, corroded contacts, broken, missing or cracked plastic.
- Make an appointment at the Genius Bar of an Apple store.
Apple Retail Store - Genius Bar

Suddenly initramfs in kernelpanic

Similar Messages

Maybe you are looking for