White screen after force quit Finder

The message on my MacBook Pro was that disk space needed to be freed up...tried to move files to the trash but just stayed "in progress" for hours...online support suggested a force quit of Finder...after reboot, I only see a white screen of death.
So many pictures that haven't been backed up...help!

Welcome to Apple Discussions.
Try starting in safe mode by holding the shift key until the grey Apple logo appears. If it starts like this open Disk Utility, select the drive and do a verify disk.
If that shows any errors insert the original installation dvd and restart holding the c key until the grey Apple logo appears. On the 1st installation screen select language & on the next locate DU from the top menu. This time run 'Repair Disk'. If it shows repairs completed rerun it until it shows no errors/repairs necessary. Then restart normally.
Report back with your results.
Neville

Similar Messages

MacBook all white screen after force quit and restart

Hiya. My good old MacBook froze last night (European time). Lots of things (ID, PS, AI, Fetch, etc) running and Firefox was idling some site not working. Gave it a rest but that only worsened things as I couldn't even skip between programs or let alone force quit Firefox. So I shut the whole thing down using cmd, alt, shift and pwr. After restarting with the reassuring sound of Apple, nothing happened. The screen didn't even turn blue but stayed on whitish grey??? I have reset the pram, done the SMC reset by disconnecting, taking the battery out and pressing pwr for 5 secs. Still same crisis. White screen and always a the start-up sound loud and clear.
Ideas, anybody. Got an Apple Protection Plan
Thanks!

Welcome to Apple Discussions.
Try starting in safe mode by holding the shift key until the grey Apple logo appears. If it starts like this open Disk Utility, select the drive and do a verify disk.
If that shows any errors insert the original installation dvd and restart holding the c key until the grey Apple logo appears. On the 1st installation screen select language & on the next locate DU from the top menu. This time run 'Repair Disk'. If it shows repairs completed rerun it until it shows no errors/repairs necessary. Then restart normally.
Report back with your results.
Neville

White screen after forced reload (used to fix previous white screen issue)

Last Friday after doing a battery pull to clear a stuck Facebook notification, upon reboot my Curve 8520's screen faded to white. I immediately did another battery pull, but then the same thing happened again. It did not return to normal until I plugged it into my wall charger.
I called my carrier, Rogers, about the issue and they sent me instructions to do a forced reload. I didn't have my USB cable until today, so I followed all the instructions for the forced reload this morning. After it went through and re-installed the software, I did a restore using the Desktop Manager. I'd been slowly working through re-installing all my applications when it froze up, so I did a battery pull. It did the "white screen of death" again after the reboot. Now it's just happening at random (ie. while waiting for a website to load), but still gets fixed temporarily if I plug it into the charger.
Is there anything else I can try to fix this? I can't exactly carry my wall charger around everywhere just in case this happens.
Another note: I'm nearly 2 years into my 3-year contract and am upset that this device isn't living up to the term. I can't afford a new phone and I don't want to get locked into another 3 years

So it's just happened again, this time without the battery pull. I was downloading the Toronto Maple Leafs app from mapleleafs.mobi, and it was nearly completed when the screen faded to white. This is very frustrating

HT201276 after force quitting finder it will not relaunch finder without having to restart the computer. Why?

can anybody help me with this. I find it extremely annoying that I have to restart the computer as the finder will not relaunch without doing so. I am new to Mac and have just purchased one last month and am having a few issues with it I would like to resolve.

ok so finder crashed on me again just before and I took a few screen shots to show you, I was copying files I had on my portable hdd into a folder on my portable hdd - I really don't think it makes a difference if im copying from my mac hdd or my portable hdd it still seems to do it sometimes

Pages file document went missing after force quit. cant find it anywhere even after using recovering files softwares. HELP

