If you look in the xpad-noone repo it was updated last week.

Just wanted to follow up on this, as I'm still not sure what the best path forward is. Do we want to add xpad-noone to xone (despite the fact that xpad-noone is _way_ out of date with the upstream xpad driver), or do we want to wait for xpad-noone to be updated?

Yes absolutely, nothing to do with this. My apologies. Looked like a similar log in my searching.

To be clear, this issue is unrelated to that and you should open a new issue instead.

It was mentioned on the forum that this might be related to the TLP upgrade. If you have TLP installed remove it and see if the issue persists.

Happen for me after updating

Thanks for trying to help.

Thanks for reporting back (and also sorry, I didn't even see your response before; I think that was the day the dev tracker server ran out of memory)

This week after update is working everything well. Thanks

"Can you check whether your ESP is big enough for the new kernel. If it's not the kernel update won't apply and thus the nvidia-driver modules won't match the kernel version."
I do not know what is ESP so i google it and according response it is connected to partitions.

Can you check whether your ESP is big enough for the new kernel. If it's not the kernel update won't apply and thus the nvidia-driver modules won't match the kernel version.
Can you try uninstalling the nvidia driver to see if it correctly boots with nouveau after the update?

Considering that Nautilus is now using libadwaita, I think this can probably get marked complete.

@Animpacz The original SDL2 issue is now closed after they've reverted a certain change, so this issue should hopefully be fixed. That fix was part of SDL 2.26.0.

Unfortunately, the maintainer of xone and xpad-noone hasn't been heard from in some time. I don't believe there was any plans to update xpad-noone.

It looks like the xpad driver has seen a bunch of changes since last they updated xpad-noone, did you happen to see if they had any intention of re-basing xpad-noone on top of the current upstream?

Yes, it's worth checking if 6.0.10 (soon 6.0.11) fixed the issue. I saw several issues from other people be resolved by 6.0.10, maybe this one did as well. If that doesn't help you can install linux-lts for now and get me the output of dmesg and lsmod.

I have an E3372 as well. On my System it works perfectly well using the latest 6.0.10 kernel.

I recently downloaded the latest version of Solus Mate (version 4.3) from the website; prior to the update, my USB Huawei e3372 detected and worked fine; however, after the update installation with the most recent kernel version (version 6.0 current), my USB modem no longer works and Solus cannot recognize it at all. I tried removing and reinserting the USB modem, but nothing happened.

The main reason I opened this task is that I'm not really sure how best to proceed here. I could have the xone build script check out a particular commit of xpad-noone, and install that alongside xone. That's probably the best idea I've had so far. Seeking advice.

Which update are we talking about here? The most recent one? When was the last time you updated before that? Are you on the linux-current kernel (IE does uname -r say 6.0.9-222.current)? Does switching to linux-lts make it start working again?

I am also updating it to 7.4.3.

i am sorry but i am not using elisa music player anymore or anything regarding linux.
but all i can say i fixed it after install kvantum manager and qt5 thing.

I can't reproduce this. Can you open a terminal, write elisa and paste the output here?

I am unsure since I have recently switched distro's to Manjaro. The problem does not occur on Manjaro with kernel 5.15.78. I guess you can close this as no one else reported the problem.

Is this still an issue with the latest 5.15?

Should be fixed when we update the ISO.

@ReillyBrogan Thank you for your hint!
I'm kinda new to Linux as a desktop, so didn't know about pipewire at all.

Yeah that'll do it. Make sure you log out and back in after running those commands.

No, I didn't try that.
Is this the proper way to do so?: Reddit

That bug mentions that this might be a pulseaudio bug, @Animpacz have you tried running pipewire as your audio server instead?

@Staudey: I can confirm, you got that right.
With the latest sdl2 version 2.24.1-30-1-x86_64 raw mouse input is fine and only audio cracks remain.

@Animpacz: Just to confirm: The original issue of heavy stuttering with raw mouse input is gone, and now the audio cracks remain, correct?

THIS PROBLEM IS NOT SOLVED!

Interesting. I have a Toshiba Satelite radius That I would dearly love this to work on as well.
I am running solus KDE and am not very computer savvy, but I have installed iio-sensor-proxy via eopkg, but dont know how to get it to work with my system. Any help would be appreciated. Thankyou

Crash should be fixed by https://dev.getsol.us/R2214:17c65b7a039bb04b1c7d3ebc603d621f41c0f7c6

$ cat trigger.odf
<iframe src='macro:Shell("firefox")'></iframe>

The current version we have in the repo: 7.4.1 is not affected. See https://cve.circl.lu/cve/CVE-2022-3140. Thanks for the concern!

M1005 MFP is on HPLIP's supported printers list, so it should work. You can try downloading and installing the binary plugin via terminal by running hp-setup.

nevermind. It says that you don't have enough privileges.

you should be able to find the setting to delete your account when you click on your profile picture and then manage.

Seems like this just requires updating gdk-pixbuf, though I’d imagine that’s easier said than done.

Nice. There have been a lot of updates to our compiler toolchain, mesa, mutter, budgie, etc. since this issue first appeared so hopefully some of that finally fixed it

As an update, I haven't experienced this issue in months now.

Actually, this is valid for us since the codecs are enabled by default for Mesa 22.1 and earlier and it's only Mesa 22.2 that exposes the option to disable them (which Fedora did). We're still going to need to make a decision here since we can't stay at 22.1 forever.

We do not have those codecs enabled. https://dev.getsol.us/source/mesalib/browse/master/package.yml so nothing changes.

Resolved in unstable. You _may_ be able to manually cherry-pick it to stable with sudo eopkg it https://packages.getsol.us/unstable/g/glib2/glib2-2.74.0-87-1-x86_64.eopkg --ignore-dependency

The issue should be resolved with R926:a9a6c568b74d.

Can replicate the issue, will take a look.

Are you running unstable currently?