[02:53] <Edir456> I am following this guide: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/ but the link under 'kernel patches' doesn't work
[02:53] <Edir456> Does anyone know where I can find these now?
[03:06] <Edir456> Hello?
[03:13] <Edir456> Nevrmind then...
[14:00] <mimecar> Good afternoon...
[22:04] <ilhami> hey
[22:04] <ilhami> when will we see more improvements in Ubuntu Touch?
[22:06] <ilhami> it looks really laggy.
[22:07] <ilhami> and unpolished
[22:25] <ljp> things will probably start cranking up again after year end holidays
[22:31] <ilhami> hmm okay.
[22:31] <ilhami> what holidays exactly?
[22:47] <dobey> ilhami: if you have specific bugs, then file them. generalized statements like "it looks really laggy and unpolished" aren't at all helpful.
[22:47] <dobey> and it's not really laggy at all for me
[22:48] <dobey> k1l_: ?
[22:48] <k1l_> that is a known troll. was again banned in #ubuntu now and is banned on other channnels, too
[22:49] <dobey> oh ok
[23:03] <Vincenttttt> does anyone know if the acer liquid e700 (android phone) is compatible for ubuntu touch?
[23:08] <dobey> !devices | Vincenttttt


[01:17] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [18.2-4-g05926e48-0ubuntu1~16.04.2]
[01:21] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (artful-proposed) [18.2-4-g05926e48-0ubuntu1~17.10.2]
[02:44] <tsimonq2> infinity: That email I told you I'd write is now in the ubuntu-release queue.
[02:44] <tsimonq2> Just needs someone to approve it.
[02:55] <tsimonq2> infinity: Also: https://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu/commit/?id=00228d62db78d902b17486a3dc1ff24f50635c4b
[03:15] <tsimonq2> infinity: As far as I can tell, livecd-rootfs needs changes to drop no-follow-recommends for Lubuntu (export APT_OPTIONS="--yes --no-install-recommends") and proper revertion of https://code.launchpad.net/~tsimonq2/livecd-rootfs/lubuntu-seed-mangling/+merge/342064 , and ubuntu-cdimage needs changes to germination so that lubuntu-next isn't germinated for Cosmic. I'm not sure what needs to stay
[03:15] <tsimonq2> and what can just be paved over.  :D
[06:39] <cpaelzer> umm, seing cosmic in the archive as name but haven't seen a mail yet - can we already upload to cosmic already?
[06:55] <apw> cpaelzer, it is very nascient as yet ...
[06:56] <cpaelzer> ok, then I'll give it a few days more to bloom :-)
[06:56]  * cpaelzer goes on tagging bugs/mails that need C to be fully open
[06:56] <cpaelzer> thanks
[07:42] -queuebot:#ubuntu-release- Unapproved: gnome-session (bionic-proposed/main) [3.28.1-0ubuntu2 => 3.28.1-0ubuntu3] (ubuntu-desktop)
[08:55] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (bionic-proposed) [2.42+18.04.2]
[09:28] -queuebot:#ubuntu-release- Unapproved: pulseaudio (xenial-proposed/main) [1:8.0-0ubuntu3.9 => 1:8.0-0ubuntu3.10] (core)
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (xenial-proposed) [1:8.0-0ubuntu3.10]
[09:33] -queuebot:#ubuntu-release- Unapproved: dput (cosmic-proposed/main) [1.0.1ubuntu1 => 1.0.2ubuntu1] (core)
[10:51] <acheronuk> sil2100: FYI I will be hoping to do this tomorrow: LP: #1687444
[10:52] <acheronuk> umm that is an old one. 2 secs
[10:52] <acheronuk> I meant LP: #1768245
[10:53] <acheronuk> currently doing some preliminary tests with ppa builds
[10:58] <sil2100> acheronuk: ok, thanks for the heads up!
[10:58] <sil2100> acheronuk: there's a national holiday tomorrow but I should be around for a quick SRU round
[10:59] <acheronuk> sil2100: any particular time of day you are likely to be doing that? no worries if you can't say
[11:00] <juliank> acheronuk: https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/344951
[11:00] <juliank> um
[11:00] <juliank> Laney: : https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/344951
[11:00] <acheronuk> :/
[11:00] <juliank> sorry
[11:00] <acheronuk> ah. np
[11:00] <Laney> acheronuk can review if he wants :-)
[11:00] <juliank> sil2100: https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/344951
[11:01]  * acheronuk shoves it back. no thanks :P
[11:01] <juliank> slangasek: copy log.gz https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/344951
[11:01] <juliank> it's running right now
[11:01] <juliank> :-)
[11:09] <LocutusOfBorg> please accept virtualbox-ext-pack and boinc?
[11:44] <Laney> http://autopkgtest.ubuntu.com/packages/gzip/cosmic/amd64
[11:44] <Laney> now there's no place to hide
[11:45] <Laney> 👮
[11:45] <slangasek> juliank, Laney, sil2100: woot on the log copy
[11:46] <juliank> it's at ruby-acts-* now
[11:48] <juliank> Error connecting to swift, re-connecting in 0s: Object PUT failed: http://<IP_ADDRESS>:8080:8080/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/r/ruby-asciidoctor-plantuml/20180326_095824_aa07a%40/log.gz 401 Unauthorized  [first 60 chars of response]
Unauthorized