pages file document went missing after force quit. cant find it anywhere even after using recovering files softwares. HELP
i was working on a document with pages. while transferring files from USB, the 'pinball' thing popped up for the longest time which lead me to force quit the document. the document had been saved before quitting. however, my macbook starts to reboot, and after rebooting that specific file is missing. Before it quit, it says that the file is locked and asked me to create a duplicate, which i clicked yes to.

Hi,
just to say that while waiting for a help
I decided to go back from zero and moved to a second network (thanks i got some few computers available for my tests ) and this time i run in another trouble wich is the subject of a former post (with no reply...) <<HELP!! "Checksum failed" & "Integrity check on decrypted field failed ">>
http://forum.java.sun.com/thread.jspa?threadID=791804&messageID=9468957#9468957
Seems this always just leads us to problems...
Strange Sun Java Security Team just won't do anything to help us deploy quite easily on one of the most widely-spread platform ( despite we don't like them that much it's MS servers (2000 and 2003) )
Anyway if one could help... on one of the two issues Thanks

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.

TS2570 white screen after login

i have a white screen after login on my macbook pro 17' what does that mean?
i cant do anything but all the users are accesable
no finder no desktop... nothing

Reinstall Lion, Mountain Lion, or Mavericks without erasing drive
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu.
Reinstall Lion, Mountain Lion, or Mavericks
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless.

