Announcement

Collapse
No announcement yet.

Kubuntu Feisty; unresponsive & flaky

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kubuntu Feisty; unresponsive & flaky

    I was wondering if anyone else's experience is like mine, ie that Feisty's KDE desktop is slow, often unresponsive with frequent program crashes?

    My main offenders are Firefox, which will 'hang' for a minute or more before closing with frequently crashing at the end of it, Amarok and Kate behaving similarly. Amarok is so bad that I have removed.

    And how does one give experience feedback to the developers, other than the tedious bug reporting system?


    regards

    #2
    Re: Kubuntu Feisty; unresponsive & flaky

    could you pls tell us how much ram you have on your system
    and then post the result of the following from konsole...
    Code:
    free
    Code:
    swapon -s
    Code:
    df -h
    kde and its applications are fast and reliable: your instance should too!
    gnu/linux is not windoze

    Comment


      #3
      Re: Kubuntu Feisty; unresponsive & flaky

      I have the same problem with Firefox, but even more so with Thunderbird. I have to shut it down and restart it alot and it crashes upon closing. It doesn't seem to close smoothly.
      Also I have had numerous problems with xorg. It has gotten corrupted 3 times already and I have had to do a complete reinstall of the dist each time.

      Comment


        #4
        Re: Kubuntu Feisty; unresponsive & flaky

        The only gripe about kubuntu from me is the slow boot up. I am not a guru by any means, but I have tinkered with various flavors of linux from Corel thru red hat 6 and most of the fedoras and kubuntu is quickly becoming my favorite. I haven't touched winders since 7.04 landed.

        Does anyone know how to tweak the boot up?

        Comment


          #5
          Re: Kubuntu Feisty; unresponsive & flaky

          Originally posted by jankushka
          could you pls tell us how much ram you have on your system
          and then post the result of the following from konsole...
          Code:
          free
          Code:
          swapon -s
          Code:
          df -h
          total used free shared buffers cached
          Mem: 1035784 1017376 18408 0 144496 535860
          -/+ buffers/cache: 337020 698764
          Swap: 3028212 19300 3008912

          swapon
          Filename Type Size Used Priority
          /dev/hda5 partition 3028212 19300 -1

          Filesystem Size Used Avail Use% Mounted on
          /dev/hda1 71G 11G 57G 16% /
          varrun 506M 240K 506M 1% /var/run
          varlock 506M 0 506M 0% /var/lock
          procbususb 506M 112K 506M 1% /proc/bus/usb
          udev 506M 112K 506M 1% /dev
          devshm 506M 0 506M 0% /dev/shm
          lrm 506M 33M 473M 7% /lib/modules/2.6.20-15-generic/volatile



          kde and its applications are fast and reliable: your instance should too!
          That was my experience with edgy. I was very pleased with it and think perhaps that I should put it back.

          regards

          Comment


            #6
            Re: Kubuntu Feisty; unresponsive & flaky

            i don't see anything macroscopically wrong with your configuration.
            i'm sorry.
            all looks ok.

            3 things you could do:
            a) open up the performance monitor (kmenu->system->performance monitor)
            there may be some (possibly buggy) process using a lot of cpu...
            b) open up the log viewer (kmenu->system->system logs viewer)
            and look for error messages in the system's log, in the kernel's log, ...
            c) hit ctrl-alt-f1 (ctrl-alt-f7 to go back) and see if any messages come up on the console...


            gnu/linux is not windoze

            Comment


              #7
              Re: Kubuntu Feisty; unresponsive & flaky

              Originally posted by RamaJama
              Does anyone know how to tweak the boot up?
              Only thing I noticed new in feisty... fsck checks EVERY filesystem in fstab, even if 'noauto' is specified. This can slow down boot a lot if you have partitions you don't normally mount. At least I assume it's getting the list from fstab, unless it built another list during installation - I haven't really bothered with it because I don't reboot much. Other than that the boot seems a little faster than edgy was. Certainly runs faster.


              Check out my blog for useful scripts and tips... http://igurublog.wordpress.com

              Comment

              Working...
              X