In Gnome 3.30 v64 sometimes stays visible in the lock screen #829
Comments
|
Closing as duplicate of #641. |
|
But this is in Manjaro. I don't use the Ubuntu dock in Manjaro and the fix that was done in #641 was done for Ubuntu dock. I don't see how I can implement the same modifications in Dash to dock itself. Any idea? |
|
I am also affected in Fedora, so I think this issue is not only about Ubuntu, so #641 should cover all distros. |
|
Hi @micheleg , sorry I can't investigate further, but I an at least confirm what others are experiencing: this bug does not only pertain to ubuntu-dock (which I don't have on my system). I have the same issue (once a day roughly) on Debian Testing, but I suspect it could be due to the GJS dependencies pulled from Sid (with mozJS 60). I'll try to attach a log next time I see this. @rugk and @rocky7x , can you confirm that the error reported is always the same? I.e. with respecct to |
|
Hi, Yes, I can confirm that the error always relates to the destroy command for transparency (at least for all instances of the error I investigated, it always related to that line if code). |
|
Hi, Same issue here. I'm running Gnome 3.30 on CentOS 7, the Ubuntu-dock fix of the other thread doesn't apply here. |
No, I don't even know how I would get to this error report. 😄 |
|
When it happens, check the journalctl for the dash-to-dock stack trace. You will see references to certain lines of code in certain files (similar to mine log in the top message of this issue) - something like this: /usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/theming.js:416 when you trace the lines of code through the files from top to bottom, by the time you get to the 5th or 6th reference, you will probably run into the code line this._transparency.destroy(); . That is what franglais125 had in mind. |
|
Anybody can post a more complete log? What is the actual error? I cannot reproduce the bug yet. |
|
Hi, I have not used the extension recently, because it annoyed me, having to deal with that, but I have turned it on now and will wait for a new occurence. Once I have it I will post the complete stack trace from the journalctl and also check for any errors in the Looking Glass. The problem is that it also happens for me sporadically, so I am not able to successfully reproduce it at will. |
|
Hi, Ok I got another instance of the failure - this is the full stack from journalctl: It seems I cannot find any other log file that would contain any mention of the error. Once it occurred I checked the Looking glass for errors, there was nothing. It seems I don't have .xsession-errors either. |
|
Just wanted to let you know that when I switched to Wayland, the bug seems to be gone. I haven't experienced it since the switch to Wayland.. |
|
I am all the time on Wayland, so this does not seem to be the reason. Maybe just a coincidence? |
|
Might be. For me it hasn't happened yet on Wayland, while on Xorg it was happening at least once a day. But, as soon as I get the occurrence on Wayland, I'll drop a message here... |
|
OK, I can now confirm that it is not Xorg/Wayland related - happened to me on Wayland as well. The error stack is the same. So this is still an open issue, not Ubuntu related. |
|
The relevant part from Basically same as what @rocky7x has posted above. gnome-shell: 3.30.2 |
In Gnome 3.30 (Manjaro 18) the version 64 sometimes stays visible in the lock screen. The stack trace points to the following lines of codes:
/usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/theming.js:416
/usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/theming.js:415
/usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/theming.js:424
/usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/theming.js:89
/usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/docking.js:456
It means that there is an issue with destroying the object with label transparency as this is the function that causes it to fail:
this._transparency.destroy();Can you please have a look what is ging wrong here?
The problem is that the issue is not reproducible always, just sometimes, but it only started with Gnome 3.30 and v64.
The text was updated successfully, but these errors were encountered: