Results 1 to 4 of 4

Thread: Boot issues after a crash.

  1. #1
    Acidworm NNTP User

    Default Boot issues after a crash.

    I'm using OpenSuse 11.1, and it was doing the updates that it wanted to do (the ones that pop up in the bit next to the clock), and I was using firefox to browse the net. Suse crashed, The mouse still moved the cursor, but all the windows were unresponsive, so I rebooted the machine.
    It wouldn't boot into normal mode, it got to the point where it has the OpenSuse logo and a loading bar beneath it, it took a while to start moving, but it did fill up to the end, and then the screen went black, and stayed that way until I rebooted.
    I started it up in Failsafe mode completely normally.

    Here is the bug buddy analysis:

    Code:
    Distribution: openSUSE 11.1 (i586)
    Gnome Release: 2.24.1 2008-12-03 (SUSE)
    BugBuddy Version: 2.24.1
    
    System: Linux 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686
    X Vendor: The X.Org Foundation
    X Vendor Release: 10502000
    Selinux: No
    Accessibility: Disabled
    GTK+ Theme: Mist
    Icon Theme: Mist
    
    Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
    CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
    
    
    
    ----------- .xsession-errors ---------------------
    Nautilus-Share-Message: returned from spawn: SUCCESS: 
    Nautilus-Share-Message: exit code 255
    Nautilus-Share-Message: ------------------------------------------
    Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled
    warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
    HP Linux Imaging and Printing System (ver. 2.8.7)
    System Tray Status Service ver. 0.1
    Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
    This software comes with ABSOLUTELY NO WARRANTY.
    This is free software, and you are welcome to distribute it
    under certain conditions. See COPYING file for more details.
    --------------------------------------------------
    Any help on fixing the problem would be much appreciated.

    Thanks

  2. #2
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,857
    Blog Entries
    20

    Default Re: Boot issues after a crash.

    If it was still updating when it crashed did you run updates again?

    Try the normal boot again and hit Esc. to view verbose text, make notes of what you see.
    Tumbleweed_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #3
    Acidworm NNTP User

    Default Re: Boot issues after a crash.

    It was still updating when it crashed, and I haven't updated again in safe mode because the little popup icon in the bottom corner that told me to update hasn't popped up, and I'm not sure that all the ones in the Yast update list are the same thing.

    I did a normal boot and pressed the esc key, but I don't know what I'm looking for, it looked pretty much the same as the failsafe boot, and everthing said done, and then it just went black when it finished booting.

  4. #4
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,857
    Blog Entries
    20

    Default Re: Boot issues after a crash.

    When in the system
    open a terminal and become su and do

    Code:
    zypper ref
    then
    Code:
    zypper up
    Tumbleweed_KDE
    My Articles Was I any help? If yes: Click the star below

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •