Bug 76958 - transset fails to pick correct window under GNOME
Summary: transset fails to pick correct window under GNOME
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: App/other (show other bugs)
Version: 7.7 (2012.06)
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-02 17:11 UTC by Marius Gedminas
Modified: 2018-08-10 21:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marius Gedminas 2014-04-02 17:11:14 UTC
I can make windows 50% translucent in gnome-shell if I run

    xprop -f _NET_WM_WINDOW_OPACITY 32c -set _NET_WM_WINDOW_OPACITY 0x7fffffff

and click on a window, but when I try the same with

    transset 0.5

nothing appears to change (and xprop doesn't show a _NET_WM_WINDOW_OPACITY property on that window).

Running transset -v prints

    Set Property to 0.75
    Property set on: 0x104ce00

which is different from the window ID shown by xwininfo.

I've also compared transset and xprop under xtrace and saw that transset is using the wrong window ID.

Looks like x11-apps/transset/dsimple.c (Get_Window_Under_Cursor) may need to be updated to do the recursive search for a window with the WM_STATE property that is done in, e.g., x11-utils/xprop/dsimple.c (Select_Window).


Originally filed at https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1301472
Comment 1 GitLab Migration User 2018-08-10 21:35:50 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/app/transset/issues/1.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.