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 764678 - GtkListBox: Graphics artifact when setting gtk-application-prefer-dark-theme at runtime
GtkListBox: Graphics artifact when setting gtk-application-prefer-dark-theme ...
Status: RESOLVED DUPLICATE of bug 763517
Product: gtk+
Classification: Platform
Component: Widget: Other
3.20.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-04-06 12:11 UTC by Cédric Bellegarde
Modified: 2016-05-18 05:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cédric Bellegarde 2016-04-06 12:11:42 UTC
Lollypop music player provide a party mode. When user switch party mode one, lollypop switch gtk-application-prefer-dark-theme to "dark".

Since GTK 3.20, when switching to/from "dark", lollypop fails to draw GtkListBoxRow without artifacts. Switching to another window and go back to lollypop window fix the issue.
Comment 1 Cédric Bellegarde 2016-04-06 12:12:46 UTC
Here a screencast showing the issue:
https://www.youtube.com/watch?v=8BTdAGNIjhc

Does not happen with Gtk 3.18/3.16/3.14
Comment 2 Timm Bäder 2016-04-07 09:31:19 UTC
This looks like a known css cache problem, does running with GTK_DEBUG=no-css-cache fix it?
Comment 3 Cédric Bellegarde 2016-04-19 14:38:27 UTC
Yes, setting this variable fix the issue.
Comment 4 Cédric Bellegarde 2016-05-17 13:20:29 UTC
Where is original bug report ? (about cache problem?)
Comment 5 Timm Bäder 2016-05-17 17:56:14 UTC
I can only find

https://bugzilla.gnome.org/show_bug.cgi?id=764126
https://bugzilla.gnome.org/show_bug.cgi?id=763517

right now. I don't think there's a bug specifically for this problem tbh.
Comment 6 Cédric Bellegarde 2016-05-18 05:11:20 UTC

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