The problem still persists with Kernel 5.2.13-126.

I'm not sure, I'll need to check since I no longer use this as my main system.

Is this still an issue? we've been through a lot of kernels since then.

In T8359#158168, @JoshStrobl wrote:

This is GNOME's Control Center, I would suggest filing a bug report with them. Do note however that we will be pushing out a new stack upgrade, GNOME 3.34, in the next week or two (depending on both testing locally as well as the unstable repo), so this may be resolved in that new release of GNOME Control Center. Doubtful, but worth checking regardless.

This is GNOME's Control Center, I would suggest filing a bug report with them. Do note however that we will be pushing out a new stack upgrade, GNOME 3.34, in the next week or two (depending on both testing locally as well as the unstable repo), so this may be resolved in that new release of GNOME Control Center. Doubtful, but worth checking regardless.

As I have a little bit time today, I can add the firefox settings are fine when using only one display.
If I power up second display after firefox was started with only one display, the phenomenom does not occur.

If this is behavior you are getting on both Mozilla's binaries as well as ours, I would suggest filing your issue with upstream Mozilla so they can look into the issue: https://bugzilla.mozilla.org

This isn't the bug tracker for GNOME. Report your issue at https://gitlab.gnome.org/GNOME/evince

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

https://github.com/UbuntuBudgie/budgie-extras/issues/219

They're running it with pkexec, that's what is causing the prompts. https://github.com/UbuntuBudgie/budgie-extras/blob/master/budgie-brightness-controller/src/helpers/LightHelper.vala#L142

File the issue with GNOME.

In T2532#150381, @alecbcs wrote:

It looks like the Clear Linux team is no longer interested in integrating this into clr-boot-manager.

Nothing in your mainlog and interestinglog indicating an actual error or crashing. I'd suggest filing your issue with the 0AD developers at https://trac.wildfiregames.com/

This should be reported to GNOME, it's their control center.

Closing as this is an upstream issue in network-manager-applet: https://gitlab.gnome.org/GNOME/network-manager-applet/issues/59

This is a bug in network-manager-applet: https://gitlab.gnome.org/GNOME/network-manager-applet/issues/65

Upstream issue: https://bugs.kde.org/show_bug.cgi?id=409073

Could you please let me know if the problem still occurs after doing a fill system update ?

This should be reported to GNOME.

Closing due to lack of response.

No, it isn't on our side. We ship their translations. It's on them.

In T8001#151622, @JoshStrobl wrote:

Not our responsibility. Should be filed with the KDE developers.

Not our responsibility. Should be filed with the KDE developers.

This is an issue upstream and the PR you referenced was reverted due to causing crashes. Not our responsibility.

I don't recall this being Phabricator's own development tracker. Most interactions are designed for users which are logged in.

It looks like the Clear Linux team is no longer interested in integrating this into clr-boot-manager. If all that needed, is to mount the /boot partition before running fwupd, maybe we could consider integrating this with eopkg for the time being, and then sol later on.

This is very much an upstream issue with Deepin Icon Theme. I tested it against Budgie and GNOME and both of them are missing icons, have icons with white backgrounds, etc. @kyrios123 filed an issue related to desktop icons clear back in December, see: https://github.com/linuxdeepin/deepin-icon-theme/issues/20

Is this even still an issue? We've had...I don't even know how many updates to KF5 now.

This sounds like an upstream issue with gedit and file encodings.

Traditional tray icons are handled by XEmbed and effectively each application has to construct and handle it themselves. This is not something we are responsible for fixing.

This is a known issue with Discord itself. See https://support.discordapp.com/hc/en-us/community/posts/360039152191-Linux-Update

