[00:27] <da-viper> hello
[02:10] <adoring-fan> howdy
[02:12] <adoring-fan> uh, does anyone know what kde neon's keyserver is, or do i need to manually hunt it down and import it?
[02:12] <adoring-fan> trying to update from a usb
[02:30] <genii> Since the Kubuntu team now uses latest packages on their own official PPA, Neon is obsoleted. It was supposed to be a rolling release of Kubuntu, which if you add the official Kubuntu PPAs is now the same thing.
[02:31] <genii> The various ones are listed here https://launchpad.net/~kubuntu-ppa
[02:34] <adoring-fan> crap really? I thought they just updated neon.
[02:34] <adoring-fan> Guess I'm updating to kubuntu then. No biggie. thank you!
[02:35] <genii> Recommended PPAs are updates and backports
[02:46] <adoring-fan> so, you guys doing anything cool / kubuntu related?
[02:50] <adoring-fan> aight peace
[03:25] <valorie> genii: I disagree that neon isn't needed
[03:25] <valorie> they build even stuff from git
[03:25] <valorie> we'll never do that
[03:26] <valorie> if it was useless, Rik wouldn't package for neon too
[03:26] <valorie> btw neon's keys are on the download page
[03:27] <genii> valorie: OK, I'll remember for next time
[03:28] <valorie> not all KDE devels use it, but a lot do
[03:28] <valorie> of course some use Kubuntu, arch, fedora, suse, etc.
[03:29] <valorie> we all help one another out
[06:24] <howyoubeen> hey all, you know how xampp is more  or less a contained LAMP set up with a gui? Is there a gui for qt or kde if i wanted to set all that up on my laptop with my own MAMP setup?
[06:25] <howyoubeen> I don't mind turning things on and off in the terminal, just curious if there are alternatives
[06:26] <howyoubeen> Basicly its Visual Studio Code running with a tasksel LAMP setup
[08:08] <viewer|82> kubuntu is the best
[08:10] <eeos> is anyone using shairport-sync?
[08:31] <eeos> anyone who knows ow to use airplay devices from linux (stream from linux to a sonos or marantza receiver for example)
[08:39] <eeos> nyone who knows ow to use airplay devices from ubuntu (stream from linux to a sonos or marantz receiver for example)
 eeos: that's possible. Open the pulseaudio preferences and check a box there
[13:44] <BluesKaj> Hi folks
[14:37] <Dakeiz> Hello everyone. I'm having trouble connecting to my WiFi (phone access point). It says "Configuring interface" for a long time, then pops a notification "The WiFi network could not be found". I have not installed the proprietary drivers when installing Kubuntu, so I am thinking this could be it. Is there someone kind enough to help me?
[14:40] <Dakeiz> I just tried with my home WiFi (router), and I get the same error. "Wireless Interface (wlp3s0f0): The Wifi network could not be found". :(
[16:12] <user|27375> Hi
[16:12] <user|27375> What is system requiremnts for kubuntu ?
[16:12] <BluesKaj> !requirements
[16:13] <BluesKaj> !Kubuntu | user|27375
[16:13] <user|27375> thanks. is it the same as ubuntu ?
[16:14] <BluesKaj> user|27375, not quite check out https://kubuntu.org
[16:18] <user|27375> I couldnt find any information over there
[16:20] <BluesKaj> user|27375, just post your hardware specs here and we can give an informed guess :-)
[16:20] <oerheks> multi core CPU/4 gb/good videocard/ssd is preferable
[16:23] <user|27375> i5 8th gen, 8gb, m2ssd 256, intel graphics
[16:24] <masonbee-M> Using it on something like that right now user|27375
[16:24] <BluesKaj> user|27375, you'll be fine with Kubuntu
[16:25] <BluesKaj> same as my laptop and it runs great on Kubuntu
[16:27] <oerheks> maybe that m2 is *too fast*  :-P
[16:28] <BluesKaj> oerheks, I also have a m2 ssd, runs just fine
[16:29] <user|27375> ok thanks
[16:30] <eeos> hi! I would like to monitor the average battery consuption by process on my *ubuntu laptop 18.04 LTS .... how do I do that? I think there is something that does not work well with lat update, and battery consumption is through the roof..
[17:29] <joaco1> hi anyone knows how to fix this emojis??
[17:29] <joaco1> https://i.imgur.com/PxATUCh.png
[17:29] <joaco1> I have noto emoji installed
[17:29] <joaco1> this kubuntu 20.04
[20:05] <user|64794> were can i find kubuntu 12.04 for old powermac g5 or ppc
[20:06] <user|64794> im trying to download it but it dont work
[20:07] <oerheks> maybe the old versions page.. but then there are no updates
[20:07] <oadam> good night
[20:07] <oerheks> and you are vulnerable; such machines should not be connected to the internet
[20:08] <oadam> i get grub setup error. is there anyone who can help me
[20:08] <oerheks> 16.04 is still valid. http://cdimage.ubuntu.com/ubuntu-mate/releases/16.04/release/
[20:08] <user|64794> can 16.04 work on old ppc
[20:09] <oerheks> maybe, try it out? there is a live session in it too
[20:11] <user|64794> ok thanks
[20:13] <user|64794> i want to use my powermac g5 for movie streaming is it posible
[20:13] <valorie> try it and see?
[20:14] <user|64794> also trying to get a good computer the already bring linux which one are out there
[20:15] <user|64794> how is everything with the coronavirus
[20:15] <user|64794> keep safe
[20:16] <oerheks> a G5 might work as videoserver, itself would be horrible to show movies with a  NVIDIA GeForce FX 5200
[20:36] <philipsnot> everyone known sarver PT-BR?
[20:37] <philipsnot> ?
[20:42] <oerheks> !pt
[20:42] <oerheks> !br
[20:43] <oerheks> oh, same factoid
[20:48] <philipsnot> tks


[07:51] <openstackgerrit> melissaml proposed openstack/cloud-init: Put py34 first in the env order of tox  https://review.openstack.org/266753
[15:32] <george_> hi all, is there a recommended way of adding additional config modules
[15:32] <george_> other than copying them into /usr/lib/python2.7/site-packages/cloudinit/config or the equivalent?
[19:01] <george_> bump from earlier in case it was misssed: is there a recommended way of adding additional config modules?
[19:01] <george_> other than copying them into /usr/lib/python2.7/site-packages/cloudinit/config or the equivalent?
[19:44] <harlowja> george_ currently that will be the way u'll have to do it
[19:44] <harlowja> https://github.com/openstack/cloud-init/blob/0.7.x/cloudinit/stages.py#L648 only looks in the cloudinit.config module
[19:45] <george_> yeah, that's the only thing i saw
[19:46] <george_> thanks!
[19:47] <harlowja> np
[19:52] <harlowja> smoser yo, https://github.com/harlowja/cloud-init/tree/0.7.x-final-final-final-really is the most up to date bzr 0.7.x sync
[19:52] <harlowja> if u want i can ask the infra folks to sync ^ and replace https://github.com/stackforge/cloud-init/tree/0.7.x with that
[19:52] <harlowja> sorry i mean https://github.com/openstack/cloud-init/tree/0.7.x
[19:52] <smoser> ii was afraid you'd bug me again :)
[19:53] <harlowja> ;)
[19:53] <harlowja> i am in your basement
[19:53] <harlowja> lol
[19:53] <harlowja> u can not escape
[19:53] <smoser> AH!
[19:53] <harlowja> :-P
[19:53] <harlowja> soooo how about that, lol
[19:57] <harlowja> sooo
[19:57] <harlowja> lol
[23:51] <kasey-al`> Hi all, I am trying to debug an issue on a VM (C6.5 image) where the cloud-init script is running and the routes are not properly added.  This is on a cluster running Openstack Icehouse, C6.5 hypervisors, and OpenContrail SDN.  The image boots just fine on 60+ different hypervisors, but fails on a couple.
[23:52] <kasey-al`> tcpdump shows repetitive dhcp discover, offer, request, ack cycles, but the console-log of the VM just ends with the route table.
[23:52] <kasey-al`> and it never gets to the login prompt.
[23:52] <kasey-al`> Is there a way to get more verbose output out of cloud-init?


