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

Conflict between Burn My Windows and Desktop Cube #805

Closed
ChiefArug opened this issue Jan 9, 2025 · 6 comments
Closed

Conflict between Burn My Windows and Desktop Cube #805

ChiefArug opened this issue Jan 9, 2025 · 6 comments
Labels

Comments

@ChiefArug
Copy link

Extension version/Build date

0.9.6 & 2.0.3

Cinnamon version

2.0.3

Distribution

Mint 22

Graphics hardware and driver used

NVIDIA GeForce GTX 1650 MAX-Q (Mobile) and nvidia drivers 535.183.01

Extension name and maintainer

DesktopCube@yare @klangman

What happened?

When an animation from burn my windows and desktop cube play at the same time the screen turns black. Some mashing of the workspace switch keys can often fix it, but sometimes the panel dissapears and I need to restart Cinnamon with Alt + F2 -> r.

Other information

(for the seo have CinnamonBurnMyWindows@klangman too)

Note this video was recorded on my second monitor, so there is no panel anyway.

conflict_cinnamon.mp4

.xsession-errors: https://gist.github.com/ChiefArug/8496116ef2d9d43ea0e3298685702602

@ChiefArug ChiefArug added the BUG label Jan 9, 2025
@klangman
Copy link
Contributor

klangman commented Jan 9, 2025

Thanks for reporting the issue. I'll look into it.

@klangman
Copy link
Contributor

klangman commented Jan 9, 2025

I was not able to recreate the issue myself, but based on the exception in your xsession-errors I made a fix that should work #806

Let me know if this fix addresses the issue, thanks!

@ChiefArug
Copy link
Author

Thanks for the quick response! Unfortunately that did not fix it. New .xsession-errors: https://gist.github.com/ChiefArug/9bfedd2083e6e51b3dcee1d1c0da96c7

@klangman
Copy link
Contributor

klangman commented Jan 9, 2025

Oh.. Oops, stupid mistake. My fix was not quite right. I'll do a better job later tonight.

@klangman
Copy link
Contributor

Ok.. 2nd attempt to fix this is in #807

@ChiefArug
Copy link
Author

Awesome, that fixed it! Thank you!

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

2 participants