[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!

Preview is STILL frozen even after force quitting, rebooting and reopening. Help?!? I need to see my files!

Not sure what I did, but Preview continues to stay frozen even after force quitting, rebooting and reopening. It seems like it is trying to open all 720 pdf documents I have on my internal memory. That's my best guess... I really don't know what happened. I've tried clicking the 'close windows when closing application' option under general settings and every other thing I've seen listed on help sites... nothing is working. PLEASE HELP?!?

Back up all data. Quit Preview if it's running.
Hold down the option key and select Go ▹ Library from the Finder menu bar. From the Library folder, delete the following items, if they exist:
Containers/com.apple.Preview
Preferences/com.apple.Preview.LSSharedFileList.plist
Preferences/com.apple.Preview.SandboxedPersistentURLs.LSSharedFileList.plist
Saved Application State/com.apple.Preview.savedState
Log out and log back in. Launch the application and test.

Mavericks white screen after login

After upgrading to Mavericks my MacBook now goes to a white screen after login screen. Anybody having same issue? Any solutions?

Reinstalling Mavericks, Lion/Mountain Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion, Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

Force quit Finder - now Finder won't restart!

Hi there,
Last night I was converting a bunch of video files in Quicktime and copying them to a samba server on the LAN (so I could play them on my Linux-based media machine) when the Finder stopped responding and I got the spinning beachball of death.
The beachball appeared when I clicked on one of the files in Finder and it tried to generate a preview in column-view. The media files were fairly big ones (1 gig) and .mkv format (which seem particularly processor-intensive to decode) and I'm pretty sure the file in question was on the Samba server.
So all in all everything seemed to be against the Finder creating this preview and I figured it was going to take a long time to do so, so I'd just force-relaunch the Finder and go back and open the folder in a different view in order to copy it wherever it needed to be.
After doing so, though, Finder fails to restart - I've got no icons on my desktop and I can't navigate to a folder of files to click on the one I want to view.
Often in the past when I've experienced this, typing `open /path/to/folder` in terminal has had the effect of forcing Finder to restart, however on this occasion I get this error message "2008-05-23 18:11:07.383 open[7567] LSOpenFromURLSpec() returned -600 for application (null) urls file://localhost/Applications/."
If I look for the process using `ps` I see the process name in brackets:
$ ps -wwwwwx | grep Finder
5958 ?? E 0:00.00 (Finder)
$
Apparently the "E" in the above line indicates that the process is trying to exit. I can't get any further using `kill -9 5958` or anything else I've tried so far.
The Finder icon is still showing in the Dock and if I right-click on it I see "Application not responding" (greyed out), "Hide" and "Relaunch". Choosing "Relaunch" has no effect. Finder does not seem to appear in Activity Monitor (showing "All Processes") . If I open the "Force Quit Applications" dialogue again the Finder is still shown and highlighting it changes the button from "Force Quit" to "Relaunch", but clicking that has no effect (except that Finder disappears from the lit of programs; it reappears if I close the "Force Quit" window and reopen it from the Apple menu).
*+Obviously I could sort this by rebooting my computer, but I really don't want to do that right now.+* Can anyone suggest a way of properly killing this process so that Finder can restart?
Many thanks in advance for any suggestions,
Stroller.

BDAqua wrote:
Sometimes after Force quitting it a few times, it'll work... about 5% of the time.
Thanks - I'll give that a few more goes. Not that I haven't already!!
Might try to open Activity Monitor to see what else is hung, my guess is System UIServer or Window Server.
How would they show as hung?
WindowServer shows 1% - 2% activity, and the real & virtual memory values are updated every second or so, so I assume that's fine.
I was about to say that SystemUIServer does indeed show no activity, but it just blipped up to 0.2%.
I'm not familiar with SystemUIServer, but if I recall correctly killing or restarting WindowServer will close all my active windows, which is exactly what I'd like to avoid (I might as well reboot the machine as do that).
$ ps -wwwwwvvxa | grep -e WindowServer -e SystemUI
61 Ss 87:59.46 0 664 0 474840 107808 - 0 1.8 -5.1 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphic s.framework/Resources/WindowServer -daemon
177 S 0:46.88 0 652 0 253740 11164 - 0 0.0 -0.5 /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer -psn0655361
8520 R+ 0:00.00 0 488 0 27812 276 - 0 0.0 -0.0 grep -e WindowServer -e SystemUI
~ $
Furthermore, I think your HD/OS needs some maintenance.
I wouldn't debate that - I installed OS 10.4 on this machine when 10.4 was released, IIRC, so it's well overdue for a reinstall. I want to upgrade this system to 10.5, but have a load of procrastinating to do first.
But I would debate your evidence for saying it - doesn't everyone have a hung Finder occasionally? I don't think I've ever had a Mac which I didn't sometimes have to reboot. I would guess I've had pretty much this problem half a dozen times since this G5 was new - I reboot it and everything works fine and I forget about it. No worries. But right now that's not terribly convenient.
Typically I sleep my Macs when not in use, and `uptime` typically shows a month or two. But I do believe that Macs are prone to "inexplicable grouchiness" in this condition.
Stroller.

IMac will not boot. Stuck at white screen after chime.

I am starting a new thread this because it seems that other people with this problem are able to get their Macs working with some sort of keyboard combination on boot. I am not. Nothing is working. My computer is currently a 27 inch brick... Actually a lamp, since it is frozen on a really nice white screen.....
Installed Yosemite on my 27" iMac (early 2010, i7) when Yosemite came out a couple weeks ago. Everything was working fine but it wouldn't read my external drive, so I did a reboot. After the reboot, it freezes on the white screen after the chime. No keyboard combinations work to get it to do anything....also, if I hit the power button it shuts off immediately.
Nothing is working to get it moving. And yes, I am using a usb keyboard, not the Bluetooth, to try to hit any of the keyboard combinations posted in various discussions.
My AppleCare is expired, so I'm going to be very upset if I have to go pay to have Apple fix their problematic software. Any help you guys can give will be greatly appreciated.
Thank you,

See if you can boot into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear and again when you log in. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don’t do them all at once.
Safe Mode - Mavericks
Safe Mode - About
Startup - Gray, Blue or White screen at boot, w/spinner/progress bar
Startup - Gray Screen
Startup Issues - Resolve
Startup Issues - Resolve (2)

How do i get out of white screen after login

How do i get out of the white screen after signing on to my computer.

Hi GregConk,
Thank you for visiting Apple Support Communities.
If I understand right, your iMac is only starting up to a blank white screen after you log in. If so, there are some good troubleshooting steps that may resolve this behavior.
First, try booting your computer into Safe Mode, to see if your desktop appears in this mode:
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Start your Mac, then immediately hold the Shift key. This performs a Safe Boot. Advanced tip: If you want to see the status of a Safe Boot as it progresses, you can hold Shift-Command-V during start up (instead of just Shift).
Note: A Safe Boot takes longer than a typical start up because it includes a disk check and other operations.
If your Mac starts up as expected, immediately try restarting.
From:
Mac OS X: Gray screen appears during startup - Apple Support
If you see your desktop in Safe Mode, but not when starting up normally, try the troubleshooting tips in this article next:
OS X Yosemite: If you think you have incompatible login items
Best Regards,
Jeremy

IPod 4th Gen has white screen after replacement, and restore

Okay. Here's the problem. A while ago, I dropped my iPod, and it's screen cracked. I've been living with it ever since perfectly, but just with a cracked screen. Now, I ordered a new screen, and I begin to replace it. I knew how, and like an easy job, I did it pretty quick compared to others. After both ribbon cables where in, I pressed the lock button, and my iPod had a white screen. I was a little worried about that, so, I tried to reattach the screen. Now it was just black, after even using the home and lock button restart method. Eventually I got it back up and to the white screen by draining the battery and recharging, and there I was again, stuck. I looked at some forums on the internet to try to see if anyone had my problem. After clicking on the first link, it turns out, alot of people had this problem as well as me. The solution they said was pressing the home button and lock button for about 10 or so seconds, and then it goes to the apple screen and is all better again. I tried it, and my home button broke. Great. So, now I had to use the little button that the home button was pressing down to try the solution. Tried it, and, nothing. Still the blank, plain, white screen. Looked some more and saw that pressing the home and lock buttons along with the volume up button worked for some people too. Tried it, worked just as good as the previous one. Nothing. I even tried some person's idea of doing home, then volume up, then lock, in different timed stages. Nothing. I also saw people begging for them not to restore their iPods and begging for a solution. I was fine with a restore, I just had games that I played on my iPhone as well. So, I went with it, and restored it, without any backups, just going to factory mode. Afterwards I heard my iPod make the iOS "plugged in" sound, and anxiously tried the lock button. Still had the white screen. STILL. Now, I'm here, begging for a solution like others, with an iPod that won't function properly. Can someone please help me?

No nothing like that happened, I'm sure, but I actually spent the day looking for a fix. Luckily, I had the idea of taping the spring down because I though the screen didn't touch it. Turns out I was right, but however, I found out that the screen I ordered was broken in a way, because it still had the white screen after the taping. Just to make sure, I tried the other screen to clarify if the taping worked or not. I did the home and lock button restart, and up popped the apple logo. So, that means that the screen I got from the seller was either a rip-off, or was just broken somehow in process of making, or delivering in some matter. Unfortunately, I think I can't ship it back unless for alot of money because the person I got it from comes from China. I live in the USA. So that's gonna be a matter to work with myself. Thank you for trying to help.

After force quitting iTunes, now my phone is "in use" by another user

OK, here's what just happened to me tonight. I had the "beach ball of death" in iTunes, so I used a force quit. Now when I plug in my week old iPhone 4, I'm getting the message that this phone is already in use by another user on this computer. Huh?!? For one thing, I am the ONLY user although I do have a "guest" account, but I'm logged in on my regular account.
I've tried restarting iTunes, same message. Every time I plug in the phone it's doing it now. So, how am I supposed to sync my phone now?
Has anyone else had this problem after force quitting iTunes? Any ideas?

Nope, tried that, didn't work. 3 complete reboots didn't worked either. However, on the 4th complete computer reboot, it worked!! I don't know why, but I'm happy that I can sync again.
I guess it just reinforces the old, "if at first you don't succeed...."
{:)

White screen after force quit Finder

Similar Messages

Maybe you are looking for