[03:09] <marco> So does anyone received error message about changing user group when editing software sources in Muon or Discover?
[05:28] <Guest48> while i type sudo apt-get update- get these lines. ..E: Malformed entry 1 in list file /etc/apt/sources.list.d/pgdg.list (Suite)
[05:28] <Guest48> E: The list of sources could not be read.
[05:28] <Guest48> what to do
 You will need to use NANO inside Terminal with root privileges and remove that line from the /etc/apt/sources.list.d file (re @IrcsomeBot: <Guest48> while i type sudo apt-get update- get these lines. ..E: Malformed entry 1 in list file /etc/apt/sources.list.d/pgdg.list (Suite))
 You will need to use NANO inside Terminal with root privileges and remove that line from the /etc/apt/sources.list.d/pgdg.list file or remove the file entirely:
 pgdg.list (re @IrcsomeBot: <Guest48> while i type sudo apt-get update- get these lines. ..E: Malformed entry 1 in list file /etc/apt/sources.list.d/pgdg.list (Suite))
[08:54] <Devel78> Yo guys, any of you managed to upgrade to 22.04 by doing do-release-upgrade?
[09:34] <RikMills> Alkis: I added a backtrace with debug symbols to that report
[09:37] <alkisg> Meh, matrix keeps highlighting me when "Alkis" is mentioned :D
[09:37] <Alabama_Al> sdf
[09:38] <Alkis> RikMills: thanks.  looks like something is wrong with Qt, doesn't it? https://github.com/KDE/kstars/blob/master/kstars/main.cpp#L67
[09:44] <RikMills> Alkis: well, it was build against 5.15.2 and we got 5.5.3 later on in jammy, so 1st I am seeing what happen when rebuild against 5.15.3
[09:44] <RikMills> *5.15.3 later on
[09:45] <RikMills> also have something else to try....
[09:46] <Alkis> RikMills: the "optimised out" of argc looks a bit suspicious too
[09:46] <RikMills> and of course, there is a new 3.5.8 out since....
[12:25] <user|17> Hi. I've upgraded from to 22.04 LTS from 21.10 it kill my system. NetworkManager seems go crazy. 32% cpu.. constant reconnects seems by logs. Any suggestions how to fix this. Its also leads to Plasma crash.
[12:29] <BluesKaj> Hi all
[13:10] <tmlk> hello! I'm running latest Kubuntu (22.04). I have 3 Kernels installed (5.11, 5.13 and 5.15). Currently 5.15 is the default one. I'd like to set 5.11 as the default one. What's the "proper" way to do so?
[13:14] <BluesKaj> tmlk, choose it during boot in grub boot loader, but why don't you ask your real question?
[13:15] <tmlk> BluesKaj: Thanks for your answer. The real question is that after recently upgrading to the latest release of Kubuntu the wake on bluetooth (external mice/keyboard) stopped working. Before digging I wanted to test a previous version of the Kernel just in case some regression was added.
[13:16] <BluesKaj> tmlk, have you updated/upgraded since your install?
[13:17] <tmlk> yes, all packages are up to date
[13:19] <tmlk> I've double checked the udev rules and still not working. I added an ugly cron like this "echo enabled | tee /sys/bus/usb/devices/*/power/wakeup" and as a matter of fact, pluggin any of the plugged in devices resume from suspend. So I've narrowed it down to bluetooth.
[13:20] <tmlk> s/pluggin/unplugging
[13:23] <BluesKaj> ok, check System Settings/Hardware/Bluetooth
[13:24] <tmlk> all looks good in there
[13:24] <tmlk> besides, there aren't options related to wake from suspend
[13:30] <Elliria> Hey there. I'm thinking about installing Inkscape on Kubuntu 20.04 LTS, but it says it depends on python2:any and I don't want to mess up my Python3 installation. Will installing Inkscape cause any Python problems for me?
[13:31] <BluesKaj> tmlk, try this: sudo systemctl start bluetooth, then, rfkill unblock bluetooth, and reboot
[13:34] <tmlk> I can try that, as a side note the bluetooth.service is started, rfkill already shows that both wlan and bluetooth are both soft/hard unblocked.
[13:34] <tmlk> should I try regardless?
[13:36] <BluesKaj> Elliria, Inkscape lists python 3 as a depenedency on 20.04 so it should work fine if you install it
[13:36] <BluesKaj> tmlk, yes
[13:36] <tmlk> ok, brb
[13:37] <BluesKaj> dpendency rather
[13:39] <Elliria> Thanks, BluesKaj, but I'm not seeing that. Muon says it depends on python2:any. Why are we seeing different dependencies?
[13:40] <tmlk> BluesKaj: same, no wake on bluetooth mice/keyboard
[13:40] <BluesKaj> Elliria, https://askubuntu.com/questions/1232812/whats-the-default-python-version-in-ubuntu-20-04
[13:42] <BluesKaj> tmlk, think there's a bug or 2 related to sleep on 22.04
[13:42] <tmlk> any forum or thread in git I can follow-up on this?
[13:43] <BluesKaj> tmlk, think i saw someting about it at the #ubuntu chat a few days ago
[13:44] <Elliria> Maybe I should ask my question in a different way. If a target package depends on python2:any, what will happen to my Python3 installation if I install that target package?
[13:45] <BluesKaj> Elliria, have you updated/upgraded lately.? It seems that python 3 should be default on 20.04
[13:47] <Elliria> My system uses Python 3.8.10 and the target package that I'm thinking about installing on my system depends on python2:any and I'm worried that Python 2 will be installed on my system if I install the target package.
[13:48] <tmlk> BluesKaj: thanks for input on this. I'll keep an eye open, see if I can find out more.
[13:48] <BluesKaj> Elliria, what's your "target package"?
[13:49] <Elliria> Inkscape
[13:50] <Elliria> It also depends on packages like python-numpy rather than python3-numpy, etc.
[13:51] <BluesKaj> well inkscape is in the repos so it's supposed install and work without any ill effects or are you trying an earlier version ?
[13:52] <Elliria> I'm in the repositories on Muon and looking at the dependencies before deciding whether to install and what I'm seeing is worrying me, which is why I figured I'd do a bit of research before diving in.
[13:53] <BluesKaj> Elliria, I'm on 22.04 and muon here doesn't show python 2 as a dependency
[13:54] <cbreak> python2 has been dead and deprecated for years
[13:55] <BluesKaj> perhaps an upgrade to 22.04 LTS will lift your concerns
[13:55] <Elliria> Yeah, I suppose staying with the LTS does pose its own challenges.
[13:55] <Elliria> Wait, what? There's a brand new LTS?
[13:56] <BluesKaj> yup
[13:57] <cbreak> https://www.python.org/doc/sunset-python-2/ // it seems people that didn't get the message to move away from python2 in 2008 might still use it... but anything made in the last decade or so shouldn't rely on it
[13:58] <Elliria> Yeah, that was why I'm worried about installing it, cbreak.
[13:58] <Elliria> Okay, I guess I need to upgrade Kubuntu. Man, I wish I'd known that was going to be an LTS or I would have waited. I just installed 20.04 about two weeks ago.
[13:58] <cbreak> 20.04 is also an lts
[13:59] <Elliria> Yeah, I only run LTS versions, but I didn't realize we were getting another one so soon.
[13:59] <Elliria> Someone might want to fix the https://wiki.ubuntu.com/Releases page since it doesn't show it as an LTS.
[14:00] <cbreak> hmm... inkscape on 21.10 seems to use python3
[14:00] <Elliria> Yeah, on 20.04 it depends on python2:any.
[14:01] <cbreak> there's an inkscape snap it seems
[14:01]  * BluesKaj stays away from snaps, but that's just me....
[14:01] <Elliria> Is there a command I can run to update to the new LTS in place without having to reinstall everything?
[14:02] <cbreak> do_release_upgrade
[14:02] <cbreak> but that's not been enabled yet
[14:02] <cbreak> it'll probably take a few months for that
[14:02] <Elliria> Oh. Heh. So I'd have to start over.
[14:02] <cbreak> Sorry, it's do-release-upgrade
[14:02] <Elliria> Well, I might want to get that over with since I'm still recovering from upgrading two weeks ago. May as well be as current as possible.
[14:02] <cbreak> Elliria: you could switch to non-lts, and / or update in dev mode, and switch back when you're done
[14:02] <BluesKaj> yeah do-release-upgrade -d
[14:03] <Elliria> I'll just do a wipe and install and copy my stuff back over as usual. It's a big royal pain, but it's doable.
[14:03] <BluesKaj> the above command will install the next LTS
[14:04] <BluesKaj> did it on my old HP pc without any problem
[14:04] <Elliria> Even now, BluesKaj? Even though it's not enabled yet?
[14:05] <cbreak> Elliria: that's why you have to use -d
[14:05] <BluesKaj> -d will be in use until the .1 version of the LTS is available, probly in july
[14:06] <Elliria> Okay, thanks.
[14:09] <Elliria> I'm gonna go put it in a VM and mess around with it and then get to installing. Thanks for the help.
[14:09] <Elliria> Hugs all the way around.
[15:01] <user|66> hello please help me to install kubuntu with UEFI os thanks
[16:48] <user|21> hi everyone.  After upgrading from 21.10 to 22.04 has anyone else started seeing this error during startup?  ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[16:51] <tmx> hello is me
 R6WE
 Hi guys, I got a big bug in the wayland session, basically no flatpak shows up even though I have many flatpaks installed on my system
 Ah, I've fallen into this issue a couple of weeks ago (re @Dansit0: Hi guys, I got a big bug in the wayland session, basically no flatpak shows up even though I have many flatpaks installed on my system)
 Let me guess, you're using zsh?
 I fixed it by adding
 emulate sh -c 'source /etc/profile'
 To .zshenv
 yes (re @adhooooooooom: Let me guess, you're using zsh?)
 how? :( (re @adhooooooooom: I fixed it by adding
 emulate sh -c 'source /etc/profile'
 To .zshenv)
 Can you explain me the steps for this? I do not deal much with this issue of the shell and path (re @adhooooooooom: I fixed it by adding
 emulate sh -c 'source /etc/profile'
 To .zshenv)
 thanks man
 ❤️
 Did you fix it?
 yes
 Great
 You're welcome