[00:09] Hm. I can start krunner from the command line, and it works once, but then not again? [00:09] That's... weird. [00:46] crell have you uninstalled it and tried again? [00:46] purge files [00:50] I have not. Which package is krunner in? [00:52] plasma-workspace [00:59] crell: 'sudo apt purge krunner' then reinstall it [01:14] krunner is not it's own package. It is a component of the package previously mentioned, plasma-workspace [01:14] !info krunnner [01:14] Package krunnner does not exist in focal [01:14] eg^ [01:16] apt search krunner [01:16] has plenty of info [01:16] ..also, easier instead of purging them reinstalling, is : sudo apt-get install --reinstall [01:16] Hm. That seems a bad thing to uninstall. :-) I'll try the reinstall command. [01:17] purging will get rid of all files and configs, not the same [01:17] two different things [01:17] After doing a reinstall, do I need to restart KDE? [01:17] shouldn't need to [01:18] Are you bridged in from Slack or something? :-) [01:18] @sigAIO install -reinstall overwites whatever filles it currently has with factory install config files [01:18] Still no Alt-F2 response. Running `krunner` on the command line brings up the dialog once, but once only. [01:19] If I run into problems and I need to reinstall a package that I have no need to save config files I purge packages. [03:57] does kubuntu have a bootable usb drive creator? [04:18] yes, in kubuntu 20.04: usb-creator-kde === cesar_ is now known as Guest14675 [05:26] LtVerdier was added by: LtVerdier [05:30] Hi everybody, … I've got the Kubuntu 20.04 LTS and despite "the Screen lock after 15 min" choice, after serveral hours of inactivity a simple mouse move wake the screen without passwd. Did I forget to do something ? [05:51] josebenaque was added by: josebenaque [06:24] @LtVerdier - that makes me suspect that you have a permissions problem in your home [06:24] probably in your ~/.config [06:24] probably chowning your home will fix that [06:24] !chown [06:24] An explanation of what file permissions are and how they can be manipulated can be found at https://help.ubuntu.com/community/FilePermissions [06:30] Mpramono was added by: Mpramono [06:48] Thakns for this answer. The '/home/~' belong to me, I did a chown -R from "~/.config" to test your solution and wait for the screen lock [07:25] hello, on a laptop I'm testing firefox -> hamburger menu -> customize ... -> disabled Title Bar [07:25] in this way I recovered some precious pixels [07:25] the only thing is that the title of the tabs are dark gray on slightly lighter gray [07:25] it happens also to you? [07:27] Good mornin [07:27] * Good morning [08:19] hi. kubuntu 20.04 running here. works well overall, except that the systray icons are blank. so, the systray is there, the icons are there (i can see the context menus when I right-click there), but the are where I nornmally would see the icons are empty. [08:20] I can't find a bug report about this. if I remove the systray and reinsert it into the panel again, the icons do show up. [08:23] icons from KDE specific subsystems like kde connect or the clipboard do appear, however. [09:22] @valorie, No relation with the ownership. I was the owner of the entire /home/~. Do you have another explanation ? It's a safety problem for me... === Lord_of_Life_ is now known as Lord_of_Life === hussam_ is now known as hussam === kubuntu is now known as Guest76954 === pmsobrado is now known as pasogo91 [11:43] Federico Pacini was added by: Federico Pacini === utente is now known as Guest57072 === steveire is now known as steveire__ === steveire__ is now known as steveire [12:10] Hi folks === mike_ is now known as Guest35943 === Cubic is now known as Guest89606 === Guest89606 is now known as Exarmatio === pmsobrado is now known as pasogo91 === kubuntu is now known as Guest18519 [16:57] * masonbee-M uploaded an image: Screenshot_20200507_185636.png (23KB) < https://kde.modular.im/_matrix/media/r0/download/kde.org/pejaIUfRcGCnQCexQCxfCMrq > [16:57] BluesKaj: Top of the Riot screen (using the web client) there is a lot of stuff about Kubuntu 18.10 being released today. [17:02] masonbee-M, 18.10 is EOL [17:03] !EOL [17:03] End-Of-Life is when security updates and support for an Ubuntu release stop. Make sure to update Ubuntu before it goes EOL so you get updates promptly for newly-discovered security vulnerabilities. See https://help.ubuntu.com/community/EOL and https://wiki.ubuntu.com/Releases for more info. Looking to upgrade from an EOL release? See https://help.ubuntu.com/community/EOLUpgrades [17:03] BluesKaj: At the top of this forums page, it says it is being released today 😇 [17:04] BluesKaj: Who do I contact to get them to update is? [17:05] well, it's obviously out of date no matter what that url states === me is now known as Guest48696 [17:06] Yes, but it should probably be changed is what i am getting at. I figured you either are, or would know who is, the admin. [17:08] no idea who the admin would be, but you can report that in #kubuntu-devel chat if you wish [17:09] OK, thank you. [17:09] np [17:10] there are no admins for matrix === RikMills changed the topic of #kubuntu to: Official Kubuntu support | FAQ: https://community.kde.org/Kubuntu | Pastes: https://paste.ubuntu.com | Chat in #kubuntu-offtopic | Guidelines: https://ubottu.com/y/gl | Kubuntu 20.04.0: https://kubuntu.org/news/kubuntu-20-04-lts-has-been-released/ | https://forum.kde.org, https://www.kubuntuforums.net [17:36] https://github.com/matrix-org/matrix-appservice-irc/issues/703 [17:36] it's just the matrix bridge failing again [17:37] I assumed so [18:09] Slight discrepancy in 18.04 [18:09] htop is saying all cores are free and System Monitor is saying 60-80% of CPU in use [18:10] 'sudo dpkg --configure -a' has been running an hour [18:11] I have no idea what is sucking up the CPU, because I cannot see any process in the Process Table that would be using it, nor can I see any load in htop [19:29] wranglar was added by: wranglar === roberto_ is now known as roberto__ [21:03] A_bdoh was added by: A_bdoh [21:11] have you tried restarting your session? === Lord_of_Life_ is now known as Lord_of_Life [22:54] (Photo, 720x1280) https://irc-attachments.kde.org/UkHJgHIh/file_29109.jpg hi my computer isn't booting, it reaches this point and then nothing what should I do? [22:57] salvaconnome: which kubuntu version is this? can you speculate on the cause of the malfunction - did it work previously, what changed? [22:57] salvaconnome: basic hardware details would also help. [22:57] and try switching to a tty, see whether oyu got a text login prompt there. [22:57] !tty [22:57] To get to the TTY terminals 3-6, use the keystroke Ctrl + Alt + F3-F6 respectively. Ctrl-Alt-F2 or Ctrl-Alt-F1 will get you back to your graphical login (Ctrl-Alt-F7 on 16.04). To change TTY resolution, see https://help.ubuntu.com/community/ChangeTTYResolution [22:57] I'm on Kubuntu 19.10 [22:59] I had another problem first, I can't turn off the power. It was stuck at reboot: power down [23:00] I tried doing an update to the system and then rebooted [23:01] (Photo, 1280x720) https://irc-attachments.kde.org/MKJuv7zQ/file_29110.jpg [23:03] (Photo, 1280x720) https://irc-attachments.kde.org/15f00Nh1/file_29111.jpg [23:05] will try in a moment [23:08] tty works [23:08] I'm on tty right now [23:09] (Photo, 1280x720) https://irc-attachments.kde.org/IdYY687W/file_29112.jpg [23:13] doh, your /boot is a 53 GB file system [23:13] that's unusually large [23:13] lulz [23:14] is that a problem or just an unusual thing? [23:15] the kernel image listed on the top of your grub menu shot, which will be booted by default, looks like a kernel-ppa image. [23:15] /boot being huge is probably just unusual, i assume it's not a problem [23:15] should I remove this kernel and go back to the old one? [23:17] maybe later, for now now just reboot to one of the 5.3.0 ones [23:17] see whether this makes booting work again [23:17] which graphics hardware and driver do you have there? [23:18] Nvidia. don't remember exactly, is an old PC, I'll tell you in a moment when I reboot on 5.3 [23:20] no more questions, your honor. [23:20] 😆 [23:20] hahaha [23:21] okay 5.3 is working [23:21] (Photo, 720x1280) https://irc-attachments.kde.org/m7Kd7R08/file_29113.jpg [23:22] so you were using old nvidia hardware with maybe their proprietary driver (probably a very old one, too, then) with an unsupported test kernel, and that didn't let the nvidia driver start up properly. i'm not terribly surprised. [23:23] 😅 sorry [23:23] GeForce 8600 GT [23:23] no worries. ;) [23:23] G84 [23:24] released in april 2007 [23:24] any other info you need? what should I do now? delete new kernel and stay with old one? [23:25] yes, keep using supported kernel images and you'll probably be more or less fine [23:25] okay [23:25] sudo dpkg --purge linux-image-unsigned-5.6.0-050600-generic [23:25] with this old a graphics card you'll probably also have a very old CPU, though [23:25] is this the best way? [23:25] yes [23:26] i'd always prefer apt [23:26] Core 2 Quad Q9400 @ 2.66GHz [23:26] apt purge linux-image-unsigned-5.6.0-050600-generic [23:26] thanks will do that then [23:27] chances are this cpu got no or not all the meltdown / spectre security patches [23:28] it'll also eat much power compare dto todays' systems with similar compute power. [23:29] yikes [23:30] so I'll should throw it trough the window and then pick the pieces and send it to the trash? [23:31] problem is I have no money to buy a new one atm [23:31] well, if you have the coins to replace it. [23:31] see ;) [23:31] haha [23:32] it's not my computer actually but my mom's... I have a much faster and newer laptop... [23:32] anyways [23:32] I uninstalled the kernel and are rebooting now to see if it starts normally [23:34] aha, so mom gets the trash! ;-) [23:34] It wasn't trash when she got it (10 years ago) [23:34] lmao [23:35] was a pretty decent computer at that time [23:35] time flies [23:36] if you have a good book, yes === dilfridge is now known as DarthDilfridge [23:47] okay so now the computers turns on okay but it won't turn off [23:48] sometimes it says nothing sometimes it says this reboot: shut down message [23:52] hmm, those are usually caused by buggy bioses, bioses not supporting linux well [23:52] sudo shutdown -h from tty worked fine [23:53] yeah the bios from this monstrosity of a computer is buggy a.f. [23:53] I'm doomed then [23:53] you got the latest there was? [23:53] nothing showed up on the screen [23:54] it just went dark and then shut down [23:54] also there is possibly a workaround at http://iam.tj/prototype/enhancements/Windows-acpi_osi.html [23:55] comparing this dedicated graphics card https://www.videocardbenchmark.net/gpu.php?gpu=GeForce+8600+GT&id=64 to 2016's (CPU) integrated graphics card: https://www.videocardbenchmark.net/gpu.php?gpu=Intel+Iris+Pro+580&id=3481 [23:58] lol I assume higher numbers are better