Solus hangs

pnbalaji1974

Hi,

I have been using Solus OS on my desktop for the past couple of months and for the most part, it is working perfectly fine. However, for the past couple of weeks, I have been experiencing an issue. Once in a while, my desktop just hangs. The mouse pointer moves, but I can't click on anything with the mouse. The keyboard doesn't work in this case and my option is to power down the desktop and reboot by pressing the power button for about 10 seconds. I am not sure what is causing this issue as this is happening completely random. I checked the dmesg output and could not find any useful information.

I am assuming that this is caused by some hardware conflicts or something like that, but I am not able to pinpoint the issue.

Can someone help?

just

pnbalaji1974 Once in a while, my desktop just hangs.

Does it happen during heavy I/O operations (copying | moving 10..50+ G of data)?

Framani

Do you have a nvidia gpu with proprietary drivers? If so, that might be the issue. I'm also struggling with that at the moment (not that often) what I'm having constant problems with is the sleep resuming issues where the screen refuses to wake up. I hope someone can fix this or guide us toward a solution.

pnbalaji1974

I don't have any nvidia or AMD cards that need proprietary drivers. Mine is an intel integrated graphics driver.

pnbalaji1974

No, it just happens at random times. However, it mostly seems to happen when I have multiple browsers open with multiple tabs. I have firefox, chrome, and brave installed and have all three browsers open most of the times,

JoshStrobl

I would try just having one of them open for a prolonged period of time. If you don't get freezes it's entirely possible that all of the browsers leveraging GPU acceleration is just too problematic on your hardware.

If the issues persist we can always try to get X.org and related logs to try to get further insight.

pnbalaji1974

I could not figure out the exact reason. However, the system got stuck today and I had to do a cold reboot. After the reboot, the first thing I tried is to run the command "sudo journalctl -xb -p err" and below are the error messages from the journal entries.

================================================================================================

`-- Logs begin at Tue 2020-04-28 07:50:21 CDT, end at Sun 2020-07-19 04:57:11 CDT. --
Jul 18 23:56:24 solus kernel: ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.OSC.CAPB], AE_ALREADY_EXISTS (20200110/dsfield-181)
Jul 18 23:56:24 solus kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20200110/dswload2-477)
Jul 18 23:56:24 solus kernel: ACPI Error: Aborting method _SB.PCI0.OSC due to previous error (AE_ALREADY_EXISTS) (20200110/psparse-529)
Jul 18 23:56:24 solus kernel: platform INT0800:00: failed to claim resource 0: [mem 0xff800000-0xffffffff]
Jul 18 23:56:24 solus kernel: acpi INT0800:00: platform device creation failed: -16
Jul 19 04:56:32 test-pc systemd-udevd[467]: /usr/lib64/udev/rules.d/51-android.rules:690 Unknown group 'adbusers', ignoring
Jul 19 04:56:41 test-pc systemd-tmpfiles[548]: Failed to copy files to /etc/issue: No such file or directory
Jul 19 04:56:47 test-pc systemd[1]: Failed to start Load AppArmor profiles.
-- Subject: A start job for unit aa-lsm-hook.service has failed
-- Defined-By: systemd

-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- A start job for unit aa-lsm-hook.service has finished with a failure.

-- The job identifier is 742 and the job result is failed.
Jul 19 04:56:58 test-pc lightdm[834]: gkr-pam: unable to locate daemon control file
Jul 19 04:56:59 test-pc lightdm[834]: gkr-pam: unable to locate daemon control file
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x50f5f0 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x50f470 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x50f470 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x7f0fe40053a0 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x7f0fe4005460 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x7f0fe40055e0 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x7f0fe40055e0 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x549220 finalized while still in-construction
Jul 19 04:57:00 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:01 test-pc mate-session[883]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x5492e0 finalized while still in-construction
Jul 19 04:57:01 test-pc mate-session[883]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is inval>
Jul 19 04:57:05 test-pc spice-vdagent[1094]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Jul 19 00:00:47 test-pc pulseaudio[1005]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did no>

`

Does any one have ideas on how to address this?