I see, thanks. I thought it may have been something to do with how it was packaged... (I'm new to 'this' [linux] )

This is an upstream issue with speech-dispatcher: https://github.com/brailcom/speechd/issues/198

Ah, you're probably right. However I wouldn't consider this a blocker because there are lots of updates that don't require the EFI partition and it's possible to make it run without clr-boot-manager integration. Also it doesn't seem like there is much development on that front.

The only problem I see is that we don't mount the EFI partition which means the user has to do it himself when he wants to update BIOS/firmware.

I wanted to give it another try because I also really need this and I noticed that Clear Linux already has a package for it, which means that clr-boot-manager must be compatible.
TL;DR: I just updated the ME firmware of my T480s successfully.

I'm wondering whether the Chrome built is a totally different one under Solus or maybe there are any other optimizations that can be done?

@JoshStrobl It's not that speech-to-text isn't working. It is indeed working in Google Chrome under Solus but the quality of the engine is just not good and doesn't match the results I get under Windows 10 using an identical version of Google Chrome. I'm wondering whether the Chrome built is a totally different one under Solus or maybe there are any other optimizations that can be done?
@mate-user Did you compare the engine in an identical version of Google Chrome under Windows 10?

@feuerstein I tried it now in Chrome on Solus Mate, since it doesn't work in Firefox. It worked fine for me detecting English (UK). Maybe you have to change the language or it's because of your hardware ?

Is there anything that can be done about it?

This is fixed upstream https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=528871b456026e6127d95b1b2bd8e3a003dc1614 so waiting time begins to see if they backport it or we have to wait for kernel 5

In T7096#143612, @JoshStrobl wrote:

Furthermore:

You are only allowed to distribute the “Product” provided by Kingsoft as a whole on an AS IS basis. The distributed “Product” shall only be the unmodified complete (including without limitation the whole content of the attached “Kingsoft Software End-User License Agreement” (hereafter referred to as “Kingsoft EULA”)) version provided by Kingsoft that includes all copyright identification

In T7096#143611, @DataDrake wrote:

1) You shall guarantee that you will guide the third party to distribute the “Product” (including the repacked “Product”, which means that you consent to the distributing of the repacked “Product” by the third party according to the Agreement without paying any charge to you) in the way licensed in the Agreement in a lawful manner. You shall inform the third party that before first use the “Product” (including the repacked “Product”), they should send an email to Kingsoft at this e-mail address: wps_linux@kingsoft.com and filled out their relevant information (including but not limited to the name of the community, contact person, contact number and address), read through and agree to all the terms of the Agreement. Under the above-mentioned condition, the third party has the right to distribute the “Product” (including the repacked “Product”) according to the Agreement. Otherwise, any use (including without limitation repacking and distributing actions) of the “Product” (including the repacked “Product”) shall be deemed to be unauthorized use, and Kingsoft reserves the right to the legal responsibility.

Unenforceable. Still valid.

You are only allowed to distribute the “Product” provided by Kingsoft as a whole on an AS IS basis. The distributed “Product” shall only be the unmodified complete (including without limitation the whole content of the attached “Kingsoft Software End-User License Agreement” (hereafter referred to as “Kingsoft EULA”)) version provided by Kingsoft that includes all copyright identification

1) You shall guarantee that you will guide the third party to distribute the “Product” (including the repacked “Product”, which means that you consent to the distributing of the repacked “Product” by the third party according to the Agreement without paying any charge to you) in the way licensed in the Agreement in a lawful manner. You shall inform the third party that before first use the “Product” (including the repacked “Product”), they should send an email to Kingsoft at this e-mail address: wps_linux@kingsoft.com and filled out their relevant information (including but not limited to the name of the community, contact person, contact number and address), read through and agree to all the terms of the Agreement. Under the above-mentioned condition, the third party has the right to distribute the “Product” (including the repacked “Product”) according to the Agreement. Otherwise, any use (including without limitation repacking and distributing actions) of the “Product” (including the repacked “Product”) shall be deemed to be unauthorized use, and Kingsoft reserves the right to the legal responsibility.

Unenforceable. Still valid.

@DataDrake Because of that license thing? 'Cause that argument's invalid since that disputable bit is not included in the actual WPS for Linux license: https://github.com/getsolus/3rd-party/issues/9#issuecomment-459958519