This server could not verify t
[11:48] <juliank> Error connecting to swift, re-connecting in 5s: 'NoneType' object has no attribute 'find'
[11:48] <xnox> Laney, awwww
[11:50] <juliank> So sometimes copying errors out with 401
[11:50] <juliank> restarting it makes the copy works
[11:50] <juliank> but the file is now 401
[11:51] <juliank> now it's fine
[11:51] <juliank> hmm
[11:53] <juliank> we gotta make the retry more robust I guess
[12:07] <tsimonq2> xnox: ubiquity> <3
[12:07] <tsimonq2> What else can be converted? :D
[12:08] <xnox> tsimonq2, debian-installer maybe? but i'm not sure what infinity / apw / etc think about doing that.
[12:08] <xnox> to git, or not to git?
[12:08] <tsimonq2> Always git. :D
[12:11] <infinity> xnox: Leave d-i.
[12:21] <tsimonq2> infinity: What about architectural things like lp:u-cdimage or lp:u-a-publishing or lp:livecd-rootfs?
[12:25] <infinity> tsimonq2: I might be slightly busy with other things.
[12:26] <cjwatson> I imagine I'll do u-a-publishing once LP itself is done
[12:27] <tsimonq2> cjwatson: Ooh.
[12:28] <tsimonq2> When is that expected (ish)?
[12:28] <cjwatson> Not quite sure yet, but we cleared a substantial blocker today.
[12:28] <cjwatson> (A complicated buildbot upgrade that had to happen first)
[12:28] <tsimonq2> Nice.
[12:38] -queuebot:#ubuntu-release- Unapproved: base-files (cosmic-proposed/main) [10.1ubuntu2 => 10.1ubuntu3] (core)
[12:38] -queuebot:#ubuntu-release- Unapproved: vim (cosmic-proposed/main) [2:8.0.1453-1ubuntu1 => 2:8.0.1453-1ubuntu2] (core)
[12:38] -queuebot:#ubuntu-release- Unapproved: distro-info-data (cosmic-proposed/main) [0.37 => 0.37ubuntu1] (core)
[12:39] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (cosmic-proposed) [10.1ubuntu3]
[12:39] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (cosmic-proposed) [0.37ubuntu1]
[12:42] <slangasek> xnox: is there a good reason that ~ubuntu-core-dev is not a member of ~ubuntu-installer?
[12:43] <cjwatson> Historically the reason was because bug subscriptions weren't well-configured so it would be massive bug spam
[12:43] <slangasek> xnox: pre-build hook not ported> ugh so is it at least encapsulated to it can be run by hand?
[12:43] <cjwatson> We should possibly unsubscribe ~ubuntu-installer from various things (notably ubiquity) and rely on individual subscriptions there instead
[12:43] <cjwatson> the pre-build hook is literally just debian/rules update-local
[12:44] <slangasek> ah, k
[12:50] <acheronuk> cjwatson: would copying stuff in a ppa from bionic to cosmic work yet?
[12:50] <acheronuk> ummm. mor a LP question. sorry
[12:50] <infinity> acheronuk: Yes.
[12:51] <acheronuk> *more
[12:51] <acheronuk> :)
[12:52] <acheronuk> just want to get Kubuntu's CI repos set up for cosmic, without having to rebuild the KDE world in that. thanks
[12:54] <cjwatson> for future reference, include-binaries copies work from the instant that the series has a status that isn't Future
[12:55] <cjwatson> copies that require builds might take a bit longer since chroots need to exist
[12:56] -queuebot:#ubuntu-release- Unapproved: debhelper (cosmic-proposed/main) [11.1.6ubuntu1 => 11.2.1ubuntu1] (core)
[13:06] <ogra_> canimal ? i knew we'd be running out of animals one day so we'd need to invent them :P
[13:06] <cjwatson> it's a placeholder
[13:07] <ogra_> indeed :)
[13:07] <ogra_> <- not serious
[13:14] <cwayne> ogra_: we've already had made up animals
[13:14] <apw> cwayne, the other kind of made up, names which we create rather than animals like unicorns
[13:16] <cwayne> apw: fair point
[13:17] <apw> i would expect and LTS+1 to be a mythical creature again, those are fun
[13:17] <xnox> slangasek, yeah, that bug mail; yes ./debian/rules update is what one typically wants to do before upload; as update-local is mostly a safe-guard that yells at you "omg there are newer things in the archive, and this copy is out of date, bail" type of thing.
[13:18] <slangasek> ogra_, cjwatson: I am not looking forward to Ubuntu http://danimals.com/
[13:18] <ogra_> LOL
[13:19] <xnox> slangasek, omg! it's a thing!
[13:21] <ogra_> i love how cosmic-changes sounds like "news from outer space" though :)
[13:22] <jbicha> danimals "may cause momfidence"
[13:25] <slangasek> or projectile momviting
[13:26] -queuebot:#ubuntu-release- Unapproved: binutils (cosmic-proposed/main) [2.30-15ubuntu1 => 2.30-17ubuntu1] (core)
[13:28] -queuebot:#ubuntu-release- Unapproved: accepted binutils [source] (cosmic-proposed) [2.30-17ubuntu1]
[13:38] -queuebot:#ubuntu-release- Unapproved: gcc-7 (cosmic-proposed/main) [7.3.0-16ubuntu3 => 7.3.0-17ubuntu1] (core)
[13:39] -queuebot:#ubuntu-release- Unapproved: accepted gcc-7 [source] (cosmic-proposed) [7.3.0-17ubuntu1]
[14:11] -queuebot:#ubuntu-release- Unapproved: software-properties (bionic-proposed/main) [<IP_ADDRESS>.1 => <IP_ADDRESS>.2] (desktop-core, ubuntu-server)
[14:19] <tsimonq2> Cosmic uploads. \o/
[14:40] <apw> tsimonq2, a very few early toolchain ones... yes
[14:41] <tsimonq2> I'm happy (maybe too much?) regardless. :)
[14:42] <apw> it is cirtainly a welcome move :)
[14:49] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-21.22] (core, kernel)
[14:49] -queuebot:#ubuntu-release- Unapproved: gcc-8 (cosmic-proposed/main) [8-20180414-1ubuntu2 => 8.1.0-1ubuntu1] (core) (sync)
[14:49] -queuebot:#ubuntu-release- Unapproved: accepted gcc-8 [sync] (cosmic-proposed) [8.1.0-1ubuntu1]
[14:50] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-21.22] (core, kernel)
[15:00] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-21.22]
[15:00] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-21.22]
[15:24] -queuebot:#ubuntu-release- Unapproved: accepted debhelper [source] (cosmic-proposed) [11.2.1ubuntu1]
[15:25] -queuebot:#ubuntu-release- Unapproved: accepted dput [source] (cosmic-proposed) [1.0.2ubuntu1]
[15:30] -queuebot:#ubuntu-release- Unapproved: accepted vim [source] (cosmic-proposed) [2:8.0.1453-1ubuntu2]
[15:55] -queuebot:#ubuntu-release- Unapproved: ncurses (cosmic-proposed/main) [6.1-1ubuntu1 => 6.1+20180210-2ubuntu1] (core)
[15:57] -queuebot:#ubuntu-release- Unapproved: accepted ncurses [source] (cosmic-proposed) [6.1+20180210-2ubuntu1]
[16:01] -queuebot:#ubuntu-release- New binary: ncurses [ppc64el] (cosmic-proposed/main) [6.1+20180210-2ubuntu1] (core)
[16:05] <doko> infinity: please can you remove the freeze request?
[16:05] -queuebot:#ubuntu-release- New binary: ncurses [amd64] (cosmic-proposed/main) [6.1+20180210-2ubuntu1] (core)
[16:05] <infinity> doko: The queue freeze or the britney block?
[16:05] -queuebot:#ubuntu-release- New binary: ncurses [i386] (cosmic-proposed/main) [6.1+20180210-2ubuntu1] (core)
[16:06] -queuebot:#ubuntu-release- New: accepted ncurses [amd64] (cosmic-proposed) [6.1+20180210-2ubuntu1]
[16:06] -queuebot:#ubuntu-release- New: accepted ncurses [ppc64el] (cosmic-proposed) [6.1+20180210-2ubuntu1]
[16:06] -queuebot:#ubuntu-release- New: accepted ncurses [i386] (cosmic-proposed) [6.1+20180210-2ubuntu1]
[16:08] -queuebot:#ubuntu-release- New binary: ncurses [arm64] (cosmic-proposed/main) [6.1+20180210-2ubuntu1] (core)
[16:08] -queuebot:#ubuntu-release- New binary: ncurses [armhf] (cosmic-proposed/main) [6.1+20180210-2ubuntu1] (core)
[16:09] -queuebot:#ubuntu-release- New: accepted ncurses [arm64] (cosmic-proposed) [6.1+20180210-2ubuntu1]
[16:09] -queuebot:#ubuntu-release- New: accepted ncurses [armhf] (cosmic-proposed) [6.1+20180210-2ubuntu1]
[16:10] -queuebot:#ubuntu-release- Unapproved: ncurses (cosmic-proposed/main) [6.1-1ubuntu1 => 6.1+20180210-2ubuntu2] (core)
[16:11] -queuebot:#ubuntu-release- Unapproved: accepted ncurses [source] (cosmic-proposed) [6.1+20180210-2ubuntu2]
[16:11]  * infinity goes to find breakfast.
[16:15] -queuebot:#ubuntu-release- New binary: ncurses [s390x] (cosmic-proposed/main) [6.1+20180210-2ubuntu2] (core)
[16:16] -queuebot:#ubuntu-release- New binary: ncurses [ppc64el] (cosmic-proposed/main) [6.1+20180210-2ubuntu2] (core)
[16:16] -queuebot:#ubuntu-release- New: accepted ncurses [ppc64el] (cosmic-proposed) [6.1+20180210-2ubuntu2]
[16:16] -queuebot:#ubuntu-release- New: accepted ncurses [s390x] (cosmic-proposed) [6.1+20180210-2ubuntu2]
[16:17] -queuebot:#ubuntu-release- New binary: ncurses [i386] (cosmic-proposed/main) [6.1+20180210-2ubuntu2] (core)
[16:20] -queuebot:#ubuntu-release- New binary: ncurses [arm64] (cosmic-proposed/main) [6.1+20180210-2ubuntu2] (core)
[16:21] -queuebot:#ubuntu-release- New binary: ncurses [armhf] (cosmic-proposed/main) [6.1+20180210-2ubuntu2] (core)
[16:24] -queuebot:#ubuntu-release- New binary: ncurses [amd64] (cosmic-proposed/main) [6.1+20180210-2ubuntu2] (core)
[16:34] <tsimonq2> If I wanted to put stuff in the cosmic queue to be approved when and only when the archive has opened, is that fine?
[16:36] <tsimonq2> (I just have some force syncs to do.)
[16:57] <LocutusOfBorg> tsimonq2, for one or two weeks, everything will require additional work for RT
[16:58] <LocutusOfBorg> better write them on a paper and wait for the archive to open for devs, so nobody will be hurt by force-syncs
[16:59] <tsimonq2> OK
[17:15] -queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (bionic-proposed/main) [3.28.0-2ubuntu6 => 3.28.0-2ubuntu6.1] (ubuntugnome)
[17:16] -queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (cosmic-proposed/main) [3.28.0-2ubuntu6 => 3.28.0-2ubuntu7] (ubuntugnome)
[17:34] -queuebot:#ubuntu-release- New: accepted ncurses [amd64] (cosmic-proposed) [6.1+20180210-2ubuntu2]
[17:34] -queuebot:#ubuntu-release- New: accepted ncurses [armhf] (cosmic-proposed) [6.1+20180210-2ubuntu2]
[17:34] -queuebot:#ubuntu-release- New: accepted ncurses [arm64] (cosmic-proposed) [6.1+20180210-2ubuntu2]
[17:34] -queuebot:#ubuntu-release- New: accepted ncurses [i386] (cosmic-proposed) [6.1+20180210-2ubuntu2]
[19:38] -queuebot:#ubuntu-release- Unapproved: glance (cosmic-proposed/main) [2:16.0.0-0ubuntu1 => 2:16.0.1-0ubuntu2] (openstack, ubuntu-server)
[19:41] -queuebot:#ubuntu-release- Unapproved: glance (bionic-proposed/main) [2:16.0.0-0ubuntu1 => 2:16.0.1-0ubuntu1.1] (openstack, ubuntu-server)
[19:49] <jbicha> please remove gnome-initial-setup 3.28.0-2ubuntu7 from bionic unapproved queue, it's superseded by later upload
[19:56] -queuebot:#ubuntu-release- Unapproved: cinder (cosmic-proposed/main) [2:12.0.0-0ubuntu1 => 2:12.0.1-0ubuntu2] (openstack, ubuntu-server)
[20:01] -queuebot:#ubuntu-release- Unapproved: cinder (bionic-proposed/main) [2:12.0.0-0ubuntu1 => 2:12.0.1-0ubuntu1] (openstack, ubuntu-server)
[20:02] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (bionic-proposed/main) [1:18.04.17 => 1:18.04.18] (core)
[20:03] -queuebot:#ubuntu-release- Unapproved: panko (bionic-proposed/universe) [4.0.0-0ubuntu1 => 4.0.1-0ubuntu1] (no packageset)
[20:03] -queuebot:#ubuntu-release- Unapproved: panko (cosmic-proposed/universe) [4.0.0-0ubuntu1 => 4.0.1-0ubuntu2] (no packageset)
[20:08] -queuebot:#ubuntu-release- Unapproved: neutron (cosmic-proposed/main) [2:12.0.1-0ubuntu1 => 2:12.0.1-0ubuntu2] (openstack, ubuntu-server)
[20:09] -queuebot:#ubuntu-release- Unapproved: neutron (bionic-proposed/main) [2:12.0.1-0ubuntu1 => 2:12.0.1-0ubuntu1.1] (openstack, ubuntu-server)
[20:14] -queuebot:#ubuntu-release- Unapproved: designate (cosmic-proposed/main) [1:6.0.0-0ubuntu1 => 1:6.0.1-0ubuntu2] (openstack, ubuntu-server)
[20:15] -queuebot:#ubuntu-release- Unapproved: designate (bionic-proposed/main) [1:6.0.0-0ubuntu1 => 1:6.0.1-0ubuntu1] (openstack, ubuntu-server)
[20:16] -queuebot:#ubuntu-release- Unapproved: gnocchi (cosmic-proposed/universe) [4.2.0-0ubuntu5 => 4.2.4-0ubuntu2] (no packageset)
[20:17] -queuebot:#ubuntu-release- Unapproved: gnocchi (bionic-proposed/universe) [4.2.0-0ubuntu5 => 4.2.4-0ubuntu1] (no packageset)
[20:20] -queuebot:#ubuntu-release- Unapproved: nova (cosmic-proposed/main) [2:17.0.1-0ubuntu1 => 2:17.0.3-0ubuntu2] (openstack, ubuntu-server)
[20:21] -queuebot:#ubuntu-release- Unapproved: nova (bionic-proposed/main) [2:17.0.1-0ubuntu1 => 2:17.0.3-0ubuntu1] (openstack, ubuntu-server)
[20:41] -queuebot:#ubuntu-release- Unapproved: debootstrap (cosmic-proposed/main) [1.0.95 => 1.0.95ubuntu1] (core)
[20:44] -queuebot:#ubuntu-release- Unapproved: accepted debootstrap [source] (cosmic-proposed) [1.0.95ubuntu1]
[20:52] -queuebot:#ubuntu-release- Unapproved: neutron-vpnaas (cosmic-proposed/universe) [2:12.0.0-0ubuntu1 => 2:12.0.0-0ubuntu2] (openstack)
[20:56] -queuebot:#ubuntu-release- Unapproved: cdrom-detect (cosmic-proposed/main) [1.57ubuntu5 => 1.57ubuntu6] (core)
[20:56] -queuebot:#ubuntu-release- Unapproved: iso-scan (cosmic-proposed/main) [1.55ubuntu5 => 1.55ubuntu6] (core)
[20:56] -queuebot:#ubuntu-release- Unapproved: choose-mirror (cosmic-proposed/main) [2.78ubuntu3 => 2.78ubuntu4] (core)
[20:57] -queuebot:#ubuntu-release- Unapproved: preseed (cosmic-proposed/main) [1.71ubuntu7 => 1.71ubuntu8] (core)
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted cdrom-detect [source] (cosmic-proposed) [1.57ubuntu6]
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted iso-scan [source] (cosmic-proposed) [1.55ubuntu6]
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted choose-mirror [source] (cosmic-proposed) [2.78ubuntu4]
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted preseed [source] (cosmic-proposed) [1.71ubuntu8]
[21:43] -queuebot:#ubuntu-release- Unapproved: python-apt (cosmic-proposed/main) [1.6.0 => 1.7.0~alpha0~ubuntu1] (core)
[21:44] <juliank> ^ the usual python-apt "add new release template" upload ...
[21:45] <juliank> gotta move that crap into distro-info at some point
[21:45] <juliank> and simplify it maybe
[21:45] <juliank> perhaps generate it
[21:46] <juliank> ok, the description still says 18.04 bionic beaver, we'll have to change that too
[21:47] <juliank> but I guess it's better than nothing
[21:49] <juliank> my master branch says 18.10 Cosmic CANIMAL now
[21:49] <juliank> but I don't think it's much better :)
[21:50] <juliank> the current upload should do the trick until we have an animal name
[22:07] <infinity> juliank: Lemme add python-apt to my local CANIMAL.txt, so I don't forget. :P
[22:13] <tumbleweed> sounds like we need a bugtracker for sabdfl
[22:17] <juliank> infinity: +1
[22:22] -queuebot:#ubuntu-release- Unapproved: debian-installer (cosmic-proposed/main) [20101020ubuntu543 => 20101020ubuntu544] (core)
[22:23] -queuebot:#ubuntu-release- Unapproved: accepted python-apt [source] (cosmic-proposed) [1.7.0~alpha0~ubuntu1]
[22:23] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (cosmic-proposed) [20101020ubuntu544]
[22:26] <mwhudson> can we just call it capybara if we don't get another name in $X days?
[22:26] <sarnold> I kind of like Cosmic Canimal. It sets us up nicely for Miasmic Manimal down the road.
[22:29] <bdmurray> infinity: https://code.launchpad.net/~brian-murray/apport/lp-cosmic-retracers/+merge/344989
[22:35] <infinity> bdmurray: Why (still) no s390x?
[22:35] <infinity> bdmurray: Obviously not a blocker for the merge, just a bit WTF.
[22:43] <bdmurray> infinity: Hrm, I'm seem to recall sending an email that it just worked a while ago.
[22:44] <bdmurray> infinity: I mean retracing s390x w/ gdb should work so I wonder why the LP retracers don't do it.
[22:46] <infinity> bdmurray: Yeah, I mean it obviously won't work on the retracers, since it needs an s390x/sources.list > ../sources-ports.list thing.
[22:47] <infinity> bdmurray: I can't imagine we get a lot of apport bugs from s390x, mind you, but if it works, may as well enable it.
[22:47] <infinity> bdmurray: (Of course, none of it works until ddebs.u.c actually has cosmic...)
[22:51] <bdmurray> infinity: the only apport crashes from s390x are from xnox and me and mine was a mistake
[22:52] <infinity> bdmurray: Heh.
[22:52] <infinity> bdmurray: Then it definitely can't hurt to enable it. ;)


