Hi i already speak about my nautilus freeze, glibc error and so on in other bug report. So is there something with the following error from attached file. In gnome-monitor i also see read and write grow to 12 giga, for ```systemd --user```
in fact "JS ERROR" flood my journalctl, sometime, every minutes
You missed to attach the error output…
Created attachment 14525 [details] gnome-shell/extensions JS ERROR Here it is. I just see an explanation here : https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/445
CC: (none) => surfzoid
For info: Summary : AppIndicator/KStatusNotifierItem support for GNOME Shell Description : This extension integrates Ubuntu AppIndicators and KStatusNotifierItems (KDE's blessed successor of the systray) into GNOME Shell. You can use gnome-tweaks (additional package) or run in terminal Eric, can you also say how you are using this package? Did the error occur from when you started using it, or more recently?
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #4) > For info: > Summary : AppIndicator/KStatusNotifierItem support for GNOME Shell > Description : > This extension integrates Ubuntu AppIndicators and KStatusNotifierItems > (KDE's > blessed successor of the systray) into GNOME Shell. > You can use gnome-tweaks (additional package) or run in terminal > > Eric, can you also say how you are using this package? Did the error occur > from when you started using it, or more recently? ii d'ont really know, i just discor it now, also i did an urpme of it and use gnome-shelln-extension web page to use the last version but same issue. The ubuted link i provided say it is appindicator API badly used by other app.
Please test new gnome-shell-extension-appindicator-58-1.mga9.noarch.rpm which should fix this issue. Assigning to QA, Packages in 9/Core/Updates_testing: ====================== gnome-shell-extension-appindicator-58-1.mga9.noarch.rpm From SRPMS: gnome-shell-extension-appindicator-58-1.mga9.src.rpm
Assignee: bugsquad => qa-bugsCC: (none) => geiger.david68210
(In reply to David GEIGER from comment #6) > Please test new gnome-shell-extension-appindicator-58-1.mga9.noarch.rpm > which should fix this issue. > > > Assigning to QA, > > Packages in 9/Core/Updates_testing: > ====================== > gnome-shell-extension-appindicator-58-1.mga9.noarch.rpm > > From SRPMS: > gnome-shell-extension-appindicator-58-1.mga9.src.rpm got a not compatible with this gnome version.
So ok please test with upcoming gnome-shell-extension-appindicator-53-1.1.mga9 in Updates_testing repo.
(In reply to David GEIGER from comment #8) > So ok please test with upcoming > gnome-shell-extension-appindicator-53-1.1.mga9 in Updates_testing repo. No more JS ERR, just warning, but not sure it come from appindicator. gnome-shell[1531]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x77dc190] is on because it needs an allocation. gnome-shell[1531]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2200006 specified for 0x2200004. Thanks you David
Packages in 9/Core/Updates_testing: ====================== gnome-shell-extension-appindicator-53-1.1.mga9.noarch.rpm From SRPMS: gnome-shell-extension-appindicator-53-1.1.mga9.src.rpm
Source RPM: (none) => gnome-shell-extension-appindicator
CC: (none) => andrewsfarm
Give OK due comment#9
Keywords: (none) => advisoryWhiteboard: (none) => MGA9-64-OK
Validating.
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0137.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
Hi, bug come back, see log . urpmi gnome-shell-extension-appindicator Le paquetage gnome-shell-extension-appindicator-53-1.1.mga9.noarch est déjà installé
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
Created attachment 14536 [details] gnome-shell/extensions JS ERROR bis
This update has already been pushed. Don't we need a new bug if the issue has come back?
(In reply to Thomas Andrews from comment #16) > This update has already been pushed. Don't we need a new bug if the issue > has come back? I agree, Eric Petit please open a new bug
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
(In reply to katnatek from comment #17) > (In reply to Thomas Andrews from comment #16) > > This update has already been pushed. Don't we need a new bug if the issue > > has come back? > > I agree, Eric Petit please open a new bug What, i need to do again the same content for the same bug?
Is a(In reply to Eric Petit from comment #18) > (In reply to katnatek from comment #17) > > (In reply to Thomas Andrews from comment #16) > > > This update has already been pushed. Don't we need a new bug if the issue > > > has come back? > > > > I agree, Eric Petit please open a new bug > > What, i need to do again the same content for the same bug? I know this can bother to you but as this bug is considered as solved and advisory was published, the advisory is linked to the bug and package version, and we can't republish the advisory if the bug is solved with new version of same package or with the pubilshing of other package.