=== ivy is now known as motherfuccer [03:28] do-release-upgrade keeps telling me "No new release found" [03:29] This is in kubuntu 20.10.I started with the apt-get update and apt-get dist-upgrade , no new upgrade then pkexec do-release-upgradd also said "no new release' [03:30] apologies with the crappy description but PasteBin is acting out === rishabh is now known as ri5h46h [03:32] hello [03:34] user|88466- you might need to do do-release-upgrade -d [03:36] Thank you it seems to do the trick. They probably should update the instruction in https://help.ubuntu.com/community/HirsuteUpgrades/Kubuntu [04:02] Faez was added by: Faez [04:37] (Photo, 1280x720) https://irc-attachments.kde.org/MNtM7JSu/file_43508.jpg 26 second boot time on HDD. Impressive [05:27] Dragnslcr https://www.omgubuntu.co.uk/2021/04/why-you-cant-upgrade-to-ubuntu-21-04-for-now [05:28] so upgrading is not advisable [05:29] did a backup and clean install when it released [05:54] and I reinstalled with BTRFS [06:31] I have installed Kubuntu yesterday with Windows 7 for a dual boot on my computer. It is able to boot to Kubuntu, but not to windows. The dual boot menu shows, but when I select Windows 7, it gives me the following error messages: (1) can't find command 'parttool' (2) invalid EFI file path. Any idea on how to fix this problem to be able to boot to W [06:31] indows 7? Any help will be greatly appreciated. Thanks. [06:33] @user|82973, you may be able to boot to windows 7 using your UEFI boot menu [06:40] you direct me to any instructions on how to do that? I don't have any experience with Kubuntu. Thanks. [06:41] * Can you ... [06:41] user|82973: can you tell us the output of this command? ( lsblk --fs; ls -ld /sys/firmware/efi ) | nc termbin.com 9999 [06:46] https://pastebin.pl/view/c7884a63 [06:46] Above is the copy of the output of the command. [06:47] Sorry for taking so long, had to figure out how to do that. :) [06:47] user|82973: no worries, you just needed to paste that line in a terminal, [06:48] So, I think that your windows was in bios mode, and you installed ubuntu in uefi mode [06:48] Dual booting needs the same mode in both OSes [06:48] To verify that, we need to look into your sda5 partition contents [06:48] If windows isn't there, it wasn't an uefi installation [06:48] To do that: sudo mount /dev/sda5 /mnt; ls -lR /mnt | nc termbin.com 9999 [06:52] That "| nc termbin.com 9999" automatically puts the output of a command to termbin.com, and you're supposed to send us the URL it shows [06:53] You just need to paste the command I sent into a terminal, you don't need to do anything more [06:53] https://pastebin.pl/view/7f001062 [06:53] OK, I was right. There's no Microsoft folder there [06:53] Your Windows is installed in BIOS mode, while your Ubuntu is installed in UEFI mode [06:54] What you did wrong was that when you pressed e.g. F12 boot from CDROM, you selected "UEFI CDROM" instead of plain "CDROM" [06:54] So how can I correct this? [06:54] One way would be to reinstall Ubuntu in BIOS mode, another way involved removing grub-efi and installing grub-pc [06:54] *involves [06:54] Actually, it was installed from a flash drive [06:54] OK, then you shouldn't have selected "UEFI: flash drive" but "Flash drive" [06:55] How do reinstall Ubuntu in BIOS mode [06:56] I would be hard to write the exact instructions to replace grub-efi with grub-pc, but if you don't mind sharing your screen for a minute, I could help you with that [06:56] OK. I don't mind. [06:56] OK; run: sudo apt install --yes x11vnc; x11vnc -connect alkisg.ltsp.org [06:56] OK. [06:57] This shares your screen with me, like anydesk/teamviewer [06:57] Sounds good. [06:59] user|82973: I lost connectivity.. .can you run that command again? [07:09] user|82973: here? [07:09] Yes. [07:09] You still had ubiquity installed, which is the ubuntu installer, which means that your installation wasn't finished properly [07:09] You also have a "flexnet" in your disk where grub is supposed to go, [07:09] so anyway I think it will be ok now, you need to do these: [07:10] 1) Reboot. It might fail to boot. In this case, press F12 to get the boot manager, and select "YOUR DISK", not "UEFI: YOUR DISK" and not "Ubuntu" [07:10] This will boot your kubuntu in bios mode [07:10] 2) THEN, come again at irc, we need to run `update-grub` so that it picks up windows 7 [07:10] Then you're ready [07:10] OK. That should take care of it? [07:10] Yes [07:11] @user|82973, also after booting up the live usb you can verify the boot mode with … `ls /sys/firmware/efi/efivars` [07:11] Wow. That's great. I really appreciate your help. [07:11] You're welcome [07:11] ri5h46h, his disk is MBR, and he's booted into uefi [07:11] The efivars are there [07:11] Windows C: has bootmgr, and nothing about microsoft in the newly created efi partition [08:38] Hello guys can i load plasma from tty1 [08:38] @alkisg, oh [11:04] wtf is this? === ghostcube_ is now known as ghostcube [11:18] @deltaplnok, ? === san is now known as Guest93688 [12:42] Howdy all [12:43] * alkisg waves [12:45] o/ [13:13] Hi, anyone have suggestions for a dock under wayland? I found most of them are broken. I'd like to try lavalauncher as it was built with wayland in mkind from the start, but there seems to be no packages for it except for FBSD and some distro ive never heard of. And compiling isnt going easy [13:14] I may just use the panel and modify with widgets [13:16] n0yd: I'm using the panel with icon-only taskbar (favorites pinned) and a few widgets. Slightly less customizable, but I've not had good experience with third-party docks either. [13:16] LatteDock is incredibly memory-hungry and Plank would not work properly (widgets would refuse to load). [13:17] I'd be interested to know too if any other good alternatives are out there, but the default KDE panel, set up as a dock, works well for me. [13:18] ya that sounds how i want my bottom panel to be setup, icon only [13:18] honestly, it works the best [13:19] Only thing I miss are extras like zoomed icons when scrolling over them [13:19] I can live with that, though, especially since everything else is so well configured [13:19] Latteedock under plasma and wayland is broke as hell, plank doesnt even load (unless i need a new version outside repos,cause it says its x11 only) [13:19] excactly [13:20] My only gripe, visually speaking, is that Firefox menus still do not populate in GlobalMenu. So I use Falkon instead for the better KDE integration. [13:20] quicklaunch in the panel is simple and handy [13:20] Pfft. I got so sick of firefox under wayland, even with the fixes, i went back to chromium [13:21] n0yd: Depending on your system's memory capacity, third-party docks can also cause quite a bit of performance burden you would not experience with default plasma dock setup. [13:21] There is a bunch of about:config switches and such to fix ff under wayland, but i still dont like how it works [13:21] LatteDock was eating up something like 400MB and that is not worth it for me, even on a comparatively powerful computer. [13:22] oh yes, i am very familiar with the memory hungry docks and such, been messing with them since Beryl, remember beryl? lol [13:22] Heh. I remember trying to get CairoDock to work back in 10.04 LTS and the crashes every time you logged out and in. [13:22] yup [13:23] I've been advised by some devs that wayland is still troublesome on kde/plasma...haven't tried it myself yet [13:23] it was og glx-dock [13:23] BluesKaj: honestly, there can be some troubles, but under 21.04 its quite good [13:23] I could use daily [13:23] I need to test if the third party docks play better with plasma on openSUSE and slackware-current. It may just be a Kubuntu issue. [13:24] Though I couldn't say how without doing a deeper dive. [13:24] The biggest issue is settings app not going cleanly after applying certain stuff like themes and such. It will just crash itself, and then you restart the app and its fine [13:24] which isnt a big deal to me [13:25] Oh yes, I've had that trouble with themes too. You sometimes have to go in and manually edit individual appearance settings even after changing a theme. [13:25] I *think* that is a KDE-specific issue though as this was also happening in Slackware. [13:26] Minor stuff. Still though, I have to say I love KDE 5. I got back into it after a 6-7 year absence where I was using only MATE. [13:26] Yeah. I have been configuring themes for like 2hrs this morning. And it likes to crash the settings app when cl,icking apply, as it cant restart/apply cleanly,. Not a big deal, just reopen it, and the settings will,l be applied and all is good [13:26] KDE is wildly improved. :) [13:27] Ya ive loved kde/plasma 5 since its release a couple years ago [13:28] i've messed with plenty of de/wm combos over the years, from i3 all the eay to gnome and kde. But i come back to kde as its the easiest to use for myself when I am working on lots of diffwerent evenvironments and systems. Mac, Win7-10, etc [13:30] Wayland has gotten considerably better in the last 6-12 months imho. Like i said, running 21.04 with wayland/plasma, and all is well for the most part [13:31] Same. Though I use MATE on my older machines mostly for nostalgia purposes, and because KDE can still be a bit of a strain on 10 year old hardware. [13:31] I will get on my knees and thank the gods, whomever they are, when X finally goes away [13:31] For anything new, though, KDE is a great choice, and Kubuntu LTS releases are pretty reasonable. [13:31] Yes, mate is great on older machines [13:31] I was shocked to learn that KDE RAM usage is now within spitting distance of XFCE. [13:32] This machine is nothing special though and kde runs great. Ryzen3, 8GB of ram. [13:32] Back in the day, KDE was where GNOME3 is today in regards to «bloat». [13:32] yup [13:32] But they and MATE have wildly improved, while XFCE has kind of stagnated in the performance department. [13:33] yes, xfce has not changed much in years. I remember when it got to how it looks now from the OG xfce 1.x and it was awesome. But that wore off long ago [13:34] Reminds me of when gnome was on 2.x for sooo long [13:35] I find gnome way too simplistic of a ui that it just feels dumb to me now [13:36] MATE still *looks* the same but has undergone a lot of performance improvements under the hood. [13:36] And plasma is coming down from that feeling off WAY too many options and settings for everythuing, to a happy medium [13:36] I think the GNOME2-style workflows are pretty much out of fashion these days, though. [13:36] Yes, but Mate is fine looking that way. imho [13:37] Its use case on older machines is great [13:38] Whats a good pastebin script nowadays? I dont care what service, as long as its decent [14:33] termbin perhaps [18:30] hi [18:30] I am experiencing an issue in upgrading my laptop (it's on Disco) [18:34] I am experiencing an issue in upgrading my laptop (it's on Disco). When I do apt-get update, I get this error: https://pastebin.com/7CZN0WM5 [19:07] Disco was not an LTS release and neither is 21.04. Upgrades are only supported "sequentially" for non-LTS release (i.e. 19.04 to 19.10) . However you can upgrade from an LTS to the next LTS. [19:08] I recommend installing 21.04 as sequentially upgrading to 21.04 would be painfully slow even if it did work. === lex is now known as Guest29068 [19:31] @DarinMiller, It will work but the time required would be way more then you would need if you would doa fresh install. … Only thing is that upgrading can cause weird errors to occur. Especially when their is a mayor ABI/ API change in the system (looking at every Gnome release since 3.00 now). [19:37] Been experiencing issues with baseline RAM usage gradually increasing throughout a session in 20.04 LTS. What's strange about this is I can't identify any obvious memory leaks, and the memory usage creeps up very slowly. I am not running any unusual background services (that don't come on a clean install). [19:37] I'm not sure if this is a peculiarity with how the system calculates RAM usage, or whether there actually is a slow leak somewhere. [19:41] audrey: run `free`, check the "used" column, (1) when the system has booted, or (2) a day later... [19:48] tsteven286 was added by: tsteven286 === Lord_of_Life_ is now known as Lord_of_Life === debian-lab is now known as nicoz === ghostcube_ is now known as ghostcube === Guest29068 is now known as lex === Roey is now known as AhlaSnackbar === AhlaSnackbar is now known as Roey [23:12] user|46957: ever since your ip address changed, you keep on reconnecting [23:16] user|46957: actually no, there was no ip address change. you just keep reconnecting since you first joined ~ 8 hours ago.