[03:29] <lotuspsychje> good morning
[09:54] <bigfoot-> Hi.  Since upgrading to 20.04 focal, KDE's ALT-F2 "run command" global shortcut doesn't work anymore; is this a known issue? (Others, like ctrl-alt-T starting a terminal, still work fine.)
[09:55] <bigfoot-> Everything else went surprisingly smoothly, besides the fact that xpdf seems to be gone for good now. :(
[09:55] <lotuspsychje> bigfoot-: 20.04 is still in development mode right now, we strongly advice to help testing it on daily iso base, instead of early upgrades
[09:55] <lotuspsychje> bigfoot-: would help the devs, if you can doublecheck this on a clean daily to see if you can reproduce this
[09:55] <bigfoot-> ok.
[10:15] <lotuspsychje> bigfoot-: in 2h Blueskaj will join, he's on kde 20.04 also, i can ask him aswell
[10:15] <lotuspsychje> idle a bit here
[10:17] <bigfoot-> In the Kubuntu live image, it works fine.  Starting "krunner" manually also works ...
[10:17] <bigfoot-> and: ALT-F2 gives me a "Q" character in the currently open terminal.
[10:18] <lotuspsychje> so we can conclude this is caused by your upgarde bigfoot- ?
[10:18] <lotuspsychje> *upgrade
[10:18] <bigfoot-> probably
[10:18] <lotuspsychje> allrighty, thank you for doublechecking this
[10:25] <bigfoot-> I wonder whether this guy experienced the same issue: https://bbs.archlinux.org/viewtopic.php?id=253297
[10:26] <lotuspsychje> !info kde-plasma-desktop
[10:27] <lotuspsychje> this your version bigfoot- ?
[10:28] <bigfoot-> 5.18.2?  Yes.
[10:28] <bigfoot-> Interestingly, kde-plasma-desktop isn't installed at all.
[10:29] <lotuspsychje> nevermind me, been too long since i played with kde
[10:31] <bigfoot-> moving ~/.config away (as suggested by the archlinux forum post I mentioned) solves the problem
[10:31] <bigfoot-> ... now the fun begins, finding the broken config file and restoring the remaining ones ...
[10:47] <bigfoot-> OK, I now know how to fix this without manually touching ~/.config .
[11:05] <bigfoot-> As this may bite other upgraders, should I report a bug?
[11:07] <lotuspsychje> bigfoot-: didnt you say you did not have this issue on a live?
[11:30] <bigfoot-> lotuspsychje: Yes.  But as it seems to be a config migration issue (from Plasma 5.16.5 to focal's 5.18.3), other upgraders might be bitten as well.
[11:30] <bigfoot-> My description of bug + fix on KDE's own forums: https://forum.kde.org/viewtopic.php?f=17&t=164820&p=429259#p429259
[11:32] <lotuspsychje> bigfoot-: your choice to do what you want and test, but please avoid making an official bug on 20.04 based on upgrades
[11:35] <bigfoot-> lotuspsychje: That's why I was asking.  But I'd bet this issue is still there when 20.04 gets released, biting other upgraders.
[11:35] <lotuspsychje> bigfoot-: maybe, but i would advice to start testing this after final beta coems out
[11:36] <lotuspsychje> right now, things are still shaping up
[11:57] <lotuspsychje> bigfoot-: what does ALT+space do?
[12:01] <bigfoot-> lotuspsychje: before my fix: nothing; now: works as expected.
[12:02] <lotuspsychje> bigfoot-: BluesKaj just tested on his 20.04 and seems to work, so must be your upgrade bork
[12:02] <bigfoot-> Yes, as I said -- it seems to be a config migration issue
[12:04] <BluesKaj> bigfoot-, I did a complete reinstall a few weeks ago and there were definitely some config changes on the new install 
[14:01] <gsedej> I have issue with desktop ubuntu-installer on EFI system. System has 1 ssd (with existging EFI 18.04). I am trying to install 20.04 EFI on external USB drive. Problem is that EFI-system-partition is being used by internal SSD drive (and brakes GRUB)
[14:44] <gsedej> I reported bug. Should I add more info? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1866358
[14:47] <oerheks> what if you set disk order to the external too? not only boot priority, but hdd listing
[14:51] <gsedej> what do you mean disk order? In BIOS/UEFI?
[14:55] <oerheks> yes
[14:57] <gsedej> well I was playing quite much with actually saving the existing installation... so but the main issue is, as mentioned, EFI-partition on USB was not "installed" (empty) and fstab on USB-root-ext4 was trying to use EFI-partition from SSD
[16:36] <BluesKaj> hope this isn'r an isolted problem just for kde/plasma or is this seen on other flavors as well ? https://paste.ubuntu.com/p/wDSsdSh2YQ/
[18:31] <takov751> greetings i have a quick question
[18:32] <takov751> about ignoring a broken package
[18:33] <takov751> so apt wont remove it.
[18:33] <takov751> I just installed steam-launcher
[18:35] <takov751> i had to make dpkg ignore python package dependencies,because in 20.04 there is no package called python. As of course python2 is deprecated
[18:36] <takov751> however whenever i would like to install or remove anything its just wants to remove steam ,because of the missing dependencies
[18:37] <oerheks> i guess you want python3?
[18:37] <oerheks> want/need ..
[18:49] <takov751> yes i would need python3 ,however something like steam-launcher depends on python2 .... for some reason and aliasing python3 would just brake the stea
[18:49] <takov751> m