[13:05] <zzarr> Hello!
[13:06] <brunch875> Hello, zzarr!
[13:08] <zzarr> I was wondering, since Qualcomm have good support for Ubuntu/Linux, would a Snapdragon 835 based phone be a good platform to port Ubuntu Touch/Personal to?
[13:10] <brunch875> zzarr: Unfortunately, it's not just the processor what the phone depends on
[13:11] <zzarr> I know, the GPU and other things too
[13:11] <zzarr> I tried to port Ubuntu before I got my self a MX4
[13:12] <zzarr> myself*
[13:14] <zzarr> But I think that the Adreno is among the supported once
[13:14] <zzarr> I was looking at the Nokia 8 phone
[13:16] <brunch875> I can't give you advice on that, I have no idea :-p
[13:21] <zzarr> :)
[13:22] <zzarr> The Dragonboard 410c have a Snapdragon and a Adreno GPU
[13:22] <zzarr> I have one of those
[14:55] <dobey> zzarr: if it was using a more standard bootloader like dragonboard, and could use open source drivers for everything, sure. but as far as phones/tablets go, that is pretty much never the case
[15:11] <taiebot> Fair play to Jolla. they seem to be doing great at this MWC 2017. I wish Ubuntu will join them in offering alternative OS in phones
[15:12] <taiebot> https://twitter.com/JollaHQ
[15:12] <dobey> taiebot: https://twitter.com/fairphone
[15:13] <taiebot> dobey: community support vs partnership
[15:14] <taiebot> I wish all the best to the fairphone but it is not a phone i would buy at the moment.
[15:14] <dobey> ubuntu is a community project
[22:54] <zzarr> Okey, thanks dobey


[12:21] <zul> works fine Linux homer 2.6.22-8-xen #1 SMP Thu Jul 12 17:32:08 GMT 2007 i686 GNU/Linux
[01:45] <lamont> /home/lamont/kernel/hppa-ia64/scripts/gcc-version.sh: line 11: hppa-linux-gcc: command not found
[01:45] <lamont> sigh
[01:56] <lamont> Running splitconfig.pl ...
[01:56] <lamont> debian/scripts/misc/oldconfig: line 73: /home/lamont/linux-source-2.6.22-2.6.22/debian/scripts/misc/splitconfig.pl: Permission denied
[01:56] <lamont> updateconfigs target needs a chmod
[01:59] <lamont> hrm... I'll probably wind up committing something before bed tonight, but I'm nowhere close to finished
[08:52] <kraut> moin
[12:05] <\sh> bug #127125
[12:13] <\sh> fabbione: you don't have hands on a x4500 from sun with full storage?
[12:19] <fabbione> no
[12:19] <fabbione> i don't get x86* junk here
[12:19] <fabbione> sorry :)
[12:21] <\sh> fabbione: well, my interest is just the storage ;)
[01:35] <Nafallo> BenC: seems there are device-ids missing from the ralink drivers. want a bug about them?
[01:36] <Nafallo> grep 3c03 * in ubuntu/wireless/rt2x00 should show binary match, right?
[01:44] <Nafallo> BenC: never mind me. I checked git, and it's there.
[02:30] <BenC> Nafallo: you can't grep for hex strings in a binary
[02:30] <Nafallo> BenC: yea, I discovered that :-)
[02:31] <Nafallo> BenC: a user complained a ralink-based usbthingie didn't work in feisty, so I git-cloned and the ids is there. I told him to file a bug.
[02:32] <Nafallo> s/is/are/
[05:36] <jovans> is there a kernel bugfix release soon for feisty?
[05:38] <jovans> or can i use the current version kernel under gutsy?
[06:53] <bdmurray> BenC: is there enough info in bug 123669 for you guys to work on it?
[06:58] <BenC> bdmurray: could use full dmesg and lspci -vvn output
[06:58] <BenC> bdmurray: narrow down the driver for us, since cable detection is driver dependent
[06:59] <BenC> ...in some cases
[06:59] <BenC> the fact that he's using hdc instead of scd0 means IDE, and I'd like to find out if switching to libata-pata would help him
[07:00] <bdmurray> cool, I would have thought cable detection was generic
[07:00] <BenC> there's generic ATA code, and some drivers have specific cable detection