[01:20] <callmepk> good morning
[02:20] <duflu> Morning callmepk
[02:20] <callmepk> morning duflu
[05:10] <jibel> Good morning
[05:54] <duflu> Morning jibel
[06:03] <jibel> hi duflu
[06:07] <oSoMoN> good morning desktoppers
[06:07] <oSoMoN> hey duflu, jibel
[06:07] <duflu> Morning oSoMoN
[06:10] <jibel> Salut oSoMoN
[06:42] <didrocks> good morning
[06:43] <duflu> Morning didrocks
[06:44] <didrocks> hey duflu
[06:56] <seb128> hey duflu, lut didrocks, goood morning desktopers
[06:57] <duflu> Hi seb128
[06:57] <jamesh> morning seb128 and others
[06:57] <seb128> hey jamesh
[06:57] <seb128> it's friday! :-) how are you?
[06:57] <didrocks> salut seb128, joyeux vendredi
[06:57] <didrocks> hey jamesh
[07:01] <seb128> didrocks, salut et à toi également ;-)
[07:05] <duflu> Hi jamesh
[07:05] <duflu> Come here often?
[07:11] <Maik> good morning  everyone
[07:48] <seb128> clobrano, hey, I saw the comment on bug #1875993 , while we encourage users to report issues upstream when they can we don't discourage them to report bugs against the Ubuntu package in launchpad since Ubuntu is what they are using
[07:49] <seb128> ideally triagers would help to review and upstream those as needed though
[07:49] <seb128> also reporting upstream requires knowledge and every project has their own infra, users might not want to go through creating stack of accounts to report their issues
[08:00] <duflu> It's also objectively correct to log a bug in Ubuntu first, since the bug definitely exists in Ubuntu at least
[08:00] <duflu> but not always in the upstream
[08:05] <Laney> sup supo supo sup
[08:05] <duflu> super
[08:05] <duflu> sup Laney
[08:07] <seb128> hey Laney, happy friday to you!
[08:07] <Laney> hey duflu seb128, happy friday indeed
[08:07] <Laney> feels like a long week this time
[08:08] <seb128> time to go back to have fridays off! :p
[08:10] <Laney> tempting
[08:11] <Laney> whoever came up with 5/2 work/non-work days was wrong :>
[08:34] <Laney> ricotz: hey, just wondering about the libreoffice upload in the queue... is your plan to push 7.0.2 final next week?
[08:35] <Laney> actually, looks like 7.0.2 is out now? so should we skip the rc? https://blog.documentfoundation.org/blog/2020/10/08/libreoffice-702/
[09:44] <seb128> ricotz, hey, I saw your msg yesterday, https://launchpad.net/ubuntu/+source/nv-codec-headers/<IP_ADDRESS>-0ubuntu2
[10:25] <Laney> ah good, we have that clear-old-devices flag set in pulseaudio, was going to ping about that
[11:26] <ricotz> Laney, this package was actually meant to be pushed last week, not sure why it got delayed that much
[11:27] <ricotz> rc2 == final, so it would basically mean to repack and change the version string
[11:27] <ricotz> there is no need to do this
[11:28] <ricotz> seb128, thanks
[11:39] <luna_> seb128: Wimpress: Sent in some suggestions for Swedish for the new AD and ZFS Features in the installer now :)
[11:45] <seb128> luna_, great!
[12:08] <Laney> ricotz: you don't think there is value in having it labelled as a stable release properly?
[12:10] <ricotz> Laney, no
[12:10] <Laney> :/
[12:11] <Laney> I can guarantee you we will get complaints / questions / enquiries about that
[12:11] <ricotz> Laney, I understand, but there is no real benefit doing so
[12:11] <Laney> worth the 10 minutes work
[12:11] <ricotz> Laney, this is not 10 min work
[12:11] <ricotz> likely an hour
[12:17] <ricotz> Laney, please accept this package, I will provide a "final" package next week
[12:19] <Laney> ok, sorry, I'm watching a presentation at the same time as this
[12:20] <Laney> tkamppeter: https://launchpadlibrarian.net/494034809/system-config-printer_1.5.12-0ubuntu1_1.5.12-0ubuntu2.diff.gz lol
[12:21] <tkamppeter> Laney, I discovered this today when I checked whether there are still packagges recommending or requiring ippusbxd.
[12:22] <tkamppeter> The -0ubuntu3 is uploaded.
[12:22] <Laney> yeah, that's why I went back to look at the previous upload
[12:22] <Laney> funny ;)
[13:05] <luna_> marcustomlinson: saw your work on better theming support for Snaps listening to this weeks Ubuntu Podcast, looks great :)
[13:23] <marcustomlinson> luna_: thanks :) big up to jamesh for doing most of the work ;)
[14:49] <oSoMoN> seb128, I prepared the shared-mime-info update in salsa, do we want to preventively upload to ubuntu before it's in Debian?
[14:50] <seb128> oSoMoN, wouldn't hurt since we are getting close from release?
[14:51] <oSoMoN> seb128, would you mind giving it a quick review?
[14:51] <seb128> oSoMoN, let me review
[14:51] <oSoMoN> (I verified that it builds on all arches and installs fine, ofc)
[15:21] <seb128> oSoMoN, seems fine to me, I will sponsor to Debian a bit later but feel free to upload to ubuntu as 0build1 or 1~fakesync
[15:21] <seb128> (I tend to do 0build1 so it got automatically synced without manual intervention next cycle)
[15:22] <oSoMoN> ok, I'll do that
[15:22] <seb128> thx
[15:23] <Laney> both versions achieve that, only the string 'ubuntu' stops auto-sync
[15:24] <Laney> only saying because it read like a claim the second one does too, maybe that wasn't the intention
[15:33] <oSoMoN> so semantically speaking, using ~fakesync is more correct, right? (because it's not a no-change rebuild)
[15:35] <seb128> Laney, thanks, I didn't know *ubuntu was special, I though *build was, I learnt something :-)
[15:36] <seb128> oSoMoN, yes, I just though that it wouldn't be automatically overwritten
[15:37] <Laney> some people don't rev the number at all, they just re-target the _source.changes for ubuntu (syncpackage --no-lp)
[15:38] <seb128> that feels weird to me :p
[15:38] <Laney> me too, but I see the logic as it's unchanged and not a rebuild, kind of morally a sync
[15:38] <seb128> indeed
[15:39] <Laney> wouldn't do it for syncs from new though, as they could end up being rejected and then you would be lying about the contents
[15:39] <seb128> right
[15:40] <didrocks999> "I didn't know *ubuntu was special, I though *build was, I learnt something :-)" +1, I was thinking *build was special-cased
[15:40] <seb128> speaking of updates I started on an hackish script to automate some of the steps to do GNOME updates
[15:40] <seb128> I will try to clean that up next week and share it
[15:41] <seb128> didrocks999,^5
[15:41] <Laney> https://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/auto-sync#L438
[15:41] <seb128> didrocks999, still not land line for internet?
[15:41]  * didrocks999 high five back (999 times)
[15:41] <didrocks999> seb128: no, but TBH, with 4G, I have 50Mb/s, where DSL here is 2…
[15:41] <Laney> script> niceeeeeeeee
[15:41] <oSoMoN> seb128, that script sounds interesting, looking forward to seeing it
[15:41] <didrocks999> the only issue is stability with those micro-cut
[15:42] <seb128> wouldn't be an issue on mattermost :p
[15:42] <didrocks999> BUT that doesn’t impact TV or HO, only IRC
[15:42] <didrocks999> yeah
[15:42] <seb128> we need that to replace IRC
[15:42] <didrocks999> TBH, browsing and all the rest is great
[15:42] <didrocks999> only IRC sucks (and lack of static IP for my server)
[15:43] <didrocks999> I wasn’t expecting such reliable bandwidth (also, I’m aggregating 3 frequency bands)
[15:44] <didrocks999> with TV and due to all-day HO with j_ibel, I’m topping 300Gb/month for 16€…
[15:45] <didrocks999> so, I think, I’ll wait for fiber (it’s now only 150m away!) to get wired
[15:45]  * didrocks999 sees fiber going from one house closer to the next one :)
[15:46] <oSoMoN> seb128, ready for sponsoring: https://people.canonical.com/~osomon/sponsoring/shared-mime-info.debdiff
[15:47] <seb128> oSoMoN, did you apply for moday's dmb meeting yet? ;-)
[15:48] <seb128> and did you corner didrocks or Laney to get extra endorsements?
[15:48] <oSoMoN> seb128, no, I'm waiting for at least a third endorsement (gotta ping my favourite coredevs again), and I'm afk on Monday anyway
[15:48] <Laney> you need to give N days notice anyway (7?)
[15:49] <Laney> I will do it :>
[15:49] <Laney> need to check what I sponsored
[15:49] <oSoMoN> Laney, didrocks999: this is the perfect task for a Friday afternoon, right before opening a beer: https://wiki.ubuntu.com/OlivierTilloy/CoreDevApplication
[15:49] <didrocks999> afternoon? is it still afternoon? :p
[17:16] <oSoMoN> alrighty, I'm off for three days, have a good week-end everyone


