Bug 1008944 - nautilus eating cpu and raising temperature
nautilus eating cpu and raising temperature
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-09-17 07:37 EDT by Germán Racca
Modified: 2015-02-17 12:13 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:13:05 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
htop showing Nautilus CPU usage (613.60 KB, image/png)
2013-09-17 07:47 EDT, Germán Racca
no flags Details

  None (edit)
Description Germán Racca 2013-09-17 07:37:30 EDT
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 Germán Racca 2013-09-17 07:47:57 EDT
Created attachment 798769 [details]
htop showing Nautilus CPU usage
Comment 2 Germán Racca 2013-09-17 07:49:44 EDT
Description of problem:

I didn't open any Nautilus window, but it is there in htop (see figure in attachment).

CPU usage was at 100% and sensors command report these values:

Adapter: Virtual device
temp1:        +97.5°C  (crit = +100.0°C)

Adapter: ISA adapter
Core 0:       +90.0°C  (high = +95.0°C, crit = +105.0°C)
Core 2:       +95.0°C  (high = +95.0°C, crit = +105.0°C)

After killing Nautilus, temperatures and cpu usage stabilized.

Version-Release number of selected component (if applicable):

How reproducible:
I don't know, Nautilus just appeared eating my CPU and raising the temperature.

Steps to Reproduce:

Actual results:
Nautilus came out of nowhere, eating CPU and raising temperature.

Expected results:
Nautilus shouldn't be opened if you don't call it.

Additional info:
$ uname -r

$ rpm -q gnome-session

$ rpm -q gnome-shell
Comment 3 Marcin Zajaczkowski 2014-01-08 15:33:26 EST
Duplicate of bug 975592?
Comment 4 Germán Racca 2014-01-28 15:38:04 EST
Maybe, but now in Fedora 20 I haven't seen this behavior anymore.
Comment 5 Fedora End Of Life 2015-01-09 14:52:11 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2015-02-17 12:13:05 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.