[14:10] -ubottu:#ubuntu-news- ::omg!ubuntu:: Ubuntu ‘Command Not Found’ Open to Exploit, Warn Experts @ https://www.omgubuntu.co.uk/2024/02/security-researchers-detail-ubuntu-security-flaw
[20:10] -ubottu:#ubuntu-news- ::planet:: Ubuntu Blog: Firecell and Canonical to demonstrate 5G private mobile network (PMN) solution running on Ubuntu at MWC Barcelona @ https://ubuntu.com//blog/firecell-and-canonical-to-demonstrate-5g-private-mobile-network-pmn-solution-running-on-ubuntu-at-mwc-barcelona
[20:10] -ubottu:#ubuntu-news- ::planet:: Ubuntu Blog: Auto-scaling of Intel FlexRAN components based on MicroK8s and Ubuntu real-time kernel support @ https://ubuntu.com//blog/auto-scaling-of-intel-flexran-components-based-on-microk8s-and-ubuntu-real-time-kernel-support


[08:14] <darkxst> infinity, would it be possible to move webkit2gtk source only into main for building?, we need for it gnome-online-accounts which is need by gnome-control-center. bug 1466290
[08:14] <infinity> darkxst: I had that bug open to look at.  Just hadn't gotten there yet.
[08:18] <darkxst> ok, anyway the binaries that dep on webkit2gtk can all be demoted to universe (not used by Ubuntu even though they are in main)
[08:20] <infinity> darkxst: I haven't looked at the situation well enough to answer that yet. :P
[09:48] <bdrung_work> hi, http://releases.ubuntu.com/15.04/ shows ubuntu-15.04-snappy-amd64+generic.img.xz and ubuntu-15.04-snappy-amd64-generic.img.xz. What's the difference beside the one character (+ vs -) in its name?
[10:08] <infinity> bdrung_work: One is a symlink to the other because a blog post mentioned the incorrect (-) naming scheme. :P
[10:08] <bdrung_work> ah, okay
[10:09] <infinity> Or some install instructions or something.  I forget the history, but should probably revisit the next time someone asks me to publish a snappy thing to cdimage and make sure it's not a problem anymore.
[10:13] <bdrung_work> infinity, having two files opens the question, which is the correct (and future proof) name
[10:16] <infinity> bdrung_work: arch+subarch is the canonical way to name subarches (as seen with, say, amd64+mac)
[11:00] <darkxst> infinity, I checked gnome-control-center and gnome-online-accounts, admittedly though I didnt check if there are other syncs from debian that might start building with webkit2gtk
[12:09] <rbasak> ScottK: thank you for releasing the grub2 SRU. Though grub2-signed hasn't been released concurrently. Won't this cause a problem for those who are doing the UEFI signed verification thing?
[12:10] <rbasak> cjwatson: ^^ help. infinity is asleep, slangasek presumably not up yet, and I don't know who else I can ask. Will this cause a regression?
[12:13] <cjwatson> That will cause a regression, yes.
[12:14] <rbasak> Well, it's live now, so we should do something.
[12:14] <cjwatson> Let me go and release it quickly now - it isn't quite aged, but the main change was in grub2 anyway.
[12:14] <rbasak> OK - thanks!
[12:16] <cjwatson> And as you say most of it was already live.
[12:16] <cjwatson> Done.
[12:16] <rbasak> Thank you!
[12:17] <cjwatson> Oh, yikes, I accidentally released it for utopic too and it wasn't explicitly verified for that so grub2 hadn't yet been released.
[12:18] <cjwatson> I think the path of least resistance is to release it there too.
[12:18] <cjwatson> Odds of problems are pretty low.
[12:18] <rbasak> :(
[12:18] <rbasak> OK
[12:18] <rbasak> I'll see if matsubara can verify utopic.
[12:18] <cjwatson> All done now.
[13:22] <arges> infinity: rbasak: hi. looking at bug 1454719, looks like most packages are in except docker.io... do i need to wait on somebody before putting that into -proposed?
[13:23] <arges> rbasak: and whats up with golang-pty-dev for utopic? did that ever get uploaded?
[13:30] <rbasak> arges: working on infinity on it. I have a list of fixes that are needed for the remaining items.
[13:30] <rbasak> err, _with_ infinity
[13:31] <arges> rbasak: got it. i'll leave it then
[16:38] <jamespage> please could the python-os-brick binary NEW packages be acked into wily
[16:42] <jamespage> ta
[19:16] <infinity> rbasak: Any progress on docker while I slumbered?
[19:56] <rbasak> infinity: sorry, kickinz1 was out today, so I focused on other stuff instead. I'll get back to Docker tomorrow with kickinz1.
[20:06] <infinity> rbasak: Mmkay.
[20:58] <tjaalton> infinity: do you know if the daily trusty image should boot fine? mine drops in initramfs
[20:58] <tjaalton> could me my fault of course
[21:27] <infinity> tjaalton: I think that might be because we need the casper in the queue. :P
[21:27] <infinity> tjaalton: Let me review that and get it in.
[21:28] <infinity> tjaalton: I find it a bit disconcerting that no one's complained until now, since it's probably been broken for weeks. :/
[21:33] <infinity> tjaalton: Next daily (at 6:31am UTC) should have the fix.
[21:33] <infinity> tjaalton: If you're around and want a test ISO faster, I can spin a one-off.
[21:33] <tjaalton> infinity: nah it's fine, I can try the next daily
[21:34] <tjaalton> should I ack the packages from proposed if it's good?
[21:34] <tjaalton> the xorg stack that is
[21:34] <tjaalton> realized that there's no tracker bug for everything..
[21:34] <infinity> tjaalton: Let me know if the daily fixes your boot issue, that should help validate the casper bug.
[21:34] <tjaalton> ok
[21:34] <infinity> tjaalton: And yes, if you decide all the X stuff is good, lemme know.
[21:34] <tjaalton> right
[21:35] <infinity> tjaalton: Other than booting on two laptop with nearly identical Intel configs, I can't really test the X HWE reasonably. :/
[21:35] <infinity> tjaalton: I hope you have access to a few more video cards than I do.
[21:35] <tjaalton> well it's just the mechanics that need testing
[21:36] <tjaalton> and it's solid last I tried
[21:36] <infinity> tjaalton: Oh, there's also new nvidia drivers in the trusty queue.  I'm guessing I need those for the point release?  Or are the current ones in -updates 3.19 compatible?
[21:36] <infinity> (binary drivers, that is)
[21:36] <tjaalton> hmm yes you want those too, tseliot pinged about those earlier I think
[21:36] <infinity> tjaalton: Right, I'll get those reviewed.
[21:37] <infinity> tjaalton: And you also uploaded a new intel-lts-vivid for me, I see.  I'll look at that too.
[21:37] <tjaalton> yeah noticed they weren't in sync
[21:38] <infinity> Oh, was that the awful xv video corruption bug?
[21:38] <tjaalton> need to set up the scripts that mlankhorst had, if I could login to people.c.c (or whatever it is), vpn doesn't work for me
[21:38] <infinity> Definitely want to fix that.  It's vile.
[21:38] <tjaalton> scripts that generate these webpages with package versions and stuff
[21:38] <tjaalton> yep that one
[21:38] <infinity> tjaalton: VPN doesn't work for you?
[21:39] <tjaalton> naw
[21:39] <infinity> tjaalton: Sounds like something you should bring up in #is. :P
[21:39] <tjaalton> I have no dns if I start it
[21:39] <tjaalton> yeah tried that too
[21:39] <infinity> tjaalton: Do you have dnsmasq installed?
[21:39] <tjaalton> maybe if I don't use _this_ machine
[21:39] <infinity> tjaalton: If so, don't.
[21:40] <tjaalton> dnsmasq-base it seems
[21:40] <infinity> -base is fine (and needed)
[21:40] <infinity> Anyhow, lemme look at driver SRUs.
[21:40] <tjaalton> right, thx
[21:43] <infinity> tjaalton: Intel accepted.  nvidia will take a bit more gin before I'm prepared to face it.
[21:43] <tjaalton> nvidias are straight backports from vivid iirc
[21:43] <infinity> Pretty sure he did a bit of mangling to make them trusty-compatible.
[21:43] <infinity> At least, the changelog implies such.
[21:44] <tjaalton> ok
[21:44] <tjaalton> the one I was able to ack was clean
[21:44] <infinity> So, I need to diff and understand said mangling, and check for sanity.


[01:56] <AccelShark> Where do I go for Xubuntu 20.10 kernel problems, I have encountered a problem that doesn't show in Arch Linux but it is present in Xubuntu even on the 20.10 debug build. The ASRock TRX40 Creator still doesn't have a working front headphone jack on Xubuntu 20.10 beta but the Arch Linux 5.8+ kernels have working audio.
[01:56] <AccelShark> And yes, it is present on 20.04
[01:56] <AccelShark> well, the jack doesn't work on 20.04 that is
[02:04] <AccelShark> Whooooooops it's a PulseAudio bug
[02:05] <AccelShark> I'll bbiab, downgrade the ISO to 20.04, and try getting the PulseAudio TRX40 patches in.
[09:46] <seb128> hey there
[09:46] <seb128> whoever is maintaining https://xubuntu.org/release/20-04/ , the torrent url needs to be updated for .1 , it's currently a notfound
[10:02] <gnrp> seb128: Maybe it is best to file a bug. Don't know if anybody responsible is here
[10:02] <gnrp> !bug
[10:07] <seb128> gnrp, unsure what component is right for the website though, https://github.com/Xubuntu/xubuntu-website ? but that seems the theme not the content
[10:07] <seb128> anyway I mentioned it in case it's useful to someone
[10:08] <seb128> bluesabre, ^ maybe?
[10:10] <Maik> seb128: https://launchpad.net/~xubuntu-website
[10:11] <Maik> not sure if it is helpful but you could give it a shot there
[10:11] <seb128> Maik, bug tracking seems closed there, no report button
[10:12] <Maik> seb128: then use Contact this team's admins
[10:12] <seb128> ack
[10:12] <Maik> at least they will be notified then :)
[10:14] <Maik> there's also #xubuntu-devel , maybe they hide in there
[19:58] <xu-irc70w> The microphone records system sounds, what can you do about it?
[20:00] <diogenes_> xu-irc70w, system sounds?
[20:08] <xu-irc70w> Browser
[20:12] <diogenes_> xu-irc70w, more precisely?


