[00:37] <Noskcaj> BenC, I don't have enough internet to check right now, but i believe there's a small database of debian developer locations used to find people for keysigning
[02:19] <rsalveti> xnox: was syncing the package in the archive with the branch, because I was planning on doing a small upload against it
[02:19] <rsalveti> wasn't in sync
[02:20] <rsalveti> would be nice to keep the packages in sync with the uploads
[05:52] <mitya57> lpotter: hi, is https://codereview.qt-project.org/102665 something we need to have in vivid 5.3.2 packages?
[05:52] <mitya57> I see Timo uploaded that to a silo but didn't commit to bzr for some reason.
[06:12] <pitti> Good morning
[06:12] <pitti> gnuoy`: feel free to steal merges :)
[06:14] <pitti> stgraber: network config which hangs> oh, can you please write a bug about that? will look at that ASAP
[06:15] <stgraber> pitti: bug 1414544
[06:18] <pitti> stgraber: ah, merci
[07:11] <dholbach> good morning
[08:53] <LocutusOfBorg1> hi developers
[09:39] <LocutusOfBorg1> hi pitti I'm wondering if my mail went into your spam folder :)
[09:42] <pitti> LocutusOfBorg1: no, I still have Friday's and didn't get a new one
[09:45] <LocutusOfBorg1> sent again :)
[09:51] <pitti> LocutusOfBorg1: got it
[09:52] <LocutusOfBorg1> wonderful!
[10:13] <xnox> rsalveti: yes. sorry about that. In essence there was a branch with changes "~xnox/upstart/systemd-bridge" however I've used silo to land the upload.
[10:13] <xnox> and it was manual dput, and separate branch
[10:14] <xnox> and at cleanup I did not push the branch at the same time.
[10:14] <xnox> sorry about that. Usually lp:ubuntu/upstart is up to date, or has staged changes to be uploaded next time.
[10:40] <ari-tczew> xnox: ping
[10:40] <xnox> ari-tczew: yo
[10:44] <ari-tczew> xnox: question about esys-particle package. you've added a couple of files like /debian/test/* in release 2.2.u2-2ubuntu4, but Debian has applied only one file debian/test/box30.0.geo. however, Debian approved also autopkgtest.
[10:44] <ari-tczew> xnox: can we sync that package?
[10:46] <xnox> i did not intentionally add things to debian/test dir.
[10:47] <xnox> do check if there is any delta left, and do test build in vivid before syncing
[10:49] <ari-tczew> xnox: just FYI: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/esys-particle/vivid/revision/13
[10:50] <ari-tczew> xnox: ok, delta is approved in debian and I'm building package right now.
[10:52] <tseliot> infinity: hi, do you know if this fix has ever been included in glibc? https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/967149
[12:34] <Madkiss> hey there.
[12:34] <Madkiss> is ppa.lp.net down?
[12:38] <ivoks> Madkiss: some network issues... should be over soon, if it's not already
[12:39] <Madkiss> ah, alright, thanks
[12:51] <dholbach> slangasek, who can help with the following merge proposals?
[12:51] <dholbach> https://code.launchpad.net/~ubuntu-mate-dev/debian-cd/ubuntu-mate/+merge/246189
[12:51] <dholbach> https://code.launchpad.net/~ubuntu-mate-dev/ubiquity/ubquity-mate-fixed/+merge/246079
[12:51] <dholbach> https://code.launchpad.net/~ubuntu-mate-dev/livecd-rootfs/livecd-rootfs-ubuntu-mate/+merge/244446
[13:52] <xnox> dholbach: i've tried mvo , infinity is a good one to try as well
[13:52] <xnox> i can do ubiquity myself, but at the moment my ubuntu time is focused on the hardest stuff i can work on (i.e. upstart->systemd)
[14:17] <cyphermox> xnox: thanks, I'm aware. I'll upload the fix in a bit
[14:45] <mlankhorst> what's gmsh?
[14:50] <mitya57> mlankhorst: http://launchpad.net/ubuntu/+source/gmsh — "Three-dimensional finite element mesh generator"
[14:51] <mlankhorst> I'm more curious how it blocks mesa..
[14:52] <mitya57> oh, an autopkgtest failure
[14:52] <mitya57> That seems to be a random segfault as it succeeded on amd64 and failed only on i386
[14:52] <mitya57> Perhaps pitti can retry it.
[14:53] <mlankhorst> oke
[14:53] <mlankhorst> pitti: ^ ?
[14:53] <pitti> (already at it..)
[14:53] <mlankhorst> thanks
[14:53] <pitti> err no, it's not random
[14:53] <pitti> https://jenkins.qa.ubuntu.com/job/vivid-adt-gmsh/?
[14:53] <pitti> it has never succeeded
[14:54] <pitti> i. e. it has always failed on i386, and succeeded on amd64
[14:54] <mlankhorst> ok could you override mesa then?
[14:54] <pitti> jibel: do you know why http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#mesa happens even though gmsh never succeeded?
[14:54] <pitti> jibel: https://jenkins.qa.ubuntu.com/job/vivid-adt-gmsh/?
[14:55] <pitti> mlankhorst: I will, but we shoudl investigate this first ^; I think I've seen it on other occasions
[14:56] <mlankhorst> maybe because amd64 passes?
[14:58] <jibel> pitti, looking
[15:20] <shadeslayer> is there a way to get pull-lp-source to download from vivid instead of vivid-proposed?
[15:21] <pitti> shadeslayer: just add "vivid" as the second argument
[15:21] <shadeslayer> pitti: doesn't work :(
[15:21] <pitti> shadeslayer: or "precise", "trusty-proposed", etc.
[15:21] <shadeslayer> try doing it for firefox
[15:21] <pitti> shadeslayer: sorry, "vivid-release"
[15:21] <shadeslayer> it downloads 36 here
[15:21] <shadeslayer> ah
[15:21] <shadeslayer> yep, that does the trick, thanks
[15:23] <rbasak> You can also just use the exact version string you want as the second argument.
[15:24] <rbasak> (assuming you know it already and don't have to go look it up)
[15:40] <xnox> shadeslayer: vivid-release
[15:41] <xnox> oh, sorted
[15:41]  * xnox is slow
[15:41] <shadeslayer> xnox: yeah :D
[15:46] <shadeslayer> btw firefox 35 never migrated to the release pocket in vivid?
[15:48] <xnox> shadeslayer: you should know how to check that yourself by now.
[15:49] <xnox> shadeslayer: using docs at https://wiki.ubuntu.com/ProposedMigration
[15:49] <shadeslayer> xnox: yeah, I'm just curious if someone is looking into that? or no ff 35 for vivid?
[15:49] <shadeslayer> rmadison says only 34 is available in -release and 36 in proposed, and 35 in proposed for architechtures that 36 didn't build on
[15:50] <xnox> shadeslayer: yeah, so what?
[15:50] <shadeslayer> xnox: so vivid users don't get FF 35
[15:50] <xnox> shadeslayer: 35 ftbfs on armhf, 36 ftbfs on arm64/powerpc/ppc64el. but only a complete set is ever considered for migration.
[15:50] <shadeslayer> they'll just go from 34-36?
[15:50] <shadeslayer> right, so no 35 for vivid then
[15:50] <xnox> shadeslayer: read ProposedMigration page....
[16:00] <slangasek> dholbach: cyphermox is your man
[16:00] <cyphermox> howdy!
[16:00] <dholbach> ah ok, thanks
[16:01] <dholbach> cyphermox: I just askef for flexiondotorg_ who could review his MPs:
[16:01] <dholbach>  https://code.launchpad.net/~ubuntu-mate-dev/debian-cd/ubuntu-mate/+merge/246189
[16:01] <dholbach>  https://code.launchpad.net/~ubuntu-mate-dev/ubiquity/ubquity-mate-fixed/+merge/246079
[16:01] <dholbach>  https://code.launchpad.net/~ubuntu-mate-dev/livecd-rootfs/livecd-rootfs-ubuntu-mate/+merge/244446
[16:01] <dholbach> s/askef/asked
[16:01] <cyphermox> yep, just opened them from scrollback
[16:01] <cyphermox> I'll review
[16:02] <LocutusOfBorg1> thanks pitti :)
[16:03] <cyphermox> flexiondotorg_: if you're around, I noticed there's a typo in your change to tools/add_live_filesystem for debian-cd; if you want to fix that while I continue the review.
[16:04] <slangasek> cyphermox: thanks :)
[16:13] <brainwash> we would like to push a micro release update for xfdesktop4, but it's stuck in trusty-proposed since 2 months. this bugfix update does not resolve one of the several issues completely (it's triggered less often), and therefore the verification has been marked as FAILED. however, people did not notice any regressions or new bugs.. so, can I mark the verification as DONE?
[16:13] <brainwash> it's bug 1365965
[16:42] <mitya57> Laney, hi, can you top-approve https://code.launchpad.net/~mitya57/ubuntu-themes/wncktask/+merge/245292 please? It has been approved by larsu but he can't set the status.
[16:43] <Laney> he should get in the team
[16:43] <Laney> who is Frank Schoep?
[16:43] <Laney> but yes, fine
[16:44] <mitya57> Laney: thanks
[16:47] <ari-tczew> cyphermox: congrats on get network-manager merged! I think it was a huge job.
[16:47] <bdmurray> pitti: Is it time to enable apport reporting to launchpad for Vivid?
[16:47] <cyphermox> ari-tczew: you have no idea ;P
[16:48] <ari-tczew> cyphermox: well, s/I think/I guess :P
[16:48] <cyphermox> heh. there was a test regression I hadn't quite squashed properly though, so there's an update still waiting to get to proposed; depwait due to libndp
[16:49] <pitti> bdmurray: after alpha-2 is kind of the traditional time; at some point we wanted to phase this out in favor of just errors.u.c., but I guess until we have the more elaborate "additional plugin to collect more information" powers, we should keep LP for devel?
[16:49] <ari-tczew> cyphermox: yeah, I'm looking now on bug 1392385
[16:50] <pitti> hallyn, stgraber: new systemd uploaded with the lxc cgroup ownership fix, works great now!
[16:50] <bdmurray> pitti: I think so yes
[16:50] <stgraber> pitti: great, thanks!
[16:51] <pitti> it'll be stuck in -proposed for a fair while though; powerpc builders are clogged, and arm64 too
[16:51] <stgraber> pitti: so I guess that means LXC no longer is a blocker for the switch to systemd
[16:51] <hallyn> pitti: cool, thanks
[16:51] <pitti> stgraber: indeed not; it's pretty much down to maas and juju now (for !touch)
[16:51] <pitti> hey stgraber -- did you arrive in one piece this time, without further cancellations?
[16:52] <hallyn> he hasn't left :)
[16:52] <hallyn> safely hasn't left
[16:52] <pitti> ah
[16:52] <stgraber> pitti: leaving for the airport in ~4 hours
[16:52] <stgraber> arriving at 1pm tomorrow (instead of the original 8am)
[16:57] <pitti> bdmurray: uploaded
[17:00] <pitti> infinity: are adare and ross down deliberately, or is teh "no route to host" a glitch?
[17:34] <pitti> stgraber, hallyn: oh, does the new lxc release include the fix for bug 1350947? it got committed upstream months ago, so I figure it did?
[17:35] <pitti> ah yes, it does
[17:35] <pitti> \o;
[17:35] <pitti> ouch -- \o/
[17:41] <hallyn> "doc it hurts when I do this:  \o;".  "don't do that then"
[18:19] <slangasek> mlankhorst: hi, so I notice trusty already has llvm-3.5 binary packages, from llvm-toolchain-snapshot; instead of adding a new llvm-toolchain-3.5 package in SRU, can we just use the existing llvm-toolchain-snapshot source package name?
[18:37] <infinity> pitti: Not sure what the state of ross and adare are right now, but we also haven't been using them for months.
[18:51] <doko> slangasek, mlankhorst: yes in theory, but haven't checked for packaging changes. and the llvm-toolchain-snapshot package is now blacklisted. not sure if this is relevant for trusty
[18:52] <slangasek> doko: packaging changes shouldn't matter, really?  whatever's in utopic for llvm-3.5, we would take as part of the HWE stack, this would just be taking over the llvm-toolchain-snapshot source name to reduce the archive inconsistency
[19:19] <infinity> rbasak: Any progress on LP: #1412830 ?
[19:19] <infinity> rbasak: I just realised I've been rejecting some mail because of it. :/
[19:19] <flexiondotorg_> cyphermox, Thanks for reviewing my merge proposals.
[19:20] <flexiondotorg_> cyphermox, I'll prepare re-submissions based on your feedback.
[19:20] <cyphermox> flexiondotorg_: cool; let me know and I'll merge what I can :)
[19:24] <flexiondotorg_> cyphermox, https://code.launchpad.net/~ubuntu-mate-dev/ubiquity/ubquity-mate-fixed/+merge/247641
[20:59] <bluefoxxx> Anyone else on 14.10 experiencing this?
[20:59] <bluefoxxx> http://pastebin.com/NVAv2Rrf
[21:00] <bluefoxxx> 15:59:54 up 2 days, 22:53,  3 users,  load average: 1.87, 0.72, 0.52
[21:00] <bluefoxxx> I'm using Chromium browser, Virtualbox, and Gnome-3.  /home is a separate hard disk entirely.
[21:00] <bluefoxxx> Nothing in particular going on, it's just a desktop.
[21:01] <bluefoxxx> Obviously, there are some 34GB of deleted files.  I reclaimed about 1GB by SIGHUP'ing update-manager (it was holding open deleted partial package downloads)
[21:07] <rbasak> infinity: I asked kickinz1|afk to look at it but he had to take this afternoon off. I'll follow up tomorrow.
[21:07] <infinity> rbasak: Kay.  It's pretty critical for people who haven't noticed yet. :/
[21:08] <infinity> rbasak: Once I realised the problem, was easy enough to comment out the bits, but I'm sure there are lots of people out there silently dropping mail on the floor without knowing, which sucks.
[21:08] <infinity> (Which was me, up until my brother complained a few hours ago)
[21:08] <bluefoxxx> why oh why isn't there an open-deleted-file histogram tool
[21:08] <bluefoxxx> that needs to be an option in ncdu
[21:09] <bluefoxxx> I'm having no luck tracking this down with lsof :|
[21:10] <infinity> bluefoxxx: Not to be facetious or ruin your fun, but if you're putting that much effort into hunting down open handles on deleted files to try to fix them, why not just reboot and be done with it?
[21:10] <bluefoxxx> infinity, the system has been up for 2 days and done nothing special
[21:11] <bluefoxxx> Am I to believe Ubuntu simply bloats space usage with deleted files as normal, accepted behavior, and will use dozens of gigabytes of space and need a reboot every couple days?
[21:11] <bluefoxxx> 13GB of files, 47GB of used space
[21:11] <infinity> bluefoxxx: No.  And that's not "normal" here.
[21:11] <bluefoxxx> that's my issue
[21:11] <bluefoxxx> nobody told me there was a 100GB / partition requirement to run this system
[21:11] <infinity> bluefoxxx: So whatever non-special thing you aren't doing, I'm not doing it harder. :P
[21:12] <bluefoxxx> wait.  it's btrfs.
[21:13]  * bluefoxxx squints really hard.
[21:13] <jrwren> ha! btrfs strikes again.
[21:13] <bluefoxxx> oh haha.
[21:14] <bluefoxxx> Can you guess what happened?
[21:15] <bluefoxxx> http://pastebin.com/Z6v1e7e5
[21:16] <infinity> bluefoxxx: That doesn't look like it "suddenly" happened over 2 days. :P
[21:16] <bluefoxxx> infinity, I said it's been up for 2 days
[21:17] <bluefoxxx> I didn't say i ever looked before
[21:17] <bluefoxxx> also, holy crap, snapshots have been automatic since quantal
[21:20] <bluefoxxx> well, that got me down to 35G.  :|
[21:20] <bluefoxxx> I'll continue my investigation.
[21:24] <flexiondotorg_> cyphermox, Thank you!
[21:28] <cyphermox> flexiondotorg_: np. maybe by tomorrow we can merge things, I need to wait for mvo and cjwatson for some questions and some buttons I can't push  ;)
[21:29] <flexiondotorg_> cyphermox, No probs. Thanks for helping.
[21:44] <infinity> utlemming: Can you look at LP: #1414752 and reassign, fix, close as appropriate?
[21:45] <utlemming> infinity: ack, looking now
[22:13] <smoser> does anyone else belive that update-initrramfs gets called during 'apt-get upgrade|isntall' more than its supposed to?
[22:13] <utlemming> *\
[22:13] <infinity> smoser: Yes, Andy and I have a plan.
[22:14] <sarnold> infinity: yay :)
[22:14] <smoser> infinity, is there a bug ?
[22:15] <infinity> smoser: There may be, but we're not tracking one that I know of.
[22:15] <infinity> smoser: It's a fundamental rewrite of how initramfs-tools and the kernel interact for triggers, not a simple "oh, this is a bit broken" bugfix.
[22:16] <infinity> pitti: Don't suppose you're still around?
[22:53] <infinity> mlankhorst: Minor complaint (which I'm not rejecting for, but should be fixed).  Many of the lts-X packages have a symlink to usr/share/bug/xserver-xorg-core/script which isn't being placed in the right renamed spot.


[12:00] <blaze> RikMills: is it time for 5.67 already?
[12:01] <RikMills> it is out today
[12:01] <blaze> I see
[12:24] <BluesKaj> Howdy all
[15:47] <santa_> RikMills: I have a fix for the baloo acc test, I'm going to push it as soon as it's tested, ok?
[15:50] <RikMills> santa_: ok, I am just pushing stuff, so pull 1st please once that is done for all fw
[15:51] <santa_>  ugh
[15:58] <RikMills> x86 build farm is a bit broken, so I uploaded already. particularly as a rebuild of most of fw was done by a core-dev earlier against new binutils, and if I did not do it straight after our fw would be queued behind a bazillion tests!
[15:59] <RikMills> and I want most of fw out of the way for plasma 5.18 on Tuesday
[20:33] <santa_> RikMills: done. be careful because I think latest apt from focal is crashing sometimes
[20:49] <blaze> mine never did actually so far, try maybe to recreate your index


 share: Ron Paul uses BitchX, why don't you?
[02:38] <bazhang> and more in that vein
[04:09] <Flannel> Ron Paul wouldn't use BitchX.  It's unsupported.
 FlyOnZeWall,  may as well just go with Windows instead of Winbuntu
[17:11] <bazhang> first time to hear that one
[17:31] <bazhang> flyzoola was repeatedly asking for support of 11.04


[15:14] <bcurtiswx> nigelb, so why the dislike towards SVN? :P
[15:14] <nigelb> bcurtiswx: I like git :D
[15:14] <nigelb> bcurtiswx: and generally, dvcs
[15:14] <bcurtiswx> nigelb, ah i guess i've used all before and have gotten used to the differences for the most part
[15:15] <nigelb> bcurtiswx: yeah, I've used all of them at some point
[15:15] <nigelb> bcurtiswx: oh btw, want to talk about upstreaming bugs at UDW?
[15:15]  * nigelb is in recruitment mode
[15:16] <bcurtiswx> what day
[15:16] <nigelb> bcurtiswx: pick an empty slot https://wiki.ubuntu.com/UbuntuDeveloperWeek/Timetable#preview
[15:31] <nigelb> bcurtiswx: final decision? :)
[15:32] <bcurtiswx> nigelb, i'm thinkin :)
[15:33] <nigelb> hehe
[15:33] <nigelb> bcurtiswx: feel free to team up with pedro or hggdh or charlie-tca :D
[15:34] <hggdh> heh
[15:35] <nigelb> the very subtle form of recruitment ;)
[15:35] <bcurtiswx> any of you want to do a session on "Bugs: Head to Dead.
[15:35] <bcurtiswx> "
[15:35] <bcurtiswx> maybe two sessions worth
[15:36] <bcurtiswx> OK, maybe that was a bad play on words
[15:37] <bcurtiswx> Where we triage a couple bugs live, from NEW to Triaged
[15:39] <bcurtiswx> hggdh gets the interest with the obvious public attraction, and i just get to stamp my name on it. how about it :P
[15:39] <charlie-tca> Do you really want to start at "New" if you are talking to developers?
[15:40] <bcurtiswx> charlie-tca, good point.
[15:40] <bcurtiswx> but how well do devs understand our triaging techniques?
[15:41] <charlie-tca> bcurtiswx: valid point, too. Some do, perhaps most do not?
[15:43] <bcurtiswx> charlie-tca, i don't know.
[15:45] <bcurtiswx> hggdh, charlie-tca, bdmurray: Would a "Bug Triage: NEW to TRIAGED" really benefit dev's in your own opinions
[15:48] <bdmurray> bcurtiswx: that seems more appropriate for open week
[15:48] <charlie-tca> A developer working his bugs doesn't really care what our steps are. If they can fix the bug, it could jump from New to Fixed in one step
[15:50] <bcurtiswx> nigelb, i think that best sums up that.  Sorry :)
[15:50] <nigelb> bcurtiswx: well, you could always talk about upstreams and their importance ;)
[15:51] <bdmurray> One thing I've talked about in the past is how to get better quality bug reports
[15:51] <bdmurray> by writing apport hooks for example
[15:52] <nigelb> oh, apport hooks would be a fun session
[15:52] <nigelb> when I wrot them, I kept looking at your sessions bdmurray :)
[15:52] <charlie-tca> That would be good, but I know nothing about that...
[15:53] <bcurtiswx> nigelb, you have your own session to run then ;)
[15:54] <nigelb> oh no
[15:54] <nigelb> how did I fall into that trap
[15:54] <nigelb> :-P
[15:54] <nigelb> bdmurray: can you help me if I'm willing to take an apport session? :)
[15:55] <bdmurray> nigelb: sure when is it?
[15:55] <nigelb> 1600 4th March?
[15:57] <bdmurray> okay that's a fair bit of time
[15:58] <nigelb> \o/
[15:58] <nigelb> session added
[16:23] <Gartral> hello, I see a fix was posted for Gobi2k 3g radios in Kernel, (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554099?comments=all) but I can't use that Kernel due to a TPM-locked Kernel architecture.. and I was hoping the needed driver was available as a Module.. my other problem is I can't compile the module myself as until i fix 3g in ubuntu, my computer won't have internet.
[16:23] <ubot4> Launchpad bug 554099 in linux-backports-modules-2.6.32 (Ubuntu Maverick) (and 9 other projects) "Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken (affects: 73) (dups: 4) (heat: 424)" [Undecided,Invalid]
[16:24] <Gartral> yes ubot4 that's the package and bug.
[16:41] <gondoi> I'm a little confused on the SRU instructions...
[16:41] <gondoi> I want to submit an SRU for this bug
[16:41] <gondoi> https://bugs.launchpad.net/ubuntu/+source/munin/+bug/699967
[16:41] <ubot4> Launchpad bug 699967 in munin (Debian) (and 2 other projects) "Empty list of plugins/services with hostname containing uppercase letters (affects: 2) (dups: 1) (heat: 20)" [Unknown,Confirmed]
[16:41] <gondoi> but I'm not sure whether to submit it in that bug or start a new one
[16:42] <gondoi> can anyone help me?
[16:42] <charlie-tca> a little patience is appreciated. We are all volunteers, not sitting looking at the monitor waiting for questions.
[16:42] <gondoi> same here
[16:43] <gondoi> just throwing it out there and waiting for a reply
[16:43] <charlie-tca> and expecting an answer within a minute?
[16:44] <Gartral> hello, I see a fix was posted for Gobi2k 3g radios in Kernel, (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554099?comments=all) but I can't use that Kernel due to a TPM-locked Kernel architecture.. and I was hoping the needed driver was available as a Module.. my other problem is I can't compile the module myself as until i fix 3g in ubuntu, my computer won't have internet.
[16:44] <ubot4> Launchpad bug 554099 in linux-backports-modules-2.6.32 (Ubuntu Maverick) (and 9 other projects) "Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken (affects: 73) (dups: 4) (heat: 424)" [Undecided,Invalid]
[16:44] <charlie-tca> gondoi: Use the same bug, nominate for series "maverick"
[16:44] <gondoi> dude, it wasn't intended as a bump... just asking for assistance
[16:44] <gondoi> thank you charlie-tca
[16:44] <charlie-tca> You are welcome
[16:44] <Gartral> (if waiting 20 minutes between posts aint long enough, sorry, trying too compensate for joins which i turned off...
[16:45] <charlie-tca> Gartral: I would suggest asking in #ubuntu-kernel, also, for that issue. They might have a workaround you can use.
[16:46] <shankhs> hi
[16:47] <Gartral> charlie-tca: maybe, maybe not, keep in mind im forced too use a kernel that I don't even have headers for... so compiling my own module isn't an option
[17:04]  * micahg wonders if we're having a meeting
[17:04] <micahg> hggdh: charlie-tca: yofel: bdmurray ^^^
[17:05] <Gartral> ?/?
[17:05] <shankhs> Hi i am very much eager to participate in bug day (10 feb ) but I have never done any bug-fixing for ubuntu before . Also I have never saw the code of OpenOffice or LibreOffice. How do I get started with this? I have signed the ubuntu code of conduct and read the Triage guide. Thanks a lot for the help
[17:05]  * yofel totally forgot about it, thanks for the ping
[17:06] <micahg> shankhs: can you stick around another hour, we're supposed to have a meeting now, but it might not happen
[17:06] <shankhs> micahg: sure!
[17:07]  * micahg doesn't see pedro
[17:09] <bdmurray> micahg: pedro is on holiday
[17:09] <micahg> bdmurray: ah, good for him :)
[17:09] <micahg> bdmurray: well, should we have a meeting or defer 1 week?
[17:10] <bdmurray> micahg: looking at the agenda it needs some cleanup and no announcement was sent so I'd pefer to wait
[17:10] <bolster> Hey all, I'm new to the bugsquad (and haven't exactly contributed yet, but exams finished this week so I should be a productive human being tomorrow). Have read most / all of the knowledgebase so hopefully can hit the ground running as soon as I can block off some time for it :D
[17:11] <micahg> bdmurray: ok, makes sense
[17:11] <yofel> +1
[17:14] <bdmurray> okay, I'll take care of the agena, email and channel topic
[17:15] <micahg> bdmurray: thanks,
[17:16] <micahg> shankhs: so, it's just a matter of installing LIbreOffice and seeing if you can reproduce the OpenOffice bugs, if so, add a bug task for LibreOffice
[17:16] <micahg> I think
[17:16] <bdmurray> right you don't need to know the code to help out triaging bug reports
[17:17] <micahg> bdmurray: are we adding tasks for LibreOffice or moving the bugs? (not everyone might know if something's SRU worthy or not)
[17:18] <shankhs> micahg bdmurray : thanks any more pointers
[17:18] <bdmurray> micahg: adding seems the easiest to me
[17:19] <micahg> bdmurray: ok, thanks
[17:20] <vish> bdmurray: hi.. when you get some time, could you have a look at Bug #659947 ? thanks! :)
[17:20] <ubot4> Launchpad bug 659947 in launchpad "Users, unfamiliar with bug-triage, often confuse 'Triaged' and 'Confirmed' status (affects: 2) (heat: 10)" [Low,Triaged] https://launchpad.net/bugs/659947
[17:34] <bdmurray> vish: what are you looking for with that bug?
[17:35] <vish> bdmurray: some solution to prevent redoing the confirmed -> triaged work..
[17:36] <vish> ie, not revisiting the triaged bugs again..
[17:37] <vish> bdmurray: it is a follow up bug, to the earlier one where i suggested locking down the permissions as to who changes those, but their feedabck was a better solution was to looking at reducing the number of statuses
[17:38] <vish>  to merge triaged and confirmed
[17:38] <Gartral> hello, I see a fix was posted for Gobi2k 3g radios in Kernel, (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554099?comments=all) but I can't use that Kernel due to a TPM-locked Kernel architecture.. and I was hoping the needed driver was available as a Module.. my other problem is I can't compile the module myself as until i fix 3g in ubuntu, my computer won't have internet.
[17:38] <ubot4> Launchpad bug 554099 in linux-backports-modules-2.6.32 (Ubuntu Maverick) (and 9 other projects) "Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken (affects: 73) (dups: 4) (heat: 424)" [Undecided,Invalid]
[17:38] <bdmurray> vish: okay
[17:39] <micahg> vish: I think that's a bad idea, confirmed means there's a real bug, but not enough information to work on it, triaged means there's enough information to work on it
[17:40] <vish> micahg: yea.. thats how i thought so too.. but sinzui and mpt suggestion seemed OK.. but i'll take whatever fixes the current situation ;)
[17:42] <micahg> Gartral: you might want to ask in #ubuntu-kernel about that
[17:53] <ddecator> assuming my calendar is correct, there is a bugsquad meeting starting in a few minutes, right?
[17:55] <micahg> ddecator: calendar is wrong :)
[17:56] <ddecator> micahg: what the, i swear i copied it from the fridge calendar..
[17:57] <ddecator> micahg: ...from your calendar
[17:57] <micahg> ddecator: yeah, I saw that, idk why it was set for 18:00, meeting was 17:00 I thought, but in any case, no announcement and an old agenda postponed the meeting
[17:57] <ddecator> micahg: ah, gotcha. when is it now?
[17:58] <micahg> ddecator: TBA
[17:58] <ddecator> micahg: alright, thanks
[19:33] <Rcart> hello, there are logs available for the talk that took place today?
[19:34] <ddecator> Rcart: the meeting? it's being rescheduled
[19:36] <Rcart> ddecator: Oh, great. 10 February right?
[19:36] <ddecator> Rcart: i don't think a new time has been determined yet
[19:37] <charlie-tca> It should change in the topic here when it is decided
[19:37] <Rcart> ddecator: Thanks, I was confusing it with the Hug Day date ^^
[19:38] <hjd> Hi. I'm tagging some bugs 'upgrade-software-version' and wondered what (if anything) I should do with bugs tagged 'upgrade'. Should I replace the tag with usv, add it in addition or leave them alone?
[19:39] <Rcart> charlie-tca: I'll be waiting for the update then :). Thanks.
[19:40] <bdmurray> micahg: what did we decide about upgrade vs upgrade-software-version?  I'd say keep the old one
[19:41] <micahg> bdmurray: hmm, I've been using the new one?  either way is fine, there are only about 15 wtih the new tag
[19:42] <charlie-tca> seems like it would depend on the actual bug, if they used upgrade in place of upgrade-software-version or to report a bug that happened during an upgrade
[19:42] <micahg> charlie-tca: upgrade bugs are supposed to be specified by their releases (i.e. lucid2maverick)
[19:42] <charlie-tca> I know, but that doesn't mean the reporter did not add "upgrade".
[19:42] <bdmurray> micahg: if the bug is already tagged upgrade I'd say keep that tag
[19:43] <micahg> bdmurray: ok, I've just been adding, not changing
[19:43] <bdmurray> hjd: so add usv inaddition to upgrade
[19:44] <bdmurray> hjd: thanks for asking
[19:45] <hjd> ok. I've left them alone so far, just thought I'd check.
[19:51] <hjd> For some requests for newer versions, I've found similar bug reports in debian as well. However, the Ubuntu bug and Debian bugs mention different versions. Should I add a bugwatch to these or not? As a new release might fix one of the bugs, but not the other. (I can probably find an example)
[19:55] <hjd> for instance bug 451947 vs http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599617. (Perhaps a bad example, as the difference i version numbers are pretty small)
[19:55] <ubot4> Debian bug 599617 in php-codesniffer "php-codesniffer: New upstream version available" [Wishlist,Open]
[19:55] <ubot4> Launchpad bug 451947 in php-codesniffer (Ubuntu) "Version bump request (1.2.0) (affects: 2) (heat: 7)" [Undecided,New] https://launchpad.net/bugs/451947
[20:05] <bdmurray> hjd: I think making the ubuntu one less version specific and linking to the debian bug is a good idea
[20:19] <hjd> bdmurray: something like this (bug 451947)?
[20:19] <ubot4> Launchpad bug 451947 in php-codesniffer (Debian) (and 1 other project) "Version bump request (affects: 2) (heat: 12)" [Unknown,Unknown] https://launchpad.net/bugs/451947
[20:20] <bdmurray> hjd: yes - you could also confirm since you know ubuntu is behind
[20:23] <hjd> bdmurray: confirmed as well. Wasn't aware I should do taht.
[20:23] <hjd> *that


[15:11] <tjaalton> upgraded my noble laptop, and now firefox has no audio (output/mic)
[15:12] <tjaalton> the kernel didn't change
[15:15] <seb128> tjaalton, is it specific to firefox?
[15:17] <tjaalton> seb128: seems like it, the audio capplet shows both working and vlc at least works
[15:17] <tjaalton> ffox is at 121
[15:17] <seb128> weird
[15:17] <seb128> any apparmor denial in the journal?
[15:21] <tjaalton> no, but errors from wireplumber
[15:21] <tjaalton> "pipewire links failed to activate"
[16:03] <jbicha> tjaalton: what version of pipewire do you have installed & have you logged out since updating pipewire last?
[16:03] <jbicha> are you using the Firefox snap?
[16:04] <jbicha> current Firefox is 122
[16:11] <jbicha> we will be backporting the pipewire snap work to mantic so we do want to understand where it is breaking people's workflows first
[16:12] <tjaalton> I've rebooted, and updated the firefox snap too but that didn't help
[16:13] <tjaalton> pipewire is 1.0.1-1ubuntu3
[16:21] <Rastersoft> Hi all
[16:25] <jbicha> Rastersoft: could you help us find logs or other useful info from tjaalton's system to try to understand why pipewire isn't working right
[16:27] <Rastersoft> Yes
[16:28] <Rastersoft> It would be great to have the full logs...