[07:19] <tjaalton> jcristau: oh, nice.. didn't spot that one
[07:21] <bryce> heya
[07:21] <tjaalton> howdy
[07:22] <tjaalton> no archive-admin action yet, it seems :)
[07:22] <bryce> yeah :-/
[07:22] <bryce> I did mention the sync req's to rick
[07:22] <bryce> if they don't get done in the next day I can ping some people
[07:23] <tjaalton> most of the protos should be autosynced anyway, since they entered testing yesterday
[07:23] <tjaalton> but I need to merge xutils-dev so they build
[07:27] <tjaalton> maybe I should upgrade my laptop as well..
[07:28] <tjaalton> before the madness
[08:14] <tjaalton> mvo: hey, could the "failed to install" bugs attach the output of df to the bug. I suspect most of them are due to full root partition..
[08:18] <tjaalton> 'df -l' would do
[08:56] <mvo> hey tjaalton
[08:56] <mvo> tjaalton: sure
[08:56] <mvo> tjaalton: good idea
[08:56] <mvo> hm, update-manager should check (well, approximate) that now, however apt itself does not
[09:00] <tjaalton> mvo: great, thanks
[09:09] <tjaalton> mvo: is it generally ok to drop Breaks/Depends/.. on packages from a past devel version (so that the version was not in the final release)?
[09:10] <tjaalton> since I don't think we support upgrades from a past alpha
[09:13] <mvo> yeah, that should be fine
[09:14] <tjaalton> good
[09:41] <mvo> tjaalton: df -l commited to my bzr branch, thanks
[09:41] <tjaalton> mvo: excellent :)
[10:01] <Unggnu> hi all
[10:02] <Unggnu> I have read that the big X/Kernel changes are scheduled before Alpha 1. So it doesn't make sense/is dangerous before that to upgrade a Lucid Testing environment?
[10:03] <Unggnu> Btw. which gain do we have through noveaou. I mean it has no 3D support yet afaik and KMS is good but most people would switch to the proprietary driver anyway.
[10:04] <Unggnu> I mean nv is quite stable and has an alternative or are there many bugs for nv?
[10:04] <tjaalton> bah, I upgraded an hour ago
[10:04] <Unggnu> tjaalton, So the big changes hasn't happened yet or already? :)
[10:04] <tjaalton> nv is pretty much dead
[10:04] <tjaalton> Unggnu: not yet
[10:04] <Unggnu> tjaalton, But they still make it work for new cards, 2d and xv or not anymore?
[10:04] <tjaalton> waiting on syncs from debian, and xorg & xorg-server merges to be uploaded
[10:05] <tjaalton> Unggnu: it has modesetting bugs that wont be fixed
[10:05] <Unggnu> Ok, noveau would be great for old Nvidia cards that has no proprietary driver anymore but I doubt that it is already fast or so stable
[10:05] <tjaalton> it's fast for 2D
[10:05] <Unggnu> ok, I just thought it is a tough decision for LTS
[10:05] <tjaalton> and some people can't get nv up at all
[10:06] <Unggnu> I mean radeon driver is in development since a long time and still has no Powerplay
[10:06] <Unggnu> which makes the computer pretty loud and uses much energy
[10:07] <Unggnu> I don't know if the nv has the pendant.
[10:07] <jcristau> it doesn't
[10:07] <Unggnu> But with the edgers package KMS already works and textured video (still with tearing though).
[10:08] <Unggnu> Ok, we will see how it works out. I haven't any Vvidia card anymore, at least not in use.
[10:10] <Unggnu> Through ChromeOS and developments like this Nvidia will probably change their decison, at least I hope so
[10:10] <Unggnu> The pressure through Dell has already worked in some areas afaik
[10:11] <Ng> chromeos would be more likely to be used on a tegra type platform I would have thought?
[10:12] <Unggnu> Ng, on Netbooks and in future it should be combine with Android afaik. Anyway Nvidia also produces chips for this devices afaik.
[10:12] <Unggnu> If they only use open source drivers they have to change
[10:13] <Ng> sure, the tegra, but I'm assuming wildly that it's very different to their desktop offerings
[10:14] <Unggnu> synergy ;)
[10:22] <Unggnu> KMS seems to work with nouveau even for nvidia TNT, that's cool.
[10:22] <Unggnu> So Debian plans to use Nouveau in SID too?
[10:23] <tjaalton> probably not as default. that would mean kernel changes
[10:23] <tjaalton> which is the painful part
[10:25] <Unggnu> yes, I have heard
[10:26] <Unggnu> Radeon is also pretty fast without KMS
[10:26] <Unggnu> but I think this was fixed lately
[10:29] <Unggnu> Got to go, thanks for the information, bye.
[13:48] <diverse_izzue> hi all, using kernel 2.6.32 from the mainline kernel ppa and the xorg-edgers ppa on karmic, i get no dri. xorg.log says:(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] radeon kernel module version is 2.0.0 but version 1.17.0 or newer is needed. [dri] Disabling DRI.
[13:48] <diverse_izzue> any ideas?
[13:56] <diverse_izzue> i should say that i also enable kms
[13:56] <tjaalton> does .31 work?
[13:57] <diverse_izzue> tjaalton, i'll check that, just a minute
[14:03] <diverse_izzue> tjaalton, same thing with 2.6.31-15 from karmic repos
[14:04] <tjaalton> don't use kms, it seems
[14:05] <diverse_izzue> it does use KMS i believe
[14:05] <tjaalton> but if you use modeset=1, DRI works
[14:05] <tjaalton> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/394263
[14:05] <tjaalton> erm, =0
[14:06] <diverse_izzue> i'm quite sure it's someting in the updated  X stack, because i get dri with the X stack from karmic + KMS
[14:06] <tjaalton> mesa then
[14:07] <tjaalton> google for the error, there are tons of hits
[14:07] <jcristau> diverse_izzue: your issue is either your ddx driver doesn't support kms, or there's a race when loading the radeon kernel module which makes this fail.
[14:07] <diverse_izzue> jcristau, my ddx driver is the most recent one from the xorg-edgers ppa
[14:07] <diverse_izzue> so probably number 2
[14:07] <diverse_izzue> what to do about that?
[14:08] <jcristau> modeset=0, or load radeon earlier
[14:08] <diverse_izzue> how to load radeon earlier?
[14:13] <diverse_izzue> have to go to the lab, back in a little while...
[14:22] <tormod> bryce, can you join our radeon kms discussion on #ubuntu-kernel please?
[14:24] <tjaalton> doubt he's awake yet
[14:25] <diverse_izzue> the xorg wiki talks about the error: http://www.x.org/wiki/radeonBuildHowTo.
[14:25] <tormod> hmm doesn't his son keep him awake all the time?
[14:25] <tjaalton> hehe
[14:26] <jcristau> tjaalton: i'd forgotten xft.. damn lib not starting with lib.  fixed now, on its way to sid.
[14:27] <tjaalton> jcristau: hehe, time to rename it? :)
[14:27] <tjaalton> it's libXft upstream
[14:27] <tjaalton> so it would be even consistent :)
[14:27] <tormod> diverse_izzue, it's not what they say on the x wiki
[14:28] <diverse_izzue> tormod, but what...?
[14:38] <tormod> diverse_izzue, the reason for that error message can be what the x wiki says, and it can be what my page says
[14:38] <tormod> on Ubuntu, the x wiki explanation is not applicable since we build with the kms api
[14:41] <apw> bryce, yo ... we are discussing the change to enable radeon kms on #u-k
[14:41] <tormod> apw, I tried to wake him too :)
[14:44] <apw> heheh
[14:45] <tjaalton> so how does intel initialize early enough, but not radeon?
[14:45] <tjaalton> is the module in initramfs?
[14:45] <tjaalton> AIUI it isn't
[14:48] <tormod> tjaalton, is the i915 force loaded somewhere, not by the X server?
[14:48] <tjaalton> tormod: maybe, I don't know
[14:49] <tormod> I just remember there was this i915 and fbcon(?) issues in karmic before release
[14:50] <tormod> wasn't there some kind of race that got sorted out?
[14:50] <tjaalton> apw: ^
[14:50] <tjaalton> or should Keybuk know?
[14:50] <tjaalton> things progress too fast for me :)
[14:50] <tormod> I asked Keybuk about all this some days ago
[14:51] <tormod> he did not know
[14:51] <tjaalton> heh ok
[14:51] <tormod> I thought I had more time to sort it out anyway :)
[14:51] <apw> its odd, we load the drivers which do that very early, in responce to udev events for them
[14:51] <apw> we then boot ... slowly for several seconds, then start X
[14:52] <apw> how it could not be ready in time i do not know
[14:52] <tormod> radeon does not load by itself
[14:52] <tormod> I tried, see my gdm.conf on the wiki page
[14:52] <apw> the radeon driver does not have module aliases ?
[14:52] <tormod> if I remove "modprobe radeon" X does not start
[14:53] <tjaalton> tormod: but kms worked?
[14:53] <tormod> if I then manually modprobe radeon, boom X starts
[14:53] <tjaalton> I mean, how can it work without radeon?
[14:53] <tormod> no kms does not activate before
[14:53] <apw> it can't work without radeon, but radeon should load automatically by itself
[14:53] <tjaalton> right
[14:53] <apw> if its done right
[14:53] <tjaalton> it takes 2.5s for i915 to load here
[14:54] <apw> but that is sychonous
[14:54] <apw> so its done by the time X starts
[14:54] <tormod> historically only the X server would make radeon load
[14:54] <tormod> and only if the X server uses "radeon" DDX I guess
[14:54] <tormod> and not if it uses fglrx
[14:55] <tormod> so it's a chicken and hen element to this
[14:55] <tormod> *egg
[14:55] <apw> #if defined(CONFIG_DRM_RADEON_KMS)
[14:55] <apw> MODULE_DEVICE_TABLE(pci, pciidlist);
[14:55] <apw> #endif
[14:55] <apw> if KMS is turned on in the build (which it is) then we should load the driver if the id's are listed
[14:55] <tjaalton> ha
[14:56] <tjaalton> maybe that would do it?
[14:56] <apw> that is the current settings
[14:56] <tormod> that is the current settings since a long time right?
[14:56] <apw> so if you disabe the gdm upstart job, we'd expect to see it loaded by udev
[14:56] <tjaalton> tormod: has anyone tried with a kernel where it's enabled?-)
[14:56] <apw> all of karmic yes
[14:56] <apw> thats enabled, with or without modesetting selected
[14:56] <tormod> tjaalton, CONFIG_DRM_RADEON_KMS means support for KMS
[14:57] <tormod> not that it is on by default
[14:57] <tjaalton> ah right
[14:57] <apw> yep we have the code ON but disabled by option
[14:57] <tormod> well, it does not load by itself here
[14:57] <apw> then the module aliases are wrong i would guess
[14:57] <tormod> what can I check?
[14:58] <tormod> wait I know
[14:58] <apw> if you don't load it by default
[14:58] <apw> then you can see what udev sees in its logs /var/log/udev
[14:59] <tormod> my card is 1002:5653 and I see pci:v00001002d00005653sv*sd*bc*sc*i* in modinfo
[14:59] <apw> tormod, there are a lot of id's listed
[14:59] <apw> nope not listed
[14:59] <tormod> is /var/log/udev kept logged to?
[15:00] <apw> its a live file i believe
[15:00] <apw>    This file is auto-generated from the drm_pciids.txt in the DRM CVS
[15:00] <apw>    Please contact<EMAIL_ADDRESS>to add new cards to this list
[15:00] <apw> ok the list of supported id's has that comment in it
[15:01] <tormod> apw, not listed where? I see it in modinfo
[15:01] <apw> yeah ... hrm
[15:01] <apw> it is in there
[15:03] <apw> tormod, i see the ids in the source but not in the modules.alias file
[15:04] <tormod> anyway, it can still be racy since kms init takes ~0.6s and X starts earlier and earlier
[15:04] <apw> tormod, wa
[15:04] <apw> tormod, what is the solution to that ...
[15:05] <tormod> apw, you saw my gdm.conf hack?
[15:05] <tormod> there must be a real solution though
[15:06] <tormod> drmCheckModesettingSupported in libdrm should not return before init is finished maybe
[15:08] <tormod> if there's a way from userspace to see if drm init has finished regardless of kms support
[15:08] <apw> we have an issue that we want X to start earlier to get things working qucker, but that makes people do init async, and we have no way to work out if its meant to be coming
[15:08] <apw> the issue is that there is no way to know if the device will find an output and modeset it or not
[15:11] <tormod> we could make drm emit an event and let gdm wait for it, but then if you boot something where there is no drm hw...
[15:12] <apw> you need to know its done whether it did anything or not
[15:13] <tormod> I am tending towards fixing radeon DDX, it knows it has a drm device, just have to wait for it to finish init before probing it
[15:16] <tormod> I wonder if /dev/dri/card0 shows up before it is fully initialised?
[15:17] <tormod> in other words, if /dev/dri/card0 shows up before /sys/class/.../drm/controlD* which is the KMS marker it probes for
[15:19] <tormod> I mean /sys/bus/pci/devices/.../drm/controlD*
[15:26] <tormod> yes it does, that is obvious from Xorg.0.log
[16:25] <tormod> (more loud thinking in #radeon)
[17:05]  * tormod notices libdrm 2.4.16 is out!
[18:01] <apw> bryce, yo!
[18:02] <apw> i reenabled ati kms, tormod seems to think that userspace is not ready, what do you want the Alpha-1 kernel to have  as the default, on or off?
[18:10] <tormod> apw, I have some ideas to avoid potential races if the module already has been loaded and is under initialisation, but what about the fact that radeon is not loaded by itself?
[18:15] <apw> its sounding like you guys just need to do more before this is ready
[18:15] <apw> so i'll just turn it off again
[18:16] <tormod> apw, yes I agree. we could add some quick workarounds now, but we need to find a better solution
[18:17] <apw> we
[18:17] <bryce> heya apw
[18:17] <apw> i'll put together an email tomorrow saying that we're turning it off
[18:17] <tormod> would be good if more of you devs would run lucid and latest bits and KMS though
[18:17] <apw> and you guys can argue about how to fx it for alpha2
[18:18] <apw> we all sensibly have intel
[18:18] <tormod> if I am the only one who have tested KMS, I would not enable it for everybody ATM
[18:18] <apw> then we'll never enable it, which seems like no progress
[18:18] <apw> bryce, talking about radeon
[18:18] <tormod> yes that's bad that you all use the same hardware
[18:18] <apw> i enabled it in the -6 kernel and its seeeming its not working
[18:19] <apw> userspace issues, so i wanted to confirm whether i should switch it off for a1 or not
[18:20] <bryce> if it is completely broken, there's not much time remaining pre-a1 for us to fix it
[18:20] <apw> bryce, i thought from our disucssions at uds it was ok, but tormod says userspace isn't ready
[18:21] <apw> perhaps you could disucss with him and let me know what you wnat the default to be for a1
[18:21] <apw> i'll be uploading tommorrow am my time for the release
[18:21] <apw> i have to run now, so drop me an email....
[18:21] <bryce> leave it off
[18:22] <apw> ack
[18:22] <bryce> I tend to prefer switching things on right after a release, to give maximal time to test
[18:22] <bryce> if we already know radeon kms doesn't work reliably, I'd rather not have the deluge of bug reports ;-)
[18:23] <apw> ok so lpan of off for a1 and on in the first upload after thant
[18:23] <bryce> yep
[18:23] <bryce> I'll work out the plan with tormod for what we have to do on the userspace side and hopefully get that squared away in the mean time
[18:23] <tormod> bryce, to summarize: radeon is not loaded before X loads it, but when X probes for KMS the module has not finished initializing so it thinks KMS is off
[18:24] <tormod> and you get UMS and KMS at the same time!
[18:24] <bryce> tormod, ah
[18:24] <tormod> bryce, please read the backlog here, #ubuntu-kernel and #radeon
[18:24] <bryce> tormod, could we just force it to expect KMS and sleep if it is missing?
[18:24] <jcristau> tormod: afaict with CONFIG_DRM_RADEON_KMS=y, the radeon module exports a device table that should get it loaded automatically by whatever at boot
[18:24] <bryce> hmm, I'm not on #radeon
[18:25] <tormod> jcristau, I was discussing this with apw above, but it seems it is not loading
[18:26] <bryce> hmm and looks like I caught only the tail end of the #ubuntu-kernel discussion...  mind re-summarizing the main bits for me?
[18:26] <jcristau> hmm the MODULE_DEVICE_TABLE isn't enough?
[18:26] <tormod> so maybe it is a kernel issue although apw blames userspace :)
[18:27] <jcristau> well there's still another bug if 'modprobe radeon; drmCheckModesettingSupported()' fails
[18:27] <tormod> bryce, I have a patch for what you suggested there :)
[18:27] <tormod> jcristau, yes it is still racy
[18:28] <jcristau> tormod: but that should only matter in the case where radeon doesn't get loaded by udev earlier
[18:28] <tormod> jcristau, or everything starts up really quick :)
[18:28] <jcristau> which is aiui the whole point of the device table
[18:29] <tormod> note also that radeon will need firmware available, currently missing from initrd
[18:29] <jcristau> it doesn't need to be in initrd
[18:29] <tormod> depends on when you load radeon...
[18:30] <jcristau> udev should load it after / is available, i think
[18:36] <tormod> bryce, this is patch http://ubuntu.pastebin.com/d3b3afb7c
[18:38] <bryce> tormod, firmware?
[18:39] <tormod> bryce: platform radeon_cp.0: firmware: requesting radeon/R420_cp.bin
[18:39] <bryce> tormod, yeah that's what I was thinking
[18:40] <tormod> on my own laptop, I have a kms-ready.conf that waits for "filesystem" to load radeon
[18:41] <tormod> then I let gdm.conf wait for kms-ready (which is NOP without KMS)
[18:41] <jcristau> tormod: that patch seems wrong.  drmCheckModesettingSupported returns 0 if modesetting *is* supported
[18:41] <tormod> jcristau, quite possibly, not tested yet :)
[18:41] <bryce> tormod, oh right the command processor
[18:42] <jcristau> also a 2s penalty for ums users seems a lot...
[18:42] <tormod> not if KMS is default
[18:42] <bryce> right ideally we don't care about UMS
[18:43] <bryce> like with -intel people need UMS only to work around bugs
[18:43] <bryce> (in theory, ideally)
[18:43] <tormod> ideally drmCheckModesettingSupported should be fixed to wait if stuff is initialising
[18:43] <jcristau> yes
[18:44] <tormod> jcristau, this is not a upstream patch :) just a Ubuntu hack
[18:44] <tormod> drmCheckModesettingSupported is kind of mickeymouse also IMO
[18:51] <tormod> how difficult would it be to fix the radeon module to create a /sys file that tells if KMS is enabled or disabled (and not just one of them)
[18:53] <bryce> jcristau, do you envision in debian testing wanting to support both UMS and KMS on radeon?
[18:54] <jcristau> i don't think we'll turn radeon kms on by default if that was the question
[18:54] <bryce> jcristau, since I know with -intel the plan is to eliminate UMS entirely, I'm sort of figuring supporting both to be just a transitional thing
[18:54] <bryce> jcristau, ok gotcha
[18:55] <jcristau> (if we do, we'd have to track whatever's in f12, since apparently dave didn't get all fixes in .32 final, and considering the manpower issues we have i don't think that's feasible
[18:56] <jcristau> )
[18:57] <tormod> since many users does kernel-hopping it would be good if user-space can deal with both active-by-default and not
[18:57] <bryce> email from alex deucher:
[18:57] <bryce> Any chance you can pull radeon drm bits from 2.6.33 during
[18:57] <bryce> development?  We are planning to move radeon kms out of staging during
[18:57] <bryce> 2.6.33 and there are a number of important patches already queued for
[18:57] <bryce> 2.6.33: a number of bug fixes, tmds support on pre-avivo igp chips,
[18:57] <bryce> interrupt support on r6xx/r7xx, and displayport support to name a few.
[18:57] <bryce>
[18:57] <bryce> Displayport is supported now in xf86-video-ati master for UMS, and for
[18:57] <bryce> KMS the patches are in drm-radeon-testing.  I hope to have the
[18:57] <bryce> interrupt bits for KMS DP/HPD merged soon too.  This will give us
[18:57] <bryce> interrupt driven monitor detection which will trigger a uevent (e.g.,
[18:57] <bryce> box pops up saying: "You've attached/disconnected a monitor", etc.).
[18:58] <bryce>
[18:58] <bryce> monitor uevents... sweetness
[18:59] <tormod> anyone here on radeon UMS ATM?
[18:59] <bryce> yes
[19:00] <tormod> can you pastebin your "find /sys/devices/pci-blahblahvideocard" ?
[19:01] <bryce> http://pastebin.ubuntu.com/334037/
[19:01] <tormod> thanks
[19:08] <tormod> my KMS one: http://ubuntu.pastebin.com/d43af9bdf drmCheckModesettingSupported looks for drm/controlD* in there
[21:10] <bryce> tjaalton, how are we looking for the 1.7 merge?  would it help if I work on some of the misc. outstanding merges?
[21:11] <tjaalton> bryce: 44 packages are waiting to be synced
[21:12] <tjaalton> xorg & xorg-server are merged, but the latter has some patches that need a review & refresh
[21:12] <bryce> tjaalton, right, beyond the syncs anything else needed that I should work on?
[21:12] <tjaalton> well, maybe have a look at the patches and see if they are needed?
[21:13] <tjaalton> I've updated the versions page with some new syncs and comments
[21:14] <bryce> ok
[21:14] <bryce> I've pinged pitti to do the syncs
[21:14] <tjaalton> great
[21:15] <bryce> are the patches to review flagged somehow in git?
[21:15] <bryce> ah yes they are
[21:15] <bryce> ok on it
[21:15] <tjaalton> uncommented from series, and marked in the changelog
[21:40] <tormod> are you gonna use udev in the xserver for A1?
[21:42] <tjaalton> yes
[21:43] <tormod> cool
[21:46] <bryce> hrmph, everyone complains "canonical doesn't contribute to X.org upstream", yet here are all these patches I made and sent upstream and they never got taken (or got a reply as to why not)
[21:47] <bryce> and I continue to wait for my fdo git account  :-P  https://bugs.freedesktop.org/show_bug.cgi?id=20373
[21:50] <tjaalton> maybe ping someone on #xorg-devel?
[21:51] <tjaalton> and the workflow has changed, so direct commits to master are a no-go, so posting patches for a review doesn't require the login (not that it would harm either..)
[21:52] <tjaalton> but maybe it's just the xserver that follows this, dunno
[21:52] <bryce> oh interesting
[21:52] <bryce> yeah mainly I wanted access to do work on -ati
[21:52] <tjaalton> it's been discussed on the list several times the past few months :)
[21:53] <bryce> yeah read those, and also discussed at XDC which I attended.
[21:53] <bryce> you'd think I'd remember these things
[21:53] <tjaalton> oh right
[21:53] <tjaalton> hehe
[21:53] <jcristau> it's mostly for the server, where keith is the one to push to master
[21:53] <bryce> yeah I guess I can try pushing the patches in again
[21:54] <bryce> iirc some of them whot said were just papering over issues and he'd prefer to crash in those situations
[21:54] <jcristau> i need to resend the udev stuff
[21:54] <bryce> I tend to prefer issuing a warning in Xorg.0.log and not crash... seems more friendly to the user
[21:54] <Sarvatt> patch 169 obsoleted by http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.7-branch&id=3d30789a05a730a03faa6058c73a5eda36ef3779 ?
[21:55] <bryce> Sarvatt, unfortunately that's not the only place where MIPOINTER() is dereferenced without checking for NULL
[21:57] <tormod> tjaalton, I don't see the touchpad rule in git yet
[21:57] <bryce> Sarvatt, grepping launchpad, patch 169's error string does show up in a couple bug reports (for proprietary drivers).
[21:57] <bryce> maybe those are outdated, I didn't check
[21:57] <jcristau> tormod: i think i pushed it to -synaptics...
[21:58] <tormod> jcristau, oh that would make sense
[22:00] <bryce> tjaalton, looks like the syncs are coming in
[22:00] <bryce> libs at least so far
[22:00] <tjaalton> bryce: yep :)
[22:01] <bryce> looks like lp is about to go down so rest are going to wait for tomorrow
[22:03] <tjaalton> it's only 90min or so
[22:03] <bryce> I think pitti wants to go to bed
[22:03] <tjaalton> ah, right :)
[22:06] <Sarvatt> at least most of that wont build without the missing protos so things wont be broken until then :D
[22:06] <tjaalton> yep
[22:08] <bryce> ok, down to two patches
[22:08] <bryce> but oy, saved the hardest for last
[22:09] <Sarvatt> nothing can be worse than libx11's 03 patch lol
[22:10] <Sarvatt> which one is left?
[22:10] <bryce> 003_recognize_glibc_2.3.2_locale_names.diff ?
[22:10] <bryce>     - 135_rethrow_signals.patch - TODO: Refresh
[22:10] <bryce>     - 190_cache-xkbcomp_output_for_fast_start_up.patch
 bryce: ok, it's still alive, synced all bug bug 491051
