Sync Updates for Week 31, 2023

Update again. Just synced a revert to wine 8.10 until we know whats wrong with 8.13.

Harvey And also a Budgie Desktop backport to fix searching for programs in Run Dialog and Budgie Menu with non-Latin characters.

WetGeek Apparently Oracle is working on it. I'll add details to the bug report in Dev Tracker.

Somewhat related, I've created VirtualBox VMs for Budgie, GNOME, MATE, Plasma, and Xfce. Although I know that Boxes and virt-manager produce VMs that can be used at full screen on Wayland, I don't think this is a good time for me to abandon VirtualBox. So when I need to work with a VM at full screen, I'll just log in to an X11 session.

i can't start my bluetooth from settings in gnome DE, when i toggle on, it back to off again like in this video

Great! thank you! the bug which was important for me, was fixed in last update which I tried just now
You're awsome!

Harvey Thanks Harvey, all good now.

Another mini-sync to fix the issue with the file picker not opening from Flatpaks in GNOME (and potentially in other cases)

Today I got a chance to begin a very minimal bit of configuration for my five Solus VMs, such as a new Solus user might do after installing Solus on a computer. In most cases, I changed to a dark theme, created four workspaces to help me with maintenance, and used eopkg to do the remaining upgrades that weren't in Friday's update.

In that process (in an X11 session) I attempted to work with the VMs at full-screen, since Oracle seems to have been working on that lately. Of the five Solus VMs, Budgie, Plasma, and Xfce gave me no concerns in any way. (Other than Xfce is understandably still sluggish in some respects, because it's not release-level software yet.)

My GNOME VM now boots to a black screen. I've seen that before with other distros, so I changed the VirtualBox video adapter from VBoxSVGA (that we use with Solus VMs and others) to VMSVGA, the other choice. Then the GNOME VM was able to boot to a login screen. After I logged in, however, its behavior was still flawed. Although it could be taken to full screen with HOST+F, the VM's image remained the same size, and at full screen, it was in the middle of a very thick black border. If I changed its video resolution to 1920x1080 in the system settings, I could then make it full screen, but when toggled back to a smaller size, it had vertical and horizontal scroll bars.

The MATE VM behaved the same as GNOME, although it was fine with the VBoxSVGA video adapter. But it required setting its video resolution to 1920x1080 in order to use it a full-screen, and when toggled to its original smaller size, it ended up with scroll bars instead of a smaller image of the VM's output.

I'm not going to shed any tears over MATE, because it's no secret that it won't be around much longer. I'm more concerned with GNOME. Booting to a black screen without its preferred video adapter makes it different from all our other editions. And I'm well aware that even GNOME might work well on bare hardware.

davidjharder when i run dmesg | grep -i blue it is resulting

[    4.770018] Bluetooth: Core ver 2.22
[    4.770054] NET: Registered PF_BLUETOOTH protocol family
[    4.770055] Bluetooth: HCI device and connection manager initialized
[    4.770059] Bluetooth: HCI socket layer initialized
[    4.770061] Bluetooth: L2CAP socket layer initialized
[    4.770065] Bluetooth: SCO socket layer initialized
[    5.598014] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.598029] Bluetooth: BNEP socket layer initialized
[    6.851558] Bluetooth: hci0: Opcode 0x c03 failed: -110

for the problem i'm not remember if it occurred from when i using solus 4.3 before, but i sure that after i reinstalling to solus 4.4 it is the bluetooth is not working. is my hardware not supported ? but when i using opensuse timbleweed it is working fine.

First: Thanks for this awesome distro. It is definitely currently one of the greatest desktop distros out there.

Updated my packages yesterday and one of the packages was the nvidia driver. Now it doesn't start X anymore. Kernel and Nvidia driver are out of the sync. The kernel module has a different version than the nvidia driver package.

Please correct that asap. Thanx a lot!

m1h43l you're going to have to be more specific than that, we have multiple Nvidia drivers and they were all rebuilt after the kernel upgrade

CommonUser What is your bluetooth hardware?

ReillyBrogan

From dmsg

API mismatch: the client has the version 535.86.05, but this kernel module has the version 535.54.03

uname -a

Linux mymachine 6.3.12-244.current #1 SMP PREEMPT_DYNAMIC Sat Jul 15 23:23:42 UTC 2023 x86_64 GNU/Linux

ReillyBrogan

... cannot edit my own post ... wtf...

eopkg list-installed | grep vidia :

nvidia-470-glx-driver-modaliases
nvidia-glx-driver-32bit
nvidia-glx-driver-common
nvidia-glx-driver-current
nvidia-glx-driver-modaliases