[00:37] <jbicha> RAOF: please push your pristine-tar branch for colord
[01:20] <jbicha> upstream branch too
[01:29] <RAOF> jbicha: They're already pushed?
[01:30] <RAOF> As far as I can tell.
[01:36] <jbicha> RAOF: no, there's only the master branch https://salsa.debian.org/debian/colord/branches
[01:36] <RAOF> Huh. That 404s for me!
[01:37] <RAOF> jbicha: Would you kindly pull the pristine-tar and upstream branches from https://salsa.debian.org/raof-guest/colord ?
[01:39] <jbicha> RAOF: I gave you access instead
[01:40] <RAOF> I will accept that as a workable solution :)
[01:40] <jbicha> I've never seen that meson build stamp stuff before but I guess it makes sense
[01:41] <RAOF> jbicha: It's a huge faff.
[01:41] <RAOF> Because meson won't let you generate the build system twice.
[01:42] <jbicha> maybe you could ask debhelper to allow maintainers a more elegant way of overriding configure flags for arch-indep
[01:43] <jbicha> there's a nodoc build profile that probably works for most cases like that, but these aren't docs
[01:52] <jbicha> the repo is private, that's very strange
[01:55] <RAOF> I didn't set it up; blame Seb :)
[07:18] <didrocks> good morning
[07:55] <willcooke> morning all
[07:55] <willcooke> suddenly Wednesday
[08:00] <jibel> morning willcooke
[08:01] <Laney> suppington
[08:01] <jibel> willcooke, could you try latest Cosmic in vbox again and check if you reproduce the problem from last week? It works for me but I'm on cosmic and it's a newer version of virtualbox
[08:01] <willcooke> jibel, sure thing
[08:02] <willcooke> jibel, this image?  2018-09-25 16:45	1.9G
[08:02] <willcooke> current or pending
[08:02] <willcooke> oh, they are the same
[08:03] <willcooke> We should probably think about removing this text now:
[08:03] <willcooke> "Warning: This image is oversized (which is a bug) and will not fit onto a standard 703MiB CD. However, you may still test it using a DVD, a USB drive, or a virtual machine."
[08:03] <willcooke> since it's a bug which is never ever going to get fixed
[08:04] <willcooke> Any ideas who owns that page?
[08:04] <jibel> willcooke, yes this image
[08:04] <jibel> cdimage AFAIR
[08:04] <jibel> there might be a bug existing already
[08:05] <jibel> cannot find the exact package name, I'll search
[08:05] <willcooke> jibel, don't worry about it now
[08:05] <willcooke> not important
[08:05] <willcooke> I'll speak to inifinity at the release sprint
[08:10] <Laney> it's lp:ubuntu-cdimage
[08:10] <Laney> size_limit() function
[08:11] <willcooke> hi Laney
[08:11] <Laney> guten tag
[08:11] <willcooke> ca va?
[08:12] <willcooke> jibel, black screen here
[08:13] <Laney> muy bien
[08:13] <Laney> А вы?
[08:13] <willcooke> estic cansat
[08:14] <Laney> 😫
[08:17] <jibel> willcooke, which version of bionic?
[08:17] <jibel> s/bionic/vbox/
[08:18] <willcooke> jibel,
[08:18] <willcooke> virtualbox:
[08:18] <willcooke>   Installed: 5.2.10-dfsg-6ubuntu18.04.1
[08:18] <willcooke>   Candidate: 5.2.10-dfsg-6ubuntu18.04.1
[08:18] <willcooke>   Version table:
[08:18] <willcooke>  *** 5.2.10-dfsg-6ubuntu18.04.1 500
[08:18] <willcooke>         500 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages
[08:18] <willcooke>         100 /var/lib/dpkg/status
[08:18] <willcooke>      5.2.10-dfsg-6 500
[08:18] <willcooke>         500 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages
[08:19] <willcooke> jibel, I removed quiet and splash from the kernel options and I got a live session log in screen
[08:19]  * willcooke looks at Plymouth
[08:20] <jibel> willcooke, it'sthe same problem I had last week, on my laptop, the shell fails to start
[08:23] <jibel> ah, it doesn't boot after installation, same problem than yesterday
[08:24] <Laney> probably will get the new gdm later today
[08:25] <Laney> maybe you can try that to see if it changes anything
[08:25] <willcooke> my vm has locked up now
[08:25] <jibel> it seems to be when snaps are installing
[08:25] <willcooke> after reporting a problem with xorg
[08:25] <willcooke> jibel, I didnt even get that far
[08:25] <willcooke> I'll try agai
[08:26] <jibel> willcooke, can you try the version of vbox from cosmic. If it's installable on bionic of course
[08:27] <willcooke> the "Live Session User" should have no password, right?
[08:27] <willcooke> i.e. it's not "ubuntu"
[08:28] <willcooke> jibel I got in to a live session this time (removing quiet & splash  from the boot options) and I'm trying the install now
[08:28] <willcooke> I get "Would you like to report an error" about xorg, but it still seems to be running
[08:33] <willcooke> jibel, I'll nurse this through installation and then try a different version of vbox
[08:33] <willcooke> it feels a bit slugish right now
[08:33] <willcooke> like something's not right
[08:34] <jibel> willcooke, it's bug 1432137, xorg crashes, the shell cannot start and the session restarts
[08:41] <willcooke> jibel, yeah, it;s dead.  Ok, trying the Cosmic version of virtual box
[08:41] <willcooke> hm, I dont want to scre up this machine
[08:41] <willcooke> I will install B on my test machine and try it there
[08:42] <willcooke> but before I do that I have to finish a couple of other things, can it wait a few hours?
[08:43] <jibel> willcooke, np, i'll do it
[08:45] <willcooke> jibel, I can make a start, I'll let you know how far I get
[08:46] <jibel> is there a way to "unseed" snap so the system is in the same state than first boot?
[08:46] <willcooke> e.g. while it's installing I can write docs
[08:46] <willcooke> not sure
[08:47] <willcooke> as in, the snaps haven't been started or updated?
[08:47] <willcooke> You could rm -rf the ~/snap dir?
[08:52] <jibel> like the snaps have never been installed on the system
[08:52] <jibel> and installed on boot
[08:52] <willcooke> ah
[08:53] <jibel> I think that's what causes the black screen
[09:26] <willcooke> jibel, B installed on my test machine
[09:26] <willcooke> jibel, shall I just try and install the vbox debs from C?
[09:27] <jibel> willcooke, yes, if the kernel module is compatible with the kernel from B it should work fine
[09:31] <willcooke> jibel, lots of missing deps, mainly around qt, this will take me a while to unpick
[09:32] <willcooke> urgh, and libc
[11:26] <willcooke> Would one expect that software-properies-gtk does not show that nvidia proprietary drivers are available in the live session?
[11:26] <willcooke> i.e. I open it and it says there arent any drivers, but I think that there should be
[12:05] <Laney> jibel: might want to try the gdm in ppa:laney/ppa to see if it changes your bug at all
[12:21] <jibel> Laney, I've another failed boot. I'll try your ppa
[12:21] <jibel> I cannot even switch to a tty
[12:31] <cpaelzer> tkamppeter: would you have an advice what a good next step to debug http://paste.ubuntu.com/p/sDWCS83qKd/ might be?
[12:31] <cpaelzer> The TL;DR is - it sometimes works after boot, but if it doesn't then no printer on/off nor cable replug can resovle it
[12:32] <cpaelzer> the /dev/usb/lp1 entry that it would usually gain never appears and I'm lost where to check for more
[12:32] <cpaelzer> I wondered if I should try a HWE kernel, but wanted to hear your opinion first
[12:51] <jibel> would anyone know a way to disable snaps initialization on first boot?
[12:57] <willcooke> jibel, like stopping snapd from starting?  Can we just disable the systemd unit?
[12:59] <jibel> willcooke, another machine running cosmic, same version of vbox and cosmic doesn't start
[13:00] <tkamppeter> cpaelzer, do  not worry about the usblp kernel module. It is not used any more for years. The USB CUPS backend does raw USB access via libusb. Otherwise have a look at the "USB printer" section on https://wiki.ubuntu.com/DebuggingPrintingProblems.
[13:01] <willcooke> jibel, I dont follow, are you saying its racey?
[13:01] <tkamppeter> Anyone can help me on a gnome-control-center/network setup issue?
[13:03] <tkamppeter> I have a problem with gnome-control-center. In the VPN config window the green "Apply" button is always grayed out and I cannot change my settings.
[13:05] <willcooke> tkamppeter, which sort of VPN?
[13:06] <willcooke> PPTP or OpenVPNB
[13:06] <willcooke> *OpenVPN
[13:13] <tkamppeter> willcooke, our Canonical VPN.
[13:15] <tkamppeter> willcooke, I do not know whether it is PPTP or OpenVPN.
[13:16] <tkamppeter> willcooke, I also selected the config where the VPN is only used for the internal hosts for which the VPN is actually needed.
[13:18] <tkamppeter> willcooke, another hint: On Monday it happened to me that my home directory ran full. I immediately cleaned up to have space again, but I do not know whether it can have broken something in my g-c-c config, perhaps something which allowed me as normal user having root access to certain config settings.
[13:51] <tkamppeter> Anyone has an idea here?
[13:53] <willcooke> tkamppeter, Our VPN is OpenVPN
[13:54] <tkamppeter> willcooke, any hint? Whon could help me with this?
[13:54] <willcooke> tkamppeter, can you send me a screenshot of the config you've got set up so far
[13:54] <willcooke> I got it working, so it must be possible
[13:55] <tkamppeter> willcooke, I got it working in the first place and then it suddenly stopped.
[13:55] <tkamppeter> Probably I will simply remove everything related to it and follow the instructions again, as I had nver done it.
[13:57] <tkamppeter> I hoped that I am here with the guys who maintain g-c-c and have a quick hint for me.
[14:06] <jibel> Laney, when booting an iso do you know if it's possible to break after the squashfs is mounted but before ubiquity-dm starts?
[14:09] <Laney> jibel: I usually use systemd.unit=rescue.target
[14:09] <Laney> and then systemctl start network-online.target to get network
[14:09] <Laney> is that enough?
[14:11] <jibel> Laney, yes it should.
[14:12] <tjaalton> jibel: you've filed the same bug twice now :) please install the new mesa, it should fix it
[14:13] <tjaalton> jibel: oh, unduped it.. that's better
[14:13] <jibel> tjaalton, actually I am not sure they are duplicates because the boot failure happens without the xorg crash and on errors.u.c there are no crahs for cosmic
[14:15] <tjaalton> that crash is just a symptom of a failure somewhere else, like in this case the gallium swrast driver
[14:20] <tjaalton> I wonder if it's a theme bug that I can't select text on a split terminator window from the start of the line, it always grabs the vertical border instead
[14:21] <tjaalton> in cosmic, bionic was fine but it has issues with some elements being transparent..
[14:23] <tkamppeter> willcooke, I have tried to enter all again and it seems that something has changed in the g-c-c. Now it seems to be required to have a CA private key or a CA key password. This is not contained in the provided credentials.
[14:24] <tkamppeter> willcooke, therefore the "Apply" button is grayed out.
[14:24] <willcooke> tkamppeter, I have a private key in my VPN set up, so I think it does exist, but likely the instructions haven't been updated recently
[14:25] <willcooke> fwiw, my private key is called "canonical-will.key" inside .vpn
[14:25] <willcooke> inside ~/.vpn/
[14:26] <tkamppeter> willcooke, this is the "User Private Key". What it also wants to have is a "CA Private Key".
[14:29] <willcooke> hm, not sure
[14:29] <willcooke> I'll set it up from scratch on another machine
[14:45] <Laney> tkamppeter: it's probably https://gitlab.gnome.org/GNOME/network-manager-applet/issues/20
[14:45] <gitbot> GNOME issue 20 in network-manager-applet "Cannot import VPN configuration from standard ovpn files" [Closed]
[14:45] <Laney> maybe you could try the linked merge request (!27) and see if that fixes you
[14:48] <jibel> tjaalton, it boots with mesa from canonical-x ppa
[14:49] <willcooke> thanks Laney
[14:49] <Laney> de nada
[14:50] <tjaalton> jibel: great. it's uploaded to the queue already, should hopefully enter cosmic after the beta is out
[14:51] <willcooke> That means beta gets released broken though, right?
[14:52] <tjaalton> I'm not opposed if someone pings the release team about it.. I've tried
[14:52] <tjaalton> +else
[14:53] <tjaalton> uploaded it to the queue last night
[14:53] <willcooke> tjaalton, ack
[14:59] <tjaalton> pinged again
[15:25] <tkamppeter> Laney, thank you very much. I will try it soon. Is it already planned to go into Cosmic?
[15:28] <Laney> Don't know, but it would be a good idea
[17:00] <Trevinho> Laney: can you please publish https://bileto.ubuntu.com/#/ticket/3440 ?
[17:01] <Trevinho> Laney: no sorry, don't.
[17:02] <Trevinho> looks like I've to remerge the src in the pkg first -_-
[17:08] <jibel> sil2100, toreporduce bug 1794280 did you keep the default options in the installer?
[17:08] <jibel> to reproduce*
[17:19] <sil2100> jibel: basically only things I did was disable downloading updates during install and selected minimal
[17:19] <sil2100> jibel: rest was default basically
[17:21] <jibel> Laney, no improvement with your ppa
[17:22] <jibel> Laney, the difference is that gdm tries continuously to restart the session
[18:29] <Trevinho> Laney: https://bileto.ubuntu.com/#/ticket/3440 now is fine
[20:45] <tkamppeter> Laney, I have tried the patch for libnma and now I can set up Canonical's VPNs again, the "CA Private Key" field simply went away after applying the patch. Thank you very much.
[20:46] <tkamppeter> Laney, so please let this patch go into Cosmic.
[20:50] <tkamppeter> Laney, only the DNS problem is not solved. I cannot connect to rugby.internal.