[22:10] <Sarvatt> ugh yeah thats the nightmare one I spent 8 hours refreshing
[22:11] <bryce> oop he did that one too
[22:11] <tjaalton> bryce: 003? where's that from?
[22:11] <bryce> tjaalton, ok all in
[22:11] <bryce> tjaalton libx11
[22:11] <tjaalton> hehe
[22:11] <Sarvatt> libx11, sorry was talking about nightmare patches
[22:11] <tjaalton> the infamous la_AU patch
[22:12] <bryce> Sarvatt, 006 looks bad too (at least, it's huge)
[22:12] <Sarvatt> wait, you need x11proto-input 2.0 from experimental not the one from unstable dont you?
[22:12] <tjaalton> indeed
[22:12] <bryce> $ diffstat 006_tailor_pt_BR.UTF-8_Compose.diff
[22:12] <bryce>  Compose.pre | 5619 ------------------------------------------------------------
[22:12] <bryce>  1 file changed, 1 insertion(+), 5618 deletions(-)
[22:12] <bryce> ok maybe not so bad, just deletes a lot of stuff :-)
[22:12] <tjaalton> huh
[22:13] <bryce> Sarvatt, yes, the bug was just misfiled, my bad
[22:13] <jcristau> Sarvatt: want to help getting it upstream?
[22:13] <jcristau> :)
[22:13] <tjaalton> bryce: only patch 16 is ours
[22:14] <tjaalton> 016 I mean
[22:14] <tjaalton> so it's a simple merge
[22:19] <bryce> hey, speaking of XI2, does this finally get rid of the 256 limitation on key codes?
[22:19] <bryce> or is that a more fundamental X11 protocol issue?
[22:23] <jcristau> the core protocol still only has 8bit for keycodes
[22:23] <jcristau> but i think apps can listen to xi2 events and get 32bit keycodes
[22:24] <jcristau> so we probably still need xkb2 and then fix clients
[22:28] <bryce> jcristau, so will only apply for xi2 compliant apps?
[22:28] <bryce> do apps need changed to use this or is it something that can be taken care of by the toolkits?
[22:28] <jcristau> bryce: may be enough to migrate toolkits
[22:29] <jcristau> that's probably all that's needed
[22:29]  * bryce nods
[22:29] <jcristau> but then it's possible even fewer people understand gtk's input code than X's
[22:29] <jcristau> ;)
[22:29] <bryce> lol
[22:30] <Sarvatt> refreshing the udev patch for master and i'll upload it in a bit tormod
[22:31] <Sarvatt> oh darn he just left, nevermind
[22:37] <bryce> ok patch 135 done, one patch left
[22:54] <bryce> done
[22:55] <bryce> and refreshed/re-enabled the timing patch 160 for good measure
[22:55] <Sarvatt> that one fails nastily on master :D
[22:56] <bryce> Sarvatt, the timing patch?
[22:56] <Sarvatt> 190_cache-xkbcomp_output_for_fast_start_up.patch
[22:56] <bryce> oh
[22:56] <bryce> it required only minor tweaking to get it to apply (just one chunk was off)
[22:57] <tjaalton> bryce: so 156 is no longer needed?
[22:58] <tjaalton> the commits were a bit messy ;)
[22:58] <bryce> tjaalton, where might I best snag xorg-server_1.7.2.orig.tar.gz ?  I'll do a build test
[22:58] <tjaalton> packages.debian.org?
[22:58] <jcristau> ftp.debian.org works
[22:58] <tjaalton> that too
[22:58] <bryce> tjaalton, my commits were messy?  sorry about that, tried to keep one commit per patch
[22:59] <tjaalton> well, some changelog edits etc. and patch 156 is still in git and enabled, also referenced in the changelog :)
[22:59] <Sarvatt> sweet, changelog is down to 4 hooks for xorg-server master now from about 40 :D
[23:00] <bryce> oh whoops
[23:00]  * bryce fixifies
[23:01] <bryce> pushed
[23:01] <tjaalton> thanks
[23:04] <Sarvatt> 02_Add-libgcrypt-as-an-option-for-sha1.diff is upstream 164_trap-aspect-ratios.patch fails 190_cache-xkbcomp_output_for_fast_start_up.patch fails and 12-Add-libudev-input-hotplug-backend.diff just needed 2 words changed. ah yeah and --disable-werror needed to be changed to --disable-strict-compilation in rules on master
[23:05] <bryce> what's the error on 190?
[23:05] <bryce> ftp.debian.org is slooow
[23:10] <Sarvatt> wait, you're patching the patch in the patch?
[23:10] <Sarvatt> in 190
[23:10] <Sarvatt> --- a/debian/patches/190_cache-xkbcomp_output_for_fast_start_up.patch
[23:10] <Sarvatt> +++ b/debian/patches/190_cache-xkbcomp_output_for_fast_start_up.patch
[23:12] <bryce> oh hell
[23:12] <bryce> hang on
[23:13] <tjaalton> :)
[23:17] <bryce> wow I made a mess
[23:18] <bryce> er, wait maybe not
[23:20] <Sarvatt> all of configure.ac and 2 hunks out of ddxLoad.c failed on master though before the patch patched itself and tried to delete all the other hunks :D
[23:21] <Sarvatt> that patch just speeds up startup times after the first one?
[23:25] <bryce> ok I think I see what happened
[23:27] <Sarvatt> lucid's got a pretty nasty bug right now, all the standard preferences and administration items are gone from the menus
[23:28] <RAOF> I guess now's not the time to restart, then.
[23:31] <Sarvatt> not till ya get a gnome-menus update for sure
[23:54] <bryce> fixed (I think) 190 pushed
[23:55] <bryce> my pbuilder env is not getting the new protos for some reason
[23:55] <bryce> and                                 Depends: libxi-dev (>= 2:<IP_ADDRESS>) but 2:1.2.1-2ubuntu1 is to be installed.
[23:58] <Sarvatt> thats a good sign --
[23:58] <Sarvatt> robert@ubuntu-9{/opt/source/xorg-pkg-tools}:aptitude show x11proto-xext-dev
[23:58] <Sarvatt> Segmentation fault
[23:58] <Sarvatt> :D
[23:58] <bryce> maybe not everything got sync'd after all?
[23:59] <Sarvatt> think it's even moved past the libs that were synced before the protos that wont build yet?


[11:37] <nammn_de> stickupkid_: https://github.com/juju/juju/pull/10894 a ci job fix. How do I test it on jenkins again?


