[01:07] <pragmaticenigma> Just discovered yesterday... there are no 32bit ISO for the netinstaller mini.iso anymore... bummer :-(
[01:10] <tomreyn> even for 18.04?
[01:14] <tomreyn> pragmaticenigma: how about http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/installer-i386/current/images/netboot/
[01:49] <pragmaticenigma> tomreyn, after 18.04
[01:49] <tomreyn> oh ok, that's not surprising to me then.
[01:51] <pragmaticenigma> I was hoping they might continue to release 32bit through that means... but I guess they really want to cut all 32bit support where they can
[01:52] <pragmaticenigma> I get that 32bit machines are becoming far less common. I've already found another means to keeping my 32bit machines going a bit longer through the use of another Debian based distribution.
[01:52] <pragmaticenigma> 32bit Ubuntu was getting to be too much for my machines to handle anyways, even running something like Xubuntu or Lubuntu was struggling
[01:59] <tomreyn> puppylinux will probably "work" for a while longer. i wouldn't use it for processing any sensitive data but you should be able to burn some watts at least ;)
[02:01] <pragmaticenigma> these old machines mostly serve for entertainment purposes. I installed MX Linux on them. They're approach seems to reduce the overhead enough to get things running smoothly
[02:01] <pragmaticenigma> *Their
[02:01] <pragmaticenigma> I think as long as Debian devs keep it going, there will be 32 bit support in the Debian branch for a while
[02:01] <pragmaticenigma> how long before packages themselves get to be too big, that's a matter to worry about on another day
[02:04] <tomreyn> debian will probably support i386 a while longer, too, but i guess it'll become a port.
[02:05] <tomreyn> *unoffical* port, i mean
[02:06] <pragmaticenigma> hard to say... RPi's are still 32bit
[02:06] <tomreyn> yes, but arm, not intel
[02:08] <pragmaticenigma> right, but still means a need for 32 bit software. The compilers handle the archetecture differences (at least good compilers will)
[02:14] <tomreyn> the reason ubuntu is dropping support is that kernel development for i386 is being phased out. that's not the case for 32-bit ARM platforms as far as i know. if ubuntu had continued to support i386 till 20.04 it'd have to have done ESM for another 10 years, effectively mataining an otherwise dead kernel architecture.
[02:15] <tomreyn> debian has shorter lifecycles so it's an easier decision there, i guess.
[02:15] <pragmaticenigma> ah, that would make sense
[02:15] <pragmaticenigma> I don't follow kernel news, as I've found it too chaotic to follow
[02:25] <tomreyn> actually, i386 development is still happening on the kernel according to https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/refs/heads but at a slower pace, i think. some spectre patches took months after amd64 release to be developed there.
[02:40] <pragmaticenigma> makes sense that it isn't a high priority
[03:35] <lotuspsychje> good morning
[04:54] <lotuspsychje> jnewt: a few tips to solve bugs faster: actively help your own bug, keep it alive and find new users that are affected
[05:00] <pragmaticenigma> jnewt, what we are trying to convey to you is not about it being supported. If you have a specific issue with Unity, then please ask for support directly related to your issue. If you are experiencing that particular bug, the reason it is still open is because Canonical isn't developing Unity anymore. Therefor it will likely remain open until someone decides to clean up old tickets.
[07:37] <ducasse> good morning
[14:55] <lotuspsychje> we might keep our eyes open for screen issues on 5.3 hwe
[14:56] <lotuspsychje> few new bugs entered in #ubuntu-bugs-announce
[14:56] <oerheks> now a fan issue too
[15:00] <lotuspsychje> bug #1860230
[15:00] <lotuspsychje> bug #1860268
[15:01] <lotuspsychje> bug #1860253
[15:01] <lotuspsychje> thats it
[15:03] <jeremy31> nvidia dkms drivers likely haven't been patched for 5.3
[15:09] <lotuspsychje_> good point jeremy31
[15:09] <lotuspsychje_> the titlebar bug is also on unity, so that could be unity only related perhaps
[15:10] <jeremy31> There seem to be a lot of bugs against 5.3.0-26
[15:11] <lotuspsychje_> have a few on 20.04 kernel 5.4 also here jeremy31
[15:11] <lotuspsychje_> kerneloops, xorg bugs, dock issues,..
[15:12] <jeremy31> Been seeing wireless issues with out of tree modules
[15:12] <lotuspsychje_> bug #1860271
[15:14] <jeremy31> I looked at that one, most of those modules should work in 5.3
[15:37] <lotuspsychje> jeremy31: what do you think of my bug #1854146
[15:37] <lotuspsychje> just happened right now on 5.4 too
[15:41] <jeremy31> I can't access the oops files
[15:43] <lotuspsychje> jeremy31: http://dpaste.com/3094XBA
[15:44] <lotuspsychje> http://dpaste.com/213NV7K
[15:46] <jeremy31> Wonder if it could be caused by virtualbox?
[15:47] <lotuspsychje> interesting idea
[16:33] <oerheks> tomreyn, i discussed this bot thingy with sarnold ..
[16:33] <oerheks> i guess it is not oke, but he seems the only user.
[17:07] <tomreyn> thanks oerheks, i concur
[17:07] <lotuspsychje> moar corrupted ati bug #1860282
[17:10] <tomreyn> "Distro: Linux Mint 19.3 Tricia"
[17:10] <lotuspsychje> yeah saw its on cinnamon
[17:10] <lotuspsychje> the other corruption was on unity
[17:10] <tomreyn> but it can affect ubuntu, too, i guess
[17:10] <tomreyn> logs are missing, though
[17:11] <lotuspsychje> bug #1860268
[17:11] <tomreyn> "CurrentDesktop: Unity:Unity7:ubuntu"
[17:11] <lotuspsychje> yep
[17:12] <lotuspsychje> i wonder if they would have the same on gnome
[17:14] <tomreyn> worth a try for sure.
[17:15] <lotuspsychje> seen alot of ati corruptions on xenial with unity in the past, including my own ex ati x800
[17:15] <lotuspsychje> cant say ive seen it on gnome
[17:34] <tomreyn> is linux 5.3 in bionic-hwe known to break nvidia drivers?
[17:34] <lotuspsychje> ive seen a bug passby holdon tomreyn
[17:35] <lotuspsychje> another mint one though... bug #1860221
[17:36] <tomreyn> hmm thanks
[17:36] <lotuspsychje> and jeremy31 earlier suspected nvidia dkms drivers not patched yet?
[17:37] <ducasse> is any action taken on mint bugs at all?
[17:37] <jeremy31> ducasse: I have seen some of them addressed
[17:38] <lotuspsychje> ducasse: jeremy31 would prob know that
[17:38] <jeremy31> I know at one time they were flat out ignored
[17:40] <ducasse> that is what i'd expect to happen, tbh
[17:41] <lotuspsychje> i asked the kernel guys same question the other day
 lotuspsychje, if they are our actual kernel binaries we are interested in bug found; though we may not be able to tell if it is a 'different userspace' interaction in some cases to be sure
 apw: but if ubuntu's kernel suffers a bug, does that mean that mint also suffers that bug?
[17:41] <tomreyn> https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bugs?orderby=-id&start=0 lists no recent reports (but i'm not even sure that's the "usual" nvidia driver in bionic)
 lotuspsychje_, i could not say for sure; if they have the same kernel likley yes
[17:44] <lotuspsychje> tomreyn: 340 is for older cards
[17:46] <tomreyn> oh, what's current?
[17:46] <lotuspsychje> depends on the card and the ubuntu version
[17:46] <lotuspsychje> but more newer cards would pull 390 and higher
[17:48] <jeremy31> What is this linux-modules-nvidia-435-generic-hwe-18.04?
[17:48] <tomreyn> okay, so there is 340, 390, 430, 435
[17:49] <lotuspsychje> not sure jeremy31
[17:51] <lotuspsychje> 19.10 should include the nvidia drivers on the iso now
[17:52] <tomreyn> those linux-modules-nvidia-* packages have been existing for a while: https://packages.ubuntu.com/search?suite=bionic-updates&section=all&arch=any&keywords=linux-modules-nvidia-+-generic&searchon=names
[17:53] <tomreyn> actually not that long, only since december
[17:53] <tomreyn> ah those seem to be secure boot signed modules?
[17:54] <lotuspsychje> !info linux-modules-nvidia-435-generic-hwe-18.04
[17:54] <tomreyn> i wonder how canonical can safely sign them.
[17:56] <tomreyn> (or what this attestation actually means)
[18:01] <jeremy31> lotuspsychje: Can you check your driver manager?  Does the backports-iwlwifi-dkms show there?
[18:02] <lotuspsychje> jeremy31: hmm it does :p
[18:02] <jeremy31> lotuspsychje: thanks, then it isn't just Mints version doing that
[18:02] <lotuspsychje> but its greyed out for me
[18:03] <lotuspsychje> i can only select, continue with using the manual driver
[18:04] <jeremy31> There almost has to be some data file that goes along with the driver manager
[18:06] <lotuspsychje> driver=iwlwifi driverversion=5.4.0-9-generic firmware=46.6bf1df06.0
[18:06] <lotuspsychje> still im connected on wifi
[18:08] <lotuspsychje> tomreyn: what is usually do is compare ubuntu's versions with https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
[18:10] <tomreyn> those are the same nvidia branches / versions there.
[18:10] <lotuspsychje> !info nvidia-driver-435
[18:10] <tomreyn> but newer package verisons
[18:11] <tomreyn> https://packages.ubuntu.com/bionic-updates/nvidia-driver-435
[18:11] <lotuspsychje> Version 435.21-0ubuntu0.18.04.2
[18:11] <lotuspsychje> yeah
[18:11] <tomreyn> actually 440 is not in ubuntu proper
[18:12] <tomreyn> not in bionic anyways
[18:12] <tomreyn> nor 304, nor 515, nor 418
[18:12] <tomreyn> nor 304, nor 415, nor 418
[18:13] <lotuspsychje> not sure wich driver those big RTX pulls by default on ubuntu
[18:13] <lotuspsychje> would be interesting to see a 19.10 with RTX 2080
[18:15] <tomreyn> they all use amdgpu, just different firmwares
[18:17] <lotuspsychje> tomreyn: apt-cache shows nvidia-driver-440 - NVIDIA driver metapackage on 20.04 here
[18:18] <lotuspsychje> not on bionic?
[18:41] <lotuspsychje> digikin: geary is cool
[18:41] <digikin> X)
[18:41] <lotuspsychje> but 'best' is pretty relative of course
[18:46] <tomreyn> lotuspsychje: ah i missed you saying nvidia-driver-440 is only available on 20.04 here - too much channel hopping on my part
[18:46] <lotuspsychje> its sunday, no sweat :p