Announcement

Collapse
No announcement yet.

Kubuntu gives me a "blue screen of death"

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Kubuntu gives me a "blue screen of death"

    Yesterday I was messing around with some command line stuff and not having a lot of success. I closed the computer and when I went to log on later is when I ran into the problem. It starts up OK, lets me sign in with my user name and password. The blue background screen comes up and everything stops. The mouse freezes and no further action takes place. The only way I can get out of it is to unplug the machine. When it boots I chose a login that lets me try some repairs but that was not any help at all. It is a dual boot machine with Windows 7.

    I am wondering if the install CD would run in a repair mode. I've seen that on other distros.

    Any help would be appreciated.
    Tags: None
    • Top
    • Bottom
    #2
    You mentioned that you were messing around with "some command line stuff", it would help us to identify what yoiu did and how to correct it if youi can let us know this "command line stuff" you did.
    • Top
    • Bottom

    Comment

      #3
      Originally posted by NickStone View Post
      You mentioned that you were messing around with "some command line stuff", it would help us to identify what yoiu did and how to correct it if youi can let us know this "command line stuff" you did.
      Thank you, I thought solution to your request rather simple. Go and copy the commands off the command line, but.... I could not get to that command line. In any event I hoped that Kubuntu would repair it and so I installed it again. Dumb Huh! More than dumb, this 14.04 is not as good as the last one. The last one was updated on line from a previous version. It had Wine this one doesn't. Previouisly if I went to root->mnt the Windows came up from the other half of this dual boot system, I could use a number of windows programmes via Wine. Now the "mnt" command is just blank. The reason for all this is that I downloaded 14.04 from the webisite. Now I want to know how to mount windows once again and hopefully map to the tag in Dolphin. I've tried twice to install Wine and I am still not sure if I have got it as it is not showing up in the menus which it did before.
      Last edited by elder73; Nov 28, 2014, 09:38 PM.
      • Top
      • Bottom

      Comment

        #4
        When ever the desktop fails to appear after logging in one of the causes can be the permission on ~/.Xauthority has changed and root has become the owner and group. You can take the recovery mode at boot up and log into a root console. Then use ls to check .Xauthority in your home account. If it is owned by root you can use chown and chgrp to change it back to your account name and group.
        "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
        – John F. Kennedy, February 26, 1962.
        • Top
        • Bottom

        Comment

          #5
          Originally posted by GreyGeek View Post
          When ever the desktop fails to appear after logging in one of the causes can be the permission on ~/.Xauthority has changed and root has become the owner and group. You can take the recovery mode at boot up and log into a root console. Then use ls to check .Xauthority in your home account. If it is owned by root you can use chown and chgrp to change it back to your account name and group.
          Thank you GreyGeek wish I had read this before I installed 14.04 again. My previous 14.04 came after two online updates. This time I downloaded the disk and it does not act the same and is a perishing nuisance. Cheers, elder73 +5
          • Top
          • Bottom

          Comment

            #6
            Originally posted by GreyGeek View Post
            When ever the desktop fails to appear after logging in one of the causes can be the permission on ~/.Xauthority has changed and root has become the owner and group. You can take the recovery mode at boot up and log into a root console. Then use ls to check .Xauthority in your home account. If it is owned by root you can use chown and chgrp to change it back to your account name and group.
            Hello GreyGeek it happened to me again. This time it happened after I have been trying to install Win and failing at it. I can get to the command line and ultimately to my files, so I am going to follow up on what you suggest above. However, I have not done command line stuff in years, so I am a bit nervous about using chown and chgrp. Thank you, elder75
            • Top
            • Bottom

            Comment

              #7
              As root in a console you can issue
              chown youraccoutname:youraccountname /home/youraccount/.Xauthority
              replacing "youraccountname" with your actual account name.
              "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
              – John F. Kennedy, February 26, 1962.
              • Top
              • Bottom

              Comment

                #8
                Originally posted by GreyGeek View Post
                As root in a console you can issue
                chown youraccoutname:youraccountname /home/youraccount/.Xauthority
                replacing "youraccountname" with your actual account name.
                Thank you, I sat down to try it and instead I picked "Ubuntu with advanced options" and everything was there. So I think I will leave it alone.
                • Top
                • Bottom

                Comment

                  #9
                  By saying "everything was there" are you saying that /home/youraccount/.Xauthority was owned by you and your group?
                  "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                  – John F. Kennedy, February 26, 1962.
                  • Top
                  • Bottom

                  Comment

                    #10
                    Originally posted by GreyGeek View Post
                    By saying "everything was there" are you saying that /home/youraccount/.Xauthority was owned by you and your group?
                    To be honest I did not look but I will now. When I did go back to Kubuntu I tried its normal startup and it worked fine. If you have any thoughts about installing Wine I would love to hear them. I keep running into blocks.
                    • Top
                    • Bottom

                    Comment

                      #11
                      Originally posted by elder73 View Post
                      To be honest I did not look but I will now. When I did go back to Kubuntu I tried its normal startup and it worked fine. If you have any thoughts about installing Wine I would love to hear them. I keep running into blocks.
                      WINE is not worth the effort, IMO.

                      I've used the repository version and I've purchased CodeWeaver's commercial version, CrossOver, which is better in its approach to WINE's fundamental problem: every new release breaks all the tweaks you did to get some Windows app to run under WINE and it stops running. CrossOver isolates each Windows app in its own "bottle", so that when you install another windows application its configuration and tweaking supposedly does not alter the tweeks in the other bottles. I've had mixed results.

                      Another big problem for both is that there is NO guarantee that any particular Windows app will run under either version of WINE or, if it once ran, would do so now. The WineHQ has an AppDB which lists the Windows apps that run under WINE and how well they run. Those that run on a fresh "out of the box WINE installation" are classed as "platinum". "Gold" apps require some special configurations (which may or may not work on your system), "Silver" apps have minor issues which "do not affect typical usage", and ever other app, which doesn't run well or at all.

                      https://appdb.winehq.org/

                      In my experience the latest versions of Windows apps usually don't run on any version of WINE, only the older version, whose code is locked in stone, works. Microsoft Outlook 2010 is on the Silver list. CrossOver's database is here.

                      I use SteamLinux. I've purchased CastleStory and Portal2 for my grandsons to play on their Kubuntu machines, and I've purchased Universe Sandbox2 for experimenting on my box. When you install Steam it sets up the appropriate menu option to connect to steam. If you get a freebie or purchase a program its installation installs a menu option. You don't trash up your home account with hidden directories and hidden files that mimic the "C:/" drive, etc...

                      Windows XP was a moving target that neither version of WINE could hit very often. I suspect that Win7 and its apps are equally elusive.

                      I used WINE once, along time ago, to test Windows malware I'd get as payloads on incoming email. Using WINE I'd fire them off to see what they did and what files they left behind. When I was done exploring them I'd delete the WINE hidden directory and the whole mess would be deleted. I'd reinstall WINE and test another virus or Trojan. But, it got boring because most of them used the same vectors at the time.
                      Last edited by GreyGeek; Dec 01, 2014, 04:04 PM.
                      "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                      – John F. Kennedy, February 26, 1962.
                      • Top
                      • Bottom

                      Comment

                      Previous template Next
                      Working...
                      X