Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-02-26 Thread Martin Pitt
What did the previous version do for you if you called it through
sudo?

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

My 5 bugs today: #185273 #190947 #193494 #192786 #172792
Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-02-26 Thread jlinho
No nautilus-debug-log.txt anymore. Thanks a lot. sudo nautilus and closing
does not lead to a crash for me. Si that's another issue.

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-02-26 Thread Martin Pitt
DickeyWang [2008-02-26 23:09 -]:
 Is this fix for Hardy only or it is also for Gutsy? My Gutsy system is
 up to date, and I just got another nautilus-debug-log.txt in my home
 directory 5 minutes ago.

It is already in Hardy. For gutsy it is in -proposed at the moment,
where it is tested by a wider audience. I guess you don't have
proposed updates enabled? (System - Administration - Software
Sources - Updates).

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-02-21 Thread Jordan Erickson
Thank you!!! Just saw it download from the ropes.

=) =) =)


Sebastien Bacher wrote:
 you need to restart nautilus to get the new version running
 

-- 
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

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-20 Thread Gligor Horia
Kyle M Weller wrote:
 i can re-create this issue by having myself logged in and have any user
 log in then  log off, their processes arent killed and nautilus is at
 100 % cpu usage here is a syscall trace screenshot attached, dont know
 if it shows anything to diagnose problem

 ** Attachment added: strace.png
http://launchpadlibrarian.net/11446926/strace.png

   
don-t get me rong but didn-t we astablished that nautilus has a bug and 
we should figure out what the problem is, let-s find similarities, or we 
will not go any where

1. is it buged out of the box?
did u install aditinal software, is it because of un update to some 
library, let-s think a litle more constructive, not just confirm the 
bug, the bug was already confirmed!

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-20 Thread jlinho
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 PROTECTED]:

 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.


-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-20 Thread Jordan Erickson
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 PROTECTED]:
 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

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-20 Thread Jordan Erickson
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 PROTECTED]:
 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

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-20 Thread Jordan Erickson
Yikes. Nevermind again, I didn't know this was being copied to the bug
report already.

My signal-to-noise ratio is getting worse. ;)

Jordan Erickson wrote:
 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 PROTECTED]:
 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

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-20 Thread Jordan Erickson
Wow - unacceptable, unprofessional?

Somehow I think relevant information regarding when, how and with what
equipment would be worth more than simply throwing stones. This *is*
open source, guys. The community helps improve itself by working together.

- Jordan


---
Kyle M Weller wrote:
 Pjotr12345, you are totally right, this is totally unacceptable, my
 company is already thinking of switching back to windows because of this
 issue.  It is indeed very unprofessional as well.
 

-- 
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

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-15 Thread Gligor Horia
Jordan Erickson wrote:
 I'd like to reiterate that it my instance of 100% CPU utilization of
 Nautilus, it is a brand new install of Gutsy. I was able to reproduce it
 the first time the first created user logged out (with extremely minimal
 usage of Gnome, not including the actual browsing through the Nautilus
 file manager window).

   
I think the bug description is verry accurate: log in , log out (that's 
all u have to do...)

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-08 Thread jlinho
For me the easiest way to reproduce it is:
- The  User Switcher Applet should be added to the panel if you have
removed it. The bug occurs also on a fresh install.
- Log in in one account
- Work a little bit with nautilus
- Log out
- Log in on an another account
- Nautilus is now 100% CPU

If i remove the UserSwitcher Applet, the bug occurs rarely on my account.
But my brother manages to repeat the bug each time he works on his account,
playing with nautilus and totem.

I use a 32 bits Ubuntu; with an Intel Core 2 Quad Q6600.

How can I apply the patch manually ?

Thanks for help*
*

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-07 Thread Jordan Erickson
I would think, opening up a Gnome session, navigating in Nautilus, doing
other misc. tasks, and then logging out would cause the bug to trigger -
for me, it's not EVERY time, but definitely more times than not.

Sebastien Bacher wrote:
 Opening a gutsy task. Does anybody has an easy way to trigger the issue
 and could try if the patch works correctly on gutsy?
 
 ** Changed in: nautilus (Ubuntu Gutsy)
Importance: Undecided = High
Status: New = Confirmed
 
 ** Changed in: nautilus (Ubuntu Gutsy)
  Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
 

-- 
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

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2008-01-07 Thread Jordan Erickson
Interesting... The sites that I'm experiencing this on are dual CPUs
(Dual Core-2 Xeon 1.6GHz)...One is AMD64 build of Gutsy, the other i386
build. I haven't experienced it on any UPGRADED machines, only new Gutsy
(Desktop) installs (with server kernels).

