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