Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: ocassional freeze on waking screen saver

  1. #11
    Join Date
    Sep 2006
    Location
    Denver, Colorado
    Beans
    5,638
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: ocassional freeze on waking screen saver

    I can't open that archive. It seems to be corrupted.
    To err is human, to forgive is very ... dog-like.

    Thomas Aaron
    FetchMasters, LLC

  2. #12
    Join Date
    May 2006
    Beans
    133

    Re: ocassional freeze on waking screen saver

    Quote Originally Posted by thomasaaron View Post
    I can't open that archive. It seems to be corrupted.
    Somehow I missed your response, Thomas -- sorry about that.

    Something about gzipping the tar made it go screwy, but the original tar (attached) is readable.

    Also, I just confirmed that the problem persists despite the measures I've taken:

    Quote Originally Posted by Pitt Stains View Post
    1. Brightside is uninstalled
    2. In System > Power Management, I've changed "Put display to sleep when inactive for:" from 15 minutes to never.
    Thanks for your continued assistance.
    Attached Files Attached Files

  3. #13
    Join Date
    Sep 2006
    Location
    Denver, Colorado
    Beans
    5,638
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: ocassional freeze on waking screen saver

    Well, I see two interesting log entries.


    Code:
    Mar 18 12:16:44 red5 kernel: [11794.318265] nautilus[9184]: segfault at 7fb555350960 ip
    Code:
    Mar 18 12:37:45 red5 kernel: [13055.047306] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
    The first is nautilus crashing. The second is a filesystem problem.

    Open System > Admin > System Monitor > Filesystems and see if any of your partitions are full.

    If they are, empty your trash can and reboot. If that doesn't fix it, we'll look at expanding the partition in question.

    If they are not full, let's run fsck from a live CD on your partitions. Here are instructions...

    -------------------------------------------------------
    To run fsck, first boot from a live CD. Once you are booted, to to System > Administration > Partition Editor. This will show you your current partition layout and the designations of your partition. For example, your partitions may be /dev/sda1, /dev/sda5, and /dev/sda7. Whatever the designations, make note of them.

    Then open a terminal (Applications > Accessories > Terminal) and run fsck as follows (only use your own partition designations)...

    sudo fsck /dev/sda1
    sudo fsck /dev/sda5
    sudo fsck /dev/sda7

    fsck will examine your filesystems and try to repair any damage. Occasionally, filesystems get too broken for fsck to fix them. In this is the case, it may be necessary to put a fresh image on your machine.

    It could also mean that you have a faulty hard drive. However, this is pretty rare, and it is better to try re-imaging the machine first.
    ------------------------------------------------------
    To err is human, to forgive is very ... dog-like.

    Thomas Aaron
    FetchMasters, LLC

  4. #14
    Join Date
    May 2006
    Beans
    133

    Re: ocassional freeze on waking screen saver

    Any idea what would make Nautilus crash?

    My partitions are fine. The fullest one is at 66%.

    I don't have a live disk with me, so I'll have to wait until tonight or tomorrow to do the fsck. It's weird that the warning doesn't specify which partition it's referring to... Also, periodically Ubuntu will perform a regularly scheduled scan on a partition or two on boot up. Could this warning just be a notice that the internal counter has reached its magic number and that the partition will be scanned during the next boot?

  5. #15
    Join Date
    Sep 2006
    Location
    Denver, Colorado
    Beans
    5,638
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: ocassional freeze on waking screen saver

    Possibly, but...

    Since Nautilus has to browse the filesystem for files, it makes sense that a filesystem error could cause it to segfault. And nautilus segfaulting leads me to belive this has nothing to do with the automatic fsck.

    Let's try to get this one cleared up to see if it fixes the original problem. If, after running fsck from a live CD, the problem recurs, please capture another set of logs (and the time of the freeze), and I'll have another look.

    Please send another set of logs (along with the exact time of the freeze) the next time the error occurs.
    To err is human, to forgive is very ... dog-like.

    Thomas Aaron
    FetchMasters, LLC

  6. #16
    Join Date
    Sep 2009
    Beans
    217

    Re: ocassional freeze on waking screen saver

    If fscking the filesystems doesn't work you could try replacing nautilus with thunar or pcmanfm. If the crash continues, then it may be time to try upgrading. Alternately, you could see if you have the same problem in lxde or xfce.

  7. #17
    Join Date
    May 2006
    Beans
    133

    Re: ocassional freeze on waking screen saver

    Here are the results of fsck from a Live CD. I've also attached a screenshot of gparted.

    Code:
    ubuntu@ubuntu:~$ sudo fsck /dev/sda1
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    /dev/sda1: clean, 208632/500960 files, 1276970/2000084 blocks
    ubuntu@ubuntu:~$ sudo fsck /dev/sda2
    fsck 1.40.8 (13-Mar-2008)
    fsck: fsck.swap: not found
    fsck: Error 2 while executing fsck.swap for /dev/sda2
    ubuntu@ubuntu:~$ sudo fsck /dev/sda3
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    fsck.ext2: No such file or directory while trying to open /dev/sda3
    
    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
    
    ubuntu@ubuntu:~$ sudo fsck /dev/sda5
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    /dev/sda5: clean, 14573/250480 files, 495136/1000038 blocks
    ubuntu@ubuntu:~$ sudo fsck /dev/sda6
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/sda6
    
    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
    
    ubuntu@ubuntu:~$ sudo fsck /dev/sda4
    fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/sda4
    
    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
    I should probably add that sda1 mounts to /, sda2 is my swap partition, and sda5 mounts to /home. sda4 is an unused partition, set aside in case I ever feel like installing another OS on its own partition. sda6 is a TrueCrypt drive.
    Attached Images Attached Images

  8. #18
    Join Date
    Sep 2006
    Location
    Denver, Colorado
    Beans
    5,638
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: ocassional freeze on waking screen saver

    OK, I think the problem might be that sda5 is WAY too small. It is only 1.93 GB, and 1.89 of that is used. So it only has about 41 MB of memory left. Doesn't take much to fill that up -- a song, or a couple of pictures.

    You probably should start by booting from a live CD, and then going to System > Admin > Partition Editor, and then expanding that home partition by quite a bit.
    To err is human, to forgive is very ... dog-like.

    Thomas Aaron
    FetchMasters, LLC

  9. #19
    Join Date
    May 2006
    Beans
    133

    Re: ocassional freeze on waking screen saver

    Quote Originally Posted by thomasaaron View Post
    OK, I think the problem might be that sda5 is WAY too small. It is only 1.93 GB, and 1.89 of that is used. So it only has about 41 MB of memory left. Doesn't take much to fill that up -- a song, or a couple of pictures.

    You probably should start by booting from a live CD, and then going to System > Admin > Partition Editor, and then expanding that home partition by quite a bit.
    Actually, gparted reports sda5 is 3.81 GB, and of that only 1.89 GB is used, so about 1.93 GB is available. But most of the folders that would eat up space in the home directory -- and anything personal or sensitive -- are actually just symlinked to the TrueCrypt volume (sda6). For example, Music, Videos, Documents, .ssh and other folders are just symlinks on sda5; the real content is on sda6.

    Any other thoughts?

  10. #20
    Join Date
    Sep 2006
    Location
    Denver, Colorado
    Beans
    5,638
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: ocassional freeze on waking screen saver

    Actually, gparted reports sda5 is 3.81 GB, and of that only 1.89 GB is used, so about 1.93 GB is available.
    Oops! Right you are. Sorry about that.

    Another idea: Do you have screensaver selection set to random, or are you using a particular screensaver. Could you try "antspotlight" and see if you get the same results?
    To err is human, to forgive is very ... dog-like.

    Thomas Aaron
    FetchMasters, LLC

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

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