Toshiba virtual store blanc white screen after start

Hello,
I have a Toshiba JournE and I need help with Virtualstore (blanc screen when starting, after update to 70.jt1.c) please do an account reset, account number is 32508
Thanks!

Thank you for the request.
Your Toshiba Virtual Store account has been reset.

Similar Messages

  • TS2376 i have multicolored vertical lines on white screen after start up

    i have multicolored vertical lines on white screen after start up on macbook. how do i fix this?

    i have the same problem with my iphone 4s, im just waiting for it to die from battery but try rebooting,restarting or charging it

  • White Screen after start up chime and Apple logo, any common issues/reasons?

    Hi all,
    I have a 2011 quadcore i7, 4GB RAM MacBook Pro which has recently and suddenly developed this annoying fault. A perminant white screen after the Apple logo and spinwheel. I have removed the hard drive (from my early 2011 MacBook Pro) and did a clean install of Lion (10.7) and I know the harddrive is fine and functional as my Mac Pro is able to boot from it and works perfectly, put the same drive back into the MacBook Pro and same, start up chime - Apple Logo - Flash, screen stays white. So its not Harddrive and most likely not a software problem (as the drive has been whiped and OSX reinstalled.) Any thoughts that it may be a bust motherboard or graphics card?
    Already tried:
    Safe Boot
    Single-user Mode
    Verbode Mode
    Resetting the NVRAM/PRAM
    Wiping and installing OSX
    Disc recovery
    Internet Recovery
    Many thanks in advance

    Hi all,
    I have a 2011 quadcore i7, 4GB RAM MacBook Pro which has recently and suddenly developed this annoying fault. A perminant white screen after the Apple logo and spinwheel. I have removed the hard drive (from my early 2011 MacBook Pro) and did a clean install of Lion (10.7) and I know the harddrive is fine and functional as my Mac Pro is able to boot from it and works perfectly, put the same drive back into the MacBook Pro and same, start up chime - Apple Logo - Flash, screen stays white. So its not Harddrive and most likely not a software problem (as the drive has been whiped and OSX reinstalled.) Any thoughts that it may be a bust motherboard or graphics card?
    Already tried:
    Safe Boot
    Single-user Mode
    Verbode Mode
    Resetting the NVRAM/PRAM
    Wiping and installing OSX
    Disc recovery
    Internet Recovery
    Many thanks in advance

  • Toshiba Virtual Store - blank white page only

    Hi guys
    a friend of mine recently gave me her Toshiba Journ.E touch.
    She had already unpacked and tuned it on.
    Well, when i got it, i tried to visit *Toshiba Virtual Store*
    But when I did, I saw a blank page.
    I waited 30 (!) minutes but still nothing.
    I asked my friend if she remembers doing something similar, she told me she doesnt know!
    I tried to reset it but still nothing.
    I dont even know the PERSONAL ACCOUNT (which I learned of its existence from this forum!! Since i dont know how the real page looks like!!! ).
    Please help me, i dont have access to the store!!
    I cant get anything!!!!
    Greetings from greece!!!!!!!!!!!!! :D:D:D:D:D:D:D:D:D:D::D

    i found what my personal account is by pressing the ''impressum'' button down on the left...
    i already posted on forum for an account reset. Another question.. Does anybody know why my internet explorer doesnt work? It doesnt even show the keybord when i m pressing the adrees line... thx :)

  • Journ.e Touch Virtual Store - blank white screen

    I registered in the store. Then I was asked to invite an update and restart. Now I only get a white screen. Can I reset the program or download the update.
    Account 32 334, firmware E_1.101
    Thanks for the help
    Frank from Germany

    Hello!
    I also have a problem with Virtual Store. I made probably everything things with my tablet that I found on this forum. I update my soft, hard reset, soft reset. and I can't open Virtual Store. When I open VS I have a blank white page and anything else. I wait 10 minutes, 20, 30 and nothing. The Internet Connection is OK, because Opera browser open websites. After update soft the VS ask me about upatedting VS I click update and waiting. After that tablet restarts and the problem is back.
    Please help .
    Gelo

  • Starts normally, white screen after start up

    I connected it through HDMI cable to my TV and still, there is a white screen on my TV as well. It's a G61-409CA

    Some windows files are corrupted or it contains a virus.
    Try entering safe mode:
    http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03439317
    Sorry because of different timezone I might not be able to help/reply you right away.IF that happens I deeply apologize!
    **Click the White thumb if you like the answer.**
    **Please mark Accept As Solution if it solves your problem and only solves your problem, if you have any more questions please ask, this also helps others to solve related issues.**
    Feel yourself like home here, we are all happy to help, if you have an question reply or start a topic or pm me or an expert.

  • White screen after start up

    When is switch my machine on my display works fine, i pop in the password n then its white i tried pressing "cmd + option + escape " it shows no finder so I'm guessing its the finder problem as it wouldn't load . Is there a way to get the finder back to working conditions ? .
    I tried disk
    Utility but pressing "cmd + R " during start up it says my hardrive is ok .
    Please help

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    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.”
    b. 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.
    c. 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 either of the techniques in Steps 1b and 1c 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 you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
    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, or if a firmware password is set, or if the startup volume is a Fusion Drive or 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 10. 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
    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 10
    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 11
    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 12
    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.

  • How to get past white screen after start up

    .

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a boot failure is to secure your 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 your last backup, you can skip this step.   
    There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
         a. Boot into 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.”
    b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot 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.
    c. 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
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot 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.
    If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
    Step 3
    Boot in safe mode. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to boot 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 your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you boot 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, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 5.
    If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot 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 reboot as usual (i.e., not in safe mode.)
    If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 4
    Sometimes a boot failure can be resolved by resetting the NVRAM.
    Step 5
    Launch Disk Utility in Recovery mode (see Step 1.) Select your 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 reboot as usual.
    Step 6
    Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 7
    Repeat Step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
    Step 8
    This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. Both desktop and portable Macs used to have such a battery. The logic-board battery is separate from the main battery of a portable. A dead logic-board battery can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 9
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested. If you can't get to an Apple Store, go to another authorized service provider.

  • Toshiba Virtual Store Account Reset - 24479

    Hi All,
    I have got same problem like many others before. After updating virtual store just white screen shows up. I did not find the solution so can u do a virtual store account reset - 24479 for me, please.
    Thanx much.
    Best regards
    Achron

    Thank you for the request.
    Your Toshiba Virtual Store account 24479 has been reset.

  • White screen on Toshiba virtual store - account 33090

    Hello,
    I have created a Toshiba Personal Account today and after updating the application I get white screen.
    Please help.. Personal Account is 33090
    Thanks.

    Thank you for the request.
    Your Toshiba Virtual Store account 33090 has been reset.

  • Toshiba Virtual Store works perfectly after update!

    Hi
    after using my journey, I realized that I have not made ??the right choice.
    But when I saw your discussions, I told myself that I have nothing to lose if I do an update.
    I followed the instructions to the letter and " MIRACL" Toshiba virtual store works perfectly.
    I download all the applications without any problems.
    But Youtube stil not working!
    c'est dommage

    As far as I know the YouTube changed its software architecture and therefore this app is not working.
    But thanks for the commend regarding the virtual store update

  • Toshiba Virtual Store Account reset - 32536

    Hello,
    I have a Toshiba JournE and I need help with Virtualstore (blanc screen when starting, after update to 70.jt1.c) please do an account reset, account number is 32536
    Thanks!

    Thank you for the request.
    Your Toshiba Virtual Store account 32536 has been reset.

  • Toshiba Virtual Store Account Reset - 7443

    Hello,
    I have a Toshiba JournE and I need help with Virtualstore (blanc screen when starting, after update to 70.jt1.c) please do an account reset, account number is 7443.
    Thanks!
    Message was edited by: ShaielIndira

    Thank you for the request.
    Your Toshiba Virtual Store account 7443 has been reset.

  • Toshiba Virtual Store Account reset - 32644

    Hello,
    I have a Toshiba JournE and I need help with Virtualstore (blanc screen when starting) please do an account reset, account number is 32644
    thanks!
    *P.S. Please explain what is "restart" and "reboot" for this devise. I was supposed to restart and reboot after downloading the update file but i got confused and probaly did something that got my app store stuck again.*

    Hi,
    I think it will be done soon. I had the same problem. ;)
    But you can try your account in the meantime. Maybe you are lucky and it already works without a reset
    Take a look here:
    http://www.toshibatouch.eu/journe_touch_wince/faqs.php
    Q: I forget my Toshiba Virtual Store account. How can I recover it?
    A: You can recover your Toshiba Virtual Store account details by making a private request to administrator from support forum on www.toshibatouch.eu. In your request, you need to provide your user identifier for your account. You can find it in the Toshiba Virtual Store login dialog. Toshiba customer support will reply your request privatly in the same forum thread, supplying you your account information.

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

Maybe you are looking for