apparently 16 minutes remaining, and already been like 2 hours lol
apparently 16 minutes remaining, and already been like 2 hours lol
Hfailed builds are normal, do not worry about it unless the build is closer to a month old i would say, so that you havent had a new update for about 7 days is nothing to worry about.
as for if there are any issues preventing new builds, usually it is upstream issues which eventually get resolved, it is better the builds fail in github rather than you getting a broken system due to upstream issues
as for if there are any issues preventing new builds, usually it is upstream issues which eventually get resolved, it is better the builds fail in github rather than you getting a broken system due to upstream issues
UAgreed on the "better to let github suffer" piece. I'm new to using an rpm-ostree distro, so I'm just wondering about the typical cadence
Hrip, feel free to just @ me when its done then.
my VM doesnt have any network speed issue so its super weird that yours do
my VM doesnt have any network speed issue so its super weird that yours do
Lwell i did install this: rpm-ostree install virt-install libvirt-daemon-config-network libvirt-daemon-kvm qemu-kvm virt-viewer guestfs-tools pyt
hon3-libguestfs virt-top
hon3-libguestfs virt-top
Lif it has anything to do with it?
Las i could not find any help with it and so i found that online
Hyeah i wouldnt worry about lack of a new build unless its been closer to a month (or there is a severe exploit that just got patched that is actively being exploited in the wild)
Uto be clear, my system is running perfectly well.
Hand we dont want it any other way 
UI appreciate that
PDoes your CPU actually have virtualization support? And enabled in bios?
Lyes
Hnot sure what libvirt-daemon-config-network changes or if its pulled in by the "enable-virtualization" command which installs "edk2-ovmf, qemu and virt-manager"
will have to fire up a fedora VM and check
will have to fire up a fedora VM and check
Hi would believe its pulled in by the other commands but its the only package that would fiddle with anything network related
Live run VMplayer and virtual box just fine in other distros in the past pintocat, with no issues with sharing folders or network speeds
LI first used the just enable-virtualization, then rebooted, then i did the rpm-ostree install virt-install libvirt-daemon-config-network libvirt-daemon-kvm qemu-kvm virt-viewer guestfs-tools pyt
hon3-libguestfs virt-top then rebooted, and then you told me those other commands and i tried those and it finally made virtual manager work
hon3-libguestfs virt-top then rebooted, and then you told me those other commands and i tried those and it finally made virtual manager work
Las for boxes, that works perfectly fine, its just that I cant figure out how to share files from the guest os to host os
Hjust checked libvirt-daemon-config-network gets pulled in with virt-manager
im at a loss for why gnome-boxes has the network speed working fine and virt-manager doesnt
im at a loss for why gnome-boxes has the network speed working fine and virt-manager doesnt
PLots of weird issues with that install not just virt
Hyeah never seen anything like that since shouldnt gnome-boxes use libvirt in the background?
LI promise i didnt do anything special to the install lol
Lif its something wrong with it, it would then have to be something with a piece of the hardware
Lif you are sure it isnt bazzite itself
Lanyway, the internet speed is fixed now but only AFTER updating the guest OS
Ldid not have that same issue on the boxes guest OS
LI didnt have most of these issues on manjaro
Lbut i should mention I did have a lot of issues on windows 11 on the same hardware
Lwindows 11 is actually way worse than bazzite
Lfor instance files take ages to transfer on windows 11, and games can lag like hell
Lbut on bazzite they are super fast
Ljust mentioning this in case anyone has any ideas as to whats going on. oh also I could not even get chimeraOS to install/run on my hardware no matter what i tried
RDRD is broken again
RRit breaks sleep.
RApparently Valve can't code shit that works /s
DIt has been a while since the last update on bazzite-deck:latest
RI've tracked down the probable source of the bluetooth pairing issues, guys.
RThis will be painful.
RIt seems to be a kernel regression.
RI tested my keyboard on bluez 5.70 on another realtek bluetooth radio.
RPaired first try, no issues.
RIt's not bluez related it seems.
Dwhy is bazzite defaulting to wayland even though there is a major issue? #Why is wayland now enabled by default?
RAnd it seems to be hardware specific.
RMy desktop with a 8771 from Realtek paired first try with no issues.
KIf I move my working install to a new computer will it just work or do I need to reinstall
Hit will work as long as you dont have any mounts in fstab that uses /dev/sdX# as those might not be the same when you move systems (which is why its recommended to use WWIDs instead by using
/dev/disk/by-id/ paths or similar instead
K( and ) was fixed a few weeks ago, I pinged you
Kif you have additional issues, open an issue with extest's github
Kworking great on my end
