search

mate-desktop / mate-menus

Library for the Desktop Menu freedesktop.org specification
https://mate-desktop.org
GNU General Public License v2.0
26 stars 22 forks source link

Mate panel (where you start apps) is crazy 2major bugs #111

Open johesch opened 2 years ago

johesch commented 2 years ago

Expected behaviour

  1. The only way that the mate-panel should change appearance, in principle, is when the user done changes to it!
  2. When you start an app from the mate-panel, the right software should be started of course

Actual behaviour

Two major bugs. One has bee discussed before I think. But these two makes me want to change Desktop-env!

  1. Mate-panel is shifting app starter icons positions ALL BY IT SELF. After you log out/in again, restarted the computer or sometimes in your current ongoing session! Completely crazy! And not acceptable! Perhaps already a bug. This bug has bee around for years and I read about it before. Why can't you fix this once and for all.
  2. Now another crazy bug appeared. It also mixes apps and app-icons in the menu. So if you click on spotify perhaps some other app i starting. This is completely stochastic! ALSO Completely crazy! And not acceptable! Makes me wonder if you test code changes at all?

Steps to reproduce the behaviour

What I have described can NOT be reproduced the way you sugest. Sorry! It is a generic bug that tends to be seen after a while. Just now as I write this text the mate LMDE main button instead starts spotify. Spotify is next to the right of the Mat LMDE main-button. And this bug is NOT a bug if I log out or restarts my computer.

You must be able use generic info. For instance when a problem comes along after a while somethin is wrong with the way variables are stored, cashing memory, tmp-variables etc. Perhaps in relation to hibernation since I use that. I can not give you any detailed steps more than this. DO you ever verify/test each other code? How do you develop? Documentation such as test protocols, design specs and test specs? How do you do your Q-job?

MATE general version

1.24.1

Package version

dpkg -l | grep -i mate-panel ii libmate-panel-applet-4-1:amd64 1.24.1-1 amd64 library for MATE Panel applets ii mate-panel 1.24.1-1 amd64 launcher and docking facility for MATE ii mate-panel-common 1.24.1-1 all launcher and docking facility for MATE (common files)

Linux Distribution

cat /etc/issue: LMDE 5 Elsie \n \l uname -a: Linux grdt01 5.10.0-16-amd64 mate-desktop/caja#1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux

Link to bugreport of your Distribution (requirement)

rbuj commented 2 years ago

Please provide the steps to reproduce your issues, and the components or applications of MATE which are involved: mozo, mate-session-properties, mate-menus, ...

lukefromdc commented 2 years ago

Panel applets (which launchers are an example of) moving or disappearing on some installations has been an intermittant problem back to GNOME 2, from which MATE was forked. Problem is nothing shows up in any of rhe logs or .xsession-errors when this happens.

Sometimes when I first start a session, nm-applet appears twice or not at all. I keep a script on the desktop with just one line killall mate-panel and use that to forcibly restart the panel when this happens. Ugly, but this sort of thing predates GNOME 2 becoming MATE and nobody has ever found the cause.

Inabillty to invoke this at will on a developer's machine further complicates all attempts to find it

johesch commented 2 years ago

Hi, and thanks for your info I just wonder what ambition the maintenance of "old gnome2 code" thats still in use is? I my mind I would try to deliver a well functioning software even if I inherited some buggy code!? But what do I know. I am more of a systems engineer that is blackbox view. This buggy behaviour has made me angry for years now. And I must say that I expect more from you guys! Could perhaps be time for re-coding it!? Other desktops seems to manage this, so.....whats the problem?

Panel applets (which launchers are an example of) moving or disappearing on some installations has been an intermittant problem back to GNOME 2, from which MATE was forked. Problem is nothing shows up in any of rhe logs or .xsession-errors when this happens. JS: Yes I know its inherited since gnome 2. But many folks love gnome 2 and NOT gnome 3 and Ubuntus "mobile phone intterface, unity". I meean thats whats keep you alive and kicking isn't it? Linux mint is a dist in the "main-button-down-left" manner that many likes. And gnome2 also was. KDE is too complicated, and all lightweight type lxde etc more tweek to handle than Mate-desktop. So Mate is my first choice but after some comments from you that maintain mate I just wonder what is your goal for all the work you do?