No longer valid since WPS will soon be removed from 3rd-Party.

I'd suggest checking if this is still an issue in Files (Nautilus) after our GNOME 3.30 / 3.32 upgrade. If it is, file it upstream with GNOME, they're the developers.

The Bugzilla issue is actually verified closed using Firefox 65, I think that this could be closed now ?

This is solved in my system

This functionality really has to be exposed and implemented across multiple projects:

I suspect this may have something to do with the Intel video drivers

Those ABI changes are completely normal and in accordance with ones which you would see from Discord's use of Electron. I'm locking this issue, file your issue with Discord lockups with them, they are responsible for the application (we make no modification of it outside of placing the application in a designated directory).

oh yeah, 0.0.8 might be right there were 2 updates in a short time.
But the changes in https://dev.getsol.us/R628:a7b4ff48253a9876d4a20dac503553cd495e69d3 abi_used_libs, are they merged from discord or is this a solus thing?

As stated, file your issue with them.

The current latest release is 0.0.8, not 0.0.7. Additionally, Discord issues should be reported to them, not us. We have no option to rollback the client, as Discord prevents older clients from being used / connecting.

Afaict your NIC is working correctly, so most likely a bug in network manager itself. Marking as low priority since it works without changing the setting.

@DataDrake I would like to keep this open for now. I am going to do some testing during updates, and opening firefox with all extensions disabled. If I can't find any correlation, I'll take this upstream.

I don't see how this could be anything to do with the package itself. It's more likely that something in your Firefox profile is getting upgraded each time you run Firefox for the first time after an update. When that happens, it is likely messing things up. I admit there may be something we are setting in the environment that Firefox isn't expecting, but I can't tell what that might be.

This would be more appropriate to file this with Valve. We're not responsible for Steam development.

A user on Solus sub reddit has pointed out:
https://bugzilla.mozilla.org/show_bug.cgi?id=1516224

D5022 has "Fixed video stuttering on Youtube" the description doesn't really matches but ....

Here on this page you can find the supported wifi devices. If you don't find it, you have to search the internet with your chipset name and build one yourself or better you buy a device which is in the list.

We neither support out-of-tree drivers or DKMS for module rebuilds.

I've been pointed to https://github.com/tomaspinho/rtl8821ce as a solution, however that's only intended for arch linux and apparently is not a good idea for other distributions.

This card isn't supported by the kernel https://bugzilla.kernel.org/show_bug.cgi?id=201875 and requires an out-of-tree driver. I'd suggest reaching out on the bug I linked.

Happens on my Intel HD 620 laptop, and I’ve gotten word from someone using Ubuntu with Gnome 3 on the prop Nvidia drivers that it happens to them as well. Seems to be a Firefox issue, with that in mind.

Apparently I am starting well 2019, it seems that this little problem has disappeared, fixed by an update, I think

thank you for reply

They literally stated what I did. Read my statement on how our packages do not and will not manipulate the home directory.

No, it's up to you they say. https://gitlab.gnome.org/GNOME/nautilus/issues/811

Oh ok, I just asked because ubuntu budgie does it by default. Anyway filed at nautlus issues.

No, the templates are picked up in your home directory via ~/Templates. Our packages are not capable of (nor do we desire that they be capable of) manipulating your home directory.

Can't you just add that while packaging?

This should be filed with the Nautilus project: https://gitlab.gnome.org/GNOME/nautilus

I have an Intel HD laptop I can test with. I haven’t noticed this issue on there yet, but I’ll take a closer look and see if I can reproduce it.

I can confirm this issue exists. I have been able to reliably reproduce it with anything using the new W3C EME bits (Netflix). I believe it is either related to Mesa or Firefox itself. I'll need to test on an Intel system.

This is an upstream issue with GNOME Settings Daemon, whether it is a significant delay in it applying brightness or not doing so at all: https://bugzilla.gnome.org/show_bug.cgi?id=775729