Comment 119 for bug 150471

Oh man...Ok sorry everyone, I'm not sure why my brain farted and I
forgot that there is already a fix for this (released in Hardy, not
backported to Gutsy).

---
nautilus (1:2.20.0-0ubuntu8) hardy; urgency=low

  * debian/patches/18_disable_signal_handler.patch:
    - Don't use the logging code signal handler it's buggy and makes
nautilus
      being stuck and eat cpu on crash (LP: #150471)
---

Everyone who is having this issue needs to go to the actual bug report
in Launchpad, at:

https://bugs.launchpad.net/ubuntu/gutsy/+source/nautilus/+bug/150471

Make an account if you don't already have one, and post a comment on the
bug requesting a backport to Gutsy. That way, the developers will see
how many people this bug is currently affecting in Gutsy and hopefully
will shift some momentum to it to backport it. =)

- Jordan

Jordan Erickson wrote:
> I thought at first the similarities were dual-core CPUS - I'm having
> this issue on HP Proliant ML370 (G5) servers - 2x dualcore Xeon 1.6GHz
> (i386 *and* AMD64 installs). They are all Ubuntu LTSP servers that serve
> entire labs. I have seen Nautilus hog 100% of the CPU when I am the only
> one logged in (and then out), after the first login after installation.
> I don't have to launch an actual filebrowser window for it to come up
> (Nautilus loads automatically to show desktop icons, etc. anyway).
>
> What's changed in Gutsy? Well, Compiz (which I don't use on my servers),
> desktop-applet/tracker (which I have removed)... Is only happens when
> someone is logging out. There has to be some sort of cleanup/other
> routine that is triggering it.
>
> I agree it can't be SO huge that *everyone* is experiencing this issue.
> So here is my setup, hopefully people who are having this issue can
> post their setups as well so we can find some commonalities.
>
> Server: Ubuntu 7.10 (A mix of i386 & AMD64, server & desktop installs,
> all with latest linux-image-server kernels, all acting as LTSP servers
> for i386 clients). All on HP Proliant ML370 G5 servers, 8GB RAM (using
> PAE in the kernel to address all 8GB), 146GB RAID 1 arrays (2 SAS
> disks). All of them running Gnome with the latest updates.
>
> All instances of 100% CPU hogging happens with users who have not
> modified Nautilus settings in any way (or have even opened filebrowser
> windows). It's definitely stock, out of the box behavior. It doesn't
> happen every time, but definitely at least 30-50% of the time, whenever
> someone logs out.
>
> HTH,
> Jordan
>
>
>
> jlinho wrote:
>> Does everybody here have a Core 2 XXX CPU ?
>>
>> I have a Core 2 Quad CPU. Maybe hardware has an influence for this bug? I
>> just can't imagine that everybody who installs Ubuntu 7.10 has such an
>> enormous bug (The 100% CPU Nautilus bug appears on a fresh Gutsy install).
>>
>> Also I am not using a 64 bits install, just a 32 bits one.
>>
>> 2008/1/20, Alen <email address hidden>:
>>> It is bugged out of the box...
>>> Maybe I'm wrong, but it happened on my machine on the fresh install and
>>> also after upgrading from feisty.
>>> All I have to do is start nautilus from "Places" menu on the secondary
>>> screen and then close it.
>>> Or log off one of the users. Simple as that: start/close or logoff.
>>>
>>> --
>>> [Gutsy] high processor activity after logging out and then logging in
>>> again
>>> https://bugs.launchpad.net/bugs/150471
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>

--
Jordan Erickson
Owner, Logical Networking Solutions
http://www.logicalnetworking.net
707-636-5678

Latest LNS Blogs - http://blogs.logicalnetworking.net

 RFID Passports coming in 2008
 Peru orders 260,000 OLPC laptops for kids, Mexico 50,000
 CNet to Microsoft: Ditch Vista