Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tranparent-panels prevents access to desktop after unlocking screen #675

Open
EarlPomeroy opened this issue Jul 19, 2024 · 0 comments
Open
Labels

Comments

@EarlPomeroy
Copy link

Extension version/Build date

Version 4.0~20220727 (2024-06-24 20:47:29)

Cinnamon version

6.0.4

Distribution

21.3

Graphics hardware and driver used

NVIDIA GeForce RTX 3080 535.183.01

Extension name and maintainer

transparent-panels@germanfr @germanfr

What happened?

The problem started with a fresh install of Linux Mint 21.3. Before this, the extension was working fine, but the machine had been upgraded from previous versions of LM. When the computer is locked or becomes locked after inactivity, unlocking the machine results in a blank screen with an active cursor. CTRL + ALT + ESC will restore the desktop, which has side effects. The most notable is that external encrypted hard drives don't always mount due to keyring issues. The other more worrying problem is the .xsession-errors file grows to 10s or 100s of GBs depending on the length of time left locked. The log is filled with the lines

(cinnamon:25200): Gjs-CRITICAL **: 20:10:09.855: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.

(cinnamon:25200): Gjs-CRITICAL **: 20:10:09.855: The offending callback was SourceFunc().
== Stack trace for context 0x5953573c1280 ==

(cinnamon:25200): Gjs-CRITICAL **: 20:10:09.855: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.

(cinnamon:25200): Gjs-CRITICAL **: 20:10:09.855: The offending callback was SourceFunc().
== Stack trace for context 0x5953573c1280 ==

repeated at dozens of entries per millisecond.

Disabling or removing the extension prevents this problem.

Other information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant