[05:20] <mborzecki> morning
[07:45] <zyga> re
[07:46] <zyga> 30 min
[07:46] <zyga> till meds
[07:47] <zyga> thank you for moving the call
[07:48] <zyga> uh, lots of pain
[08:14] <mborzecki> pedronis: hi, wondering maybe we should try to cherry-pick to 2.45 the commits that tweak spread.yaml so that we get the caching behavior from master
[08:19] <mup> PR snapd#9042 opened: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>
[08:22] <pedronis> mborzecki: yes, possibly, I'm still trying to land #9012 first
[08:22] <mup> PR #9012: release/2.45: merge 2.45.2 release <Created by mvo5> <https://github.com/snapcore/snapd/pull/9012>
[08:40] <mup> PR snapd#9043 opened: daemon: decompose access check into smaller primitive access checkers <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9043>
[08:45] <mup> PR snapd#9044 opened: github: cherry-pick gh-action fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[08:45] <mborzecki> pedronis: ^^ let's see how far that PR will run
[09:16] <zyga-x240> okay, so this is much more lucid now
[09:16] <mborzecki> zyga-x240: https://github.com/snapcore/snapd/pull/9042 apparmor cherrypicks
[09:16] <mup> PR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>
[09:16] <mborzecki> zyga-x240: and https://github.com/snapcore/snapd/pull/9044 that's the gh actins caching tweaks
[09:16] <mup> PR #9044: github: cherry-pick gh-action fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[09:16] <mborzecki> and it's red (unsurprisingly?)
[09:18] <ogra_> hmm, does command-chain only work for nondaemon apps ?
[09:18] <zyga-x240> ogra_: it should not matter
[09:18] <ogra_> (it does nto seem to get executed for me )
[09:18] <ogra_> *not
[09:19] <ogra_> weird
[09:19] <zyga-x240> looking at the failures
[09:19] <ogra_> oh !
[09:20] <ogra_> seems snapcraft ignores changes in snap/local (where my script lives) 😛
[09:20] <zyga-x240> just preseed failures
[09:20]  * ogra_ manually cleans the part
[09:20] <zyga-x240> well, in 19.10 - more failures elsewhere
[09:21] <zyga-x240> shellcheck issues
[09:45] <zyga-x240> pain slowly going away
[09:59] <mborzecki> pedronis: i've left a note about failures in https://github.com/snapcore/snapd/pull/9012 i think we should just force merge and i'll start cherry-picking the obvious things (cc zyga-x240)
[09:59] <mup> PR #9012: release/2.45: merge 2.45.2 release <Created by mvo5> <https://github.com/snapcore/snapd/pull/9012>
[10:00] <zyga-x240> looking
[10:01] <zyga-x240> I've ran the unit tests test alone and it passed
[10:01] <zyga-x240> so maybe random as well
[10:01] <zyga-x240> ah drat, wrong branch
[10:01] <pedronis> mborzecki: thx, other emergency maybe solved
[10:01] <pedronis> we'll see
[10:01] <zyga-x240> I agree we should merge
[10:01] <zyga-x240> and iterate
[10:01] <pedronis> I'look in a bit
[10:07] <pedronis> zyga-x240: mborzecki: merged
[10:07] <pedronis> mborzecki: it seems most thing you mentioned worth cherry picking are kind of small?
[10:07] <pedronis> mborzecki: maybe worth doing one PRs with them, most of them?
[10:07] <pedronis> to 2.45?
[10:08] <mborzecki> pedronis: yes, i'll do it
[10:08] <mborzecki> pedronis: thanks for merging the branch
[10:10] <mup> PR snapd#9012 closed: release/2.45: merge 2.45.2 release <Created by mvo5> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/9012>
[10:12] <zyga-x240> we have this 41d38c4b7f7554bdef88d567608241930a237cd9
[10:13] <zyga-x240> let me check if that is in the release branch
[10:13] <zyga-x240> (nfs fix)
[10:14] <mborzecki> zyga-x240: ah, cool
[10:15] <zyga-x240> one sec
[10:15] <mup> PR snapd#9039 closed: cmd/snap-seccomp/syscalls: add faccessat2 (2.45) <Simple 😃> <⛔ Blocked> <Created by bboozzoo> <Closed by pedronis> <https://github.com/snapcore/snapd/pull/9039>
[10:16] <zyga-x240> https://github.com/snapcore/snapd/pull/9045
[10:16] <mup> PR #9045: Disable part of the nfs-support test that checks udp proto on debian-… <Created by zyga> <https://github.com/snapcore/snapd/pull/9045>
[10:17] <zyga-x240> now about https://github.com/snapcore/snapd/pull/9044
[10:17] <mup> PR #9044: github: cherry-pick gh-action fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[10:17]  * zyga-x240 looks at failures
[10:17] <mborzecki> zyga-x240: looked at failures already, i'll stat pushing cherry-picks there
[10:17] <mborzecki> zyga-x240: also, will pick 9045
[10:17] <zyga-x240> ok
[10:20] <mup> PR snapd#9045 opened: Disable part of the nfs-support test that checks udp proto on debian-… <Created by zyga> <https://github.com/snapcore/snapd/pull/9045>
[10:23] <mborzecki> zyga-x240: pushed most to #9044, i need to look at the PR with preseed tests, either pick everything from it or just https://github.com/snapcore/snapd/commit/0a9a25f1b4c3a711a96874a1d14933d01a97e0e8
[10:23] <mup> PR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[10:28] <zyga-x240> mborzecki: shall I push there directly?
[10:30] <mborzecki> zyga-x240: hmm, yes, but maybe let's wait for spread jobs to run through
[10:30] <zyga-x240> ok
[10:33] <mborzecki> zyga-x240: btw. tests/main/lxd has changed quite a bit, one from 2.45 branch is failing spread-shellcheck locally here: https://paste.ubuntu.com/p/W9htPXc3bx/
[10:35] <mborzecki> zyga-x240: hm fixes are trivial, so i'll just fix it rather than picking even more patches :/
[10:37] <zyga-x240> eh, silly shellcheck
[10:37] <zyga-x240> ok
[10:48]  * zyga-x240 backported preseed fixes, testing now
[10:52]  * zyga-x240 looks at go
[11:03] <zyga-x240> https://github.com/snapcore/snapd/pull/9046 has the preseed changes, it should be merged into https://github.com/snapcore/snapd/pull/9044 when another round of tests passes
[11:03] <mup> PR #9046: tests: backport preseed test fixes to 2.45 <Created by zyga> <https://github.com/snapcore/snapd/pull/9046>
[11:03] <mup> PR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[11:04] <mborzecki> zyga-x240: thanks
[11:05] <mborzecki> wow, commits form april
[11:05] <mborzecki> from
[11:05] <zyga-x240> we should release 2.46
[11:05] <zyga-x240> even if it's not in stable
[11:05] <zyga-x240> just try to iterate
[11:05] <mup> PR snapd#9046 opened: tests: backport preseed test fixes to 2.45 <Created by zyga> <https://github.com/snapcore/snapd/pull/9046>
[11:06] <mborzecki> zyga-x240: hm maybe i should just cherry-pick everything from 9046 to 9044
[11:06] <zyga-x240> yes
[11:06] <zyga-x240> git merge it
[11:06] <mborzecki> mhm
[11:06] <zyga-x240> I opened it separately to see how it behaves
[11:06] <mborzecki> will do
[11:14] <mborzecki> zyga-x240: one more cherry-pick i didn't notice before: https://github.com/snapcore/snapd/commit/6c09de0f3f
[11:14] <zyga-x240> ah
[11:15] <zyga-x240> put it directly into your fixes branch
[11:23] <mborzecki> yup
[11:37] <pedronis> mborzecki: the plan is to land only 9044?
[11:39] <mborzecki> pedronis: yes, i plan to push necessary fixes to 9044, land it, and then rebase #9042 on top
[11:39] <mup> PR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>
[11:40] <mborzecki> pedronis: the good part is that most changes, if not all are in tests
[11:41] <pedronis> mborzecki: sounds good
[11:44] <zyga-x240> hmmm
[11:44] <zyga-x240> is there anything in go that guarantees errno is set to zero before C calls?
[11:44] <zyga-x240> because if not then user/ is buggy
[11:55] <zyga-x240> ijohnson: around?
[11:55] <zyga-x240> mborzecki: maybe cherry pick the travis test away as well :D
[11:56] <pedronis> zyga-x240: go in general does it own syscall handling, it not following C conventions
[11:57] <ijohnson> zyga, not quite yet still having breakfast but I'll be into the office in 30 min or so
[11:57] <pedronis> I suspect cgo does the right thing
[11:57] <pedronis> but would need to dig
[11:57] <zyga-x240> mmm
[11:57] <zyga-x240> ijohnson: ok
[11:57] <zyga-x240> talk to you later
[11:58]  * zyga-x240 reviewed https://github.com/snapcore/snapd/pull/9041#pullrequestreview-453246893
[11:58] <mup> PR #9041: osutil/group.go: treat all non-nil errs from user.Lookup{Group,} as Unknown* <Bug> <Preseeding 🍞> <⚠ Critical> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9041>
[11:58] <mborzecki> zyga-x240: all of it now https://github.com/snapcore/snapd/pull/9044 hopefully we can land it once the spread jobs finish
[11:58] <mup> PR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[11:58] <zyga-x240>  brb
[12:03] <paul424> I try to modfiy the file : /snap/opendungeons/27/etc/opendungeons/plugins.cfg  ; I get non-writable file system. What should I do to modfiy the aforementioned file ? :)
[12:05] <mborzecki> paul424: is this fil expected to be modified by the end users?
[12:06] <mborzecki> heh, we have `var osutilFindGid = osutil.FindGid` in journal.go which does not appear to be used?
[12:06] <paul424> well yes and no, the friend of mine created ad hoc solution of packaging the OD into snap; usually the user is expected to modfiy the file plugins.cfg in Ogre3d game engine for example : to set the proper path of the rendering plugins
[12:07] <mborzecki> pedronis: all patches (sans apparmor backports) are now in https://github.com/snapcore/snapd/pull/9044 if you want to take a look
[12:07] <mup> PR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[12:07] <paul424> so... but I remember I somehow by-passed this and run succesfully OD .... problem is I don't remember how...
[12:07] <mborzecki> paul424: as those plugins something the user is expected to be able to add later?
[12:08] <mborzecki> s/as/are/
[12:08] <paul424> mborzecki: the rendering plugins comes with Ogre3d engine hmm ....
[12:09] <paul424> PluginFolder=/usr/lib/OGRE
[12:10] <paul424> cause troubles, also shoudn't that be reassigned to diffrent path if it is running under snap ? That is to the path of Snap's Ogre library ?
[12:13] <paul424> the snap ogre lib is in :  /snap/ogre/151/lib/
[12:13] <paul424> Does snapper create a virtual executable envoierment or something ?
[12:14] <zyga-x240> paul424: snaps are immutable filesysytems, they cannot be modified at all
[12:14] <paul424> great
[12:14] <zyga-x240> paul424: snap author should arrage for files that need to be modified to live in other places
[12:14] <zyga-x240> paul424: like $SNAP_DATA or $SNAP_USER_DATA
[12:14] <zyga-x240> paul424: there are ways to make this work but it requires some cooperation with the snap author
[12:14] <mborzecki> zyga-x240: in this case it sounds like ogre (the engine) is expected to be a content snap?
[12:15]  * zyga-x240 doesn't want to jump into details
[12:16] <paul424> thanks for enlighting me :D
[12:34] <zyga-x240> mborzecki: https://github.com/snapcore/snapd/pull/9044 looks optimistic
[12:34] <mup> PR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[12:34]  * ijohnson is back
[12:34] <mborzecki> zyga-x240: yup
[12:34]  * ijohnson or maybe here for first time today
[12:34] <zyga-x240> ijohnson: +1 on the error checking for user lookup PR
[12:34] <ijohnson> thanks
[12:34] <zyga-x240> I had a look through go and meh
[12:35] <mborzecki> ijohnson: o hi, fun stuff with user lookup :/
[12:35] <zyga-x240> too much inconsistency
[12:35] <ijohnson> yeah it's a bit disappointing, but then again the man page for getgrpnam_r does kinda say it's impossible anyways
[12:35] <ijohnson> mborzecki: oh? what more fun stuff ?
[12:35] <zyga-x240> ijohnson: but I would expect _some_ level of consistency
[12:35] <zyga-x240> between the various backends
[12:35] <zyga-x240> but no, that's not the case
[12:36] <ijohnson> yeah
[12:37] <pedronis> zyga-x240: regarding your errno question, go in general seems to do it's own syscall handling, about cgo afaict it works as expected because th c code gets its own tls stuff, but this is as usual slightly hard to follow in the go code
[12:37] <zyga-x240> pedronis: right, I was only curious because some calls do not reset errno
[12:37] <zyga-x240> and I was wondering if cgo explicitly sets errno = 0 ahead of all calls
[12:38] <zyga-x240> the real bug is in the higher layer in go
[12:38]  * zyga-x240 starts a test and takes that break
[12:40] <pedronis> zyga-x240: anyway cgo itself seems to emit "errno = 0" in some cases
[12:42] <pedronis> zyga-x240: see cmd/cgo/out.go in go itself
[12:43]  * zyga-x240 looks
[12:49] <mborzecki> ijohnson: while you're around, can you take a look at https://github.com/snapcore/snapd/pull/9030 ? :)
[12:49] <mup> PR #9030: bootloader/assets: helpers for registering per-edition snippets, register snippets for grub <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9030>
[12:49] <zyga-x240> mborzecki: tests are failing on ...
[12:49] <zyga-x240>  2020-07-22T12:22:24.0548501Z        /tmp/sanity-squashfs-830795014: no space left on device
[12:50] <zyga-x240> 2020-07-22T12:22:24.0542897Z ##[error]2020-07-22 12:22:24 Error executing google:ubuntu-19.10-64:tests/main/install-store-laaaarge (jul221201-927192) :
[12:50] <mborzecki> pfffff
[12:50] <ijohnson> mborzecki: ah so sorry yes I will submit it now, I wrote all the comments and it seems I forgot to submit it :-)
[12:50] <zyga-x240> another failed on EOF from reboot
[12:50] <zyga-x240> 2020-07-22T12:42:59.1435778Z ##[error]2020-07-22 12:42:59 Error executing google:ubuntu-core-16-64:tests/core/reboot (jul221201-861200) : kill-timeout reached after jul221201-861200 (google:ubuntu-core-16-64:tests/core/reboot) reboot request
[12:51] <mborzecki> heh, gdoc does not like firefox
[12:51] <zyga-x240> one failed on preparing due to purge
[12:51] <mborzecki> zyga-x240: lxd?
[12:51] <zyga-x240> no, just prepare up front
[12:51] <ijohnson> mborzecki: submitted
[12:51] <zyga-x240> one more is in progress
[12:51] <mborzecki> zyga-x240: 8883 is still waiting
[12:52] <mborzecki> ijohnson: thanks
[12:52] <zyga-x240> I'd restart the three to see if they can land cleanly
[12:52] <zyga-x240> but I'd be fine with override as well
[12:52] <ijohnson> mborzecki: but did you see my question in IRC earlier? was there something else to know about the user stuff ?
[12:52] <mborzecki> ijohnson: probably missed it, what was the question?
[12:53] <ijohnson> mborzecki: oh you just said there was more fun, and I wasn't sure if you were just referring to the situation in general or something else that you found after looking at the PR
[12:53] <zyga-x240> mborzecki: 640GB should be enough for a google doc
[12:54] <mborzecki> ijohnson: ah, nah just the general state of things around that area
[12:54] <ijohnson> yeah rather sad
[12:54] <ijohnson> but good that we debugged it in MM some more and it sounds like CPC has a way forward in the meantime while waiting for the fix
[13:01] <mborzecki> zyga-x240: that failure in prepare is 8883
[13:01] <pedronis> ijohnson: standup?
[13:01] <ijohnson> yes
[13:02] <ijohnson> cachio: SU?
[13:16] <mborzecki> zyga-x240: restarted the spread job in https://github.com/snapcore/snapd/pull/9044
[13:16] <mup> PR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[13:16] <zyga-x240> ok
[13:27] <zyga-x240> ahh
[13:27] <zyga-x240> there's one thing I didn't do that jamie surely did
[13:27] <zyga-x240> run this as user!
[13:27] <mborzecki> zyga-x240: the caching behavior in #9044 is such a nice improvement now that i restarted the ci job
[13:27] <mup> PR #9044: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[13:27] <zyga-x240> :D
[13:43] <zyga-x240> why do we even bother with hangouts on non-mobile devices, mobile experience is just so much better
[13:44] <pedronis> zyga-x240: mborzecki: we can close 9045 and 9046 right?
[13:44] <zyga-x240> checking
[13:44] <zyga-x240> yes
[13:44] <zyga-x240> they are now in the big PR
[13:45] <ijohnson> pedronis: ok, so looking again the ones that are blocking things are these PR's: 8890, 8612, 8854, 8652, and 8795
[13:45] <mborzecki> pedronis: zyga-x240: closed them now
[13:45] <ijohnson> pedronis: the only ones that are not strictly snap-bootstrap related are the _writable-defaults thing, and a cloud-init related thing that needs to land with the _writable_defaults, otherwise the _writable-defaults PR as-is will undo the cloud-init fix
[13:46] <ijohnson> pedronis: if you like I can prepare a backport PR with all of those after 9044 lands cleanly
[13:46] <mup> PR snapd#9045 closed: Disable part of the nfs-support test that checks udp proto on debian-… <Created by zyga> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/9045>
[13:46] <mup> PR snapd#9046 closed: tests: backport preseed test fixes to 2.45 <Created by zyga> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/9046>
[13:47] <mborzecki> pedronis: ijohnson: for preseeding we may want https://github.com/snapcore/snapd/pull/9015 and https://github.com/snapcore/snapd/pull/9018 in .45 right?
[13:47] <mup> PR #9015: cmd/snap-preseed: handle relative chroot path <Bug> <Preseeding 🍞> <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9015>
[13:47] <mup> PR #9018: cmd/snap-preseed: check that target path exists and is a directory on --reset <Preseeding 🍞> <Simple 😃> <Created by stolowski> <Merged by anonymouse64> <https://github.com/snapcore/snapd/pull/9018>
[13:48] <ijohnson> mborzecki: yes to 8015, 9018 is nice to have but not necessary, it is just better error handling
[13:48] <mborzecki> ack
[14:04] <zyga-x240> break
[14:12] <mborzecki> pedronis: zyga-x240: so 9044 is looking good, the failure on 19.10 is probably related to user session fixes in tests that are done in master, but were not cherry-picked
[14:16]  * pedronis in meeting
[14:19] <zyga-x240> mborzecki: looking
[14:20] <zyga-x240> hmm
[14:20] <zyga-x240> 2020-07-22T13:47:54.7315113Z Failed to connect to bus: Connection refused
[14:20] <zyga-x240> yeah I think that's ok to merge
[14:20] <zyga-x240> +1 and let's rebase the rest
[14:20] <mborzecki> yup, doing so now
[14:20] <zyga-x240> ok
[14:21] <mup> PR snapd#9044 closed: many: cherry-picks for 2.45, gh-action, test fixes <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/9044>
[14:24] <mborzecki> zyga-x240: rebased https://github.com/snapcore/snapd/pull/9042 please take a look
[14:24] <mup> PR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>
[14:36] <mup> PR snapd#9047 opened: cmd/snap-preseed: backport fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9047>
[14:37] <mborzecki> ijohnson: can you take a look ^^ ?
[14:38] <ijohnson> mborzecki: sure
[14:38] <mborzecki> ijohnson: thanks
[14:38] <ijohnson> I updated the getgrnam_r PR, but some of the code I changed has to do with sudo, so I would like some extra eyes on it
[14:51] <ijohnson> cachio: so regarding #9027, I think it is actually pretty unfortunate but I don't think we have another option right now, because there doesn't seem to be a way for us to identify the case where we have a real bug in snapd vs this bug in qemu where the system gets rebooted randomly in the middle of the test
[14:51] <mup> PR #9027: tests: refresh/revert snapd in uc20 <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9027>
[14:51] <ijohnson> cachio: I think we need to just merge it with the changes you have and expect that the test is very flaky / fail often due to this qemu bug
[15:01] <cachio> ijohnson,
[15:01] <cachio> ok
[15:01] <cachio> I'll try a new change with the gce platform to see if it improves
[15:01] <mborzecki> ok, the ci jobs are running, seems like the most problematic bits of 2.45.3 are done, need to run some errands now, but i'll check in on the PRs later
[15:02] <ijohnson> thanks mborzecki !
[15:40] <zyga-x240> ijohnson: https://github.com/snapcore/snapd/pull/9041#pullrequestreview-453438323
[15:40] <mup> PR #9041: osutil/group.go: treat all non-nil errs from user.Lookup{Group,} as Unknown* <Bug> <Needs security review> <Preseeding 🍞> <⚠ Critical> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9041>
[15:40] <ijohnson> thanks zyga-x240
[15:42]  * cachio lunch
[16:14] <pedronis> ijohnson: I need a break and then I'll try to go over that least of UC20 PRs
[16:14] <ijohnson> pedronis: k, sounds good
[16:17] <mup> PR snapd#8980 closed: tests: backport preseed test fixes to 2.45 <Test Robustness> <Created by stolowski> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/8980>
[16:21] <pedronis> mmh, I forgot about that one, that's bit the issue with long lived PRs
[16:22] <ijohnson> which one ?
[16:22] <pedronis> the backport pawel did
[16:22] <pedronis> already
[16:23] <pedronis> 8980
[16:23] <ijohnson> ah yes
[16:24] <ijohnson> well for that one I think pawel made changes there that weren't on master so it would have been a bit tricky to merge the release branch back to master when time came to actually finalize the release
[16:37] <mup> PR snapd#9048 opened: .github/workflows/snap-build.yaml: build the snapd snap via GH Actions too <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9048>
[16:38]  * ijohnson may have opened a new PR, but also closed an old one, so net PR count change is 0
[16:39]  * ijohnson goes back to actual productive things
[16:42] <mup> PR snapd#8143 closed: github: add github workflow <⛔ Blocked> <Created by sd-hd> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/8143>
[16:56] <pedronis> ijohnson: that list of UC20-related PRs seems fine, the questions I suppose is whether they backport cleanly?
[16:56] <ijohnson> pedronis: not sure, but I can check
[16:57] <ijohnson> pedronis: if they backport cleanly shall I open a PR with them included ?
[16:57]  * ijohnson is about to break for lunch
[16:57] <pedronis> ijohnson: yes, but needs to be on top of the two things we want to land
[16:57] <pedronis> ijohnson: so maybe wait a bit?
[16:57] <ijohnson> pedronis: which ones, mborzecki already landed one of them I think
[16:58] <pedronis> #9042 and #9047 ?
[16:58] <mup> PR #9042: interfaces: optimize rules of multiple connected iio/i2c/spi plugs (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9042>
[16:58] <mup> PR #9047: cmd/snap-preseed: backport fixes (2.45) <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9047>
[16:58] <ijohnson> ah ok
[16:58] <pedronis> unless I'm confused, which can be, I'm slightly exhausted atm
[16:59] <ijohnson> pedronis: it's okay I know what to do, I can land these PR's in my PM if they are green, I will do a double-check on 9042, but the other one is aleady approved
[17:02] <zyga> re
[17:02] <zyga> back after painkillers
[17:02] <zyga> sorry the overlap hours are not great
[17:06] <zyga> ijohnson|lunch: https://github.com/snapcore/snapd/pull/9048#pullrequestreview-453515399
[17:06] <mup> PR #9048: .github/workflows/snap-build.yaml: build the snapd snap via GH Actions too <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9048>
[17:16] <ijohnson|lunch> zyga, we may be able to leverage that in the builds themselves, I haven't looked into it too much I really just copied what joedborg did for the microk8s snap GitHub actions :-P
[17:16] <cmatsuoka> build queue blocked again?
[17:16] <zyga> look at the time 16 minutes!
[17:16] <zyga> that's 16 less in each of the re-execing systems
[17:17] <zyga> cmatsuoka: let me check
[17:18] <zyga> not stuck - processing loads of jobs
[17:18] <cmatsuoka> ah ok, thanks
[17:18] <zyga> many are close to 40 minute CPU time
[17:18] <zyga> this is usually when they end
[17:19] <zyga> btw, if anyone has decent home network
[17:19] <zyga> and a spare laptop
[17:19] <zyga> I we can grow the pool
[17:20] <zyga> anyway
[17:20] <cmatsuoka> what kind of access is needed? I have a machine here but it's only accessible via ipv6
[17:21] <zyga> only private IPv4 address
[17:21] <zyga> a machine behind lan is ok
[17:21] <zyga> it reaches out to github
[17:22] <zyga> I don't think ipv6 is supported in practice
[17:23] <cmatsuoka> I have ipv4 but it's behind a nat, if that's ok I can set up a couple of nodes here to see what happens
[17:23] <cmatsuoka> just send me the directions
[17:23] <zyga> sure
[17:24] <zyga> let me find the repo
[17:27] <zyga> hmmm, where is it?
[17:29] <zyga> actually
[17:30] <zyga> cmatsuoka: do you know things like ansible or other "magic" frameworks for deployment>
[17:30] <zyga> my instructions work but are really manual
[17:30] <cmatsuoka> zyga: I know that they exist, but never used them
[17:31] <cmatsuoka> manual is good, we learn a lot doing things by hand
[17:31] <cmatsuoka> as long as I don't have to do it multiple times
[17:35] <zyga> cmatsuoka: let's do this some other time - the real version that would allow snapd to benefit requires admin access to the repo
[17:35] <zyga> cmatsuoka: I can recommend two things
[17:35] <zyga> cmatsuoka: I'll share the doc I wrote
[17:35] <zyga> and the scripts
[17:36] <zyga> and I'd recommend deploying that for a personal repo
[17:36] <cmatsuoka> ok
[17:36] <zyga> you will learn the process
[17:36] <zyga> and improve it as well
[17:36] <cmatsuoka> sounds good
[17:40] <zyga> cmatsuoka: my recommendation is to do this on a focal system with focal containers
[17:40] <zyga> drat, I'm terrible at google docs
[17:40] <zyga> I know for a fact there's a gdoc
[17:40] <zyga> let me try on my phone
[17:41] <zyga> google is the worst UX company on this planet
[17:41] <zyga> borland docs would be better
[17:41] <cmatsuoka> finding stuff in gdocs is hard, these guys should learn something about searching
[17:41] <cmatsuoka> oh wait
[17:41] <zyga> haha
[17:41] <zyga> right?
[17:44] <zyga> installing the app
[17:50]  * zyga searches gmail
[17:51] <zyga> I'm lost
[17:51] <zyga> sorry, I wonder where that is
[17:52] <cmatsuoka> someday you'll find it, and then you tell me
[18:14]  * pedronis admits to have made a gdoc with links to other gdocs
[18:37] <mup> PR snapd#9024 closed: sysconfig/cloudinit: add RestrictCloudInit <Created by mvo5> <Merged by anonymouse64> <https://github.com/snapcore/snapd/pull/9024>
[18:46]  * cachio kinesiologist
[18:52] <ijohnson> zyga: https://github.com/snapcore/snapd/pull/9048#issuecomment-662625884
[18:52] <mup> PR #9048: .github/workflows/snap-build.yaml: build the snapd snap via GH Actions too <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9048>
[19:14] <zyga> jdstrand: I found one more bug in my implementation of the reproducer of the bug you found
[19:14] <zyga> jdstrand: testing it now, fingers crossed that it finally shows something
[19:34] <zyga> testing that now
[19:41] <ijohnson> uggh why do we have to have infinite amounts of conflicts in cmd_initramfs_mounts.go
[19:42]  * ijohnson cries a little a lot on the inside
[19:43]  * zyga hugs ijohnson virtually
[19:43] <ijohnson> haha
[19:43] <zyga> I had to deconflict some of those snapstate.go things
[19:44] <zyga> I learned how to tell my editor "yeah, you can use this much memory"
[19:44] <ijohnson> haha so true
[19:44] <ijohnson> before pstolowski split up that snapstate_test.go file, a conflict there was sure to crash my editor
[20:04] <zyga> jdstrand: no luck, I wrote a much more elaborate test that really mimics what you experienced except there's no failure yet :|
[20:04] <jdstrand> weird. I took my system out of it and did it in a vm in the bug...
[20:05] <zyga> I will try with your snap verbatim
[20:05] <zyga> I must have missed something
[20:06] <zyga> I pushed the updated (non failing) test to fix/lp-1888305
[20:07] <zyga> https://github.com/zyga/snapd/commit/db5c7c98b666ad3022d67a771706d11291f24da8
[20:07] <zyga> if you could eyeball that and spot any obviously wrong things I'd love to know
[20:08] <zyga> otherwise I will run with your snap in a VM tomorrow
[20:13] <mup> PR snapd#9049 opened: release/2.45: backport of uc20 PR's <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9049>
[20:13] <jdstrand> zyga: I think those experimental feature can be removed. I didn't carry those into the vm
[20:13] <zyga> OK
[20:13] <zyga> I will do one more round with a long running process
[20:15] <jdstrand> zyga: something that I don't see in this (maybe I missed it?) is that I have a long running process
[20:15] <zyga> right
[20:15] <zyga> I didn't do that because it should not be a factor
[20:15] <jdstrand> zyga: specifically, I have an app indicator that is long running
[20:16] <jdstrand> hmm
[20:16] <zyga> I though that it is caused by skew in snapd tools as snapd revisions change
[20:16] <jdstrand> zyga: are you sure? if there is a process running, isn't there different behavior for mount namespace updates?
[20:16] <zyga> no because snapd does not trigger mount namespace updates in our model
[20:17] <jdstrand> zyga: note that I could always resolve the issue by stopping and starting the indicator
[20:17] <zyga> that made me add the "observe" mode
[20:17] <zyga> as I realized that may matter
[20:18] <zyga> started one more round with the process running
[20:18] <zyga> that is interesting bit of information as well actually
[20:18] <zyga> it suggests that indeed the namespace "turns stale" somehow
[20:19] <zyga> and that starting a process is enough to fix it
[20:19] <zyga> but that's unusual as we must have done something to choose to update the namespace
[20:19] <zyga> and snapd, again, is not a factor
[20:19] <zyga> unless mount profiles changed somehow?
[20:40] <zyga> jdstrand: no change with running process
[20:43] <pedronis> ijohnson: I landed 9025, I suppose #9026 need a master merged now
[20:43] <mup> PR #9026: tests/nested/manual: add spread tests for cloud-init vuln <Run nested> <Created by mvo5> <https://github.com/snapcore/snapd/pull/9026>
[20:43] <mup> PR snapd#9025 closed: overlord,o/devicestate: restrict cloud-init on Ubuntu Core <Created by mvo5> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/9025>
[20:45] <ijohnson> pedronis thanks yes I think so
[20:52]  * zyga EODs
[20:52] <zyga> o/
[23:14] <mup> PR snapd#9040 closed: spread: add opensuse 15.2 and tumbleweed for qemu <Simple 😃> <Created by jdstrand> <Merged by cmatsuoka> <https://github.com/snapcore/snapd/pull/9040>


[07:41] <akoskm> hi! I'm trying to build my java packages in launchpad, the problem is that at compile time I have to get a jar file from downloads.sourceforge.net, at this point the build always fails with java.net.UnknownHostException. Any ideas to solve this? Here is the build log https://launchpadlibrarian.net/71131967/buildlog_ubuntu-natty-i386.libqtjambi_4.7.2-0ubuntu7_FAILEDTOBUILD.txt.gz
[07:43] <wgrant> akoskm: The builders do not have Internet access.
[07:45] <akoskm> wgrant: wow, but they had like 3 month ago, right?:d
[07:46] <akoskm> anyway, I'll just include that file with the sources, thank you for pointing out the problem!
[07:46] <wgrant> akoskm: No, they never have.
[07:46] <wgrant> Allowing arbitrary code execution with Internet access would be a very bad idea :)
[07:47] <akoskm> uh
[07:49] <spm> automated hack scan farm ftw!
[09:31] <ramana> hi
[09:31] <ramana> a query about bug watchers in Launchpad .
[09:32] <ramana> https://bugs.launchpad.net/binutils-linaro/+bug/772200 is a case where a bug watch was added in lp to an upstream binutils bugzilla. How is it that comments made in that bug don't seem to reflect in the lp bug report ? I've seen other bug watchers added to the GCC bugzilla where comments made on the bug entry make it back into lp
[09:43] <henninge> allenap: Hi! Can you help ramana regarding bug watches? ^^
[09:44] <allenap> henninge: I'll give it a go :)
[09:44] <henninge> Thanks!
[09:45] <jfi> Hello, is there a way to maintain the consistency between 2 http requests using 'next_collection_link'? Is it scoped by the http session?
[09:48] <henninge> jfi: I always thought statelessness was one of the defining qualities of a restful service.
[09:48] <henninge> jfi: Or what do you mean by "consistency"?
[09:49] <allenap> ramana: It seems to be because Launchpad can't detect an XML-RPC at http://sourceware.org/bugzilla/. I'm going to dig a bit further to see if there's something obvious I can do about it. It might be a bug on Launchpad, or it could be that the remote tracker needs a config change.
[09:49] <allenap> s/an XML-RPC/an XML-RPC endpoint/
[09:50] <ramana> allenap: ok cool :) thanks for looking at it . It just seemed to be something missing when I looked at it in LP .
[09:50] <jfi> henninge, first request get 0 to 74th first items, then something modify the result which shift the 74th item to 75th, so the second request will miss one item and get twice the 74/75th item
[09:50] <wgrant> jfi: There's no direct way to maintain consistency there at the moment.
[09:50] <wgrant> jfi: Most consumers cope OK.
[09:50] <wgrant> But once bug #752153 is fixed, it will be consistent.
[09:52] <jfi> wgrant, I guess there is no way to exceed the '300 limit'? no way to request an unlimited result?
[09:52] <wgrant> jfi: No, that would sort of nullify the purpose of having batches: to maintain reasonable request time limits.
[09:53] <jfi> wgrant, yes, I understand the reason
[09:55] <jfi> well, I will manage the consistence in my code, it may miss (in theory) some items but it is possible to avoid duplicated items
[09:55] <jfi> thanks for your response
[10:04] <allenap> ramana: The remote bug tracker is returning an internal error when Launchpad tries to probe for an XML-RPC endpoint. I'll email someone at sourceware.org to let them know.
[11:01] <ramana> allenap: Thanks for looking into this .
[11:03] <allenap> ramana: No worries.
[11:38] <sfunke> Hi, my name is Simon Funke and I am a developer for the fluidity code (https://code.launchpad.net/~fluidity-core). In order to do some tests, I created a experimental branch  (https://code.launchpad.net/~simon-funke/fluidity/automatic_differentiation) to which I would like to commit some changes now.  The exact error message is:
[11:38] <sfunke> sf1409@doodson:/data/sf1409/src/fluidity_adjoint/adjoint2$ bzr commit
[11:38] <sfunke> Unable to obtain lock  held by<EMAIL_ADDRESS>[11:38] <sfunke> at crowberry [process #17283], acquired 24 minutes, 50 seconds ago.
[11:38] <sfunke> See "bzr help break-lock" for more.
[11:38] <sfunke> bzr: ERROR: Could not acquire lock "(remote lock)": bzr+ssh://bazaar.launchpad.net/~simon-funke/fluidity/automatic_differentiation/
[11:39] <sfunke> Do you have an idea what is going wrong here?
[11:40] <henninge> sfunke: it looks like a previous run of bzr died
[11:40] <henninge> sfunke: or is still running
[11:40] <henninge> sfunke: did you look at "bzr help break-lock"?
[11:41] <sfunke> a previous bzr process on my machine or on launchpad?
[11:41] <henninge> sfunke: on your machine
[11:42] <henninge> sfunke: bzr locks the branch when it works on it. If it gets interrupted doing that, the lock will not be removed.
[11:43] <sfunke> henninge: I was not sure if bzr break-lock is safe safe to use.
[11:43] <sfunke> henninge: thanks, i will try it again then
[11:43] <spiv> sfunke: the lock is owned by your bzr client
[11:44] <spiv> sfunke: if your old bzr process isn't running, then it's safe to break its lock
[11:44] <henninge> sfunke: what spiv  said
[11:45] <sfunke> I checked that no bzr process is running and broke the lock. the commit worked fine now
[11:46] <sfunke> i thought launchpad is still doing background work and that is was causing the lock, but it was indeed my machine
[11:46] <sfunke> thanks
[11:46] <henninge> sfunke: np
[11:46] <wgrant> sfunke: It says "held by simon-funke", so it was a client authenticated as you.
[12:04] <henninge> adeuring: ready to take over?
[12:04] <adeuring> henninge: sure
[12:04] <henninge> adeuring: cool ;)
[12:04]  * henninge lunches
[14:19] <pfarrell> hi! I have a project on launchpad (libadjoint) which has two recipes building from the trunk. the two recipes are the same (I think), except they go to two different ppa's. However, one builds very successfully (https://code.launchpad.net/~libadjoint/+recipe/libadjoint-daily) and the other one failed to upload (https://code.launchpad.net/~pefarrell/+recipe/libadjoint-daily-fluidity).
[14:20] <pfarrell> I got an email saying "File libadjoint_0.1-0~207~maverick1.tar.gz already exists in Fluidity Supporting Software, but uploaded version has different contents."
[14:20] <pfarrell> but I don't really understand it
[14:22] <wgrant> pfarrell: It's trying to upload a package that has already been uploaded.
[14:22] <wgrant> In particular by an earlier build of that recipe, 21 hours ago.
[14:22] <wgrant> The version number has no changed, so it cannot be successfully built again.
[14:22] <pfarrell> ah, I see. so this is only caused because I requested a manual build first, and then when the daily build built it, it couldn't upload it?
[14:23] <pfarrell> so now, if I leave it alone, it won't happen again?
[14:24] <wgrant> That's correct, as long as your version template includes all relevant revision numbers, so a change to any branch will change the version.
[14:24] <wgrant> In this case it's fine.
[14:24] <pfarrell> yep
[14:24] <pfarrell> great, thanks for clearing that up
[14:28] <pfarrell> next question (sorry about this, still learning launchpad). Is there a way to formally associate a bug report with a branch that fixes it? In this case, I have a bug (https://bugs.launchpad.net/fluidity/+bug/783987) which I think is fixed in a branch (lp:~pefarrell/fluidity/spatialindex-mktemp), and I was wondering if there's a better way of associating them than just saying-so in a comment
[14:28] <spiv> pfarrell: click "link a related branch" on the bug's page
[14:29] <pfarrell> ahh
[14:29] <pfarrell> sorry
[14:29] <pfarrell> it's obvious when you say it
[14:29] <spiv> pfarrell: (or "Link a bug report" from the branch's page)
[14:30] <spiv> pfarrell: also, if you add "--fixes=lp:783987" to your "bzr commit" invocation that will happen automatically as soon as Launchpad sees that commit
[14:51] <pfarrell> spiv: good to know, thanks
[15:07] <deryck> adeuring, tag I'm it. :-)
[15:07] <adeuring> deryck: thanks!
[15:09] <pfarrell> what does being the "help contact" imply?
[15:10] <deryck> pfarrell, if you need help here, you can ping the help contact directly.
[15:10] <deryck> and we also watch IRC a bit more closely during our shift.
[15:11] <pfarrell> ah, fair enough, thanks
[15:11] <deryck> np
[15:14] <karni> Ahoy guys! We're writing the Android application for Ubuntu One Files and we're looking for a solution to annonymously collect bug reports (any crashes whatsoever). Would there be a possibility for an annonymous, not logged-in user to submit a bug report with an attachment via POST to launchpad?
[15:15] <karni> deryck: hey mate, I see you in the topic :) Do you happen to have an answer to my question ↑ ?
[15:16] <deryck> hi karni.  reading it now....
[15:16] <karni> deryck: Thanks!
[15:16] <karni> deryck: We might use the Oops thingy, just exploring possibilities here :)
[15:17] <deryck> karni, is this question "do we (or would we) allow anonymous users to post bugs" ?
[15:18] <karni> deryck: heheh. I know we currently don't allow that. I'm asking if there a possibility if we could :)
[15:18] <deryck> karni, yeah, we don't support it now.  I'm not sure if we would.  it would require some work on our end....
[15:19] <deryck> karni, you probably want to chat with jml about this if you need it.  but this will slow you down obviously.
[15:19] <karni> deryck: I believe so. I see. All right then, we'll look into the Oops'es thingy then first :) Thanks deryck !
[15:19] <ScottK> karni: Set up a role account to accept the bug reports and preauthorize the app to use LP for that account.  Then they aren't "anonymous".
[15:20] <karni> ScottK: interesting :)
[15:21] <deryck> karni, np.  and yeah, as ScottK notes, you just need *an* account to submit bugs.
[15:21] <karni> deryck: okey :)! /me looks into lp help
[15:40] <ogra_> so i have this open team on LP ... and just thought it would be nice to have a PPA for it ....
[15:41] <wgrant> ogra_: That doesn't make sense.
[15:41] <ogra_> .... i clicked on "Create PPA" and added the details
[15:41] <wgrant> Open team with PPA == free root for everyone.
[15:41] <ogra_> to then get told that open teams cant have ppas
[15:41] <ogra_> why is the UI offering me to create a PPA if that kind of team cant use it ?
[15:42] <ogra_> (i wasnt actually aware its an open team)
[15:42] <wgrant> Probably because the restriction was only added a few months ago, and nobody has pointed out that the link should be hidden :(
[15:42] <wgrant> Could you file a bug?
[15:42] <ogra_> will do
[16:28] <awolfson> deryck, Hi. I can not run my scripts using "-s staging" - getting error 401 unauthorized. They work on production and qastaging. Is there any way to reset my credentials? I tried to remove all authorized apps from https://staging.launchpad.net/~awolfson/+oauth-tokens but it did not help
[16:29] <deryck> awolfson, you can also try removing the credentials from $HOME/.launchpadlib
[16:29] <awolfson> deryck, I did that as well
[16:30] <deryck> awolfson, ok, that seems weird.  when you run the script you don't get prompted to re-auth?
[16:30] <awolfson> deryck, no I don't
[16:30] <awolfson> deryck, that is what I hoped for to reauthorize, but it did not happened
[16:32] <deryck> awolfson, do you have anything stored in the gnome password manager, or whatever it's called?
[16:32] <awolfson> deryck, good question - let me check
[16:34] <awolfson> deryck, at least in passwords and encription keys there is nothing with launchpad
[16:34] <deryck> awolfson, and you're running these scripts via terminal?
[16:34] <awolfson> deryck, yes
[16:35] <deryck> awolfson, you try logging out on staging?
[16:35] <awolfson> deryck, you mean from the web browser?
[16:36] <deryck> awolfson, yes, just log out via web browser at staging, and try again.
[16:36] <deryck> well, that doesn't make sense, sorry :-)
[16:36] <deryck> the credentials have to be cached somewhere
[16:36] <deryck> awolfson, can you pastebin me the output from terminal when you run it?
[16:37] <awolfson> deryck, sure one sec
[16:38] <awolfson> deryck, https://pastebin.canonical.com/47541/
[16:40] <deryck> awolfson, can you debug the script and figure out what it's using for cachedir?  that "unknown access token" implies cached credentials somewhere on your system.
[16:40] <awolfson> deryck, OK let me do it.
[16:41] <deryck> benji, can you look at the pastebin above ^^ and see if my advice to awolfson is sound?
[16:41] <deryck> benji, I'm guess cached credentials somewhere, but he's blow away .launchpadlib and revoked oauth tokens.
[16:42] <deryck> maybe there's some other obvious thing I don't know?
[16:42] <benji> lastlog awolfson
[16:42] <benji> heh, that needs a slash to be a command
[16:43] <deryck> heh
[16:43] <awolfson> benji, what do you mean by lastlog?
[16:44] <benji> I was trying to run the command "/lastlog awolfson" to see what you had said earlier (it had scrolled off my screen) but I left off the leading slash so I said it instead
[16:45] <benji> that's the IRC equivalent of "did I just say that out loud?!" :)
[16:46] <awolfson> benji, thanks, I did not know that command - good to know
[16:48] <benji> awolfson: what version of launchpadlib are you using?
[16:48] <awolfson> benji, how to find that out?
[16:49] <awolfson> benji, deryck For cache i have: cachedir = os.path.join(os.environ["HOME"], ".launchpadlib/cache")
[16:49] <awolfson>     lp = Launchpad.login_with("lp-fish-tools", options.lpsystem, cachedir)
[16:49] <benji> awolfson: dpkg -s python-launchpadlib | grep Version
[16:50] <deryck> awolfson, and if you ls that dir you don't show any credentials?
[16:50] <deryck> benji and I are doubling up on awolfson :-)
[16:51] <awolfson> deryck, benji 1.9.7-0ubuntu2
[16:51] <awolfson> and I cleaned that dir
[16:51] <benji> awolfson: in that case the credentials are stored in the gnome keyring, let me see how you clear those
[16:53] <awolfson> benji,looks like I found it under network password
[16:53] <awolfson> let's see if I can clean it
[16:57] <awolfson> benji, deryck It solved the problem. Thank you for help! Details: in system settings->Passwords and Encription Keys there are 3 entries named "network password" in details you can see which one was for staging and delete it
[16:57] <benji> awolfson: great!
[16:57] <deryck> awolfson, awesome!
[16:57] <awolfson> benji, deryck thanks again
[17:48] <poolie> that's a known bug i think
[17:48] <poolie> it can get corrupted
[17:48] <poolie> https://bugs.launchpad.net/launchpadlib/+bug/745801
[17:49] <primes2h> Hello kiko. I had a look at this bug #176558 and I wonder if it's possible to have (if any) a svg or whatever of those icons.
[17:50] <kiko> primes2h, I think we do have SVGs for them, but they have a special license -- joey, flacoste?
[17:51] <joey> kiko: the only ones I'm aware of the LP Icons that we had created. Canonical owns the copyright for them.
[17:52] <primes2h> kiko: in the bug you mention they have (c) Canonical
[17:52] <joey> and flacoste would be the Canonical rep for them at this point... or mrevell
[17:52] <joey> they are not specifically addressed under https://help.launchpad.net/Legal
[17:54] <primes2h> kiko: I would like to start working at that bug, so it would be nice to have SVGs.
[18:01] <deryck> abentley, handing over to you now.
[18:20] <primes2h> joey: so should I ask flacoste or mrevell about this?
[18:27] <joey> primes2h: either.  Matt R is probably a good person to email
[18:28] <primes2h> joey: kiko: ok, thank you very much. :-)
[18:35] <flacoste> primes2h: you can find the SVG in lib/canonical/launchpad/images/src/ in LP source tree
[18:37] <primes2h> flacoste: do I have permission to use them in the tracker?
[18:38] <flacoste> primes2h: as long as you are fine that they are not redistributable
[18:39] <flacoste> primes2h: i can grant the right to use it on the qatracker site, but if that site is free-software users of it wouldn't have that right
[18:39] <flacoste> primes2h: if you want more, i'll have to escalate the request
[18:42] <primes2h> flacoste: sure.But how can I handle this for use them in the tracker? Do I have to put the license in the qatracker-website source?
[18:42] <primes2h> flacoste: about more, you mean for use them on other projects?
[18:43] <flacoste> primes2h: yes, or making them open source
[18:44] <flacoste> primes2h: see the LP license
[18:45] <primes2h> flacoste: I'll have a look at it later. I must go now. Thanks for now. If I need more help I'll ping you here ;-)
[18:46] <flacoste> primes2h: no problem
[18:51] <rye> hi, as I see lp has started using support U1 RT, but there appear to be tons of incoming messages to launchpad feedback that do not pass any spam filtering and just end up creating more and more tickets in the queue
[19:55] <flacoste> rye: yep, that's a known problem, we notified IS of this
[19:55] <rye> flacoste, thanks
[20:05] <abentley> lifeless: bug 704698 seems to be fixed.  I recently had to deal with fallout of transaction killing in BranchUpgradeJob.  Do you agree?
[20:07] <abentley> lifeless: bug 777958 is the one where killing transactions caused oopses.
[20:42] <keks-n> sup
[20:42] <keks-n> Guys, I have some problems with uploading to ppa
[20:43] <keks-n> dput says "dput says "Successfully uploaded packages.", but I cann't find my package in the build queue
[20:45] <jdobrien> beuno, do you have anyone sharing a folder with you?
[20:45] <jdobrien> oops
[20:54] <fta> spam in bug 296463
[20:56] <abentley> keks-n: I don't know, I'll find someone who does.
[20:56] <keks-n> tnx
[20:59] <abentley> keks-n: it looks like the right people aren't available right now.  Could you file a Question, and I'll assign it to the appropriate people?
[21:02] <keks-n> Where can I do it? I cann't find the form at answers.launchpad.net
[21:05] <keks-n> found it
[21:09] <keks-n> https://answers.launchpad.net/ubuntu/+question/157948
[21:20] <lifeless> abentley: looking
[21:25] <lifeless> abentley: for bug 704698 I'm thinking larger scale - we have many different scripts (the email ones, rosetta translations, garbo etc
[21:25] <lifeless> abentley: all of them need to have some insurance against long transaction
[21:26] <abentley> lifeless: are you saying we kill some transactions but not others?
[21:27] <lifeless> ah, I'm talking about two different mechanism
[21:27] <lifeless> the transaction killer is a global backstop
[21:27] <lifeless> I'm talking about a timeout mechanism like the appservers have
[21:28] <lifeless> we might be able to use the transaction killer to implement that, I hadn't thought about that; I'm not sure if its fine grained enough to have different policies for different users
[21:28] <lifeless> which I imagine we'll need as many scripts would fail today.
[21:33] <abentley> lifeless: so far, it seems we want to restrict scripts'/jobs 1. memory use 2. duration 3. transaction duration.
[21:34] <lifeless> yes, though with 2 that limit might be several days
[21:34] <lifeless> (for the specific case of upgrade jobs)
[21:34] <abentley> lifeless: I don't have any examples of upgrade jobs taking longer than two hours, but yeah.
[21:35] <lifeless> thats cool
[21:35] <abentley> lifeless: for merge proposal diff generation, we limit it to 10 minutes.
[21:35] <lifeless> I thought hairy things like mysql5 still took many hours
[21:35] <abentley> lifeless: We may be past all those.  The logs don't go back terribly far.
[21:36] <lifeless> abentley: I don't know if they have migrated yet; they have some inertia to overcome aiui
[21:36] <lifeless> anyhow, most things don't need such high constraints
[21:36] <lifeless> we have a couple of 12ish hour scripts that run nightly
[21:36] <lifeless> but they do lots of little xactions
[21:37] <abentley> lifeless: anyhow, perhaps we should be looking at generalizing those things.
[21:38] <lifeless> I think we can do 1 and 3 easily because we have appropriate places to hook in already
[21:38] <lifeless> 2 might be harder for /some/ of our backend things that aren't in the jobs framework, for instance
[21:39] <lifeless> I think 1 and 3 matter the most - if they are in place its hard to take out the rest of the system
[21:39] <lifeless> I've no objection to enforcing all three
[21:39] <lifeless> just doing a little analysis about it
[21:57] <abentley> lifeless: I agree it would be harder.  I suppose we could rig up something to run scripts under ampoule.  But it seems like we want to prevent runaway scripts as much as runaway jobs.
[22:26] <broder> hmm...is there any way to suppress e-mails about successful daily recipe builds? they're kind of spammy
[22:45] <lifeless> broder: there is a bug open
[22:46] <lifeless> I think poolie has a patch even
[22:47] <broder> lifeless: indeed - i see that now, thanks