Sometimes when I first start a session, nm-applet appears twice or not at all. I keep a script on the desktop with just one line killall mate-panel and use that to forcibly restart the panel when this happens. Ugly, but this sort of thing predates GNOME 2 becoming MATE and nobody has ever found the cause. JS: This is not a serious solution, sorry! This should not be the way forward

Inabillty to invoke this at will on a developer's machine further complicates all attempts to find it. JS: As I said you must be able to use generic info and then check the code, and there is not always a way to reproduce a bug, sorry. Software is more complicated than that!

/Johan S

Den sön 17 juli 2022 kl 17:19 skrev Luke from DC @.***>:

Panel applets (which launchers are an example of) moving or disappearing on some installations has been an intermittant problem back to GNOME 2, from which MATE was forked. Problem is nothing shows up in any of rhe logs or .xsession-errors when this happens.

Sometimes when I first start a session, nm-applet appears twice or not at all. I keep a script on the desktop with just one line killall mate-panel and use that to forcibly restart the panel when this happens. Ugly, but this sort of thing predates GNOME 2 becoming MATE and nobody has ever found the cause.

Inabillty to invoke this at will on a developer's machine further complicates all attempts to find it

— Reply to this email directly, view it on GitHub https://github.com/mate-desktop/mate-menus/issues/111, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJBLXWUHMVM7UIMXHKKYUGTVUQQBZANCNFSM53X3WSEQ . You are receiving this because you authored the thread.Message ID: @.***>

rbuj commented 2 years ago

If you can see the Collections menu entry in your app launcher menu, try this wotkarround https://github.com/mate-desktop/mate-menus/issues/101#issuecomment-907591259. Then you can request your software distributor to disable the collections feature. https://github.com/mate-desktop/mate-menus/issues/101

the panel can include several things: the indicator applet (which has multiple implementations) the application launcher menu (which has multiple implementations: Classic Menu, Brisk menu, ... as well as they make use of other general purpose common libraries). if you don't know which component is, try to add it again to find out the name.

rbuj commented 2 years ago

The issue has nothing to do with caja.

johesch commented 2 years ago

Please describe this in blackbox. I filed a bug on the mate-menu. Caja is a file explorer. And then you close the issue on mate-panel?

/Johan S

Den mån 18 juli 2022 kl 15:36 skrev Robert Antoni Buj Gelonch < @.***>:

Closed mate-desktop/mate-menus#111 https://github.com/mate-desktop/mate-menus/issues/111 as completed.

— Reply to this email directly, view it on GitHub https://github.com/mate-desktop/mate-menus/issues/111, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJBLXWV6T2XBWGGJABAQZ6TVUVMUZANCNFSM53X3WSEQ . You are receiving this because you authored the thread.Message ID: @.***>

rbuj commented 2 years ago

Your issue has been transferred from caja to mate-menus. As far as possible open your issues in the appropriate place, do not open an issue describing several unexpected behaviours if they aren't related, open an issue for each of them.

johesch commented 2 years ago

Ok, I thought I opened it on mate-menu, and not on caja, sorry

/JS

Den mån 18 juli 2022 kl 16:01 skrev Robert Antoni Buj Gelonch < @.***>:

Your issue has been transferred from caja to mate-menus. As far as possible open your issues in the appropriate place, do not open an issue describing several unexpected behaviours if they aren't related, open an issue for each of them.

— Reply to this email directly, view it on GitHub https://github.com/mate-desktop/mate-menus/issues/111#issuecomment-1187510851, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJBLXWRNFW2NLSJBGSJQ2YTVUVPT7ANCNFSM534J2MEA . You are receiving this because you authored the thread.Message ID: @.***>

DrReD commented 2 years ago

I think the question of "moving icons" is more related to mate-panel than mate-menus.

P.S. This issue in particular was -somehow- addressed in the first gtk3 version of the gnome3-fallback panel. The icons positions where made somehow relative (to each other? idr), instead of absolutely positioned. This allowed icons-positions on the panel to survive resolution changes etc. It was not perfect, but indeed better than the gnome2 panel. This "fix" was never back-ported to mate-panel, which started from the last gnome2 gnome-panel.