[00:11] <tomreyn> that one, out of thousands reported each month?
[00:26] <tomreyn> in case you're referring to CVE-2024-3094, then based on what's known so far: unless you are using (unreleased, in-development) noble numbat (24.04) with -proposed, you should not be affected. note that i'm not in any formal position, not speaking for (k)ubuntu.
[00:26] -ubottu:#kubuntu- Malicious code was discovered in the upstream tarballs of xz, starting with version 5.6.0. Through a series of complex obfuscations, the liblzma build process extracts a prebuilt object file from a disguised test file existing in the source code, which is then used to modify specific functions in the liblzma code. This results in a modified liblzma library that can be used ... <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094>
 Hello darlings
 I recently installed kubuntu but my wireless network has unknown
 I need it for install softwares
 How can I solve this problem?
 Wdym by unknown ?
 Cant able to use wifi? (re @Trust: Hello darlings
 I recently installed kubuntu but my wireless network has unknown
 I need it for install softwares
 How can I solve this problem?)
 In the icon of network there is no connection
 I need wireless networks (re @milesdredd: Wdym by unknown ?
 Cant able to use wifi?)
 KUEP (re @join_captcha_bot: )
[11:35] <user|24> hola buen día
[12:37] <BluesKaj> Hi all
[15:34] <VanUnamed> and i bricked it.
[15:49] <allan> Bonjour, Sauriez-vous comment on personnalise son masque d'hôte comme ça ~allan@user/allan ?
[15:58] <bombastick> eatyourglory: https://www.openwall.com/lists/oss-security/2024/03/29/4 the detect.sh script attached here should tell you
[15:58] <bombastick> tell you if you are affected
[16:40] <VanUnamed> https://ibb.co/MDnJ7gP
[16:40] <VanUnamed> i just resized a partition, not the one with the OS
[16:40] <VanUnamed> and thats what happened.
[16:41] <VanUnamed> https://i.ibb.co/BVLYBfT/20240330-182526.jpg
[17:29] <tomreyn> VanUnamed: i'm guessing that you modified the file system you are meaining to mount to /media/DATA?
[17:30] <VanUnamed> i modified only /media/data
[17:30] <VanUnamed> not /
[17:30] <VanUnamed> hdd is like / partition, efi stuff partition /data
[17:31] <VanUnamed> i just chopped /data into media/data1 and data2
[17:31] <VanUnamed> and now it does this.
[17:31] <VanUnamed> i even attempted grub boot repair with the live
[17:31] <VanUnamed> no dice
[17:31] <tomreyn> VanUnamed: and apparently you have what is to be mounted at /media/DATA listed in /etc/fstab as a required moun, but you forgot to adjust the path to this file system in /etc/fstab
[17:31] <tomreyn> moun -> mount
[17:32] <VanUnamed> so i should just edit etc fstab?
[17:32] <tomreyn> the file system with the uuid printed on your screen probably no longer exists with this very uuid, i.e.t he uuid changed when you changed the file system.
[17:33] <VanUnamed> and why boot repair didnt fix it?
[17:33] <tomreyn> you need to get the new file system id, and edit /etc/fstab, and reboot (or step through the boot routine manually)
[17:33] <VanUnamed> is there a way for me to tell which is the new file system id?
[17:33] <tomreyn> your boot did not fail, the system booted fine, or you would not have seen this much output
[17:34] <tomreyn> lsblk -o +UUID
[17:34] <VanUnamed> oh ok, i see
[17:34] <VanUnamed> will try
[17:35] <VanUnamed> is this uuid maybe wirtten in some file i can access with an external drive/
[17:35] <tomreyn> it is written into the file system header
[17:36] <tomreyn> if you live boot some other linux you can also run the same command and it should list it, given the file system type is also supported there
[17:36] <VanUnamed> okk i will try. but why the grub boot repair did not do this?
[17:37] <tomreyn> i'm not very familiar with boot repair. my understanindg is that it's meant to automatically repair non-booting systems (in those scenarios it covers). as i mentioned, your system did boot fine, just not all systemd units succeeded.
[17:37] <VanUnamed> ah ok. thanks mr tomreyn . will try tomorrow
[17:39] <tomreyn> you can, and probably should, mark removable file systems (or rather file systems locate don removable media/disks) as optional on fstab, so that systemd will not run into an error situation if this file system won't be available in the future.
[17:42] <tomreyn> i.e. add the "nofail" file system option for this mount in /etc/fstab
[21:09] <stefanathomeuk> Good evening
[21:10] <stefanathomeuk> I am using VLC player to watch my movies from our NAS Station but I get only an error
[21:10] <stefanathomeuk> That the file can't be shown
[21:11] <stefanathomeuk> Online I can't find any assistance
[21:13] <stefanathomeuk> As it looks like nobody else has that issue
[21:13] <stefanathomeuk> Goodnight and Goodbye