The border is essentially interrupted in those two respective areas.
Just a thought, but I think you might find greater success sharing your issues with the development team directly at
which would have eyes from all other distros looking at the issue as well.
3 Likes
There is a generous region that includes both the visual demarcation between where the window is and where it isn't, and includes some surrounding continuous neighbourhood, where the mouse cursor can hover that allows for resizing if I hold down the left mouse button whilst in this region. The visual on-screen depiction of where the window begins and ends, is about 1 pixel in width, as expected.
Did you try a different theme and experience the same problem in the end?
2 Likes
Yes, Blue Menta works fine but is unsatisfactory for other reasons.
1 Like
Somehow Wolfgang Ulbrich or someone anonymous who did not bother to leave their names for posterity managed to FUBAR it, so it should be out there.
How hard is it to protect the core code from the theme mucking up the fundamental functions such as resizing? They should not be themable/skinnable, otherwise individuals like them will silently muck things up and laugh at our efforts, from their lair.
I'm sure that the coders, who are allowed to commit code, have all been vetted by peers, before being admitted to the development teams.
So ... I have a hard time visualizing that these coders are "mucking things up" deliberately.
Everyone is doing the best they can ... with the time and skills they have.
Every organization being stretched as they are today are accepting coders with ever-narrower scope of experience, leading to the "blind-spots" identified in Johari's Window!
As Users of "Free OSS", we are considered an integral part of the informal "Verification Team". Developpers fully expect us to help them,
- in a clear specific detailed manner, documented with examples,
identify where they have done a mis-step in their coding.
Keep in mind, we are referring to team"S", meaning
- many,
- separate,
- independant,
- sharing/communicating their goals/directions/evolution as best they can, and
- sharing/communicating what they think they need to share with others (Johari is very much at work here).
Which is why I, again, encourage you to pursue matters directly with the MateTheme Team, and see where that goes, and how quickly they could resolve your issue, or clarify where the breakdown is.
2 Likes
Can you also show me the output of:
gsettings get org.mate.Marco.general theme
I assume this will show 'GreenLaguna' (assuming that's the theme you are using). FWIW - GreenLaguna and BlueMenta have the same metacity-theme-1.xml; so maybe go easy on Wolfgang Ulbrich after all.
Also, if you really do want to see who is responsible for (literally) each line of code; use the 'Blame' tab on GitHub: Blaming mate-themes/desktop-themes/GreenLaguna-border/metacity-1/metacity-theme-1.xml at master · mate-desktop/mate-themes · GitHub
2 Likes
I completely understand how frustrating it is. You're doing the best thing you can, anyway, by engaging in the feedback process and helping narrow down where the problem lies. A solution may or may not be easy, and that's a little out of your control (I am fairly sure you aren't a developer), but there are people trying.
1 Like
I envy you. You live in a wonderful world. The world in which I live mucks things up in every next release of Linux and becomes defensive when informed about that. On desktop, nothing new that is of any value appeared in Linux over the past 10 or so years. On the server, things are much better, but that is for the cloud operators only. Meanwhile, the list of things that are broken keeps growing.
I am a low-income senior!
My first exposure to Ubuntu was with Dapper Drake, because being hit by another virus with all the anti-virus installed and in effect, was the last straw for me with Windows. I have tried a few other distros, hoping to improve my experience, but always opted to stay with Ubuntu as tried and true, and UbuntuMATE as the best, in my view, and most stable!
Except for the hard-drive and external 4TB MyBook backup drive, my own computer is a home-built, under-powered, Frankenstein kludge that is over 10 years old, at risk of losing hardware support in the near future. My own experience with Linux is such that I have been just as upset and disheartened with what I "perceived" to be ill-conceived, malformed in structure or poorly deployed.
Not sure that I could, given the complete lack of knowledge about your own context, personal life or experience, venture to conceive of, let alone attempt to, opine and pass judgement about your perspective on the world and that to which you are being subjected on an ongoing basis, if not daily.
However, I have had to learn that the generous-minded contributors to the "OSS ecosystem" are doing their best, with good intentions, and that I, an "unworthy" benefactor of that generosity, needs to keep in mind that two long-standing pearls of wisdoms hold true:
-
Beggars can't be choosers!
-
You attract more (worker) bees with honey, than you do with vinagar!
In my career (multi-national corporate server-side HP-UX), I have learned that you don't even think of trying to stop a rolling freight train by raising your hand to yell "Stop!" The momentum of the huge and complex Linux ecosystem (my only desktop environment) is such that we simply cannot hold back the "drift of change" inherent in the interminable evolution that is under way.
Another pearl of wisdom is this:
- We can adapt and survive ... or ... we can stagnate and die!
So, I try as much as I can to adapt and, as with my own experience with the MateTheme package, "jump ship" by switching to a different theme that "mostly" does what I need it to do, with what is to me the least acceptable need for tweaking/customization.
Beyond that, I find that putting the issue in the "appropriate mailbox" ensures that "those who know" get to see it.
Correctly identifying that proper mailbox early has gone a long way to reducing my frustration ... because I get responses and solutions in a timeframe more in line with the timelines of my personal need. Using the right approach, the right expert will, more often than not, go out of his way to either guide you or, in many cases, give you the fix.
6 Likes
That is because the Linux development community was still in the "wild-west" mindset that nobody can tell anyone else what is "best"!
I might be wrong about this perception, but I think that the Linux Developer Community as a whole has worked thru its "steroid" phase and is now looking to triage and solidify on the "software infrastructure standards" side, if not actual number of distros which are each competing for the Community's intellectual mind-share. As the standards become ever more adopted and implemented, there will be greater opportunity for the distro-specific components to become more "cross-distro portable" than they are at this time.
What we have both experienced with the Theme aspect of GUIs is just one element among the many having to work through the rough patch of that transition. 
2 Likes
My 1st Linux was Slackware 1.0. I stayed with Slackware until the advent of RedHat.
I stayed with RedHat until it became paid and switched to Mandrake/Mandriva/Fedora/Ubuntu/Debian/CentOS and back to Fedora.
My 1st WM was FVWM until KDE became a thing.
Then KDE FUBARed itself, and I switched to Gnome2.
I stayed with Gnome2 until it was slaughtered then switched to Mate.
Yesterday I had enough up to here and am building a Slackware 15 machine with KDE. So far it looks (and sounds!) almost perfect, compared to the putrid rotten corpse that Fedora Mate spin has become. Some packages are still missing, and I am slowly working through getting/building them, but this is finally a breath of fresh air.
I hope some world leader finds courage to bring down the RedHat tower one day because that organization has become a monster and it summoned all of the world's monsters that now call themselves Fedora Project, Sauron style.
I praise your willingness, and evident progress, in conquering a completely new Distro's ecosystem. I can only wish you well and success!
For myself, Slackware represents "a bridge too far", being so different from the Debian-derived ecosystem.
It is no surprise to the RedHad distro evolutionary path ... given that they were bought out by IBM Corp!
1 Like