- User Since
- Feb 14 2019, 12:59 AM (190 w, 1 d)
Tue, Oct 4
Thu, Sep 29
@ZachBacon already updated Evolution to 3.46.0 which contains the fix for this issue. This will be resolved as of the next sync.
FYI I'm planning on making this change after the October security release. Just so you don't think that I'm ignoring this request :)
Wed, Sep 28
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.
Sun, Sep 25
Thu, Sep 22
Fri, Sep 16
- more descriptive description
Thu, Sep 15
Wed, Sep 14
Yeah it's required for lxc/lxd as well. I'm hoping that the new kernel feature around id mapping for mounted filesystems will ultimately lead to this no longer being necessary.
Sat, Sep 10
Sep 6 2022
Aug 25 2022
Aug 23 2022
Aug 21 2022
Given that this package could be used by several other packages (systemd, libsecret, gnutls) it should probably not have a maintainers file.
I'm thinking of splitting openjfx out of the openjdk-11 package and to a new package anyway. I'll probably enable it then.
Aug 20 2022
2.24.0 didn't quite make it in before the sync, but if anyone wants to try it on stable they can run the following:
Aug 19 2022
This might be fixed by D13483 which updates the version of Electron used by Mailspring. I also undid some graphics library linking that the package was doing which none of our other Electron packages were doing (I couldn't find anything about why it was doing that in the first place, and the person who made that change no longer seems to contribute to Solus).
Aug 18 2022
Aug 15 2022
Aug 9 2022
Aug 8 2022
OK, if this is fixed upstream I don't really see the point in trying to work on pinning down exactly what fixes this. I say you (and anyone else who jumps in here with the same issue) should just use the 2.0.18 packages given that they are the newest one without issues and when we update to 2.24 (I think it's due soon) this should be fixed overall. I would expect the audio cracks in the dev build to be something that should be resolved before they do the full release.
- Add HELDBACK.md
In Wayland the window app_id needs to match the name of the desktop file in order for windows to be correctly associated. This fixes Plasma (and presumably GNOME too) so that the Element icon is shown in the top left of the title bar and directly underneath the window in the overview.
I think consistency is better, but I have no issue with that. I'm not really hunting for these, I'm just fixing them as I come across them.
Here's another one. This one is built from the most recent commit of the development branch, so this one is more likely to not work than the previous two. This one will show us if the issue has already been identified and fixed upstream (and save us a lot of work if so).
Just built packages for 2.0.18 and 2.0.20. Please try BOTH of them, and after installing each one log out and back in (just to ensure a clean state), and then test the issue.
Aug 7 2022
Aug 6 2022
Aug 4 2022
Did you test that rhythmbox-alternative-toolbar was working? That's why I didn't update this myself.
Aug 3 2022
Not golang 1.19?
Aug 2 2022
Ah, it was probably mesalib. There's something funky about eopkg's handling of the mesalib package and we've had strange issues get solved by a reinstall of the package.
No, I mean rolling back to the rel 176 right before this commit was introduced: https://dev.getsol.us/R2066:a55d0e8229446a9a09f175cced40b02db7da70f7. I mention it because that commit fixed a vaapi issue affecting old GPUs using the crocus driver and I wonder if it might be related. The bug report linked in that commit was commented on by users of sandy bridge-era GPUs, which I imagine your GPU is closely related to.
Aug 1 2022
Does rolling back mesalib help at all?
Jul 29 2022
I'm going to close this. I think everything has been tested extensively at this point and the things that have not specifically been tested are fairly unlikely to specifically have issues that the other polkit-integrating apps didn't have.
I figured it would. Go ahead and close this then (I don't have permission to do so).
Note for reviewers, the diff for that markOops patch rebase seems like it has more going on then it does but the only actual changes are to the shenandoahForwarding.inline.hpp file where I had to fix some issues that caused the build to fail to compile (which Serebit never noticed because he didn't compile with shenandoahgc enabled). I've also started the process of getting that patch upstreamed so hopefully we can drop it with 11.0.17. The change to the comment and to the make targets may make it seem like we dropped the JRE but in actuality it was built but never included as part of the install.
Jul 28 2022
@silke gave me permission to push a diff on IRC
Release notes link is broken. Not that it matters now that this has been committed.
- Change branch?
Jul 27 2022
Jul 26 2022
Jul 25 2022
Jul 24 2022
- update commit
- Update commit message