[00:26] <space-cube-5-M> where am i
[00:55] <rain_523> Hello, I've been having some problems by trying to pair some wireless headphones of mine to my pc with bluetooth. Whenever I turn bluetooth on the headphones never appear. I've connected the headphones to my phone before so I'm sure there's a problem with my laptop, not the headphones.
 try to unpair them
 i mean delete your headphones from yr laptop list
 bleutooth list
[03:28] <space-cube-5-M> onqi gud
 (Photo, 1280x720) https://irc-attachments.kde.org/0HMGbCQh/file_43766.jpg hello guys i don't know why (individual core usage widget) Text-only Sensors not showing and sometimes battery icon suddenly gone and when i add battery widget show no battery available
 Fwd from erfan_sta: i reset plasma to factory but not helped
[06:07] <lordievader> Good morning
[06:10] <alkisg> o/
 morning
[07:26] <lnielsen> Hi all. My multi-monitor configuration is corrupted. Whenever I open the configuration, my 4K display isn't shown, the laptop it's connected to also has a screen which is either replicated which I can't disable or it overlaps, or it shows some kind of screen-in-screen...
[07:27] <lnielsen> I already tried restarting, disconnecting and reconnecting, removing and adding, shuffling the screens around, but my 4K monitor isn't even shown in the arrangement.
[07:27] <lnielsen> Any way I can hard reset the entire config?
[07:27] <lordievader> lnielsen: Does `xrandr` still see it?
[07:27] <lnielsen> It sees the monitor in the configuration
[07:27] <lnielsen> It doesn't show it in the layout arragnement
[07:28] <lnielsen> And I have desktop, it's just messed up, a replica, an overlap, etc.
[07:28] <lnielsen> This is extremely buggy, but I just want to do a hard reset
[07:29] <lnielsen> Also, I somehow can't switch off 'replica' for the laptop monitor
[07:32] <lnielsen> Also, both are somehow named "laptop screen" in the dropdown, until I select the 4K, it changes to its real name/ID
[07:32] <lnielsen> So, very obviously totally corrupted and bugged
[07:32] <lordievader> lnielsen: Does a new profile have the same problem?
[07:33] <lnielsen> Hmm, good idea
[07:33] <lnielsen> I'll try that
[07:33] <lnielsen> bbiab
[07:37] <lnielsen> Whoever I was talking to just now: the problem doesn't present when creating a new user
[07:37] <lnielsen> So I could run a diff -Nru
[07:38] <lnielsen> Or something?
[07:40] <lnielsen> Hmmm, that yields no difference
[07:40] <lordievader> These days all the kde config should reside in `~/.config`. I'd hunt out anything related to kscreen, move that to somewhere else, and then a log-out-> log-in to see if the problem persists.
[07:41] <lnielsen> Yeah, I switched to .config just now and the changes are endless
[07:43] <lnielsen> Ok, I'll see what I can dig up with some cli magix
[07:43] <lnielsen> :p
 I have backports repo on hirsute enabled and added the stuff to /etc/apt/preferences to always use the backports repo (pin priority 500). … When I do a … apt -t hirsute-backports upgrage … I receive error saying its not in sources.
 "E: The value 'hirsute-backports' is invalid for APT::Default-Release as such a release is not available in the sources"
[07:50] <lnielsen> lordievader: there is no .kscreen ?
[07:52] <lordievader> Hrmm, would `~/.local/share/kscreen` be responsible?
[07:56] <lnielsen> lordievader: looks like it
[07:58] <lnielsen> trying..
[08:01] <lnielsen> lordievader: you're a goddamned hero
[08:02] <lnielsen> just renaming the folder to .old and logging back in worked, Not unexpected, I inspected the contents of what was in there and it did look exactly the kind of warped display config I expected to find
[08:02] <lnielsen> But I would have had no idea where to look if not for you, so thanks a million
[08:04] <lordievader> No problem. Been there done that ;)
 Hi, … I think I somehow messed my audio/bt drivers. … I manage to connect my bt headphones (I get a notification they are connected from both the computer and the headphones), yet all sounds come only from the computer. Imagine what it can lead to... … Did anybody experience the same issue?
 5ANA
