Thanks, when I had attempted to test updating it myself, I get an error that I was not the owner (even though all I had done after modifying the package.yml was run "make", so I thought that @JoshStrobl needs to be the one updating it.

In T9252#176857, @hyphens wrote:

maybe try the -lts kernel? that worked for me: https://discuss.getsol.us/d/5518-can-t-run-away-from-freezes-forever/8

In T9252#176731, @JoshStrobl wrote:

Update: I am now seeing these issues also on 5.7.10, though a lot less often than on 5.6.19.

We don't have the 5.7 kernel as our current kernel, so I have no idea what you're talking about. That was reverted clear back in July. Your issue is not related. The first issue by @endumiuz is a CPU soft lock, there isn't really any information on it, we'd need to see if it's resolved with newer kernels when we finally upgrade to that (blocked by NVMe issues). The second issue presented by @endumiuz is, at first glance, related to a bug in Dash to Dock extension for GNOME Shell, so I would suggest they ensure they're using the default settings since they shouldn't be getting any sort if "infinite recursion" issues.

For whatever reason, I can set my laptop monitor's refresh rate to 120Hz when set below the native resolution, even though it's EDID does not list 120Hz as an option.
Could this perhaps be related?

An update on this.

Update: I am now seeing these issues also on 5.7.10, though a lot less often than on 5.6.19.

I can confirm that this is also happening to me, with a slight variation.
For me, it is only the graphics and keyboard input actions that freeze (I can toggle Num/Caps lock), on both my desktop and my laptop (recently upgraded with a new Barracuda Pro).
Additionally, the screen keeps flickering on Intel graphics.

Certainly interesting, I wonder how this stacks up to Clear Sans, especially with RTL languages.

In T8904#171584, @juliocormor wrote:

In T8904#171295, @moriel5 wrote:

@juliocormor With pleasure. I hope your issue will get resolved, though.

I'm home and trying to test your solution. I'm not sure what do you mean with "refresh XRandr's information via radeon-profile". I have radeon-profile installed but i can't find any options to do that?
Also, I think on the distros the second screen worked were using the modesetting driver for the iGPU, while in Solus the system it's using Intel driver. I have read about how to change it but I'm not sure how. If someone helps me change drivers I think the issue is solved.

That is a problem. Noted.

@juliocormor With pleasure. I hope your issue will get resolved, though.

@Darius I'm not ruling out the drivers being out of date, that happens all too often with new AMD hardware, however I said that the ISO may be corrupt, which means that no matter how many times you reflash it, you will have problems, and the only recourse is to delete it, and download it again (that was what I had to do in my case).

Thanks.

Rather late, however I had a similar issue on my desktop (not at home for the time being, and will need to repair the hard drive when I return, so no way to test anything), however by simply refreshing XRandr's information (via radeon-profile), my TV (old, low-end, with bloated capacitors, 42" 1080p non-smart TV that I got from a friend that was throwing it out after replacing it with a 4K smart TV) was instantly picked up, though I had to due this each time I connected or disconnected it to my Radeon HD6950.

I remember when I had issues installing Solus in the past, and I forget who suggested this to me (probably via IRC, since I cannot find this on the Phabricator) (I think it was either Ikey, Josh, or Drake), however perhaps your installation media got corrupted (that's what happened to me)?

This issue can be closed for now, since the current drivers lack support for UVP (more reverse engineering will need to be done with Microsoft's proprietary protocols).

Update: I have managed to get networking to work via the chroot, and update the system, however there is no change unfortunately.

I seem to have gotten myself into this predicament now, however after attempting to fix it via the means outlined in the Solus Help Center (except for updating the system, as it was already mostly up-to-date (just plasma-desktop-branding not being in the index, and I do not have that installed in any case), plus I was unable to get networking to work inside the chroot), I had managed to fix the Systemd errors, however not the fact that the system is unable to switch-root.

Now, ever since I had updated my desktop, the same thing is happening there.

This is weird, but at least things appear to be working.

Thanks, I'll take a look at them.
Update: I do not see any firmware updates for the 9260, unfortunately.

@aquasp Thanks, it appears I also had that installed.
Back when I had initially set up Solus, I installed this to provide additional codec coverage, however looking at the Arch Wiki page, it is pretty much irrelevant unless you are using Nouveau on NVidia's 900-series or newer cards, and even then, it only appears to support decoding (plus, no support by either Firefox or Chromium).
Otherwise, everything it supports seems to be supported by VA-API and/or NVidia's proprietary driver.

Sure thing:

I intend to try maintaining this package.
I'll reopen this issue if I see that I could reasonably do so.

Thanks, I was concerned whether Srain would be added due to some if it's shortcomings (which will probably be fixed), however I see we were of the same mind on this.

Added abi_symbols

@joebonrichie From what I can see from the patch notes, it looks to be pre-Gen4 graphics.

This is weird, I had noticed that lately my laptop's time and date isn't syncing for whatever reason, and I am getting the issue from time-admin brings me the same message, while gnome-control-center simply does nothing at all.

In D8295#133667, @DataDrake wrote:

In D8295#133050, @moriel5 wrote:

That's odd, abi_symbols wasn't added.

It did when I built it locally just now. Did you forget to git add?

@aquasp Yes, I do (both actually, the 32-bit package for Wine support), as well as the others (though these are more for cases where I need to boot from another PC).

Extremely late update, since I had forgotten all about it, and I'm usually not at home.
My fake "7570" has apparently gotten damaged at the same time as my DH55HC motherboard (thankfully it was just the RTC chip (on the DH55HC), and I got a new one of the same model, however I still need to find someone that will be able to help me replace it).
It still works, but not very well, with VGA having limited resolutions (up to something like 1366x768p), and ignoring the actual monitor's settings, and DVI getting a black screen, no idea about HDMI.

@DataDrake Then in that case, I'll check whether this solves the "blank screen on wake" issue that's been plaguing every PC using Intel graphics (everywhere from i3-540 to i5-6200U, including a BayTrail Celeron and an i3-3220) I had installed Solus on since kernel ~4.19 (granted, it happens much less often, and is a minor issue since I just need to switch TTYs, but it still happens,and the less bugs, the better).

@DataDrake Thanks, I see I had mixed the KMS driver with the DDX driver, and the Mesa driver with the KMS driver.
So in short, anything relying on Gen7 or older?

I'm curious, what does X-Org rely upon if you remove the driver, CPU-based graphics?

That's odd, abi_symbols wasn't added.

Updated.
Now development headers are also created.

1. Updating D8295: Update FlashROM to v1.2

Accepted.
At least we can get some ideas for a greeter in the future.

Sure thing, I'd prefer that as well.

Thanks, I did not realize that since I was using the CLI when accidentally sending this differential.

Please ignore this, I had accidentally sent this while reviewing how I need send the differential (to refresh my memory).
A proper differential will be submitted soon.

That is certainly odd.
I'm on the unstable branch, and I had no such issues, not on my 9260, nor on my AX200 (the AX200 does heat up to ~50-55 degrees occasionally, however I expect that to be due to how new it is), perhaps it is due to the fact that I was busy using my computer at the time, and did not have to time to reboot it until the issue was fixed.

It looks like at least some of the modules are licensed under the GPLv2, from what the LICENSE files in the package show, however the legal language makes it confusing as to what is open source, what is open source under an exception, and what is closed-source.

Apparently tss2-esys from tpm2-tss is now required to compile xmlb, one of fwupd's dependencies.

Thanks, that would be great.

Thanks, though I do not think that it is relevant, since my model is neither.
From dmesg, it looks like the kernel thinks it's a sonixj camera for some reason.

Hello everyone.
First, I need to apologize, since I wasn't at home half the time, and the other half I was trying to catch up with other tasks.
Second, I wish to maintain this package, however I'm not sure I'll be able to, since I shall be joining a new learning program soon, and as such, I'll be online even less. So it depends on the release cadence.

Sorry, I was on a family trip and did not have time to do anything.
I just got back ~20 minutes ago.

Sorry, I thought that this was necessary for it be accepted.
Thanks for educating me, this wont happen again from me.

It took some time, due to issues with the package.yml (I guess I cannot use more than one line, so spaces it is), but with the help of some of the veterans (such as @Girtablulu amongst others), I present my package.yml, currently on version 0.4.2 of drawing.

It appears that gcc-ada is required for Intel graphics to work on most boards when compiling CoreBoot.
So I had found when attempting to compile CoreBoot (for the first time) for my grandmother's old computer (apparently it is almost completely supported, with just a few things left which are merely untested), after building for her a new computer (AMD B450-based).

I just checked, and all is well now.

Fixed Markdown to use "-" instead of "*".

Thanks, though I am always on Unstable (on my own PCs), so I just installed it by running sudo eopkg update.
grub-customizer is working perfectly now.

Markdown corrections.

Manually doing the content of the previous commits with the help of GEdit.

Proper summarization.
Including forgotten word "patch".

Minor edit to correct test plan description (not the plan itself).

Sorry about that, I'm done with that issue since the issue must be with the files themselves (made by the owners of the packaged software (plural)), nothing wrong with Solus (though it is funny that engrampa managed to deal with them).

No problem, I already use that.

Affirmative, and generally enabled it as well.

The issue at hand is that this is not an issue with the apps themselves, but with an underlying library, and we cannot say for sure whether this only affects .deb archives, or whether this is a broader issue,

This issue seems to have returned, intermittently, on VLC 3.0.7 and 3.0.7.1.

0.3 (a.k.a. pre-0.4) is compile-only.
0.4 isn't out yet.