[01:52] <FurretUber> Hi, what is the correct way to do something as "sudo apt purge linux*generic*" now?
[01:57] <FurretUber> As globs seem to no longer work on apt
[02:18] <Bashing-om> FurretUber: Cleaner way ' sudo apt --purge autoremove ' - will leave the current kernel and one other.
[02:19] <FurretUber> The example I took from a case where an user had to install the lowlatency kernel but it was not possible to open the grub menu (this I don't know why)
[02:20] <FurretUber> So after confirming linux-lowlatency was installed, that command was used to remove the generic kernel as grub was the generic kernel
[02:20] <FurretUber> But using globs on 20.04 apt is no longer possible
[02:22] <FurretUber> Using the same example: https://paste.ubuntu.com/p/bSrdDBt8Jy/
[02:22] <FurretUber> I imagine this change will cause some programs to break, and I would like to be aware what would be the 20.04 equivalent
[02:29] <FurretUber> Globbing not working on apt will break at least one of my image creation scripts
[02:54] <lotuspsychje> good morning
[05:03] <AlexMax> I'm having issues with the graphical installer
[05:04] <AlexMax> It seems super-desparate to tell me about how it's going to create "Primary" and "Logical" partitions despite booting into EFI mode
[05:04] <AlexMax> Also, it seems super-desparate to tell me that it's going to format a swap partition located on a completely different hard drive that I would prefer the installer not even touch
[05:05] <AlexMax> Also it mentions boot loaders - which I thought wasn't a thing on EFI
[05:05] <AlexMax> At least the wiki page about EFI notes that I really shouldn't be seeing that selection in EFI mode
[08:43] <Dr8g0n> Hey all - I installed 20.04 yesterday on HP 360. All very very well. Except for multi-touch gestures on touch screen (these on touchpad work).
[08:43] <Dr8g0n> Anybody knows how to fix?
[08:45] <lotuspsychje> Dr8g0n: mostly when i tweak system, i try dconf-editor but i dont see much about touch or gestures, maybe you can look around too?
[08:45] <lotuspsychje> Dr8g0n: an other approach for touchscreen devices, is installing unity desktop and test things there too, they usualy have great touch support
[08:47] <Dr8g0n> lotuspshychje thanks but I do like Gnome too much... Looking for a solution on 3.36...
[08:48] <Dr8g0n> lotuspsychje ... (getting to grips with IRC again as well - it's been over a decade I think)
[08:48] <lotuspsychje> Dr8g0n: yeah i understand
[08:49] <lotuspsychje> i havent touched gnome much yet on touch devices yet, think it might still have rough edges
[09:36] <freezer> hi
[09:38] <pavlushka> nvidia-driver-440 is not working on 20.04, blacklisted nouveau but still no display
[09:38] <freezer> Getting these kinds of Errors with Intel Wireless 7260
[09:38] <freezer> https://paste.ubuntu.com/p/RKr4BqXWRc/
[09:38] <freezer> it can connect to wifi, but a lot of packetloss and these resets going on 
[09:39] <freezer> already ordered some USB wifi cause i need this machine on the wifi
[09:43] <tomreyn> freezer: ubuntu version, kernel version?
[09:44] <freezer> 20.4 @ 5.4.0-21-generic
[09:44] <tomreyn> also get the pci id from    lspci -knn | grep -EA3 'Network controller' | nc termbin.com 9999 
[09:45] <tomreyn> oh this is #ubuntu+1, sorry, i'm still waking up
[09:45] <freezer> https://termbin.com/6opd
[09:45] <freezer> haha
[09:46]  * pavlushka bribes coffee to tomreyn 
[09:46] <freezer> ubuntu-drivers listed showed backport-iwlwifi-dkms
[09:46] <freezer> installed those, maybe will fix it
[09:47] <tomreyn> yes, that's worth a try. 
[09:49] <tomreyn> "Loaded firmware version: 17.3216344376.0" - i'd also look for a newer one
[09:50] <freezer> that backport broke it entirely https://paste.ubuntu.com/p/yk7C8vhVt7/
[09:51] <freezer> trying reboot
[09:52] <freezer> ok works now, gonna test stability
[09:54] <freezer> no same issues
[09:54] <freezer> where can i find a newer firmware?
[09:56] <tomreyn> you could potentially find newer firmware in the "linux-firmware" git repository, but there doesn't seem to be any. also this is not the very latest hardware so normally it should be working out of the box. i guess it's something specific to this kernel version. then.
[09:57] <freezer> darn, and there i thought i just go ahead and use 20.04
[09:57] <freezer> well, guess i still could and use that usb wifi with RTL chipset
[09:58] <freezer> thank you
[09:59] <tomreyn> try a 18.04 live iso for now
[09:59] <tomreyn> or !mainline
[09:59] <tomreyn> !mainline
[10:00] <tomreyn> those kernels are not supported, and you need ensure you'll upgrade yourself whenever upgrades are built (there are some scripts which automate parts of this)
[10:02] <freezer> would kernel 5.6 still work with the nvidia drivers?
[10:04] <Dr8g0n> there's a channel #ubuntu-touch which seems more appropriate for my question but it is invite-only
[10:05] <Dr8g0n> anyone here can add me?
[10:06] <pavlushka> nvidia-driver-440 is not working on 20.04, blacklisted nouveau but still no display, any clue?
[10:08] <freezer> i have that same driver, but running desktop on the integrated intel
[10:08] <freezer> NVIDIA settings say all fine though, driver loaded, card detected etc
[10:10] <freezer> you have any IGP, maybe its displaying it on that?
[10:18] <tomreyn> freezer: i wouldn't expect nvidia (proprietary) drivers to work with non default kernel versions, no.
[10:18] <tomreyn> (that's in response to "would kernel 5.6 still work with the nvidia drivers?")
[10:21] <pavlushka> tomreyn: the version is 5.4 on 20.04 and the card works with the 440 driver on a 5.5 kernel on arch
[10:27] <tomreyn> those driveres are versioned, too, and usually further customized by the distribution shipping them. unless you using drivers you downloaded from nvidia.com, which would not likely work on ubuntu anyways.
[10:27] <freezer> [  299.520221] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 UTC 2020
[10:27] <freezer> worked with kernel 5.6 and DKMS
[10:27] <tomreyn> * you are
[10:28] <lotuspsychje> Dr8g0n: ubuntu touch is a stopped project, see the community group #ubports now
[10:32] <freezer> tomreyn, same issue with kernel 5.6 :(
[10:32] <freezer> think i just install archlinux, at least that works out of the box with Folding@Home client
[10:32] <pavlushka> tomreyn: finally it loaded but taking longer time to load the desktop than on nouveau and performing worse than nouveau as the mate-terminal transparency gone
[10:33]  * pavlushka switching back to nouveau
[10:35] <tomreyn> freezer: hmm, or you can try a supported ubuntu release.
[10:45] <freezer> ok think 18.04 should still work fine. 
[10:45] <freezer> don't wanna spend potential many hours getting to know Arch
[10:45] <freezer> although i installed it once before
[10:49] <lotuspsychje> freezer: did you check your ubuntu-drivers list ?
 ubuntu-drivers listed showed backport-iwlwifi-dkms
[10:51] <lotuspsychje> no nvidia drivers?
[10:52] <tomreyn> ah sorry, this is about nvidia, i dunno then
[11:01] <freezer> nvidia worked for me
[11:01] <freezer> im getting the same FW error with Ubuntu 18.04 setup, what the heck is going on 
[11:01] <freezer> maybe broken HW?
[11:02] <tomreyn> hmm, maybe.
[11:03] <tomreyn> searching the web for those outputs you get may help
[11:03] <tomreyn> make sure you got the latest 18.04 installer (and seek support in #ubuntu instead)
[11:12] <freezer> this seems to work https://askubuntu.com/questions/1184601/intel-wireless-adapter-suddenly-not-working-ubuntu-19-10
[11:12] <freezer> sudo modprobe iwlwifi 11n_disable=1 bt_coex_active=0
[11:13] <freezer> but only 54mbits
[11:13] <freezer> and i wanted to have a NAS on there
[11:25] <tomreyn> you disabled 802.11n, so 5 GHz, so you're stuck with (a)bg now
[11:25] <tomreyn> (2.4 MHz)
[11:26] <tomreyn> actually it might do 802.11ac as well, not sure, but apparently not in your case if that's the outcome.
[12:16] <lotuspsychje> Dr8g0n: any luck with your gestures?
[12:16] <freezer> it looks like connecting to a different 5GHz AP is fixing it
[12:17] <freezer> incompatibility with OpenWRT?
[12:17] <freezer> omg
[12:17] <freezer> that is ridiculous
[12:21] <freezer> yes looks like there was a bug for it
[12:21] <freezer> https://bugs.openwrt.org/index.php?do=details&task_id=2679
[12:56] <sumagna> now tell
[12:56] <lotuspsychje> sumagna: wich release are you using now?
[12:57] <sumagna> ubuntu 19.10
[12:57] <lotuspsychje> sumagna: we mostly reccomend to upgrade when final is released, but it depends what the user wants
[12:58] <lotuspsychje> sumagna: we have users that help test bugs out too, and install beta and help the community
[12:58] <sumagna> ohh
[12:58] <lotuspsychje> so its up to you
[12:58] <sumagna> i was thinking about installing
[12:58] <sumagna> but stepped back after a thought came to my mind
[12:59] <sumagna> i dont want mess up the windows 10 os
[12:59] <sumagna> *want to
[12:59] <lotuspsychje> its always wise to backup things before upgrading
[12:59] <sumagna> can it screw up my windows 10?
[12:59] <sumagna> i used windows 10
[12:59] <lotuspsychje> sumagna: its always possible bugs arise on any Os and release
[13:27] <Dr8g0n> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872076
[13:28] <lotuspsychje> tnx to report this bug Dr8g0n 
[13:29] <lotuspsychje> Dr8g0n: you might wanna idle in #ubuntu-quality where testers & devs meet and talk, never know someone tested that
[13:29] <Dr8g0n> lotuspsychje - ok will do.
[13:30] <howarth> Have anyone else noticed mouse freezes under 20.04? I hadn't seen these under 19.10 on a 2008 MacPro with Mac ROMed GTX680 but they occur once a day under current 20.04.
[13:30] <howarth> I've switched over the Xwayland to see if that suppresses the issue
[13:31] <lotuspsychje> howarth: wich nvidia driver in use please?
[13:35] <howarth> nouveau
[13:36] <howarth> Can't use nvidia as it doesn't play well with the Mac ROM'd GTX680
[13:36] <lotuspsychje> howarth: did you tested all drivers from ubuntu-drivers list yet?
[13:37] <howarth> The non-free ones?
[13:37] <howarth> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1797791
[13:37] <howarth> Those won't work
[13:37] <lotuspsychje> the 340 is a bit old indeed, no other drivers list?
[13:38] <lotuspsychje> if you have the 390 in your list, that would be good to test
[13:39] <howarth> nvidia-graphics-drivers-340 is the last one prior to the introduction of the nvidia-modeset 
[13:39] <howarth> https://forums.developer.nvidia.com/t/black-screen-with-mac-version-of-gtx-680/66030/12
[13:40] <lotuspsychje> howarth: did you check ubuntu-drivers list yourself?
[13:40] <howarth> What actually happens is that the Apple HD Cinema display (under nvidia drivers) will light up its LED back into sleep mode indicating that it has lost contact with the graphics card
[13:40] <howarth> I tried 440
[13:41] <howarth> That was enough for me
[13:41] <howarth> It is exactly the same issue as always
[13:41] <lotuspsychje> 440 is a very latest driver...for an older card not the best solution
[13:41] <howarth> the Mac ROMed GTX and Apple motherboard doesn't play well with nvidia-modeset
[13:41] <lotuspsychje> so
[13:41] <lotuspsychje> did you check ubuntu-drivers list ?
[13:41] <howarth> I'd have to go all the way back to 340
[13:42] <howarth> 360 isn't far enough back
[13:42] <howarth> as it has nvidia-modeset... that kills it for this combo
[13:42] <lotuspsychje> howarth: did you check ubuntu-drivers list?
[13:43] <howarth> where is that? You mean in the non-free drivers list?
[13:43] <lotuspsychje> howarth: open a termina and type: ubuntu-drivers list please
[13:43] <lotuspsychje> *terminal
[13:44] <howarth> nvidia-340
[13:44] <howarth> nvidia-driver-390
[13:44] <howarth> nvidia-driver-435
[13:44] <howarth> nvidia-driver-440
[13:44] <howarth> bcmwl-kernel-source
[13:44] <lotuspsychje> ok, can you please test 390
[13:44] <howarth> odd
[13:46] <howarth> Hmmm
[13:46] <howarth> I wonder if they changed that
[13:46] <lotuspsychje> yes, 20.04 include the nvidia drivers default now
[13:46] <howarth> I swore it was nvidia-driver-360 rather than nvidia-340 last I checked
[13:47] <howarth> I'll give that a spin on my test external drive that I have been using for testing the full installs
[13:47] <lotuspsychje> its worth a test right howarth 
[13:47] <lotuspsychje> older card, test the oldest driver
[13:47] <howarth> Still will be a rough ride if I want to use Wayland
[13:47] <howarth> The freeze is actually pretty random
[13:48] <lotuspsychje> howarth: nvidia + wayland is not perfect yet
[13:48] <howarth> I'll leave my main drive with nouveau/wayland to see if that suppresses it.
[13:48] <lotuspsychje> there are some improvements and workarounds out there, but think still being worked on
[13:49] <howarth> Anyway, it probably won't be long before the GTX680 is dropped out of the main nvidia releases
[13:50] <howarth> I am still trying to puzzle out the situation with clock scaling and nouveau
[13:51] <howarth> I thought there was supposed to be code added for that at some point
[13:53] <howarth> IMHO, other than the nvidia issue, a 2008 MacPro is pretty much the sweet spot for running linux on a Mac
[14:29] <ubuking> Hi
[14:33] <Ussat> meh, use a VM and be not concerned
[14:34] <Guest_46> When I power on my device, the internet connection (via WiFi) exists. After few minutes the internet access disappears (the WiFi remains connected, question mark appears on the WiFi icon). To fix this I have to switch off the WiFi and then reconnect. This happens every few minutes and then I have to repeat the fix.  (Focal Fossa 20.04 beta)
[14:35] <ubuking> E
[14:35] <ubuking> Help
[14:36] <ubuking> Hello
[14:39] <ubuking> Hiiiiiii
[14:39] <MikeRL> This may be the wrong place to ask, but I heard and experienced hellfire trying to get 19.10 on the Pi 4. I tried an unofficial image someone brewed up and it works. Source is from: https://jamesachambers.com/raspberry-pi-4-ubuntu-server-desktop-18-04-3-image-unofficial/
[14:40] <ubuking> Here is only 20.04 support!!!!!! 😳 
[14:40] <MikeRL> No issues. How difficult in short would it be for someone, if interested, to get 20.04 with the desktop on the Pi 4? 18.04 is better than no Ubuntu, as I dislike Raspbian in comparison, and the server variant works well, but the GUI is a mess on the offical images.
[14:41] <MikeRL> Yeah I know. Just mentioning that if 19.10 didn't play nice chances are 20.04 will be harder as well.
[14:41] <MikeRL> Not too much excessive changes from a release prior to an LTS to an LTS.
[14:43] <MikeRL> I donate per each Ubuntu release, but after realizing there's a shortage of manpower and time as the main bottlenecks, I don't throw as much money at the Pi releases.
[15:35] <howarth> I can confirm that the nvidia-340 drivers work fine under Ubuntu 20.04 on a 2008 MacPro with Mac rom'ed GTX680
[15:35] <howarth> Tested the 3D performance with the pymol demos and it looks okay
[15:36] <howarth> Oddly, going back to nouveau to compare, I noticed that shaders seem to now be blacklisted on nouveau under pymol
[15:36] <howarth>  Detected blacklisted graphics driver.  Disabling shaders.
[16:43] <FurretUber> Hi, I'm having a problem with the new APT. I'm reading the man page but now hit a problem
[16:44] <FurretUber> On 18.04, "apt list gc*7*" would show all packages that start with "gc" and have a "7" in the package name
[16:45] <FurretUber> As this no longer works on 20.04, I'm trying to use the patterns. However, "apt list '~ngc ~n7'" find anything that has "gc" and "7", regardless if it starts with "gc" or not. Even worse, it is finding pakages with the "7" before the "gc"
[16:46] <FurretUber> So, what is the 20.04 equivalent for "apt list gc*7*"?
[17:05] <ducasse> it's working here
[17:08] <FurretUber> With list it works, but it doesn't on install or purge
[17:12] <FurretUber> When I gave a real example with purge yesterday, the focus was given on why I would use that command instead...
[17:13] <FurretUber> ...and the reason is that I don't know how to make the default kernel be a non-generic kernel
[17:13] <FurretUber> But this specific question is about apt patterns on 20.04
[17:16] <ducasse> try escaping the *
[17:23] <FurretUber> It didn't work, the error message is exactly equal, however
[18:10] <jjoeshua> does Net Speed works on Focal Fossa ? I cant install it.. :/
[18:15] <jjoeshua> Err:4 http://ppa.launchpad.net/fixnix/netspeed/ubuntu focal Release  404  Not Found [IP: 91.189.95.83 80]
[18:16] <Eickmeyer> jjoeshua: You'd have to check with the ppa owner.
[18:17] <jjoeshua> anyone know some other way to install it?
[18:17] <Eickmeyer> If it's not in the repos, we don't support it.
[18:17] <jjoeshua> also I have anoter problem:
[18:17] <jjoeshua> when I try to update I get:
[18:17] <Eickmeyer> !paste
[18:17] <jjoeshua> jjoeshua@jjoeshua:~$ sudo apt get updateE: Invalid operation getjjoeshua@jjoeshua:~$ 
[18:18] <Eickmeyer> jjoeshua: Omit the "get" and you should be fine.
[18:19] <jjoeshua> thanks , learning.. I am new in this
[18:19] <Eickmeyer> jjoeshua: If you're brand new, installing a prerelease version of Ubuntu is not a good way to learn. :)
[18:19] <jjoeshua> E: The repository 'http://ppa.launchpad.net/fixnix/netspeed/ubuntu focal Release' does not have a Release file.N: Updating from such a repository can't be done securely, and is therefore disabled by default.N: See apt-secure(8) manpage for repository creation and user configuration details.
[18:19] <jjoeshua> from where to start? :)
[18:19] <Eickmeyer> Again, you need to contact the PPA owner. That's not a bug.
[18:20] <Eickmeyer> https://launchpad.net/~fixnix
[18:22] <jjoeshua> I learn basics command of terminal and how to use it.. what to learn next? I was thinking to start with Python
[18:22] <Eickmeyer> That's up to you. A good place to ask (since that's not a support question) is #ubuntu-offopic.
[19:59] <nonix4> Switched from upgraded-to-20.04-beta to fresh install... which made bunch of issues disappear. But which package is supposed to create "power" group? bus-daemon[1860]: Unknown group "power" in message bus configuration file
[20:00] <nonix4> referred to in /etc/dbus-1/system.d/org.freedesktop.thermald.conf
[20:15] <KjetilK> TJ-: Is there a change in the status of Secure Boot in 20.04 Beta with regards to your Full_Disk_Encryption_Howto_2019 walkthrough?
[20:20] <KjetilK> Oh, bummer, I'll keep it off for now 
[21:08] <nael_n> "The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is important to make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices."
[21:08] <nael_n> Does anybody get that while upgrading GRUB to 2.04-1ubuntu24 on 20.04, or is it just me? I haven't changed anything to my disks or my GRUB.
[21:15] <nonix4> nael_n: single ubuntu installation on all attached disks or multiple os?
[21:16] <nael_n> Single Ubuntu installation on a single internal NVMe in a laptop. I haven't touched /boot either. First partition is the EFI system partition.
[21:17] <nael_n> It's a pretty standard setup methinks
[21:18] <valorie> is that a new install?
[21:18] <valorie> I have experienced in the past (as have some others) randomly: grub being installed on the USB!
[21:19] <valorie> I didn't notice it until removing the usb and then having no grub
[21:19] <valorie> had to fix it with at chroot
[21:19] <valorie> afaik it has still not been fixed because it happens rarely and randomly
[21:22] <nael_n> No it's not a new install, it's a 20.04 system which I've been using/testing since late December. Updating it with apt from time to time.
[21:23] <nael_n> I am at a complete and utter loss
[21:42] <valorie> in both the devel and -release chan I've seen notice of some grub issues
[21:42] <valorie> it's being worked on
[22:10] <nael_n> Thx valorie. I'm going to click OK and hope for the best!
[22:11] <valorie> I'm not sure that's a good idea, but OK
[22:11] <valorie> you can always fix grub in a chroot from a live USB
[22:11] <valorie> that ain't fun, however
[22:16] <nael_n> I like to live dangerously
[22:17] <nael_n> A diff of the listings of /boot before and after the update shows no difference in file names or file sizes, so there's that at least
[22:22] <valorie> hopefully you have good backups, nael_n
[22:23] <valorie> and a handy ISO burned onto a USB
[22:24] <nael_n> I'm backing up as we speak! XD
[22:24] <valorie> good move!
[22:24] <valorie> I need to do that before upgrading
[22:25] <valorie> upgraded the travel laptop with no issues
[22:25] <valorie> but it has basically no data on it
[22:25] <valorie> and no nvidia
[23:07] <FurretUber> What is the proper way to avoid bug 1870265?
[23:08] <FurretUber> I was trying to stop the crashes, and noticed there are multiple approaches that fix this, but I don't know which one is thebest
[23:09] <FurretUber> One approach involves changing Xorg settings, making the system use the intel Xorg driver instead of modesetting
[23:09] <FurretUber> The other approach involves changing xfwm4 configuration, so it uses xpresent or off
[23:09] <FurretUber> Which one of the workarounds is best to avoid the crash?
[23:26] <nael_n> @valorie despite the grub malarkey, my computer rebooted swimmingly, thank goodness