running hardy here and saw same errors as gimme5 described, which on
reboot gives me a black screen with no control bars/panels. the only
reason i'm able to submit this bug is because pidgin starts correctly
and i can tell it to open my gmail from there. adding the killall
nautilus to
I have the same problem on Gutsy amd64 on a Core2Duo with nVidia Go7600
256Mb and no nautilus installed
I can run and see pidgin, the calculator, evolution
but no Firefox or terminal
--
[Gutsy] high processor activity after logging out and then logging in again
Oops... i did had nautilus installed dããã
disabling the effects
and
apt-get purge nautilus
apt-get install nautilus
/etc/init.d/gdm restart
seems to have resolved the black desktop problem but still no icons
on menu and no buttons on windows
--
[Gutsy] high processor activity after
maybe a shot in the /dev/null ... but I installed everything again, and I see a
bunch of lines like this:
/var/lb/scrollkeeper/oc/scrollkeeper_extended_cl.xml:2777: Parse error : Extra
content at the end of the document
/sect
^
/var/lb/scrollkeeper/oc/scrollkeeper_extended_cl.xml:2777: Parse
Copied to gutsy-updates.
** Changed in: nautilus (Ubuntu Gutsy)
Status: Fix Committed = Fix Released
--
[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
After applying the update yesterday on our LTSP-server there are no
hanging processes anymore.
--
[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
Thanks for the testing so far. Positive feedback in the sense of I
applied the update and everything still works as normal is also
appreciated.
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You received this bug notification
applied
and no high cpu usage so far on single und multi user desktops with nautilus.
No nautilus debug file anymore.
thx a lot.
--
[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
** Tags added: verification-done
** Tags removed: verification-needed
--
[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
Nobody experiments a nautilus crash since the patch when doing a
sudo nautilus
??
--
[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
(sorry, when doing a sudo nautilus, AND closing nautilus.)
--
[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.
--
** Tags added: verification-needed
** Tags removed: verification-done
--
[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
I applied the update last night and it works for now: no more hanging (and high
CPU usage) nautilus when opened closed on secondary screen.
As for sudo nautilus, usually I don't do that, but here is the result: upon
closing I get Segmentation fault (core dumped).
But nautilus doesn't get hung
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!
It used also to crash (don't remember if a .crash was created, though)
but the processor was additionnaly under a high activity, and unable to
close.
Nautilus process was needed to be killed, to unload the processor.
--
[Gutsy] high processor activity after logging out and then logging in again
Thanks. So that's hardly a regression then and the new package seems
better. Thanks for confirming!
** Tags added: verification-done
** Tags removed: verification-needed
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You
The same thing happened here. But my biggest problem was logging off another
user or closing nautilus on the secondary screen.
Fixing /etc/gdm/PostSession/Default solved the first problem, and this update
seems to have fixed the other. I never had the problem with large
nautilus-debug-log.txt
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
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.
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You received
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
Fix has been working for me for several days, now with no evident side
effects. Thank you!
--
[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,
I applied the patch. No nautilus-debug-log.txt up to now.
--
[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.
--
the change is not to solve crasher but to get nautilus not being stuck
on the log when there is one
** Attachment removed: _usr_bin_nautilus.1000.crash
http://launchpadlibrarian.net/12135108/_usr_bin_nautilus.1000.crash
** Attachment removed: second user session
Since it was an artificial crash (when talking about the first one), a
consequence of nautilus being stuck, I thought it could be of use.
I was wrong. If you need something else...
--
[Gutsy] high processor activity after logging out and then logging in again
the bug seems to mix different issues. Does anybody still get nautilus
creating a nautilus-debug-log.txt on crash when using the update?
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You received this bug notification
Like Jordan, I've also bin bitten by this bug on a dual LTSP server
network. We also have NFS home directories, which compounds the
slowness.
I just applied the updates for nautilus and nautilus-data from gutsy-
proposed. I'll see what happens over the next few days.
--
[Gutsy] high processor
you need to restart nautilus to get the new version running
--
[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.
--
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 -
I applied the updates for nautilus, nautilus-data and libnautilus-
exension1 from gutsy-proposed (release 7.1). Unfortunately, no change;
nautilus runs, and whenever I quit, it crashes and the process uses a
high amount of the processor.
Reproducing it is quite easy: open a terminal, run sudo
** Attachment added: second user session
http://launchpadlibrarian.net/12135148/_usr_bin_nautilus.1007.crash
--
[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
Great level of detail Psykotic. :)
--
[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
right, neither the ubuntu triagers nor upstream has really used this log
so it should be no issue, I've already uploaded the update
--
[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
Accepted into gutsy-proposed, please test and give feedback here. Can
someone come up with a reproducible test case?
** Tags added: verification-needed
** Changed in: nautilus (Ubuntu Gutsy)
Status: Confirmed = Fix Committed
--
[Gutsy] high processor activity after logging out and then
** Attachment added: the corresponding changes
http://launchpadlibrarian.net/12083909/nautilus_2.20.0-0ubuntu7.1_source.changes
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You received this bug notification because
** Attachment added: debdiff for gutsy-proposed update
http://launchpadlibrarian.net/12083888/nautilus.debdiff
--
[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
** Attachment added: the svn change which is already using in hardy
http://launchpadlibrarian.net/12083923/92_from_svn_no_buggy_signal_handler.patch
** Description changed:
- Binary package hint: nautilus
-
- When I log on as user A, log out and log in as user B, the processor
- remains in
@ Sebastien Basher:
Thank you very much Sebastien. I was about to post my PPA's link, in which
I've put your patched version of Nautilus to make it available for wide
testing, for I'm using it since the beggining of December without an issue on
my Gutsy machine, but I guess I wont have to do
Thank you Jean, that's not required, users should rather try the gutsy
update when it'll be available
--
[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
Ah, this will stop creating the 'nautilus-debug-log.txt' files in user's
home directory? I think that's a regression we can live with, we can
always ask folks to click on the apport .crash file (which we should get
instead now). Approved, please upload.
--
[Gutsy] high processor activity after
Deleting .thumbnails folder and restarting fixed the problem for me.
--
[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.
noticed the same thing and solved it by adding a killall -9 nautilus to
/etc/gdm/PreSession/default and /etc/gdm/PostSession/default . This prevents
nautilus from chewing cycles when people are not logged in
instead of just waiting untill someone logs in again. This also works if X dies
to the Ubuntu team: may I (may we) help you to resolve this bug? Do you
need more informations?
--
[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
Did anyone notice some other simptoms beside nautilus hogging all the CPU?
Killing it in /etc/gdm/PostSession/Default solved the logout problem for me.
Today after returning from work I noticed (again) slow user switching, slow
application startup - it took 20 s to maximize pan with a lot of
I have to admit that my previous reaction was a bit over the top, for
which I apologize.
Nevertheless, I am annoyed that this confirmed critical bug isn't fixed
yet, although I posted it more than 3 months ago (October 8, 2007).
Also it irritates me, that apparently somehow the decision was made
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
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
it is indeed bugged out of the box, its a shame, same bug on all 15
computers at my work, and 3 ubuntu pc's at my home, just login from
another account while one is logged in and then log off the second user
and 100% cpu on all 18 computers I operate... Its pretty sad to have
this bug for so long
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
This problem is indeed critical.
i have this problem on old AMD CPUs.
like a Mobile AMD Sempron2.8Ghz
--
[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
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
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
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
We absolutely need a backport to Gutsy. This is a critical and totally
unacceptable bug, that chases many people away from Ubuntu. No way this
can remain unfixed. It's very unprofessional not to fix it, as well.
--
[Gutsy] high processor activity after logging out and then logging in again
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.
--
[Gutsy] high processor activity after logging out and then logging in again
By the way the issue can be re-created with Pentium 4 Hyperthreaded 3.0
ghz pc's with speed step technology, as well as P4 HT's w/o speed-step
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You received this bug notification
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:
Please people, calm down. You do not pay for this service, remember this
fact.
If you want to run a flavor which is designed to be used in professional
area, stay on LTS (ubuntu 6.06, Dapper Drake).
I'm also worried by this critical bug, but I can see devs are aware and
working on it.
Do not
I have to agree with Jordan here. If Ubuntu is such a high priority for
your company, you may want to consider working with the repositories
more closely, paying for support, or sticking with the more supported
versions.
I don't think calming down is the right advice though. Your
enthusiasm is
ok I have this issue as well, here is some lsof usage of the user kim on my
system after logging her off, keep in mind all processes should be killed after
logoff, hopefully this will shed some light...
[EMAIL PROTECTED]:~$ sudo lsof | grep -i kim lsof-nautilus.txt
[EMAIL PROTECTED]:~$ mousepad
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
OK,
I discovered that my investigation wasn't finished when I red the first
comment of this bug and followed the links deeply, it is very important:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/150471/comments/1
So following Ubuntu advises, I made scripts that debug everything, from
I can reproduce nautilus fault any time I want.
This is the procedure:
Preparation {
-Copy, to a temporary directory, 2 copies of $HOME/.local
~/Temp/.local1
~/Temp/.local2
-Make sure ~/Temp/.local?/share/applications have al least 250 *.desktop
files (Make copies to increase
I can reproduce nautilus fault any time I want.
Sorry, small mistake because of hasty typing.
Here it goes again:
This is the procedure:
Preparation {
-Copy, to a temporary directory, 2 copies of $HOME/.local
~/Temp/.local1
~/Temp/.local2
-Make sure ~/Temp/.local?/share/applications
I did it again!
This time I used (like the first time) directories full of *.desktop files.
After copying and changing ownership of a bunch of files (procedure described
in earlier messages), nautilus went crazy again. It did not happen the first
time, I had to repeat the trick 3 or 4 times.
I
Where do you have a file called .gnome-system-monitor.manolo ??
I can't reproduce manolo's bug with gksu (i.e everything went fine when
copying files in .local/share/applications between users and chown them
to the other user).
I have bad news Manolo:
I did a little bit of 'investigation' on
Thanks for your comments Manzano.
My .local/share/applications has 233 *.desktop files. Perhaps that is
the difference. It must be quite a job for nautilus to show and update
them all.
It seems somebody else thought of the same name. I have written XSu
myself. It is a bash shell using 'Xdialog'
By the way '.gnome-system-monitor.manolo' is in /home/manolo. I guess it
has been produced by gnome-system-monitor.
--
[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
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
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
I think nautilus has done its thing in front of my very nose!
First I want to confirm I have noticed all the symptoms mentioned here:
-Occassionally nautilus grabs almost 100% CPU.
-When I kill it, trackerd in turn grabs CPU.
-There are more chances nautilus goes berserk if it is run as root
Manolo,
You errors messages are XSu related, you should try the same thing with gksu,
not XSu.
As explained, think to open xsession-errors BEFORE reproducing the bug and
reload it each time it produce a new message.
Good luck in your investigation!
--
[Gutsy] high processor activity after
Ref: My previous comment.
Sorry I did not explain myself. XSu messages in .xsession-errors mean there
were no error messages from nautilus. It went crazy silently.
These are normal messages and they appear every time nautilus starts (Launched
by XSu).{
(nautilus:29473): GnomeUI-WARNING **:
Even if I could not reproduce the fault by copying a file from
normal_user_nautilus's window to root_user_nautilus's window and then changing
ownership of the copied file (and the directory where it resides) with 'chown
-R user:user Dir', I got some (interesting?) error messages from the
I often run file browser as root (gksu, sudo, etc), and I believe
mouting an NTFS volume does this too... This is a great point that you
add. It may be common grounds...
-Tres
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
oops, I forgot to add:
remove all content of subfolders in .thumbnails (in normal, large and fail
folders)
--
[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
Sorry, second thought of my last comment, it could be many thing in
Nautilus too.
--
[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
- Log in in one account
- Work a little bit with nautilus
- Log out
- Log in on an another account
- Nautilus is now 100% CPU
Good chances are, in this case, it's tracker
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You
Hi guys,
Since Nautilus is linked with MANY things, there are many reasons for Nautilus
to crash.
I spent hours to track this one and removed a lot of stuff before pushing the
right triger for me.
Let me ask a question to everyone:
Do you use to have the 'list view' with 'smallest icon size
If you mean, do we show detailed view, yeah, I usually do by default. I
haven't loaded the station back up at work in a while. killall nautilus
works for now lol...
-Tres
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You
It's not so complicated for me: all I have to do is open nautilus on the
secondary screen (LCD TV) and close it - it remains among the other processes
with 100% CPU usage. Usually there are two users logged on on the machine and
no one can logout without nautilus to go wild :-)
Removed tracker
I had this problem for 2-3 days, everytime I started Nautilus (within same
session, login-logout, etc).
Based on my logs (different error messages), I found other bugs related to
nautilus and tried many different things.
It was fixed when I changed in a Nautilus window (after waiting 5-10
As promised I wrote a full article about tracking a bug in Ubuntu with this bug
as example of investigation.
see my first post above for the web address.
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
You received this bug
nope, i got to the system monitor first...
hope i don't uppset any 1 for duble posting on this, i red the
instructions and i don-t think any atachments will make any deal on this
subject, after reinstalling apache2 and php5 (aka apt-get remove, apt-
get install (no dependencies erased) ) it seams
No worries. I don't think my affected system has php installed.
Cheers.
--
[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
i got this bug on kiwilinux (ubuntu 7.10), after installing apache2 and
php, i could not figure out wich one did it but i think this is an older
bug that needs to be fixed! PS: after i closed nautilus, another
application went 100% cpu but i forgat wich one, i closed it to fast, is
there any way i
If you killed it from command line, try history.
-Tres
--
[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.
--
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
Any news regarding this bug, affecting so many among us? Any patch for
gutsy users?
--
[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
I had the 100% processor problem today and it reproduced 3 times today.
I did nothinh special, the only 2 used applications in this session were:
nautilus and totem.
I just clicked much around the music files in nautilus and played a lot of
music. 10 minutes later, the CPU becomes crazy and top
I am still having this (horrible) issue as well, at multiple LTSP sites
(which effectively slows the entire lab down). I would greatly
appreciate a backport to Gutsy. It has effectively turned one of my
customers away from Linux all together - and they're strongly
considering moving their computer
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) =
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
In my case the repro was simply:
1) Install Ubuntu 7.10 from CD.
2) Log in to desktop GUI and apply available updates from notification icon.
3) Reboot and never get an interactive desktop upon GDM login while nautilus
log thrashes (text console logins work fine).
My is/was slightly different
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
--
[Gutsy] high processor activity after logging out and then logging in again
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
The easiest way I've been able to reproduce it is login to one account,
log out, login to another account, logout and keep repeating the
process. Eventually it will just happen.
--
[Gutsy] high processor activity after logging out and then logging in again
https://bugs.launchpad.net/bugs/150471
I've got exact the same problem.I have only one user account on my
laptop and I have removed Tracker two months ago and the problem still
exist. But not every day so it is difficult to find out where it come
from.
--
[Gutsy] high processor activity after logging out and then logging in again
WARNING: There are side effects to the following workaround so use with
caution.
Here's another method to clean up a users session after they log out.
Make sure you have the slay program installed and in
/etc/gdm/PostSession/Default add before exit 0:
/usr/sbin/slay -clean $USER
if you are
It is fixed in 8.04, not in 7.10. Since this bug is reported against
7.10, I think it should *not* be marked as Fix released.
--
[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
this bug don't let me update to gutsy about 20 Computers, I care for.
--
[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.
1 - 100 of 170 matches
Mail list logo
