[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 PostSession/Default did not do anything for me. i'm thinking perhaps gimme5 and i are seeing a different issue than this bug, but i did see the same list of lines he described here and now can't use my nautilus at all. :( -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 error : Extra content at the end of the document /sect ^ /var/lb/scrollkeeper/oc/scrollkeeper_extended_cl.xml:2777: Parse error : Extra content at the end of the document /sect ^ on the 199 updates I have listed after this fresh install... -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
** 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
(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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
** 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 any more...it crashes nicely instead :-) -- [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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 -- [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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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. -- 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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 nautilus, and close. The processor will be highly solicited. The only way to have back its ressources, is to kill the process. I think it only go through this behaviour once, afterwhat it works normally. However, the close reports always a segmentation fault (core dumped) into the terminal. Find in attachment the crash report. Be warned I cannot open it, don't know why the reports regarding nautilus can't be opened. I also attach a crash resulted from opening a second user session. ** Attachment added: _usr_bin_nautilus.1000.crash http://launchpadlibrarian.net/12135108/_usr_bin_nautilus.1000.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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
** 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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
** 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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
** 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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
** 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 a very high level of activity, almost 100 %. Top shows that - nautilus is the culprit. - - For clarity: I don't use the switch user option: this happens when I - do a clean log out and then a log in. + The signal handler user by nautilus for logging is using non signal safe + functions which creates issues, since the log are not really used anyway + the easier option is to disable logging, which has already be done in + hardy -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
@ 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 that. Anyway, if you think is a good idea to do so, please advise 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 randomly or someone does Ctrl+Alt+Backspace. Beware that if you use xdmcp or some other way of having more than one session at once then other nautilui will be killed by this . Nautilus should restart automatically for any effected user so this might not be as bad as it seems , ymmv . How about a patch ubuntu peeps ? -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 disk activity. Swap usage 1.5/2 GB :-) Sometimes nautilus from the other user hangs silently, not using any CPU, but eating a lot of RAM [EMAIL PROTECTED]:~$ free -m total used free sharedbuffers cached Mem: 2027 1976 50 0 17300 -/+ buffers/cache: 1658368 Swap: 2047 1574473 PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 14755 elly 15 0 648m 519m 11m S0 25.6 2:13.74 nautilus So, until now i have: - nautilus hanging every time i open it on the secondary screen - when logging off users (solved) - random hanging with 0% CPU usage but eating RAM Not to mention other bugs...people I'm switching back to feisty until hardy comes out, still have it on other partition... -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 to fix it only for Hardy Heron (next release) and not for Gutsy Gibbon (current release). This bug bears the stamp fixed now, but it is *not* fixed. Greetz, Pjotr. -- [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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 without a fix. Everyone is effected, ubuntu is meant for multple users but unfortunately we cannot take advantage of the linux operating system, THIS SHOULD BE LABELED CRITICAL! -- [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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
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
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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [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 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
[Bug 150471] Re: [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 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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 expect a professional (understand here correction by a week) service when you do not pay for it. Such childish comments do not help ubuntu team. -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 great. Demanding free support is putting that enthusiasm in the wrong direction. I think you'll find that if you budget the money to switch to windows, you'll get an immediate solution to switching users, along with a whole other can of worms not worth discussing here. -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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 lsof-nautilus.txt output attached [EMAIL PROTECTED]:~$ w 18:35:44 up 57 min, 2 users, load average: 3.32, 2.91, 2.68 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT kyle tty9 :0 18:080.00s 1:16m 0.14s x-session-manager kyle pts/0:0.0 18:080.00s 0.01s 0.00s w btw my cpu usage is 100% ** Attachment added: lsof-nautilus.txt http://launchpadlibrarian.net/11446809/lsof-nautilus.txt -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 one simple window, see screenshot and download them from http://blog.vocamen.com/2008/01/18/100-cpu-and-stops-before- debug-a-solution/ I hope it will help you finding Nautilus bug and others. Have a nice week end Phil -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 number).
-Open a nautilus window (normal user) in ~/Temp/.local1/share/applications
-Open a nautilus window (root user) in ~/Temp/.local2/share/applications
-Open a root terminal.
-Run gnome-system-monitor
}
Repeat 1 .. 3 times {
-In root terminal run 'chown -R user2:user2 ~/Temp/.local2' (user2:
registered user, not owner of ~/Temp/.local1).
-Select a group of files (5 or 6) in normal_user_nautilus' window for copying
(Ctrl C).
-Move to root_user_nautilus' window and copy files (Ctrl V).
!!-Very often nautilus goes crazy now -Check with gnome-system-monitor.
-Repeat in root terminal 'chown -R user2:user2 ~/Temp/.local2'
!!-Very often nautilus goes crazy now -Check with gnome-system-monitor.
}
Please try it in your systems and inform.
Notes:
-At least 250 *.desktop files in ~/Temp/.local?/share/applications.
-Repeat at least 3 times.
Saludos,
Manolo.
--
[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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 have al least 250 *.desktop
files (Make copies to increase number).
-Open a nautilus window (normal user) in ~/Temp/.local1/share/applications
-Open a nautilus window (root user) in ~/Temp/.local2/share/applications
-Open a root terminal and run 'chown -R user2:user2 ~/Temp/.local2' (user2:
registered user, not owner of ~/Temp/.local1)..
-Run gnome-system-monitor
}
Repeat 1 .. 3 times {
-Select a group of files (5 or 6) in normal_user_nautilus' window for copying
(Ctrl C).
-Move to root_user_nautilus' window and copy files (Ctrl V).
!!-Very often nautilus goes crazy now -Check with gnome-system-monitor.
-Repeat in root terminal 'chown -R user2:user2 ~/Temp/.local2'
!!-Very often nautilus goes crazy now -Check with gnome-system-monitor.
}
Please try it in your systems and inform.
Notes:
-At least 250 *.desktop files in ~/Temp/.local?/share/applications.
-Repeat at least 3 times.
Saludos,
Manolo.
--
[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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 suppose desktop files are particularly difficult to show: nautilus has
to read contents to show 'Name' and 'Icon' instead of the real file name
and default document type icon.
Next follows the relevant section of .xsession-errors (Lines not coming from
the XSu instance which launched the root_user_nautilus edited out):
{
XSu-12288. BEGIN.
XSu-12288.CmdLine: XSu DefaultFileSystemBrowser /
XSu-12288: (nautilus:12367): GnomeUI-WARNING **: While connecting to session
manager:
XSu-12288: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-12288: ** (nautilus:12367): WARNING **: No description found for mime type
x-special/socket (file is .gnome-system-monitor.manolo), please tell the
gnome-vfs mailing list.
XSu-12288: /home/common/bin/DefaultFileSystemBrowser: line 590: 12367 Killed
$Application $Options $@
XSu-12288. END.
}
As you can see nautilus went crazy again without giving any error messages.
The last line shows when I killed the rogue nautilus process (It was
originally invoked with a switchboard shell script:
DefaultFileSystemBrowser) from the root terminal.
The root_user_nautilus' window went blank like the first time.
Th mail account I used to register (several years ago) is chockful with
spam. If you want details please use glesialoAtgmailDotcom.
Saludos,
Manolo.
--
[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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 xsu: It's not updated since around 2003 (and of course, Nautilus evolved since this time) xsu is removed from debian (2004) and might be removed from hardy (https://bugs.launchpad.net/ubuntu/+source/xsu/+bug/181495) I'm sorry Manolo but it looks like you'll need to switch to another su, I encourage you to test your procedure with gksu. -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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' and 'expect' packages. I have used if for quite a long time (way before Gutsy and nautilus' craziness) without any problems. I encourage any other reader to try to reproduce the fault in the way I have. The number of *.desktop files to show may be relevant: You can copy, several times, the files you have until you have quite a bunch. Note: Don't mess your $HOME/.local directory make a copy somewhere else. Best regards, Manolo. -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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). -- [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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 (gksu).
-Nautilus writes enormous nautilus-debug-log.txt files with the useless message:
0x8177510 2008/01/14 11:18:03.2623 (USER): debug log dumped due to signal 11
Note: My system also has dual processor (Pentium IV hyperthreading) and, when
nautilus grabs the CPU, it alternates using both CPUs.
Let's go to the crime's scene:
-I had two nautilus' windows open one as normal user (manolo) and another as
root using my own version of gksu: XSu.
-One of the windows was showing /home/manolo/.local/share/applications, the
other (running as root) /home/manolo2/.local/share/applications.
-I had copied a file from first to second window.
-In a console (running as root), I then ran 'chown -R manolo2:manolo2
/home/manolo2/.local' to change ownership of the file just copied.
-Immediately the root-running nautilus' window went blank.
-I ran gnome-system-monitor and nautilus was using 80-90% CPU alternately from
each CPU.
-I found a nautilus-debug-log.txt in /root with current date-time.
-In the root console, I killed the berserk nautilus instance with 'kill -9
29473'.
Next follows the relevant part of .xsession-errors:
{
XSu-29054. BEGIN.
XSu-29054.CmdLine: XSu DefaultTerminalEmulator
XSu-29291. BEGIN.
XSu-29291.CmdLine: XSu DefaultTextEditor
XSu-29291: (gedit:29368): GnomeUI-WARNING **: While connecting to session
manager:
XSu-29291: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-29291. END.
XSu-29395. BEGIN.
XSu-29395.CmdLine: XSu DefaultFileSystemBrowser /
XSu-30705. BEGIN.
XSu-30705.CmdLine: XSu echo | DefaultTextEditor $COMMON_ETC_DIR/CommonSettings
XSu-30705: Command to run, 'echo | DefaultTextEditor
/home/common/etc/CommonSettings', not found. Aborting.
XSu-30705. END.
XSu-31072. BEGIN.
XSu-31072.CmdLine: XSu DefaultTextEditor $COMMON_ETC_DIR/CommonSettings
XSu-31072: (gedit:31149): GnomeUI-WARNING **: While connecting to session
manager:
XSu-31072: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-31072. END.
** (gnome-system-monitor:31202): WARNING **: SELinux was found but is
not enabled.
** (gnome-system-monitor:31496): WARNING **: SELinux was found but is not
enabled.
** (gnome-system-monitor:31496): CRITICAL **: Could not run gksu_run(kill -s
19 29473) : Password prompt canceled.
XSu-29395: (nautilus:29473): GnomeUI-WARNING **: While connecting to session
manager:
XSu-29395: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-29395: (gedit:29778): GnomeUI-WARNING **: While connecting to session
manager:
XSu-29395: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-29395: /home/common/bin/DefaultFileSystemBrowser: line 590: 29473 Killed
$Application $Options $@
XSu-29395. END.
}
The XSu instance running the rogue nautilus is 'XSu-29395'. Cleaned of other
irrelevant messages:
{
XSu-29395. BEGIN.
XSu-29395.CmdLine: XSu DefaultFileSystemBrowser /
** (gnome-system-monitor:31202): WARNING **: SELinux was found but is
not enabled.
** (gnome-system-monitor:31496): WARNING **: SELinux was found but is not
enabled.
** (gnome-system-monitor:31496): CRITICAL **: Could not run gksu_run(kill -s
19 29473) : Password prompt canceled.
XSu-29395: (nautilus:29473): GnomeUI-WARNING **: While connecting to session
manager:
XSu-29395: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-29395: (gedit:29778): GnomeUI-WARNING **: While connecting to session
manager:
XSu-29395: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-29395: /home/common/bin/DefaultFileSystemBrowser: line 590: 29473 Killed
$Application $Options $@
XSu-29395. END.
}
Hope it helps!
Best regards,
Manolo.
--
[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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols
specified are supported and host-based authentication failed.
}
Sad to tell, I have tried several times to reproduce the fault without any
success :-(
--
[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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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
root_user_nautilus:
{
XSu-6185. BEGIN.
XSu-6185.CmdLine: XSu DefaultFileSystemBrowser /
XSu-6185: (nautilus:6260): GnomeUI-WARNING **: While connecting to session
manager:
XSu-6185: Authentication Rejected, reason : None of the authentication
protocols specified are supported and host-based authentication failed.
XSu-6185: (nautilus:6260): Gtk-CRITICAL **: gtk_tree_model_sort_get_value:
assertion `VALID_ITER (iter, tree_model_sort)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_object_set_property:
assertion `G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_value_unset: assertion
`G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): Gtk-CRITICAL **: gtk_tree_model_sort_get_value:
assertion `VALID_ITER (iter, tree_model_sort)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_object_set_property:
assertion `G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_value_unset: assertion
`G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): Gtk-CRITICAL **: gtk_tree_model_sort_get_value:
assertion `VALID_ITER (iter, tree_model_sort)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_object_set_property:
assertion `G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_value_unset: assertion
`G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): Gtk-CRITICAL **: gtk_tree_model_sort_get_value:
assertion `VALID_ITER (iter, tree_model_sort)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_object_set_property:
assertion `G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_value_unset: assertion
`G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): Gtk-CRITICAL **: gtk_tree_model_sort_get_value:
assertion `VALID_ITER (iter, tree_model_sort)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_object_set_property:
assertion `G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): GLib-GObject-CRITICAL **: g_value_unset: assertion
`G_IS_VALUE (value)' failed
XSu-6185: (nautilus:6260): Gtk-CRITICAL **: gtk_tree_model_sort_iter_next:
assertion `tree_model_sort-stamp == iter-stamp' failed
XSu-6185: (nautilus:6260): Gtk-CRITICAL **: file
/build/buildd/gtk+2.0-2.12.0/gtk/gtktreeview.c: line 5928
(validate_visible_area): assertion `has_next' failed.
XSu-6185: There is a disparity between the internal view of the GtkTreeView,
XSu-6185: and the GtkTreeModel. This generally means that the model has changed
XSu-6185: without letting the view know. Any display from now on is likely to
XSu-6185: be incorrect.
XSu-6185: (nautilus:6260): Eel-WARNING **: nautilus-metafile.c: metafiles
hash table still has 3 elements at quit time (keys above)
XSu-6185: (nautilus:6260): Eel-WARNING **: nautilus-directory.c: directories
hash table still has 3 elements at quit time (keys above)
XSu-6185. END.
}
The above is an extract of .xsession-errors after I tried the
copying/changing_ownership trick several times. I have edited out any lines not
coming from the XSu instance which launched the root_user_nautilus.
By the way, when I changed ownership nautilus did not show the change
(once I waited a couple of minutes) in the listing of files (List view).
I had to click 'reload' to have nautilus show it right.
Saludos,
Manolo.
--
[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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
- 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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 possible' by default?? If yes, try to increase it to 'small' and give it a try. When I'll have time, I'll write a full article about it on my unbuntu blog, at blog.vocamen.com, let me know there if it worked for 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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 a long time ago since it would go crazy when nautilus was killed... Should I remove user switcher? I t tends to crash xserver from time to time... -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 minutes for the hang to stop): EditPreferencesViewsList View DefaultDefault zoom level75% (or gconf-editor appsnautiluslist_viewdefault_zoom_levelsmall if Nautilus cannot never starts) and removed 8000+ thumbnails created in .thumbnails subfolders (but I didn't removed the folders) to get back to my prefered list view at 25% (smallest). I understand that killing Nautilus is a quick fix and it worked for me too (at least when I didn't need Nautilus), but I wanted to go further to find why this bug. I found that a faulty thumbnail can lead to a non working Nautilus. I couln't check each of 8000 created thumbnails and since Nautilus re-builds thumbnails when it needs it ... In addition if you kill Nautilus at gdm session's end, you shouldn't be able to save your session state for it. You might loose this function. -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 to be working fine...hmm... -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 can view logs on my system monitor so i cand trace that out wile it is still fresh? Oh and another thing, if what i say is right, shouldn't this thread be posted as ubuntu 7.10 bugs? ty, i just hope i-m not wasting your time, i know that's verry important for all of us! -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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. -- 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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 indicates nautilus is eating 100% of my CPU. This bug seems now more important to 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 lab back to Windows. -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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) -- [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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 because it was triggered simply by logging in, not logging out and back in or by switching users. However, the symptoms were the same. I installed Debian Etch because I need a stable desktop to get work done. I was genuinely surprised this wasn't getting attention in a supported *release* version, thanks. -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [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 certain that nautilus is the only app hanging, instead use: /usr/bin/killall nautilus -user $USER -- [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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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 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
[Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