FatButtLarry wrote:
 Worth noting, 7.10 at work (Dual Processor Xeon) does this, but 7.10 at
 home (AMD64) I haven't seen it yet.
 
 Might be because I haven't run updates at home (can't remember).
 
 -Tres
 

-- 
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

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-27 Thread jlinho
You say: I occasionally still have the problem...
Did you experience this problem each time before removing Deskbar and
Tracker ?

2007/11/27, Pjotr12345 [EMAIL PROTECTED]:

 Tracker is definitely *not* the bad guy here. Nearly a week ago, I
 completely removed Tracker, using Synaptic, and also Deskbar Applet. Yet
 I occasionally still have the problem...

 This is really a bad bug, in urgent need of repair.

 --
 [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.


-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-22 Thread doclist
On Thu, 2007-11-22 at 10:28 +, Pjotr12345 wrote:
 Possibly the bad guy is Tracker. Tracker is a plugin in Deskbar applet.
 An hour ago, I've completely removed Tracker from my system with
 Synaptic, and I'm curious if the problem is over now.
 
 Maybe you could try this, too, and report here if it has been a success?

I do not have Tracker installed and still experience the problem.

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-22 Thread doclist

On Thu, 2007-11-22 at 21:25 +, Pjotr12345 wrote:
 @doclist: I would like some clarification from you, because this is an
 important matter. Tracker is installed in the standard installation, so
 everybody has tracker automatically. So if I understand you correctly,
 you already removed tracker before, and still have the problem?
 

That's right.

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-19 Thread sja821
I have taken tracker out of the sessions preferences, but have not yet
removed the package.  What is the name of the package to make sure I
remove the proper one? (It shouldn't be in use anyway, but it is worth
a shot)

On 11/19/07, greenhunter [EMAIL PROTECTED] wrote:
 How do i remove the deskbar applet?

 --
 [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.


-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-19 Thread jlinho
Sorry greehunter, but it solved the problem clearly for me. If I re-add
Deskbar to my Gnome Panel the problem appears again.

2007/11/19, greenhunter [EMAIL PROTECTED]:

 ups,

 I don't use the deskbar aplpet at all under no accounts and no
 computers.

 --
 [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.


-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-07 Thread doclist
On Nov 7, 2007 8:12 AM, Luiz Alberto Medaets [EMAIL PROTECTED] wrote:
 Tracker is a desktop search tool, part of Gnome, and is loaded when you
 start (Disable  Tracker on System – Preferences – Sessions and the
 problem will end.) or when you ask for file search.
 Open System - Administration -System Monitor. Look for Trackerd on
 process tab to see if it's running . If it is, right click and stop then
 right click and kill.

 Megahertz


I know what Tracker is. I could have been clearer: I uninstalled
Tracker soon after upgrading to Gutsy.

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-07 Thread Luiz Alberto Medaets
Tracker is a desktop search tool, part of Gnome, and is loaded when you
start (Disable  Tracker on System – Preferences – Sessions and the
problem will end.) or when you ask for file search.
Open System - Administration -System Monitor. Look for Trackerd on
process tab to see if it's running . If it is, right click and stop then
right click and kill.

Megahertz

07 at 00:11 +, doclist wrote:
 On Nov 6, 2007 6:06 AM, Luiz Alberto Medaets [EMAIL PROTECTED] wrote:
  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
 
 
 I don't have tracker installed at all (and haven't since the first day
 of installing Gutsy) and still experience the problem.
 
-- 
Megahertz
[EMAIL PROTECTED]

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-06 Thread Luiz Alberto Medaets
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 +, 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  0xe509 in ?? ()
 #9  0xb5c32d74 in ?? ()
from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
 #10 0x 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 PROTECTED]

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-06 Thread Luiz Alberto Medaets
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 Sun, 2007-11-04 at 21:50 +, Kamil Páral wrote:
 I experience the same problem quite often. People have attached logs,
 setting as confirmed.
 
 ** Changed in: nautilus (Ubuntu)
Status: Incomplete = Confirmed
 
-- 
Megahertz
[EMAIL PROTECTED]

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again

2007-11-06 Thread doclist
On Nov 6, 2007 6:06 AM, Luiz Alberto Medaets [EMAIL PROTECTED] wrote:
 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


I don't have tracker installed at all (and haven't since the first day
of installing Gutsy) and still experience the problem.

-- 
[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 member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs