After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 649908 - "System" tab: merge into System Info "Overview" tab, then suppress
"System" tab: merge into System Info "Overview" tab, then suppress
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: sysinfo
3.3.x
Other Linux
: Normal minor
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 653460 689312 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-05-10 16:20 UTC by rockonthemoonfm
Modified: 2012-12-06 19:50 UTC
See Also:
GNOME target: ---
GNOME version: 3.3/3.4



Description rockonthemoonfm 2011-05-10 16:20:06 UTC
The general hw/sw information shown in System Monitor "System" tab should be merged into System info "Overview" tab in System Settings, since it's now duplicating the informations in two different, but similar, places.

- The app will just focus on monitoring and caring about system state.
- System Info will display its generic static system informations.
- System monitor code will be easier to mantain.
- could reuse the dropped code for System Settings

on more thing: "Preferences" window should follow Gnome3 new "parented windows" policy (which I love).

Hope you find it useful and agreeable.
thanks you all!
alex

screenshot attached
Comment 1 Chris Kühl 2011-05-12 22:49:59 UTC
(In reply to comment #0)
> The general hw/sw information shown in System Monitor "System" tab should be
> merged into System info "Overview" tab in System Settings, since it's now
> duplicating the informations in two different, but similar, places.
> 
> - The app will just focus on monitoring and caring about system state.
> - System Info will display its generic static system informations.
> - System monitor code will be easier to mantain.
> - could reuse the dropped code for System Settings
> 

Currently most of this information is duplicated but I'm not completely sure this is a bad thing. Maybe removal of some of the duplicate info would be appropriate but that's a separate bug. Also, I can foresee adding additional system status information (uptime, power usage, etc.) which is not duplicate information but appropriate for this tab. 

> on more thing: "Preferences" window should follow Gnome3 new "parented windows"
> policy (which I love).

Actually, looking a nautilus and GNOME Terminal, this is not the case.

> screenshot attached

No attachment but it's not needed anyways. ;)

Thanks for the bug report but I'm marking this as WONTFIX. Reopen if you think you can convince me otherwise, though.
Comment 2 Chris Kühl 2011-09-18 18:09:01 UTC
*** Bug 653460 has been marked as a duplicate of this bug. ***
Comment 3 rockonthemoonfm 2011-12-18 14:12:31 UTC
in the System Info (system settings) side they agree that the static information here are duplicated. More, this app should focus only into dynamic data. https://bugzilla.gnome.org/show_bug.cgi?id=649909 (*)
I've read this remark on many blogs and forums too.


Could be nice to suppress this tab for 3.4. Anyway there are good candidates too:
disk usage (baobab integration) https://live.gnome.org/Design/Apps/Usage
power consumption (gnome-power-manager integration) https://bugzilla.gnome.org/show_bug.cgi?id=499724

System monitor would become so a much more central piece of software in gnome environment, and I hope this will happen for real.

reopening this bug, since (*) it should have "confirmed" status too

Cheers,
alex
Comment 4 Robert Roth 2012-12-02 19:33:19 UTC
*** Bug 689312 has been marked as a duplicate of this bug. ***
Comment 5 Robert Roth 2012-12-05 12:16:57 UTC
The plan then is to drop the system tab from system monitor completely, and propose the improvements (e.g. processor naming) as patches to apply to gnome-control-center.
Comment 6 Robert Roth 2012-12-06 19:50:09 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.