[00:47] <SuperLag> nautilus is a crashy mess for me, on a clean install
[00:47] <SuperLag> I can't even open a folder without it crashing on me
[05:18] <LordPants> hey all, I was asked to repeat my question in here... just finished installing 64-bit 13.10, and it's working great. but apt-get won't let me install ia32-libs to run 32-bit software. what's the new method in Ubuntu 13?
[05:19] <IdleOne> !find  ia32-libs
[05:20] <IdleOne> hmm doesn't look like 13.10 has it
[05:20] <LordPants> yeah, I figured it was deprecated
[05:20] <LordPants> but I don't no what the new package is, and my google-fu isn't turning anything up
[05:20] <LordPants> don't know*
[05:20] <IdleOne> try searching for multiarch in the package manager
[05:21] <IdleOne> I'm not sure what it was changed to
[05:22] <LordPants> IdleOne: all that turns up in the software center is a "transitional multiarch", whatever that is (and it's already installed anyway) and a multiarch binutils, which isn't needed for executing, only building and linking.
[05:23] <IdleOne> LordPants: don't know what else to suggest, stick around and someone will be along sooner or later
[05:24] <LordPants> cool, thanks
[05:28] <LordPants> I actually only had a minute to ask, but I'll be back later
[05:28] <LordPants> thanks again
[07:43] <iceroot_> do we have something at the moment like ssh -X, rdesktop, vnc specially for mir? so that i can share the view and controls from another pc?
[07:44] <iceroot_> and what is a way to configure the display with specific resolutions if udev is failing? something like /etc/X11/xorg.conf
[11:50] <kelly> hello guys, i'm using Ubuntu 13.10 64bit, how can i set up keyboard shortcut , i want to use alt+shift to change between English and French
[11:51] <erle-> will ubuntu 13.10 have gnome 3.10?
[11:51] <bazhang> is there a 3.10?
[11:51] <erle-> it will come on september
[11:51] <bazhang> no
[11:52] <ObrienDave> bazhang==> yes, it's a pre-release. not officially supported yet
[11:52] <erle-> the schedule was always this way, bazhang
[11:52] <erle-> its an exception that ubuntu this time does not have 3.8 still
[11:52] <bazhang> ObrienDave, but not part of standard ubuntu gnome
[11:52] <erle-> the release cyle of ubuntu is synct to the release cycle of gnome
[11:52] <erle-> gnome is released always a month before
[11:53] <bazhang> erle-, always being the last couple of cycles
[11:53] <erle-> no, the whole point of the april and october dates is that gnome is released a month before
[11:53] <erle-> and fedora does a similar thing by the way
[11:58] <kelly> i installed gnome-tweak-tool and set "alt+shift" to change layout but still does not work, any idea
[11:58] <kelly> also i used before setxkbmap -option grp:switch,grp:alt_shift_toggle,lv3:ralt_alt
[12:05] <BluesKaj> 'Morning folks
[12:34] <erle-> looks like saucy has gnome3.8
[12:34] <bazhang> correct
[14:10] <LarsN> is it possible to kill the "monitor my mouse battery" function?
[14:11] <LarsN> I'm not sure why but my Logitech MX Anywhere seems to think it's constantly at 1% power and the popups redefine annoying.
[14:14] <DJones> LarsN: Looks like its a known bug anyway https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1103064 the last few comments talk about logitech mice showing 1%, seems to suggest that fix has been released
[14:16] <LarsN> DJones: fixed 2 days ago.  Alright I could buy that. :)
[14:17] <LarsN> DJones: I think I looked at that same bug, about a week ago.
[14:17] <DJones> Heh, always assuming the fix filters down :)
[14:21] <diogobaeder> Hi guys, just out of curiosity, is anyone working on getting these guys fixed?: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1212025 https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1221161
[14:31] <agrester> Hello, yesterday I upgrade from 13.04 to 13.10 and some things are a bit off: many application menu
[14:32] <agrester> mistype, the things that are off are: application menus are not in the top panel when maximized, the dash doesn't have any scopes on the bottom list just one and other issues, how can I do a full reset of Unity to fix this?
[15:45] <johnjohn101> BETA 1 today!! yippeee
[16:09] <rymate1234> Yay
[16:12] <johnjohn101> i guess i'll upgrade my 13.04 system in a week or so
[20:10] <xubuntu-fanatic> i have installed xubuntu 13.10 beta 64bit and i can't find ia32-libs package why ?  Does it means that i will not be able to run steam and other 32bit apps
[20:35] <genii> So long as multiarch-support is installed you should be fine.
[21:48] <johnjohn101> oh i reread the schedule. I guess for ubuntu we're not at beta but for the optional flavors we are?


[07:59] <tamaroth_web> fossfreedom: hmm, it's not there :( I tried installing it also through apt, but it's not on the list either, probably missing some ppa or something
[08:00] <fossfreedom> tamaroth_web, you need to enable our backports ppa and update - budgie-welcome - recommendations
[08:02] <tamaroth_web> yeah, that did the trick, thank you so much :)
[08:03] <tamaroth_web> need to relog then, thanks again


[17:18] <alephant> Hi all!
[17:19] <alephant> Can I use output redirection in an upstart script, e.g. /bin/fnord >> /var/log/fnord.log?
[17:19] <alephant> Or is my only option /dev/console and thence to syslog?


[08:22] <apw> leitao, the module list for the previous abi ?
[10:20] <maximk> Anyone here interested in aarch64 kernel panics on ubuntu 16.04 kernel running on APM Mustang?
[10:31] <cascardo> launchpad is
[10:31] <cascardo> :-)
[10:40] <maximk> cascardo: any link with pointers?
[11:22] <cascardo> maximk: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
[11:22] <maximk> cascardo: thanks
[14:21] <PaulePanter> Hi. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc2/
[14:22] <PaulePanter> The packages from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc2/ do not install under Ubuntu 16.04.4 LTS, as `linux-update-symlinks` is not found.
[14:56] <apw> problematic indeed
[14:58] <apw> PaulePanter, would you file a bug against linux-base for me, so i remember to think about it, post the bug number here for me
[15:10] <PaulePanter> apw: I’ll try to do it today.
[17:03] <Gargravarr> tyhicks: just wanted to say thank you very much for your help with 1759920, installed 4.4.0-121 this morning after running -119 for a week or two, machine is stable and sssd is working :)
[17:03] <tyhicks> Gargravarr: that's great to hear - thanks for letting us know :)
[17:05] <Gargravarr> now we look forward to the next incomprehensible microcode+auth system-freeze :)
[17:12] <tyhicks> ugh, don't jinx it
[17:13] <Gargravarr> surely a jinx is when you say something and the opposite happens, so by saying it, i have actually jinxed it NOT to happen? :D
[18:27] <LocutusOfBorg> jsalisbury, the patch for the acer key button seems to be in the approved upstream queue, I don't know the merge window, but should go mainline soon(TM) thanks for the help! I hope bionic new kernel will be uploaded soon too :)
[19:12] <jsalisbury> LocutusOfBorg, Yeah, I'm going to SRU the commit, so it's in Ubunutu and not have to wait for it to make it's way through stable.
[19:59] <stgraber> ogasawara: any known problems with the fan using vxlan on 18.04?
[20:00] <ogasawara> stgraber: not that I am aware.  smb ^^
[20:00] <ogasawara> stgraber: if you are seeing a problem, please do file me a bug and we'll chase
[20:01] <stgraber> doing some more tests to figure out what's going on, maybe it's just our fault (lxd), will file a bug after I dig some more
[20:02] <ogasawara> stgraber: ack
[20:07] <stgraber> doh, looks like broken logic on our side, miscalculating IPs
[20:08] <stgraber> shows that we have a total of 0 users using that particular function in LXD networking then :)


[20:08] <sudip> Can anyone please mark LP: #2024325 as affecting Jammy
[20:08] -ubottu:#ubuntu-bugs- Launchpad bug 2024325 in trac (Ubuntu) "trac crashes while importing a library in Ubuntu 20.04 (ImportError: cannot import name 'soft_unicode' from 'jinja2.utils')" [Undecided, Confirmed] https://launchpad.net/bugs/2024325
[20:31] <rbasak> Done
[20:49] <sudip> thanks rbasak
[20:53] <sudip> and LP: #2040059 as affecting Mantic please
[20:53] -ubottu:#ubuntu-bugs- Launchpad bug 2040059 in sagemath (Ubuntu) "Sage crashes on start due to a missmatched dependency" [Undecided, Confirmed] https://launchpad.net/bugs/2040059
[21:02] <rbasak> Done
[21:02] <sudip> thanks rbasak
[21:03]  * sudip now has lots of bugs in hand and stops bug hunting (for now)
[21:04] <sudip> rbasak: one doubt about LP: #2040059, what will be the status of the main bug for that? sagemath is not available in Noble
[21:04] -ubottu:#ubuntu-bugs- Launchpad bug 2040059 in sagemath (Ubuntu) "Sage crashes on start due to a missmatched dependency" [Undecided, Confirmed] https://launchpad.net/bugs/2040059


