| Summary: | marco improperly renders window frames using bluecurve theme | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dennis W. Tokarski <dwt> |
| Component: | bluecurve-gtk-themes | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | rstrode |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:42:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Dennis W. Tokarski
2016-12-12 19:50:55 UTC
(In reply to Dennis W. Tokarski from comment #0) > Description of problem: > > When the bluecurve (plain or classic) theme is used, the sides and bottom of > window frames are black instead of the grey used everywhere else. > > > Version-Release number of selected component (if applicable): > > marco-1.16.0-1.fc25.x86_64 > > How reproducible: > > Always. > > Steps to Reproduce: > > 1. Install the various bluecurve theme packages, at minimum > bluecurve-gtk-themes and bluecurve-metacity-theme. > > 2. Log in and go to System=>Preferences=>Look and Feel=>Appearance. > > 3. Click on the Bluecurve theme, or click customize and select Bluecurve > or Bluecurve-classic under the Window Border tab. > > Actual results: > > Window borders have their sides and bottoms rendered in black instead of > grey. > > Expected results: > > Window borders should be rendered in the same color all the way around. See > Fedora 23 and earlier for correct behavior. Haven't tried Fedora 24 because > the installer was too broken. > > > Additional info: > > I was surprised this wasn't specifically a theme problem, but the bluecurve > packages in Fedora 25 are the ones from Fedora 23. By using rpm to erase the > marco package and forcibly replacing it with marco-1.14.2-1.fc23.x86_64.rpm, > the problem goes away. > > On a possibly related note--though I realize this is a separate question--is > it a bug that the Colors tab is missing in the customize window for > mate-appearance-properties from mate-control-center-1.16.0-1.fc25.x86_64? If > so I'll report it separately. If it was intentional, can that feature be > restored? This does not work with gtk3, so this tab is disable. > > I'm getting the general impression that much of this bumpiness is due to > mate's incremental transition from gtk2 to gtk3. Looks like bluecurve isn't ready for gtk3 (In reply to Wolfgang Ulbrich from comment #1) > (In reply to Dennis W. Tokarski from comment #0) > > Description of problem: > > > > When the bluecurve (plain or classic) theme is used, the sides and bottom of > > window frames are black instead of the grey used everywhere else. <snip> > > > > On a possibly related note--though I realize this is a separate question--is > > it a bug that the Colors tab is missing in the customize window for > > mate-appearance-properties from mate-control-center-1.16.0-1.fc25.x86_64? If > > so I'll report it separately. If it was intentional, can that feature be > > restored? > This does not work with gtk3, so this tab is disable. OK. Is this going to be the permanent state of affairs, or is that feature coming back? What I'm fearing here is that the gnome-devs' hostility toward any user configurability is so intense they're purging gtk3 of anything which would support nice features like theme tweaking. Native gnome applications like dconf-editor do not seem to respond to theme changes in any way at all, for example. Most of the available gtk3 themes are really ugly, mostly the same looking, and many, many of the are just broken. All the kool young kidz who are doing DE development these days seem to be purging end user theme control, even KDE. They (KDE) haven't done away with theme selections altogether, but it looks like they're starting to follow in gnome's footsteps. Which leaves Mate. It would be really sad to see Mate forced to go off in the same direction. > > > > I'm getting the general impression that much of this bumpiness is due to > > mate's incremental transition from gtk2 to gtk3. > > Looks like bluecurve isn't ready for gtk3 Yeah. But on a happier note--at least for now--Ubuntu Yakkity has a theme called Blubuntu which does work. Very much like Bluecurve but gtk3 ready, mostly. And it works on Fedora 25 just by copying the requisite files into /usr/share/themes. Blubuntu controls aren't very appealing and don't work with a lot of applications, but BlueMenta controls with Blubuntu window frames looks very nice. Transition periods can be hell, can't they? (In reply to Dennis W. Tokarski from comment #2) > (In reply to Wolfgang Ulbrich from comment #1) > > (In reply to Dennis W. Tokarski from comment #0) > > > Description of problem: > > > > > > When the bluecurve (plain or classic) theme is used, the sides and bottom of > > > window frames are black instead of the grey used everywhere else. > > <snip> > > > > > > > On a possibly related note--though I realize this is a separate question--is > > > it a bug that the Colors tab is missing in the customize window for > > > mate-appearance-properties from mate-control-center-1.16.0-1.fc25.x86_64? If > > > so I'll report it separately. If it was intentional, can that feature be > > > restored? > > This does not work with gtk3, so this tab is disable. > > OK. Is this going to be the permanent state of affairs, or is that feature > coming back? permanent, as css theming is to complex for this simple gui tab. > > What I'm fearing here is that the gnome-devs' hostility toward any user > configurability is so intense they're purging gtk3 of anything which would > support nice features like theme tweaking. > > Native gnome applications like dconf-editor do not seem to respond to theme > changes in any way at all, for example. Sadly, the dev started to hardcode some settings with a own css file. .....for no reason imo. > > Most of the available gtk3 themes are really ugly, mostly the same looking, > and many, many of the are just broken. I can't say that from mate-themes. > > All the kool young kidz who are doing DE development these days seem to be > purging end user theme control, even KDE. They (KDE) haven't done away with > theme selections altogether, but it looks like they're starting to follow in > gnome's footsteps. > > Which leaves Mate. It would be really sad to see Mate forced to go off in > the same direction. omg, only because we drop one feature wich is imposible to use for gtk3. .....sounds like daily mirror lies. > > > > > > > I'm getting the general impression that much of this bumpiness is due to > > > mate's incremental transition from gtk2 to gtk3. > > > > Looks like bluecurve isn't ready for gtk3 > > Yeah. > > But on a happier note--at least for now--Ubuntu Yakkity has a theme called > Blubuntu which does work. Very much like Bluecurve but gtk3 ready, mostly. > And it works on Fedora 25 just by copying the requisite files into > /usr/share/themes. Blubuntu controls aren't very appealing and don't work > with a lot of applications, but BlueMenta controls with Blubuntu window > frames looks very nice. > > Transition periods can be hell, can't they? This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |