White screen after failed Lion upgrade - how can I recover?

After running the Lion upgrade, I received an error that said Lion could not be installed becuase a recovery disc could not be created. The computer then restarted to a white screen. I've tried resetting PRAM, unpugging, and booting from a Snow Leopard CD, but I can't get past the white screen. All external drives are unplugged. Any ideas?

I can't speak to iPhoto (did you ask about iPhoto?), but:
The version of Quicken 2007 for Lion is 16.1.1, which now offers an update to version 16.1.2 for Mountain Lion (among other fixes).
Presumably the Mountain Lion version is what is being offered on the online download that you acquired. You could check the version number in the Quicken 2007 menu in About Quicken and report back to us anxious iPhoto users.

Similar Messages

Iphone 5 not restoring my back up data from itunes? Iphone 5 began freezing and turning off by itself after ios7 updates. How can i recover my data?

I began having problems with my iphone 5 after I updated to ios7. It began having several issues e.g. freezing, turning on and off by itself and the home button was not responding.
It is a long story because I had to talk to apple reps etc. to make a long story short; my iphone is now in recovery mode and only works when it is set as a new iphone.
Now my back up data on itunes will not back up into my iphone 5 and my iphone is still in recovery mode.
How can I restore my itunes back up data into my iphone 5?
How can I get my phone out of recovery mode?
How can I recover my potentially lost data, contacts, sms, etc., due to backing up my iphone and trying to fix the issues with apple reps?

ArmanG wrote:
Should I just let the energy run out and then plug it into iTunes and see what happens?
Might be a better idea to try ALL of the Basic Troubleshooting steps as already mentioned to attempt to resolve the issue.

Just upgraded to Lion. My screen divider went away. How can I recover? Thanks! v

Just upgraded to Lion. My screen divider is no longer on my desktop. How can I get it back?

I saw that and almost replied, but I wasn't sure if it was the same problem because you referenced it happening when the "screen times out" and for me it was only when it was being activly used. Glad to hear I'm not the only one seeing this issue.

Blank White Screens After Installing Lion in Software

Before I start, I have a Macbook Pro 5,1 -- 2.66Ghz Core2Duo with 8GB of RAM, 500GB 7200rpm HDD, and an nVidia 9600GT M Graphics card
I installed Lion. This install was an UPGRADE from 10.6.8. Most of my apps arent working at all. Adobe CS 5.5 Master Collection, Final Cut Pro, Ableton Live, and even Time Machine.
They all just open up and give me a blank white screen (literally, a window, and instead of there being stuff inside the window its just a big giant WHITE BOX OF NOTHING). Time machine actually shows me the selected finder window but i couldnt select any older time machine dates.
Additionally I tried dragging icons off the dock, and it froze up my entire machine just by dragging them off the dock. I had to right click on icons to remove them.
I finally booted up into the "Recovery HD" and recovered my Time Machine backup to Snow Leopard 10.6.8 that I was using before.
I would very much like to use Lion, but it seems to have alot of problems with my machine. Should I do a completely fresh install maybe?
Any other solutions?

I have reverted to a backup from yesterday in which Lion was first installed and ran without problems. But this time, the windows of my apps were still white.
I also tried creating a new user account, thinking that there was a chance that it was a conflict with a piece of 3rd party software. Not that I can rule out software conflicts, but I still had the same problems.
So I'm now reverting to Snow Leopard. Ugh…
At least the "Recovery Partition" is pretty cool ;)
-Chris

I installed Windows 8 Consumer Preview and after that I cannot run OS Lion. How can I recover options to boot back in OS Lion?

I tried to reboot from CD or USB and the Mac Mini simply bypasses it to Windows 8 Consumer Preview.
How can I avoid to Windows 8 boot and have the options to select OS Lion?
I used Boot Camp as shown in many videos. I did not select any additional OSX drivers for install.
Thanks,
Marcio

I am stuck in Windows 8. I cannot boot back to LION. HELP!!! I am in Microsoft World again and no option to get back.
how can I install boot camp 4 in Windows 8 so I can reconfigure my computer back?

MBA hangs on login screen after mountain lion upgrade