[00:29] <rbalint> Laney, vorlon I'm seeing LP: #1907803 again on http://autopkgtest.ubuntu.com/running could the change proposed on Salsa please be picked ahead of Debian's autopkgtest upstream?
[01:35] -queuebot:#ubuntu-release- New binary: gprbuild [s390x] (hirsute-proposed/universe) [2<IP_ADDRESS>8b109-3] (no packageset)
[01:35] -queuebot:#ubuntu-release- New binary: gprbuild [ppc64el] (hirsute-proposed/universe) [2<IP_ADDRESS>8b109-3] (no packageset)
[01:38] -queuebot:#ubuntu-release- New binary: gprbuild [amd64] (hirsute-proposed/universe) [2<IP_ADDRESS>8b109-3] (no packageset)
[01:48] -queuebot:#ubuntu-release- New binary: gprbuild [armhf] (hirsute-proposed/universe) [2<IP_ADDRESS>8b109-3] (no packageset)
[01:49] -queuebot:#ubuntu-release- New binary: gprbuild [arm64] (hirsute-proposed/universe) [2<IP_ADDRESS>8b109-3] (no packageset)
[02:46] -queuebot:#ubuntu-release- New binary: gprbuild [riscv64] (hirsute-proposed/universe) [2<IP_ADDRESS>8b109-3] (no packageset)
[03:08] -queuebot:#ubuntu-release- New: accepted gprbuild [arm64] (hirsute-proposed) [2<IP_ADDRESS>8b109-3]
[03:08] -queuebot:#ubuntu-release- New: accepted gprbuild [riscv64] (hirsute-proposed) [2<IP_ADDRESS>8b109-3]
[03:08] -queuebot:#ubuntu-release- New: accepted gprbuild [armhf] (hirsute-proposed) [2<IP_ADDRESS>8b109-3]
[03:08] -queuebot:#ubuntu-release- New: accepted gprbuild [amd64] (hirsute-proposed) [2<IP_ADDRESS>8b109-3]
[03:08] -queuebot:#ubuntu-release- New: accepted gprbuild [s390x] (hirsute-proposed) [2<IP_ADDRESS>8b109-3]
[03:08] -queuebot:#ubuntu-release- New: accepted gprbuild [ppc64el] (hirsute-proposed) [2<IP_ADDRESS>8b109-3]
[05:15] -queuebot:#ubuntu-release- New binary: adacgi [amd64] (hirsute-proposed/universe) [1.6-26] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: adacgi [arm64] (hirsute-proposed/universe) [1.6-26] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: adacgi [s390x] (hirsute-proposed/universe) [1.6-26] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: powa-archivist [ppc64el] (hirsute-proposed/universe) [4.1.0-1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: adacgi [armhf] (hirsute-proposed/universe) [1.6-26] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: powa-archivist [s390x] (hirsute-proposed/universe) [4.1.0-1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: git-lfs [amd64] (hirsute-proposed/universe) [2.12.1-2] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: adacgi [ppc64el] (hirsute-proposed/universe) [1.6-26] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: proftpd-dfsg [s390x] (hirsute-proposed/universe) [1.3.7a+dfsg-1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: proftpd-dfsg [amd64] (hirsute-proposed/universe) [1.3.7a+dfsg-1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: unrar-nonfree [amd64] (hirsute-proposed/multiverse) [1:6.0.3-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: proftpd-dfsg [ppc64el] (hirsute-proposed/universe) [1.3.7a+dfsg-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: powa-archivist [arm64] (hirsute-proposed/universe) [4.1.0-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: powa-archivist [armhf] (hirsute-proposed/universe) [4.1.0-1] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: adacgi [riscv64] (hirsute-proposed/universe) [1.6-26] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: powa-archivist [riscv64] (hirsute-proposed/universe) [4.1.0-1] (no packageset)
[05:30] -queuebot:#ubuntu-release- New binary: proftpd-dfsg [arm64] (hirsute-proposed/universe) [1.3.7a+dfsg-1] (no packageset)
[05:33] -queuebot:#ubuntu-release- New binary: proftpd-dfsg [armhf] (hirsute-proposed/universe) [1.3.7a+dfsg-1] (no packageset)
[05:33] -queuebot:#ubuntu-release- New binary: openstructure [amd64] (hirsute-proposed/universe) [2.2.0-2] (no packageset)
[05:35] -queuebot:#ubuntu-release- New binary: powa-archivist [amd64] (hirsute-proposed/universe) [4.1.0-1] (no packageset)
[06:31] -queuebot:#ubuntu-release- New binary: proftpd-dfsg [riscv64] (hirsute-proposed/universe) [1.3.7a+dfsg-1] (no packageset)
[07:47] -queuebot:#ubuntu-release- New: accepted adacgi [amd64] (hirsute-proposed) [1.6-26]
[07:47] -queuebot:#ubuntu-release- New: accepted adacgi [armhf] (hirsute-proposed) [1.6-26]
[07:47] -queuebot:#ubuntu-release- New: accepted adacgi [riscv64] (hirsute-proposed) [1.6-26]
[07:47] -queuebot:#ubuntu-release- New: accepted adacgi [arm64] (hirsute-proposed) [1.6-26]
[07:47] -queuebot:#ubuntu-release- New: accepted adacgi [s390x] (hirsute-proposed) [1.6-26]
[07:47] -queuebot:#ubuntu-release- New: accepted adacgi [ppc64el] (hirsute-proposed) [1.6-26]
[07:47] -queuebot:#ubuntu-release- New: accepted git-lfs [amd64] (hirsute-proposed) [2.12.1-2]
[07:47] -queuebot:#ubuntu-release- New: accepted unrar-nonfree [amd64] (hirsute-proposed) [1:6.0.3-1]
[07:47] -queuebot:#ubuntu-release- New: accepted openstructure [amd64] (hirsute-proposed) [2.2.0-2]
[07:48] -queuebot:#ubuntu-release- New: accepted powa-archivist [amd64] (hirsute-proposed) [4.1.0-1]
[07:48] -queuebot:#ubuntu-release- New: accepted powa-archivist [armhf] (hirsute-proposed) [4.1.0-1]
[07:48] -queuebot:#ubuntu-release- New: accepted powa-archivist [riscv64] (hirsute-proposed) [4.1.0-1]
[07:48] -queuebot:#ubuntu-release- New: accepted proftpd-dfsg [amd64] (hirsute-proposed) [1.3.7a+dfsg-1]
[07:48] -queuebot:#ubuntu-release- New: accepted proftpd-dfsg [armhf] (hirsute-proposed) [1.3.7a+dfsg-1]
[07:48] -queuebot:#ubuntu-release- New: accepted proftpd-dfsg [riscv64] (hirsute-proposed) [1.3.7a+dfsg-1]
[07:48] -queuebot:#ubuntu-release- New: accepted powa-archivist [arm64] (hirsute-proposed) [4.1.0-1]
[07:48] -queuebot:#ubuntu-release- New: accepted powa-archivist [s390x] (hirsute-proposed) [4.1.0-1]
[07:48] -queuebot:#ubuntu-release- New: accepted proftpd-dfsg [ppc64el] (hirsute-proposed) [1.3.7a+dfsg-1]
[07:48] -queuebot:#ubuntu-release- New: accepted powa-archivist [ppc64el] (hirsute-proposed) [4.1.0-1]
[07:48] -queuebot:#ubuntu-release- New: accepted proftpd-dfsg [s390x] (hirsute-proposed) [1.3.7a+dfsg-1]
[07:48] -queuebot:#ubuntu-release- New: accepted proftpd-dfsg [arm64] (hirsute-proposed) [1.3.7a+dfsg-1]
[10:14] -queuebot:#ubuntu-release- Packageset: Added intel-processor-trace to i386-whitelist in hirsute
[10:39] -queuebot:#ubuntu-release- New binary: ulfius [amd64] (hirsute-proposed/universe) [2.7.0-1] (no packageset)
[10:39] -queuebot:#ubuntu-release- New binary: ulfius [s390x] (hirsute-proposed/universe) [2.7.0-1] (no packageset)
[10:39] -queuebot:#ubuntu-release- New binary: ulfius [ppc64el] (hirsute-proposed/universe) [2.7.0-1] (no packageset)
[10:41] -queuebot:#ubuntu-release- New binary: ulfius [armhf] (hirsute-proposed/universe) [2.7.0-1] (no packageset)
[10:52] -queuebot:#ubuntu-release- New binary: ulfius [riscv64] (hirsute-proposed/universe) [2.7.0-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New: accepted ulfius [amd64] (hirsute-proposed) [2.7.0-1]
[11:12] -queuebot:#ubuntu-release- New: accepted ulfius [ppc64el] (hirsute-proposed) [2.7.0-1]
[11:12] -queuebot:#ubuntu-release- New: accepted ulfius [s390x] (hirsute-proposed) [2.7.0-1]
[11:12] -queuebot:#ubuntu-release- New binary: boost-defaults [ppc64el] (hirsute-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[11:12] -queuebot:#ubuntu-release- New: accepted ulfius [armhf] (hirsute-proposed) [2.7.0-1]
[11:12] -queuebot:#ubuntu-release- New binary: boost-defaults [amd64] (hirsute-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[11:12] -queuebot:#ubuntu-release- New: accepted ulfius [riscv64] (hirsute-proposed) [2.7.0-1]
[11:12] -queuebot:#ubuntu-release- New binary: boost-defaults [s390x] (hirsute-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[11:14] -queuebot:#ubuntu-release- New binary: boost-defaults [arm64] (hirsute-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[11:19] -queuebot:#ubuntu-release- New binary: boost-defaults [armhf] (hirsute-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[11:34] -queuebot:#ubuntu-release- New binary: onednn [s390x] (hirsute-proposed/universe) [2.0+ds-1] (no packageset)
[11:35] -queuebot:#ubuntu-release- New binary: boost-defaults [riscv64] (hirsute-proposed/main) [<IP_ADDRESS>ubuntu1] (i386-whitelist, ubuntu-desktop)
[11:36] -queuebot:#ubuntu-release- New: accepted boost-defaults [amd64] (hirsute-proposed) [<IP_ADDRESS>ubuntu1]
[11:36] -queuebot:#ubuntu-release- New: accepted boost-defaults [armhf] (hirsute-proposed) [<IP_ADDRESS>ubuntu1]
[11:36] -queuebot:#ubuntu-release- New: accepted boost-defaults [riscv64] (hirsute-proposed) [<IP_ADDRESS>ubuntu1]
[11:36] -queuebot:#ubuntu-release- New binary: onednn [ppc64el] (hirsute-proposed/universe) [2.0+ds-1] (no packageset)
[11:36] -queuebot:#ubuntu-release- New: accepted boost-defaults [arm64] (hirsute-proposed) [<IP_ADDRESS>ubuntu1]
[11:36] -queuebot:#ubuntu-release- New: accepted boost-defaults [s390x] (hirsute-proposed) [<IP_ADDRESS>ubuntu1]
[11:36] -queuebot:#ubuntu-release- New: accepted boost-defaults [ppc64el] (hirsute-proposed) [<IP_ADDRESS>ubuntu1]
[11:44] -queuebot:#ubuntu-release- New binary: onednn [amd64] (hirsute-proposed/universe) [2.0+ds-1] (no packageset)
[12:34] -queuebot:#ubuntu-release- New: accepted onednn [amd64] (hirsute-proposed) [2.0+ds-1]
[12:34] -queuebot:#ubuntu-release- New: accepted onednn [s390x] (hirsute-proposed) [2.0+ds-1]
[12:34] -queuebot:#ubuntu-release- New: accepted onednn [ppc64el] (hirsute-proposed) [2.0+ds-1]
[14:26] <ricotz> doko, hi, may I point you to a libreoffice 7.0.4~rc2 package to use for the boost transition instead of doing a no-change rebuild?
[14:44] <ricotz> doko, libreoffice - 1:7.0.4~rc2-0ubuntu1 from https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+packages?field.name_filter=&field.status_filter=&field.series_filter=hirsute
[15:40] <LocutusOfBorg> vorlon, wrt all the delta we have because of i386, e.g. "can't depend on ocaml packages", and similar, we have to introduce delta to "drop build-deps" and this change is not easily upstreamable in debian.
[15:40] <LocutusOfBorg> my suggestion (sorry if this sounds bad), can be: introduce a new "fake-i386-binaries source package" that provides all the "missing binaries" just empty, so we can depend on that fake package and live happy. what do you think?
[23:20] -queuebot:#ubuntu-release- New binary: libxmlezout [amd64] (hirsute-proposed/universe) [1.06.2-4] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: libxmlezout [s390x] (hirsute-proposed/universe) [1.06.2-4] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: libgnatcoll [s390x] (hirsute-proposed/universe) [21.0.0-3] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: osmo-iuh [amd64] (hirsute-proposed/universe) [0.6.1+dfsg1-2] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: libxmlezout [ppc64el] (hirsute-proposed/universe) [1.06.2-4] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: libgnatcoll [ppc64el] (hirsute-proposed/universe) [21.0.0-3] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: osmo-iuh [s390x] (hirsute-proposed/universe) [0.6.1+dfsg1-2] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: osmo-iuh [ppc64el] (hirsute-proposed/universe) [0.6.1+dfsg1-2] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: libgnatcoll [amd64] (hirsute-proposed/universe) [21.0.0-3] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: libxmlezout [arm64] (hirsute-proposed/universe) [1.06.2-4] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: libxmlezout [armhf] (hirsute-proposed/universe) [1.06.2-4] (no packageset)
[23:35] -queuebot:#ubuntu-release- New binary: libxmlezout [riscv64] (hirsute-proposed/universe) [1.06.2-4] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: libgnatcoll [armhf] (hirsute-proposed/universe) [21.0.0-3] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: osmo-iuh [arm64] (hirsute-proposed/universe) [0.6.1+dfsg1-2] (no packageset)
[23:43] -queuebot:#ubuntu-release- New binary: osmo-iuh [armhf] (hirsute-proposed/universe) [0.6.1+dfsg1-2] (no packageset)
[23:45] -queuebot:#ubuntu-release- New binary: libgnatcoll [arm64] (hirsute-proposed/universe) [21.0.0-3] (no packageset)
[23:50] -queuebot:#ubuntu-release- New binary: osmo-iuh [riscv64] (hirsute-proposed/universe) [0.6.1+dfsg1-2] (no packageset)