[19:10] <OvenWerks> No meeting this week... no real new stuff with controls. But the end is near because jackdbus is less stable than it has been in the past so a restart is required for any change... easy to do.


[00:10] <GrueMaster> ogra_: Nevermind.  I swiped NCommander's AC100 and am nuking it now.
[07:17] <R_Nev> the red color output is at max on my beagleboard xm when running ubuntu; does anyone else have this issue?
[07:41] <MrCurious_> must say ubuntu keeps looking better and better
[17:24] <brandini> dudes
[18:56] <stephen_> hi all, whats the best media player for getting a good framerate (running pandaboard with ti 1080p addon_)


[00:24] <jpmh> when I perform the arp command it lists a load of devices that I have indeed connected to .  But many of them it was a long time ago.  How long is this cache maintained?
[00:31] <jamcinnaminusr> I'm on Ubuntu 22.04 with Cinnamon desktop
[01:45] <tomreyn> jpmh: https://manpages.ubuntu.com/manpages/kinetic/en/man7/arp.7.html see gc_thresh1 + gc_stale_time
[03:10] <DoRoad> Hello everyone
[03:10] <DoRoad> Is anyone here?
[03:11] <ravage> hello DoRoad
[03:11] <DoRoad> ravage: How can I save my public IP every time I connect to?
[03:12] <DoRoad> I could write a script but I think there are some automatic tools
[03:12] <rollappuser> wat
[03:12] <DoRoad> What?
[03:13] <ravage> DoRoad, connect to what?
[03:13] <DoRoad> ravage: to the net of course
[03:14] <ravage> and how do you connect to "the net" ?
[03:15] <DoRoad> Jesus man
[03:15] <octav1a> ♫ goin surfin' on the inter'net ♫
[03:15] <ravage> never heard of that connection method
[03:15] <DoRoad> I could write a script that saves to the log my public IP
[03:15] <DoRoad> But I forgot bash
[03:17] <ravage> time to restore a brain backup then i guess
[03:17] <DoRoad> Or use stack exchange
[03:20] <DoRoad> ravage: to be honest in my situation the best I can do is getting lorry licence
[03:21] <DoRoad> I'm from a poor family I had to learn linux/unix myself and it sucks
[03:21] <ravage> !ot | DoRoad
[03:22] <ravage> there is also #bash
[03:23] <DoRoad> So, talking on the topic... Ubuntu is not an alternative for non-tech users. I mean not even a computer technicians
[03:23] <ravage> that is not a support topic. feel free to discuss in #ubuntu-discuss
[04:24] <hiya> I have a question about firmware updates, my thinkpad T16 has a pending update for bios
[04:24] <hiya> and yet it won't show in Gnome Software or anything in ubuntu
[04:24] <hiya> do I need to add it or do it manually only?
[04:25] <hiya> Also they allow it using fwupdate and fwupdmgr which tool is better?
[04:25] <ravage> bios updates nevers showed up in fwupd for me
[04:25] <hiya> ok
[04:25] <hiya> So which tool is better? fwupdate of fwupdmgr?
[04:25] <hiya> I have secureboot with password on
[04:35] <Bashing-om> hiya: Please see in  terminal ' man fwupdate ' where the debugging utility is depreciated.
[04:48] <mister_mm> hello; does anyone know how I can create a "toggle" for the shift key? To type a ``*'' for instance, I'd like to hit [shift] 8 [shift]. The first tap of [shift] would toggle shift to be "held" and the second would turn it off.
[04:49] <mister_mm> I'd like to do this for accessibility reasons
[04:50] <rbox> https://unix.stackexchange.com/questions/224827/how-do-i-enable-shift-lock-sticky-shift-key
[04:51] <ravage> mister_mm: maybe one of the tweaks here can be useful to you: https://i.imgur.com/S3ega5N.png  ( sudo apt install gnome-tweaks )
[04:55] <mister_mm> I have caps lock bound as control already
[04:55] <mister_mm> I don't know that I can overload it
[04:55] <mister_mm> seems like maybe doing something with xmodmap whatever that is probably is the answer
[05:03] <mister_mm> I think that I can get the desired behavior through enabling "sticky keys" in the accessibility settings under ``Typing Assist (AccessX)'' under the typing section
[05:13] <lotuspsychje> !info input-remapper | mister_mm maybe?
[05:13] <lotuspsychje> i recently mapped my tab to right ctrl with it
[05:45] <Umeaboy> What's the channel for questions related to Launchpad and the way it's working?
[05:46] <Umeaboy> Found it....
[08:11] <silv3r_m00n> hi there, i am using chromium , with about 150 tabs ... the browser gets stuck for 2 seconds when i switch from one tab to another... i have 32gb ram no issues there, ssd (so fast disk), cpu is i5 7400 with decent igpu that is not bottlenecking .... google chrome works fine ... how to diagnose whats causing chromium to freeze every few seconds ?
[10:51] <Schnoerbel> look for Help
[10:52] <EriC^^> Schnoerbel: ask the question or explain the problem
[11:28] <Guest6882> hi
[11:31] <Guest6882> why i get no installation candidate on my ubuntu xfce
[12:37] <nedbat> I'm running a pile of code (a bug reproducer) and it eventually fails in Python with `Could not run curl-config: [Errno 2] No such file or directory: 'curl-config'`.  I can't seem to find how to install this command.  What am I missing?
[12:39] <tomreyn> an installation of apt-file, so that you cuold search for this command, to learn which package provides it
[12:39] <tomreyn> or a search on https://packages.ubuntu.com where you can learn the same
[12:39] <lsd|2> https://www.cyberciti.biz/faq/how-to-install-curl-command-on-a-ubuntu-linux/?
[12:39] <tomreyn> or someone here telling you that you need libcurl4-gnutls-dev
[12:41] <tomreyn> or libcurl4-nss-dev, or libcurl4-openssl-dev
[12:41] <nedbat> tomreyn: thanks, I found that package from the search, but my docker container is unable to install it.
[12:41] <nedbat> tomreyn: do I need to add other sources for packages?
[12:42] <nedbat> tomreyn: does this page https://packages.ubuntu.com/jammy/libcurl4-gnutls-dev tell me something I need to do? Sorry, this is new to me.
[12:42] <tomreyn> depends on which apt sources you have now, i guess
[12:42] <tomreyn> but it's in main, so, probably not
[12:43] <tomreyn> nedbat: this page tells you about the libcurl4-gnutls-dev package in Ubuntu "jammy", so 22.04
[12:44] <nedbat> tomreyn: right, i'm using jammy
[12:44] <tomreyn> i might be able to provide more help if you would be more verbose about "my docker container is unable to install it"
[12:44] <tomreyn> !paste
[12:44] <tomreyn> you're basically saying "it does not work"
[12:45] <nedbat> tomreyn: https://gist.github.com/nedbat/e78962e4e3768e156e494100ea2cff7b (btw, dpaste.com said i was rate-limited the first time I tried to make a paste)
[12:45] <nedbat> tomreyn: i'm not sure what other information would be helpful
[12:48] <tomreyn> apt policy libcurl4-gnutls-dev
[12:48] <tomreyn> and  apt-policy
[12:48] <tomreyn> and make sure you run  sudo apt update    first of all
[12:49] <tomreyn> nedbat: ^
[12:49] <tomreyn> you can use another pastebin-like service (i like termbin.com) if it helps.
[12:50] <nedbat> tomreyn: i guess `sudo apt update` was what I needed.  My dockerfile has `apt-get update`, I'm not sure how that is different.
[12:51] <tomreyn> both would update the apt cache (or fail to do so)
[12:53] <nedbat> tomreyn: are those caches in /var/lib/apt/lists/* ?
[12:53] <tomreyn> i think the only differece is in the tools' output formatting
[12:53] <tomreyn> yes
[12:53] <nedbat> tomreyn: ok, that was bad advice in the dockerfile then, to remove those.
[12:54] <tomreyn> as far as i know part of the concept of docker is that you don't install software after the image was created
[12:55] <nedbat> tomreyn: yes, usually. but i'm trying to create a sandbox in which to run untrusted code, so I will need to install more things sometimes.
[12:57] <tomreyn> makes sense, if you consider docker to provide sufficient isolation to run untrusted code
[12:58] <BluesKaj> Hi all
[12:58] <nedbat> tomreyn: it's defintely more isolation than not using docker, but i hear you
[13:00] <Dumbo> whats new in russia?
[13:00] <tomreyn> !ot | Dumbo
[13:20] <xatrix> Hi, can you advice. I'm trying to remove deprecated
[13:21] <xatrix> 'apt-key' gpg key. But it doesn't want to. If i list keys again. 'apt-key list' it seems like appear again in the list
[13:21] <xatrix> please, take a look at the screenshot https://imgur.com/jvZZ8If.png
[13:21] <xatrix> Is there any way to remove it ?
[13:23] <tomreyn> xatrix: which key are you trying to remove?
[13:23] <xatrix> tomreyn: GitLab B.V. (package repository signing key<EMAIL_ADDRESS>[13:24] <tomreyn> xatrix: just delete the file then - its location is printed on your screen
[13:24] <tomreyn> please try to use a pastebin-like tool when sharing text in the future.
[13:25] <tomreyn> !paste
[13:25] <xatrix> tomreyn: ok. got it
[13:27] <xatrix> Any idea ?
[13:28] <tomreyn> any idea on what?
[13:28] <oerheks> just remove the .../gitlab_key.gpg ?
[13:28] <oerheks> as tom said
[13:29] <xatrix> Ah... got it. Didn't see the message you posted me before. Yea, i deleted the key. And now, it's not on the list. Thanks!
[14:05] <ylwghst> Hey, I have weird issue. Everything works fine on livecd boot. On my real system my wlan device rtl8821ae is always unavailable, can not scan network or use it in any way.
[14:06] <nedbat> what is it that changes my terminal title when logging in to ubuntu, and is there a way to make it stop?
[14:06] <tomreyn> ylwghst: which ubuntu versions and kernel versions are you comparing there?
[14:06] <ravage> ylwghst: "sudo rfkill unblock all"
[14:07] <ylwghst> rfkill is not issue it's always unblocked everything seems just fine i have tried all basic things and i have tried several different kernels and it's pretty much same with any kernel
[14:07] <ylwghst> i suspect only thing might be wrong is wpa_supplicant?
[14:07] <ylwghst> $ iw dev wlp4s0 scan -> command failed: Network is down (-100)
[14:08] <ylwghst> @tomreyn 22.10 but it happens with any kernel at the moment
[14:09] <ravage> ylwghst: did you try "ip link set wlp4s0 up"
[14:10] <ylwghst> yep has no effect
[14:10] <ylwghst> $ nmcli d => wlp4s0  wifi      unavailable  --
[14:11] <ylwghst> whatever i do this state never changes
[14:11] <tomreyn> what do your system logs say about when the device is initialized during boot?
[14:12] <leftyfb> ylwghst: just qant to add in here, wpa_supplicant has nothing to do with any of this. It is not required to load drivers or bring up an interface.
[14:12] <leftyfb> qant/want
[14:12] <ylwghst> drivers are loaded
[14:14] <ylwghst> do you want full dmesg or grep rtl8821ae is sufficient
[14:15] <tomreyn> the second is probably not enough, but even that would be a good start
[14:15] <ylwghst> it enables device 000 -> 0003, loads firmware and then 0000:04:00.0 wlp4s0: renamed from wlan0
[14:15] <ylwghst> ok
[14:15] <ylwghst> nothing strange at all
[14:16] <leftyfb> ylwghst: ls -l /sys/class/net/wl*
[14:17] <ylwghst> https://pastebin.com/Cm69ZWhV
[14:18] <xatrix> One more question. I have 22.04 LTS, and i have Lenovo G50 laptop. It has hybrid graphics Intel/[AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230]. And i can't make it work as it should. I tried to load my X.org with 'radeon' driver in xorg.conf, and 'amdgpu' but it doesn't see my screen output. https://pastebin.com/m9YHdZZw
[14:18] <tomreyn> ylwghst: please use ubuntu kernels.
[14:18] <ylwghst> here is ls -l https://pastebin.com/7kiiMSm1
[14:19] <ylwghst> i can use ubuntu kernel it's behaves same on any kernel
[14:19] <ylwghst> it's something weird
[14:21] <ylwghst> at this point i'm just really what is it
[14:21] <ylwghst> really curious*
[14:21] <Jeremy31> sudo cat /var/lib/NetworkManager/NetworkManager.state
[14:24] <ylwghst> https://pastebin.com/bDFmbx2U
[14:26] <tomreyn> xatrix: first of all, update your bios, if you haven't done that, yet
[14:26] <nedbat> does everyone just live with their terminal window title changing when they log in to an ubuntu box?
[14:28] <oerheks> nedbat, why does that bother you?
[14:29] <ravage> i dont even understad the problem
[14:29] <lotuspsychj3> maybe nedbat needs a dropdown terminal?
[14:29] <nedbat> oerheks: because I like to set the window title to the task I am working on, and if I start a docker container as part of that, it changes away from the title I chose.
[14:35] <tomreyn> ylwghst: while i haven't seen a dmesg with ubuntu kernel and default kernel options, i bet this issue would not occur on an unmodified, fully updated ubuntu installation
[14:55] <Square> Not that its a problem for me, but resuming a suspended ubuntu 22.04 install will show whatever is on screen before actually showing the unlock prompt.
[15:04] <xatrix> tomreyn: yea, i have most recent. But it's a dated laptop a bit
[15:06] <tomreyn> xatrix: those old AMD integrated graphics chipsets from the SI/CI generation are not fun to deal with, sadly.
[15:07] <tomreyn> your kernel cmdline suggests you already noticed this. ;)
[15:08] <oerheks> SiS does only Vesa mode?
[15:08] <xatrix> yea, i'm trying too much time to solve it. but, you think, there's no way to fix it ? is it ?
[15:09] <lotuspsychj3> maybe a lubuntu likes it more?
[15:09] <lotuspsychj3> !amd | xatrix see also
[15:10] <tomreyn> xatrix: i'm not sure what exactly isn't working, did you discuss this, yet?
[15:11] <xatrix> yea, i'm talking about radeon driver. it sounds as it detects my card. but it doesn't make it run
[15:11] <xatrix> also, i have it PWRDyn down in vgaswitcheroo
[15:11] <xatrix> tomreyn: yea, maybe a half a year ago
[15:11] <tomreyn> your kernel command line would prevent radeon from using your hardware
[15:12] <tomreyn> radeon.si_support=0
[15:12] <xatrix> When i enable my AMD card in bios, i can't load my Xserver, because of AMD/Radeon driver says:
[15:13] <xatrix> (WW) AMDGPU(1): No outputs definitely connected, trying again...
[15:13] <xatrix>  AMDGPU(1): Unable to find connected outputs - setting 1024x768 initial framebuffer
[15:13] <xatrix> Radeon drivers does the same
[15:13] <xatrix> i tried various combination of radeon.si_support=0 amdgpu.si_support=1, and vice versa
[15:14] <xatrix> by the way, intel driver can detect the outputs
[15:23] <tomreyn> xatrix: sorry, i wouldn't know, never had this hardware, so all i have seen are others reports online, which seem to be mixed.
[15:23] <xatrix> Yea
[15:25] <lotuspsychj3> xatrix: maybe share your dmesg and the output of lshw -C video volunteers might be able to see more of whats happening
[15:25] <xatrix> sure, it's all inside the https://pastebin.com/m9YHdZZw post, i sent here before
[15:26] <lotuspsychj3> that was not the full dmesg xatrix
[15:26] <xatrix> nothing changes if i switch to radeon driver. it will be the same picture
[15:26] <xatrix> lotuspsychj3: ok.. i'll do the full dmesg. give me some time to pls
[15:26] <lotuspsychj3> we also cant see the driver= part of lshw
[15:27] <xatrix> ah. ok
[15:27] <xatrix> give me a second, i'll switch back to my discreet graphics
[15:32] <xatrix> This is my dmesg: https://paste.debian.net/1260456/ This is Xorg.0.log: https://paste.debian.net/1260457/ And this is the lshw: https://paste.debian.net/1260458/
[15:34] <xatrix> lotuspsychj3: maybe you can advice something ?
[15:34] <lotuspsychj3> reading
[15:34] <xatrix> i'm sorry
[15:37] <lotuspsychj3> xatrix: lshw shows both driver modules are loaded so that would be a good thing, but in dmesg you get some; kernel: radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 wich would be not too good
[15:38] <lotuspsychj3> radeon: unknown parameter 'drm' ignored
[15:39] <lotuspsychj3> xatrix: a few ideas rising my mind would be, checking for bios/firmware updates, trying other ubuntu releases/kernels/flavours to compare
[15:40] <lotuspsychj3> xatrix: did you have earlier ubuntu releases working on this same box?
[15:41] <lotuspsychj3> Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic biosdevname=0", will be passed to user space.
[15:41] <xatrix> Ubuntu 18. was running good. but i can't stay forever on 18 :)
[15:42] <lotuspsychj3> yeah i ran radeon card for years till 18.04 myself properly
[15:42] <xatrix> biosdevname it's for my network interfaces to be called as eth0... intead of enp0s1...
[15:42] <bparker> tryimg to boot the 22.04 server ISO gets stuck for me at "waiting for cloud-init..." forever
[15:42] <bparker> I am not using any cloud
[15:43] <bparker> any ideas?
[15:44] <lotuspsychj3> xatrix: i had great luck with lubuntu 20.04 on ancient boxes/hardware
[15:44] <tomreyn> bparker: does it happen with 22.04.1? was the iso written properly to the installation media?
[15:44] <xatrix> yes, but i dont want to gowngrade to :)
[15:44] <xatrix> maybe there's some forums or github isses, where i can post the debug info ?
[15:45] <lotuspsychj3> first play the compare game xatrix
[15:45] <xatrix> such as radeon driver or ubuntu stuff?
[15:45] <xatrix> compare game ? sorry ?
[15:45] <bparker> no idea about .1 but I'm booting the iso from grub from the internal storage (with "toram" option)
[15:45] <bparker> because this thing currently runs 18.04 but I want to upgrade with a clean install and I have no external storage here
[15:46] <tomreyn> bparker: hmm i'm guessing that's related to the problem you're experiencing.
[15:46] <tomreyn> can't boot it from nfs or a virtual cdrom?
[15:46] <bparker> nope
[15:47] <bparker> unless there is a way to do it over wifi
[15:48] <lotuspsychj3> xatrix: downgrading ubuntu isnt possible, so comparing with other ubuntu releases/kernels/flavours as suggested above
[15:48] <xatrix> yea, i know, that 18.04 will be running good. but i'd like to stay at recent verison
[15:53] <tomreyn> xatrix: https://pcsupport.lenovo.com/gb/en/products/laptops-and-netbooks/lenovo-g-series-laptops/g50-70-notebook-lenovo/20351/downloads/ds100522-bios-update-for-windows-7-32-bit-64-bit-windows-81-32-bit-64-bit-lenovo-g40-70-g50-70?category=BIOS%2FUEFI is the latest bios for this computer, which is a slightly higher versionthan what you have. but at least this latest versions's changelog doesn't discuss anything related. there's no changelog for
[15:53] <tomreyn> earlier versions, though.
[15:53] <tomreyn> 9ACN32WW is the latest, 9ACN30WW is yours
[15:54] <xatrix> tomreyn: ok. i'll update it. but where did you find a bios version in my logs ?
[15:55] <tomreyn> [    0.000000] kernel: DMI: LENOVO 20351/Lancer 5A2, BIOS 9ACN30WW 01/27/2015
[15:57] <xatrix> ok, i'll update
[16:16] <Telanor> hello, I'm using a ubuntu liveusb and the screen res is super low.  I have an nvidia card.  Is there a way to update the drivers for a liveusb?
[16:21] <strive> Telanor: Can't you just go into display settings and adjust it there?
[16:21] <Telanor> There are no options in the dropdown
[16:24] <jhutchins> Telanor: You could build your own live image that included the drivers.
[16:24] <jhutchins> !live
[16:24] <jhutchins> Hrmph.
[16:25] <Telanor> That sounds useful, how would I do that?
[16:26] <tomreyn> jhutchins: i think current live / installer images do include nvidia drivers
[16:26] <Telanor> maybe mine's too old, I'm using ubuntu 18
[16:27] <tomreyn> Ubuntu 18.04 LTS iso's probably don't
[16:27] <tomreyn> i think nvidia drivers were added since around 20.04 LTS
[16:28] <Telanor> Maybe I can try that then, hopefully it fits on my USB, I tried kubuntu earlier and it was too big for my 4gb usb
[16:29] <Telanor> There's no way to increase the resolution a bit without drivers?
[16:29] <Telanor> looks like its 640x480 right now
[16:30] <jhutchins> Telanor: You're probably running on the fall-back VESA drivers, and that's as high as they go.
[16:31] <Telanor> (y)
[16:31] <Telanor> Im actually just trying to get into the network settings but the screen res is so low the window goes off screen and I can't hit the apply button...
[16:32] <ogra> all iso include the nvidia drivers of their time ... 18.04 might be a bt old for your card
[16:32] <ogra> *bit
[16:32] <ogra> try a newer iso ... i.e. 22.04
[16:34] <tomreyn> the 22.04 LTS desktop ISO is 3.6G
[16:34] <tomreyn> so this should work with your $G stick
[16:34] <tomreyn> * 4G
[16:38] <alkisg> Telanor: hold down Alt, then mouse-click at the inside of a window and move it around
[16:40] <Telanor> It doesn't seem to be doing anything
[16:41] <Telanor> oooh, it worked with the windows key!
[16:41] <Telanor> finally I can hit the save button! :)
[16:42] <Telanor> thank you!
[18:01] <alkisg> Hmm, maybe gnome or wayland are different, the good old xorg way was with alt
[18:32] <EagleOwl> I'm getting "AH00094: Command line: '/usr/sbin/apache2'". The notice is right: The folder/file is absent. Is there an obvious reason for that? Ubuntu in VMware on Windows, all current.
[18:34] <EagleOwl> Maybe that belongs in #httpd?
[18:34] <murmel> no you are in the right channel, we just need more info
[18:36] <EagleOwl> Glad to provide it.
[18:39] <MockingMoniker> How do I install from a certain repo when it's installed? It has packages that would be newer than the ones that come with Ubuntu. I'm installing Kodi. When I do apt install kodi*, it downloads from kinetic/universe and not from team--xbmc/ppa.
[18:39] <EagleOwl> Well, I take it back. "/usr/bin/apache2" exists at 750kb+
[18:40] <murmel> MockingMoniker: there are different ways. you can pin those packages higher than the ubuntu packages, or just use -t <distro> <packages>
[18:41] <MockingMoniker> like apt -t team-xbmc/ppa install kodi*?
[18:41] <murmel> MockingMoniker: like apt install -t kinetic kodi*
[18:41] <MockingMoniker> Oh.
[18:42] <MockingMoniker> This is a custom repo for Kodi, it's not a distro.
[18:42] <murmel> yes
[18:44] <MockingMoniker> So... then I don't understand what I'm doing.
[18:44] <MockingMoniker> Because I'm thinking specifying the distro would have no affect.
[18:44] <MockingMoniker> It's just the same distro.
[18:45] <murmel> MockingMoniker: can you please paste your apt policy
[18:45] <murmel> !paste
[18:45] <MockingMoniker> k, one moment.
[18:47] <MockingMoniker> https://dpaste.com/4K4DJR4V6
[18:47] <ForeverNoob[m]> Hi, I'm trying to get Alacritty working on a Ubuntu Server 22.04 running inside KVM/Qemu. It's GPU accelerated and requires mesa and other stuff. What packages should I install in order to get try and get it working?
[18:47] <murmel> MockingMoniker: oh, you didn't even install the ppa?
[18:48] <MockingMoniker> There's a reference to it.
[18:48] <MockingMoniker> In /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-kinetic.list: deb https://ppa.launchpadcontent.net/team-xbmc/ppa/ubuntu/ kinetic main
[18:49] <murmel> MockingMoniker: ahh, apt update, apt upgrade should do it
[18:50] <MockingMoniker> murmel: I did that, did nothing.
[18:50] <MockingMoniker> Maybe the repo is just empty?
[18:50] <murmel> ForeverNoob[m]: afaik it shoud work when you install it
[18:50] <murmel> MockingMoniker: it's not, what does apt policy kodi say?
[18:50] <murmel> at least the site says there is a package https://launchpad.net/~team-xbmc/+archive/ubuntu/ppa?field.series_filter=kinetic
[18:51] <MockingMoniker> murmel: https://dpaste.com/FCNVHRNW3
[18:51] <murmel> MockingMoniker: but for some reason your apt policy doesn't show that you have the repo "enabled"
[18:53] <MockingMoniker> Yeah... did I do something wrong?
[18:53] <MockingMoniker> I'm using Ubuntu Server, does that change anything?
[18:53] <murmel> MockingMoniker: can you give me the output of /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-kinetic.list  it almost feels like it was commented out see if there is a # in front of the deb http...
[18:53] <murmel> MockingMoniker: it shouldn't
[18:54] <MockingMoniker> deb https://ppa.launchpadcontent.net/team-xbmc/ppa/ubuntu/ kinetic main <-- the sources line is commented out but this is the first line of the two line file.
[18:54] <murmel> ahh, so remove the #
[18:55] <murmel> apt update after and upgrae
[18:55] <murmel> d+
[18:55] <MockingMoniker> No, it hasn't the #. The sources one does, this onedoesn't.
[18:56] <murmel> ahh, sorry, misunderstood you
[18:56] <murmel> MockingMoniker: can you please paste the whole apt update (with command)
[18:57] <MockingMoniker> https://dpaste.com/HTE7Z8UFT
[18:57] <MockingMoniker> It's right there... is it possible that Ubuntu is using the exact same version as the new repo?
[18:58] <MockingMoniker> I mean, the Ubuntu repo has the same packages as the added repo?
[18:58] <murmel> MockingMoniker: at least looking at the version numbers, it's definitely not the same version
[18:58] <murmel> especially since the epoch version from ubuntu is 2: and from the ppa it's 6: (small difference ;) )
[18:58] <MockingMoniker> Is this a priority issue?
[18:59] <murmel> does apt policy now show you the ppa?
[19:00] <MockingMoniker> No.
[19:00] <murmel> oO
[19:00] <MockingMoniker> https://dpaste.com/BR3JLKAFG
[19:01] <murmel> I am sitting on jammy, and it works perfectly fine :S
[19:03] <murmel> but there is definitely something wrong when apt update shows you the ppa, but later it's not added to the "policy page"
[19:03] <MockingMoniker> Yeah, and this is a fresh install, did it an hour ago.
[19:04] <MockingMoniker> Maybe I should remove it and add it again.
[19:04] <murmel> try it
[19:08] <MockingMoniker> murmel: I did that, same effect.
[19:08] <murmel> MockingMoniker: what did you do to remove and add the ppa. just to make sure nothing went wrong there
[19:11] <MockingMoniker> https://dpaste.com/H8FADV6B8
[19:11] <MockingMoniker> I did some other commands to clean up stuff.
[19:12] <MockingMoniker> Then I did: add-apt-repository ppa:team-xbmc/ppa
[19:12] <MockingMoniker> Is the repo functioning correctly?
[19:13] <murmel> it should, give me a few mins, will try it out myself
[19:22] <MockingMoniker> murmel: any luck?
[19:23] <murmel> installing right now
[19:27] <murmel> MockingMoniker: ahh lol I should have looked at the ppa more closely, there are no packages available for kinetic, the build failed
[19:28] <MockingMoniker> murmel: so it's an empty repo?
[19:28] <murmel> MockingMoniker: on the other hand, why not use the LTS release with that ppa.
[19:28] <MockingMoniker> I just downloaded Ubuntu Server and slapt in on there, I did no work to verify anything.
[19:28] <murmel> yes
[19:29] <MockingMoniker> OK.
[19:29] <MockingMoniker> Should I have used Ubuntu Desktop instead of Server for Kodi?
[19:30] <murmel> MockingMoniker: no, just that Kinetic doesn't have a release by team-kodi for now. and imo just my opinion, why not use a LTS release so you don't have to "constantly" upgrade (as the lts is supported for 5 years)
[19:30] <murmel> but that depends on what you want to do with that server+kodi machine
[19:31] <MockingMoniker> I want to grab the latest Kodi* binaries published by Kodi. The rest of the system isn't important.
[19:31] <MockingMoniker> I didn't want to install a desktop environment, but rather just let Kodi run on its own.
[19:32] <murmel> MockingMoniker: so I would go LTS (22.04) + ppa
[19:33] <MockingMoniker> murmel: is there an easy way to switch or should I download the image all over again and install that way?
[19:34] <murmel> MockingMoniker: as there is no supported way to downgrade and you have no data (i assume) just download the image and reinstall
[19:35] <MockingMoniker> OK. Will do.
[19:36] <MockingMoniker> Will Ubuntu Server 22.04.1 LTS do or I should I get Ubuntu Server 22.10?
[19:37] <murmel> 22.04.1 ;)
[19:37] <murmel> 22.10 is the release you have right now
[19:37] <MockingMoniker> Oh.
[19:37] <MockingMoniker> Silly me.
[19:37] <rob0> LTS means long term support.
[19:37] <MockingMoniker> I see.
[19:38] <MockingMoniker> It was even in my question. I didn't look at the number carefully.
[19:38] <murmel> it happens ;) especially depends on what time it is :3
[19:38] <MockingMoniker> 12:38 PM :/
[20:00] <MockingMoniker> murmel: it's working now. I get candidates from the new PPA.
[20:07] <murmel> MockingMoniker: nice :)
[20:29] <X7> I'm getting worried about the state of debian with how the number of increasing packages that are orphaned (as in no maintainer anymore) and packages can become orphaned at any time. Does ubuntu have this problem also or does it avoid it thanks to canonical backing it?
[20:32] <murmel> X7: wrong channel, it fits better in #ubuntu-discuss
[20:32] <X7> Okay. Thanks.
[21:01] <LordDoskias> hello i'm trying to boot ubuntu live usb on a thinkpad t14 that has secureboot turned on - it doesn't work, if i turn off secur eboot it works
[21:01] <LordDoskias> is this expected?
[21:03] <jhutchins> LordDoskias: The reason secure boot was developed was to keep people from loading Linux on OEM Windows systems.
[21:03] <jhutchins> LordDoskias: You can make it work with Ubuntu these days, but why?
[21:04] <LordDoskias> well i thought ubuntu's shim was signed by mcft's cert which is loaded on the machine
[21:04] <LordDoskias> though i can see ubuntu's boot certificate in the revoke list in the bios
[21:04] <LordDoskias> :D
[21:30] <tripp4h> hi! i tried installing boot-repair ( https://help.ubuntu.com/community/Boot-Repair ) but it cannot be found from the repository!
[21:33] <tripp4h> i don't remember did i say it, but i cannot transfer (large) files to the samsung a22 phone in windows either, so it's not a mtp-bug! i wonder what's with that
[21:35] <oerheks> bootrepair for what ubuntu version?
[21:35] <oerheks> Kinetic is not ready indeed.
[21:35] <oerheks> then your only option is the bootrepair disk, see 1st option
[21:42] <tripp4h> oerheks: 22.10
[21:42] <tripp4h> i don't need boot-repair now, but if i need it in future it would be handy to have it installed
[21:42] <oerheks> = Kinetic
[21:43] <tripp4h> i wonder does it add itself to grub
[22:30] <ForeverNoob[m]> Hi, in 22.04 I'm having a bit of an issue with locales. Seemingly everything looks fine: https://0x0.st/o6JN.txt - And I even did `dpkg-reconfigure locales` but a lot of stuff is complaining about locales and I'm not sure why.
[22:34] <murmel> ForeverNoob[m]: and what kind of issues do you have? I mean the link doesn't give any info on that
[22:35] <ForeverNoob[m]> @murmel: Various things, for example `perl: warning: Setting locale failed.` and rofi: `Rofi-WARNING **: ...: Failed to set locale.`
[22:35] <ForeverNoob[m]> Some stuff not starting up when they should (i3bar etc.)
[22:36] <leftyfb> ForeverNoob[m]: https://www.cyberciti.biz/faq/failed-to-set-locale-defaulting-to-c-warning-message-on-centoslinux/
[22:54] <jhutchins> ForeverNoob[m]: Hate to suggest a Stupid Windows Trick, but have you rebooted?
[22:57] <ForeverNoob[m]> I think it might be the packages that I've installed using the Nix package manager. I uninstalled rofi and installed it via apt, and now it doesn't complain anymore. So I'm going to figure out how to smooth out the locale situation with nixpkgs.


[17:06] <tarciso> Anybody know how do i add the translation pages spreadubuntu.neomenlo.org?
[17:10] <tarciso> any?
[18:49] <jakswa> just came by to shout my props for the new rebranding!!  excited for 10.04!!
[18:50] <jakswa> I had an urge to find high quality files of the new logos/etc and do up a "it's almost here" poster and plaster it around my campus...


[12:58] <sudip> I marked LP: #2028007 as Incomplete, I could not reproduce the problem and asking the reporter for the steps to reproduce the problem. is that the correct status?
[12:58] -ubottu:#ubuntu-bugs- Launchpad bug 2028007 in grsync (Ubuntu) "crashed with segmentation fault error" [Undecided, Incomplete] https://launchpad.net/bugs/2028007
[15:29] <rbasak> That's correct. Thanks! The only other thing I usually do is ask the reporter to set the status back to New once they've provided the requested information, since otherwise the bugs tends to get lost (even though Launchpad has facilities to find such bugs).
[15:30] <rbasak> They have permission to do this themselves but they often don't know that.
[16:23] <sudip> will do. thanks rbasak
[16:26] <sudip> can anyone please mark LP: #1994145 as affecting Jammy, Lunar and Mantic. Noble is also affected
[16:26] -ubottu:#ubuntu-bugs- Launchpad bug 1994145 in mirage (Ubuntu) "Mirage segfaults immediately when run" [Undecided, Confirmed] https://launchpad.net/bugs/1994145
[20:40] <sudip> and also LP: 1974446 affecting Jammy please
[20:40] -ubottu:#ubuntu-bugs- Launchpad bug 1974446 in sngrep (Ubuntu) "sngrep in Jammy segfaults in del_panel (fixed upstream)" [Undecided, Confirmed] https://launchpad.net/bugs/1974446
[23:18] <rbasak> Both done, thanks.