[09:20] <amano> didrocks, did you see https://bugzilla.gnome.org/show_bug.cgi?id=787940
[09:22] <amano> I guess that this will land in 3.26.1 rather than 3.28 (it is in master now, but there is no 3.26 branch for gnome shell yet).
[09:24] <amano> Maybe you will have to tweak the dock a bit one last time to adapt to this change.
[13:44] <duflu> Trevinho, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323
[14:01] <seb128> andyrock, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679
[14:02] <seb128> andyrock, try to rmmod vboxvideo
[15:12] <jamesh> kenvandine: https://github.com/jhenstridge/xdg-desktop-portal/commit/d3a243e32c20f1a29958c27fe61d2041fc4c0fac <- here's the code I was using to add snap detection to xdg-desktop-portal
[15:13] <jamesh> that's getting the label from D-Bus.  Reading it from /proc/$PID/attr/current should be just as good
[15:13] <kenvandine> Trevinho, ^^
[15:18] <Trevinho> thanks
[15:45]  * Trevinho c-lobrano: hey, did
[15:46] <Trevinho> c-lobrano: hey, since you fixed the issue with entries borders, maybe you can also have  a look to the switcher border? Basically we've the background being outside the border
[15:46] <Trevinho> mangify it to see :)
[15:47] <c-lobrano> Trevinho: hi! Sure, is there a bug already?
[15:49] <Trevinho> c-lobrano: it's not opened yet I believe (Laney bugged me in person) :), but this one:  https://usercontent.irccloud-cdn.com/file/CZYo0pdC/
[15:49] <c-lobrano> Trevinho: alright, I'll have a look a that
[15:56] <Trevinho> c-lobrano: thans
[15:56] <Trevinho> ks*
[15:56] <Trevinho> Laney: approve :) https://code.launchpad.net/~3v1n0/ubuntu-themes/headerbars-as-titlebar-children-fix/+merge/331242
[16:00] <c-lobrano> Trevinho: from where does that switcher come?
[16:00] <Trevinho> c-lobrano: in gnome control center
[16:01] <Trevinho> c-lobrano: or just any switcher in an headerbar
[16:01] <c-lobrano> ook
[16:08] <ximion> Laney: I resolved LP: #1719077 at least partially - PK was still querying app-install-data and sometimes failing at that, which caused all kinds of what-provides searches to fail as well
[16:08] <ximion> not sure if this qualifies for Artful, if so, I'd file a sync request for the Debian package which resolves this
[16:09] <ximion> question is: will Artful ship with PK as default in GNOME Software?
[16:12] <c-lobrano> Trevinho: just to track it https://bugs.launchpad.net/ubuntu-themes/+bug/1719355
[16:12] <Trevinho> c-lobrano: thanks a lot :)
[16:13] <c-lobrano> thank you, I was kind of bored at work today :D
[16:26] <Laney> ximion: yes
[16:26] <Laney> and hi!
[16:26] <Laney> what's new in 1.1.7?
[16:26] <Laney> if just fixes, we can sync that
[16:27] <ximion> Laney: hi :D :)
[16:27] <ximion> Laney: it's just fixes, and most of them were already cherry-picked into the 1.1.6 package anyway
[16:28] <ximion> and yes, if PK is default in Artful, you'd definitely want that release
[16:29] <ximion> FTR https://github.com/hughsie/PackageKit/blob/master/NEWS#L1-L30
[17:02] <jbicha> Laney: could you bump your ostree badtest hint to 2017.11-2ubuntu1 ? it's blocking gnome-builder 3.26
[18:02] <seb128> andyrock, https://bugs.launchpad.net/ubuntu/+source/eog/+bug/938751
[18:03] <seb128> andyrock, xprop -root -remove _ICC_PROFILE
[18:03] <seb128> and try again
[18:11] <ximion> Laney: LP: #1719384 exists now
[18:11] <ximion> (the Ubuntu bug numbers got pretty high, wow!)
[18:12] <ximion> I wonder whether there are other issues that actually have a higher priority for Ubuntu, e.g. apparently PK doesn't automagically support your phased updates
[18:14] <Laney> we're not using PK for updates right now
[18:14] <Laney> at least not from GS
[18:18] <jamesh> ximion: launchpad bug numbers are global for all projects on the system.  Also, not all numbers refer to an actual bug
[18:18] <jamesh> (it's a PostgreSQL sequence, so IDs get consumed even if a transaction gets rolled back)
[18:19] <ximion> right, I forgot that they are shared by every single project
[18:25] <jibel> seb128,https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719390
[18:30] <ximion> Laney: I wonder what you'll do when aptd is fully replaced
[18:31] <ximion> (if that is actually the plan)
[18:34] <Laney> heh
[18:34] <Laney> one day ... maybe
[18:35] <ximion> it will be offline-updates with GNOME Software vs. the updater in GNOME PackageKit, I guess
[18:35] <Laney> we could maybe impelement an online updates plugin
[18:35] <Laney> just synced PK
[18:35] <Laney> thanks for the upload!
[19:04] <flexiondotorg> Yo kenvandine
[19:09] <seb128> tkamppeter, https://bugzilla.gnome.org/show_bug.cgi?id=786077
[19:13] <casey> Laney: Hi, I reported about two weeks ago how gnome-software seemed to list OS updates and provide a "restart and install" option despite PK being disabled. I cannot seem to reproduce this systematically (it's happened only once since), and at any rate it has only happened *after* an update
[19:15] <casey> One guess would be that the updates section is somehow reading from packagekit-history
[19:15] <Laney> hi casey
[19:15] <casey> but at any rate I can't provide any definite answers at this point unfortunately
[19:15] <Laney> alright, no worries
[19:16] <Laney> you can modify /etc/xdg/autostart/gnome-software-service.desktop to add --verbose so that if it happens again we might get some logs
[19:16] <casey> ok.
[19:16] <casey> where would that log to?
[19:17] <Laney> to the journal
[19:18] <casey> ok, sounds good
[20:11] <jackpot51> I have added a patch for https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323 - can someone take a look?
[20:13] <Laney> jackpot51: it'd be best to ask #gnome-shell IMO
[20:14] <Laney> oh you did!
[20:14] <jackpot51> I did, I hope you saw!
[20:14] <Laney> ♥
[20:14] <jackpot51> :)
[20:32] <jackpot51> Any thoughts about having my debdiff in the meantime Laney?
[20:33] <Laney> not competent enough to assess it
[20:33] <Laney> maybe Trevinho is, otherwise I prefer to wait for Jonas
[20:33] <jackpot51> Ok.
[20:33] <Trevinho> I can check
[20:35] <Laney> :>
[20:36] <jackpot51> Thanks Trevinho!
[20:37] <Trevinho> jackpot51: I've seen that there are also other fixes Jonas was working on for migrating the settings
[20:37] <Trevinho> so it might make sense to get all in that patcheset
[20:44] <jackpot51> Cool, looks like Jonas saw the bug. There was another one already fixed in upstream mutter with having to select the scale setting twice before it took in gnome-control-center
[20:45] <Laney> nice
[21:26] <jackpot51> Laney: can we get these patches into Ubuntu now?
[21:26] <jackpot51> Thanks for pushing btw!
[21:31] <jbicha> jackpot51: just mutter?
[21:32] <jbicha> jackpot51: are you aware of the release schedules? Ubuntu Final Beta is this week so we're freezing and GNOME 3.26.1 is scheduled for next week
[21:34] <jackpot51> I was not aware of GNOME's release schedule. Yes, just mutter. There is an issue fixed in upstream mutter but not in Ubuntu where the scale must be set twice in the gnome-control-center before applying
[21:36] <jackpot51> Even if it has not been officially released, I strongly believe the master mutter is an improvement over the current 3.26.0 + one cherry picked commit currently in Ubuntu
[21:36] <jbicha> I could package a git snapshot of mutter but I'd like to get someone else on the Desktop Team to approve that. Otherwise, it will be fixed next week
[21:36] <jackpot51> Sounds good
[21:38] <jbicha> btw, https://wiki.gnome.org/ThreePointTwentyfive
[21:38] <jbicha> https://wiki.ubuntu.com/ArtfulAardvark/ReleaseSchedule
[21:41] <jackpot51> Thanks jbicha. The GNOME I need to look at
[21:42] <dmj_s76> jbicha: if you're packaging mutter, it would be very good to get these packages (already in upstream trunk): https://bugzilla.gnome.org/show_bug.cgi?id=787477
[21:44] <dmj_s76> Upstream has fixed a bug in mutter that prevents gnome-control-center from setting scaling right.
[21:44] <dmj_s76> /s/packages/patches
[21:47] <seb128> Laney, list row { background-color: white }
[21:48] <jbicha> seb128: do you have an opinion on packaging a git snapshot of mutter now? ^
[21:52] <seb128> jbicha, +1
[21:52] <seb128> it might also fix the external monitor config issue
[21:52] <seb128> need to go, bbl
[21:52] <jbicha> thanks, have a good evening
[21:53] <Laney> I'd do it via exp if it were me
[21:53] <Laney> those bugs affect debian too
[21:53] <Laney> laters
[21:54] <jbicha> yes that was my plan
[21:54] <jackpot51> Sweet!
[21:55] <seb128> jbicha, thanks, have a nice evening as well
[22:15] <jbicha> jackpot51: do you happen to know of any specific LP bug #s fixed in mutter git?
[22:19] <jackpot51> No, but I could create one.
[22:19] <jackpot51> The issue I have found fixed with mutter git is changing the scale factor in gnome-control-center
[22:21] <jackpot51> It has to be changed twice before taking effect
[22:22] <jbicha> it's fine, I don't think we need a bug number now but if we had one I wanted to mention it in the debian/changelog entry
[22:22] <jackpot51> Ok, thanks
[22:22] <jackpot51> It may be useful to link to this: https://bugzilla.gnome.org/show_bug.cgi?id=787477
[22:23] <jackpot51> It was also mentioned here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/comments/8
[22:24] <dmj_s76> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717272
[22:25] <dmj_s76> I believe this is a bug reporting the gnome-control-center issue that the mutter patches fix.
[22:25] <jbicha> ok, I'll mark 1717272 as fixed in this upload and y'all can reopen if it's not actually fixed
[22:25] <jackpot51> Thanks!
[22:25] <jbicha> since I don't have a hidpi screen I can't test it very well
[22:26] <jackpot51> Do you want one? Send me an email and I can see about hooking you up
[22:29] <jackpot51> This might also be fixed: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700085
[22:30] <jackpot51> There are quite a few: https://launchpad.net/+search?field.text=scale+gnome-control-center+2017&field.actions.search=Search
[22:31] <jbicha> ok, we'll try to get the new version into Ubuntu some time tomorrow (it takes several hours because it comes via Debian)
[22:32] <jbicha> I already finalized the changelog
[22:32] <jackpot51> Thanks!


[03:08] <c2tarun> anyone looked at #bug 685711
[03:08] <ubot2> Launchpad bug 685711 in openjdk-6 (Ubuntu) "jvm exit (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/685711
[03:41] <^arky^> hi jcastro
[03:54] <c2tarun> are there any defined coding standards for source codes (except proper indentation) that one has to follow before uploading a package??
[03:55] <greg-g> c2tarun: I don't know the answer to that question, but #ubuntu-motu would
[03:56] <c2tarun> greg-g: so i should repost this question in #ubuntu-motu??
[03:57] <greg-g> yep
[03:57] <c2tarun> greg-g: ok thanks :)
[08:35] <rallias> Has anyone else noticed the bug in gnash that when one applet crashes they all crash?
[11:45] <TVT> Hi!
[11:47] <TVT> Did anyone succeed in connecting to Bluetooth PAN network in Ubuntu 10.10 ?
[11:50] <TVT> After I've upgraded from 10.04 to 10.10 I cannot do that:
[11:50] <TVT> tvt@ubuntu:~$ sudo pand -c '00:17:9A:3F:49:66' -n
[11:50] <TVT> pand[9065]: Bluetooth PAN daemon version 4.69
[11:50] <TVT> pand[9065]: Connecting to 00:17:9A:3F:49:66
[11:50] <TVT> pand[9065]: Connect to 00:17:9A:3F:49:66 failed. Permission denied(13)
[11:51] <TVT> I always have "Permission denied" message.
[12:24] <c2tarun> what is bitesize??
[12:28] <nisshh> c2tarun, small, tiny, miniscule, etc :)
[12:28] <nisshh> c2tarun, bitesize is a term from eating food, it means one mouthful :)
[12:28] <c2tarun> what is its reference to launchpad bugs??
[12:29] <nisshh> c2tarun, its a new bug program, so people find it easier to fix small bugs
[12:29] <nisshh> fix/triage/etc
[12:30] <c2tarun> can u please suggest me some small bugs to work on.
[12:30] <nisshh> c2tarun, do you have a mentor in the bugsquad?
[12:31] <c2tarun> nope. i requested but never assigned one. :(
[12:31] <nisshh> c2tarun, i see
[12:31] <nisshh> vish, ^^^^^
[12:32] <nisshh> c2tarun, how long ago did you request one?
[12:32] <c2tarun> may be a week ago
[12:32] <nisshh> ok
[12:33] <c2tarun> how can i have a mentor??
[12:34] <nisshh> c2tarun, well, you just need to request one really, but it may be the case that there are not any mentors able to take on new people at the moment
[12:34]  * nisshh looks at the wiki
[12:34] <c2tarun> hmmm......
[12:36] <nisshh> c2tarun, https://wiki.ubuntu.com/BugSquad/Mentors <-- read the part about requesting a mentor, ensure you meet the requirements
[12:37] <c2tarun> nisshh: i m sorry to say but i signed the ubuntu code of conduct today only :(
[12:37] <nisshh> c2tarun, ah ok
[12:39] <c2tarun> should i request again???
[12:41] <nisshh> c2tarun, hmmm, as long as you meet the requirements, yeah, although i pinged vish a minute ago, he is an admin for the mentorship program
[12:41] <nisshh> he should be able to help you, but he doesnt appear to be around right now
[12:42] <c2tarun> ok, i'll wait for wish
[12:42] <c2tarun> sorry vish
[12:54] <c2tarun> nisshh: i think i should apply for mentor again.  last time i did by some subscription. the page you gave me has some diff method for requesting + in list of students waiting i cant see my name. can u please tell me how to create my ubuntu wiki page
[12:55] <c2tarun> nisshh ....
[12:55] <nisshh> c2tarun, sure, i dont think that list of waiting students is used
[12:55] <nisshh> c2tarun, sorry if i take a minute to reply, im being pinged in 4 channels currenty :)
[12:56] <c2tarun> sure :) u are a busy guy. in step 2 i have to setup my ubuntu wiki page. how can i do that??
[12:58] <nisshh> c2tarun, to create your own wiki page, just go to say wiki.ubuntu.com/MyName and there is an option there to create the page if it doesnt exist
[12:58] <c2tarun> MyName should be my real name of my id
[12:58] <nisshh> c2tarun, for example, heres mine: https://wiki.ubuntu.com/RyanMacnish
[12:58] <nisshh> c2tarun, it doesnt really matter, but most people use their real name
[12:58] <nisshh> some use their launchpad id though
[12:59] <nisshh> or IRC nick
[12:59] <c2tarun> ok i'll use my IRC nick as my launchpad id and irc nick are same
[13:00] <nisshh> sorry? that didnt make any sense :)
[13:00] <c2tarun> should i use the BugSquad template??
[13:00] <nigelb> You'd find that CamelCase wiki names are easier to link
[13:00] <nisshh> +1 nigelb
[13:01] <nisshh> c2tarun, just have a section about you, list your available hours and stuff, and maybe your irc nick and launchpad page
[13:01] <nisshh> c2tarun, it doesnt have to be flashy or anything
[13:05] <nigelb> c2tarun: here's an example wiki https://wiki.ubuntu.com/BeginnersTeam/Membership/BTWikiGuide
[13:06] <c2tarun> nigelb: thanks i was looking for it only
[13:06] <nisshh> nigelb, i was looking for the link that shows you how to create your own wiki page, but i cant find it :)
[13:10] <nigelb> nisshh: Yeah, I just look for the BT one which is generally pretty good :D
[13:12] <nisshh> nigelb, cool, ill remember that :)
[13:31] <c2tarun> nisshh: can u please take a look at this page... https://wiki.ubuntu.com/c2tarun
[13:35] <nisshh> c2tarun, sure
[13:36] <nisshh> c2tarun, yeah, thats good, just add the times in UTC time that you are available for the bugsquad and also which timezone you are in :)
[13:37] <c2tarun> what is UTC??
[13:37] <reventon_> has anybody been able to get unity working in virtual box on 11.04 alpha 1? i have 3d acceleration enabled, but when i try the normal desktop option at login it throws an error saying i don't have 3d support and just loads the normal desktop
[13:38] <nisshh> c2tarun, GMT time
[13:38] <reventon_> trying to figure out if i should report this
[13:41] <c2tarun> how can i check my UTC
[13:43] <nisshh> c2tarun, UTC is a timezone, you will be in a timezone, just list on your wiki page what times you will be available
[13:45] <charlie-tca> reventon_, it will not work in Virtualbox
[13:45] <charlie-tca> andol, no, it is not a valid bug
[13:46] <reventon_> so its a vbox issue. any idea if it works in vmware/parallels?
[13:47] <charlie-tca> To the best of my knowledge, it fails in all virtual machines
[13:48] <c2tarun> nisshh: can u please take a look again... https://wiki.ubuntu.com/c2tarun
[13:48] <andol> charlie-tca: Think that as the second time recently you had an completion fail on my nickname :)
[13:49] <charlie-tca> Sorry, andol
[13:50] <charlie-tca> fixed that issue, I think
[13:51] <andol> np
[13:55] <nisshh> c2tarun, sure
[13:56] <nisshh> c2tarun, yeah, that will do
[13:56] <c2tarun> can you please check that time i mentioned is correct.
[13:57] <nisshh> c2tarun, what do you mean by correct?
[13:57] <c2tarun> correct means i mentioned the time i'll be free according to my local time.
[13:58] <c2tarun> is it correct or i should write something else too.
[13:59] <nisshh> c2tarun, well, you should say "ill be available from such and such UTC to such and such UTC"
[14:00] <c2tarun> that is what i m not getting UTC means my local time of GMT time
[14:01] <nisshh> c2tarun, UTC is GMT time, they are just different names for the same thing, your local time is different
[14:01] <c2tarun> ok
[14:49] <hrw> hi
[14:50] <hrw> can someone set importance: high for bug 684625? It is mine, I have a fix for it and it is scheduled for review
[14:50] <ubot2> Launchpad bug 684625 in gcc-4.5 (Ubuntu) (and 2 other projects) "libc6 is compiled for armv5 instead of armv7a (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/684625
[17:06] <vish> pedro_: heya, so are we approving new members to the BS-mentor group or the new BS-mentor-alpha group?
[17:06] <vish> argh, that doesnt sound right. ok … no more shortening BugSquad
[17:06] <micahg> heh
[17:10] <vish> nisshh: thanks, c2tarun seems to have applied only now for the mentor team. there is another new team for BugSquad mentoring which is not one-on-one , so once pedro_ gives the order, we'll approve c2tarun. :)
[17:10] <nisshh> vish, oh cool, i didnt know about a new mentoring team, whats different about it?
[17:11] <vish> nisshh: 5 mentors to mentee
[17:11] <nisshh> vish, 5 mentors _per_ mentee!?
[17:12] <daker> hello devildante ツ
[17:12] <vish> nisshh: not _per_ , but can be at times , when there is only one mentee.. its more of a collective group being responsible for a mentee
[17:12] <devildante> hi daker :)
[17:13] <nisshh> vish, oh i see, sounds cool :)
[17:13] <daker> hello nisshh vish ツ
[17:13] <nisshh> vish, so will this replace the existing mentor program? or compliment it?
[17:13] <nisshh> hey there daker
[17:13] <vish> hey daker :)
[17:14] <vish> nisshh: well, its still in trial phase , so not yet decided..
[17:14] <nisshh> daker, im coding up a website :)
[17:14] <nisshh> vish, fair enough
[17:14] <daker> nisshh, for the ubuntu dev man ?
[17:15] <nisshh> daker, no, actually, that will be in the ubuntu.com namespace
[17:15] <nisshh> daker, but i have never done much web dev, so it will be interesting to see what i come up with :)
[17:16] <daker> nisshh, just tell me i you want some help ツ
[17:17] <nisshh> daker, nah, i should be ok, i know html, css and javascript, its more a challenge for my lame design skills :)
[17:17] <nisshh> thanks for offering anyway :)
[17:18] <daker> nisshh, yw
[17:18] <nisshh> :)
[17:18] <nisshh> daker, ill have to show you and see what you think once its done :)
[17:19] <daker> nisshh, ok
[17:22] <daker> devildante, ubuntu-ma is about to die :s
[17:22] <devildante> daker: I'm coming to the rescue :p
[17:25] <nisshh> daker, ubuntu-ma being which loco?
[17:25] <devildante> nisshh: for morocco
[17:25] <daker> yep
[17:25] <daker> nisshh, slow death
[17:26] <nisshh> ah, yes, ive heard about that one
[17:26] <devildante> daker: don't you think we should attract more people?
[17:27] <nisshh> daker, devildante, my loco, ubuntu-au is currently trying to get reapproved
[17:27] <nisshh> :)
[17:27] <devildante> nisshh: great :)
[17:27] <nisshh> :)
[17:29] <daker> devildante, i am doing all the necessary, starting from the wiki to animate the facebook group
[17:29] <devildante> daker: super-great
[17:30] <daker> devildante, i guess you are not on facebook
[17:30] <devildante> daker: nope
[17:33] <Ynot_82> Hi all, looking for advice
[17:33] <Ynot_82> I've filed a bug that deals with a generic packaging problem
[17:33] <Ynot_82> Bug affects an unknown number of upstream applications
[17:33] <Ynot_82> Currently there's only a single upstream associated with the bug
[17:34] <Ynot_82> Is there a generic "packaging" category that I can associate the bug with?
[17:34] <Ynot_82> (Just FYI - https://bugs.launchpad.net/ubuntu/+source/hedgewars/+bug/685421)
[17:34] <ubot2> Launchpad bug 685421 in hedgewars (Ubuntu) "Packaging bug - Image file alteration causes issues (affects: 1) (heat: 6)" [Undecided,Confirmed]
[17:41] <micahg> Ynot_82: scour and pkgbinarymangler are your 2 packages to file against
[17:41] <micahg> oops
[17:41] <micahg> nope
[17:41] <micahg> that's for svgs
[17:45] <micahg> Ynot_82: pkgbinarymangler is one, I forget what the png optmizer is, take a look at the changelog for pkgbinarymangler
[17:45] <Ynot_82> micahg: thanks
[18:02] <c2tarun> i dont know whether it is a bug or not, but before reporting i just wanted to discuss it here. whenever i run my laptop on battery and try to play a movie, it plays smoothly in window form. but when i switch my player to full screen the smoothness goes away. movie runs a bit slower and not that good quality.
[18:03] <devildante> c2tarun: only on battery?
[18:03] <c2tarun> devildante: yup only on battery. when i plug it to power movie plays fine in window and in full screen mode
[18:04] <micahg> c2tarun: cpu scaling?
[18:05] <c2tarun> never heard of that, but my friend using lucid only with slower processor, less ram and no graphic card, never encounters such problem. is the problem with graphics driver or something??
[18:06] <c2tarun> i m using core i3 processor, with 4GB ram and 1GB ATI Radeon Graphic card
[18:06] <micahg> c2tarun: yeah,so you're probably having cpu scaling on batter power
[18:06] <charlie-tca> different hardware results in different cpu power on battery
[18:06] <micahg> gnome-power-manager might be able to fix that
[18:06] <micahg> or a panel applet
[18:07] <c2tarun> how to fix this by gnome power manager??
[18:09] <micahg> c2tarun: that's a support question, I don't use it
[18:09] <c2tarun> ok
[18:39] <bdmurray> micahg: could you look at 684858?  It might be firefox / xubuntu specific
[18:41] <micahg> bdmurray: yeah, I can look into it later tonight
[18:44] <bdmurray> pedro_: where do I find the unity team / developers?  bug 684052
[18:44] <ubot2> Launchpad bug 684052 in indicator-session (Ubuntu) "live CD does not have reboot on the power menu (affects: 1) (heat: 6)" [High,Triaged] https://launchpad.net/bugs/684052
[18:44] <pedro_> bdmurray, #ubuntu-desktop
[23:35] <CarlFK> sudo apt-get install atftp ... Err http://us.archive.ubuntu.com/ubuntu/ natty/universe atftp i386 0.7.dfsg-9.2
[23:35] <CarlFK>   Something wicked happened resolving 'fe80::208:2ff:fea0:abcf:8000' (-9 - Address family for hostname not supported)
[23:35] <CarlFK> I am not trying to do ipv6
[23:36] <CarlFK> it is a mostly vanilla natty install with squid-deb-proxy-client
[23:37] <CarlFK> which I am guessing is where the bug is, but would like someone to confirm
[23:46] <CarlFK> http://dpaste.de/Kxxr/  all of apt-get spew


[16:30] <tyhicks> hello
[16:30] <mdeslaur> hello
[16:30] <tyhicks> #startmeeting
[16:30] <meetingology> Meeting started Mon Aug  8 16:30:57 2016 UTC.  The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:30] <meetingology> Available commands: action commands idea info link nick
[16:31] <tyhicks> The meeting agenda can be found at:
[16:31] <tyhicks> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:31] <tyhicks> [TOPIC] Weekly stand-up report
[16:31] <tyhicks> jdstrand: you're up
[16:31] <jdstrand> hi!
[16:31] <jdstrand> transitional browser-support interface has landed in upstream (chrome/chromium/electron/firefox)
[16:31] <jdstrand> system-trace interface and /usr/src mounting has landed in upstream (bcc)
[16:31] <jdstrand> dbus-app has been reviewed and still in progress. will be working on that this week
[16:31] <jdstrand> snappy PR reviews. Notably, pluggable-storage, zigbee-dongle, docker and lxd
[16:32] <jdstrand> I'm working on pluggable-storage right now
[16:32] <jdstrand> there are various others I've gotten pings on
[16:32] <jdstrand> review tools updates related to browser-support and os snap
[16:32] <jdstrand> I think between all that and various iterations on existing PRs of mine, that's it for me
[16:33] <jdstrand> but if not, I'll start to look at CLONE_NEWUSER vs snap-confine and/or snap-confine with os mounts
[16:33] <jdstrand> that's it for me
[16:33] <mdeslaur> I'm on community this week
[16:34] <jdstrand> (in other words, I'll go down the list in the snappy lane)
[16:34] <mdeslaur> I'm about to publish some curl updates
[16:35] <mdeslaur> and I'll be going down the cve list after that
[16:35] <mdeslaur> that's it from me
[16:35] <mdeslaur> who's next?
[16:35] <tyhicks> me
[16:35] <tyhicks> I'm on CVE triage this week
[16:35] <tyhicks> I will be assisting with some MIR review work
[16:36] <tyhicks> I'll be working on seccomp complain mode for snappy
[16:37] <tyhicks> it looks like I need to investigate AppArmor SRU autopkgtest regressions
[16:37] <tyhicks> and then maybe I'll get to some review tools work for squashfs bugs
[16:37] <tyhicks> that's it for me
[16:37] <tyhicks> jjohansen: you're up
[16:38] <jjohansen> I have a short week this week, I will be out wednesday and thursday, and maybe but hopefully not friday
[16:38] <jjohansen> I am going to finish up on my review of the gsettings apparmor work
[16:39] <jjohansen> and continue chasing a couple oopses that have surfaced in the stacking work that is supposed to fix the name lookup errors
[16:40] <tyhicks> jjohansen: are you ready to send a pull request to the kteam after those oopses are fixed?
[16:40] <jjohansen> tyhicks: hopefully, pending further testing, with lxc etc
[16:40] <tyhicks> great to hear!
[16:41] <jjohansen> thats it for /me sarnold you are up
[16:41] <tyhicks> I don't see sarnold around yet
[16:41] <tyhicks> he'll be focused on MIRs this week (he's in the happy place)
[16:41] <tyhicks> chrisccoulson: go ahead
[16:42] <chrisccoulson> I've got Chromium to sponsor this week
[16:43] <chrisccoulson> I also want to finish off my instructions for updating Flash (I did start that, but just haven't finished it off yet)
[16:44] <chrisccoulson> I spent quite a bit of time last week debugging a couple of regressions in oxide, but managed to get through a few items on https://blueprints.launchpad.net/oxide/+spec/converged-device-support. I want to get through a few more this week
[16:44] <chrisccoulson> And also have a play with snappy
[16:44] <chrisccoulson> That's me done
[16:44] <sarnold> heh tyhicks could stand in for my reports :) happy place, MIRs, and also snapping a snap with snapcraft for snap and snapd on snappy ubuntu core. I'll try to make it snappy. (Get it? alligator sandwich?)
[16:45] <tyhicks> :)
[16:45] <tyhicks> thanks
[16:46] <tyhicks> [TOPIC] Highlighted packages
[16:46] <tyhicks> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:46] <tyhicks> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:46] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/sblim-sfcb.html
[16:46] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/macopix.html
[16:46] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/gamera.html
[16:46] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/t-coffee.html
[16:46] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/lsyncd.html
[16:46] <tyhicks> [TOPIC] Miscellaneous and Questions
[16:46] <tyhicks> Does anyone have any other questions or items to discuss?
[16:48] <sarnold> heh, "gamera"... "gamera is really neat! gamera is filled with meat!"
[16:49] <mdeslaur> lol
[16:49] <tyhicks> jdstrand, mdeslaur, jjohansen, sarnold, ChrisCoulson: Thanks!
[16:49] <tyhicks> #endmeeting
[16:49] <meetingology> Meeting ended Mon Aug  8 16:49:31 2016 UTC.
[16:49] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-08-08-16.30.moin.txt
[16:49] <mdeslaur> thanks tyhicks !
[16:49] <jjohansen> thanks tyhicks
[16:50] <sarnold> thanks tyhicks!
[16:59] <jdstrand> tyhicks: thanks!
[17:00]  * genii washes out the coffeepot
[17:03]  * DJones hands genii this https://i.ytimg.com/vi/JYggqDHbW2k/maxresdefault.jpg
[17:04] <genii> DJones: Hehe, yesssss!
[17:25] <tsimonq2>  /ts
[17:25] <tsimonq2> whoops sorry


