[07:06] <vishalrao> hello. is ubuntu-mobile only meant for ultra-mobile devices? any chance of work/support for tablet pc's and their touchscreens and fingerprint readers? i have a new hp pavilion tx1302au and i got wireless and touchscreen working with commandline tinkering. still researching possibilities for the authentec aes1610 fingerprint reader :)
[07:07] <pwnguin> i think the developers are focused on getting hildon running on umpc
[07:07] <pwnguin> ive been looking at it for Tablet PCs
[07:07] <pwnguin> at least what's in gutsy is not impressive
[07:08] <vishalrao> any place i can help, maybe by installing test software to collect info for developers?
[07:09] <pwnguin> the wiki has a guide
[07:09] <pwnguin> for a xephyr install
[07:59] <pwnguin> vishalrao: also, there's a debian team called FingerForce looking at fingerprint Auth
[08:00] <vishalrao> yup i have some links, currently that one too :)
[08:00] <pwnguin> vishalrao: im aiming to get a similar tool into 8.04
[08:00] <vishalrao> neat
[08:00] <pwnguin> for a different device
[08:01] <pwnguin> its already in my ppa, but it requires users to be in the root group to work perfectly at the moment
[08:01] <vishalrao> nice
[08:02] <pwnguin> beware, US developers have certain export restrictions regarding fingerprints
[08:02] <pwnguin> do umpcs have fingerprint auth tools?
[08:03] <vishalrao> right. im umpcs have auth tools in windows :)
[08:03] <vishalrao> im *sure* umpcs have...
[08:04] <pwnguin> you own one?
[08:05] <pwnguin> i dont see one on the q1u
[08:06] <vishalrao> the sony ux has one iirc
[08:07] <vishalrao> no i have a regular hp pavilion tablet pc tx1302au, just got it saturday :)
[08:09] <pwnguin> have the tablet working?
[08:13] <vishalrao> yup, tried both ubuntu gutsy rc and opensuse 10.3, both need some tweaking to get sound, wireless working. lot of work to get touchscreen working. now im interested in getting the fingerprint reader working (somehow) :)
[08:13] <pwnguin> what kind of digitizer does it use?
[08:13] <pwnguin> wacom?
[08:14] <vishalrao> some sort of "passive" one, the proc/bus/devices displays it as an "eGalax USB touchscreen"
[08:14] <vishalrao> its not very good for handwriting, just basic touch is feasible... toshibas are better with their "active" screens i guess...
[08:15] <pwnguin> my tecra is verra nice
[08:15] <pwnguin> but the hardware integration isn't there
[08:16] <pwnguin> i was hoping ubuntu mobile could produce some packages i could steal in a hurry, but they seem to be after a different kind of device
[08:16] <vishalrao> yup
[08:17] <vishalrao> really now laptop sales are (have) overtaking desktops, linux distros should try to support touch/finger/wireless as best as possible. i know vendors are not providing much hardware spec support... but some campaigning can help :)
[08:18] <pwnguin> you'd be surprised what's starting to work these days
[08:21] <vishalrao> yup, my main requirement was to get wireless working, which it does nicely using ndiswrapper. touch and finger are nice bonuses to have working... the hp tablet has a good price/feature/specs combuination which other laptops couldnt match...
[08:22] <pwnguin> im quite satisfied with the tecra m7; it's a bit expensive, but it did come with a worthy video card
[08:23] <vishalrao> what video do you have? mine is "onboard" nvidia geforce go 6150 :) runs vista aero glass fine, and i dont go gaming
[08:23] <pwnguin> quadro nvs 110M
[08:23] <vishalrao> nice
[08:24] <pwnguin> apparently it's around geforce 7300ish
[08:24] <pwnguin> and a year old
[08:24] <pwnguin> anyways, this isnt very mobileandembedded-ish
[08:24] <vishalrao> right
[08:24] <pwnguin> perhaps #ubuntu-laptop would be a place more suited to discussing the finer points of tablet PC
[08:24] <vishalrao> umpcs are all the rage these days
[08:25] <vishalrao> ah, will check that out
[08:25] <vishalrao> heh, it asks to go to plain #ubuntu for support :) very few people in there
[08:40] <dholbach> good morning
[10:48] <Peter_u2> Mithrandir, hello
[10:49] <Mithrandir> Peter_u2: hi?
[10:49] <Peter_u2> One strange gtkrc issue I don't workout.
[10:51] <Peter_u2> I add one style and setting *.wm_pm_tb_prev_bn to use that style. Then in moblin-media app, glade file use wm_pm_tb_prev_bn as id of a GtkButton. Know possible reasons?
[10:52] <Peter_u2> The style and its usage is in gtkrc.maemo_af_desktop like what we did with marquee buttons.
[10:52] <Peter_u2> Just can't work.
[10:53] <Mithrandir> I don't know much about how GTK theming works, sorry.
[10:53] <Mithrandir> maybe kwwii knows?
[10:54] <Peter_u2> kwwii, he might still not wake, I guess
[10:54] <Peter_u2> kwwii, you wakeup and lol?
[10:56] <Peter_u2> Mithrandir, thanks anyway
[10:57] <Peter_u2> Anybody here knows the gtkrc issue?
[11:28] <kwwii> Peter_u2: now I am
[11:28] <Peter_u2> kwwii, lol. Very happy you are here.
[11:29] <Peter_u2> You saw my issue description above?
[11:29] <kwwii> Peter_u2: to be honest gtkrc stuff is pretty much magic to me too
[11:29] <kwwii> I have no idea
[11:29] <kwwii> sorry
[11:29] <Peter_u2> kwwii, no need say sorry. no problem. I have sent this to mailing list to see if anyone can help.
[11:30] <kwwii> cool
[11:31] <Peter_u2> kwwii, once I get that done. I will update ume-basic theme as well.
[11:31] <kwwii> excellent
[11:35] <Peter_u2> you know when is it time to add ume-basic to gutsy repository?
[11:36] <Mithrandir> Peter_u2: it's not going in.  Too late.
[11:37] <Mithrandir> we'll add it in hardy
[11:37] <Peter_u2> Mithrandir, get it. That's fine.
[11:39] <Peter_u2> Mithrandir, neither not for libtelepathy, right? I didn't see upgrade for libtp neither.
[11:40] <Mithrandir> yeah, sorry, I didn't get around to getting it in.
[11:41] <Peter_u2> Mithrandir, no problem. what's the quickest possible time to begin hardy circle?
[11:42] <Peter_u2> s/circle/cycle
[11:45] <Mithrandir> Peter_u2: the next release usually opens sometime during the UDS, between one and two weeks after release.
[11:48] <Peter_u2> When is gutsy released? I assume currently it's just code freeze stage
[11:49] <pwnguin> the schedule suggests the 18th
[11:50] <Peter_u2> pwnguin, good. Thanks.
[11:53] <Peter_u2> where can I see such schedule info? A link is welcome
[11:56] <pwnguin> https://wiki.ubuntu.com/GutsyReleaseSchedule
[11:58] <Peter_u2> cool, pwnguin. I appreciate it.
[11:59] <pwnguin> np
[12:00] <pwnguin> does the lpia arch work well in gutsy?
[12:00] <pwnguin> ive set up a chroot and im underwhelmed so far
[12:00] <lool> pwnguin: What's the problem?
[12:00] <pwnguin> well right now
[12:00] <pwnguin> start-hildon tanks on a missing mas
[12:01] <pwnguin> whatever that is
[12:01] <lool> Yes, but it's not packaged I think
[12:01] <lool> You're not supposed to use start-hildon
[12:01] <pwnguin> ah well
[12:01] <lool> I came across the same error yesterday (and it's harmless)
[12:02] <pwnguin> and when it was working, the whole thing felt... not nearly as finished as the screenshots i'd seen. i donno if theres some theme transition or what
[12:02] <lool> pwnguin: Note that the wiki mentions custom scripts, not the one you saw here
[12:02] <pwnguin> perhaps its just that chroot doesn't cut it anymore
[12:02] <lool> pwnguin: There's a ume-xephyr-smthg script in a config package which you get when you build a fset
[12:02] <lool> pwnguin: I think you should setup a chroot via mic instead of manually
[12:03] <pwnguin> i think mic crashes on me
[12:03] <lool> pwnguin: I started the same way you did, and the results were awful
[12:03] <lool> pwnguin: What's the crash?
[12:03] <pwnguin> it locks up trying to add an fset
[12:03] <lool> pwnguin: I got this in my chroot http://people.dooz.org/~lool/ume-xephyr.png but it was nearly as expected when using mic
[12:04] <pwnguin> see, that looks nice
[12:04] <pwnguin> i just got a "zomg you dont have flash"
[12:04] <lool> pwnguin: If you start it from a terminal you should see what it's running
[12:04] <lool> pwnguin: Perhaps your choice of packages wasn't exactly the same then
[12:04] <pwnguin> perhaps
[12:04] <lool> I simply installed ubuntu-mobile to get this
[12:04] <pwnguin> huh
[12:05] <pwnguin> i wonder what i installed
[12:05] <pwnguin> because it wasnt ubuntu-mobile
[12:06] <pwnguin> maybe i just grabbed hildon-desktop thinking it was the equiv of ubuntu-desktop
[12:07] <lool> hildon-desktop is just an application handling the hildon desktop; it's not a meta-package pulling everything
[12:07] <lool> Might be the source of the confusion
[12:13] <pwnguin> well, that didnt exactly fix it =/
[12:15] <lool> pwnguin: I really recommend you try from the fset, making it work in a chroot means more manual work to repeat for you
[12:15] <pwnguin> oh, it just takes time to start =/
[12:18] <pwnguin> its not like i actually have a umpc
[12:21] <lool> Here neither :)
[12:21] <pwnguin> man, theres' gotta be some insane dbus problem or something causing this huge lag
[12:22] <pwnguin> ** (gecko:26146): WARNING **: could not start: org.moblin.media: dbus-launch failed to autolaunch D-Bus session: EOF in dbus-launch reading address from bus daemon
[12:23] <pwnguin> probably because of the chroot
[12:23] <lool> pwnguin: You did start dbus in the chroot?
[12:26] <pwnguin> i thought so
[12:27] <pwnguin> complains about NetworkManager and system-tools-backends
[12:34] <pwnguin> that's on a restart
[12:35] <pwnguin> if i just start it, nothing bad happens...
[04:58] <agoliveira> HappyCamp, sodarock, ping me when you arrive, please.
[05:03] <agoliveira> The package libgl1-mesa-dri is not installed when a Q1 fsets is selected. Is there any specific reason?
[05:04] <StevenK> I thought Mesa wasn't built on lpia
[05:04] <StevenK> If I recall
[05:05] <Mithrandir> StevenK: it is now, at least.
[05:05] <agoliveira> StevenK: Well, it is :) I didn't have direct redering on the Q1 because i915_dri.so was missing. I installed it manually and it's fine now.
[05:05] <agoliveira> (by manually I mean installing libgl1-mesa-dri)
[05:07] <StevenK> We so need to hack stylus gestures into frozen bubble
[05:07] <StevenK> That would *rock*
[06:12] <lool> Is there a way to calibrate the touch screen?
[06:13] <lool> (on the Q1)
[06:13] <agoliveira> lool: I don't know if it actually works but in the control panel there's a utility that does it.
[06:16] <lool> I'll try that in a breeze, my manual build doesn't have the control panel, let's see the dailies
[06:16] <lool> agoliveira: (thanks!)
[06:17] <agoliveira> lool: The daily (at least from yesterday) does not have either. You need to install a package... let me see...
[06:18] <lool> Does the daily have SSH?
[06:18] <agoliveira> lool: No.
[06:18] <lool> agoliveira: BTW wifi worked fine here! :)
[06:18] <lool> agoliveira: So I guess you mount the .img or the USB key and chroot + install the package in there?
[06:18] <agoliveira> lool: Here is working well too. I don't know what happened yesterday.
[06:19] <agoliveira> lool: No, I star the network and apt-get.
[06:20] <agoliveira> I just installed a image-creator image with the samsung-full-mobile-stack and it has the control-panel working.
[06:20] <agoliveira> (and the wifi works better too)
[06:20] <lool> agoliveira: Thanks for the tips
[06:20] <agoliveira> lool: My pleasure
[06:21] <lool> Did you upgrade the BIOS?
[06:21] <lool> Or rather, should i?
[06:21] <agoliveira> lool: No. I didn't.
[06:21] <agoliveira> I don't know either :)
[06:22] <lool> Do you know on what the installer is based?  Is this some preseeded d-i or is it a kind of scripted ubiquity copying the casper live tree?
[06:23] <agoliveira> lool: I beg your pardon?
[06:23] <cwong1> Mithrandir: ping
[06:24] <lool> agoliveira: The "Install" flavor of the .img: do you know which software is used to do the installation?  Is it the same software as the alternate install CD (d-i based) or the one of the live CD (casper / ubiquity based)?
[06:24] <lool> agoliveira: Indeed, wifi is better with the daily build
[06:24] <agoliveira> lool: It's just a script that does the instalation. Nothing fancy.
[06:25] <lool> agoliveira: Ok
[06:25] <lool> agoliveira: So it's based on the live FS on the USB key which is being cped; thanks
[06:25] <lool> Groumpf, screensaver also kicks in when one doesn't move the mouse on the daily build
[06:26] <agoliveira> lool: Never took a closer look but makes sense.
[06:27] <lool> Crap, panel didn't come up and WM died
[06:27] <lool> Or something died
[06:29] <lool> Arf, Ctrl Alt Backspace to the rescue
[06:30] <lool> agoliveira: I don't get the Control Panel unfortunately; it writes loading on the right top corner, then I see a small window part on the top left, and that's all :-/
[06:31] <agoliveira> lool: On the daily yu have to install something... I don't recall what it is right now but using the image-builder I get it right from beginning
[06:32] <cwong1> agoliveira: do you know anything about the Acrobat reader for gusty?
[06:33] <agoliveira> cwong1: Acrobat reader is commercial, I don't know the status in this case but you can use evince.
[06:34] <lool> Pff can't get focus in the terminal
[06:34] <lool> Let's find a second keyboard
[06:34] <cwong1> agoliveira: I have tried evince and it works fine. Does Mithrandir know more about this?
[06:35] <agoliveira> cwong1: Very lkikely
[06:35] <cwong1> agoliveira: tx, I will contact him. What timezone is he in?
[06:36] <agoliveira> cwong1: Good question but I guess is GMT +5
[06:36] <cwong1> tx
[06:37] <sodarock> agoliveira: what's up?
[06:38] <agoliveira> sodarock: Hello there. Sorry but now I forgot :) Shouldn't be anything important...
[06:39] <sodarock> okay :)
[08:23] <Mithrandir> cwong1: don't ask to ask, just ask your question and I'll respond when I'm around.
[08:24] <cwong1> Mithrandir: Do you know that status on Acrobat Reader?
[08:24] <cwong1> s/that/the/
[08:25] <Mithrandir> cwong1: I have a local package which seems to work.
[08:26] <cwong1> Mithrandir: Is it the same as the one that you can download from Adobe site?
[08:26] <Mithrandir> yes
[08:27] <cwong1> Mithrandir: Does it work for you in Firefox on Gusty?
[08:27] <Mithrandir> haven't tried.
[08:28] <cwong1> I tired it and it didn't work for me.
[08:29] <cwong1> Will this package be available in gusty for download?
[08:29] <Mithrandir> no
[08:29] <Mithrandir> gutsy is closed for further uploads, and additionally adobe reader doesn't come with a redistribution licence.
[08:30] <agoliveira> cwong1: For quite some time I don't feel the need for Acrobat reader as evince is working quite well and it's smaller, quicker and free :)
[08:31] <cwong1> is evince an opensource project?
[08:32] <agoliveira> cwong1: Unless it has changed since last time I messed with the sources, yes :)
[08:33] <cwong1> agoliveira: is there any plan on hildonize Evince?
[08:34] <agoliveira> cwong1: It's done already (though I didn't test it lately to tell you the truth...)
[08:34] <cwong1> agoliveira: I tried it and it wasn't.
[08:34] <agoliveira> cwong1: Did you try the lpia build?
[08:35] <cwong1> agoliveira: I just did.  The menu is not hildonize.
[08:35] <agoliveira> cwong1: Crap... let me check
[08:36] <cwong1> agoliveira:  The version number is 2.20.0.
[08:37] <agoliveira> cwong1: 2.20.0-3?
[08:38] <agoliveira> I'm checking the sources and the patch is there. Let me check the binary... hold on
[08:38] <cwong1> agoliveira: mine is 2.20.0
[08:38] <cwong1> agoliveira: from the about box
[08:39] <agoliveira> The problem is that the latest binary available from ports.ubuntu.com is 2.20.0-1 (don't know why)
[08:40] <cwong1> agoliveira: how do i get the 2.20.0-3 then?
[08:40] <agoliveira> cwong1: apt-get source evince and build in a lpia chroot.
[08:51] <cwong1> agoliveira: will this be fix in gusty?
[08:51] <agoliveira> cwong1: I don't think so.
[08:51] <cwong1> agoliveira: apt-get source evince didn't find the package
[08:51] <agoliveira> cwong1: Check you sources.list. I just did it.
[08:51] <cwong1> agoliveira: my sources.list has "deb http://ports.ubuntu.com/ubuntu-ports gutsy main"
[08:51] <agoliveira> ports don't have sources. Do it from your normal gutsy install or add a gutsy source linux there
[08:51] <cwong1> ok.  tx
[08:51] <Mithrandir> agoliveira: because hildon's not in main yet, and evince is, so it can't build on lpia until hildon is in main
[08:51] <agoliveira> Mithrandir: Oh... understood. Thanks for the explanation.
[08:51] <agoliveira> cwong1: So you will have to do build yourself but should be pretty straightforward
[08:51] <cwong1> agoliveira: got it
[08:51] <agoliveira> cwong1: Cool.
[10:52] <Inuka> robr, ping
[10:53] <robr> Inuka: yes?
[10:54] <Inuka> robr, does the current kernel support lpia?
[10:54] <robr> yes
[10:54] <Inuka> what is it called when I specify the architechture at compile time? (lpia?)
[10:55] <robr> yes, in the sense we compile it with lpia optimizations...the architecture passed into the kernel makefile is still i386
[10:55] <Mithrandir> cwong1: I repackaged it into a .deb
[10:55] <Inuka> robr, oh ok so I do not need specify any special options. it is already in the rules?
[10:57] <robr> Inuka: if you're building it in an lpia build root (i.e. image-creator lpia project) then that's correct, as far as i know
[11:01] <cwong1> Mithrandir: Can you send me the instr. on how to do that or put the image somewhere that I can try?
[11:59] <Inuka> rob, where you able to get x to start after enableing c4, my x windows keeps on restarting in a loop.
[12:00] <Inuka> rob, I am in the process of recompiling a new kernel I will give it a shot with that
[12:03] <Inuka> rob, if I boot to the terminal the system is not stable though...
[12:51] <Inuka> rob, left usb drive and instructions on your desk


[11:23] <davmor2> morning all
[13:45] <cr3> top of the morning, folks
[13:56] <fader_> cr3: Hey dude
[13:57] <davmor2> morning fader cr3
[15:30] <moustafa> cr3, fader Good morning!
[15:30] <davmor2> moustafa: Boo!
[15:31] <cr3> moustafa: hey dude!
[15:31] <fader_> moustafa: hey man
[15:31] <moustafa> davmor2: Ahh!  Didn't see you there!  Did you just pop out of the Tardis?
[15:31] <moustafa> cr3: Hon hon!
[15:31] <moustafa> fader_ : Yo!
[15:32] <cr3> moustafa: gerard depardieu
[15:32]  * moustafa could go for a Croissant
[15:36] <fader_> moustafa: +1
[15:37] <moustafa> fader_: Maybe one day. :)
[17:44] <seven1> how to restore ubuntu 9.04 from live cd...ubuntu will not load due to free veo graphics driver fail...fail happened post virtualbox installation...any thoughts ideas?
[17:45] <seven1> freevo


