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 729777 - CSD context menu doesn't use _NET_DESKTOP_NAMES
CSD context menu doesn't use _NET_DESKTOP_NAMES
Status: RESOLVED DUPLICATE of bug 729780
Product: gtk+
Classification: Platform
Component: Widget: Other
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: CSD
 
 
Reported: 2014-05-08 06:14 UTC by Martin Gräßlin
Modified: 2014-06-25 14:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Martin Gräßlin 2014-05-08 06:14:51 UTC 
In the context menu on the window decoration the "Move to another Workspace" menu contains names like "Workspace 1", "Workspace 2" etc. This menu should show the names specified in _NET_DESKTOP_NAMES. Note: in Plasma it's not a "Workspace" but a "Desktop"

Steps to reproduce:
1. Use KWin
2. Configure Desktop names in kcmshell4 desktop
3. Start gtk3-demo (3.12.1)
4. Right click on decoration
5. Open "Move to another Workspace"

Actual Result:
Names are called "Workspace 1", "Workspace 2" etc

Expected Result:
Names are like previously configured

for reference:
xprop -root | grep _NET_DESKTOP_NAMES
_NET_DESKTOP_NAMES(UTF8_STRING) = "Desktop 1", "Desktop 2", "Desktop 3"
Comment 1 Matthias Clasen 2014-05-11 13:57:25 UTC 
I don't think this adds enough value to add api to gdk to pull these names out of the property. If would probably accept a patch that does it inside gtkwindow, in an #ifdef GDK_WINDOWING_X11 section.
Comment 2 Matthias Clasen 2014-05-11 13:58:50 UTC 
anyway, this problem will go away when we move the window menu back to the wm side in the near future
Comment 3 Martin Gräßlin 2014-05-11 14:31:58 UTC 
(In reply to comment #2)
> anyway, this problem will go away when we move the window menu back to the wm
> side in the near future

This is not a solution for our stable release 4.11 which got released last
July! We are not able to add new code for that. I do hope that you intend to
fix this regression.
Comment 4 Matthias Clasen 2014-05-11 15:44:30 UTC 
No, I don't
Comment 5 Martin Gräßlin 2014-05-11 16:13:44 UTC 
that's rather disappointing :-(
Comment 6 Jasper St. Pierre (not reading bugmail) 2014-06-25 14:23:24 UTC 
Same as bug 729780.

*** This bug has been marked as a duplicate of bug 729780 ***