[BUG]: Can't use suspend mode

[Amadoabad]

Describe the bug Open Bar is affecting the suspend mood in a weird way. Whenever I return from suspend it appears as if I logged out. so all of my open apps before suspend is closed!!

To Reproduce Steps to reproduce the behavior: Just enabling Open Bar While my laptop is returning from suspend this line flashes on a black screen before going into the log in screen "^@^@[ 3506.256865] Bluetooth: hci0: unexpexted event for opcode 0x0000" I don't know what is the problem with bluetooth since I didn't even enable it. what is worth mentioning though is that sometimes it's gonna stuck into this screen waiting for something and when I interrupt it using ctrl+c it goes to the log in screen but if I tried to log in it just takes me back again to the log in screen as if it's stuck in a loop .

I dunno if it's relative to the problem but when I disable the extension with this command running SHELL_DEBUG=all journalctl /usr/bin/{gjs,gnome-shell} -fo cat it prints this line four times in the terminal g_signal_handler_disconnect: assertion 'handler_id > 0' failed

[neuromorph]

Hello,

Open Bar is affecting the suspend mood in a weird way. Whenever I return from suspend it appears as if I logged out. so all of my open apps before suspend is closed!!

Are you using OpenBar Trilands or Candybar? There is an open bug in Gnome/Mutter that causes it to crash on screen lock if a stylesheet was applied to Top Bar or Dock. As a solution, please try this:

• Go to OpenBar installation directory - ~/.local/share/gnome-shell/extensions/openbar@neuromorph
• Open metadata.json file
• Add a comma at the end of last line and below that add this line - "session-modes": ["user", "unlock-dialog"]

This will allow the extension to run on Lock screen and can prevent the crash. Let me know if that works out for you.

"^@^@[ 3506.256865] Bluetooth: hci0: unexpexted event for opcode 0x0000" sometimes it's gonna stuck into this screen waiting for something and when I interrupt it using ctrl+c it goes to the log in screen but if I tried to log in it just takes me back again to the log in screen as if it's stuck in a loop .

This looks like some other issue, not from OpenBar.

when I disable the extension with this command running SHELL_DEBUG=all journalctl /usr/bin/{gjs,gnome-shell} -fo cat it prints this line four times in the terminal g_signal_handler_disconnect: assertion 'handler_id > 0' failed

When you disable an extension, Gnome internally first disables other extensions that were enabled after it and then re-enables them. So one of those are likely causing this error. But nothing much to worry here.

Thanks for reporting!

[Amadoabad]

Are you using OpenBar Trilands or Candybar? I'm using Trilands There is an open bug in Gnome/Mutter that causes it to crash on screen lock if a stylesheet was applied to Top Bar or Dock.

this is strange as I'm using a couple of other extensions that modify the behavior of the top bar with no problems like " Blur my shell, Just Perfection"

As a solution, please try this:

Go to OpenBar installation directory - ~/.local/share/gnome-shell/extensions/openbar@neuromorph
Open metadata.json file
Add a comma at the end of last line and below that add this line - "session-modes": ["user", "unlock-dialog"]

I've tried this but same problem. I was wondering would changing the login manager change anything?

[neuromorph]

this is strange as I'm using a couple of other extensions that modify the behavior of the top bar with no problems like " Blur my shell, Just Perfection"

Not about the behavior but any extension that adds a stylesheet affecting styles of panel. When Gnome disables them (on screen lock) it unloads the stylesheet but some references remain that cause seg-fault. You can find existing bug links and more details in these issues: #35 and #63 BTW, Ubuntu has added a patch in latest versions for this exact bug since they faced issues with their Dock.

I've tried this but same problem.

That's unfortunate! Some users had good luck with it. It can be a bit random based on all other configuration in use. Some users also had luck by using current version in GitHub or the previous commit. These changes were added in attempt to avoid the issue. More details in the issue #77 (check last few comments).

Nothing so far works for everyone to avoid the issue. This is only for Trilands or Candybar though, other variations work OK. The upstream issue needs fixing. I will try something in the meanwhile but I am quite busy at the moment. That is also the reason for the delay in response :(

Feel free to add any insights you get from trying as above.

Thanks!