[03:00] <mysteriousdarren> how well does speech control work?
[03:15] <Fudge> mysteriousdarren  with what exactly
[03:16] <mysteriousdarren> Fudge:  I wanted to use it for speech recognition for writing to text documents
[03:18] <Fudge> oh like with simon?
[03:21] <mysteriousdarren> yes is that the best one? I have been googling and googling and comparing.
[03:21] <Fudge> so i believe but sorry i use text to speech, not speech  to text
[03:25] <mysteriousdarren> so simon is just speech to text?
[03:28] <Fudge> yes
[03:28] <Fudge> where orca is text to speech, screen reader
[03:35] <mysteriousdarren> Fudge: Thank you for the clarification
[03:37] <Fudge> you're welcome
[19:05] <Pendulum> charlie-tca: can you let me know when you want to start doing a11y classes in -classroom and what time/day of the week is good for you?
[19:05] <Pendulum> charlie-tca: also, can you possibly look at a11y bugs to see which might be bitesized?
[19:06] <charlie-tca> Okay, I will try to do that this week
[22:57] <Fudge> think guys that speechd-up should be fixed or upgraded for upcoming precise so it actually installs and works
[22:57] <Fudge> im using the vinux package to use it
[22:59]  * Fudge pings AlanBell  TheMuso
[23:31] <TheMuso> Fudge: Yes, it should be fixed, what needs doing to it?
[23:32] <Fudge> i dont know exactly it returns errors on install and there are no init scripts installed, forcing  all to install doesnt work either
[23:44] <TheMuso> Fudge: Ok I'll have a look when I get a moment.


