Today, my system is updated with 60 packages (934,44 MiB) and everything seems alright and the whole is fluid, so thank's or the great work of the Solus developer team. 👏
NB. I would like to know about Firefox if it's normal to change in Settings the language of this software in French each time it changes version number in Solus ?

@EbonJaeger : The bug where a virtual machine locks up the system when it's taken to full screen in a Wayland session is not resolved, but it's changed. Apparently Oracle is working on it. I'll add details to the bug report in Dev Tracker.

    launching a game using Wine seems to not work for me now. terminal output:

    0024:err:environ:run_wineboot failed to start wineboot c00000e5
0024:err:win:get_desktop_window failed to start explorer c00000e5
0024:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0024:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
0024:err:d3d:wined3d_caps_gl_ctx_create Failed to create a window.
0024:err:d3d:wined3d_adapter_gl_init Failed to get a GL context for adapter 01D8B780.
0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0024:err:d3d:wined3d_caps_gl_ctx_create Failed to create a window.
0024:err:d3d:wined3d_adapter_gl_init Failed to get a GL context for adapter 01D8B780.
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux0
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux1
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux2
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux3
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux4
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux5
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux6
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux7
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux8
0024:fixme:pulse:pulse_channel_map_to_channel_mask Unhandled channel aux9

      synth-ruiner

      wine is broken for me too:

      [  247.084865] wine64-preloade[33260]: segfault at 28 ip 00007f3b0c8acc69 sp 00007fffe9b729b0 error 4 in wine64-preloader[7f3b0c8ac000+2000] likely on CPU 3 (core 3, socket 0)
[  247.084874] Code: 00 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 81 ec 78 01 00 00 4c 8b 2f 48 89 7c 24 08 <64> 48 8b 04 25 28 00 00 00 48 89 84 24 68 01 00 00 31 c0 49 8b 45

        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.

            • [deleted]

            • Post #26

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

            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.

            CommonUser

            If you run the control center from the terminal with gnome-control-center --verbose do you see anything interesting?

                davidjharder when running then opening bluetooth option it is showing
                03:06:27.1641 cc-bluetooth-panel[ 2815]: MESSAGE: BluetoothHardwareAirplaneMode: 0

                my laptop is acer Swift SFX14-41G.

                    CommonUser pretty sure that message is normal, I see the same thing.

                    what about running dmesg | grep -i blue ?

                    Also, was bluetooth working for you before the sync?

                        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