X-Properties are missing and incorrect

Bug #425370 reported by Rotbart van Dainig
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
notification-daemon
Unknown
Low
notification-daemon (Ubuntu)
Incomplete
Low
A. Walton
Nominated for Karmic by Rotbart van Dainig

Bug Description

The essential X-Properties are missing or incorrect, making window-matching (Compiz, etc.) impossible.

$ xprop _NET_WM_WINDOW_TYPE | cut -d_ -f10
NORMAL

That should be: Notification

$ xprop WM_CLASS | cut -d\" -f2
<unknown>

$ xprop WM_CLASS | cut -d\" -f4
<unknown>

Those should report something at least, too.

Revision history for this message
A. Walton (awalton) wrote :

Strange, both themes included with notification-daemon properly set the hint code-wise: the "bubble" theme sets the hint by subclassing GtkWindow and sets the property at construction-time, the "standard" theme creates it directly with gtk_window_set_type_hint() when it's making the window. On X, this /should/ set _NET_WM_WINDOW_TYPE, so this might be a bug in GTK+, perhaps pertaining to the recent client-side-windows merge.

Class-hints should also be set automatically by GTK+, which is why we don't call set_role() or set_wmclass() (beyond that it's broken, deprecated and non-portable).

Then again, I have to ask, are you sure you mean notification-daemon, or did you intend to file this bug against notify-osd?

Changed in notification-daemon (Ubuntu):
assignee: nobody → A. Walton (awalton)
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Rotbart van Dainig (rotbart-van-dainig) wrote : Re: [Bug 425370] Re: X-Properties are missing and incorrect

Am Montag, den 07.09.2009, 01:16 +0000 schrieb A. Walton:
> Strange, both themes included with notification-daemon properly set the
> hint code-wise: the "bubble" theme sets the hint by subclassing
> GtkWindow and sets the property at construction-time, the "standard"
> theme creates it directly with gtk_window_set_type_hint() when it's
> making the window. On X, this /should/ set _NET_WM_WINDOW_TYPE, so this
> might be a bug in GTK+, perhaps pertaining to the recent client-side-
> windows merge.

No idea, honestly - I just noticed that window-matching didn't work
anymore and started to poke around with xprops.

> Class-hints should also be set automatically by GTK+, which is why we
> don't call set_role() or set_wmclass() (beyond that it's broken,
> deprecated and non-portable).

In Jaunty, those classes are at least set "notification-daemon", though
the type is "normal", too.

> Then again, I have to ask, are you sure you mean notification-daemon, or
> did you intend to file this bug against notify-osd?

Yes, notification-daemon indeed.

Revision history for this message
A. Walton (awalton) wrote :

Then there's almost no way it could be notification-daemon's fault, the code has changed /very/ little since Jaunty (the theme code should be 100% the same, in fact).

Probably want to look into filing this against Gtk+ over at bugzilla.gnome.org.

Revision history for this message
Rotbart van Dainig (rotbart-van-dainig) wrote :

You are right: Just cross-checked against Fedora Rawhide - it's the same there, too.

Changed in notification-daemon:
status: Unknown → New
Changed in notification-daemon:
importance: Unknown → Low
status: New → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.