[15:00] <dbungert> o/
[15:00] <bdmurray> #startmeeting Weekly Ubuntu Foundations team
[15:00] <meetingology> Meeting started at 15:00:08 UTC.  The chair is bdmurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[15:00] <meetingology> Available commands: action, commands, idea, info, link, nick
[15:00] <mclemenceau> o/
[15:00] <bdmurray> #topic Lightning Round
[15:00] <sil2100> o/
[15:00] <doko> already?
[15:00] <bdmurray> doing the shuffle
[15:00] <bdmurray> doko: times changed here
[15:00] <bdmurray> dbungert slyon ginggs xypron mwhudson doko vorlon ogayot alexghiti bdmurray juliank waveform enr0n schopin sil2100 jawn-smith
[15:01] <dbungert> * subiquity - setup of stable branches for both subiquity and probert,
[15:01] <dbungert> Update api test for compatibility with v2 curtin actions, fix probert for
[15:01] <dbungert> python 3.10 (LP: #1964571) and point core22 console-conf to that, fix offsets
[15:01] <dbungert> generation for fresh partition tables, work in progress on more partitioning,
[15:01] <dbungert> * subiquity vs risc-v - workaround a command timeout, move builds along,
[15:01] <dbungert> log analysis of issues
[15:01] <dbungert> (done)
[15:01] <slyon> - Discussions around network-online.target spec
[15:01] <slyon> - systemd v249.11 bugfix release
[15:01] <slyon> - some proposed-migration for systemd
[15:01] <slyon> - some bug grooming & triage for systemd & netplan
[15:01] <slyon> - explaining some systemd/SRU things to enr0n
[15:01] <slyon> - Prepare systemd fix for HP Omen 15/17 calculator key, LP: #1929345
[15:01] <slyon> [15:01] <slyon> - discussions around symbol versioning for libnetplan
[15:01] <slyon> - multi-driver matching compat for SRUs, LP: #1918421
[15:01] <slyon> - v0.104 SRUs (Impish/Focal), LP: #1964481
[15:01] <slyon> - reviewed https://github.com/canonical/netplan/pull/261
[15:01] <slyon> - review & merged https://github.com/canonical/netplan/pull/267
[15:01] <slyon> - working on meson+ninja buildsystem support
[15:01] <slyon> (done)
[15:01] <bdmurray> graham is out
[15:01] <bdmurray> xypron:
[15:02] <bdmurray> doko: ?
[15:03] <doko> I'll need a bit, going later
[15:03] <bdmurray> ogayot:
[15:03] <ogayot> * subiquity:
[15:03] <ogayot>    * rebranded ubuntu advantage -> ubuntu pro
[15:03] <ogayot>      * added compatibility layer for autoinstall keys
[15:03] <ogayot>    * implemented HTTP 409 responses to report server side tasks cancelled (to be reviewed later)
[15:03] <ogayot>    * investigated failures on riscv64
[15:03] <ogayot>    * fixed crash when Ubuntu Pro token expiration uses RFC3339 format
[15:03] <ogayot>    * more discussions on Ubuntu Pro design with UX team
[15:03] <ogayot>    * discussed third-party drivers design updates with UX team
[15:03] <ogayot>    * more investigation on bug 1962205 - reproduced on riscv64 by xypron
[15:03] <ogayot>    * working on prerequisites to merge third-party drivers to jammy
[15:03] <ogayot>    * done ☑
[15:03] <alexghiti> Live-installer on Unmatched board failure (can be caused by a kernel bug, investigating)
[15:03] <alexghiti> UEFI image on VisionFive
[15:03] <alexghiti> -  patch for grub is necessary as the kernel can’t boot from the dtb in the factory uboot
[15:03] <alexghiti> - rebase VisionFive patches on top of Ubuntu unstable 5.17 branch
[15:03] <alexghiti> Netdata fix riscv64 package sponsored by @schopin
[15:03] <alexghiti> (done)
[15:04] <xypron> I have concentrated on testing riscv installer image.
[15:04] <xypron> detected multiple issues in subiquity
[15:04] <xypron> and curtin.
[15:05] <xypron> upgraded in nezha-boot0 in a ppa to support more boards
[15:05] <xypron> <done />
[15:05] <bdmurray> updated the errors code to include changes necessary for 18.04
[15:05] <bdmurray> added riscv64 to the drop list of arches for the Error Tracker
[15:05] <bdmurray> further digging into removing tasksel from Ubuntu
[15:05] <bdmurray> finished update of manifest contacts in the ISO tracker database
[15:05] <bdmurray> investigation into ISO tracker settings for sil2100
[15:05] <bdmurray> uploaded apport fix for LP: #1964405
[15:05] <bdmurray> uploaded the packagekit patch in LP: #1963904
[15:05] <bdmurray> inclusive naming update for ubuntu-release-upgrader
[15:05] <bdmurray> uploaded ubuntu-release-upgrader with deb2snap changes LP: #1964443
[15:05] <bdmurray> added Ubuntu Studio to the deb2snap transition for firefox
[15:05] <bdmurray> sponsored ranger package for dbungert
[15:05] <bdmurray> sponsored zlib patch for LP: #1961427
[15:05] <bdmurray> preparing for and conducting interviews
[15:05] <bdmurray> administrative work
[15:05] <bdmurray> ✔ done
[15:05] <juliank> * redid grub2 focal SRU paperwork, it ready now
[15:05] <juliank> * uploaded initramfs-tools with zstd -1, lz4 -2 changes agreed upon
[15:05] <juliank> * uploaded nullboot to jammy, filed MIR
[15:06] <juliank> * apt 2.4.2 fixes Debian reportbug bugscript regression, two translation updates
[15:06] <juliank> * got paride access to autopkgtest cloud
[15:06] <juliank> (done)
[15:06] <bdmurray> WaVeR:
[15:06] <bdmurray> waveform:
[15:06] <waveform> * u-boot merge done \o/ (LP: #1964365)
[15:06] <waveform> * Investigated reports of eth+wifi failure on Core 20
[15:06] <waveform> * Trawled the flash-kernel bug history and cleaned up a few bits (LP: #1794841, LP: #1928314, LP: #1962309, LP: #1893491)
[15:06] <waveform> * Worked on speeding up flash-kernel (LP: #1965129)
[15:06] <waveform> * Worked on rpi-imager snap customization (missing auto-connections)
[15:06] <waveform> * Worked on netboot of Ubuntu on Pi images
[15:06] <waveform> * Pi meetings
[15:06] <waveform> (done)
[15:07] <bdmurray> enr0n:
[15:07] <enr0n> * python3-reportlab FTBFS (Debian bug 1006763)
[15:07] <enr0n>   - vorlon uploaded 3.6.7-1ubuntu1
[15:07] <enr0n>   - doko uploaded 3.6.8-1 to Debian, which has since
[15:07] <enr0n>     synced to -release
[15:07] <enr0n> * u-r-u fixed LP: #1964443
[15:07] <enr0n>   - Bug was for Kubuntu, but we also added firefox deb2snap entries for other
[15:07] <enr0n>     flavors that are shipping the snap in jammy
[15:07] <enr0n> * Followed up with reporter on LP: #1961432, waiting to hear back
[15:07] <enr0n>   - Added core20 to deb2snap in any case
[15:07] <enr0n> * +1 maintenance this week
[15:07] <enr0n>   - Fixed the following packages, and waiting for sponsors on each
[15:07] <enr0n>     * golang-github-valyala-fasthttp autopkgtest regression on s390x (LP: #1965134)
[15:07] <enr0n>     * python-pecan FTBFS (LP: #1965132)
[15:07] <enr0n>     * nfstrace FTBFS (LP: #1965155)
[15:07] <enr0n>     * mit-scheme FTBFS (LP: #1965163)
[15:07] <enr0n>     * pktstat FTBFS (LP: #1965174)
[15:07] <enr0n>   - Investigating the entanglement of python-uvicorn, python-pytest-asyncio, pytest-mock
[15:07] <enr0n>   - Looked into pyparsing FTBFS (LP: #1964782)
[15:07] <enr0n>     * Leaving alone for now due to new 'railroad' dependency having no Debian package
[15:07] <enr0n>   - Looked into python-b2sdk FTBFS (LP: #1964973)
[15:07] <enr0n>     * Needs a newer version of python3-logfury, have yet to look into packaging
[15:07] <enr0n>       this new version
[15:08] <enr0n> (done)
[15:08] <schopin> * Rust: Ongoing work on addressing the vendoring sources concerns from the security team for the rustc MIR.
[15:08] <schopin> * OpenSSL:
[15:08] <schopin>   - Currently packaging OpenSSL 3.0.2 for Jammy (LP: #1965141), trying to figure out some issues with the test suite.
[15:08] <schopin>   - Uploaded a fix for serf (LP: #1956040)
[15:08] <schopin>   - Worked with athos on a fix for php-dapphp-radius (LP: #1964514)
[15:08] <schopin>   - Sponsored alexghiti's fix for netdata riscv64 build to get an libssl3-linked version to the release pocket (LP: #1962837)
[15:08] <schopin> * Netplan:
[15:08] <schopin>   - Rebased the YAML consolidation branch dedicated to the `set` command
[15:08] <schopin>   - Discussed the new API scheme with slyon to address some newly identified shortcomings
[15:08] <schopin> * Other distro work:
[15:08] <schopin>   - Sponsored php-symfony-polyfill for athos (LP: #1964709)
[15:08] <schopin>   - Patched tinyssh to work with SSH 8.9 (LP: #1964585)
[15:08] <schopin> ✓ done
[15:08] <sil2100> * Partially sick on Monday
[15:08] <sil2100> * SRU reviews and releases
[15:08] <sil2100>   - Spent some time on the big netplan.io SRU review
[15:08] <sil2100> * FFe reviews
[15:08] <sil2100> * NEW reviews (nullboot, some ignition-* packages)
[15:08] <sil2100> * Discussed subiquity release-management ideas
[15:08] <sil2100> * WSL isotracker support
[15:08] <sil2100>   - Iterating on the new isotracker user, sending over the credentials
[15:08] <sil2100>   - Poking for merging of the WSL notify-isotracker changes
[15:08] <sil2100> * HWE meeting
[15:08] <sil2100> * Released new core18 to stable
[15:08] <sil2100> * A lot of work on the new ubuntu-image design
[15:08] <sil2100>   - Lots of discussions with Steve, William and other teams
[15:09] <sil2100> * RISC-V live installer
[15:09] <sil2100>   - Experimented with livefs-editor to help with injecting subiquity
[15:09] <sil2100>   - Reviewed a related livefs-editor PR from Michael
[15:09] <sil2100>   - Some clean up of debian-cd changes to build the images on infra
[15:09] <sil2100>   - Various debugging
[15:09] <sil2100> * Preparing new test images for intel-iotg
[15:09] <sil2100> * Started working on some new UC20 test images for intel-iotg
[15:09] <sil2100> * Other stuff
[15:09] <sil2100> (done)
[15:09] <jawn-smith> * ubuntu-image:
[15:09] <jawn-smith>     * Updating PR per sil2100's feedback
[15:09] <jawn-smith>     * Working on classic image redesign spec
[15:09] <jawn-smith>         * Discussion about gadget package vs gadget file tree under git control
[15:09] <jawn-smith> * Raspberry Pi:
[15:09] <jawn-smith>     * piboot UC22 testing
[15:09] <jawn-smith>     * Rebuilding kernel and snapd snaps with piboot changes
[15:09] <jawn-smith>     * Preparing config.txt changes for piboot
[15:09] <jawn-smith> * RISC-V:
[15:09] <jawn-smith>     * Troubleshooting the installer image. Fixed one of the bugs in curtin
[15:09] <jawn-smith> * Go 1.18 transition
[15:09] <jawn-smith>     * Packaged in Debian and Ubuntu
[15:09] <jawn-smith>     * Test rebuilds done against the released version of Go 1.18
[15:09] <jawn-smith>     * Fixed and uploaded many packages for which Go 1.18 complained about unused variables
[15:09] <jawn-smith>     * Submitted upstream bugs for any projects using SHA1 signed certificates in test cases
[15:09] <jawn-smith>     * Started discussion with security team about how to handle SHA1 certificates in test cases
[15:09] <jawn-smith>     * Wrote information for all failing packages in bug 1964270
[15:09] <jawn-smith> [done]
[15:10] <bdmurray> Any questions on status?
[15:10] <doko> - some +1 work on Wed - Sat
[15:10] <doko> - tbb / onetbb update, to restore numba
[15:10] <doko> - binutils 2.38 updates for various targets
[15:10] <doko> - python 3.10.3 updates and distutils/setuptools fixes
[15:10] <doko> - GCC 12 update
[15:10] <doko> - LLVM 14 as the default
[15:10] <doko> - helping Graham with the python3.10-only uploads
[15:10] <doko> - doing python 3.10 performance testing on various architectures
[15:10] <doko> (done)
[15:11] <bdmurray> #topic Release Incoming Bugs
[15:12] <bdmurray> #link https://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-jj-incoming-bug-tasks.html
[15:12] <bdmurray> bug 1923052 still needs testing / we are waiting to hear back from the reporter
[15:12] <bdmurray> bug 1958720 is with the server team
[15:13] <bdmurray> bug 1962751 have you tested that sil2100?
[15:13] <sil2100> ...no, let me fetch my laptop in a moment
[15:13] <bdmurray> bug 1745648
[15:14] <slyon> that's a very old bug about input validation. I lowered it from Critical to High, but I guess it should be fixed eventually, should be easy
[15:15] <bdmurray> Does eventually mean for 22.04 or 22.10?
[15:15] <slyon> 22.10 should be good enough
[15:16] <bdmurray> So we can change the tags to rls-kk
[15:16] <bdmurray> bug 1947588
[15:16] <slyon> wfm
[15:16] <bdmurray> schopin: Did you dig into this at all?
[15:16] <schopin> sadly no.
[15:17] <bdmurray> Would a card help?
[15:17] <schopin> Not really, it's on my private pile already
[15:18] <bdmurray> Okay
[15:18] <bdmurray> bug 1618522
[15:18] <slyon> that's another bug which should be easy to fix nowadays
[15:18] <bdmurray> That seems like something we could punt down the line
[15:18] <slyon> bug I guess we can move it to rls-kk
[15:18] <slyon> (it as been as-is for >5y)
[15:18] <bdmurray> Okay, I'll do that then
[15:19] <bdmurray> bug 1962454 would still be nice to do but not worth carding
[15:19] <bdmurray> ubug 1965180
[15:20] <bdmurray> bug 1965180
[15:20] <juliank> needs fixing
[15:21] <juliank> probably comes from ddstreet's refactoring?
[15:21] <ddstreet> does, yeah
[15:21] <bdmurray> Is that something you'll fix ddstreet or should we take it?
[15:21] <ddstreet> if you're already on it, go for it
[15:22] <ddstreet> i can work on it soon if not
[15:22] <juliank> we are deciding whether to put it i nthe backlog here :)
[15:22] <bdmurray> We are making a choice about taking it on, which I guess we'll do as a backstop.
[15:22] <ddstreet> yep sounds good
[15:23] <bdmurray> bug 1965293
[15:23] <slyon> this was created today. systemd autopkgtests seem to have regressed in release on Impish and Focal.
[15:23] <slyon> we should card & investigate this.
[15:23] <bdmurray> That sounds like High to me
[15:24] <slyon> ack
[15:25] <bdmurray> The tasksel bugs need to be rethought as removing the package isn't easy but let's move those down to rls-kk
[15:25] <bdmurray> bug 1964923
[15:26] <bdmurray> The crash is actually in ubuntu-drivers-common so we should ping tseliot about it
[15:26] <juliank> this
[15:26] <juliank> this needs fixing in update-notifier
[15:26] <bdmurray> Or juliank you were talking about some changes recently made is this a result of that?
[15:26] <juliank> yeah presumably regression from u-d-c switching to apt_pkg
[15:27] <juliank> we have software-properties changes to accomodate that, u-n needs similar ones presumably
[15:27] <bdmurray> Okay, so let's target and card that
[15:27] <juliank> (oh I forgot  Ireviewed those in my status :D)
[15:27] <bdmurray> We should all use "some stuff" in our status
[15:27] <bdmurray> that's it for rls-jj
[15:27] <bdmurray> rls-ii is empty
[15:28] <bdmurray> rls-ff has the /boot bug
[15:28] <bdmurray> I guess I'll reply to the email thread again
[15:28] <bdmurray> proposed migration jawn-smith
[15:28] <jawn-smith> o/
[15:28] <schopin> #link https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[15:29] <jawn-smith> first up is pygments and that was ginggs
[15:29] <jawn-smith> ginggs is out, so we'll wait on that for now
[15:29] <doko> on vacation this week
[15:29] <jawn-smith> next up is binutils
[15:29] <jawn-smith> alexghiti: is actually going to take a look at pygments
[15:30] <jawn-smith> any binutils experts?
[15:30] <doko> yes, but no crash expert ;p
[15:31] <jawn-smith> doko: crash vs binutils, thanks!
[15:31] <jawn-smith> systemd: slyon ?
[15:31] <slyon> ack
[15:31] <jawn-smith> alright, all that's left to look at is zlib
[15:31] <jawn-smith> any volunteers to look at zlib regressions before people get voluntold?
[15:31] <bdmurray> I'm going to look at zlib a bit since I uploaded it
[15:32] <bdmurray> But I think fheimes should too
[15:32] <jawn-smith> some of these are covered already: crash and systemd
[15:32] <bdmurray> slyon: Is the binutils task in bug 1940505 still valid?
[15:32] <slyon> bdmurray: most probably not
[15:33] <jawn-smith> bdmurray: is going to look at all of the zlib regressions in theory
[15:33] <jawn-smith> I'm guessing quite a few of these just need retries
[15:33] <jawn-smith> so between fheimes and bdmurray we'll consider zlib covered
[15:34] <jawn-smith> python3.10 only has one regression so far
[15:34] <jawn-smith> anyone eager to look at gnudatalanguage vs python3.10?
[15:34] <jawn-smith> we'll just retry that test once autopkgtest queues are settled down
[15:35] <jawn-smith> and then if it still fails we'll just assign it to waveform
[15:35] <jawn-smith> python + arm64 = waveform
[15:35] <waveform> who's off next week ;)
[15:35] <jawn-smith> and that's it for proposed migration. Back to you bdmurray
[15:36] <bdmurray> schopin: What is the status of the openssl transition?
[15:36] <schopin> https://discourse.ubuntu.com/t/openssl-3-0-transition-plans/24453
[15:36] <juliank> I wanna say this transition worked very smoothly from my limited sight into it :)
[15:37] <bdmurray> So there are like 8 packages needing work?
[15:37] <schopin> Besides the couple of NBS packages remaining, there's a handful of packages currently in the release pocket that are buggy with openssl 3.0
[15:37] <schopin> I'm a tiny bit worried about the Ruby ones
[15:38] <doko> are we able to remove these?
[15:38] <schopin> I doubt it. ruby-net-ssh is kinda important :)
[15:39] <bdmurray> Okay, well let's try and help out with these
[15:40] <schopin> I'll prepare the list of rdeps for each package, just in case.
[15:40] <bdmurray> enr0n it might be something for you to look at during +1
[15:40] <bdmurray> #topic AOB
[15:40] <juliank> I'm out tomorrow
[15:40] <schopin> So am I.
[15:40] <doko> POWER9
[15:40] <ogayot> So will I
[15:41] <bdmurray> I've an errand tomorrow morning so will be out half the day
[15:41] <bdmurray> doko ?
[15:41] <doko> we raised the baseline in December, so we should do no-change uploads for all packages in main which were not uploaded since the baseline change.
[15:41] <doko> any volunteers for that?
[15:42] <sil2100> ...is that something I could do during my +1? Or rather outside of the +1 focus?
[15:42] <bdmurray> all packages doesn't sound foundations exclusive
[15:43] <doko> sure, anybody could do that, just not all at once
[15:43] <bdmurray> So I'd say yes
[15:43] <sil2100> I could tackle that next week then
[15:44] <doko> just before the beta?
[15:44] <bdmurray> The beta is in 2 weeks
[15:44] <doko> ahh, ok
[15:44] <sil2100> If someone wants to start the work this week, sure
[15:44] <sil2100> I can continue on Monday
[15:45] <bdmurray> Alright I think that covers everything
[15:46] <bdmurray> thanks everybody
[15:46] <bdmurray> #endmeeting
[15:46] <meetingology> Meeting ended at 15:46:56 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-03-17-15.00.moin.txt


[05:54] <lordievader> Good morning.
[06:48] <jhenke> hi
[06:49] <jhenke> any firefox maintainer here? I got a bit of a strange bug: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1439532
[06:49] <jhenke> it only affects the version in vivid as far as I ca say
[07:22] <zezeekx> hello
[07:23] <zezeekx> it seems that afterr the latest update my Kubuntu 15.04 goes ape poo.
[07:23] <zezeekx> In my W7 boot now
[07:23] <zezeekx> It seems that when I boot into Kubutnu I have about 10 seconds in plasma before my desktop becomes slow and eventually freezes
[07:24] <zezeekx> kdeinit, dropbox, baloo are at high cpu it seems
[07:24] <zezeekx> when I log into a terminal I can do some stuff
[07:25] <zezeekx> but that too becomes a bit slow
[07:25] <zezeekx> but still reponsive
[08:18] <igalic> zequence: is the console still available? (Ctrl+Alt+F1…F6)
[08:19] <igalic> zequence: might be useful to take a look at (h)top and see what's causing the high-cpu load.
[08:19] <elfy> do you mean zezeekx - who's gone?
[08:31] <igalic> i… need more coffee, or sleep.
[10:04] <mark_chang_1492> I try to bootup with 15.04 from usb storage,  but I can not boot successful. Display "boot: gfxboot.c32: not a com32R image" repeatly. any body have suggestion??
[10:06] <mark_chang_1492> The version I try was daily build "2 April".
[10:51] <BluesKaj> Hi folks
[11:05] <aftereyo> hey
[11:25] <lordievader> o/
[13:11] <scellow> Hello guys,  my java apps can't access https links, only http, (gradle http repo works great, while https doesn't work :/) i believe it's a problem with certificates, but it's a fresh install, can you please help me ?
[13:14] <solsTiCe> hi. once 15.04 is released, how can I switch back to stick to it and not use beta(dev) build ?
[13:14] <k1l_> that is automatically
[13:14] <solsTiCe> ok. thanks
[13:15] <k1l_> the alpha/beta will become a regular release when running the updates
[13:15] <scellow> oh i found the fix : https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1396760
[13:17] <solsTiCe> that systemd-fsck delays i annoying. I use now fsck.mode=skip in kernel boot parameter. but that's disble fsck :-( I did not had problem in 14.10 but it was upstart. I think I only booted once with systemd in 14.10 and I did not get the 30s wait. So this is only systemd 219 and 15.04
[13:53] <solsTiCe> there is a serious bug in the gui installer. when you upgrade, it ask for a user. if you comply, it removes the existing user (id=1000) and create a new one.
[13:56] <solsTiCe> in fact, I think /etc has simply been wiped. for an upgrade that is rather radical
[13:56] <k1l_> file a  bug please
[13:56] <solsTiCe> k1l_: do you know against which package ?
[13:57] <solsTiCe> I had placed test file in /etc and  /etc/cron.daily and they are gone. but home of previous user is still there.
[13:59] <k1l_> hm, i cant remember what the name was
[13:59] <solsTiCe> never mind; i am doing another reinstall in vbox
[19:49] <lord_cotton> so Kubuntu 15.04 is broken for me
[19:49] <lord_cotton> kdeinit5 eats all ram plus swap
[19:49] <lord_cotton> gotta kill it in the tty
[19:49] <lord_cotton> logging into plasma lasts ~20s
[19:56] <MoonUnit`> they should have fixed that.
[19:57] <MoonUnit`> kubuntu-notification-helper was the culprit.
[19:58] <lord_cotton> did you get that too?
[19:58] <MoonUnit`> yes
[19:58] <MoonUnit`> https://www.kubuntuforums.net/showthread.php?67778-Kubuntu-15-04-Beta-2-unusable-after-a-short-period-of-time
[19:58] <lord_cotton> I tried 40min ago a apt-get update and dist-upgrade
[19:58] <MoonUnit`> but it got updated yesterday
[19:59] <lord_cotton> o.O
[19:59] <lord_cotton> I will try tomorrow
[19:59] <lord_cotton> But thansk for the link
[19:59] <lord_cotton> Although some updates were not able to be retrieved
[20:00] <MoonUnit`> you can uninstall it
[20:02] <lord_cotton> I could uninstall  kubuntu-notification-helper and that would work too?
[20:02] <MoonUnit`> yes, i had to do that before they fixed it
[20:03] <lord_cotton> I will try that
[20:03] <lord_cotton> and then reinstall it ?
[20:03] <lord_cotton> or will update and dist-upgrade fetch it for me?
[20:04] <MoonUnit`> update and dist-upgrade should fix it
[20:06] <lord_cotton> Alright
[20:06] <lord_cotton> that should fix it hopefully
[20:29] <MoPac> I have an issue where I'm unclear whether a bug would be kernel-related or just something wrong with Ubuntu or Ubuntu's tweaks to the kernel. Essentially, some of my hybrid notebook's hardware inputs are being misinterpreted. So, e.g., if the accelerometers signal that I tilted it into portrait configuration, the OS thinks I have set a WiFi hardware switch into the "disabled" position.
[20:29] <MoPac> Is this the kind of thing to just leave in Launchpad (https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1438422), or does potentially implicate anything upstream?  I'm not clear on whether that kind of hardware interpretation is part of the kernel itself
[21:22] <Roy007> INVITE
[21:22] <Roy007> hi
[21:22] <Roy007> any one there
[21:22] <Roy007> need help
[21:22] <Roy007> ?
[21:22] <Roy007> really
[21:23] <k1l_> if you actually ask a technical question people could eventually help
[21:23] <Roy007> yes
[21:23] <Roy007> sure
[21:23] <Roy007> I want  to know one thing about ubantu
[21:24] <Roy007> as i am new in ubantu
[21:24] <Roy007> I find out that it is taking too much space day by day
[21:24] <Roy007> I am running low in space
[21:24] <k1l_> when you are new, you should not start with the beta version.
[21:24] <Roy007> how to overcome
[21:25] <Roy007> means?
[21:25] <k1l_> 15.04 is still developed. 14.04 or 14.10 are the ones that are finally done
[21:26] <k1l_> on 15.04 you get a lot of updates every day. so no wonder that is taking up space
[21:27] <Roy007> yes I am using Ubuntu 14.04
[21:27] <Roy007> I do not take any update
[21:28] <Roy007> And it is difficult to find out which update i should take.
[21:29] <Roy007> ????
[21:32] <k1l_> #ubuntu is the right channel for you then
[21:33] <elfy> for sure


 Qt 5.15.0 just landed in Neon user edition, FYI
 \o/ https://www.qt.io/blog/qt-5.15.1-released
 @RikMills [\o/ https://www.qt.io/blog/qt-5.15.1-released], qtbase already uploaded to Debian :)
 nice 👍
 oooh, and ubuntu has opus 1.3.1!
 @RikMills [Qt 5.15.0 just landed in Neon user edition, FYI], I looked at their packaging and some things look strange/wrong to me. E.g. https://packaging.neon.kde.org/qt/qtdeclarative.git/patch/?id=a2a2e5b805c7affcaa7682f7aba836374714790e — commit message says “it needs to be arch all” but the package ships files in /usr/lib/$DEB_
 @RikMills [oooh, and ubuntu has opus 1.3.1!], Saw that, yes :)
 @mitya57 [I looked at their packaging and some things look strange/wrong to me. E.g. https …], odd
 @mitya57 have mentioned that to them
 @RikMills [@mitya57 have mentioned that to them], Is that on some IRC channel?
 @mitya57 [Is that on some IRC channel?], #neon on freenode
 umm #kde-neon I mean
 Thanks. Joined
 [14:38] <JonathanRiddell4> hmm
 is the only reply so far
 oooh. I lie https://packaging.neon.kde.org/qt/qtdeclarative.git/commit/?h=Neon/release&id=baa8b8cd4c463d86637f3046b4f046bc1e40e2e7
 For Qt WebEngine we will have to pass Debian's NEW queue because of the new PDF libraries. Our copyright file is terribly outdated and we don't have a way to update it properly so I don't know how that will be possible :(
 Anyway, today I uploaded qtbase, qtdeclarative and qtwebsockets. Will continue tomorrow, maybe Lisandro will do a few more packages during my night.
[18:46] <lisandro> I really hope so
[20:36] <valorie> thank you all for your work
 @mitya57 Neon is seeing some fails like: https://paste.ubuntu.com/p/z6xS5Pvdj6/
 and I see you did: https://salsa.debian.org/qt-kde-team/qt/qtspeech/-/commit/f8fe5283685fe5503d3ef53a3749e896e5d91ee5
 Neon doesn't even have a recommends, but recommends are not installed in a buildd anyway
 oh must be 😴 time for you. sorry


[06:02] <xubuntu22w> is anyone there?
[06:02] <cfhowlett> xubuntu22w, don't ask that question.  ask your support question.
[06:04] <xubuntu22w> I have 15.04 running on a laptop. For the most part things work well, but I've continually been struggling with a black screen after logging in, unlocking the screen saver or switching users. I was able to fix the problem for a while but now it is back with a vengence. Any suggestions on how to correct this problme?
[06:05] <cfhowlett> xubuntu22w, screensaver?  xubuntu recommends removal of screensaver.
[06:05] <xubuntu22w> When this happens I have to do a hard reboot, Ctrl+Alt+F1 2 3 4 what ever doesn't help
[06:06] <xubuntu22w> there is no screen saver, whatever is there by default
[06:06] <xubuntu22w> when the screen locks it goes black
[06:06] <xubuntu22w> when I hit a key I get a login prompt, after logging in it goes black again, more than 50% of the time
[06:06] <cfhowlett> xubuntu22w, dpgk -l | grep xscreensaver               xscreensaver is known to conflict with lightlocker
[06:08] <xubuntu22w> I assume you ment dpkg, there is no screen saver retruned from that command
[06:09] <xubuntu22w> though in lightlocker settings it has a section that says lock the screen when screensaver is activated, don't know if that is an indicator of part of the problem
[06:15] <cfhowlett> xubuntu22w, I was specifically referencing item #1  http://xubuntu.org/news/5-things-to-do-after-upgrading-from-12-04-to-14-04/
[06:21] <xubuntu22w> This was a fresh install of 15.04 there is no xscreensaver
[06:35] <xubuntu22w> I literally hear crickets...
[06:51] <parlabane> what does one use in xubuntu to format and repartition a hdd... been looking through the menus and can't seem to find anything
[06:51] <cfhowlett> !gparted | parlabane,
[06:51] <parlabane> does anything come preinstallad ?
[06:52] <parlabane> ok thanks cfhowlett
[06:52] <parlabane> gparted doesn't seem to be installed! will have to do that
[06:53] <parlabane> so it doesn't come with like a disks. porgram like the ubuntu does ?
[08:58] <brainwash> xubuntu22w: I suggest that you actually disable/remove light-locker and install xscreensaver instead
[11:00] <xubuntu79d> has anyone here had trouble starting xubuntu after the 15.04 update?
[11:01] <knome> xubuntu79d, why don't you ask about your problem so people can potentially help with that?
[11:02] <xubuntu79d> OK - the only way I can start xubuntu is to hold shift down, then select recovery mode. Then I can select from the menu to resume a normal startup and it works.
[16:09] <xubuntu80w> argh. Xubuntu installer ate my encrypted partition. no warnings were given. :(
[16:10] <xubuntu80w> It feels kind of crappy that an issue for this was opened nearly 6 years ago and yet this is still a problem. :( https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/420080
[16:11] <xubuntu80w> and also as someone has posted from links in at least one of the few bug reports: this is as easy to check for as looking for "LUKS" as the first few characters of the drive. :( :(
[16:11] <xubuntu80w> I would have expected something like: "This already looks like an encrypted partition, are you sure we want to destroy all of your data?"
[16:11] <xubuntu80w> (and it kills the data before hitting next. argh.)
[16:12] <holstein> xubuntu80w: did you have backups?
[16:14] <xubuntu80w> of course not, hahahaha. :( :(
[16:14] <xubuntu80w> so everything is gone. this is just a "woe is me, I know my data is gone"
[16:14] <xubuntu80w> holstein: the next question you'll probably ask is: "will you have backups now that you were burnt?" /me nods
[16:15] <holstein> ouch.. im sorry to hear that.. in the future, i say, just try and keep up with best practices on that kind of thing, as much as possible..
[16:15] <xubuntu80w> I do for all servers. this was just my desktop. Not really anything that important there. still sucks to lose all my bookmarks and such.
[16:15] <holstein> i just assume, any installer, or partitioner could break things. but, its becuase i had a similar experience with another OS years back..
[16:16] <xubuntu80w> at the point when everything was half broken and I was undergoing the attempt of "wow my system is screwed up from 14.10 -> 15.04, let me reinstall Xubuntu over the previous"
[16:17] <xubuntu80w> I should have done backups at that point
[16:17] <holstein> well, sounds like that happened..
[16:17] <holstein> anyways, sorry to hear you lost data..
[16:17] <xubuntu80w> er, I mean of course earlier. but definitely at that point
[16:18] <xubuntu80w> holstein: do you know how the installer gets baked into xubuntu? it feels like this should at least be fixed so it doesn't happen to me or others in the future. :-/
[16:19] <holstein> xubuntu80w: AFAIK, this will not be specific to xubuntu or xfce..
[16:20] <xubuntu80w> I think Ubuntu uses a slightly different installer
[16:20] <xubuntu80w> but yes, Kubuntu for instance probably also uses (ubiquity?)
[16:54] <xubuntu07d> Hi. I have a simple question. Where do I find the checksum to verify my download? I been searching the website but can't seem to find it.
[16:55] <GridCube> !checksums
[16:55] <GridCube> !checksum
[16:57] <GridCube> also xubuntu07d if you open any of the mirrors you get a lot of files containing all sorts of sums, http://mirror.aarnet.edu.au/pub/xubuntu/releases/15.04/release/
[16:58] <xubuntu07d> that's great! thanks!
[21:50] <HaroldV> Hi
[21:51] <knome> hello
[21:52] <HaroldV> where are you from ?
[21:52] <knome> do you have a support question?
[21:53] <HaroldV> yes
[21:53] <HaroldV> do you speak spanish ?
[21:53] <knome> !es | HaroldV
[21:53] <HaroldV> Muchas Gracias :)
[22:17] <a1fa> any remmina users in here?
[23:23] <tgm4883> running 15.04 here on my laptop. Occasionally when I resume from standby, after login I'll get a blank screen (without backlight as well). Pointers on where to start looking at this?
[23:23] <tgm4883> switching to TTY1 works fine
[23:25] <Unit193> Are you using late locking/
[23:28] <tgm4883> late locking?
[23:29] <Unit193> 15.04 uses light-locker, which has a feature called 'late-locking'.  I believe the claim of that is less problems with black screen bugs, but alas I don't know much on this topic.
[23:29] <Unit193> (I don't use light-locker.)
[23:29] <tgm4883> I've not setup anything like that I think, but I'll take a look
[23:57] <xubuntu98w> Hi everyboby :)
[23:58] <xubuntu98w> I need some help to install "Git" on my Ubuntu Studio (14.04)...
[23:59] <xubuntu98w> Is there someone know how to do, please ?
[23:59] <bazhang> sudo apt-get install git


[18:25] <LocutusOfBorg> https://autopkgtest.ubuntu.com/packages/v/virtualbox/groovy/amd64
[18:25] <LocutusOfBorg> ppisati, ^^ any idea?
[18:25] <LocutusOfBorg> I don't know what the kvm is...
[18:48] <sforshee> LocutusOfBorg: linux-kvm is built with a stripped down config really just meant for kvm, you can ignore those failues
[19:11] <LocutusOfBorg> nice to know
[21:41] <LocutusOfBorg> ppisati, if you want to open a merge request, there you can see the issue I opened https://github.com/draios/sysdig/issues/1669


[20:34] <laduke> An older UAC-AP  from ebay that says "48v 0.5A" on the label, is that poe.af or + or?


[19:25] <genii> sarnold: Did the user in #u ever get his guest session issue of not being able to access external drives sorted out? I couldn't hang around that night to see the end of the saga
[19:26] <sarnold> genii: I don't think he did
[19:27] <genii> Ah :(
[19:27] <sarnold> genii: my vague recollection was someone aimed him at a SO post from 2012 or something that suggested some apparmor policy changes, and then he took off :/
[19:28] <genii> Thanks for the update, was curious
[19:32] <sarnold> genii: what's really frustrating is that it might not have been so terrible to have been seated at the machine and figure things out, but over text, slow-ish responses, not big on details :(
[19:34] <genii> Yes. Sometimes I have the time available to go in depth with such users, but not that day, unfortunately
[19:35] <oerheks> another one today, with usb not rw under guest session, fixed it himself with a setting in  /etc/usbmount/usbmount.conf  ... which is empty on my system
[19:36] <genii> oerheks: Interesting
 Found the solution to permission issues for FAT32 USB automounted drives.  Solution was to edit /etc/usbmount/usbmount.conf to change the fmask and dmask for FAT32


[00:00] <cjwatson> Pre-publishing now so it can mirror overnight
[00:14] <bdmurray> cjwatson: has anybody looked at bug 1240683?
[00:14] <ubot2> Launchpad bug 1240683 in ubiquity (Ubuntu) "Ubuntu one login during install hangs" [Undecided,Confirmed] https://launchpad.net/bugs/1240683
[05:22] <stgraber> I'm heading to bed now, just finished testing all of Edubuntu and all the Core images that I could (leaving arm64 to infinity)
[05:22] <stgraber> bug wise, the only new thing that got reported is bug 1240794
[05:22] <ubot2> Launchpad bug 1240794 in ubiquity (Ubuntu) "In partioner 'select something else' deleteing and adding a partition causes crash" [Undecided,New] https://launchpad.net/bugs/1240794
[05:22] <stgraber> I tried reproducing it quickly here but I don't have a VM that lets me do resize at the moment and any attempt to reproduce by directly using the manual partitioner failed (as in, it worked as expected)
[05:23] <stgraber> so maybe that's somehow related to resize or that's not a very reproducable issue, either way, doesn't seem world ending
[07:55]  * apw manages to trigger something which looks like bug #1240794
[07:55] <ubot2> Launchpad bug 1240794 in ubiquity (Ubuntu) "In partioner 'select something else' deleteing and adding a partition causes crash" [Undecided,New] https://launchpad.net/bugs/1240794
[08:58] <xnox> maybe let that into the archive ^ ? =)
[08:58] <smartboyhw> Question: I presume https://wiki.ubuntu.com/SaucySalamander/Beta2/UbuntuStudio should be changed to https://wiki.ubuntu.com/SaucySalamander/UbuntuStudio for the final release? (A template for all flavours)
[09:06] <cjwatson> apw: cf. bug 1060484
[09:06] <ubot2> Launchpad bug 1060484 in parted (Ubuntu) "When using gparted com.canonical.Unity.Devices blacklist is set back to Default of []" [Undecided,Fix released] https://launchpad.net/bugs/1060484
[09:10] <infinity> smartboyhw: Or SaucySalamander/ReleaseNotes/UbuntuStudio, or whatever.  There doesn't seem to be much agreement here about where to find them.  I'm having a hard time finding everyone's. :P
[09:10] <smartboyhw> infinity, OK, I will just do /ReleaseNotes/UbuntuStudio
[09:11] <infinity> Thankfully, it's a wiki, so people can add links to their notes in the primary notes after release if we can't find them all...
[09:15] <smartboyhw> infinity, how about the "Common infrastructure" thing again?
[09:21] <infinity> smartboyhw: No point in the CI thing.  Reproducing everything in 7 different-but-similar release notes is silly.
[09:22] <smartboyhw> infinity, so, what am I supposed to do?
[09:25] <smartboyhw> Riddell, ^ mark upgrades ready too probably?
[09:25] <infinity> smartboyhw: Honestly, I wouldn't worry about having that section at all.  You could have a "for more information about this Ubuntu release in general, see the Ubuntu release notes at: $link".
[09:26] <smartboyhw> infinity, -.- OK
[09:27] <Riddell> smartboyhw: waiting on valorie for that
[09:27] <infinity> Riddell: Can you link the Kubuntu release notes in the Kubuntu section in the primary notes?
[09:27] <smartboyhw> Riddell, OK, I thought the testcases all passed
[09:28] <smartboyhw> infinity, to notify you, Studio's release notes is at https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes/UbuntuStudio
[09:29] <infinity> smartboyhw: Great, thanks.
[09:30] <Riddell> infinity: can do, copying those over to the website now
[09:30] <smartboyhw> Not sure about release announcements though, I need to clarify something with zequence
[09:30] <infinity> Riddell: Or give me a link, whichever.
[09:30] <Riddell> infinity: http://www.kubuntu.org/news/kubuntu-13.10
[09:48] <infinity> Riddell: Is that the announce or the notes?  (or do you not have notes?)
[09:48] <Riddell> infinity: right, same thing for us
[09:48] <xnox> cjwatson: http://www.ubuntu.com/content/what%E2%80%99s-new-ubuntu-server-1204-lts
[09:48] <cjwatson> ta
[10:08] <ogra_> stgraber, already around ? i was wondering how our release process works for touch i assume you will make saucy a standlone dir and re-link devel to T ?
[10:32]  * utlemming marked cloud images as ready
[10:55] <xnox> cjwatson: apw: http://www.ubuntu.com/getubuntu/releasenotes
[11:00] <cjwatson> looks like most of the flavour release notes links in https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes need to be updated?
[11:01] <smartboyhw> I told infinity Studio's
[11:01]  * ogra_ waits for apw to stop sitting in the lock
[11:02] <ogra_> s/in/on/
[11:04] <JackYu> I will update soon.
[11:06]  * ogra_ twiddles thumbs
[11:06] <ogra_> apw, are you writing a novel ?
[11:09] <xnox> OGRA!
[11:09] <ogra_> yes, thats me !
[11:09] <apw> ogra_, i am ... and did you write over it any how?
[11:10] <ogra_> apw, nope
[11:10] <xnox> ogra_: yes, he is writing a novel fixing all the urls that point to beta-1 & 2 instead of final.
[11:10] <ogra_> i'm canceling all the time here
[11:10] <ogra_> ah, lovely
[11:11] <apw> ogra_, ok ... have a go now, and let me know when you are done so i can have another bash
[11:18] <ogra_> apw, heh, now didrocks stole the lock
[11:18]  * ogra_ knew that going to the restroom wasnt a good idea
[11:19] <didrocks> \o/
[11:19] <didrocks> finishing up copying the known issues
[11:19] <didrocks> but the wiki hanged…
[11:19] <ogra_> well i guess i'll better check then that you dont have my issues on it already
[11:21] <didrocks> lock released
[11:21] <didrocks> ogra_: apw: ^
[11:22] <ogra_> grabbed
[11:23] <smartboyhw> infinity, http://ubuntustudio.org/2013/10/ubuntu-studio-13-10-released/ (the release announcement)
[11:25] <cjwatson> Riddell: Could I move https://wiki.ubuntu.com/SaucySalamander/Final1/Kubuntu to https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes/Kubuntu to line it up with the other flavours?
[11:27] <cjwatson> highvoltage: Should we have a separate release notes page for Edubuntu, or do you just want to link to the master one in the installer?
[11:27] <Riddell> cjwatson: that page can be deleted, it's at kubuntu.org/news/kubuntu-13.10
[11:28] <cjwatson> Riddell: OK, so that's more like an announcement than release notes?  Where should the release notes link in the installer go though?
[11:28] <cjwatson> Riddell: Just the master release notes page?
[11:28] <Riddell> cjwatson: yeah
[11:28] <ogra_> saved feel free to take over
[11:29] <ogra_> didrocks, i added a "platform" section for us
[11:29] <ogra_> (added the upstart memleak and uevent spam bugs)
[11:29] <cjwatson> knome: Is https://wiki.ubuntu.com/SaucySalamander/Final/Xubuntu intended as release notes or as a staged announcement?
[11:29] <didrocks> ogra_: yeah, sounds good :)
[11:30] <knome> cjwatson, that would be the notes, but it is not final-final yet.
[11:30] <cjwatson> knome: If the former, can we move it to https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes/Xubuntu for uniformity with other flavours?
[11:30] <knome> cjwatson, that's fine :)
[11:30] <cjwatson> knome: That's fine, just trying to get the structure right so that the web team can do links
[11:30] <cjwatson> OK, great, will do
[11:30] <knome> cheers
[11:44] <pietro98-albini> Hello everybody
[11:44] <pietro98-albini> I'm pietro from the italian loco
[11:44] <pietro98-albini> In our site we have a box with the md5 of downloaded iso
[11:45] <pietro98-albini> Can someone give me saucy md5's asap?
[11:45] <cjwatson> Er, it's terrible to have md5s copied around lots of sites
[11:46] <cjwatson> Can't you just link to https://help.ubuntu.com/community/UbuntuHashes (which is still terrible, but at least centralises the terribleness)?
[11:46] <cjwatson> I'll update that shortly
[11:48] <pietro98-albini> cjwatson, ok
[11:51] <cjwatson> right, UbuntuHashes done, need a shower now :P
[11:52] <ogra_> heh
[12:58] <infinity> Does anyone have link to release announcements for Xubuntu, Edubuntu, Lubuntu, GNOME, and Kylin?
[13:05] <knome> infinity, xubuntu will be at http://xubuntu.org/news/saucy-salamander-final/
[13:09] <infinity> knome: Thanks.
[13:17] <smartboyhw> Released!
[13:18] <rtg> infinity, I thought tantric was nixed ?
[13:18] <infinity> rtg: This is me not knowing the real name yet. :P
[13:18] <wgrant> Awww
[13:18] <rtg> bummer
[13:18] <apw> who'd need a name, to like open the release
[13:19] <smartboyhw> infinity, please confirm it is released
[13:19] <apw> there will be an announcement, when it is
[13:19] <wgrant> Could just convince Mark to use t-series as the adjective, to make things easy now.
[13:19] <cjwatson> smartboyhw: it is
[13:19] <smartboyhw> cjwatson, ACK:)
[13:19] <cjwatson> the topic change is confirmation :P
[13:20] <smartboyhw> :P
[13:20] <cjwatson> (announcement is in the mod queue, James is getting the website sorted first)
[13:20] <smartboyhw> I got afraid of the "not not" stuff in #u-r-p
[13:20] <cjwatson> this channel is more authoritative than #u-r-p
[13:23] <stgraber> ogra_: there's no actual release actions for touch, everything stays as it's until we get the first T images. Once we do, I'll setup the channels for T and change the devel aliases to point to it
[13:24] <ogra_> and saucy points to anything ?
[13:24] <ogra_> or do we just leave it as saucy
[13:24] <ogra_> (i.e. will you introduce "stable" alongside devel)
[13:24] <stgraber> saucy-proposed will be updated whenever a new saucy image is published to cdimage, that's how we do post-release updates
[13:24] <stgraber> ogra_: we already have stable
[13:24] <knome> there is no CommonInfrastructure page for final?
[13:25] <stgraber> ogra_: and it's already pointing to saucy
[13:25] <ogra_> stgraber, we wont do any saucy images after release
[13:25] <cjwatson> https://lists.ubuntu.com/archives/ubuntu-announce/2013-October/000177.html
[13:25] <ogra_> the plan is to roll on top of distro
[13:25] <ogra_> WHEE !
[13:25] <stgraber> ogra_: phablet-flash actually defaults to stable I believe
[13:26] <stgraber> ogra_: hmm, not what we discussed last vUDS, we said we'd do a few saucy updates post release but not support for the whole 9 months
[13:26] <stgraber> ogra_: (so we can at least test the process for 14.04)
[13:27] <ogra_> stgraber, i think what we agreed on in recent landing team meetings is that we stay without image for a few days until we can spin the first T one
[13:27] <ogra_> and then move on in T
[13:27] <mdeslaur> congrats!
[13:27] <didrocks> congrats guys \o/
[13:27] <ogra_> mdeslaur, to you too !
[13:28] <didrocks> stgraber: ogra_: phablet-flash defaults to stable indeed
[13:28] <didrocks> stgraber: the planned changed
[13:28] <stgraber> ogra_: I think we really should be publishing a couple of updated saucy ones (even if we do so after the switch to T) so we can make sure this process works
[13:28] <rickspencer3> nice job  with the release apw, cjwatson, infinity, xnox and anyone else who was in the office :)
[13:29] <infinity> rickspencer3: Be sure to visit the website 5000 times, so I win the betting pool.
[13:29] <rickspencer3> didrocks, stgraber my understanding was that we would release some update for any SRUs that happened to impact the phone or tablet images
[13:29] <rickspencer3> for about a month
[13:29] <rickspencer3> but we wouldn't necessarily make special updates
[13:30] <ogra_> hmpf
[13:30] <rickspencer3> infinity, ok, I'm working on my script now
[13:30]  * ogra_ would prefer we just move forward
[13:31] <popey> rickspencer3: can we get a public announce about that. it's still very vague
[13:31]  * ScottK isn't aware of any discussions with the SRU team about special SRU rules for phone.
[13:31] <ogra_> ... and concentrate on T instead of wasting resources on saucy ...
[13:32] <ogra_> that will make the first T image appear faster
[13:32] <rickspencer3> popey, so far as I know, nothing changed from vUDS
[13:32] <popey> rickspencer3: for those who weren't "at" vUDS
[13:32] <stgraber> ogra_: we're just talking about running the cdimage script a couple of times with -updates enabled to make sure the result is usable and that the system-image script import those fine
[13:32] <stgraber> ogra_: that can be done after devel is switched to T so I really don't see the harm
[13:33] <rickspencer3> popey, sure, let me synch with asac, et al
[13:33] <stgraber> ogra_: and I'd really rather we find any problem with saucy than with T
[13:33] <popey> cool
[13:33] <ogra_> stgraber, that still means the people will fiddle with SRUing stuff instead of working on T
[13:33] <ScottK> The SRU rules from the TB, not a UDS session.
[13:33] <stgraber> ogra_: nope
[13:33] <ScottK> ... rules are from ...
[13:33] <stgraber> ogra_: for all I care the only delta could be from standard distro (non-touch) SRUs
[13:33] <ScottK> Of course if we had a tech board, it would be nice.
[13:34] <infinity> stgraber: The plan was exactly that, to just take the distro SRUs as they come to test the system image machinery.
[13:34] <stgraber> right
[13:35] <ogra_> by SRU rules the uploads have to ripen for 2 weeks anyway before they can go to updates (or did that change)
[13:35] <ogra_> so what does an image buy us
[13:35] <stgraber> ogra_: 7 days, less if a SRU team member feels it's been sufficiently tested
[13:35] <ogra_> in 2 weeks we should also have our first T image
[13:35] <ogra_> which makes putting time into S a waste imho
[13:36] <stgraber> ogra_: do you even read what I'm writing? :) the whole point is to test post-release system-images, I also said I'm fine doing those after we switch people to T. The only time we're talking here is running a cdimage script to spin a new image, I really don't see the problem.
[13:36] <rickspencer3> ogra_, I thought the "not wasted" part was to test the update and upgrade logic
[13:36] <stgraber> (vs the time to fix T post-release because we didn't notice something was badly broken in saucy)
[13:36] <rickspencer3> sorry, I'm repeating stgraber
[13:36] <rickspencer3> how about this ...
[13:37] <rickspencer3> ew all chill out and enjoy Saucy today
[13:37] <ogra_> rickspencer3, why would updates from a stable channel be different than the ones in devel ?
[13:37] <rickspencer3> and figure it out tomorrow
[13:37] <ogra_> its just another name
[13:37] <ogra_> and we test devel every day
[13:37] <rickspencer3> ogra_, I'm just tellign you what was th decision as I understood it
[13:37] <rickspencer3> and was discussed in the session on this at UDS
[13:37] <rickspencer3> I don't think I want to argue about it now
[13:38] <rickspencer3> and if stgraber thinks something is a good idea, I usually trust that it is a good idea ;_)
[13:38] <ogra_> stgraber, the problem is that devs will focus on fixing S if that option is there
[13:38] <ogra_> instead of focusing fully on T
[13:39] <ogra_> which makes us waste precious resources
[13:39] <rickspencer3> ogra_, devs shoudl focus on fixing S if they are working on the desktop or server
[13:39] <ogra_> anyway, if this is set in stone it is set in stone and i wont bother further
[13:40] <rickspencer3> in the meantime ... WE ACTUALLY SHIPPING UBUNTU FOR PHONE
[13:40] <rickspencer3> :)
[13:40] <rickspencer3> and it's good
[13:40] <ogra_> :D
[13:40] <rickspencer3> and we brought forth image based updates
[13:40] <rickspencer3> and application isolation
[13:40] <rickspencer3> and Mir with Unity 8
[13:41] <rickspencer3> etc... :)
[13:42] <ogra_> yeah, it is pretty awesome what we can manage in 6 months
[13:44] <didrocks> ogra_: +1, it's insane to see the amount of changes that happened and how the result is :)
[13:45] <ogra_> yeah
[13:50] <med_> looks like openstack is stuck at RC for a bit.
[13:55] <jamespage> med_, fortunately all of the RC's landed in saucy before 13.10 released; so the updates are version number only
[14:11] <stgraber> infinity: I assume it's a bit late now, but http://www.edubuntu.org/news/13.10-release is the URL for Edubuntu
[14:24] <med_> jamespage, cool
[14:39] <infinity> stgraber: I'll be sure to go back in time and edit my email.
[14:39] <xnox> Tasty Takin
[14:46] <stgraber> FYI I'm planning on accepting the procps SRU to all releases and after testing it myself to release it directly to -updates
[14:46] <ogra_> Twiddly Thumbs
[14:46] <stgraber> as anyone using containers currently has a broken apt
[14:49] <jamespage> stgraber, thankyou - I have alot of those :-)
[14:49] <stgraber> yeah, got 150 containers just by myself plus a dozen angry people who sent me e-mails
[14:49] <stgraber> so I want that resolved SAAP
[14:49] <stgraber> *ASAP
[14:50] <mdeslaur> stgraber: what? I thought only the security team got the death threats? :)
[14:51] <stgraber> jamespage: feel free to help with validation (bug 1157643)
[14:51] <ubot2> Launchpad bug 1157643 in procps (Ubuntu T-series) "procps fail to start" [Undecided,Confirmed] https://launchpad.net/bugs/1157643
[14:51] <stgraber> mdeslaur: well, it turns out that people running thousands of containers using unattended-upgrade don't like you when all of a sudden they're all broken and require manual changes ;)
[14:51] <jamespage> stgraber, ack - I have at load of containers winging in our openstack test environment which is all 12.04
[14:52] <mdeslaur> stgraber: hehe :P
[14:52] <stgraber> jamespage: yeah, 12.04 is definitely the most urgent, most people using LXC tend to stick to LTS, the rest is still impotrant but slightly less urgent
[14:52] <jamespage> stgraber, great - as soon as it lands I'll give it a run
[15:08] <phillw> please note that both the upgrade lubuntu's are also good for release. the arm-ac100 has not been tested and therefore not being released.
[15:08] <ogra_> infinity, do we know what we pull from for T (unstable/testing) ?
[15:08] <ogra_> cjwatson, ^^^
[15:11] <cjwatson> ogra_: unstable
[15:11] <ogra_> thx !
[15:12] <cjwatson> we're doing our own testing effectively, so most of what we get from testing would be being slowed down
[15:12] <ogra_> yeah, i agree
[15:43] <Daviey> The SRU's for openstack final are merely rc3 to final version bump, ie re-tagged.  I'm not sure on the worth of it personally, but I can recognise that there is interest in being seen to hav the /final/ version.
[15:43] <Daviey> Does anyone in ~ubuntu-sru have views on this?
[15:48] <slangasek> stgraber: so the recent comments on bug #1157643 show an interesting regression potential I hadn't considered; I've added it to the bug description.  Since you accepted the package, I wonder if you have any thoughts on this.
[15:48] <ubot2> Launchpad bug 1157643 in procps (Ubuntu T-series) "procps fail to start" [Undecided,Fix committed] https://launchpad.net/bugs/1157643
[15:49] <stgraber> slangasek: looking
[15:49] <slangasek> Daviey: well, there's a provisional MRE for OpenStack; and you can't get more micro than a plain version bump.  I'm not thrilled about a rebuild that just changes the version number, but there is value in getting rid of the ~rc3 in the version string
[15:50] <stgraber> slangasek: good points. I don't think I'd be opposed to having sysctl failing when run as non-root, however this would just be a temporary hack since soon enough we may want it to work as non-root (user namespaces)
[15:50] <slangasek> (I would draw a distinction between "getting rid of the pre-release version number", which is something we've done for packages post-freeze from time to time, and "take an upload with new upstream version numbers so that the version numbers are in sync", which happened earlier with ubuntuone)
[15:51] <slangasek> stgraber: well, the /new/ regression potential is "sysctls now get applied that weren't applied previously, due to skipped errors"
[15:51] <Daviey> slangasek: Yeah, rbasak made a good point.. we've previously had users complaining they want the latest version number.. when it's of no consequence to the user
[15:51] <stgraber> slangasek: for the second case, it's right that this may cause a change in behaviour on some systems, though I think this should be considered as a bugfix more than anything else (any container user running a full distro with sysctl probably expected sysctl to work)
[15:52] <stgraber> slangasek: note that sysctl at least partly worked in containers before since things like the IPv6 privacy options were applied fine for me
[15:52] <slangasek> stgraber: examples given in the comments include "My networking is no longer working the way it was before"
[15:52] <slangasek> (comment #38 - he attributes it to iptables, though it probably has to do with route forwarding or something)
[15:53] <stgraber> that's odd since /proc/sys/net is namespace aware and writable in containers
[15:54] <stgraber> slangasek: also note that this is on OpenVZ so on a non-standard kernel
[15:54] <stgraber> using a unofficial openvz template which does extra changes to a bunch of system files
[15:55] <slangasek> stgraber: so I was thinking that this was because sysctl was exiting with an immediate failure before fully processing all of the entries; but I've read the code now and see that this is not what's done, sysctl attempts to apply all the settings and or's their return values
[15:56] <slangasek> in which case there doesn't seem to actually be a risk
[15:56] <stgraber> slangasek: yeah, just went and re-read the code too, so it's not causing an actual behaviour change, the only difference is the return code
[15:56] <slangasek> yep
[15:58] <stgraber> oh, that's annoying... I assumed I could just update a broken container to the new procps and all would be fine, but it's not
[15:58] <stgraber> apt still insists on running the old postinst fist...
[15:58] <stgraber> *first
[15:58] <slangasek> uhm?
[15:59] <slangasek> when running what command?
[15:59] <stgraber> slangasek: http://paste.ubuntu.com/6251720/
[16:00] <slangasek> Daviey: I hope you're going through and checking that each of these packages is indeed covered by the MRE, there have been gaps before
[16:00] <Daviey> slangasek: There are two which were not.. celiometer and heat.
[16:01] <slangasek> stgraber: that's just weird
[16:01] <slangasek> Daviey: ok, and those are https://lists.ubuntu.com/archives/technical-board/2013-October/001732.html
[16:01] <Daviey> slangasek: Would you consider this to need an MRE, http://launchpadlibrarian.net/153986728/ceilometer_2013.2~rc2-0ubuntu1_2013.2-0ubuntu1.diff.gz ?
[16:02] <slangasek> Daviey: any SRU needs either an MRE or a fine-toothed comb; since ceilometer and heat are now included in the provisional MRE, I'm not getting out my comb ;)
[16:02] <Daviey> Oh yes, i forgot sabdfl +1'd it.
[16:03] <stgraber> slangasek: yeah, I certainly wasn't expecting that behavior....
[16:04] <slangasek> stgraber: it's probably affected by apt's "immediate configuration" option
[16:04] <stgraber> (FWIW, same thing on dist-upgrade, I was expecting that but wanted to make sure)
[16:04] <slangasek> because this package is so low in the stack, apt wants it to be in working order before it goes on
[16:05] <slangasek> stgraber: so see if -oAPT::Immediate-Configure=no helps
[16:08] <stgraber> slangasek: no difference
[16:08] <stokachu> is tantric tarantula official or is that a joke
[16:09] <stokachu> infinity: is this your doing? :)
[16:10] <rtg> stokachu, its a joke
[16:10] <stokachu> haha
[16:10] <doko> xnox, might be worth to prepare the boost1.54 split for the t-series, if we want to open with it
[16:10] <rtg> unless it sticks
[16:10] <Laney> I still want turgid
[16:11] <Laney> that's the kind of message we want to convey for an LTS
[16:11] <stokachu> or tony's tiger
[16:11] <stokachu> haha
[16:11] <stokachu> 14.04: Thunder Tiger
[16:11] <stokachu> sounds badass
[16:13] <stgraber> slangasek: I'm going to quickly check that it works when applied manually to all supported releases, then sru-release it so anyone who didn't update will go straight to .2 and not get the issue
[16:18] <stgraber> slangasek: hmm, so I just did the same test in a clean container and it just worked, so maybe it's some weird config I've got or something caused by packages I have installed...
[16:19] <stgraber> anyway a clean precise container => update to .1 =. update to .2 works fine
[16:19] <stgraber> that or my laptop is buggy, re-testing and looking very carefully
[16:21] <bkerensa> why does http://cdimage.ubuntu.com/releases/13.10/release/ only have server?
[16:21] <stgraber> bkerensa: because cdimage is only for things that aren't on releases.u.c
[16:22] <bkerensa> :s
[16:22] <bkerensa> ok
[16:22] <stgraber> slangasek: hmm, .1 worked fine here so it's some local weirdness, I need to first get .1 to fail, then I can properly test the SRU on my machine
[16:22] <stgraber> I suspect I need a sysctl entry to actually differ for sysctl to try to do something
[16:26] <stgraber> ok, ignore me for now, looks like apparmor isn't working with my LXC locally (limited to the daily builds so not something to worry about for Ubuntu)
[18:17] <bkerensa> noticed that https://wiki.ubuntu.com/SaucySalamandar/ReleaseNotes/Credits/ is missing
[18:18] <bkerensa> should we still add in credits for this release?
[19:45] <slangasek> bkerensa: I didn't understand why we were trying to do that in the first place; trying to exhaustively list all the people involved in the release seems like busy work to me, and missing people out by accident is worse than not doing it at all
[19:47] <xnox> doko: i have it, and I would have uploaded it to https://launchpad.net/~ubuntu-toolchain-r/+members Can you please approve me?
[19:47] <xnox> doko: i'm using "devel" nickname so it works for uploading both now and in the future to saucy/t-series (as of when it opens)
[19:47] <bkerensa> slangasek: You raise very good points I guess for the most part it served only as a form of credit for contributors since it is unlikely users would look elsewhere like changelogs :)
[19:56] <ScottK> slangasek: +1
[19:57] <xnox> ... if only we had any Technical Board members to actually open the new series, even if deciding to override the name....
[20:00] <ScottK> The TB does have one member.  Someone could ask him to override the name thing.
[20:01] <xnox> ScottK: Error: StackOverflow recursion detected.
[20:02] <slangasek> snerk
[20:04]  * xnox reads dictionary "Verb or Noun: Small sound that is emitted through the nose and mouth, usually a compressed laugh or snort. Often accompanied with a small grin, smirk, or sneer. Usually a tone of either derision, (as when someone says something you find stupid) or innocent humor. (When someone tells you a funny joke and you are busy doing something else, so a full-fledged laugh is difficult.)Nice to use behind other's backs, as when they do
[20:42] <roaksoax> Hi all! So /win 3
[21:00] <stgraber> cjwatson: when you have a minute, can you add the usual SRU bits to bug 1197766?
[21:00] <ubot2> Launchpad bug 1197766 in partman-auto (Ubuntu Precise) "Different partition layout after recovery with keep home partition" [High,In progress] https://launchpad.net/bugs/1197766
[21:01] <sil2100> Hi everyone! Can anyone from the SRU team take a look at https://bugs.launchpad.net/unity/+bug/1043627 and assess if we can release it as an SRU?
[21:01] <ubot2> Launchpad bug 1043627 in nux (Ubuntu Raring) "[SRU] Add XIM Support to Nux" [Undecided,Confirmed]
[21:01] <sil2100> (for precise)
[22:16] <med_> Timid Titmouse.
[22:17] <med_> ah Tenacious Tribbles
[22:22] <ScottK> Tardy Tiger
[23:33] <TheLordOfTime> Wubi wasn't readded for 13.10 was it?  I remember a discussion around the mailing lists around 13.04 where Wubi was dropped...
[23:48] <slangasek> TheLordOfTime: in the end, wubi did release with 13.04 after the community stepped up to maintain it, but it has been de-emphasized on the download pages
[23:50] <TheLordOfTime> slangasek, "after the community stepped up to maintain it"... does that mean it's still technically "unsupported" except by the community?  The main question about this is whether in #ubuntu and other locations it's considered "supported" or not
[23:50] <TheLordOfTime> slangasek, the wubi.exe isn't included on the ISOs, though, is it?
[23:50] <TheLordOfTime> (and it still suffers from the UEFI and Win8 incompatibilities, right?)
[23:51] <slangasek> yes, it still has incompatibilities with newer versions of Windows, which is why it's de-emphasized on the download pages
[23:51] <slangasek> it is present on the images
[23:51] <slangasek> and what does "supported" mean
[23:52] <TheLordOfTime> (exactly the issue)
[23:52] <TheLordOfTime> meh, the general question is answered, now, i might poke the relevant governance teams on whether or not a given support method covers Wubi in post-13.04
[23:55] <sarnold> cjwatson,slangasek,stgraber, is this expected? https://bugs.launchpad.net/ubuntu/+bug/1241251
[23:55] <ubot2> Launchpad bug 1241251 in Ubuntu "Some kernel modules are failing digital signature checks during boot - kernel is tainted." [Undecided,New]