Comment 25 for bug 150471

Revision history for this message
Luiz Alberto Medaets (megahertz) wrote : Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

Disable Tracker on System – Preferences – Sessions and the problem will
end.
Tracker is a desktop search tool, it has a bug, and it is launched every
time you make a search on file browser (Nautilus).
Luiz

On Wed, 2007-10-31 at 00:47 +0000, doclist wrote:
> I also experience 100% CPU usage from Nautilus after logging in userA,
> logging in userB, logging out userB. The offending process is owned by
> userB. This is new (for me) in Gutsy.
>
> I can't seem to get a proper backtrace. This is what I get immediately
> after attaching through GDB.
>
> =========
> #0 0xb727d45f in fputs () from /lib/tls/i686/cmov/libc.so.6
> #1 0x080e27c8 in write_string (filename=0x0, file=0x8905b48,
> str=0x1 <Address 0x1 out of bounds>, error=0x0) at nautilus-debug-log.c:446
> #2 0x080e28ab in nautilus_debug_log_dump (
> filename=0x89058f0 "/home/USER/nautilus-debug-log.txt", error=0x0)
> at nautilus-debug-log.c:508
> #3 0x0807e776 in dump_debug_log () at nautilus-main.c:213
> #4 0x0807e7bf in sigfatal_handler (sig=11) at nautilus-main.c:258
> #5 <signal handler called>
> #6 0xb7657af6 in gconf_client_remove_dir () from /usr/lib/libgconf-2.so.4
> #7 0xb5c2e9cd in ?? ()
> from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
> #8 0xe5000009 in ?? ()
> #9 0xb5c32d74 in ?? ()
> from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
> #10 0x00000000 in ?? ()
> =========
>
>
> Trying to 'continue' in GDB gives the following:
> ====
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1228183888 (LWP 22236)]
> 0xb7657af6 in gconf_client_remove_dir () from /usr/lib/libgconf-2.so.4
> ====
>
--
Megahertz
<email address hidden>