White Screen at shutdown

Occasionally when i shut down my mac it takes a while and the screen remains white for about 30 seconds or so.....is this a major issue? how can i prevent this from happening in the future? solutions? advice?

I checked the link that you posted and it does not look like the one shown. It looks like a PC bios bootup screen with lot of "doing this messages" and then it boots 100% normally.
It might actually be by design although like I said I did not have it on my ealrier Mac Mini.

Similar Messages

Stuck at white screen during shutdown

My new macbook pro 13inch is taking forever to shut down. When i clicked the shutdown button, everything goes on as per normal till it reaches the white screen with the roller and it just stays there forever, draining battery till I force shut it down. Any ideas on why is this happening and and solution? Thanks in advance for all your help! (:

Hi. Thanks for your prompt reply! I'm not too sure on how to go about looking for entries that might indicate a hang but i've attached a screenshot of the console and would you kindly help me take a look? Thanks! (:

Won't get past white screen on shutdown/restart

When I choose shut down or restart on my 2012 rMBP, it logs out and moves to the white screen. From what I've seen, for an unlimited time.
When it does this (which I think is every time), my only option is press-and-hold standby key - which I hate doing!
This has been a problem since before Mavericks. I've tried resetting pram, repairing permissions etc etc. any other advice?
Even just a list of things to check which I may have already would be appreciated so I can discount them.

Been looking for a solution to this for ages and still no luck.
Even when I boot up in Safe Mode I still get infinite white screen when I shut down!!

White Screen After Shutdown? Macbook will not shut off!

Hello All,
Hopefully someone can help me out, please! Just restarted my Macbook using solo safe because i was getting "the white screen of death." Thought I fried it after it encountered a little water spill...not the case. I got it up and running again...but my only issue is, when i shut down my Macbook...the screen and the apple logo behind it remains lit. It will continue to charge and when I want to power on will turn on. Any mystery to why the laptop won't fully shut down? We left it uncharged overnight thinking it was a fried logic board so could the low charge have something to do with it?

Collettey wrote:
" Thought I fried it after it encountered a little water spill...not the case.
How much water and what did you do to dry it out?
Did you power up before it was dried out?
Dale

White screen on shutdown

I bought a G550 laptop last month, running Windows 7. Occasionally on shutdown, the screen goes brilliant white, and remains like this until the battery runs down! The system has obviously really shut down, as the status lights go off and there is no disc activity. However, restarting and shutting down again just returns it to the same state. The only solution appears to be to remove the battery, wait a few seconds, then replace.
Is this a known problem? Is it a BIOS problem, and is there a fix?
Thanks for any assistance!

I do not know if there is a fix or not. My old HP laptop did the same with Ubuntu. (Turn white then get whiter until it turned off)
IT Specialist and Consultant
Lenovo Tablet Evangelist
Current Machines: IdeaCentre A300, ThinkPad Tablet, IdeaPad U410, and Yoga 3 Pro Touch
Deutsche Community Comunidad en Español
Lenovo - the latest in DOtabs, DOpads, DOcentre's, DOstations and DOservers!

Why does iMac show after boot white screen

Hi, the iMac is about a year old and showed suddenly a problem with the screen. It turned blue and it disapeared only by pulling out the power cord.
Today, the restart stops after the apple logo and ends in a white screen. Shutdown is posible by the power switch - holding three seconds.
It is not a problem of a harddrive, because i could see the recovery drive. However starting the recovery drive did show the same steps ending in a white screen.
What is the problem? I think it is a failure if the grafic card?

iMac (27-inch): AMD Radeon 6970M Video Card Replacement Program

TS1440 iMac freezes, no choice but to hard shutdown, turn back on, white screen with folder and question mark appears

Hi,
so my iMac (it's not the most recent iMac if it makes any difference, and I'm running mountain lion 10.8.3) often freezes and I do a hard shutdown as I cannot force quit the applications or click on the apple in the top left to shut it down. When I come to turn it back on, I'm greeted with a white screen, in the middle of which is the dreaded folder with the flashing question mark in it. I've noticed that just before a freeze occurs, it starts running slowly and if I try going onto Facebook for example, it says that it cannot connect to facebook.com despite the internet connection being fine as I can browse things on Google. I have also noticed that before a freeze, in Finder, in All My Files, no files show. I went through this http://support.apple.com/kb/TS1440 and the problem still persists. Sometimes it does load fine if I shut it down again but when I eventually open up safari, if I had been on youtube for example, it will reload the page from a few videos before and not the one I was on when it actually froze.
Any help would be hugely appreciated,
Thanks
Side note: When it says I must choose a community in order to post this, it only gives me a choice of 3 which are Mac OS X v10.4 Tiger, v10.5 Leopard, v10.6 Snow leopard, so apologies if this is posted in the wrong place - is there any way to get it moved to the correct place?

Yes,easy fix but difficult to buy,think you can get them from the states (off the top of my head about £15).When you go to the apple store,tell yhem what you suspect and they will test if it is the cable or if its the hard drive,dosn't take that long and it's free.If you know what to do you can take the back off and with strong magnifying glass you might be able to see the fray look at the bend of the cable.

White screen and freeze when trying to restart after downloading Mountain Lion 8.2 upgrade. Mac will not shutdown or restart without freezing on whitescreen.

Downloaded Mountain Lion update 10.8.2 last night. All went well until the message after the download – restart your mac to install this update. The screen went white and the machine didn’t restart. After waiting for quite a while, I shutdown using the main power button. Restarted iMac later and it opened in 10.8.1 and the iTunes icon informed me that I had an upgrade to 10.8.2 that required me to restart the machine to install the upgrade. I did this and again, the screen went white and froze when trying to restart. Rebooted thinking I might be OK to run in 10.8.1 and ignoring the update but when I tried this the Mac worked fine but when I came to shut down I got the white screen freeze thing again. Does anyone have any easy-to-follow solutions for this or will I have to shut down using the main power button every day?
Many thanks for any suggestions.

Bootup holding CMD+r, or the Option/alt key to boot from the Restore partitirion & use Disk Utility from there to Repair the Disk, then Repair Permissions.
If that doesn't help Reinstall the OS.

Mail application cancels shutdown-white screen on computer startup

When clicking a dock icon, it continues to bounce and will not open. Then when I try to shutdown computer, I get the message that mail is stopping the computer from shutdown and needs to be force quit. When I do this, the screen goes white for 15 minutes before it will shutdown. When I restart it, I get the white screen forever and must use the power button to turn it off and unplug it for 20 seconds and all is fine. Doesn't happen everyday. Not sure if it is related, but at times a screen keeps moving an inch or so from left to right again and again. Must keep clicking the mouse to get it to stop. imac, 2 years old, Mountain Lion

Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
Reboot, test again.
If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.
Check the System Preferences>Other Row, for 3rd party Pref Panes.
Also look in these if they exist, some are invisible...
/private/var/run/StartupItems
/Library/StartupItems
/System/Library/StartupItems
/System/Library/LaunchDaemons
/Library/LaunchDaemons
Have you blown the dust out lately?
Get Temperature Monitor to see if it's heat related...
http://www.macupdate.com/info.php/id/12381/temperature-monitor
iStat Menus...
http://bjango.com/mac/istatmenus/
And/or iStat Pro...
http://www.islayer.com/apps/istatpro/

Iphone 3gs shutdowns random, it fails to turn on, it displays a white screen with colors lines

I have an iPhone 3GS. It It shutdowns random, it fails to turn on, it displays a white screen with colors lines.

I have the 3GS and it recently started the RSD. At first I thought it was just the batter not holding a charge and being lower than what the display showed. However, even when fully charged the RSD's occur mostly when loading either Apps or web pages in Safari.
I have not experienced the white screen and colored line, yet apparently. Is this the logic board like in the MacBook's?
iPhone 3GS, IOS 4.2

NOTHING i do to this Ipod touch is making the BLANK WHITE SCREEN go away......

Please help! I now hook my ipod touch up to my P.C, and it is NOT RECOGNISING my ipod!! Heres the problem AGAIN, let me make myself a little more clear on WHAT a stupid thing i did earlier..... I receieved a message (ON MY IPOD) saying a new version of I.O.S 6 is available, so it says I needed at least 50% charged, OR had to be plugged in, so I PLUGGED in, and hit the button to update to newest version, then did what I had to do, came BACK to the iPod at 30 min later, and the bar seemed to not be moving, and i had to go to work, so i FORCED A SHUT DOWN by holding the home and the top button together, as i normally would to shut the thing down if something was jammed or whatever....so I did that, and it came back on BY ITSELF with the apple sign, then 5minutes later, the blank screen came up, and NOW every single time I TRY shutting it down, it WON'T STAY OFF, it comes right back on to the apple sign, then back to blank screen every time, can't get it to stay off! And now when I hook to my PC, it's not recognizing the iPod, I don't know how to recover it, cuz the iPod WON'T STAY OFF for me to do it!! And another thing, i let the ipod die completely, then plugged it in to charge, then it came back on as usual by itself, and still done the same thing!! All because i stopped an update in the middle of it updating!! It seems as if i wiped it completely out! But theres gotta be a way to restore??? need to speak with someone on the phone, cuz I don't have the money to spend right now on an apple support person!

Please please READ what I have written before u respond,PLEASE!!because I MANUALLY STOPPED THE UPDATE TO IOS 6 WHILE IT WAS IN THE MIDDLE OF UPDATING (by forcing shutdown in the middle of it all..) and when it turned back on it went right to the white blank screen and has been that way EVER SINCE!! i cannot put in recovery mode, cuz every single time I SHUT my ipod down (by holding the power, and home button at the same time till it shuts down...) it DOES NOT show me the slide bar to power off, and it immediately shuts down (goes black..) then immediately STARTS BACK UP BY ITSELF and shows the APPLE LOGO for about 5 minutes, then goes RIGHT BACK TO THE WHITE, BLANK SCREEN!!!! It will NOT STAY OFF, it WILL NOT SHOW ME THE SLIDE BAR TO POWER OFF MANUALLY, and when I force shutdown, it immediately comes BACK ON BY ITSELF!! And then nothing but white screen! My PC COMPUTER will NOT recognize the iPod as being plugged into USB on my computer for me to RECOVER this IPod, so I do not know what else to do??? I have updated to the latest version of iTunes, and STILL NOTHING!!! This is my kids iPod that I screwed up here, and I am very upset! It's a 4th gen, 32gb iPod touch that is NOT CHEAP at all, and I am freaking out man!!! What do I do?

Can't login to the store,get a blank white screen

I am running the latest Itunes, on a Mac running OS 10.5.8. I can open Itunes, but when I try to reach the store all I get is a white screen. Upon itunes shutdown a page of errors is listed as long as your arm. Any thoughts on how to fix this.

In iTunes prefs>Store - is the Store check box unchecked?
Did you repair pemissions with Disk Utility?
MJ

White Screen at Boot When Attempting to Access Recovery or Select a Boot Disk

Introduction
I want to share a solution for a problem I encountered that Apple technical support was unaware of (they said they would create a new kdoc when I called them to share my problem and its solution) and for which I could find no documentation online.
First, this is really a tip rather than a question, but I did leave it marked as a question in case anyone wants to earn some points by responding with a different solution to the problem I am about to describe. Additionally, I do not have a enough points to post a "Tip" so I am just starting a discussion instead.
Next, when I encountered the problem I am about to describe, I had not yet enabled a firmware password.
Finally, a massive "Thank you!" to the Great Pondini (James Pond - http://pondini.org) for helping me learn so much more interesting stuff about various OS X features and functionality (all for no charge) over the years.
Now on to why I have started this discussion...
The Problem
I recently purchased a new MacBook Pro (Core i7, SSD, etc.). After working with Setup Assistant to transfer everything from the most recent Time Machine backup of the older MBP I was replacing, applying all OS updates, and then enabling FileVault 2 and letting the requisite disk encryption process complete, I decided to I would go ahead and just proactively repair any permissions and ACLs for my user directory just in case any repair was necessary.
However, after shutting down my MBP, waiting, and then starting it up with Cmd-R being pressed while turning the MBP on, nothing would happen - I would just have a white screen with no Apple logo, no EFI login, no Recovery Console, nothing (and I waited for a very long time for something to show up). My only option was to do what I really do not like doing and that was to just power my new MBP down.
So, I tried again, this time holding down Opt while turning my computer on so as to select a disk at boot. The same problem returned.
Just to check, I once again started up while holding down the Shift key to attempt a Safe Boot. No dice.
Prior to trying all of this I made sure that I did have the Apple Recovery Partition in addition to my user partion and the EFI partition, so I did not understand why this would be happening. Why could I not boot into Recovery? Why could I not select a boot disk? And, why could I not go into Safe Boot?
To be safe, I started up and logged into my MBP as I normally would, then set my startup disk to be my Recovery USB for OS X 10.8, restarted, and verified all three partitions (and, since I had my Time Machine disk connected all three times I forced the computer to power off, I verified it as well). I then set my startup disk back to my SSD, and logged in and got online to see if anyone else had experienced this issue. After making sure I was not being crazy and using key combinations that were somehow made irrelevant, I shut my MBP down and walked away for a few minutes.
The Solution
So what solved my problem? A good 'ol reset of the NVRAM (aka/fka PRAM). If you are not familiar with how to reset the NVRAM:
Power off your Mac and go do something else for 30 seconds to a minute.
Press and hold down the Opt, Cmd, P and R buttons, and then press the power button. I have big hands and this is a one person operation for me. If you are not so "lucky", find someone to press the power button as you hold those four buttons down.
Continue holding those four buttons down through the first startup chime and then release all four of them only after the second startup chime is sounded.
So, for some reason, I had to reset the NVRAM on a brand new MBP that had been started up only once and restarted only once when I enabled FV2. Maybe something cached needed to be cleared out following the FV2 process, or maybe something funky was carried over after it was setup in the factory and shipped direct to me from China.
The moral of the story is: If you have strage issues during the startup of your Mac, just reset the NVRAM and try again. This has worked for a number of strange issues on various Macs for me in the past and proved to be useful once again on a brand new MBP that I never would have thought needed its NVRAM reset so soon into its lifecycle.
Special Note
There are two processes I always complete and recommend to others following a major software update (e.g. upgrading to a new version of OS X) and when I restore or otherwise transfer the most recent Time Machine backup to my current Mac or to a new one.
First, following a major or massive software update, go into Disk Utility, select your system and data drive(s), and then just click on "Repair Permissions" (Choosing "Verify Pemissions" will result in having to then click "Repair Permissions" if any permissions need to be repaired, so remove one click from the process).
Second, after transferring from a Time Machine backup, I like to make sure that my user directory permissions are good to go before any time is allowed for problems with those permissions to set in. If you are not familiar with the user directory permissions and ACL repair process (this process is not the same as the "Repair Permission" functionality in Disk Utility), here is how to do it:
Shutdown your Mac and wait about 30 seconds.
Press and hold down Cmd-R and then power on your Mac. Once the Apple logo with the spinning wheel shows up, release those two keys.
From within the Recovery Console, open a new Terminal session via the "Utilities" menu.
Invoke the following command (all one word, lowercase): resetpassword
In the "Reset Password" application that opens, select the disk that your user home directory is on, and then click the "Reset" button at the bottom underneath the "Reset Home Folder Permissions and ACLs" heading and wait for the process to finish. Any messages displayed can typically be safely ignored. If you want to be sure, search for information regarding any messages that you do not like.
Restart your MBP and enjoy using it.
(Note that if you have FV2 enabled, you will need your FV2 Recovery Key to actually reset your password. This is one of many reasons that I enable FV2 - anyone can startup a Mac and go into the Recovery Partition if it exists and reset a password, but having to also enter the FV2 Recovery Key adds a nice extra layer of protection. In addition to that, setting a Firmware Password makes it nearly impossible to start up from any disk other that that which is currrenlty installed in your Mac without knowing the Firmware Password - another security bonus. If someone gets ahold of your Mac, and you have FV2 enabled and an appropriately complex Firmware Password set, then them using your Mac as their own becomes a decently difficult process. It's by no means perfect computer security, but it makes it more challenging for someone to steal and use your Mac.)
If anyone has any other tips to share or additional solutions to problem I described, please discuss and share.

Which OS X is installed on your Mac ?
Troubleshooting advice can depend on that information.

My 2006 Macbook won't start up completely. It gets to the white screen but wont go further. What do I have to do to fix the issue?

I was syncing my ipod to my itunes and the computer froze up. So I used the force shutdown by holding the power button. I then tried to turn it back on but when I did, it would play the chime and bring up the blank white screen before it shows the apple, but it won't go any further than that. Theres alot of clicking going on this whole time as well. The clicking had started while my ipod was syncing. I keep the computer on a cooling pad so i dont think heat had anything to do with it. I shut it down everytime I get off of it, so its not left on for long periods of time either (and i let it power down before closing the laptop).
I have pushed Alt-Command-P-R to get to the Pram, but my computer still does nothing. I've removed the battery a few times and held down the power button until the beep. Nothing seems to be working. Does anyone know what I have to do?

TutorDaddy, if this Mac is still covered by the initial warranty or under AppleCare, take it in and have it looked at. As the old label used to say, there truly are "no user serviceable parts inside." Kernel panics very usually indicate failing hardware.
I have an older iBook G4 that started developing kernel panics and like you, despite reinstalling the OS from a freshly formatted volume, they kept continuing. I looked at the crash log and saw that in each instance of panic, the last bit of code to be accessed had something to do with AirPort. Knowing that the AirPort software was at then current levels, I surmised the problem to be a bad AirPort networking card which, on that particular model of the iBook, was a very small module attached directly to the logic board. Since the computer was out of AppleCare, I broke the machine down myself (I didn't realize that there could be so many barely visible screws in one machine) and removed the offending piece of hardware. My iBook lives but without WiFi, it now sits as a more or less desktop machine needing an ethernet connection to stay connected to a network.
I do not suggest you break into your iMac. First of all, I'm guessing one would need to be able to pull off the glass and have the necessary glue to reattach it, which is not really available to us consumers. If you're feeling adventurous enough to read the crash logs from each panic, you might be able to surmise the hardware component (or badly written application or library; it can happen) that's causing the panic. If it's a software issue, remove the offending software app and see if the panics return. If it's a hardware issue, it's best to let a competent service tech qualified on Apple hardware to handle it.
[edited to add:]
After browsing through related problems in the discussions, I saw this link to a third-party web site being handed out. Perhaps you'll find it useful: http://www.thexlab.com/faqs/kernelpanics.html
Message was edited by: Stephen Adams

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

White Screen at shutdown

Similar Messages

Maybe you are looking for