Open alecbcs opened 5 years ago
I'm also having this problem after installing Fortitude. My machines details are:
My SSD is encrypted with LUKS too.
At the moment, I cannot recreate it reliably but this does happen at least once a day and I can see the same set of errors messages when reviewing the output of journalctl -ra
. Below is the log:
Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:21 devuser budgie-wm[1218]: g_array_unref: assertion 'array' failed Apr 25 13:05:19 devuser budgie-panel[1226]: Window 0x3c0b010 has not been made visible in GdkSeatGrabPrepareFunc Apr 25 13:05:18 devuser budgie-panel[1226]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed Apr 25 13:05:18 devuser budgie-panel[1226]: button_wrapper_set_orient: assertion 'self != NULL' failed Apr 25 13:05:10 devuser budgie-panel[1226]: Window 0x37d7ca0 has not been made visible in GdkSeatGrabPrepareFunc
I don't have a fix for this, but you can continue working without a reboot by doing kill -9 ...
where ... is the budgie-wm process
Hello! I too have this issue on an XPS 13 (9380). It's very Random. I can't really make out a pattern. However, it does NOT happen on my desktop PC, or my other Dell hardware (well, not often enough for me to notice).
That is, the desktop and all windows (everything you can see) except the mouse, becomes un-responsive. I can still get to a TTY.
I will try get some logs, but they seem very full of nothing useful...
For me, this happens a few times a day. Quite annoying when working, because up till now I've just rebooted/restarted the session :-P @alkoclick I will try your work around!
Is there anyway I can create a useful log trace for the Devs? I really enjoy solus and would like to be able to help fix things like this.
Otherwise, Solus (Budgie) really works nicely on this little Laptop.
Hello, I can confirm this bug with Dell XPS 13 (9360) with SSD encrypted with LUKS. It started after the reinstallation to Solus 4 with whole disk encryption. There was no problem before with version 3 without disk encryption.
It is unfortunate because I really like Solus and Budgie, but this is quiet deal-breaker for me to restart sessions a few times a day and be unable to find out why is this happening.
I'd appreciate if people could list what specific applications they're using when the above mentioned issue occurred so I can see if it's specifically related to it, as I'm using Budgie across multiple systems, including one with full-disk encryption, and have not experienced any of the mentioned lockups / freezes. At the moment, the only identifiable commonality is similar hardware, so until more details are provided I'm hesitant to agree that this is a Budgie-specific issue.
Hello @JoshStrobl, anything that I can provide I shall endeavour to!
First off, I have 3 PC's that I work from, all on different hardware. This XPS Laptop is the only one that I have had the issue on (I think) and it's also the only one that wasn't upgraded from previous Solus versions. It was installed after 4 was released.
Software that was running: Mostly just chrome and chrome apps.
This happens with and without an external display connected.
I get a lot in budgie-wm logs and budgie-panel, but this happens all the time, not just when the "freeze" occurs. . .
I also haven't had the issue for a few days. but it is intermittent.
If it's only happening on XPS devices (@miraclecz mentioned using one as well), I imagine it's likely an issue with integrated graphics or the kernel rather than with Budgie. The g_array_unref is just a warning and shouldn't actually result in any segfaults or crashes. But I'll keep an eye on this one regardless.
I am having the issue as well with a ASUS B760i Gaming Mini-ITX Motherboard and i9-13900T.
I am using a KVM and maybe this is helping cause the issue (?) but It is happening consistently to me after swapping to another Linux Arch host then return to my Solus machine the mouse will move but no clicks or keyboard presses register.
Initially I suspected my KVM being faulty but it works with another Linux computer and windows just Solus where the lock up occurs with the GUI freezing.
Again just now left my Solus maching running for 5 minutes with no apps running and switched to Arch and went back and locked up and this happens every time. If I don't leave the Solus machine then there are no issues and it runs for days just fine but switch to another machine using KVM and the problem appears. Killing the budgie-wm does not seem to help me even with -9.
Log attached from latest freeze. As I can recreate at will I am happy to help debug.
Seeing this...
Aug 15 00:31:45 dreadnought budgie-panel[1373]: invalid (NULL) pointer instance Aug 15 00:31:45 dreadnought budgie-panel[1373]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Aug 15 00:31:45 dreadnought budgie-panel[1373]: gvc_mixer_stream_get_volume: assertion 'GVC_IS_MIXER_STREAM (stream)' failed Aug 15 00:31:45 dreadnought budgie-panel[1373]: gvc_mixer_stream_get_is_muted: assertion 'GVC_IS_MIXER_STREAM (stream)' failed Aug 15 00:31:45 dreadnought gsd-media-keys[1180]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed Aug 15 00:31:45 dreadnought budgie-panel[1373]: gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)' failed Aug 15 00:31:45 dreadnought budgie-panel[1373]: gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)' failed Aug 15 00:31:45 dreadnought budgie-panel[1373]: gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)' failed Aug 15 00:31:45 dreadnought budgie-panel[1373]: gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)' failed
dreadnought.log
Description
After recent updates Budgie freezes and everything except the mouse cursor locks up. The only way to fix the problem is to reboot the system. Note: the whole system isn't crashing because I am still able to switch to a different user session and use the system in a systemd multi user terminal mode.
Budgie version
10.5
Operating system
Solus 4.0 Fortitude
Steps to reproduce the issue
I haven't been able to reliably reproduce the freezes, but they happen on regular intervals every hour or so.
Actual result
Each time Budgie has frozen I have recorded the systemd journal. In every log at the same time as the Budgie freezes these lines are recorded to the journal.
Apr 23 11:08:41 axon budgie-wm[1313]: g_array_unref: assertion 'array' failed
Apr 23 11:08:41 axon budgie-wm[1313]: g_array_unref: assertion 'array' failed
Apr 23 11:08:41 axon budgie-wm[1313]: g_array_unref: assertion 'array' failed
Apr 23 11:08:41 axon budgie-wm[1313]: g_array_unref: assertion 'array' failed
Apr 23 11:08:41 axon budgie-wm[1313]: g_array_unref: assertion 'array' failed
Apr 23 11:08:41 axon budgie-wm[1313]: g_array_unref: assertion 'array' failed
Apr 23 11:08:41 axon kernel: rfkill: input handler enabled
Apr 23 11:08:41 axon systemd[1]: Started Getty on tty3.
-- Subject: Unit getty@tty3.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit getty@tty3.service has finished starting up.
--
-- The start-up result is RESULT.