Unable to install bazzite on the rog ally x, unicode error
Hello! Today i was trying to install bazzite on my rog ally x, i tried both using a usb drive with rufus and flashing it that way and i also tried using ventoy and booted into bazzite from there. In both cases, after a few seconds an error shows up on the screen saying: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xdf in position 0: unexpected end of data. I used 3 different usb drives, and the same error shows up, i'll also try to attach photos with what is going on
60 Replies
you are the first one with that issue ever
damn
seems like one of your disks has a funny name
wdym?
i dont know but it doesnt like something either about your sd card, ssd, or usb drive
remove your sd card and if you dont need windows nuke your drive
and then it should work
well i dont even reach that part where i can nuke the windows
it goes straight here
did you repartition your drive or something?
change labels?
regarding the windows partition yes
but it works fine
and for bazzite i dont even get the installer
time to go back and change them to latin names
then it will work
latin names?
english characters
i didnt rename them
did you touch your drive with partition manager?
do you want to keep windows?
yes
what did you do to it
not necessarly
i shrunk it
nothing else?
no
what brand is your usb drive
do you have an sd card?
kingston, another sony one and one that just says team
no
i can tell you how to wipe the drive
I cant guarantee you it will work after
i can wipe it clean if that would work
i know how
but it's still weird
it doesnt like something in one of the drives
i dont know what
if you want to wipe it
alt + ctrl + f5
then sudo cfdisk /dev/nvme0n1it doesnt let me type anything
i'll do it with something else
brb
i have a ventoy drive with hbcd
i assume it's ok with that?
im ok
it booted as normal with a clean drive
i'm in the installer rn
it installed just fine, i'm in
thanks
np
sheesh i guess i'm the second ever with this issue, but i'm trying to install on a desktop PC with 2 nvme and 1 sata ssd. I ain't formatting (or disabling cuz pain in the ass) any but the primary one (if i had another flash drive with necessary utility that is).
sorry if i post in the wrong thing, creating the new topic doesn't look good either
oh damn
no way bazzite is also facing this shit
You're not, one of you appears every two days
did you see the discussion on bluefin about this thing?
No
this must be some error on main
the UTF-8 blalbalblal error
hope it gets well soon, i'ma stick around until then
i think the latest ISOs dont have that issue
im sure the new bluefin ISOs dont
i dunno, i downloaded the latest stable iso like half an hour ago
maybe you can get the latest "latest" iso?
https://download.bazzite.gg/bazzite-latest.iso
dunno if they have that hosted on the bucket
404
damn they dont
There's no need for a latest ISO
We don't have f40 like bluefin does
That issue has never affected us
weird
If that is of any consequence, i tried installing on a VM and it just works :shrug:
Bug is fixed upstream by blivet
GitHub
Protect against exceptions when getting properties from udev · stor...
We've seen online UnicodeDecodeErrors from pyudev, but let's just
catch all exceptions here and try to process the device anyway.
Fixes: #1330
Maybe someone could cook something up and cherry pick this patch and include it in the ISO? @antheas
Otherwise this will likely take until F42 before this is included
Maybe we should just start sending them bug reports
There's an open kernel patch
¯\_(ツ)_/¯
Literally a 1 line change
https://patchwork.kernel.org/project/linux-block/patch/[email protected]/
I meant anaconda
Ah yeah maybe
We have lots of users with this issue and there are several reports on the fedora forums too so it's not very isolated at all
It's actually a quite common installer breaking bug so maybe it can be hot fixed
What I've noticed is that it mostly applies to devices that are imported with default partition names that are not at all English and that's where this bug triggers.
I doubt anyone manually adds partition names to their devices.
although i'm ukrainian i've never used ukrainian as a system language (on this machine), let alone name the partitions using cyrillic alphabet. Unless there's some weird remnants on it from the vendors or something that windows uses innately due to locale, i have no idea where to look.
But either way the installer should just let me in to format the drive instead of looking for them weird letters on it xD
Ofc you could argue that the installer has to scan all drives and partitions to make sense of the current arrangement, and the error stems to some extent from python forcing reading UTF-16 stuff as UTF-8
probably, i'm a noob in all this, but it also makes it fairly obvious that people who never used anything but english didn't even think that a problem like this could happen, hence here we are
It's more like UTF-16LE to ASCII to UTF-8
So i got bored and deleted all partitions with fdisk, which allowed me to proceed, so yeh, installing bazzite now. Hope it’s smooth from here on out xD
Yep, that's the easiest but most nuclear way to fix it 🙂
I didn’t have anything except windows on the drive, backed up stuff prior so all good
no partitions means no partition names means no bug trigger 😛
I hope i can split the partitions later tho, kinda weird having only one, used to having 2 - one for system, another for data. But i guess I don’t really need that on linux?
You can still do that if you want