[08:39] <lordievader> Install and open `pavucontrol` to see if the audio is going to the right sink.
[10:11] <lnielsen> What/where is this Telegram channel IrcsomeBot is relaying? Just curious
[10:14] <Maik> lnielsen: have a look on the kubuntu website, there should be a link to telegram
[10:30] <lnielsen> Maik: ah, yes, here: https://kubuntu.org/community/  thanks
[10:33] <Maik> np, yw
 sudo apt-get install -t hirsute-backports amarok … Reading package lists... Done … E: The value 'hirsute-backports' is invalid for APT::Default-Release as such a release is not available in the sources
 Why am I getting this error?
 Anyone please help.
 hello. What is the default audio program used in kubuntu? I would like to remove it and install kmix
[11:20] <oosk> Hello what should I do with these errors please ?https://paste.ubuntu.com/p/HjvrbNSjKv/
[11:22] <alkisg> oosk: run a `sudo LANG=C apt install -f`, and paste the whole terminal output, so that we can see which one is the first error
[11:32] <lnielsen> oosk: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1917971
[11:34] <lnielsen> I do understand some French and from what I can tell you paste says there are various dependency problems
[11:34] <lnielsen> your*
[11:34] <lnielsen> You could try to fix those with LC_ALL=C apt -f install and then tell us what the output of that is
[11:35] <lnielsen> Did you mix repositories in an attempt to install packages otehrwise inaccessible to you?
[11:35] <alkisg> Yeah, the kernel update can't write the initramfs and it's blocking the rest of the updates; but since he's using linuxmint, I told him to ask there lnielsen
[11:35] <alkisg> (he also asked in many other channels...)
[11:38] <oosk> 3 others*
[11:38] <oosk> because in LM channel they said "reinstall os"
[11:38] <alkisg> !linuxmint
[11:38] <alkisg> Unfortunately this is a problem with distributions with less users
[11:39] <alkisg> They don't have enough support
[11:39] <alkisg> (or packages of good quality)
[11:39] <alkisg> Now if you run `which apt`, you'll see that you're using a different apt than the rest of the world, because they have to patch it just to prevent their hand-modified packages from breaking
[11:40] <alkisg> If you run `apt -y update`, it'll even say "not supported"; just reinstall with normal ubuntu ;)
[11:41] <lnielsen> alkisg: oh, I missed that
[11:41] <alkisg> lnielsen: yeah that was in #ubuntu-mate
[11:42] <lnielsen> Well, I have nothing against Mint, but it's never to late to develop an antipathy :P
[11:42] <lnielsen> too*
[11:43] <lordievader> oosk, alkisg : Why can't it write the initramfs? Disk full?
[11:43] <alkisg> I spent an hour before realizing that they're shipping an "apt override" just to prevent system breakage :(
[11:43] <alkisg> lordievader: no idea, I stopped the analysis when I realized it was linuxmint
[11:44] <oosk> https://paste.ubuntu.com/p/pPffxFfHxT/
[11:44] <oosk> Boot is full
[11:44] <oosk> Disk is encrypted
[11:46] <oosk> alkisg
[11:46] <lordievader> oosk: Did you already remove unsused kernels? (The packages, not the kernels itself)
[11:46] <oosk> I tried but it seems not working
[11:47] <oosk> I got only 3 kernels installed so why boot is full ?
[11:48] <lordievader> oosk: Could you pastebin the output of `df -h /boot` and `du -hs /boot/*`?
[11:49] <oosk> https://paste.ubuntu.com/p/D6zYYSwzZf/
[11:50] <oosk> https://paste.ubuntu.com/p/fXJJH59Dzh/
[11:51] <lordievader> oosk: What is the output of `dpkg -l|grep linux-image`?
[11:52] <oosk> https://paste.ubuntu.com/p/bVqJ3nGwSb/
[11:52] <lordievader> In Ubuntu land an `apt-get autoremove` should leave only the previous and current kernel. That doesn't seem to be the case with you. Might be Mint policy.
[11:53] <oosk> I'll be back in one hour max
[11:53] <oosk> thx everyone
[11:54] <lordievader> oosk: You want to purge those -5[0-9]- kernels (`apt purge linux-image-5.4.0-5*-generic` should select all of those, but check the output). And the -26- kenrel needs to be manually removed.
[11:54] <lordievader> That will clear up some space.
[11:54] <lordievader> After that you should be able to run your updates again.
 I'm very sorry for asking it for the third time but I truely am unable to figure out what's the issue. I can not make backports to work on Kubuntu 21.04. Can anyone please help?
 https://paste.ubuntu.com/p/rJNtgfnCcQ/
 This is the error that I'm getting