[09:40] <johey> If my kernel hangs at boot when using lowlatency, how can I start tracking the problem down? Using Ubuntu 13.04 with official lowlatency kernel package.
[09:40] <johey> If started without quiet and splash kernel parameters, it just says "Loading Linux 3.8.0-31-lowlatency ..." then hangs at the purple screen.
[09:40] <johey> You can see a cursor or underscore at the line below, but it won't react on any keypress.
[09:40] <johey> Using a ThinkPad X1 Carbon, amd64 kernel.
[09:44] <smartboyhw> zequence_, your expertise^
[09:48] <johey> Good. That's a hard to find property. :)
[09:50] <smartboyhw> !kernel
[09:50] <smartboyhw> johey, though, linux-lowlatency is very simliar to linux in normal means
[09:51] <johey> Using the linux-generic is no problem. Booting perfectly. Lowlatency freeze totally.
[09:51] <smartboyhw> OK, that's a specific bug then
[09:51] <smartboyhw> johey, can you run "ubuntu-bug linux-lowlatency" within a terminal?
[09:51] <johey> I'm using it with other machines without problem.
[09:52] <johey> Ok, in a moment.
[10:30] <johey> smartboyhw: Bug reported. https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/1232413
[10:30] <smartboyhw> johey, thanks
[10:31] <johey> smartboyhw: Currently I am not using Ubuntu Studio on this machine, but it is the same kernel package, isn't it?
[10:31] <smartboyhw> johey, yes.
[10:32] <johey> I am sorry not being able to give more details. I don't like reporting a bug only saying it just hangs, but what can I do...
[10:33] <johey> I am quite technically skilled, but I'm not a kernel hacker. If there are things I can do to help debugging, please feel free to ask.
[10:33] <johey> Last time I even compiled a kernel was 2.4.
[10:34] <smartboyhw> johey, wah:O
[10:34] <johey> Nowadays, it just works, you know... :)
[10:36] <johey> Are the lowlatency and generic kernel images built from the same source just with different configurations, or is the lowlatency patched?
[10:36] <smartboyhw> johey, same source
[10:36] <smartboyhw> different configrations
[10:37] <johey> Ok. So what I could do is trying to narrow down the set of configuration options until I know which one causes the hang... Would it help you think, or is it just one option to enable a large set of code?
[10:38] <smartboyhw> johey, dunno
[10:38] <smartboyhw> I'm not the kernel guy
[10:39] <johey> Right. That's zequence_.
[10:57] <Heyokha> Hi
[11:00] <smartboyhw> Hello Heyokha
[11:01] <johey> smartboyhw: Do I have to use the lowlatency kernel to get realtime permissions for jack btw?
[11:06] <smartboyhw> johey, technically, as long as you're in the "realtime" group, you can get realtime permissions
[11:06] <smartboyhw> http://jackaudio.org/linux_rt_config
[11:07] <johey> I see. That might do it for me.
[11:07] <johey> I thought the group was audio.
[11:08] <johey> Mhm. adduser: The group `realtime' does not exist. .. Maybe this differ from ubuntu and ubuntustudio? Don't tell me I'm asking in the wrong channel... :)
[11:10] <smartboyhw> Technically, you are.
[11:10] <smartboyhw> !support | johey
[11:11] <smartboyhw> johey, it might be the audio group for us
[11:11] <smartboyhw> I forgotten which:P
[11:12] <johey> Yes I know. I happened to ask about my kernel issue in almost all #ubuntu* channels, and this one gave the best hits. :)
[11:12] <smartboyhw> johey, it should be "audio" for us
[11:15] <johey> Ok. I will investigate that. Maybe I don't need the lowlatency. As long as I can keep latency <20ms without suffering from too many xruns I'm happy.
[12:28] <zequence_> johey: If you don't do any live processing at all, you don't need low latency
[12:28] <zequence_> johey: Just to confirm, the -generic that works is the same version as the -lowlatency that doesn't work?
[12:32] <zequence_> Ah, yes. I can see it is from the bug report
[12:32] <zequence_> It's very unlikely for there to be problems with -lowlatency that do not occur on -generic, as they are almost the same exact kernel
[12:33] <zequence_> johey: Earlier versions of -lowlatency works fine, right?
[12:34] <zequence_> smartboyhw: johey: We use the audio group for realtime privilege
[12:37] <zequence_> There's no lowlatency patchset
[12:37] <zequence_> johey: It would be great if you could try other version of linux-lowlatency
[12:39] <johey> zequence_: I've tried with the oldest version I find in the repos, namely 3.8.0-22 with same result.
[12:40] <zequence_> johey: Try something like a 3.2 instead
[12:40] <zequence_> https://launchpad.net/~ubuntustudio-kernel/+archive/linux-lowlatency-sru/+packages
[12:40] <johey> It's fully reproducible on this machine. Haven't successfully passed the kernel load step one single time. Although, on my technically most equal machine, the ThinkPad X220, this is no issue at all.
[12:41] <zequence_> Download manually, under linux-lowlatency-*
[12:41] <zequence_> the package called linux-image-*-lowlatency-*
[12:41] <johey> Ok, I'll try that.
[12:45] <johey> Just to ensure, I don't need the kernel header packages, right? The installation warns me about it.
[12:49] <johey> zequence_: 3.2.0-54-lowlatency hangs the same way.
[12:58] <johey> I managed to get realtime permissions without the lowlatency kernel, but after trying recording audio I realize I really need the lowlatency kernel.
[12:59] <johey> Cannot even manage to get free from xruns with 20 ms.
[13:02] <johey> 20 ms latency that is.
[13:49] <zequence_> johey: You don't need low latency unless you are doing software monitoring
[13:50] <johey> zequence_: Well, I actually am.
[13:50] <zequence_> 20ms IMO is too high anyway
[13:50] <zequence_> johey: Can't you monitor externally?
[13:50] <zequence_> What is it you are recording?
[13:50] <johey> I'm using live guitar effects.
[13:51] <johey> When recording the latency is of lower importance.
[13:55] <zequence_> johey: Check your /var/log/dmesg.0
[13:57] <johey> zequence_: Nothing is written to /var/log/dmesg.* when booting a lowlatency kernel.
[13:58] <johey> At least not enough to write it's own kernel version.
[13:59] <johey> I've never before seen a kernel hang this early. Not one single character is printed to the screen by the kernel.
[14:00] <johey> It seems like it hangs while it is copied to memory.
[14:00] <smartboyhw> That's a rare bug:O
[14:00] <zequence-work> johey: This is the diff between -generic and -lowlatency, prior to building http://paste.ubuntu.com/6167050/
[14:00] <zequence-work> In the config, that is
[14:01] <johey> Ok, but the CONFIG_PREEMPT=y enables a large chunk of code I would guess.
[14:02] <zequence-work> Might be the realtime patch hackers might be interested in solving this problem
[14:03] <johey> Where can I find them?
[14:03] <zequence-work> https://rt.wiki.kernel.org/index.php/Mailinglists
[14:04] <zequence-work> johey: You might want to try a realtime kernel as well
[14:05] <zequence-work> johey: http://wiki.linuxaudio.org/wiki/system_configuration#build_your_own_real-time_kernel
[14:05] <zequence-work> Some of the realtime patch has been included into the vanilla kernel. Bit by bit.
[14:06] <johey> Alright! The lowlatency and realtime are different pieces of code?
[14:06] <zequence-work> lowlatency is not a patch at all
[14:07] <zequence-work> linux-lowlatency is linux-generic, but with the preemtp configuration
[14:07] <johey> I'm sure the preemt used to be a patch... And I thought it came from the realtime code, but I'm likely wrong. I usually am. :)
[14:08] <zequence-work> As I said, the realtime patch has been included into the vanilla code, bit by bit
[14:09] <zequence-work> johey: I'd be interested to know if a realtime kernel would work for you or not
[14:09] <johey> Ok. Anyway, trying out a realtime kernel is the next step I think.
[14:09] <johey> I will let you know.
[14:09] <zequence-work> johey: Thanks
[14:09] <johey> I mean it's the next-next step. Trying AVLinux first.
[18:31] <johey> zequence-work: It also hangs with 3.10.10-rt.
[19:28] <johey> zequence-work: GAAAAHHH!! You know what... ThinkPad X1 Carbon is really well prepared for standing up against evil free software. Just disabling every option in the BIOS Security menu fixed the issue.
[19:31] <OvenWerks> figures.


[17:04] <dean_> Hey. I just installed ubuntu gnome 16.04. I have a problem where when screen locks if i'm not using the laptop it freezes and i cannot unlock it again. The mouse still works and I can switch to a tty
[17:07] <dean_> The light on caps lock still works so I'm assuming that the keyboard is still working. Had the same problem on 15.10 as well. Was stuck with unity for a while. ughhh. lol.
[17:08] <dean_> I'm using Caffeine to stop it from locking for the time being but if anyone has a fix for this I'd really appreciate it.
[18:37] <DiamondSword> hello people.
[18:38] <DiamondSword> I'm interested in ubuntu gnome.. I'm trying it on VM, updated gnome to 3.20 to see the latest changes and new comings. but I don't have create "New Document" option when I right clicked.
[18:39] <DiamondSword> is it something buggy or it's already not a property of Gnome?
[18:39] <DiamondSword> I want to add it there. how can I do it?
[18:46] <DiamondSword> heyyy ?


[23:16] <sarnold> hallyn: hey :) we've got some CIS compliance tooling, eg https://ubuntu.com/security/certifications/docs/usg/cis/compliance -- I don't know how much we contribute to the CIS benchmarks themselves, but I wouldn't be surprised if we could communicate with them over specific pieces of bad advice
[23:17] <sarnold> hallyn: I wonder if that "solution" is specifically a tenable suggestion or a CIS suggestion; blindly running a sudo find .. -exec chmod seems like a horrible suggestion
[23:19] <konstruktoid> I know that a couple of Ubuntu folks comment and help update CIS benchmarks
[23:20] <konstruktoid> > hey sarnold - just wondering, do you know whether you all have any involvment with this: https://www.tenable.com/audits/items/DISA_STIG_Ubuntu_20.04_LTS_v1r5.audit:a9e7d4a8941a4fee48cbec0b5e72484a ?
[23:20] <konstruktoid> But this isn't CIS, but DISA STIG
[23:21] <sarnold> d'oh
[23:21] <sarnold> I saw 'stig' and then my mind went blank on the details
[23:22] <sarnold> we've got some disa stig compliance tools, too https://ubuntu.com/security/certifications/docs/disa-stig/audit
[23:22] <sarnold> thanks konstruktoid


[18:30] <braziercustoms> ok again I have spent days looking, 16.04 + Conjure-up  Havent been able to launch any instance I get  [Error: No valid host was found. There are not enough hosts available.].


[15:44] <efactusa> <IP_ADDRESS>  www.myefact.com myefact.com greatestate.com www.greatestate.com westonmass.net  http://www.myefact.com http://greatestate.com http://westonmass.net   do you know if I am supposed to put the HTTP part in the hosts file for LINUX  server? ????? a !!!!!!
[15:45] <efactusa> NO ONE ANSWERS ME THIS CHAT IS NO GOOD


[03:38] <yuval> Good evening.
[03:43] <ChinnoDog> hi yuval
[03:43] <yuval> How are you?
[03:43] <ChinnoDog> I am fine. Getting pretty sleepy though.
[03:45] <yuval> I had a long flight and I touched ground about an hour ago.
[03:45] <ChinnoDog> Where did you fly from?
[03:56] <yuval> From across the pond, then anoher pond.
[03:56] <yuval> From Israel
[04:07] <ChinnoDog> Long flight.  If battery life is an issue in the future I will need a portable nuclear reactor.
[23:40] <Samuraialba> Good bacon to all!
[23:41] <JonathanD> hi
[23:44] <Samuraialba> How is it going?
[23:44] <ChinnoDog> sup baconator
[23:44] <JonathanD> Ok.
[23:44] <Samuraialba> Just had my Dell Dimension e510 Amber light and smoke on me
[23:44] <Samuraialba> >.<
[23:45] <Samuraialba> Pent D 3.4Ghz
[23:45] <Samuraialba> *PO*
[23:45] <JonathanD> dead?
[23:45] <Samuraialba> oops
[23:45] <Samuraialba> *POP*
[23:45] <Samuraialba> Caps on baord
[23:45] <JonathanD> :(
[23:45] <Samuraialba> Now I'm without my Mumble/Minecraft box LOL
[23:46] <JonathanD> need a board?
[23:46] <Samuraialba> It's a BTX >.<
[23:46] <JonathanD> eek.
[23:46] <Samuraialba> Would need a case too LOl
[23:46] <JonathanD> Don't have any BTX
[23:46] <Samuraialba> Looking at an Atom D2500
[23:46] <JonathanD> Have some cases maybe.
[23:46] <Samuraialba> I have a Mini ITX case here.   I had to recover from that before continuing.
[23:51] <ChinnoDog> That board is pretty old. It might be from the time period with the mass distribution of defective caps.
[23:52] <ChinnoDog> Pretty much all motherboards from that year have bulging caps
[23:52] <Samuraialba> yeah
[23:52] <Samuraialba> noticed a few bulging near the PCIE
[23:53] <Samuraialba> Hope my Radeon 4670 is ok


[15:32] <heftig> how much spam or other abusive behavior from unregistered users do you get in #ubuntu?
[15:35] <heftig> #archlinux currently uses +r, and I would like to argue for its removal as it's a prerequisite for getting the channel bridged to matrix
[16:48] <hggdh> heftig: currently not much; we went back to -r some weeks ago, and it is, so far, manageable
[16:53] <heftig> hggdh: does the join limit help?
[16:57] <hggdh> heftig: I think so; usually clustered joins (unfortunately) tend to happen on SPAM attacks, so you have a chance of minimising effects and reacting. I do not have stats, though
[17:07] <heftig> thanks
[17:59] <ZarroBoogs> FYI, something going on with linode Newark, ubottu might be down.


[23:21] <tgunr> anyone with supermicro server experience? I have a x7dca-l which i powered on 4 times, now it won't power on
[23:21] <BlueProtoman> How can I install a 32-bit Java on Ubuntu 13.04, alongside 64-bit Java?
[23:21] <wylde> !info mjpg-streamer
[23:22] <Xerofyte> How can I check the Notifications
[23:23] <wylde> BlueProtoman: https://help.ubuntu.com/community/MultiArch
[23:23] <jboii> only synaptic will open and show message that says , row 57 is what isnt functional
[23:23] <jboii> thats the message i copied in pastebin
[23:23] <bekks> jboii: And it tells you the filename of the file where line 57 is not working.
[23:23] <bekks> jboii: So pastebin that file.
[23:24] <BlueProtoman> wylde: Thanks, but Java doesn't seem to have any 32-bit packages.
[23:25] <wylde> BlueProtoman: you won't see any until you install the ia32libs
[23:25] <Xerofyte> I mean how can I check the last notification which appeared in the Doc above.
[23:25] <wylde> BlueProtoman: and make your system multiarch
[23:25] <chstburstr> from the text grub, how does one invoke nomodeset?
[23:25] <bekks> !nomodeset | chstburstr
[23:25] <BlueProtoman> wylde: How do I do the latter?
[23:26] <wylde> BlueProtoman: fair warning, you're going to be pulling a ton of extra libs
[23:26] <BlueProtoman> wylde: Mind elaborating?
[23:30] <loki__> how i can simply start my command on boot of ubuntu?
[23:30] <loki__> for example this sudo -u motion mjpg_streamer -b -i "input_uvc.so -r 1280x720 -f 30 -d /dev/video0" -o "output_http.so -p 8090 -w /usr/www"
[23:31] <bekks> !autostart
[23:31] <jrib> loki__: proper way is to create an upstart service
[23:31] <vadi> I've got an arbitrary set of data that is zipped - how can I make it so gzip will unzip it for me? It says "not in gzip format" at the moment (file just says "data")
[23:32] <loki__> found this http://upstart.ubuntu.com/cookbook/
[23:32] <bekks> vadi: gzip will unpack .gz only, not .zip
[23:32] <vadi> Oh
[23:32] <bekks> vadi: those are different formats.
[23:32] <vadi> What is a more proper tool to use?
[23:32] <bekks> vadi: "unzip"
[23:32] <vadi> Thank you
[23:33] <chstburstr> During a live boot, I am dumped to a command prompt without a GUI.  I attempted to use nomodeset, but either it is not the issue, or I have implemented it incorrectly.
[23:33] <jboii> the message i got first  i pastebin and copied to u
[23:33] <wilee-nilee> chstburstr: have you checked the sum?
[23:33] <wylde> BlueProtoman: I've only ever bothered adding i386 once and it wasn't on an ubuntu box. I'm not 100% certain it's the same. On another debian based box  I simpy ran sudo dpkg --add-architecture <arch>
[23:33] <jboii> the document that was created , i downloaded and copied info to pastebin , and this was created
[23:34] <chstburstr> Sum checks out fine
[23:34] <chstburstr> As does the disk
[23:34] <jboii> http://paste.ubuntu.com/6169071/
[23:34] <wilee-nilee> chstburstr: this a usb or dvd?
[23:34] <jboii> the filename that software updater said it was named , is xanal
[23:34] <bekks> jboii: Thats wrong. No one here said "download a file".
[23:34] <chstburstr> wilee-nilee, usb
[23:35] <chstburstr> wilee-nilee, there is no dvd drive available right now
[23:35] <bekks> jboii: And finally, you got me to get tired. I am resting your case. Someone else may help you.
[23:35] <wilee-nilee> chstburstr: how are you loading it?
[23:35] <wilee-nilee> chstburstr: how are you loading it?sb
[23:35] <wilee-nilee> Usb*
[23:35] <chstburstr> I used the windows pendrive installer
[23:35] <jboii> software updater wont open offcourse ,, only synaptic opens and it says only row 57
[23:36] <chstburstr> wilee-nilee, pendrive installer, to load from usb
[23:37] <wilee-nilee> chstburstr: I would try another, and check the web with your hardware ie the computer to see 9f there are problems in general. Last is this a dualboot?
[23:38] <jboii> if i start the reebot the system , will i be able to load the system?
[23:38] <chstburstr> wilee-nilee, it will be a dual boot.  I've tried Ubuntu 13, and the LTS, linux mint, and xbuntu
[23:38] <wilee-nilee> chstburstr: Is the computer uefi?
[23:39] <chstburstr> wilee-nilee, yes, I am using the AMD 64 iso
[23:39] <chstburstr> wilee-nilee, and it's an AMD A6 chip... so that happens to work out
[23:40] <EvilBlob> AMD64 just means 64-bit, you don't need an AMD chip
[23:40] <chstburstr> right... it just is nice to work out that way
[23:42] <wilee-nilee> !uefi | chstburstr
[23:42] <wilee-nilee> !uefi
[23:42] <wilee-nilee> chstburstr: not sure why the bot does not kick the uefi info, here is more. http://ubuntuforums.org/showthread.php?t=2147295
[23:44] <chstburstr> wilee-nilee, thank you for that information.    I will research and possibly come back later
[23:44] <chstburstr> I appriciate your help
[23:45] <arooni-mobile> how do i download the separate+ plugin for gimp ?  ubuntu 13.04
[23:46] <wilee-nilee> chstburstr: ahh dinner cool, enjoy
[23:48] <wylde> !info gimp-plugin-registry
[23:48] <arooni-mobile> how can i fix this: Unsupported color mode: CMYK ... gimp 2.8.x ubuntu 13.04
[23:50] <wylde> arooni-mobile: they may have a good idea over in #gimp
[23:51] <bekks> arooni-mobile: use a supported color mode.
[23:52] <arooni-mobile> id think cmyk shouldnt be impossible to support
[23:52] <arooni-mobile> but im not a gimp dev
[23:53] <macbuntuargh> dpkg -L wicd-daemon claims that the package has a file /etc/wicd/dhclient.conf.template.default, but that file is nowhere to be found. I tried to reinstall the package, but the file still isn't there. Why?
[23:53] <macbuntuargh> (wicd is failing to start because that file is missing)
[23:54] <macbuntuargh> oh god why did I look at the source code my eyes


[15:01] <sil2100> o/
[15:01] <philroche> \o
[15:03] <cyphermox> o/
[15:03] <juliank> o/
[15:08] <xnox> \o
[15:11] <cyphermox> slangasek: ?
[15:13] <cyphermox> #startmeeting Weekly Ubuntu Foundations team
[15:13] <meetingology> Meeting started Thu Aug 23 15:13:53 2018 UTC.  The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:13] <meetingology> Available commands: action commands idea info link nick
[15:14] <cyphermox> #topic Lightning rounds
[15:14] <cyphermox> echo $(shuf -e slangasek bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson rcj philroche Odd_Bloke fginther juliank)
[15:15] <cyphermox> Odd_Bloke slangasek philroche doko rbalint bdmurray infinity rcj juliank mwhudson tdaitx fginther sil2100 cyphermox xnox
[15:15] <Odd_Bloke> NOOOOOOO
[15:15] <cyphermox> sorry
[15:15] <Odd_Bloke> * On vacation last week
[15:15] <Odd_Bloke> * Playing catch-up
[15:15] <Odd_Bloke> * Completed reintroduction of root tarballs in bionic and cosmic (LP: #1585233)
[15:15] <cyphermox> first shuffle got me first, and it would have looked rigged.
[15:15] <Odd_Bloke> * Interviewing candidates
[15:15] <Odd_Bloke> * Partner-facing work
[15:15] <Odd_Bloke> (done)
[15:15] <Odd_Bloke> slangasek:
[15:15] <Odd_Bloke> Who presumably isn't here, else he'd be running the meeting.
[15:15] <Odd_Bloke> philroche:
[15:15] <philroche> * Final L1TF image publication
[15:15] <philroche> * Cloud image build system development
[15:15] <philroche> * Cloud image build system vanguard
[15:15] <philroche> (done)
[15:15] <Odd_Bloke> doko:
[15:15] <Odd_Bloke> (Is on vacation?)
[15:17] <xnox> ill
[15:17] <sil2100> Mathias mentioned something he'll not be able to attend the meeting today
[15:18] <cyphermox> rbalint: ?
[15:18]  * juliank goes
[15:18] <juliank> * apt security fixes for CVE-2018-0501 (https://mirror.fail)
[15:18] <juliank> * some apt bug triage, closing about 50 bugs (~9%)
[15:18] <juliank> * answered questions from slashd about apt (bug 1788486)
[15:18] <juliank> * spent hours figuring out how to boot grub on ppc64el to reproduce bug 1785859 (was easy in the end, but hard to find instructions...), but found the fix, prepared a patch and sent it upstream (just some uninitialized variables.... https://lists.gnu.org/archive/html/grub-devel/2018-08/msg00074.html) merge proposal and SRU soon
[15:19] <juliank> * verified fix for gpgme1.0 bug 1762384
[15:19] <juliank> * further discussions re frontend locking and trying to figure out the fix for that for aptdaemon
[15:19] <juliank> (done)
[15:19] <cyphermox> tdaitx: ?
[15:19] <cyphermox> fginther: ?
[15:20] <juliank> ANYONE?
[15:20] <xnox> sil2100, ?
[15:20] <sil2100> uh oh!
[15:20] <cyphermox> Bueller?
[15:20] <sil2100> - Shorter week because of holidays last week
[15:20] <sil2100> - Still melting here
[15:20] <sil2100> - SRU reviews and releases (big queue due to holidays)
[15:20] <sil2100> - ubuntu-image:
[15:20] <sil2100>   * Did a preliminary review of the --filesystem PR
[15:20] <sil2100>   * Made u-i smart by making the qemu-user-static dep optional
[15:20] <sil2100>   * Re-released 1.4 to cosmic, pushed to bionic and xenial
[15:20] <sil2100> - core:
[15:20] <sil2100> - Kernels:
[15:20] <sil2100>   * Some emergency kernel releases + re-reviews of current cycles
[15:20] <sil2100>   * Figuring out the shanky ADT handling, getting rid of some blocking NBSes
[15:20] <sil2100>   * Some help here and there in the absence of Andy
[15:20] <sil2100>   * 4.15 kernel releases
[15:21] <sil2100> - Updated google-cloud-sdk to 212.0.0
[15:21] <sil2100> - Investigating some update-github-jobs failure spamming
[15:21] <sil2100> - Small fixes to the security-britney instance to make it finally reliable
[15:21] <sil2100> - Some familiarizing with the ubuntu-release-upgrader an update-manager code
[15:21] <sil2100> (done)
[15:22] <cyphermox> - shim-review: Cisco, CentOS.
[15:22] <cyphermox> - resubmitted shim 15 snapshot for signature by MS
[15:22] <cyphermox> - merging grub from Debian
[15:22] <cyphermox> - testing grub2 with lockdown
[15:22] <cyphermox> shim-review matrix42
[15:22] <cyphermox> - rework initramfs-tools bionic SRU (0.130ubuntu3.3):
[15:22] <cyphermox>   - remove verification-failed patch for RESUME
[15:22] <cyphermox>   - add ZFS fix (LP: #1661629) from John Gallagher
[15:22] <cyphermox> (done)
[15:23] <xnox> * working on systemd regressions, should finally migrate
[15:23] <xnox> * working on s390x updates - tools, cryptsetup, systemd
[15:23] <xnox> * did tiny uploads for the qt transition
[15:23] <xnox> * uploading fixes for usr-merge, unlikely to flip it on for cosmic (not enough stuff is tested or fixed yet, in debian)
[15:23] <xnox> * marked an interview task
[15:23] <xnox> * monday is UK bank holiday, so short week next week
[15:23] <xnox> (done)
[15:24] <cyphermox> skipping over the incoming bug triage, we don't seem to be quorate
[15:24] <cyphermox> #topic AOB
[15:24] <cyphermox> anything?
[15:25] <cyphermox> if you're not here, raise your hand.
[15:25] <juliank> not from me! ;)
[15:25] <cyphermox> in the event of a missing Steve, who wants to chair next?
[15:26] <cyphermox> don't all speak at once ;P
[15:26] <cyphermox> #endmeeting
[15:26] <meetingology> Meeting ended Thu Aug 23 15:26:19 2018 UTC.
[15:26] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-08-23-15.13.moin.txt
[15:26] <sil2100> I can!
[15:26] <cyphermox> sil2100:  ;)
[15:26] <sil2100> ME ME
[15:26] <cyphermox> http://people.ubuntu.com/~cyphermox/meetings/foundations.html
[15:26] <sil2100> Sweet
[15:26] <cyphermox> (I will finally remove tribaal from the shuffle)
[15:27] <sil2100> Chris will always be a part of our team, at least deep in our hearts
[15:28] <cyphermox> sil2100: btw, this is just javascript doing the shuffling, no need to actually run a command in a terminal
[15:29] <sil2100> cyphermox: oh, convenient!  How's it going? ;)
[15:41] <tribaal> Fine thanks! Still working from home, and the new gig is fun (there is some overlap of concerns - we've been busy patching for intel stuff as I suspect you all have as well :) )
[15:44] <sil2100> hah, oh yes we did ;)
[15:44] <tribaal> I bet :) I remember the last drill
[17:24] <elopio> /buffer 6


[12:14] <lotuspsychje> mknepper: wich commandline do you use?
[12:15] <mknepper> Hello, I'm reporting a bug in 20.04 LTS. Gnome-screenshot does not send images to the clipboard if you use the command line (gnome-screenshot -c or gnome-screenshot --clipboard) - this goes for adding a custom keyboard shortcut in the system settings as well (search for Keyboard Shortcuts in menu, open, add shortcut with options gnome-screenshot -c).
[12:15] <mknepper> lotuspsychje, gnome-screenshot -c or gnome-screenshot --clipboard
[12:15] <mknepper> Either will not send data to the clipboard
[12:15] <mknepper> However! if you use the GUI, it -does- work
[12:20] <lotuspsychje> mknepper: yeah seems like that isnt working like you say
[12:20] <Miles8of9> how do you download focal fossa? it's not on ubuntu site
[12:20] <lotuspsychje> Miles8of9: see the topic for the daily iso
[12:20] <mknepper> lotuspsychje, yeah, I'm not sure why either. I don't know how to file a bug report for that either or I would
[12:21] <lotuspsychje> mknepper: to file a bug on ubuntu, please use ubuntu-bug packagename
[12:21] <mknepper> will I be able to describe the problem or will it just send data?
[12:21] <lotuspsychje> mknepper: both
[12:21] <mknepper> awesome. I'll file that now
[12:22] <lotuspsychje> Miles8of9: just keep in mind 20.04 is in development in this stage, breakage can still happen, for testers only
[12:27] <Miles8of9> before installing 18.04 i want to test drive a bit the latest version
[12:27] <Miles8of9> maybe it won't even boot
[12:28] <lotuspsychje> it boots
[12:40] <lotuspsychje> mknepper: it does copy, when you just gnome-screenshot
[12:41] <mknepper> it doesn't for me for some reason
[12:41] <lotuspsychje> without the -c ?
[12:41] <mknepper> yes
[12:41] <mknepper> I'm not seeing it my clipboard history either
[12:41] <mknepper> it works fine if I use the GUI
[12:42] <lotuspsychje> mknepper: did you tweak hotkeys or something?
[12:42] <mknepper> I added a hotkey for gnome-screenshot -a -c
[12:42] <mknepper> to screenshot an area and copy it to clipboard
[12:42] <mknepper> but even running just gnome-screenshot in the terminal gives me nothing
[12:42] <lotuspsychje> thats weird indeed
[12:43] <lotuspsychje> here it works, without the arguments
[12:43] <mknepper> i wish gnome-screenshot had a way to display stuff in verbose in the terminal
[12:43] <mknepper> that's really weird, shouldn't you have to specify that it copies to the clipboard?
[12:43] <mknepper> i thought by default gnome-screenshot just saved a .png with the timestap as the filename
[12:43] <mknepper> *timestamp
[12:43] <lotuspsychje> it does here
[12:44] <lotuspsychje> mknepper: can you try this on a new user please?
[12:44] <mknepper> yes, let me set up another user
[12:47] <mknepper> thats a no-go
[12:47] <lotuspsychje> so doesnt work either?
[12:48] <mknepper> no, here's a screenshot of just using 'gnome-screenshot' from the terminal
[12:48] <mknepper> https://imgur.com/a/eNq69kk
[12:48] <mknepper> and one of using 'gnome-screenshot --clipboard'
[12:48] <mknepper> https://imgur.com/a/ifEtD7k
[12:49] <mknepper> so I'm not sure what's going on. this fossa install is up to date
[12:49] <lotuspsychje> and they dont create a pic in your pictures folder neither?
[12:49] <mknepper> it does create a pic in the pictures folder
[12:49] <mknepper> that part works
[12:49] <lotuspsychje> ah
[12:49] <mknepper> it just doesn't copy to the clipboard from command line
[12:49] <lotuspsychje> just the clipboard
[12:49] <lotuspsychje> right ic
[12:49] <mknepper> yeah so weird
[12:49] <mknepper> and it copies to the clipboard IF you use the GUI
[12:50] <mknepper> so somehow the GUI works but CLI doesnt, not sure what the difference is
[12:50] <mknepper> maybe the gnome-devs changed something and it hasn't been updated yet, idk
[12:50] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1733890
[12:51] <mknepper> my main user is set up as an adminstrator, didn't work, the tester user is a standard user, same thing
[12:51] <mknepper> oh, interesting
[12:51] <mknepper> i couldn't find that bug
[12:51] <mknepper> that looks a little different though
[12:52] <lotuspsychje> mknepper: can you try #13 paste into gmail?
[12:52] <mknepper> yes let me try to paste into a gmail message
[12:53] <mknepper> doesn't work
[12:53] <lotuspsychje> kk
[12:54] <mknepper> itd be really useful if i could get some sort of verbose output to see what's going on but Idk how to do that
[12:54] <lotuspsychje> journalctl -f to see logs about your system
[12:55] <mknepper> not seeing it in there either. some stuff covering the terminal and ffaudio-core but thats it
[12:56] <lotuspsychje> perhaps proceed with a new bug mknepper
[12:56] <mknepper> okay, running the GUI, i got something
[12:57] <mknepper> https://pastebin.com/PHyjUSNT
[12:59] <lotuspsychje> !info gnome-screenshot
[12:59] <lotuspsychje> is your version right mknepper ^
[12:59] <mknepper> let me double check
[12:59] <mknepper> yes, 3.33.90
[13:00] <mknepper> i have an idea. what if i have to specify the X display?
[13:00] <mknepper> gnome-screenshot --clipboard --display=default_display
[13:00] <mknepper> Idk how to do it, like, what i'd put in there
[13:00] <mknepper> but here: Jan 29 06:55:42 ubuntu dbus-daemon[1886]: [session uid=1000 pid=1886] Activating service name='org.gnome.seahorse.Application' requested by ':1.40' (uid=1000 pid=2249 comm="/usr/bin/gnome-shell " label="unconfined")
[13:00] <mknepper> is :1.40 the X display?
[13:01] <lotuspsychje> i think the display argument is just when you want to specify another then default
[13:02] <mknepper> hmm.
[13:02] <lotuspsychje> but do try
[13:02] <mknepper> i couldn't get it to work, but then again I don't know how to specific an X display
[13:02] <mknepper> Also, I pasted the wrong thing
[13:02] <mknepper> Jan 29 06:55:42 ubuntu dbus-daemon[1886]: [session uid=1000 pid=1886] Activating service name='org.gnome.Screenshot' requested by ':1.40' (uid=1000 pid=2249 comm="/usr/bin/gnome-shell " label="unconfined")
[13:03] <mknepper> that happens when you run the GUI, but nothing happens in the journalctl if you use the commandline option
[13:03] <mknepper> i guess I could just find another screenshot application
[13:08] <lotuspsychje> mknepper: try ctrl+prtscr
[13:08] <lotuspsychje> that works for me
[13:12] <mknepper> That worked
[13:13] <mknepper> ctrl+shift+prntscrn worked too
[13:14] <mknepper> strange, wonder what Ubuntu is using as the default command that makes it work vs. using the command line
[13:24] <lotuspsychje> mknepper: how about you proceed with the bug, let the devs fight it out?
[13:24] <mknepper> sounds good
[13:24] <mknepper> will do, ty
[13:24] <lotuspsychje> use ubuntu-bug ok
[13:28] <mknepper> Okay, someone else reported the same bug for 19.10
[13:28] <mknepper> Selected "Affects me"
[13:28] <lotuspsychje> whats the ID plz mknepper
[13:29] <mknepper> #1852679
[13:30] <mknepper> https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1852679
[13:30] <lotuspsychje> tnx
[13:31] <lotuspsychje> nice find mknepper affected too
[13:31] <mknepper> I added some basic info in my comments
[13:31] <mknepper> Hope this helps :)
[13:32] <lotuspsychje> mknepper: please mention its on 20.04
[13:32] <mknepper> I did
[13:33] <lotuspsychje> ah my bad, had to reload :p
[13:34] <mknepper> haha no worries. hopefully we can figure out what's causing this. thanks again. I'll keep hunting down bugs.
[13:34] <lotuspsychje> cool tnx for helping out mknepper
[13:35] <lotuspsychje> lemme try that on bionic holdon
[13:38] <lotuspsychje> mknepper: works on bionic, tested by 2 users
[13:43] <mknepper> hmm
[13:43] <mknepper> so something changed from bionic up
[13:43] <lotuspsychje> yes the version :p
[14:14] <mknepper> hahaha
[14:14] <lotuspsychje> :p


[08:02] -queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.4] has been marked as ready
[11:21] -queuebot:#ubuntu-quality- Builds: Kubuntu Desktop amd64 [Focal 20.04.4] has been marked as ready
[11:30] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop amd64 [Focal 20.04.4] has been marked as ready
 0447
 http://<IP_ADDRESS>/buggbuntu.webm GNOME App Chooser bugs in the latest 20.4.4 test images
 same in both live and installed system in Virtualbox
 where is bug report? (re @bittin1: same in both live and installed system in Virtualbox)
 nowhere yet (re @Leokolb: where is bug report?)
 will see if i can reproduce (re @bittin1: nowhere yet)
 Have in virt machine ..will test barebone
 @sil2100 could not find the problem in Qemu, so seems to be a Virtualbox thing, trying on real hardware now an older HP laptop
 running a test now on new machine - barebone (re @bittin1: @sil2100 could not find the problem in Qemu, so seems to be a Virtualbox thing, trying on real hardware now an older HP laptop)
[16:32] <bittin> works on a HP 655 older laptop so thinks its a Virtualbox thing
 Can confirm works on barebone machine but error in VirtBox (re @ubuntu_bridge_Bot: (irc) <bittin> works on a HP 655 older laptop so thinks its a Virtualbox thing)
[17:09] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.4] has been marked as ready
[18:10] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.4] has been marked as ready
[18:10] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity ppc64el [Focal 20.04.4] has been marked as ready
[18:10] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity arm64 [Focal 20.04.4] has been marked as ready
[18:10] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity s390x [Focal 20.04.4] has been marked as ready
[18:18] -queuebot:#ubuntu-quality- Builds: Ubuntu Studio DVD amd64 [Focal 20.04.4] has been marked as ready
[19:07] -queuebot:#ubuntu-quality- Builds: Ubuntu Server arm64+raspi [Focal 20.04.4] has been marked as ready
[19:07] -queuebot:#ubuntu-quality- Builds: Ubuntu Server riscv64+unleashed [Focal 20.04.4] has been marked as ready
[19:07] -queuebot:#ubuntu-quality- Builds: Ubuntu Server armhf+raspi [Focal 20.04.4] has been marked as ready
[19:07] -queuebot:#ubuntu-quality- Builds: Ubuntu Server riscv64+unmatched [Focal 20.04.4] has been marked as ready
[19:48] -queuebot:#ubuntu-quality- Builds: Ubuntu Base amd64 [Focal 20.04.4] has been marked as ready
[19:48] -queuebot:#ubuntu-quality- Builds: Ubuntu Base armhf [Focal 20.04.4] has been marked as ready
[19:48] -queuebot:#ubuntu-quality- Builds: Ubuntu Base riscv64 [Focal 20.04.4] has been marked as ready
[19:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base arm64 [Focal 20.04.4] has been marked as ready
[19:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base s390x [Focal 20.04.4] has been marked as ready
[19:49] -queuebot:#ubuntu-quality- Builds: Ubuntu Base ppc64el [Focal 20.04.4] has been marked as ready
[20:05] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop amd64 [Focal 20.04.4] has been marked as ready


[00:13] <bschaefer> MCR1, hmm strange, its alt+f5 for me one time, now its Ctrl+Super+Down, it seems like its random
[00:13]  * bschaefer goes to check the default value in the generated code
[00:14] <bschaefer> hmm it seems to want to set it as       <default><Alt>F5</default>
[00:15]  * bschaefer wonders if its using the wrong schemas
[00:16] <bschaefer> MCR1, wait, i was looking at the wrong branch....mines getting generated to
[00:16] <bschaefer>       <default><Control><Super>Down</default>
[00:16] <bschaefer> which it shouldn't be...
[00:16] <MCR1> hmmm
[00:17] <bschaefer> MCR1, hmm im seeing it set to       <default><Control><Super>Down</default>
[00:17] <bschaefer> in the metadata/core.xml.in
[00:17] <MCR1> then you have to pull again probably
[00:17]  * bschaefer 's fire fox crashed
[00:18] <bschaefer> o nice, a new rev in the core.xml
[00:19] <MCR1> :)
[00:22] <bschaefer> MCR1, also add {}
[00:22] <bschaefer> to your if/else
[00:23] <bschaefer> its confusing to read when the cond ends and the statement begins
[00:23] <MCR1> yep, you are right
[00:23] <bschaefer> MCR1, usually always include a {} if you have an if/else
[00:25] <bschaefer> MCR1, usually always include a {} if you have an if/else
[00:25] <bschaefer> opps
[00:25] <MCR1> ok, ack
[00:25]  * bschaefer hit up on the wrong window
[00:25] <bschaefer> :)
[00:28] <MCR1> Done - how is the functionality ?
[00:28] <MCR1> does it finally do what it is supposed to ?
[00:28] <MCR1> ;)
[00:32]  * bschaefer is having a window focus problem
[00:33] <bschaefer> MCR1, sweet, works
[00:33] <MCR1> phew
[00:33] <MCR1> togh job for one shortcut ;)
[00:33] <MCR1> *tough
[00:33] <bschaefer> now ill approve that and poke Daniel about the patch...though he wont have anytime besides to point me in the right direction
[00:33] <bschaefer> yeaah
[00:34] <MCR1> cool - thanx - I count on you
[00:34]  * bschaefer has a bunch of stuff on the stack
[00:34]  * bschaefer goes to finish some other work
[00:34] <MCR1> I'll do it if necessary...
[08:51] <jibel> hey, there's no auto upload of unity to the release the morning
[08:51] <jibel> there are failures in autopilot for unity and indicators
[08:51] <jibel> and dbus-test-runner FTBFS (fatal warning, g_type_init deprecated)
[08:51] <jibel> sil2100, ^
[08:54] <sil2100> jibel: hi
[08:55] <sil2100> jibel: yes, we had a talk with fginther and mterry
[08:55] <sil2100> jibel: this week there was again some refactoring in the switcher and it broke all the switcher tests ;/
[08:55] <sil2100> jibel: it was pretty late yesterday so I asked them to give me time today in the morning for fixing it
[08:55] <sil2100> jibel: so I'm working on it now
[08:57] <jibel> sil2100, k, thanks
[10:13] <smspillaz> bregma: the recent refactoring on SwitcherController doesn't make a whole lot of sense to me
[10:14] <smspillaz> bregma: it seems like we're putting bits of buisness logic inside the interface that we provide to clients. Was that intended or am I reading it wrong ?
[10:15] <luv> rye: yo, morning - last night I tried to forward port the window list patch: http://killem.al/unity-612-launchericon-windowlist.patch
[10:16] <sil2100> smspillaz: hi
[10:16] <luv> though, I didnt' get it to compile because i used a week old (or so) branch and it ended up with g++ segfault even without my patch, but i'm kinda confident it will work :-)
[10:17] <sil2100> smspillaz: I'm in the middle of fixing up switcher tests again, since bregma'a most recent changes removed the impl completely from introspection, breaking all switcher tests - do you intend on changing the switchercontroller again? Since I don't want to do the same work 3 times again ;p
[10:17] <smspillaz> I don't know whats happening because I've seen a complete lack of communication from the PS team
[10:18] <smspillaz> I suspect we should have a chat with bregma to figure what that was all about
[10:18] <smspillaz> I appreciate the desire to make some methods nonvirtual, but doing that makes testing with other components later down the road a total PITA
[10:19]  * sil2100 liked the SwitcherController when it was simple as in the beginning :(
[10:19] <sil2100> luv: thanks! I'll also try looking at it and testing it later
[10:19] <smspillaz> sil2100: it was completely untestable
[10:19] <smspillaz> the original SwitcherController is why we have the sed script BS in unity
[10:20] <sil2100> smspillaz: would be good if all the unity devs could discuss the whole concept and decide on a final version, so that we can rewrite autopilot to accomodate the changes once and for all
[10:21] <sil2100> Since currently I'm most worried with the autopilot switcher tests being broken again, which is blocking daily releases
[10:22] <MCR1> JohnLea: Hi :) Proud to announce to you: bug 966099 is in the process to be fixed :)
[10:22] <MCR1> JohnLea: (properly)
[10:23] <seb128> sil2100, fginther: hey, jibel said you are looking a indicators' stack test failures ... what is broken exactly? I would like to see the current libdbusmenu autoland ;-)
[10:23] <JohnLea> MCR1; awesome! It will be super to get it fixed at long, long last ;-)
[10:23] <MCR1> JohnLea: Next one is bug 890747
[10:24] <JohnLea> MCR1; cool ;-)
[10:24] <luv> sil2100: nice, thanks
[10:24] <MCR1> JohnLea: But for this we gotta remove a standard gnome-shortcut
[10:24] <sil2100> seb128: hi! Ok, let me check that in a moment, since I was looking into unity-release autopilot tests right now, but I'll check it and get back to you in a moment
[10:24] <MCR1> JohnLea: As currently gnome will propose to log you out
[10:24] <JohnLea> MCR1; in this case that is ok
[10:24] <MCR1> JohnLea: so no change ?
[10:25] <JohnLea> MCR1; yes to change, in this case it is ok to change the gnome shortcut so that Ctrl Alt Del brings up the Processes tab of System Monitor
[10:26] <MCR1> JohnLea: Ok, acknowledged. I yet have to find where this is hardcoded to fix it though... Last question:
[10:27] <MCR1> JohnLea: What about the additional shortcut to toggle a selected window between fullscreen/un-fullscreen
[10:27] <MCR1> JohnLea: It is Alt+Enter on most windows versions
[10:27] <MCR1> JohnLea: This is Fullscreen, not maximize
[10:28] <MCR1> JohnLea: Very useful - for media players for example, but it will also fullsceen/unfullscreen any other window
[10:28] <luv> umm, making methods nonvirtual ... premature optimizatio?
[10:29] <JohnLea> MCR1: At the moment it is usually F11, see VLC, Chrome, Firefox, etc...
[10:29] <MCR1> JohnLea: Often it is F11, in apps like chromium -> then it will do the same like standard
[10:29] <MCR1> JohnLea: Yep
[10:29] <JohnLea> MCR1; this is also a windows shortcut as well
[10:29] <MCR1> JohnLea: but media players won't work with F11...
[10:30] <MCR1> JohnLea: Well, it is not that important, but we do currently have NO! shortcut for Fullscreening/Unfullscreening in Ubuntu
[10:30] <MCR1> JohnLea: and it would be nice to have, I would say...
[10:31] <JohnLea> MCR1; We can add Alt+Enter as long as it does not affect the existing F11 behaviour (which I suppose it shouldn't)
[10:31] <MCR1> JohnLea: It won't. It is tested. I got it running here since ages.
[10:31] <MCR1> JohnLea: The only problem we have, we already have in trunk
[10:32] <JohnLea> MCR1; cool, can you ping me a bug # with *just* that change for me to ok?
[10:32] <MCR1> JohnLea: It is the possibility to invoke the HUD while fullscreened
[10:32] <MCR1> JohnLea: To reproduce: Hit F11 in Chromium and then Alt to invoke the HUD
[10:33] <MCR1> JohnLea: It will come up (the hud) but will be invisible and block F11
[10:33] <MCR1> JohnLea: So this should be fixed to avoid confusion
[10:33] <MCR1> JohnLea: I propose to forbid the HUD for fullscreened apps
[10:33] <JohnLea> MCR1; there are a bunch of other bugs with full screen mode at the moment, for example you can't reveal the Launcher by pushing against the left edge in full screen mode
[10:33] <MCR1> JohnLea: but this is a design question
[10:34] <MCR1> JohnLea: Also design question
[10:34] <MCR1> JohnLea: What should be possible in Fullscreen mode ?
[10:35] <JohnLea> It should be possible to:
[10:35] <JohnLea> - reveal a auto-hidden launcher
[10:35] <JohnLea> - use Alt-Tab
[10:35] <JohnLea> - open the Dash
[10:35] <JohnLea> - open the Hud
[10:36] <JohnLea> etc...
[10:36] <JohnLea> basically all of these things are broken now
[10:36] <MCR1> urgh, - okay -> gotta think about that one first...
[10:36] <MCR1> could be complicated to solve, because of various reasons
[10:37] <JohnLea> yup, full screen mode is really broken atm
[10:37] <MCR1> JohnLea: I will prepare the bug for you, regarding Alt+Enter Solo
[10:37] <JohnLea> cool, thx!
[10:37] <MCR1> JohnLea: might take a while, do not hold your breath
[10:39] <MCR1> JohnLea: Thanx a lot 4 your time.
[10:51] <MCR1> seb128: Hi :) I bet you know which package I have to manipulate to get rid of the hardcoded Ctrl+Alt+Del gnome shortcut to log out the user... Could you tell me ?
[10:51] <sil2100> hah, I actually see how to easily fix this now
[10:52]  * sil2100 talks about the switcher tests to himself
[10:52] <sil2100> Don't mind me
[10:52] <MCR1> hehe
[10:52] <seb128> MCR1, is it hardcoded? I'm unsure, try gnome-settings-daemon or gnome-session...
[10:53] <MCR1> seb128: I did not find it in the settings-daemon, I'll try gnome-session... thanks
[10:54] <MCR1> sil2100: Btw, do not hate me - but my implementation needs a packaging change :-[
[10:54] <MCR1> sil2100: Forget it, just the fullscreen stuff needs it...
[10:55] <seb128> MCR1, gnome-settings-daemon/plugins/media-keys/gsd-media-keys-manager.c
[10:56] <seb128>         case LOGOUT_KEY:
[10:56] <seb128>                 do_logout_action (manager);
[10:56] <seb128>                 break;
[10:56] <MCR1> seb128: oh great - that is a big help - I must have missed it :)
[10:56] <seb128> MCR1, isn't what you are looking for?
[10:56] <sil2100> ;)
[10:56] <MCR1> seb128: well, not exactly -> I am searching for the definition of LOGOUT_KEY
[10:57] <seb128> it's in plugins/media-keys/shortcuts-list.h
[10:57] <seb128>         { LOGOUT_KEY, "logout", NULL },
[10:57] <MCR1> seb128: Top. Thanks. Should be Ctrl+Alt+Del somewhere...
[10:58] <seb128> MCR1, gsettings: org.gnome.settings-daemon.plugins.media-keys logout '<Control><Alt>Delete'
[10:59] <MCR1> seb128: Last question: Where exactly is this defined, what source file writes this gsettings key ?
[11:00] <seb128> MCR1, the schemas/default value is in g-s-d: data/org.gnome.settings-daemon.plugins.media-keys.gschema.xml.in.in
[11:01] <seb128> MCR1, gnome-control-center allows you to rebind it in its keybinding ui afaik, otherwise not sure if anything writes it
[11:01] <MCR1> seb128: I am sorry for nerving, P E R F E C T ! ! !
[11:01] <MCR1> seb128: Without you this would have taken me hours to find out...
[11:01] <seb128> MCR1, no worry, glad that I was able to help you, happy hacking ;-)
[11:01] <MCR1> thx
[11:12] <sil2100> Could anyone test and review https://code.launchpad.net/~sil2100/unity/autopilot_fix_switcher_again/+merge/145578 with latest trunk?
[11:12] <sil2100> If it also fixes switcher tests for them
[11:17] <sil2100> seb128: looking into the failing tests, interesting
[11:17] <seb128> sil2100, hum, for some definition of interesting right? ;-)
[11:24] <MCR1> seb128: I now know how to perfectly fix bug 890747 without messing with gnome itself. I will upgrade the Compiz Gnome Compatibility plug-in to also deal with other gnome shortcuts (currently it just deals with showMainMenu, showRunDialog, CommandScreenshot, CommandWindowScreenshot and CommandTerminal)
[11:25] <seb128> MCR1, great!
[11:25] <MCR1> 50% of credit goes to you, seb128 ;)
[11:27] <MCR1> My fix will also have the positive side-effect that all will be perfectly configurable CCSM style, so you will be easily able to modify everything to your needs if it won't suit you...
[11:27] <MCR1> Unfortunately (once again) I will have to deal with Ubuntu Compiz patches :P
[11:28] <MCR1> smspillaz: New plan by MCR: Upgrading the Gnome Compatibility Plugin ! :)
[11:33] <rye> luv: are the changes only in launcher/ApplicationLauncherIcon.{h,cpp} ?
[11:33]  * rye is building
[11:35] <luv> yup
[11:36] <rye> luv: can't wait to see it built then :)
[11:39] <luv> well, fingers crossed :-)
[12:06] <smspillaz> MCR1: cool, I guess
[12:08] <MCR1> smspillaz: I guess (hope) too, that it will be cool ;)
[12:09] <MCR1> smspillaz: it will enhance compatibility with gnome, while upgrading customization possibility and helping us fix the Ctrl+Alt+Del issue...
[12:10] <MCR1> smspillaz: but I will keep the first upgrade simple and just add the logout command...
[12:21] <rye> luv: ok, built and it added the menu! However, in case there are more than one window with the same title it would show one entry and focus the first one. Should there be separators before window list? Where should the list be located - under quit or somewhere in between
[12:22] <rye> luv: but this is maaaajor usability improvement for me :)
[12:22] <luv> thanks .. right regarding the seperator:  http://killem.al/windowlist.ogv <- this is how it should work
[12:24] <luv> regarding the problem with one entry for more windows with same title - right, it handles it in ubuntu 12.04, so I will need to fix the patch against raring
[12:24] <luv> it really sucks, I can't get VBox guest additions running in raring so it's a nightmare using it
[12:25] <luv> though, I'm happy it builds fine and mostly works! Could you make a screenshot of how the seperator is placed on raring - it'd be interested to see that.
[12:25] <rye> luv: aha, in raring the window list is below all the other entries
[12:26] <luv> well, if i had a fully working (virtual) box running raring, it'd be a matter of an hour getting all these details sorted out :-/
[12:27] <rye> luv: at what point does vbox fail?
[12:28] <luv> well there are two problems 1) can't compile unity because of g++ segfault (not vbox related), 2) the vbox - well - i can't install guest additions (tried both, the script coming with VBox and the packages in raring repo) - I am not sure why it doesn't install properly - I should investigate that.
[12:29] <rye> luv: http://ubuntuone.com/5xzEdYJLFLcjntYP72siJ7
[12:29] <rye> luv: are you compiling unity inside vbox and get the segfault?
[12:30] <luv> yes, but somehow i don't think it is vbox related
[12:30]  * rye installs vbox, why not
[12:30] <luv> it's not that hard to get g++ segfault with c+11 even on bare metal
[12:30] <luv> oh, i dont think you have to investigate there ...  i believe the segfault was caused by me not using latest trunk
[12:31] <luv> i used a week trunk out of convenience (I just ran apt-src install in raring)
[12:31] <rye> luv: well, i built stuff for quantal/raring/precise in vm under kvm and so far i had no failures of the compiler, so it is a bit strange
[12:32] <rye> luv: well, i have a unity-team/staging ppa where I get trunk versions packaged and i just do dpkg-buildpackage to get the debs
[12:33] <rye> luv: are you using amd64 or i386 image?
[12:33] <luv> it'd be interesting if you could reproduce that segfault indeed ... it's amd64
[12:34] <luv> could i just add unity-team/staging ppa to my raring install and use apt-src install and get latest trunk unity?
[12:34]  * rye zsync the fresh iso
[12:34] <rye> luv: yup, it will be re-built on every commit in compiz/unity/nux
[12:35] <luv> very good
[12:44] <luv> yeah, here is an example g++ segfault
[12:44] <luv> http://pastebin.blesmrt.net/2881/
[12:44] <luv> g++ -std=gnu++0x c11segfault.cpp -o c11segfault
[12:44] <luv> segfaults on g++ in ubuntu 12.04 atleast
[12:53] <rye> luv: ok, that code does segfault on 12.04 but works on raring
[12:59] <luv> yeah, just tested w/ colleague and it is indeed fixed in gcc-4.7
[13:08] <sil2100> https://code.launchpad.net/~sil2100/unity/autopilot_fix_switcher_again/+merge/145578 <- can anyone review and approve? Since we need this reviewed and in to fix the daily builds of unity
[13:14] <sil2100> mterry: ^
[13:14] <sil2100> fginther: ^
[13:14] <bregma> sil2100, just approved it for you
[13:15] <sil2100> bregma: thanks :)
[13:15] <bregma> least I could do, given I caused all the trouble
[14:05] <rye> aha, vbox guest additions cannot be compiled now
[14:08] <luv> oh, good to get that confirmed, i will try to install raring on a usb drive when i get home
[14:15] <rye> vboxvideo module cannot be loaded because it cannot be built
[14:33] <Squarism> WHYY has ubuntu-unity per default occupied the majoryty of all CTRL/ALT/SHIFT + common keys. Do unity developers understand we use their window manager to run "application" that usually rely on keyboard shortcuts?!
[14:37] <fginther> seb128, I'm looking at the indicators test failure, looks like a setup issue
[14:38] <seb128> fginther, thanks for looking at it
[14:43] <fginther> sil2100, do I need to do anything special to rerun the ps-indicators-autopilot-release-testing job?
[14:50] <sil2100> fginther: huh
[14:50] <sil2100> fginther: not sure, I usually just re-ran it through jenkins
[14:50] <sil2100> But hm, I did so today and it resulted in a failure ;/
[14:51] <fginther> sil2100, that's all I wanted to know, just in case I should start some other job
[14:51] <fginther> sil2100, the failure may be due to a recent utah update, that's why I'm rerunning :-)
[14:52] <sil2100> ;( ;) Thanks!
[15:33] <Squarism> Stop hogging all damn hotkeys.. most IDE's are unusable on unity with factory settings
[15:34] <Squarism> i mean please... in particular stop using combinations of ctrl+alt+shift - theres a win/mac key that can be used for OS specific things
[15:35] <rye> Squarism: what ctrl+alt+shift keys are grabbed?
[15:36] <Squarism> CTRL+ALT arrow keys for example
[15:37] <rye> Squarism: well, that's been used to switch desktops for ages (as far as I remember, in gnome since 2006), ctrl+alt+shift+arrows - to move window to another workspace
[15:37] <sil2100> I remember ctrl+alt+arrows in Ubuntu since a long time, never had any problems with it myself, I always thought metacity used this keycombination by default as well
[15:37] <rye> Squarism: in raring by default there will be only one workspace
[15:38] <Squarism> Well, that could be - but linux/ubuntu desktop was a "enthusiast" OS in those days
[15:39] <Squarism> To gain market i would focus on catering to people who can develop the OS. Like i use Intellij - most popular ide for worlds most popular language
[15:39] <Squarism> and its hell
[15:39] <Squarism> ...ie cater to developers of all sorts
[15:40] <sil2100> It's hard to have everyone satisfied, sadly
[15:41] <rye> Squarism: well, what actions are triggered by ctrl+alt+shift+up/down/left/right (I tried to search but can't really find anything)
[15:41] <rye> aha
[15:41] <rye> Squarism: forward/back
[15:41] <Squarism> i really wanna use linux but when i need to reassign all damn keys its problematic... biggest problem though is that some "Super" keys arent modifiable (wo CCSM)... like CTRL+Super + Left/Right
[15:42] <Squarism> CTRL+ALT left/right is back/forward in intellij
[15:42] <Squarism> if i could reassign window swithcing to ctrl + super + arrows it would be dandy.. but that is non modifiable
[15:43] <Squarism> "CTRL+ALT left/right is back/forward in intellij" -> rye
[15:43] <fginther> sil2100, https://code.launchpad.net/~sil2100/unity/autopilot_fix_switcher_again/+merge/145578 is merged
[15:44] <popey> Squarism: reduce the number of desktops to 1 and then those key combinations will do nothing in Unity
[15:44] <Squarism> also ALT+F7 and CTRL+ALT+F7 seems occupied by unity
[15:44] <rye> Squarism: System Settings / Keyboard / Navigation has the Ctrl+Alt shortcuts
[15:45] <popey> also, when you say "most IDEs" you mean, one specific IDE?
[15:45] <Squarism> rye, i know.. but i cant ressagin them to Super combinations as many of them are unassignable
[15:45] <Squarism> well i i know eclipse is shortcut heavy to.
[15:47] <sil2100> fginther: yay! Thanks!
[15:47] <rye> erm, ctrl+super+down does not appear to work for restoring window
[15:47] <Squarism> I like unity as a whole.. and dont want anything else then flee from windows... but with unecessary hurdles like these i get a bit irritated
[15:48] <Squarism> rye: and ctrl+super + left/right arent modifieable
[15:48] <rye> Squarism: that is a good point
[15:48] <MCR1> Squarism: There are a few key-combinations left, which are not configurable/hardcoded. We are working on fixing those as well.
[15:49] <Squarism> MCR1, thanx - id really appreciate that!
[15:49] <rye> MCR1: there is ccsm config for ctrl+super left/right
[15:50] <Squarism> i read everywhere that CCSM isnt supported (ie can crash your desktop).
[15:50] <MCR1> bug 1017539
[15:50] <MCR1> bug 1022743
[15:50] <MCR1> ^^ this one is partially fixed, but not fully yet
[15:51] <dednick> Squarism: unfortunately there are always going to be conflicts with key-bindings, we can only do so much without making crazyily complicated ones. Do you use multiple workspaces? Or can you change the bindings in intellij?
[15:51] <MCR1> Squarism: Unfortunately CCSM is not installed by default - yes...
[15:52] <MCR1> Squarism: *maybe* this will change again as stability has improved a lot lately
[15:52] <Squarism> dednick, i use multiple workspaces. One of the reasons i like unity/ubuntu
[15:53] <rye> Squarism: CCSM is simply modifying the options that later read by compiz plugins (and unityshell as a plugin) and I personally rendered my unity session unusable several times with ccsm (or at other times got compiz to crash). But the config is stored in ~/.config/dconf/user and i usually reverted to removing that and relogin. OTOH I am running a bleeding edge version of ubuntu/unity
[15:53] <rye> which reminds me I wanted to crash compiz and report that
[15:54] <MCR1> hehe
[15:54] <dednick> hmm. suspend menu button looked suspiciously like the system settings menu. Think i need sleep.
[15:55] <Squarism> dednick, And as intellij is what I work with all days regardless of OS (sometimes on collegues machines, sometimes on client computer) - i prefer to use factory settings there
[15:57] <dednick> Squarism: Super+Ctrl+left/right work ok for me.
[15:57] <Squarism> dednick, to reassign?
[15:57] <rye> MCR1: by hardcoded shortcuts - do you mean that they are hardcoded in the code or that they are exposed via CCSM only?
[15:57] <Squarism> ...wo CCSM?
[15:58] <dednick> i just assigned it in the keyboard shortcuts section of system settings
[15:58] <dednick> oh wait...
[15:59] <dednick> no, i was right. it is working. I just assigned it to the move window to left/right workspace. But the same works for switch to left/right
[15:59] <dednick> Squarism: ^
[16:00] <MCR1> rye: unfortunately hardcoded in the code
[16:01] <Squarism> dednick, hmm.. on 12.04 it doesnt work (tested right now) and at home i run 12.10 and there its not listed (in shortcut settings)  atleast
[16:01] <dednick> Squarism: I'm on 12.10. You on latest updates?
[16:02] <Squarism> i installed it 2 weeks ago
[16:02] <Squarism> filed a bug on launchpad about then also
[16:02] <dednick> Squarism: system settings -> keyboard -> shortcuts -> navigation . Not there?
[16:03] <Squarism> dednick, no.. Exactly
[16:04] <Squarism> "Semi-maximizes window" or whatever its called
[16:04] <Squarism> dednick, you have such a setting?
[16:06] <dednick> Squarism: er, no. that sounds like something to do with an on-screen keyboard.
[16:07] <Squarism> "Semi maximize" = maximize to occupy half-right or half-right screen
[16:09] <dednick> Squarism: http://ubuntuone.com/40X7ZumcAvJk9IUD4EdDId
[16:12] <Squarism> dednick, sure - i can do that too.. but the default function "semi-maximize" is left on too / conflicts .. and it seems it has precedance
[16:15] <dednick> Squarism: i see. Use Super + Alt then? :)
[16:17] <fginther> sil2100, now that your switcher branch has landed, should we restart the daily testing?
[16:18] <Squarism> can one get involved in unity in some way?
[16:18] <Squarism> ie to release a patch on a released verison so to speak
[16:19] <sil2100> fginther: yes, let's do that :)
[16:19]  * sil2100 almost got the ibus tests fixed
[16:19] <sil2100> Almost
[16:20] <sil2100> I need to prepare something packaging related to dee now
[16:20] <fginther> sil2100, ok
[16:21] <Squarism> would appriciate a lead on where to start - ie fixing issues in unity
[16:21] <sil2100> Squarism: yes, contributions are most welcome :)
[16:21] <sil2100> Ok, so - which version of Ubuntu are you running?
[16:22] <dednick> Squarism: I'll point you at the standard website. I'm not sure about the process for community contributions (but I'm sure there is one). http://unity.ubuntu.com/getinvolved/
[16:22] <Squarism> sil2100, 12.04 and 12.10
[16:24] <Squarism> I presented a choice here http://unity.ubuntu.com/getinvolved/development/
[16:25] <Squarism> is shortcut stuff in unity, common components or common libraries
[16:25] <sil2100> Squarism: the shortcut mechanism is in compiz, but Unity shortcut definitions are in the unity source code
[16:26] <sil2100> Squarism: although some of the shortcuts you mentioned are not related to Unity but to other compiz plugins
[16:26] <Squarism> oh ok
[16:27] <sil2100> Squarism: but everything you need is defined in the bazaar branches of lp:unity and lp:compiz
[16:27] <sil2100> But those repositories have the latest changes for the upcoming release 13.04
[16:27] <sil2100> (bleeding edge)
[16:27] <Squarism> oh.. hot!
[16:28] <sil2100> 12.10 branches are in lp:unity/6.0 and lp:compiz/0.9.8
[16:28] <sil2100> But the rule is that we prefer patches first being sent to trunk (bleeding edge) and then back-ported to the earlier releases
[16:29] <Squarism> taking notes!
[16:30] <Squarism> how does the typical unity developer work? I mean.. if u develop.. how do you view/test your changes?
[16:31] <sil2100> Squarism: it's maybe a *bit* complicated, but well, the code is rather well readable
[16:31] <sil2100> hmmm
[16:31] <sil2100> I usually build packages from source and test them on my system
[16:32] <MCR1> Squarism: Right now there is Ubuntu Developer Week on the #ubuntu-classroom channel
[16:32] <MCR1> Squarism: http://ubuntuclassroom.wordpress.com/2013/01/30/ubuntu-developer-week-day-1-is-over-whats-up-on-day-2/
[16:32] <Squarism> Will that require a reboot for every test then?
[16:32] <sil2100> Squarism: it depends on developers - some prefer building packages directly from trunk and installing by make install, but I always prefer building a test package by using bzr builddeb and then testing
[16:32] <sil2100> Since I can easily revert to an earlier version
[16:33] <sil2100> Squarism: nooo, you just need to restart compiz/unity
[16:33] <dednick> Squarism: smaller changes can be tested on standalone unity components (eg dash or launcher standalone apps). But with things that need system-wide integration like shortcuts, we have dev staging sets which use to test.
[16:33] <sil2100> Squarism: it's usually a unity --replace call
[16:34] <sil2100> We're welcome to all new, precious contributors
[16:34] <Squarism> I do alot of programming in my free time so why not
[16:35] <dednick> Squarism: http://unity.ubuntu.com/getinvolved/development/unity/ gives instruction on how to build a staging set. But it "may" be a bit out of date.
[16:35] <Squarism> will need to get a working process up first though
[16:36] <Squarism> Thanx guys!
[16:36] <Squarism> Will try to bite my teeth into this when my current project is done.. (week or two)
[16:41] <rperier> sil2100: What do you think about bug https://bugs.launchpad.net/unity/+bug/1108956 ? I meant, finally this is a real bug or not I am confused
[16:46] <rperier> (otherwise I will work on another bug, np)
[16:47] <MCR1> rperier: IMHO the problem here is that Super is used to open/close the Dash primarily and Dash Home does not have a specific shortcut like the other lenses...
[16:51] <rperier> MCR1: this is not a shortcuts problems, but a problem about the switch, the transition
[16:52] <rperier> is it acceptable to have the dash closed when pressing "super" from the command lens ?
[16:52] <rperier> if yes, np this is not a bug and it can be closed :)
[16:54] <MCR1> If you change the behaviour the bug would be: Super does not close the Dash when Command Lens is opened
[16:55] <MCR1> but I noticed that pressing Alt+F2 again it does not close, which it imho should...
[17:03] <MCR1> rperier: But I confirmed the other related bug Dash->Command Lens, which you already fixed. And I can confirm your fix as well. Top job !
[17:06] <rperier> MCR1: you're confusing me :D
[17:08] <rperier> the code fix is valid, and not the bug ?
[17:08]  * rperier needs a coffee
[17:10] <MCR1> rperier: imho you should think about implementing a toggle function for Alt+F2 first, otherwise you will not be able to directly close the command lens
[17:10] <rperier> ah !
[17:11] <rperier> I see
[17:11] <MCR1> rperier: as Alt+F2 does not close the command lens at the moment (which imho is a bug)
[17:12] <MCR1> with your solution (which is nice) you would always HAVE to switch from command to home before being able to fully close everything with keys...
[17:12] <rperier> MCR1: it works here, I meant If I press ALT+F2 it opens the command lens, if I press ALF+F2 a second time, it closes it
[17:13] <rperier> mhhh... I see
[17:13] <MCR1> raring, latest trunk ?
[17:13] <rperier> raring from mirrors
[17:13] <MCR1> does not close here
[17:14] <rperier> okay so I need to add a toogle function for ALT+F2 (I agree now) and then my bug might be acceptable ?
[17:15] <rperier> the correct solution would be:   switch from home.lens to command.lens , switch from command.lens to home.lens (both without closing the dash)  + toogle function for ALT+F2 ?
[17:16] <rperier> ideally
[17:16] <MCR1> I am just a community member adding his 2 cents -> you got to assign the bug to Ayatana Design and set it to incomplete
[17:16] <rperier> ok :)
[17:44] <sil2100> rperier: hi! Yes, I agree with MCR1 that it's best to poke design about this ;)
[17:45] <sil2100> rperier: you can also try quickly poking JohnLea when he's around, usually a bit earlier
[17:45] <sil2100> Since this seems like a small issue that can be commented on real quickly
[17:48] <sil2100> fginther: hm, strangeness - the ps-indicators-autopilot-release-testing finished, but only ati tests ran for build 98
[17:48] <sil2100> fginther: why do things like that happen?
[17:48] <sil2100> I see you started job 99, hope we have more luck with that
[18:03] <fginther> sil2100, there was a hang in the intel and nvidia so it was restarted
[18:03] <fginther> sil2100,  there was a machine resource issue which I'm told is now resolved :-)
[18:04] <sil2100> uuuu ;) Great to know, thanks!
[18:56] <cwayne> mhall119: when is the switch to that new api?
[19:00] <mhall119> cwayne: for scopes?
[19:00] <cwayne> mhall119: yar
[19:01] <mhall119> cwayne: nope, but soon
[19:03] <mterry> Yay for the unity stack passing again
[19:03]  * mterry looks at the dbus-test-runner failing because of g_type_init
[19:03] <mterry> ah, tedg already merged that
[19:12] <mterry> fginther, hello!  So about crashes that happen during autopilot tests, that cause the remainder of the tests not to be run.  Can we change the jenkins logic to fail the build if autopilot or X crashes or some such?
[19:13] <fginther> mterry, yes, I think veebers was looking into implementing that
[19:13] <fginther> mterry, we discussed it yesterday
[19:13] <mterry> fginther, awesome, OK
[19:15] <luv> oh, I see my merged got merged into lp:unity even though it's not working properly yet ;-)
[19:15] <luv> s/merged/branch/
[19:16] <luv> well, at least I have motivation to polish it out tonight :-)
[19:17] <mterry> bregma, a couple focus test failures: http://<IP_ADDRESS>:8080/job/ps-indicators-autopilot-release-testing/label=autopilot-ati/lastCompletedBuild/testReport/
[19:18]  * bregma give a quick glance
[19:21]  * bregma suspects https://code.launchpad.net/~sil2100/unity/autopilot_enhance_test_hud/+merge/145595
[19:26] <mterry> bregma, how would that fix the failures?  That just adds a new assert
[19:37] <fginther> mterry, just a theory, but the assert will wait 10 seconds for it to become true, that might be enough to fix the test if it's timing related
[19:38] <fginther> mterry, in this case, the test may be failing because the application window is not ready. the assert sil2100 added will fix that
[19:39] <mterry> fginther, hrm.  OK.  We'll see if it helps
[20:05] <luv> I see, it's just a proposal, missed that in the email. I was a bit scared that code would make it through.
[20:08] <mterry> fginther, could jenkins have some -dbg packages installed when running?  That way, when apport creates a .crash file, it would have symbols built-in
[20:09] <mterry> fginther, bryce can't get a good stack out of the Xorg crash
[20:10] <fginther> mterry, if we know the list of packages, we can add it
[20:10] <fginther> mterry, is that something that would normally be handled by apport-retrace?
[20:12] <mterry> fginther, yeah I guess.  But apport can do it upfront if dbg symbols are already around
[20:13] <mterry> fginther, we'd want at least xserver-xorg-core-dbg.  Asking bryce if there are other useful ones
[20:22] <luv> Trevinho: hi, im just reading your review, thanks for the comments. I dont fully understand the comment " At that point call it into GetMenus() putting the items you computed into the result list." under line 22
[20:23] <luv> also, does it really matter if I use "for (auto const& w : Windows())" instead of 'for ( auto w: Windows() ) {" ... Window is just a 64bit integer anyway
[20:24] <luv> i am happy to change so it follows the project's way, indeed
[20:24] <mterry> fginther, can we start with at least: libdconf-dbg libdconf-dbus-1-dbg xserver-xorg-core-dbg
[20:24] <mterry> fginther, those seem to be related to the two crash files we have now
[20:27] <fginther> mterry, got it
[20:51] <Trevinho> luv: no, Windows() a list of WindowPtr... Yeah, copying a shared_ptr is not that much, but if we can save it it's better
[20:52] <Trevinho> luv: I mean, you should add a call into GetMenus() to ensure that you build your _window_menus_items, then you merge these with the results... But it's better if you do that into GetMenus
[20:56] <mterry> fginther, also libdrm2-dbg libgl1-mesa-dri-dbg  libgl1-mesa-glx-dbg
[20:57] <mterry> fginther, is it also possible to have jenkins run ubuntu-bug --save=PATH and upload PATH too (for logs and stuff when it crashes)
[20:57] <mterry> fginther, it can be run on a .crash file
[20:57] <fginther> veebers, ^^
[20:58] <veebers> mterry, fginther yep I can add that too
[20:59] <fginther> mterry, we were seeing apport-retrace crash on the test machines
[21:00] <fginther> mterry, which is causing the unprocessed crashes, hopefully these other steps will work