No issues (Budgie)
Sync Updates for Weeks 23 and 24, 2024
[deleted]
Great update, but the issue with Element window not being visible unless forcing Xwayland still remains.
thoughts:
arcmust've been updated my icons changed a wee bit. fine.
zed was native to xfce or lxde I forget? It's identical to gedit and could never tell them apart. I've used it when it was named xed. fork?
dragon player looks like lite fun but I have purposefully kept my budgie K-package free this year 
. Great throwback look.
EbonJaeger Mesalib was updated to 24.1.1. GNOME will now use explicit sync for Wayland-native applications for AMD and Intel GPU users. XWayland applications will have to wait for an updated XWayland, and Plasma users have to wait for Plasma 6.1
^^ this evolution is interesting. baby steps.
everything functioning fine this morning, thank you.
no issues. thanks
brent zed was native to xfce or lxde I forget? It's identical to gedit and could never tell them apart. I've used it when it was named xed. fork?
No, zed is completely unrelated to xed. It's a new editor from the creators of Atom. https://zed.dev/
As the original post here says it's native to neither XFCE or LXDE, as it was originally written for macOS. Linux support is new-ish, and work still ongoing on that front.
- Edited
'd by 
[deleted] TBH at this point I'd probably just set DISCORD_NO_WAYLAND in your .bashrc and call it a day. I haven't heard of anyone else with the issue
- Edited
The Update went mostly smooth, but after a restart all my Audio devices were not shown anymore. The issue seems to come from wireplumber-0.5.3-29 as manually installing the previous version fixes the issue for me.
This is the output of journalctl -xe | grep wireplumber with 0.5.3:
Jun 15 21:33:13 solus systemd[1159]: Started wireplumber.service - Multimedia Service Session Manager.
Jun 15 21:33:13 solus wireplumber[1681]: GLib: g_strrstr_len: assertion 'haystack != NULL' failed
Jun 15 21:33:13 solus systemd-coredump[1743]: Process 1681 (wireplumber) of user 1000 dumped core.
Stack trace of thread 1681:
#0 0x00007febb08f7885 n/a (libc.so.6 + 0x52885)
#1 0x00007febb0d36c41 wp_spa_json_is_int (libwireplumber-0.5.so.0 + 0x35c41)
#2 0x00007febb0d15b5b n/a (libwireplumber-0.5.so.0 + 0x14b5b)
#3 0x00007febb0d161f7 wp_conf_open (libwireplumber-0.5.so.0 + 0x151f7)
#4 0x00007febb0d16374 wp_conf_new_open (libwireplumber-0.5.so.0 + 0x15374)
#5 0x0000560bd5844141 n/a (wireplumber + 0x1141)
#6 0x00007febb08cf30e n/a (libc.so.6 + 0x2a30e)
#7 0x00007febb08cf3c9 __libc_start_main (libc.so.6 + 0x2a3c9)
#8 0x0000560bd58446a5 n/a (wireplumber + 0x16a5)
ELF object binary architecture: AMD x86-64MalteJoe Install wireplumber-dbginfo and then try that again. It won't fix it but it will give us a better backtrace.
- Edited
@Staudey @alfisya thanks for the info. was certainly curious
@elusian well this is the dangdest part....they were non-repo icons (oxygen-ionized) (my bad) that changed after the update. this is not supposed to happen in a million years, right? how would solus know to update that? anyway in plank the software center icon is now a bunch of tiny boxes out of proportion to the rest. Abiword may have changed color and other barely memorable stuff.
we're not even at the weird part yet. under budgie "widgets"--which are really folders and theme color I was at repo zukitre dark because I LOVE the light darks. But it was darker. strange. so I went to other "light darks" I love like pocillo and qogir etc and the seemed darker so went to arc-dark this morning since it was the lightest 'light black' I could find. even weirder is I don't remember any of those repo packages getting updated so now I must be at the point in life where I need psychotropics... .
none of this was enough to deviate my vote of 'just fine, thanks for asking' though--edit: because none of these are solus issues just me I think
No problems to report. Nice to see Zed in the repo, I am playing with it 
Good sync with no issues. The GNOME 46.2 update was especially beneficial for me because VRR seems to work properly now without any weird frame time inconsistencies. Butter smooth gaming. 
️
- Edited
ReillyBrogan There you go:
Process 1705 (wireplumber) of user 1000 dumped core.
Stack trace of thread 1705:
#0 0x00007f3d29c3b885 n/a (libc.so.6 + 0x52885)
#1 0x00007f3d2a07ac41 spa_json_parse_int (libwireplumber-0.5.so.0 + 0x35c41)
#2 0x00007f3d2a059b5b open_and_load_sections (libwireplumber-0.5.so.0 + 0x14b5b)
#3 0x00007f3d2a05a1f7 wp_conf_open (libwireplumber-0.5.so.0 + 0x151f7)
#4 0x00007f3d2a05a374 wp_conf_new_open (libwireplumber-0.5.so.0 + 0x15374)
#5 0x0000557b4f74b141 main (wireplumber + 0x1141)
#6 0x00007f3d29c1330e n/a (libc.so.6 + 0x2a30e)
#7 0x00007f3d29c133c9 __libc_start_main (libc.so.6 + 0x2a3c9)
#8 0x0000557b4f74b6a5 _start (wireplumber + 0x16a5)
ELF object binary architecture: AMD x86-64I did some further debugging: An empty config file in the wireplumber conf.d/ seems to trip up their parser, I filed an issue in their repo: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/675
With the empty file removed, wireplumber starts and works as expected.
MalteJoe
Joey patched this 10 hours ago, just hasn't been cherry-picked yet. https://github.com/getsolus/packages/commit/5e983282185ccc585696cd54599bc65eb8da01ee
Cherry-picked wireplumber to fix that crash.