Hi to everyone. Tagging @Wimpy here. So I thought I'd try Ubuntu MATE again in VirtualBox after having left the OS alone for a couple months or whatever. I figured that by now, maybe - just maybe - some code would've been released to fix the glaring, up-front graphical user interface bug I reported months ago (with a boundary inexplicably surrounding nearby applet icons in the taskbar when clicking on the default applets and other icons lighting up when clicking on the default applet set). But nope. Still happening. I am making this post not to shame or castigate the Ubuntu MATE team, but to express my disappointment at the lack of action about what honestly is an "in-your-face" bug that really, really, really should've been caught or addressed before release. I don't get it. One would think that sponsors or even "Patreons" would see this, and judge the team's work based on their response (or lack thereof). This could conceivably lead to lost funding should any of these people think to themselves, "The team isn't communicating nor are they fixing anything." I give up. No communication. No effort. I really dig Ubuntu MATE, and have been using another OS in its place the last couple months. I was hoping that this bug would've been fixed by now, and a hotfix issued. Nothing. Absolutely nothing. Very unfortunate. Good luck to this OS and the developers.
If the bug is reported/documented, someone will work on it.
Good things come to those who wait.
I understand that. That would be 100% fine with me if we were talking about some kind of obscure or relatively insignificant bug or whatever that can be worked around with reason. The key difference here is that what I am talking about is so obvious and "in-your-face" that it can't be ignored. It plagues the UI and in turn, the UX. Ruins the user experience.
please provide the link to the bug, thanks.
Omnimaxus
Don't even know what you're talking about. Can't see or reproduce what you are referring to.
For me a 'bug' is a program dysfunction. Not an aesthetic or look thing. If it were....then many OS out there are quite buggy.
W
It's interesting to see the difference in how much one issue can affect a user's experience versus another. I don't spend a lot of time interacting with my panel, so it would rarely impact me.
@Watford and @pavlos_kairis - the original post is here: What is this? (New bug in panel)
I think it has been registered on Ubuntu MATE Launchpad: #2078570.
A simple way to test whether this bug is present:
-
Add the inhibit applet to a MATE panel
-
Right click the inhibit applet:
-
Then left click on one of the items in the indicator applet:
If anyone wants to confirm this bug on their system and add that confirmation to Launchpad, that's one way to get more traction.
In the last few months, I've been getting a much greater appreciation for just how big and complicated the desktop projects are. This could easily take years before it is fixed.
I'm a Patreon, and I'm not at all tempted to pull my money. Ubuntu MATE ticks all the (important) boxes for me. I've been tempted to try other distributions on the side - just to see what is out there - but I spend so much time getting things done with my Ubuntu MATE system (software development, machine learning, playing games, learning video and audio production), that I never have the spare time!
Thank you to everyone. I checked the Launchpad link, and see that the bug has finally been "confirmed." Well, thank goodness for that. Hope the team can get around to fixing it. It just stupefies me how this was deemed OK to allow in the production release of 24.04. Anyway ... yeah. Don't know what more to say. Thanks again.
For a bug to be fixed prior to release, it needs to be discovered by a tester, and reported (bug tracker & ISO QA tracker for best results) with sufficient time to be fixed PRIOR to release.
If you'd like to help QA test future releases, you'd be most welcome. As with many volunteer projects, the prime limiting factor is always the lack of people volunteering to help.
There's bugs in mate-panel that are a decade old. For example, Bug #1445976 “Panel set to autohide may not always retract” : Bugs : mate-panel package : Ubuntu was reported (upstream) on July 2017, fixed in Dec 2017, then reverted in April 2018 due to a regression, since then it has gone stale.
mate-panel isn't an aberration; there are 463 confirmed bugs in gnome-panel.
It's not stupefying (to me) that these bugs are put into a release. Based on the empirical evidence - I expect them!
Some would argue that we should let competition dictate development, as it'll lead to the most efficient approach with some 'optimal' trade-off between bugs and features. Which means the bugs we see are the best we can hope for (if we live in such a perfectly competitive world). I don't particularly subscribe to that theory, however, but I'm not in a position to change anything.
I spotted the bug within a minute of first logging into Ubuntu MATE. So ... yeah.
Wow. I guess you're right. Well. Thanks, though.
I have never seen it, but I don't use the inhibit applet and I do only use the TraditionalOK theme. Every theme seems to have it's own bugs.
... and, sometimes, developers will dispute the classification as a "bug", calling it a feature instead. 
LOL but I have to agree!
Is this bug with the desktop the reason the window manager Compiz does not work properly in 24.04 Mate, where it did work properly in 22.04 Mate. I don't want to upgrade to 24.04 because of this.
No. The reason compiz "does not work properly" in 24.04 is because picom is started before compiz and conflicting with it.
Picom should not start at all
so you must disable it via mate-control-center -> autostart
(remember to tick the "show hidden" option)
b.t.w. I like your Commodore PET avatar.
( 4k RAM for the win !! )
Me neither but I can reproduce this on :
Ubuntu-MATE 22.04.5 LTS (MATE 1.26.0)
Ubuntu-MATE 24.04.1 LTS (MATE 1.26.2)
I usually don't have the inhibit-applet on the panel so I didn't notice it before, and even when installed I couldn't see it because the theme I use doesn't show it. (Ambiant-MATE-Dark).
Thanks. I tried disabling Picom but Compiz still does not work.
Desktop locks up, have to reboot back to a non-Compiz Windows Manager.
BTW, are you an old 6502 uP person? I ran a software company back in the early 1980's and wrote a several
In that case, read this thread. It contains sevral solutions:
At my technical college I started programming in hex on an 1MHz intel 8008 single board computer with an astonishing amount of 512 bytes RAM.
A few month later I started with a bit of assembly on a motorola 6800. To give an indication: it was during the golden age of the Tandy TRS 80 Model 1
Later on I did a bit of hacking on a 6502 though (Commodore 64) but I never owned one.
Those were early years you had to hand assemble code unless you had a Cross Assembler running on a Minicomputer or Mainframe. So I wrote my own resident 6502 Assembler for the Commodore PCs, Apple II, Atari, and SYM-1. Initially hand assembled it and then used it make improvements. I still recall many of the Hex Codes for 6502 instructions. I bet you do to. It was a great and magical time to be in computers.