[12:24] <lordievader> The error is quite clear, ain't it? "as such a release is not available in the sources"
[12:24] <lordievader> There likely is not support (yet) for 21.04 in the backports repo.
 What does 'sources' here represent? Is it the repositories? Or my local sources.list file in /etc/apt/ ?
 Oh! Can you enlighten me on this a bit? I manually visited http://archive.ubuntu.com/ubuntu and in the /ubuntu/dists directory, there is hirsute-backports. Although there isn't any Package in /ubuntu/dists/hirsute-backports/main/binary-amd64
 But there are "Release" files on the repo ar http://archive.ubuntu.com/ubuntu/dists/hirsute-backports
 *at
[12:49] <lordievader> Ah, wait. Perhaps I'm misinterpreting the message. Is the hirsute-backports release part of your sources? (`cat /etc/apt/sources.list` and `cat /etc/apt/sources.list.d/*.list`)
 https://paste.ubuntu.com/p/T4mkF5mgb8/
 https://paste.ubuntu.com/p/rCyBQBMX4D/
 Also ran `sudo apt update` numerous times to ensure hirsute-backports gets listed and there are no errors.
 https://paste.ubuntu.com/p/k72RbQJTNH/
[12:57] <Mamarok> and why don't you use the kubuntu backport sources?  you should have something like deb http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ hirsute main
[12:57] <lordievader> musxigxn: What is the output of `apt-cache policy amarok`?
 lordievadar, https://paste.ubuntu.com/p/GgkdrkvjvZ/
[12:58] <Mamarok> as for "backprts of Amarok": there is no such thing, at least not that I know of, you are lookign for the PPAs for the current alpha release I guess?
 I mean lordievader
 Mamarok, amarok is just for testing if the ubuntu backports repo works or not. If the package is not in the repo, the error must be different. In my case, it is related to 'hirsute-backports' being invalid for APT.
[13:00] <lordievader> Unless it is still in the kubuntu backports, I'm afraid amarok is no longer maintained: https://packages.ubuntu.com/search?keywords=amarok
[13:01] <lordievader> 18.04 seems the latest release to have the package.
 Error is not specific to the package. I tried it on other packages like gimp, libreoffice.
[13:01] <Mamarok> that's what I jsut said, you need the PPAs from pgomes or joe-yasi for the current Amarok build
 If the package isn't available in the backports repo, APT would throw a relevant error instead of saying that the release is invalid.
 I do not want amarok. I just want to get hirsute-backports repo to work.
[13:02] <Mamarok> change to the main server for your updates?
 Already using the main server.
 i.e deb http://archive.ubuntu.com/ubuntu hirsute-backports main restricted universe multiverse
[13:03] <lordievader> Looking at the size of the Packages.gz file, I think it is too early for -backports. Those files are empty for main and multiverse.
[13:04] <Mamarok> the only backports I can see that work are the kubuntu-ppa ones
 lordievader, yes, I saw that too. But how to confirm if the error is due to this fact only?
[13:04] <lordievader> musxigxn: why do you need hirsute-backports to work?
 I didn't need them. I was just reading about backports in general and liked the idea. I just gave it a try and received that strange error. I just want to know the root cause of the error for my own understanding.