I have a mid 2011 macbook air. Ever since I did the upgrade to mountain lion last week, I have had about 10 instances where it hangs on the login screen. I bring it up from sleep, I see the login but when I enter my password and hit enter, it just hangs with the login box grayed. I can hit the cancel button and it gives me the ability to interact with the login box again, but will not log in. on all but one of these instances I have had to restart the machine. I have timed it to 5 minutes twice before restarting the machine to get back in. This never happened with lion. Anyone else have this issue?

I have issues also.
With a samba share on Linux, ML can see it correctly, but on my Windows Home Server 2011, if i do smb://"server address" i receive and error saying that the share dows not exist on server. Before on Lion i had a list of my shares. On finder the Server apears with a "/" which i can not open.
If i do smb://"server address/share" is works correctly, but i would like to have tha before behaviour. Besides this the only issue that i found after upgrading is the WHS 2011 Lauchpad could not sign in (before in Lion was working).
Any ideas on how to solve this?

White screen after mountain lion install

Has anybody experienced this I do not know how to fix this ??

Similar if not the very same issue with my late 2009 iMac since upgrading to Mountain Lion.
First time I've seen actual script - DOS-like text (well, Linux or UNIX or whatever it is) that only seems to appear from a cold boot.
First time this happened I held down the power button until the system restarted.
Second time around - and from a cold boot - I entered "/exit" at the prompt and the system appears to have continuted the boot process.
Someone in another post added the following:
Open console in Applications>Utilities, check the system log for the date/time of the last problem startup for clues.
...but from this I still coudn't see where the error lies. :/

Screen separated. How can I recover my files?

Dropped the tablet and the sreen separated from the hard drive. Now the screen doesn't work. How can I recover my files?

what kind of machine?

My MacBook Pro won't go beyond a white screen, after I pushed the restart button. How can I get it to a login? I have routinely backed it up, but don't know how to bring that up, nor if I have a boot file on that external disk. Help!

My MacBook Pro won't go beyond a white screen, after I pushed the restart button. How can I get it to a login? I have routinely backed it up, but don't know how to bring that up, nor if I have a boot file on that external disk. Help!

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

TS3274 My iPad has a white screen after trying to restore. I try and restore again and the same thing happens and we are back at the white screen. How can I get it back.

My iPad has a white screen after trying to restore. I try and restore again and the same thing happens and we are back at the white screen. How can I get it back?

type HT4097 in the search bar. its unable to update or restore iOS. Follow the instructions and if that does not work then id go to the local apple store.

Hi...I have this problem, everytime I want to print something out the mac asks me for the computer password...that is really becoming annoying after. That happened since I upgraded to mountain lion. How can I stop the computer from asking me that?

Hi...I have this problem, everytime I want to print something out the mac asks me for the computer password...that is really becoming annoying after. That happened since I upgraded to mountain lion. How can I stop the computer from asking me that?

If you are printing via a Windows shared printer and it is the Windows user account that you are being prompted for then you can save this in the Keychain, as shown below.

[Solved] White screen after KDE 4.11.1 upgrade