[00:33] <k1l> Happy new year
[01:06] <bazhang> same to you k1l !
[01:06] <bazhang> we finally got chu to switch distros to spacemacs
[01:06] <k1l> :)
[01:07] <dax> oh did you see bazhang?
[01:07] <dax> there's a spacevim
[01:07] <bazhang> vim and emacs all in one glorious bundle
[01:07] <dax> https://github.com/ctjhoa/spacevim
[01:07] <bazhang> thats hilarious!
[01:26] <chu> Lol
[02:10] <hggdh> I think glory would be a vim plugin to give one the emacs default key bindings
[02:10] <hggdh> vemacs? vimacs?
[02:17] <bazhang> best would be to time travel to the moment before emacs was created
[02:17] <bazhang> and give rms an iphone
[02:18] <bazhang> thus striking a blow against emacs and apple!
[02:19] <hggdh> and automgically givving poor rms a stroke, I guess
[02:39] <bazhang> 'good fstab'
[02:39] <bazhang> is there a bad one?
 linux is the worst shit ever
[02:45] <bazhang> I wanna try the updating root again
[02:46] <bazhang> this cannot end well
[03:13] <k1l> @btlogin
[03:14] <k1l> @whoami
[03:15] <Menzador> @whoami
[05:05] <Menzador> Happy 2017!
 this network is a bait/entrapment/sting platform doing law enforcement or vigilante work. (ETHICALLY CORRUPT)
[23:17] <valorie> @login
[23:17] <valorie> @btlogin
[23:17] <valorie> hmmm
[23:17] <valorie> @btlogin
[23:18] <valorie> ubottu: help
[23:18] <valorie> ubottu: help login
[23:18] <valorie> ubottu: help btlogin
[23:19] <k1l_> doesnt work for me, too
[23:20] <valorie> oh, it finally did when I looked at what ubottu was telling me in a PM
[23:22] <valorie> huh, but the bantracker isn't searching for me
[23:23] <elky> the bantracker searches can be quite finicky
[23:24] <elky> what are you trying to find?
[23:24] <valorie> I'll keep futzing with it
[23:24] <valorie> for now
[23:24] <valorie> Review: ban<EMAIL_ADDRESS>set on Sat Dec 24 04:02:22 2016 in #kubuntu, link: https://ubottu.com/bans.cgi?log=75223
[23:25] <dax> putting <IP_ADDRESS> in the Search: box and hitting search works fine for me
[23:26] <valorie> that one did work indeed
[23:26] <k1l_> @btlogin