[13:08] <Mamarok> again, if you want Kubuntu backports, you should add the Kubuntu-ppa backports, the other one is probably without any Plasma/KDE packages
[13:08] <lordievader> I'm quite certain the backports repo is not yet in use, causing the error. Guess it is too early in the release cycle for 21.10 for there to be backports.
 @Mamarok, Kubuntu PPA backports are different than Ubuntu backports.
[13:08] <Mamarok> the kubuntu-ppa has the 5.81.0 framework packages
[13:09] <Mamarok> yes, but since you are in the @kubuntu channel here we talk about Kubuntu here :-)
 Kubuntu is essentially Ubuntu. Isn't it?
 Same packages. Same repositories (Default).
[13:14] <Mamarok> nope, different team
[13:15] <Mamarok> different desktop, etc. and the backports are specific
[13:16] <Mamarok> the only thing you might get in the ubuntu backports that is common are newer kernel versions
[13:22] <BluesKaj> Hi folks
[13:24] <Nie_Wer> Hello BluesKaj
[13:24] <BluesKaj> hi Nie_Wer
[14:27] <oosk> lordievader https://paste.ubuntu.com/p/GHHzdB4VRY/
[14:28] <oosk> Hi it's still here.
[14:29] <lordievader> Ah, lovely you're in 'that' situation. Try removing the -26- kernel and initramfs manually, perhaps that clears enough space for the new kernel.
[14:32] <oosk> I don't have that one
[14:32] <oosk> https://paste.ubuntu.com/p/bVqJ3nGwSb/
[14:36] <oosk> https://paste.ubuntu.com/p/JTjBw2pkQh/
[14:36] <alkisg> oosk: no. What was the output of `ls -l /boot`; it's best to delete some old initramfs from there, and let it run it course
[14:37] <oosk> https://paste.ubuntu.com/p/wb6hVSRQSQ/
[14:38] <lordievader> oosk: In there (/boot) you have a -26- kernel and initramfs
[14:38] <alkisg> oosk: sudo rm /boot/initrd.img-5.4.0-6; sudo apt install -f
[14:38] <alkisg> oosk: sudo rm /boot/initrd.img-5.4.0-6*; sudo apt install -f
[14:38] <alkisg> the second one; I forgot the asterisk in the first one
[14:38] <lordievader> I'd leave the -6*- kernels als there are still packages for those. A purge should clean those up (including all the modules left over)
[14:39] <alkisg> lordievader: initramfs isn't a package file
[14:39] <alkisg> It's generated, not part of dpkg -L
[14:39] <lordievader> Hrmm, fair enough
[14:39] <oosk> https://paste.ubuntu.com/p/tn5b4sG8Qz/
[14:40] <alkisg> oosk: use LANG=C, and paste all the output; did it remove the kernels above what you just sent?
[14:40] <alkisg> export LANG=C
[14:40] <alkisg> so that we can read the output of the following commands
[14:41] <oosk> https://paste.ubuntu.com/p/VC2mYnjWqw/
[14:41] <alkisg> oosk: run `ls /boot`, is it cleaner now, does it have more free space?
[14:42] <alkisg> (or df -h)
[14:43] <oosk> https://paste.ubuntu.com/p/B43HspKSMr/
[14:44] <alkisg> OK enough space; the kernel ^rc packages will be cleared when the other errors get avoided,
[14:45] <alkisg> So the errors now are basically samba-common and grub-efi-amd64,
[14:45] <alkisg> oosk, did you do anything about that, e.g. like the rm /var/lib/dpkg/info/samba-common* that you suggested?
[14:45] <alkisg> Do you have any indication why samba errors out?
[14:45] <oosk> No
[14:46] <oosk> I wanted to know if it's a good solution
[14:46] <alkisg> OK
[14:46] <oosk> ?
[14:46] <oosk> Should I try these recommendations?
[14:46] <alkisg> No
[14:46] <oosk> Ok
[14:46] <alkisg> They'll make things worse
[14:46] <alkisg> Can you install a package? sudo apt install x11vnc
[14:47] <oosk> You want teamviewer?
[14:47] <alkisg> I have vnc and anydesk
[14:47] <alkisg> teamviewer doesn't run for me it says...
[14:47] <alkisg> They complain that I used it a lot, which I didn't
[14:47] <alkisg> But if you can install x11vnc, it's just one command to share screen
[14:48] <alkisg> x11vnc -connect alkisg.ltsp.org
[14:48] <oosk> PM me
[14:48] <oosk> i'll give you anydesk
[14:52] <alkisg> oosk: wait don't leave
[14:52] <alkisg> I'm loooking for a command
[14:52] <oosk> Ok thqnks
[14:52] <alkisg> Meh I'll just re-write it
[14:53] <oosk> what is it please
[14:54] <oosk> do you know how to fix this please
[14:55] <oosk> its a minor pb
[14:55] <alkisg> oosk, the first problem was fixed. This one is BIGGER though
[14:55] <oosk> LOOOL
[14:55] <alkisg> Because it means that you have deleted files from /lib/dpkg manually
[14:55] <oosk> thanks a lot
[14:55] <alkisg> Wait, give me a bit of time
[14:56] <oosk> its due to LM upgrade from 20 to 20.1
[14:58] <oosk> I have to do this for every line
[14:58] <alkisg> No
[14:58] <alkisg> Wait, I need to go, let me sum up:
[14:58] <oosk> thanks a lot
[14:58] <alkisg> (I'll be back in an hour, wait: )
[14:58] <alkisg> I want to tell to the channel what I did
[14:58] <alkisg> And to you; keep it in your notes
[14:59] <oosk> No problem
[14:59] <alkisg> I inserted an `exit 0` at the top of samba-common.postinst and grub-efi-amd64.postinst,
[14:59] <alkisg> so that apt finishes; we can then run these postinsts later to see what's wrong,
[14:59] <alkisg> then I removed your ^rc kernels,
[14:59] <oosk> what's rc?
[14:59] <alkisg> rc means a package that was removed, but without its config files getting removed,
[14:59] <oosk> old one? non used
[14:59] <oosk> ok thanks
[14:59] <alkisg> and "ic" was a linux version that was half-uninstalled,
[15:00] <alkisg> and now you have a problem where something (possibly the upgrade) deleted the dpkg information for some packages, not all of them,
[15:00] <alkisg> if you apt install --reinstall package, then this will go away,
[15:00] <alkisg> but you DONT need all these packages; some of them might even conflict; they may only be needed in the older linuxmint,
[15:00] <alkisg> in which case, you need to apt install --reinstall package and then apt purge package
[15:01] <oosk> How can I know if I need them or not ?
[15:01] <alkisg> But you need to see e.g. in a linuxmint live cd which ones should be there and which ones not
[15:01] <oosk> Ok I see
[15:01] <alkisg> If you see a lot of changes, don't do it
[15:01] <oosk> it's not a big deal
[15:01] <alkisg> If you see that it only installs/purges a single package, do it
[15:01] <oosk> Upgrade in Linux isn't very stable I see
[15:01] <alkisg> It may cause other problems in the future, better fix it now.
[15:01] <alkisg> It's very stable. But in mint it's not
[15:02] <alkisg> Really, don't use mint next time, they break packaging
[15:02] <alkisg> Time to go! Cheers!
[15:02] <oosk> Thanks a lot Sir !
[15:03] <alkisg> np
[15:03] <alkisg> oosk
[15:03] <alkisg> ah, and another thing,
[15:03] <alkisg> You'll want to fix samba-common and grub-efi too, the postinst
[15:03] <alkisg> If you're here later on we can have a look together
[15:03] <oosk> Ok thanks !
[15:04] <oosk> If it's work without
[15:04] <oosk> I don't care
[15:04] <oosk> of them
[15:06] <oosk> As long as it doesn't trigger another mistake in the future.
[15:06] <oosk> That's fine with me.
[17:20] <n0yd> Hello
[17:21] <n0yd> Is there a way to disable the sound that comes along with using function keys (and i assune other hardware keys) to change volume?
[17:21] <n0yd> I'd like to disable to "bloop" sound for everytime you press it
[17:28] <n0yd> nvm, found the answer ;)