Hi!
I updated the system going from KDE 4.11.0 to KDE 4.11.1. On reboot I got the correct loading of KDM, but upon arrival on the desktop the latter is presented fully white with big red button with an "X" in them. Thinking it was the configuration of kde, I deleted .kde4 with the effect that the next time I always white screen (that is only the red buttons have disappeared).
I try to remove completely kde with:
pacman -Rsnc kde
and seeing that reinstalling I get the same result, I also tried to clean up the cache pacman packages listed by the command:
ls kde*4.11.1*
so I redownload and reinstalled with:
pacman -Syu kde
without solution. I also tried to do what is recommended in the wiki, that is in addition to eliminating .kde4, I run:
$ rm ~/.config/Trolltech.conf
$ kbuildsycoca4 --noincremental
without solution.
Thinking then it might be the partition / almost full, I checked with:
df
but the partition is not filled even for half of the 30gb that is available.
I checked some logs and these are the outputs:
.xsession-errors
> http://pastebin.com/GESX81PV
boot.log
[[32m OK [0m] Started Load Kernel Modules.
Mounting Configuration File System...
[[32m OK [0m] Mounted Configuration File System.
[[32m OK [0m] Found device SAMSUNG_SSD_830_Series.
Mounting /Windows...
Mounting FUSE Control File System...
[[32m OK [0m] Mounted FUSE Control File System.
[[32m OK [0m] Mounted /Windows.
[[32m OK [0m] Found device WDC_WD10EALX-009BA0.
Mounting /Dati...
[[32m OK [0m] Mounted /Dati.
[[32m OK [0m] Reached target Local File Systems.
Starting Trigger Flushing of Journal to Persistent Storage...
Starting Recreate Volatile Files and Directories...
Starting Tell Plymouth To Write Out Runtime Data...
[[32m OK [0m] Reached target Bluetooth.
[[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage.
[[32m OK [0m] Started Recreate Volatile Files and Directories.
Starting Update UTMP about System Reboot/Shutdown...
[[32m OK [0m] Started Update UTMP about System Reboot/Shutdown.
[[32m OK [0m] Started Show Plymouth Boot Screen.
[[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data.
[[32m OK [0m] Reached target System Initialization.
[[32m OK [0m] Listening on CUPS Printing Service Sockets.
[[32m OK [0m] Reached target Paths.
[[32m OK [0m] Listening on D-Bus System Message Bus Socket.
[[32m OK [0m] Reached target Sockets.
[[32m OK [0m] Reached target Timers.
Starting Restore Sound Card State...
[[32m OK [0m] Reached target Basic System.
Starting Network Manager...
Starting CUPS Printing Service...
[[32m OK [0m] Started CUPS Printing Service.
Starting Catalyst's fglrx kernel' module builder...
Starting Login Service...
Starting D-Bus System Message Bus...
[[32m OK [0m] Started D-Bus System Message Bus.
Starting Permit User Sessions...
[[32m OK [0m] Started Permit User Sessions.
Starting Wait for Plymouth Boot Screen to Quit...
Starting K Display Manager...
[[32m OK [0m] Started K Display Manager.
[[32m OK [0m] Started Catalyst's fglrx kernel' module builder.
[[32m OK [0m] Reached target Sound Card.
[[32m OK [0m] Started Restore Sound Card State.
[[32m OK [0m] Started Login Service.
Starting Manage, Install and Generate Color Profiles...
Starting Authorization Manager...
[[32m OK [0m] Started Manage, Install and Generate Color Profiles.
[[32m OK [0m] Started Authorization Manager.
[[32m OK [0m] Started Network Manager.
[[32m OK [0m] Reached target Network.
Starting Network Time Service...
[[32m OK [0m] Started Network Time Service.
[[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[[31m*[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[ [31m*[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[ [31m*[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K Starting Daemon for power management...
[[32m OK [0m] Started Daemon for power management.
Starting Disk Manager...
[[32m OK [0m] Started Disk Manager.
[ [31m*[1;31m*[0m[31m*[0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[[1;31mFAILED[0m] Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details.
Starting Getty on tty1...
[[32m OK [0m] Started Getty on tty1.
[[32m OK [0m] Reached target Login Prompts.
[[32m OK [0m] Reached target Multi-User System.
[[32m OK [0m] Reached target Graphical Interface.
[[32m OK [0m] Stopped target Sound Card.
[[32m OK [0m] Stopped target Bluetooth.
Stopping Disk Manager...
Stopping Daemon for power management...
Stopping Authorization Manager...
Stopping Manage, Install and Generate Color Profiles...
Stopping CUPS Printing Service...
[[32m OK [0m] Stopped target Graphical Interface.
[[32m OK [0m] Stopped target Multi-User System.
Stopping Network Time Service...
Stopping Catalyst's fglrx kernel' module builder...
Stopping Login Service...
Stopping D-Bus System Message Bus...
[[32m OK [0m] Stopped target Login Prompts.
Stopping Getty on tty1...
Stopping K Display Manager...
[[32m OK [0m] Stopped K Display Manager.
[[32m OK [0m] Stopped Daemon for power management.
[[32m OK [0m] Stopped Getty on tty1.
[[32m OK [0m] Stopped D-Bus System Message Bus.
[[32m OK [0m] Stopped Disk Manager.
Stopping Permit User Sessions...
[[32m OK [0m] Stopped Authorization Manager.
[[32m OK [0m] Stopped Network Time Service.
[[32m OK [0m] Stopped target Network.
Stopping Network Manager...
[[32m OK [0m] Stopped Manage, Install and Generate Color Profiles.
[[32m OK [0m] Stopped Catalyst's fglrx kernel' module builder.
[[32m OK [0m] Stopped Login Service.
[[32m OK [0m] Stopped Network Manager.
[[32m OK [0m] Stopped CUPS Printing Service.
[[32m OK [0m] Stopped Permit User Sessions.
[[32m OK [0m] Stopped target Basic System.
[[32m OK [0m] Stopped target Paths.
[[32m OK [0m] Stopped target Timers.
[[32m OK [0m] Stopped target Sockets.
[[32m OK [0m] Closed CUPS Printing Service Sockets.
[[32m OK [0m] Closed LVM2 metadata daemon socket.
[[32m OK [0m] Closed /dev/initctl Compatibility Named Pipe.
[[32m OK [0m] Closed Delayed Shutdown Socket.
[[32m OK [0m] Closed Device-mapper event daemon FIFOs.
[[32m OK [0m] Closed udev Control Socket.
[[32m OK [0m] Closed D-Bus System Message Bus Socket.
[[32m OK [0m] Stopped target System Initialization.
Unmounting Debug File System...
Unmounting FUSE Control File System...
Stopping Update UTMP about System Reboot/Shutdown...
Unmounting POSIX Message Queue File System...
Unmounting Huge Pages File System...
Stopping Setup Virtual Console...
[[32m OK [0m] Stopped Setup Virtual Console.
[[32m OK [0m] Unset automount Arbitrary Executable File Formats File System Automount Point.
Stopping Apply Kernel Variables...
[[32m OK [0m] Stopped Apply Kernel Variables.
Unmounting Configuration File System...
[[32m OK [0m] Stopped target Encrypted Volumes.
[[32m OK [0m] Stopped target Swap.
[[32m OK [0m] Stopped target Local File Systems.
Unmounting /Windows...
Unmounting /Dati...
Unmounting Temporary Directory...
Stopping Journal Service...
[[32m OK [0m] Stopped target Remote File Systems.
[[32m OK [0m] Stopped Update UTMP about System Reboot/Shutdown.
[[32m OK [0m] Unmounted Temporary Directory.
[[32m OK [0m] Unmounted POSIX Message Queue File System.
[[32m OK [0m] Unmounted FUSE Control File System.
[[32m OK [0m] Unmounted Huge Pages File System.
[[32m OK [0m] Unmounted Configuration File System.
Stopping Load Kernel Modules...
[[32m OK [0m] Stopped Load Kernel Modules.
[[32m OK [0m] Unmounted Debug File System.
[[32m OK [0m] Unmounted /Windows.
[[32m OK [0m] Unmounted /Dati.
[[32m OK [0m] Reached target Unmount All Filesystems.
[[32m OK [0m] Stopped target Local File Systems (Pre).
Stopping Remount Root and Kernel File Systems...
[[32m OK [0m] Stopped Remount Root and Kernel File Systems.
[[32m OK [0m] Stopped Journal Service.
[[32m OK [0m] Closed Journal Socket.
Starting Show Plymouth Reboot Screen...
Starting Store Sound Card State...
Unmounting /...
[[32m OK [0m] Started Store Sound Card State.
[[32m OK [0m] Reached target Shutdown.
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Hardware watchdog 'iTCO_wdt', version 0
Unmounting file systems.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All loop devices detached.
Detaching DM devices.
All DM devices detached.
Storage is finalized.
dmesg
> http://pastebin.com/fbgh2ayu
journalctl -p 3 --since=today
-- Logs begin at mar 2013-07-30 13:16:10 CEST, end at lun 2013-09-16 08:52:14 CEST. --
set 16 08:43:14 arch dhcpcd[346]: eno1: ipv6rs_sendprobe: sendmsg: Cannot assign requested address
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 0.pool.ntp.org
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 1.pool.ntp.org
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 2.pool.ntp.org
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 3.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 0.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 1.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 2.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 3.pool.ntp.org
set 16 08:45:03 arch login[308]: pam_systemd(login:session): Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
set 16 08:45:04 arch kdm[351]: :0[351]: pam_systemd(kde:session): Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
set 16 08:45:04 arch kdm[351]: :0[351]: pam_close_session() failed: Cannot make/remove an entry for the specified session
set 16 08:45:04 arch systemd-coredump[1103]: Process 309 (X) dumped core.
[1;39m-- Reboot --[0m
set 16 08:46:11 arch dhcpcd[346]: eno1: ipv6rs_sendprobe: sendmsg: Cannot assign requested address
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 0.pool.ntp.org
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 1.pool.ntp.org
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 2.pool.ntp.org
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 3.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 0.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 1.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 2.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 3.pool.ntp.org
set 16 08:48:02 arch login[305]: pam_tally(login:auth): pam_get_uid; no such user
kdm.log
> http://pastebin.com/zmgj4AGq
Xorg.0.log has no errors.
How can I resolve it?
Thanks
Last edited by Fregtux (2013-09-20 08:35:13)

Fregtux wrote:
Thanks Thaodan! I deleted /var/tmp/kdecache-$USER and I solve the problem! I also restore .kde4_backup and at the moment have no issue.
Small question: I noticed that there are also kdecache-kdm and kdecache-root. I should remove it or doesn't matter?
Thanks for the help!
THANKS, my White Screen was caused by a combination of issues but this solution worked for me.
My Problem -
I am not sure exactly what caused my white screen, I was playing around with /etc/profile & /etc/sudoers
What I changed -
sudoers - I added my user group to sudoers and allowed sudo to execute applications using xauth in home dir
profile - changed umask to 133 ( I hate execute bit ) and default text editor to nano
What Happened -
Tried to reload via source but no changes where taking effect so I rebooted.
Upon reboot I could not login to KDE, it would keep looping back to the KDM after I entered by password for my user, however it would let me login as root ( after I enabled root login ).
I figured this was a permission issue so I changed umask back to 022 in /etc/profile, I was then greeted with the White Screen after login. I read numerous posts about how to fix this, most said to reinstall kde and delete /tmp, none of this worked.
I deleted /var/tmp/kdecache-$USER and now I am back in business ( I had to re set the widgets, i.e. panel ).
I was so excited that I had to write a post about it!
Thanks again!

Can't sleep after Mountain Lion Upgrade

I have 13-Inch Mid 2009 Macbook Pro, it won't sleep after Mountain Lion upgrade. How can I solve this problem?

Hi,
After the first update to Lion, sleep problem is resovled. I am now at 10.8.1 and everything looks fine.

I can't login (always crashed) in my MacBook pro after updated to lion. How can I do?

I can't login (always crashed) in my MacBook pro after updated to lion. How can I do?

already finished to reinstall. It's a little bit better now. But still not very stable, sometime crash in login screen, sometime crash when I was browsing. Do anybody can solve it?

IMac white screen after Lion system install

Two days ago, iMac froze with the dreaded white screen. Unplugged all external hardware. Restart with "Command R", fixed all permissions and verified the disk. Cold start locked at white screen. Reinstalled Lion. After the reinstall the system did restart on its own and everything looked normal. Shut down and did a cold restart and the white screen is back. Shut down and cold start with "Command R" very long process but Utilities finally opened. But what to do next?
This iMac has had the recalled Seagate hard drive replaced by Apple, although some years ago.
Thanks for your thoughts, Bill

Page 3,
After writing the above I went in and pressed the ON/OFF button, it went black and shut down. Waited 10 seconds and pressed the ON/OFF button and instantly my desktop and all folders were back. Everything looks normal.
Now each time I have verified permissions there has been a file that can not be fixed. A "SUID ..... " file. Have to do with anything?
I am going to shut her down one more time wait the 10 seconds and Start.... locked in white screen.
Restart with "Command R", and now it appears hung up on the Apple and spinner for a very long time and Utilities finally opened. Although it will take some time before it loads enough to make things selectable. When that happens I will do a Restart from the pull down Apple menu and see what happens.
Looks more and more like my Authorized Apple Store is about to get a visit.

White screen after failed Lion upgrade - how can I recover?

Similar Messages

Maybe you are looking for