** Changed in: nautilus
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27109
Title:
nautilus uses 100% cpu after closing a ssh session
To manage
Upstream says the issue is fixed in the current version
** Changed in: gvfs (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27109
Title:
Please fix this bug: http://oi49.tinypic.com/soo1nk.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27109
Title:
nautilus uses 100% cpu after closing a ssh session
To manage
** Changed in: nautilus
Importance: Unknown = High
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
I can confirm this bug. Running Ubuntu 8.04.4 (Hardy) on Toshiba
Satellite A15-S129 and HP Pavilion a400n. Regularly use File Manager
(Nautilus) via SSH between the two. After some period of inactivity,
return to find both machines at around 60% CPU.
--
nautilus uses 100% cpu after closing a ssh
I can confirm this bug, even after all this time. It drives me
absolutely bonkers and causes all sorts of problems for me. I moved the
SSH off of Nautilus and it got a bit better, but I observe the exact
same behavior when I'm connecting to FTP servers with Nautilus' ftp://
transport. It makes
Moving this to GVFS since comments in the upstream GNOME bug report indicate
that this issue is/was GVFS related; gedit is also affected.
Can anyone actually still confirm this bug after all those years?
** Package changed: nautilus (Ubuntu) = gvfs (Ubuntu)
--
nautilus uses 100% cpu after
Marking this task for Mandriva as Invalid since it's not necessary.
Please only open a new task for another project when you're actually
reporting a bug there or when it's the proper upstream of the package.
** Changed in: nautilus (Mandriva)
Status: New = Invalid
--
nautilus uses 100%
** Also affects: nautilus (Mandriva)
Importance: Undecided
Status: New
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
I think that this is not right way to handle a bug that has been
reported since three years and through even more distros releases.
I've just landed here for the first time since I'm using nautilus for
sftp and was worried by this strange cpu activity even - and especially
- after the download
Just another hint that just happened: I've tried to unmount the sftp
folder and the desktop was frozen (only, other app widows would work
normally) then all icons simply disappeared. Killing the sftp process
made reappear the desktop icons.
So maybe it a problem rather linked to the display of
We use SFTP for managing multiple websites. This is a total pain and is
making Ubuntu unusable in our core business. The bug seems to have been
in Ubuntu since January 2006 - surely there must be a fix for this
critical bug by now??? Nautilus is still consuming 100% of CPU even
after a cold
the bug is not happening to everybody and there is no clear way to
trigger it
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
Solved it we hope! Dump Nautilus; use Konqueror.
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
I have similar problem but with samba-mounts. Unfortunately I can not
reproduce, but I had two samba mounts via nautilus, one of them caused
nautilus to use 100% CPU, as unmounting reduced the cpu-usage
immediately.
--
nautilus uses 100% cpu after closing a ssh session
I am also confirming this bug, connecting to my desktop from my laptop
via Places - Connect to Server in the Gnome menu and selecting ssh and
providing the server ip (in this case 192.168.0.104 note using private
key authentication). Nautilus' CPU utilization will spike to 100%.
If I right click
I am having difficulty reproducing the bug, I never actually noticed
when it spiked, but I was checking top and noticed that nautilus was
using 100% CPU. It remained like this for several minutes until I took
the steps mentioned in the previous post (unmounted the sftp folder)
Doing that
I can also confirm this bug, using Nautilus 2.20.
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
Ok, so this bug is about two years old now.. I guess it's related to my
problem: In Edubuntu the clients connect via SSH. After people log out a
Nautilus process is sometimes left running @ 100% CPU forcing me to kill
it. It happens almost every day and slows the server (and clients) to a
crawl.
I get the same as screwITfix on gutsy. It takes about 10 seconds for
nautilus to come down from 100% CPU usage when you unmount the
connection
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member
Hi
I got the same trouble with Gutsy, but I figured out that, when I Close or
Umount the SSH connections, Nautilus comes down to normal.
It looks like Nautilus tries to keep the SSH connections alive spending 100% of
CPU power. Sad thing is, that I now always need to Reconfigure the connection
nth-ing here on Gutsy beta.
My reproduction:
1. Start nautilus on machine A
2. On machine A, have nautilus connect server (ssh) to machine B
3. Copy files from machine B to machine A
4. Turn off machine B
5. Machine A's nautilus is now stuck at 100%
What commands can I run to give more useful
On my Gutsyfied (from Feisty to Gutsy beta) Thinkpad T23 Nautilus goes
to 100% CPU when the Gnome session is terminated. Best way to see this
is to switch user from A to B, terminate user B's session and go back to
A. The CPU is pegged with user B's dying Nautilus.
Possibly related: I quite often
I just experienced this in Gutsy, so it hasn't been fixed yet...
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Triaged
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs
I am still experiencing this in Feisty.
What seems to regularly reproduce the problem for me is to delete a file
on the ssh server (from Nautilus). Shortly after Nautilus goes to 100%
CPU. I would guess that the bug stems from Nautilus assuming that the
deleted files are still there and doing an
Me to, when I shut-down the computer while ssh-ing with it nautilus gets
sick but after a while (about 10 min) nautilus is being healed and does
not consume more cpu than normal...
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug
I'll add another me too to the list.
--
nautilus uses 100% cpu after closing a ssh session
https://bugs.launchpad.net/bugs/27109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
I can also confirm this problem in Feisty on amd64. Hope it gets fixed
sometime.
--
nautilus uses 100% cpu after closing a ssh session
https://launchpad.net/bugs/27109
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I also experience this bug regularly when copying (large) files from a
NFS-mounted directory.
Nautilus consumes 80% of CPU-usage after the copy-process is finished.
I've been living with this bug for quite a while now; and I thought it would be
fixed pretty soon since the bug is listed here
I might add that similar behaviour comes up when trying to connect to a
remote ssh server fails.
1) add a remote ssh server via places
2) doubleclick the shortcut to this server via the desktop.
3) Above does not react now and then (another bug, I know)
4) Nautilus starts using 100% cpu.
The upstream bugtracker still shows this bug opened, so maybe the ftp
bug is a different one?
--
nautilus uses 100% cpu after closing a ssh session
https://launchpad.net/bugs/27109
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
i had a similar error when transfering ftp. fix was commited by irc
#nautilus user alex to cvs yesterday or the day before.
--
nautilus uses 100% cpu after closing a ssh session
https://launchpad.net/bugs/27109
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
confirmed by saad
** Changed in: nautilus (Ubuntu)
Status: Unconfirmed = Confirmed
--
nautilus uses 100% cpu after closing a ssh session
https://launchpad.net/bugs/27109
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: nautilus (Ubuntu)
Assignee: Sebastien Bacher = Ubuntu Desktop Bugs
--
nautilus uses 100% cpu after closing a ssh session
https://launchpad.net/bugs/27109
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Yes I can confirm this in both Dapper and Edgy. Whenever the network
connection between the two hosts is terminated, nautilus on the client
(the one downloading) hits 100% CPU and remains there. It's quite a
serious bug because the only way to bring back down the cpu is to do a
'killall
FYI this still happens in dapper up to date
--
nautilus uses 100% cpu after closing a ssh session
https://launchpad.net/bugs/27109
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
37 matches
Mail list logo
