=== diana is now known as washboard
=== david_ is now known as Guest3701
[12:42] <IrcsomeBot> <Eduardo_Jose_Soares> Hello ppl! ANyone knows if the dist upgrade from version 21.10 to 22.04 LTS is available now?! (re @Андрей: As far as I know dist upgrade will be available in July-August, with 22.04.1 LTS release.)
[13:02] <BluesKaj> Hi all
[15:04] <alkisg> Eduardo_Jose_Soares, that one is considered a "normal" upgrade and it was available since April
[15:12] <IrcsomeBot> <LOBOLATELEPHONY> Yes it's available just finished working on my personal machine (re @Eduardo_Jose_Soares: Hello ppl! ANyone knows if the dist upgrade from version 21.10 to 22.04 LTS is available now?!)
[15:13] <IrcsomeBot> <Eduardo_Jose_Soares> 👍🏻👍🏻 (re @LOBOLATELEPHONY: Yes it's available just finished working on my personal machine)
[15:14] <IrcsomeBot> <Eduardo_Jose_Soares> 👍🏻👍🏻 (re @IrcsomeBot: <alkisg> Eduardo_Jose_Soares, that one is considered a "normal" upgrade and it was available since April)
[15:22] <IrcsomeBot> <Eduardo_Jose_Soares> Oh! In this page they saying that still not avaliable for upgrading. 😳 : https://irc-attachments.kde.org/dda65925/file_58740.jpg
[15:43] <IrcsomeBot> <LOBOLATELEPHONY> https://irc-attachments.kde.org/37a8ca56/file_58741.jpg
[15:54] <IrcsomeBot> <Omar> How do I change my Dell BIOS to UEFI?
[15:55] <IrcsomeBot> <Omar> And is it good?
[15:55] <IrcsomeBot> <Omar> Or should i stick to bios?
=== rushil is now known as rushil_
[16:21] <mparillo> I know others will disagree, but if you are not dual booting, and it is working, I would leave it as BIOS.
[16:22] <arraybolt3[m]> +1 ^
[16:30] <Dragnslcr> If you're building a new system, I would set it to UEFI. I wouldn't change a running system, though, unless you have a specific reason (most likely needing GPT because you're adding a large hard disk).
[16:38] <IrcsomeBot> <Omar> Ok
[16:38] <IrcsomeBot> <Omar> If i switch to UEFI what will change?
=== nunopinto is now known as Octnun
[17:08] <arraybolt3[m]> @Omar: You'll probably be unable to boot any longer, and may need to do a full reinstall to get things working again.
[17:18] <Octnun> Hey, does anyone know why some graphic cards dont let kubuntu start?
[17:50] <valorie> Octnun: you'll need to give more information than "some graphics cards" and "don't let kubuntu start"
[17:50] <valorie> !graphics
[17:50] <valorie> bummer, no factoid
=== Lord_of_Life_ is now known as Lord_of_Life
[18:27] <Octnun> valorie: I have a Red Devil Radeon RX 6700 XT 12GB GDDR6. Eveytime I plugin the card and boot it with kubuntu PEN, it stucks at the start before instalaing. If I remove it, I can install kubuntu with no problem.
[18:28] <Octnun> compatibility problem?
[20:33] <tomreyn> Octnun is gone, but what is "kubuntu PEN"? a 'pen drive' with the kubuntu live / installer on it? or some specific hardware?
[20:34] <tomreyn> i imagine it could be a stylus pen
[21:36] <marcelo52> i install kubuntu 22.04 and now?
[21:37] <marcelo52> initramfs
[21:37] <arraybolt3[m]> marcelo52: Are you getting an error while attempting to use Kubuntu?
[21:38] <marcelo52> no i want enter on kde
[21:38] <arraybolt3[m]> marcelo52: OK. Can you send a picture of the exact error that you're seeing? (You can upload it to Imgur and paste a link here.) Usually when something like that goes wrong there's some debugging data on the screen.
[21:39] <marcelo52> is in text mode i want graphic
[21:40] <Spectre> Hoping someone can help lead me in the right direction.  I can't connect to a synology nas samba share from dolphin but can mount the share from the command line with smbclient just fine.
[21:40] <arraybolt3[m]> marcelo52: I know. But in that text mode there should be a message that says *why* it's in text mode. I need to see that to figure out how to get it into graphic mode.
[21:41] <arraybolt3[m]> (The system usually boots into graphic mode, so if it's in a text mode, something is quite wrong.)
[21:41] <marcelo52> how to enter in graphic mode please?
[21:42] <arraybolt3[m]> marcelo52: I guess you could try pressing Ctrl+Alt+F1 and see if that does it. If not, try Ctrl+Alt+F2.
[21:43] <marcelo52> startx dont work
[21:43] <arraybolt3[m]> marcelo52: If neither of those work, I will *need* to see the message on your screen in order to debug the problem, otherwise I have no way to know why you're in text mode rather than graphic mode. And if I can see the error, I can at least try to help you fix it so that you can get into graphic mode.
[21:44] <marcelo52> (INITRAMFS)
[21:44] <arraybolt3[m]> marcelo52: startx isn't how you're supposed to make graphic mode work. Kubuntu is designed to boot into graphic mode by default. If it doesn't, that's the result of an error on your end. And I'm sure there's more than just (INITRAMFS) on your screen, there should be some critical data above it. So we need to fix that error so that your system will work.
[21:45] <arraybolt3[m]> marcelo52: Does it say something like "root device can't be found"?
[21:45] <arraybolt3[m]> marcelo52: Even just knowing if there actually isn't an error message will be helpful (right now I don't know if there is or not).
[21:56] <jane> hii
=== nunopinto is now known as Octnun
=== NotEickmeyer is now known as Eickmeyer
[22:21] <IrcsomeBot> <npeippo> I actually had a problem on my first boot when I installed Kubuntu a month or two ago, it never went into graphical UI, not even ctrl+alt+f1. Startx did the trick, and since then it has worked
[22:58] <user|25> hi
=== mkv is now known as m4v