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 662264 - "System Monitor" name conflicts with KDE's "System Monitor"
"System Monitor" name conflicts with KDE's "System Monitor"
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2011-10-20 04:55 UTC by Jeremy Bicha
Modified: 2013-02-10 22:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Don't show in KDE menus since they have their own "System Monitor" (825 bytes, patch)
2012-03-11 19:16 UTC, Jeremy Bicha
committed Details | Review

Description Jeremy Bicha 2011-10-20 04:55:03 UTC
As was heavily discussed in the mega-thread a few months ago on the desktop-devel-list and kde-core-devel mailing lists, the use of the same names by GNOME & KDE for System Settings and System Monitor makes it difficult for users who happen to have both desktops installed.

KDE has a short term fix for this in their master branches by renaming System Settings to KDE System Settings when not run in the KDE desktop, and a request has been made for KDE's System Monitor to not show in GNOME's menus.

gnome-control-center has OnlyShowIn=GNOME;Unity; set.

Please use NotShowIn=KDE; in gnome-system-monitor's desktop file.
Comment 1 Jeremy Bicha 2012-03-11 19:16:41 UTC
Created attachment 209444 [details] [review]
Don't show in KDE menus since they have their own "System Monitor"
Comment 2 Robert Roth 2012-07-24 20:03:47 UTC
Review of attachment 209444 [details] [review]:

Patch looks good, simple and should work.
Comment 3 Jeremy Bicha 2012-07-24 21:22:53 UTC
Review of attachment 209444 [details] [review]:

Robert, you're not a maintainer of this package so I don't think it's appropriate for you to mark this patch as accepted-commit_now.
Comment 4 Robert Roth 2012-07-24 22:10:48 UTC
Only a maintainer can review a patch? I didn't know that. You are right, I'm not the maintainer, but a developer of System Monitor, so I don't think marking a good-looking simple patch as commit now could do any harm. 
In case only the maintainer can review patches, why do I have the possibility to do it? If I shouldn't do it, I won't do it anymore, but I think the maintainer (Chris Kuehl) doesn't mind if a patch is already reviewed, and he only has to take a quick glimpse over it and commit it.
Comment 5 Jeremy Bicha 2012-07-24 23:46:06 UTC
OK, maybe you should ask Chris if you should be added as a co-maintainer then?

Attachment 209444 [details] pushed as 97374df - Don't show in KDE menus since they have their own "System Monitor"
Comment 6 Chris Kühl 2012-07-28 11:31:35 UTC
Lets not give Robert a hard time. ;)

This is an adequate quick fix but I do think there may be a better way to do this. This patch completely hides g-s-m from the entire KDE menu where a generic name change (from 'System Monitor' to 'GNOME System Monitor' may be better), in the case we're on a non-GNOME desktop, may be better. I can very well imagine a user who has installed kde and then installed g-s-m wanting to have g-s-m show up in their menu.

...and I will be sending Robert an email in the coming days about maintainership, including a summary of conversations that are happening here at GUADEC around g-s-m.

I'm reopening for now.
Comment 7 Robert Roth 2012-07-31 22:22:08 UTC
I don't agree on calling the app 'GNOME System Monitor' as adding GNOME is against the HIG [1]:
"Do not include words like "GNOME", "X Window System", "GTK+" or other platform details in Application menu names. The user probably already knows what platform they are using, and if they don't, then application names are not the right place to inform them."
We could ask the design team to suggest some better names, as there are some plans for an updated design[2], etc., so giving a name for it would be a good start. The current gnome live design page [3] calls the (System Monitor+baobab) application 'Usage', but I don't think that's a good name.
If anyone knows who to CC for design feedback, please add to the CC list, as I couldn't find this info, my searches only revealed to start pinging on #gnome-design.

[1] http://developer.gnome.org/hig-book/3.5/desktop-application-menu.html.en#menu-item-names
[2] https://live.gnome.org/Design/Apps/Usage
[3] https://live.gnome.org/Design/Apps
Comment 8 Chris Kühl 2012-08-04 14:14:50 UTC
I'm not suggesting calling it by it's full name under GNOME, where the HIG applies. I'm saying we need it to show up some way in KDE and they don't like it being called 'System Monitor' there. Thus, under KDE it should show up as 'GNOME System Monitor.' The only way I know for this to work is to have 2 .desktop files; one using NotShowIn=KDE and the other using OnlyShowIn=KDE. Any better suggestions?
Comment 9 Matthias Clasen 2012-08-04 20:58:41 UTC
> Any better suggestions?

My suggestion would be to just not worry about this. If you install gnome + kde at the same time, you essentially have two complete operating systems at the same time, and you can probably deal with the cognitive challenge to discriminate between thing1 and thing2
Comment 10 Robert Roth 2013-02-10 01:16:23 UTC
@Matthias Clasen: basically I would agree with you, but as the original request says we should have a NotShowIn=KDE in the desktop file (this has already been implemented), right now in KDE GNOME System Monitor does not appear at all.
As changing this by removing the NotShowIn=KDE would bring up the same request again, I agree with Chris that having two desktop files would fix this, and make most people happy. Do you have anything against that solution (although your argument why we should not worry about seems valid, but contradicts the reason why this bug has been filed)?
Comment 11 Matthias Clasen 2013-02-10 18:04:18 UTC
If you think it adds value, I don't have any objections.
Comment 12 Robert Roth 2013-02-10 22:59:42 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.