Bug 15977 - abnormal use of resources under gnome ram .
Summary: abnormal use of resources under gnome ram .
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-18 21:30 CEST by Sebastien Chavaux
Modified: 2023-09-30 04:27 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
screenshot1 (104.74 KB, image/png)
2015-05-21 19:18 CEST, Sebastien Chavaux
Details
the same machine with installed kde and gnome . no crazy cpu (180.50 KB, image/png)
2015-05-21 19:26 CEST, Sebastien Chavaux
Details
screenshot3 (85.67 KB, image/png)
2015-05-21 19:52 CEST, Sebastien Chavaux
Details

Description Sebastien Chavaux 2015-05-18 21:30:02 CEST
good evening ;

Then I noticed a little problem on mageia rc5 and Gnome installation.

My proccesseurs have ram pikes consumption has regular interval (a whole second).

I noticed that if I installed kde a result and I left to go under gnome kde I have more peak consumption , and consumption returns to normal. If I return in gnome go again .

I also noticed that if I made an installation of mageia rc 5 with kde as desktop, then after the first boot I install gnome-shell , I have no worries that consumption when using a gnome session.

Desolated my English , hoping that it's pretty clear . I admit that French is not only already very clear ;-) .

thank you




Reproducible: 

Steps to Reproduce:
Comment 1 Sebastien Chavaux 2015-05-19 08:00:26 CEST
Reproducible: 
reproduced on 3 pc.
I have images of system monitor that can support my statements .
Comment 2 Sebastien Chavaux 2015-05-19 08:07:23 CEST
Steps to Reproduce:
- Install mageia rc5 with dvd conventional installation.
- Choose the Gnome desktop in the installer.
- The machine stimulus once the installation has finished , have top or observation via another monitor ...
- Installing the kde desktop
- The gnome session is closed to open a kde session
- On finding the use of resources , with top and / or monitor

As against this more worries if:
- Installing mageia rc5 with dvd conventional installation.
- The kde desktop in the installer is selected .
- The machine stimulus once the installation has finished , have top or observation via another monitor that is no exaggeration consumption.
- Installing the Gnome desktop , it closes the kde session to open a gnome session
- On finding the use of natural resources , with top and / or monitor
Sebastien Chavaux 2015-05-19 08:07:50 CEST

CC: (none) => seb95.scou

Sebastien Chavaux 2015-05-19 10:15:36 CEST

CC: seb95.scou => (none)

Comment 3 Sebastien Chavaux 2015-05-21 19:18:09 CEST
Created attachment 6602 [details]
screenshot1

the CPU goes crazy every second. The only way to not have it , is to install via the conventional DVD, as kde desktop and gnome .
Comment 4 Sebastien Chavaux 2015-05-21 19:26:41 CEST
Created attachment 6603 [details]
the same machine with installed kde and gnome . no crazy cpu

Obtained by installing mageia 5 rc with kde as desktop and install gnome
claire robinson 2015-05-21 19:49:56 CEST

CC: (none) => eeeemail, mageia, olav, tmb

Comment 5 Sebastien Chavaux 2015-05-21 19:52:00 CEST
Created attachment 6604 [details]
screenshot3
Comment 6 Sebastien Chavaux 2015-05-23 19:58:48 CEST
I just made a gnome with resettlement and more arriving to reproduce this bug , I farm.

Thank you to you

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

Samuel Verschelde 2015-06-06 16:50:33 CEST

Whiteboard: (none) => MGA5TOO

Olav Vitters 2016-09-19 10:32:58 CEST

Assignee: bugsquad => gnome

Comment 7 katnatek 2023-09-30 04:27:05 CEST
Mageia 5 is EOL, due the 7 years lack of activity i assume could be closed as old

Please Reopen if still valid on Mageia 8 or Mageia 9, versions with support

Resolution: (none) => OLD
Status: UNCONFIRMED => RESOLVED


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