@mate-user is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened. Thanks.

@piotrpalek is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened. The default sound system now is pulseaudio, rather than ALSA. Thanks.

Closing due to lack of response, and that the issue cannot be reproduced.

@denis is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened. Thanks.

Closing, since the user no longer uses Solus and no one was able to reproduce

Hi, dont know, I do not run Solus right now, I would guess you can close this one, since noone else except me seem to have had this issue :/

@roebotron is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

@pomah is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

@Zaff is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

If this is still an issue for you, can you please let us know what desktop environment you're running? (Plasma, Budgie, MATE or Gnome)? Thanks.

In T8061#203196, @TClark77 wrote:

I have been able to connect to calls in Element with my bluetooth earbuds without experiencing this particular issue. I've experienced a slightly different, maybe similar issue with pipewire on Plasma.

Steps to reproduce:

• Connect to bluetooth earbuds
• Use the system tray sound icon to choose the "handsfree" setting for the earbuds rather than high-fidelity (handsfree allows both mic input and audio output)
• Start Element
• Join a call

The mic input was fine, but the output volume is at 0% in the system tray volume applet. I have to manually set the output volume to something above 0% every time I have a call.

I have been able to connect to calls in Element with my bluetooth earbuds without experiencing this particular issue. I've experienced a slightly different, maybe similar issue with pipewire on Plasma.

Much appreciated - Can confirm host sees all available cpus.

https://dev.getsol.us/R3571:39fd7666ddbf3f0f2b94162273de321294e63f11 and https://dev.getsol.us/R1966:c2a30b68f7b831ec3eebdfb5a7dc159bc2403914

@acook , does this issue still happen with an up to date Solus installation? There have been many updates and bug fixes since this issue was last updated.

@moonglow , does this issue still happen with an up to date Solus ISO (4.4) and that laptop? There have been many updates and bug fixes since this issue was last updated.

This had been resolved.

Closing due to the age of the issue, and that the user account has been deleted.

Closing due to the age of the issue, and that the user account has been deleted.

Does this issue still happen with an up to date Solus installation? There have been many updates and bug fixes since this issue was last updated.

@ReillyBrogan : Do we want to switch this to 128?

@TClark77 I stopped using Solus a number of years ago due to a few of these bugs. I don't know if it is still prevalent in the modern version of the distribution. If you have access to an HDA-Intel card you might be able to test if you can open up Element or Slack and attempt a video call.

@alecbcs , @feuerstein , is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened. Thanks.

@nils, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

Update. all above activity was with X11. I just noticed that I can choose Wayland desktop instead of X11 at login on the lower left.
When I'm using Wayland the HDMI display is 100% stable. It was flickering when I was on the login screen but after I chose Wayland and logged in, the issue was resolved. This is ok to close, but If you want to further triage X11 you can keep it open and let me know if you have any updates I can test. Thanks! ~S

Full 8nstall still flickers. {F10963376}

Hi Reilly -- I tested the live ISOs with a different display and cable at work and encountered the same problems on gnome and budgie, and it seemed less dramatically flickery on kde. All attached files are at first bootup.
One other thing I did was since my work screen is in portrait orientation I changed the display config in each to portrait for the extended display and the problem seemed to go away (I did this in gnome and kde and there was still some intermittent flickering on kde)

Does KDE have the same behavior? Also does it go away if you install Solus and then update it?

@smlinux Would you mind sharing a yml file? I would be very grateful.

I also had a problem with a non-working DCP-7057R MFP.
Maked an installation package based on the official binaries from Brother.
The package includes printer and scanner drivers.

The Brother-7057R has stopped being detected and working again. The scanner is working, but the printer has disappeared from the previously installed ones. More precisely, the setting remains, but the connection does not see.

Closing as there has been no response or update in over a year.

In T10555#201776, @16CharactersWork wrote:

Well at the moment it is not so bad where it becomes unusable, but weirdly every once in a while it starts doing this.

Supplement
I don't think the DE matters as I've also tried Solus Budgie with the same result.
Also with another distro I have the same problem with kernel 6.
Therefore, I think the problem with kernel 6 is in the cooperation with my network card

Well at the moment it is not so bad where it becomes unusable, but weirdly every once in a while it starts doing this.

Yeah, that's a SATA-600 SSD.

I might be misreading it, but your dmesg output doesn't seem to actually show the issue?

dmesg
https://bpa.st/GM5B2

Thanks for the report! Your log files only seems to include /var/log/Xorg.0.log, can you upload the output of dmesg?

awesome =)

now it works fine, thanks

Will land with 6.3.6 today

Fixed in R3571:c32cd293ee7873125cb76ab9ddf803712c7acac0 (not in R1966 yet).

Does the modemmanager update help? modem-manager, version: 1.18.12, release: 19

In T10536#201352, @Jacek wrote:

Accelerometer now works on my machine, thanks!
Maybe next time you could also consider enabling all accelerometers, not just mine, like you enabled all light sensors?

Accelerometer now works on my machine, thanks!
Maybe next time you could also consider enabling all accelerometers, not just mine, like you enabled all light sensors?

Committed as part of R3571:2d13d70b1b08830992a6732143e3e9fd96f9ccf6 and R1966:57e78ecc4da60d1a76ee14822f11df2b0ee19013

I can talk to device using picocom without any problems.

Have you tried using screen to try sending AT commands to the modem manually? Similarly to this, https://unix.stackexchange.com/questions/89067/how-to-disable-pin-on-a-sim-card/313878#313878, how does it respond?

I do not think it is related to qmi or mbim driver. QMI works properly.
Problem appears when ModemManager is trying to exchagning AT commands with module through serial ttyUSB.

This appears to depend on (at least) four different components:

Thanks for responding. Will triage as Normal priority.

This should be resolved with gstreamer-vaapi 1.19.1, we're on 1.20.5 now. Feel free to reopen if still an issue.

Should be fine - but we'll test. Thanks for volunteering :D

VRR has worked fine for me for quite a while now.

Closing this as invalid as the cause (per the above comment) does not appear to be related to Solus per se.

Is this still an issue? If it is not, please close this report.

In T7686#148190, @henres wrote:

So, after some time, the problem is still the same. Nothing change from disabled the security from the bios or authorized it from bolt. Usb lost connection after some times and lan disabled after sleep. (Does not happen on Ubuntu)

I will try the firmware update this day. Hope it will fix it.

Thanks for your help

I have a feeling this can just be closed, seeing as it's a year old hardware issue, it might even have been solved by kernel updates or something.

Possibly related to LDM task in T10440

How will this affect desktops that has an Intel integrated gpu along with a dedicated gpu from another manufacturer?

On my XP 4100, the issue is that a remotely connected scanner (e.g. WiFi) cannot be detected. I must connect it via USB.