Open MyNameIsArko opened 2 years ago
Another crash just happened that needed reboot to be able to use my computer again Errors that I see in journalctl:
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: 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.
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: The offending callback was SourceFunc().
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:07 ADRIAN-OMEN gnome-shell[3352]: == Stack trace for context 0x556797c23170 ==
maj 11 18:02:53 ADRIAN-OMEN kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20211217/dsopcode-133)
maj 11 18:02:53 ADRIAN-OMEN kernel:
maj 11 18:02:53 ADRIAN-OMEN kernel:
Initialized Local Variables for Method [HWMC]:
maj 11 18:02:53 ADRIAN-OMEN kernel: Local0: 00000000e6f45709 <Obj> Integer 0000000000000080
maj 11 18:02:53 ADRIAN-OMEN kernel: Local1: 00000000e0b689b2 <Obj> Buffer(136) 00 00 00 00 00 00 00 00
maj 11 18:02:53 ADRIAN-OMEN kernel: Local5: 00000000946e1e25 <Obj> Integer 0000000000000000
maj 11 18:02:53 ADRIAN-OMEN kernel:
maj 11 18:02:53 ADRIAN-OMEN kernel: Initialized Arguments for Method [HWMC]: (2 arguments defined for method invocation)
maj 11 18:02:53 ADRIAN-OMEN kernel: Arg0: 00000000ca63eb0c <Obj> Integer 0000000000000003
maj 11 18:02:53 ADRIAN-OMEN kernel: Arg1: 00000000ebc0d1a8 <Obj> Buffer(144) 53 45 43 55 01 00 00 00
maj 11 18:02:53 ADRIAN-OMEN kernel:
maj 11 18:02:53 ADRIAN-OMEN kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_OPERAND_VALUE) (20211217/psparse-529)
maj 11 18:02:53 ADRIAN-OMEN kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_OPERAND_VALUE) (20211217/psparse-529)
For now I'll switch to different system, because I have important exams and need to be sure it won't crash at the wrong time. I don't feel that safe now. But I look forward to any actions taken on this bug.
Do you have the full log?
Here's full journalctl log and log created in support page. Logs I send before was logs that happen around the time crash happens. pop-support_1652441864.zip journal.zip
I'll do some more testing, but it can be possible that shell update to 42.1 fixed my issue.
Edit: It's still happening so it wasn't fixed.
Anything more that I could send or this is enough for now?
I actually never encountered the same bug as you did after since I posted my issues, even though I still use the launcher (not workspace view) very often. Could it be related to how long you open the workspace view? As organizing using the workspace view does sounds like you need to stay on the same UI for quite some time. I'm saying this because last time when I saw the similar bug (i.e. my issue), it was actually me opened the launcher and fell asleep, so the launcher actually stayed open for quite a long while (probably ard 20~30 minutes).
I mean I know nothing about fixing it, just trying to see if there's anything in common between our cases :/.
I actually never encountered the same bug as you did after since I posted my issues, even though I still use the launcher (not workspace view) very often. Could it be related to how long you open the workspace view? As organizing using the workspace view does sounds like you need to stay on the same UI for quite some time. I'm saying this because last time when I saw the similar bug (i.e. my issue), it was actually me opened the launcher and fell asleep, so the launcher actually stayed open for quite a long while (probably ard 20~30 minutes).
I mean I know nothing about fixing it, just trying to see if there's anything in common between our cases :/.
I don't know what's happening it but I use it for quick reposition. I just hit super + d, drag window and close view. And it's always happening at the first step. Sometimes when hitting super+d I immediately get this issue happening.
I have same issue on Pop!_OS 22.04 LTS
, HW: bonw14 4k display version.
(1) Issue/Bug Description:
Sometimes, when using workspaces view to manage applications it will froze and have unexpected behavior. The best outcome is when it just freeze for a little, tracing over icons in dock or on the top bar will live permament highlight. To unfreeze it I had to press win+d then nothing visually changes, but probably it exited workspaces view, then win+d again two more times to get into workspaces view again so the visually aligns and unfroze itself and then exit workspaces view. The worst outcome is when it freezes so much you can't do anything on the computer and you have to reboot. In three days of using pop os 22.04 it happened twice. I had to restore everything from unsaved changes. In journalctl when freeze happens it repeatedly spams these messages:
In another freeze this message appeared:
And when freeze happened that needed reboot, unfortunately I don't have it in my journalctl logs, but it was complaining about null object not having animations therefore it couldn't display them.
(2) Steps to reproduce (if you know): I don't know, it just happens sometimes when I'm managing my windows by workspaces view. It's also not very often. Every day when I'm using my computer for 8 hours two freezes occurs and one freeze that need reboot (3) Expected behavior: Perfectly stable system that don't freeze on workspaces view (4) Distribution (run
cat /etc/os-release
):(5) Gnome Shell version: 42.0
(6) Pop Shell version (run
apt policy pop-shell
or provide the latest commit if building locally):(7) Where was Pop Shell installed from:
Along with installation of pop os
(8) Monitor Setup (2 x 1080p, 4K, Primary(Horizontal), Secondary(Vertical), etc):
Laptop, 1x1080p
(9) Other Installed/Enabled Extensions:
GSConnect
(10) Other Notes:
Edit: Another freeze just happened and this is what I meant about permament highlight on dock And log that appeared this time: