[00:01] <javatexan> I am trying to get to dashboard from another computer since Ubuntu core doesn’t  have GUI
[05:30] <zyga> good morning
[05:30] <zyga> wow, I'm early
[06:07] <mborzecki> morning
[06:08] <zyga> mborzecki: hey
[06:08] <zyga> mborzecki: I think today is get-master-to-work day
[06:08] <zyga> I left some notes on https://github.com/snapcore/snapd/pull/9121
[06:08] <mup> PR #9121: github: remove Ubuntu 19.10 from actions workflow <Simple 😃> <⚠ Critical> <Created by zyga> <https://github.com/snapcore/snapd/pull/9121>
[06:08] <mborzecki> zyga: hey
[06:08] <zyga> but there are other bugs that essentially make master red - I restarted that branch all the time over weekend
[06:08] <zyga> mborzecki: something is killing/stopping systemd --user for root
[06:09] <zyga> which takes down dbus for root
[06:09] <zyga> and makes snapd fail on installing anything with user services
[06:09] <zyga> so those tests almost always fail
[06:09] <mborzecki> zyga: which systems are affected?
[06:09] <zyga> this is in addition to the regular set of random failures
[06:09] <zyga> I'm running fedora-32 as that's what I was debugging on Friday
[06:09] <zyga> but it affects ubuntu 20.04 as well
[06:10] <zyga> I think it's more of a luck factor (some systems managed to pass) or a specific-test factor (test only on some system that breaks the world for the rest)
[06:10] <zyga> unsure
[06:10] <zyga> I set workers to one and will have some more info
[06:10] <zyga> from Friday:
 2020-08-07T15:54:53.3788099Z     - google:fedora-32-64:tests/main/snap-user-service
 2020-08-07T15:54:53.3788764Z     - google:fedora-32-64:tests/main/snap-user-service-socket-activation
 2020-08-07T15:54:53.3797466Z     - google:fedora-32-64:tests/main/snap-user-service-start-on-install
 2020-08-07T15:54:53.3798599Z     - google:fedora-32-64:tests/main/snap-user-service-upgrade-failure
[06:11] <zyga> those failed but pass in isolation
[06:11] <mborzecki> mhm
 google:fedora-32-64 .../tests/main/snap-mgmt# ls -ld /run/user/0/snapd-session-agent.socket
 srw-rw-rw-. 1 root root 0 Aug  7 19:46 /run/user/0/snapd-session-agent.socket
 google:fedora-32-64 .../tests/main/snap-mgmt# systemctl --user status snapd-session-agent.socket
 Failed to connect to bus: Connection refused
 wat?
 google:fedora-32-64 .../tests/main/snap-mgmt# ls /run/user/0/bus -l
 srw-rw-rw-. 1 root root 0 Aug  7 19:46 /run/user/0/bus
[06:11] <zyga> in addition:
 root       45646  0.0  0.2  27040  9888 ?        Ss   19:47   0:00 /usr/bin/python3 /snap/test-snapd-service/x1/bin/start-stop-mode sighup
[06:11] <zyga> there's a test that installs malfunctioning services
[06:11] <zyga> and those clearly leak and just stay behind
[06:11] <zyga> we should fix that as well though it seems harmless
[06:12] <zyga> some more debugging:
 connect(3, {sa_family=AF_UNIX, sun_path="/run/user/0/bus"}, 18) = -1 ECONNREFUSED (Connection refused)
[06:12] <zyga> strace from systemctl --user status ...
[06:12] <zyga> lastly:
 this is the test sequence: google:fedora-32-64:tests/main/degraded google:fedora-32-64:tests/main/interfaces-broadcom-asic-control google:fedora-32-64:tests/main/login google:fedora-32-64:tests/main/snapshot-cross-revno google:fedora-32-64:tests/main/interfaces-content-mimic google:fedora-32-64:tests/main/refresh-undo google:fedora-32-64:tests/main/media-sharing google:fedora-32-64:tests/main/snap-switch google:fedora-32-64:tests/main/try-snap-g
[06:12] <zyga> oes-awa
 y:test_snapd_service google:fedora-32-64:tests/main/security-seccomp google:fedora-32-64:tests/main/core18-with-hooks google:fedora-32-64:tests/main/security-dev-input-event-denied google:fedora-32-64:tests/main/snap-run google:fedora-32-64:tests/main/interfaces-content-mkdir-writable:snap google:fedora-32-64:tests/main/retryable-error google:fedora-32-64:tests/main/snap-handle-link google:fedora-32-64:tests/main/interfaces-location-control
 google:fedora-32-64:tests/main/interfaces-netlink-audit google:fedora-32-64:tests/main/snap-mgmt google:fedora-32-64 .../tests/runtime-state#
[06:12] <zyga> that's all I know
[06:12] <zyga> I forgot the seed value :/
[06:12] <zyga> sorry
[06:13] <zyga> oh, and master is still broken due to 19.10 removal
[06:13] <zyga> so perhaps fixes should go to https://github.com/snapcore/snapd/pull/9121
[06:13] <mup> PR #9121: github: remove Ubuntu 19.10 from actions workflow <Simple 😃> <⚠ Critical> <Created by zyga> <https://github.com/snapcore/snapd/pull/9121>
[06:13] <zyga> or mvo could merge that and we could target fixes to individual branches
[06:16] <zyga> mborzecki: I wonder if my fixes didn't break master: I added this to some tests: systemctl --user stop dbus.service
[06:16] <zyga> perhaps that's wrong and after getting dbus activated over the socket, it's impossible to reliably stop it
[06:16] <zyga> note that this was specifically used to stop root's dbus
[06:17] <mborzecki> zyga: as if once it becomes part of the session, it goes down with a session?
[06:17] <zyga> perhaps
[06:17] <zyga> I really don't know
[06:17] <zyga> we normally have systemd --user
[06:17] <zyga> but not dbus.service (--user for root)
[06:17] <zyga> at least that's what I think,
[06:17] <zyga> need to find the reproducing seed first
[06:37] <zyga> mvo: good morning
[06:37] <zyga> mvo: we need your help
[06:38] <mvo> zyga: good morning
[06:38] <mvo> zyga: how can I help?
[06:38] <zyga> mvo: please merge https://github.com/snapcore/snapd/pull/9121
[06:38] <mup> PR #9121: github: remove Ubuntu 19.10 from actions workflow <Simple 😃> <⚠ Critical> <Created by zyga> <https://github.com/snapcore/snapd/pull/9121>
[06:38] <zyga> mvo: we have several problems breaking master
[06:38] <zyga> that branch was restarted many times over weekend
[06:38] <zyga> mvo: I updated mborzecki on the issue as much as I know
[06:38] <mborzecki> mvo: hey
[06:39] <zyga> mvo: the short summary is that something is causing systemd --user for root to shut down, breaking all tests that install snaps with user services
[06:39] <zyga> mvo: I'm working on debugging that now
[06:40] <mvo> zyga: ok
[06:40] <mvo> mborzecki: good morning
[06:41] <mvo> zyga: merged
[06:43] <mvo> zyga: is 9119 ready? it looks ok to me and has 2 +1 but is in draft so can't be merged
[06:44] <mup> PR snapd#9121 closed: github: remove Ubuntu 19.10 from actions workflow <Simple 😃> <⚠ Critical> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9121>
[06:44] <mup> PR snapd#9123 closed: vendor: update secboot to support dual signed EFI binaries <Created by cmatsuoka> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9123>
[06:55] <zyga> re, back from breakfast
[06:56] <zyga> mvo: yeah, it was ready
[06:56] <zyga> thank you for merging, I hope we can fix the remaining issues quickly
[06:57] <zyga> mvo: merging https://github.com/snapcore/snapd/pull/9112 would help as well, somehow I keep hitting that in my debug runs
[06:57] <mup> PR #9112: tests: run as hightest via tests.session <Test Robustness> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9112>
[06:57] <zyga> oh
[06:57] <zyga> haha, nice
[06:58] <mvo> zyga: I mark 9119 as ready then
[06:59] <zyga> thanks
[06:59] <zyga> I wanted to get a clean pass but I think that's less practical now
[06:59] <mup> PR snapd#9109 closed: github: run CLA checks on self-hosted workers <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9109>
[06:59] <mup> PR snapd#9112 closed: tests: run as hightest via tests.session <Test Robustness> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9112>
[06:59] <mup> PR snapd#9113 closed: tests: port regression-home-snap-root-owned to tests.session <Test Robustness> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9113>
[07:01] <zyga> I started early today as I have physio at 18;00
[07:01] <pstolowski> morning
[07:01] <zyga> good morning Pawel
[07:04] <mborzecki> pstolowski: hey
[07:04] <mvo> good morning pstolowski
[07:04] <mup> PR snapd#9104 closed: tests: fix for timing issues on journal-state test <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9104>
[07:04] <mup> PR snapd#9119 closed: many: remove usage and creation of hijacked pid cgroup <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9119>
[07:30] <zyga> brb,
[07:30] <zyga> rebased on master, no luck with fixes yet
[07:30] <zyga> back in 20
[07:44] <zyga> reproduced
[07:45] <zyga> master
[07:45] <zyga> spread -seed=1597043051 -debug -v google:fedora-32-64:tests/main/
[07:45] <zyga> this fails on - Make snap "test-snapd-user-service" (unset) available to the system (Post "http://0/v1/service-control": dial unix /run/user/0/snapd-session-agent.socket: connect: connection refused)
[07:45] <zyga> inside 2020-08-10 09:32:24 Error executing google:fedora-32-64:tests/main/snap-user-service (aug100704-587445) :
[07:46] <zyga> I'll try to understand what causes this now
[07:47] <zyga> prior tests on this machine:
[07:47] <zyga> google:fedora-32-64:tests/main/degraded google:fedora-32-64:tests/main/interfaces-broadcom-asic-control google:fedora-32-64:tests/main/try-snap-goes-away:test_snapd_tools google:fedora-32-64:tests/main/services-stop-timeout google:fedora-32-64:tests/main/interfaces-fuse-support:parallel google:fedora-32-64:tests/main/install-refresh-remove-hooks:regular google:fedora-32-64:tests/main/interfaces-home google:fedora-32-64:tests/main/snap-interface
[07:47] <zyga> google:fedora-32-64:tests/main/debug-sandbox google:fedora-32-64:tests/main/auto-refresh-retry google:fedora-32-64:tests/main/change-errors google:fedora-32-64:tests/main/umask google:fedora-32-64:tests/main/user-session-env google:fedora-32-64:tests/main/security-apparmor google:fedora-32-64:tests/main/parallel-install-services google:fedora-32-64:tests/main/abort google:fedora-32-64:tests/main/interfaces-appstream-metadata google:fedora-32-64:tests/main/r
[07:47] <zyga> etry-network google:fedora-32-64:tests/main/interfaces-network-control-ip-netns google:fedora-32-64:tests/main/snapctl-is-connected google:fedora-32-64:tests/main/cgroup-tracking:root google:fedora-32-64:tests/main/services-disabled-kept-unhappy google:fedora-32-64:tests/main/op-remove-retry google:fedora-32-64:tests/main/revert-devmode:remote google:fedora-32-64:tests/main/base-snaps google:fedora-32-64:tests/main/interfaces-shutdown-introspection
[07:47] <zyga> google:fedora-32-64:tests/main/snapd-notify google:fedora-32-64:tests/main/install-sideload-epochs:reexec1 google:fedora-32-64:tests/main/auto-aliases google:fedora-32-64:tests/main/snap-remove-not-mounted google:fedora-32-64:tests/main/interfaces-netlink-connector google:fedora-32-64:tests/main/debug-confinement google:fedora-32-64:tests/main/services-stop-mode google:fedora-32-64:tests/main/known google:fedora-32-64:tests/main/user-data-handling
[07:48] <zyga> google:fedora-32-64:tests/main/interfaces-framebuffer google:fedora-32-64:tests/main/base-policy google:fedora-32-64:tests/main/chattr google:fedora-32-64:tests/main/interfaces-system-observe google:fedora-32-64:tests/main/searching google:fedora-32-64:tests/main/interfaces-desktop-host-fonts google:fedora-32-64:tests/main/interfaces-hardware-random-observe google:fedora-32-64:tests/main/snap-user-service + echo '# free space'
[07:48] <zyga> (sorry for pasting most of the log directly)
[07:49] <mborzecki> is pedronis around today?
[07:49] <zyga> I don't recall
[07:49] <zyga> heh, cats fighting outside
[07:49] <zyga> funny noises
[07:59] <zyga> interesting that<EMAIL_ADDRESS>is stopped normally
[07:59] <zyga> Aug 10 07:25:30 aug100704-587445 systemd[912]: Reached target Exit the Session.
[07:59] <zyga> 7:25:30
[08:00] <mborzecki> zyga:linger?
[08:00] <zyga> we should log tests
[08:00] <zyga> as in log the start / stop of a test to journal
[08:00] <zyga> this will make it evident what's going on
[08:00] <zyga> possibly
[08:01] <mborzecki> we had some changes in how linger is enabled
[08:01] <mborzecki> probably like ~month ago
[08:02] <zyga> worth a try
[08:02] <mborzecki> heh, 9 files changed, 577 insertions(+), 137 deletions(-), can't really make the content update observer smaller
[08:02] <mborzecki> tests inflate it a lot
[08:03] <zyga> mborzecki: yeah
[08:03] <zyga> tests.session -u root stops
[08:03] <zyga> stops<EMAIL_ADDRESS>[08:04] <zyga> hmm
[08:04] <zyga> maybe restore for root
[08:04] <zyga> should remember if we had really started that
[08:04] <zyga> and re-start it
[08:04] <zyga> that would give us working dbus
[08:08] <zyga> ok, I have an idea, let's try to write a patch
[08:08] <zyga> mborzecki: I also wonder what amplified this problem
[08:08] <zyga> was it something we did or was it the dependencies changing
[08:09] <mborzecki> zyga: afaiu it's observable on stable distros now?
[08:09] <mborzecki> so i'd bet on something in the tests
[08:09] <zyga> mborzecki: on 20.04
[08:09] <zyga> so presumably that's us
[08:11] <zyga> mborzecki: but this is so weird
[08:11] <zyga> we disable root linger
[08:11] <zyga> but not stop anything
[08:11] <zyga> maybe the recent changes I did for systemd-logind caused this
[08:12] <mborzecki> pedronis: hi, i've opened #9124, it's mounted fs updater & gadget.Update(), still the diffstat is +579 −137
[08:12] <mup> PR #9124: gadget: introduce content update observer <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9124>
[08:14] <mup> PR snapd#9124 opened: gadget: introduce content update observer <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9124>
[08:14] <pedronis> mborzecki: thx
[08:20] <mborzecki> hmm An error occurred with the instance when trying to launch with 'LXD': Unable to fetch https://cloud-images.ubuntu.com/buildd/daily/xenial/20200728/xenial-server-cloudimg-amd64-lxd_combined.tar.gz: 404 Not Found.
[08:20] <mborzecki> at least it does return 404
[08:23] <zyga> the date is very precise, do we use a fixed image URL?
[08:23] <zyga> perhaps we need to "lxd something" for lxd to find the proper images
[08:25] <mborzecki> https://cloud-images.ubuntu.com/buildd/daily/xenial/20200728/xenial-server-cloudimg-amd64-lxd_combined.tar.gz does not 404
[08:25] <amurray> mborzecki zyga: this is a known issue - https://forum.snapcraft.io/t/snapcraft-with-lxd-pulling-an-outdated-lxc-image/19324/3 - well not sure if the right cpc folks who could fix it know about it but is due to out of date simplestreams metadata
[08:26] <zyga> ah, thanks for sharing that
[08:50] <zyga> I found the problem
[08:50] <zyga> eh
[08:50] <zyga> systemd bugs :/
[08:50] <zyga> restarting logind is just not a good idea
[08:50] <zyga> I think we need to do two things
[08:50] <zyga> move the workaround for an older systemd bug into the system global prepare
[08:50] <zyga> then combine that with the upgrade of systemd
[08:50] <zyga> and REBOOT
[08:50] <zyga> mborzecki: the problem seems to be that logind doesn't remember sessions
[08:51] <zyga> and when we disable linger
[08:51] <zyga> it forgets it had a root session that was made by spread
[08:52] <zyga> so the recent fix for sid has amplified the problem
[08:55] <zyga> lennart replied to our bug: https://github.com/systemd/systemd/issues/16685#issuecomment-670166505
[08:56] <zyga> systemd maintainers are sure responsive, that's really nice
[08:56] <zyga> eh
[08:57] <zyga> yeah, confirmed
[08:57] <zyga> restarting logind does lose state
[08:57] <zyga> at least in 245
[08:58] <zyga> mborzecki: https://github.com/systemd/systemd/issues/16685#issuecomment-671239737
[08:59] <zyga> mvo: I will try to fix master, at least make it better, in the next hour, sorry for the mess
[08:59] <zyga> it's the fallout from the sid fix indeed
[09:07]  * zyga tests a fix now
[09:26] <zyga> mborzecki: yet-untested draft of the fix: https://github.com/snapcore/snapd/pull/9125
[09:26] <mup> PR #9125: tests: fix issues related to restarting systemd-logind.service <Test Robustness> <⚠ Critical> <Created by zyga> <https://github.com/snapcore/snapd/pull/9125>
[09:27] <zyga> locally tests are in flight, I'll report back when I get some results
[09:30] <mup> PR snapd#9125 opened: tests: fix issues related to restarting systemd-logind.service <Test Robustness> <⚠ Critical> <Created by zyga> <https://github.com/snapcore/snapd/pull/9125>
[09:31] <zyga> can we do something about the issue with lxd images?
[09:41] <zyga> mborzecki: eh, can we REBOOT from project prepare in general?
[09:41] <zyga> I recall arch does
[09:41] <zyga> but it has modern bash
[09:41] <zyga> are we still affected by the bash bug with exit code propagation?
[09:41] <mborzecki> zyga: iirc REBOOT works in prepare, there were problems in restore
[09:42] <zyga> ah, I see
[09:43] <zyga> oh man
[09:43] <zyga> catch 22
[09:43] <zyga> core workaround
[09:43] <zyga> and linger workaround
[09:44] <zyga> core16 is a big problem now :/
[09:44] <zyga> but first, let me go downstairs, I really don't know where to work today
[09:44] <zyga> bedroom is an oven, office a frying pan
[10:09] <pedronis> mborzecki: mvo: #9095 needs a 2nd review
[10:09] <mup> PR #9095: boot/bootstate20: unify commit method impls, rm bootState20MarkSuccessful <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9095>
[10:09] <mborzecki> pedronis: it's in my queue
[10:25] <zyga> mborzecki: hmm, it seems we cannot REBOOT from project prepare though
[10:25] <zyga> https://pipelines.actions.githubusercontent.com/xS8oSnypZkPEQZqiZgDaRp2kdvQJKbOY08TesHp7E8vn7g4hYR/_apis/pipelines/1/runs/10735/signedlogcontent/75?urlExpires=2020-08-10T10%3A26%3A15.6985947Z&urlSigningMethod=HMACV1&urlSignature=KBzWVhJfo58j12Er5gL0cjRFu7LXUhaRJ52TCxy8R%2B4%3D
[10:25] <zyga> 2020-08-10T09:39:43.8002986Z <REBOOT>
[10:26] <zyga> or am I reading that wrong
[10:26] <zyga> after REBOOT the test fails
[10:26] <mborzecki> hm
[10:26] <mborzecki> maybe it's not producing the same exit status as REBOOT?
[10:26] <zyga> but this is weird
[10:27] <zyga> we only have one REBOOT
[10:27] <zyga> the one provided by spread is unset immediately after cloning it
[10:27] <zyga> and this is long after
[10:27] <zyga> but this is still weird, I mean, I'm testing this locally
[10:27] <mborzecki> zyga: can you try with this https://github.com/snapcore/spread/pull/85 ?
[10:27] <mup> PR spread#85: spread/client: workaround bash 4.3 subshell errexit issues <Created by bboozzoo> <https://github.com/snapcore/spread/pull/85>
[10:27] <zyga> and I surely don't get failures (I was only testing Fedora)
[10:28] <zyga> oh
[10:28] <zyga> so this didn't land!?
[10:28] <zyga> mborzecki: I can but it works for me (I'm using the same spread as our workers do)
[10:28] <zyga> something doesn't make sense here
[10:29] <zyga> hm, fedora 32 failed after 24 minutes
[10:29] <zyga> so perhaps it does work on fedora
[10:29] <zyga> but it fails in a different way
[10:29] <zyga> 2020-08-10T10:01:49.7316727Z ##[error]2020-08-10 10:01:49 Error preparing google:fedora-32-64 (aug100938-989118) : rebooted on aug100938-989118 (google:fedora-32-64) more than 10 times
[10:29] <zyga> like a reboot loop
[10:29] <zyga> yet my local run is at 3/4 of completion without an issue
[10:30] <zyga> I think my code is naive
[10:30] <zyga> I need to have a condition for REBOOT
[10:30] <mup> PR snapd#9126 opened: boot: introduce current_boot_assets and current_recovery_boot_assets to modeenv <Simple 😃> <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9126>
[10:30] <mborzecki> pedronis: hopefully this is a trvial one ^^
[10:30] <zyga> how do I check the running version of systemd-logind
[10:33] <zyga> ok I think I have an idea
[10:36] <zyga> mborzecki: how does https://paste.ubuntu.com/p/vj7B5DNf3d/
[10:36] <zyga>  look like
[10:37] <zyga> ouch
[10:37] <zyga> sorry
[10:37] <zyga> back pain
[10:37] <zyga> I tried to work sitting
[10:38] <zyga> mborzecki: we can detect if systemd was updated across 245-246 line
[10:38] <zyga> uh back to bed for now
[10:40] <zyga> ouch
[10:41] <zyga> easier said
[10:45] <mborzecki> zyga: so when we're running < 246 and update pulls in 246+ we restart?
[10:45] <mborzecki> zyga: does it happen anywhere outside of arch/tw/sid?
[10:46] <zyga> mborzecki: yeah, that's the idea
[10:46] <zyga> we also restart if we had to reconfigure systemd
[10:46] <zyga> er, logind
[10:46] <zyga> so the actual upgrade happens on sid for now
[10:46] <zyga> but the other condition also happens on many systems
[10:46] <zyga> it's just less frequent
[10:47] <zyga> the bottom line is that restarting logind is just unsafe
[10:47] <zyga> I have no idea how to solve this on 16.04
[10:47] <zyga> where we need to make mount changes to make logind fixable
[10:47] <zyga> fix it
[10:47] <zyga> restart it to apply the fix
[10:47] <zyga> (that's already wrong then)
[10:55] <jamesh> zyga: I think I've addressed all the feedback on #9043 either with code changes or responses to comments.
[10:55] <mup> PR #9043: daemon: replace access control flags on commands with access checkers <Needs security review> <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9043>
[10:55] <zyga> ack
[10:55] <zyga> I'll look after current master woes
[10:56] <jamesh> zyga: as far as naming of the access checkers, I think there is value in keeping the naming consistent with the documentation
[11:01] <zyga> jamesh: perhaps, but only if the name is accurate
[11:01] <jamesh> zyga: sure.  I'm not saying the docs are immutable
[11:32] <zyga> brb
[11:32] <zyga> got a clean run on fedora 32
[11:32] <zyga> thinking about core16 options
[11:49] <zyga> mborzecki: yeah, so REBOOT is busted
[11:49] <zyga> https://github.com/snapcore/snapd/pull/9125/checks?check_run_id=966349834
[11:49] <mup> PR #9125: tests: fix issues related to restarting systemd-logind.service <Test Robustness> <⚠ Critical> <Created by zyga> <https://github.com/snapcore/snapd/pull/9125>
[11:49] <zyga> I'm certain we need some kind of workaround for that bash issue
[11:49] <mborzecki> zyga: have you tried with the spread branch?
[11:49] <zyga> I'll try merging it locally to see if that helps
[11:49] <zyga> not yet
[11:50] <zyga> I will
[11:50] <zyga> if it helps we need to get that reviewed
[11:50] <zyga> I wonder what to do now
[11:50] <zyga> should we revert the restart "fix" for sid
[11:50] <zyga> disable sid for now
[11:50] <zyga> do something else
[11:50] <zyga> mvo: ^ advice welcome
[11:50] <mup> PR snapd#9127 opened: bootloader: introduce TrustedAssetsBootloader, implement for grub <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9127>
[11:50] <mborzecki> pedronis: trusted assets bootloader thingy ^^
[11:51] <mborzecki> time to do some reviews
[11:53] <mborzecki> hm we haven't landed any bits for debug that call uname -a or somesuch?
[11:54] <zyga> mborzecki: we have a PR from cachio
[11:54] <mborzecki> mhm, just +1'ed it
[11:55] <mborzecki> zyga: https://github.com/snapcore/snapd/pull/9116/checks?check_run_id=965583423
[11:55] <mup> PR #9116: tests: add system information and image information when debug info is displayed <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9116>
[11:55] <mborzecki> 2020-08-10T07:31:53.5421376Z Linux aug100702-249153 4.15.0-1080-gcp #90~16.04.1-Ubuntu SMP Fri Jul 10 19:11:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[11:55] <mup> PR #90: Default to SocketMode=0660 if no socket mode option is given <Created by mvo5> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/90>
[11:55] <mborzecki> and we have cgroup2fs under /sys/fs/cgroup
[11:55] <mborzecki> on xenial
[11:56] <zyga> mborzecki: that's ... just wrong?
[11:56] <zyga> how can we get that?!
[11:56] <zyga> is it overmounted
[11:56] <zyga> as in shadowing the tmpfs normally there
[11:58] <mborzecki> zyga: hm i misread, it's tmpfs, we check whether /sys/fs/cgroup/unified exists, but it does not?
[11:58] <zyga> mborzecki: hmmmm
[11:58] <zyga> that's possible
[11:58] <zyga> though I don't remember what the conditions are
[11:58] <zyga> maybe our check is wrong?
[11:59] <pedronis> mborzecki: I reviewed #9124, looks good but couple of questions
[11:59] <mup> PR #9124: gadget: introduce content update observer <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9124>
[11:59] <mborzecki> pedronis: thanks
[12:05] <mup> PR snapd#9128 opened: tests/main/cgroup-tracking: try to collect some information about cgroups <Simple 😃> <Test Robustness> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9128>
[12:05] <mborzecki> zyga: ^^ some more info
[12:10] <zyga> nice
[12:10] <zyga> let's see what that shows
[12:10] <zyga> today is not a very good day, is it?
[12:10] <zyga> I'm making progress, will try a core 16 idea nonw
[12:10] <zyga> *now
[12:11] <pedronis> mborzecki: question(s) in #9127
[12:11] <mup> PR #9127: bootloader: introduce TrustedAssetsBootloader, implement for grub <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9127>
[12:19] <mborzecki> pedronis: right, that's for the case if one gets a bootloader without NoSlashBoot in options, it should probably be internal error as you indicated, it's not a reasonable use case
[12:34] <mborzecki> pedronis: current_trusted_recovery_boot_assets?
[12:34] <pedronis> mborzecki: ok, let's have the error and see how it goes
[12:35] <mborzecki> instead of current_recovery_trusted_boot_assets
[12:35] <pedronis> that probably reads better
[12:43] <zyga> amazing
[12:43] <zyga> what am I missing
[12:43]  * zyga checks spread source
[12:43] <zyga> nah, I am running master
[12:43] <zyga> ok, lets see if main passes
[12:43] <zyga> core16 did not crash and burn for me locally
[12:44] <ijohnson> morning folks
[12:47] <pedronis> ijohnson: hello
[12:47] <ijohnson> hi pedronis
[12:50] <ijohnson> pedronis: thoughts on moving envRefExtractedKernelBootloaderKernelState and extractedRunKernelImageBootloaderKernelState to a different file, maybe boot/bootstate20_kernelstate.go ?
[12:50] <ijohnson> that would make the bootstate20 file a little bit easier to navigate I think
[12:50] <ijohnson> of course not for my current PR, but a followup
[12:50] <zyga> hey ijohnson :)
[12:51] <ijohnson> hey zyga
[12:54] <pedronis> ijohnson: sounds ok
[12:58] <ijohnson> pedronis: cool I'll try to do that after we land the current PR
[13:15] <zyga> mvo: I've added https://github.com/snapcore/snapd/pull/9129 for 2.46
[13:15] <mup> PR #9129: sandbox/cgroup: remove temporary workaround for multiple cgroup writers <Created by zyga> <https://github.com/snapcore/snapd/pull/9129>
[13:16] <mup> PR snapd#9129 opened: sandbox/cgroup: remove temporary workaround for multiple cgroup writers <Created by zyga> <https://github.com/snapcore/snapd/pull/9129>
[13:25] <zyga> mvo: what would it take to make /var/lib/systemd/ writable on core16 (it is writable on 18 and 20 already) - I'm specifically after /var/lib/systemd/linger so we could have a subset of the directory (just linger) available to help
[13:32] <ijohnson> zyga: just for our tests or IRL too ?
[13:37] <zyga> ijohnson: it's just for out tests but we seem to have done this on core18+ so I guess that's for a reason
[13:37] <zyga> and IRL is a weird way to describe that :)
[13:38] <zyga> brb, small break
[13:43] <pedronis> in general it's easier to have the 3 consistent when there's no strong reason for not
[13:45] <ijohnson> zyga: yeah in that case we should just do it IRL for core snap
[13:47] <zyga> I agree
[13:47] <zyga> consistency
[13:47] <zyga> and less special cases
[13:47] <ijohnson> indeed
[13:55] <zyga> I will break for lunch and an errand and then go for physio
[13:55] <zyga> I will do my best to work when I'm back to prepare the fixes for logind
[14:10] <cachio> pstolowski, ijohnson thanks for the review fo #8942, I already answer the question about the variable
[14:10] <mup> PR #8942: tests: support different images on nested execution <Run nested> <Squash-merge> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/8942>
[14:13] <ijohnson> thanks cachio
[14:14] <cachio> ijohnson, sorry for the delay, didn't see that on friday
[14:14] <ijohnson> no worries
[14:17] <pstolowski> cachio: thanks
[14:27] <pedronis> mvo: cachio: are we releasing .3.1 today?
[14:27] <cachio> pedronis, I am waiting confirmation from store team
[14:27] <pedronis> thx
[14:27] <cachio> pedronis, they asked me to wait
[14:47] <cachio> pedronis, progressive release for core snap started
[14:47] <cachio> mvo, ~
[14:47] <mvo> cachio: nice, thanks
[14:47] <pedronis> thx
[14:48] <pedronis> mvo: it would probably good to land #9086 but it needs a 2nd review (it's a cleanup)
[14:48] <mup> PR #9086: many: reorg cmd/snapinfo.go into snap and new client/clientutil <Cleanup :broom:> <Created by pedronis> <https://github.com/snapcore/snapd/pull/9086>
[14:48] <mvo> pedronis: looking
[14:50] <pedronis> mvo: I moved my assertions PR to 2.47
[14:50] <mvo> pedronis: thank you
[15:16] <zyga> made some more progress on core16, should have a green pass soon
[15:16] <zyga> but now physio
[15:16] <zyga> see you in a few hours
[15:18]  * cachio lunch
[15:19] <ijohnson> mborzecki: have you seen the triggerwatch unit test  triggerwatchSuite.TestNoDevsWaitKey fail before?
[15:19] <ijohnson> FAIL: triggerwatch_test.go:80: triggerwatchSuite.TestNoDevsWaitKey
[15:19] <ijohnson> triggerwatch_test.go:87:
[15:19] <ijohnson>     c.Assert(err, IsNil)
[15:19] <ijohnson> ... value *errors.errorString = &errors.errorString{s:"trigger not detected"} ("trigger not detected")
[15:19] <ijohnson> OOPS: 4 passed, 1 FAILED
[15:25] <pedronis> mvo: I forgot to mention last week, did you see this: https://github.com/snapcore/core18/pull/155 ?  (same for the parallel PRs), the name of the dir is wrong
[15:25] <mup> PR core18#155: hooks: fix broken symlink /etc/sysctl.conf.d/99-sysctl.conf <Created by mvo5> <https://github.com/snapcore/core18/pull/155>
[15:26] <mvo> pedronis: oh, missed that, sorry
[15:27] <ijohnson> interestingly a model assertion unit test panic'd on riscv64, seems to be timing related somehow https://pastebin.ubuntu.com/p/7ppt8pTbdz/
[15:28] <ijohnson> cachio: do you need to delete some images on gce again? I see `2020-08-10 14:33:27 Cannot allocate google:opensuse-tumbleweed-64: cannot allocate new Google server google:opensuse-tumbleweed-64 (aug101430-988733): cannot find ready marker in console output for google:opensuse-tumbleweed-64 (aug101430-988733)` in spread runs now
[15:35] <mborzecki> ijohnson: heh, probably a timing issue
[15:35] <mborzecki> was outside for a bit, +35C
[15:39] <mvo> pedronis: I reviewed 9086 now
[16:03] <kenvandine> mvo: what's the status of lzo support?  Is that ready to be used?  What snapd version first supported it?
[16:04] <mvo> kenvandine: for snapd on install it's actually transparent, so any snapd version will work
[16:04] <kenvandine> but not at runtime.  We're talking about injecting an "assumes" in there
[16:05] <mvo> kenvandine: not at runtime? what issue/error do you see with older snapd versions?
[16:05] <mvo> kenvandine: "snap pack --compression=lzo" is more recent
[16:06] <kenvandine> wait... when you launch the snap on an old version of snapd
[16:06] <mvo> kenvandine: but the ability to run lzo snaps should be transparent to snapd
[16:06] <kenvandine> that would work?
[16:06] <mvo> kenvandine: yes
[16:06] <mvo> kenvandine: I don't see why it would not :) maybe I'm missing something
[16:07] <kenvandine> ok, i thought there was talk about needing specific versions
[16:07] <kenvandine> i guess i misunderstood :)
[16:07] <kenvandine> mvo: and no known issues on other distros?  centos, fedora, etc?
[16:08] <mvo> kenvandine: same, as long as they have a kernel that supports lzo for squashfs (which they all do) then this will be fine
[16:08] <kenvandine> ok
[16:09] <kenvandine> mvo: thanks, we're going to start testing it :)
[16:09] <kenvandine> with real snaps
[16:09] <mvo> kenvandine: \o/ nice!
[16:09] <mvo> kenvandine: AIUI chromium is already whitelisted in the reviewtools to allow lzo
[16:09] <kenvandine> ok
[16:10] <kenvandine> Wimpress was suggesting we try a few snapcrafter snaps first, so we'll work that out
[16:10] <kenvandine> and maybe experiment with the gnome platform snap too
[16:30] <cachio> ijohnson,  done
[16:30] <Aavar> How would I go about building a snap of deluge 1.3 for 20.04? Or better yet, would anyone be interested in creating such a snap?
[16:31] <ijohnson> thanks cachio
[16:43] <oerheks> Aavar, there is 2.0.3 already
[16:43] <oerheks> https://snapcraft.io/deluge-lukewh
[17:36]  * zyga-mbp is back from physio but not working ye
[17:36] <zyga-mbp> *yet
[17:37] <mup> PR snapd#9130 opened: [RFC] Support for gadget.yaml "$kernel:" style references <Created by mvo5> <https://github.com/snapcore/snapd/pull/9130>
[17:45] <ijohnson> cachio: I
[17:46] <ijohnson> I'm still seeing that ready marker error in spread with tumbleweed
[17:46] <ijohnson> `2020-08-10 17:21:32 Cannot allocate google:opensuse-tumbleweed-64: cannot allocate new Google server google:opensuse-tumbleweed-64 (aug101718-511919): cannot find ready marker in console output for google:opensuse-tumbleweed-64 (aug101718-511919)`
[17:46] <ijohnson> does it take a while for that to deploy ?
[17:46] <cachio> ijohnson, ah, ok, in that case this is another error
[17:46] <cachio> let me cehck again
[17:46] <ijohnson> ok
[17:46] <cachio> ijohnson, fixed
[17:47] <ijohnson> thanks I'll try again
[17:47] <cachio> I'll need to re create a new image for tumbleweed
[18:33] <zyga> back from physio
[18:33] <zyga> how are things?
[18:34] <zyga> I will get back to 16.04 part of the problem in a moment, let me review public tests first
[18:35] <cachio> zyga, I could reproduce the error in the cgroup-tracking
[18:35] <zyga> cachio: tell me more!
[18:35] <cachio> but still couldn't find which test is producing it
[18:35] <zyga> cachio: I reproduced it a few times
[18:36] <zyga> cachio: but I didn't focus on debugging it yet, I'll try tomorrow - assuming the current issues are fixed
[18:36] <zyga> cachio: we added some detectors to invariant checker and it's not the kernel - it is clearly some other factor
[18:36] <cachio> zyga, what I found is that there is another test which if it executed before the  cgroup-tracking test fail
[18:36] <zyga> cachio: when it happened it was running the 4.15 gce kernel
[18:36] <zyga> yeah, I think that must be the case
[18:37] <zyga> we could find an intersection of sets after a few runs
[18:37] <zyga> I'm sure we'll find it
[18:37] <cachio> zyga, yes
[18:37] <cachio> let me find that
[18:37] <cachio> I'll send you what I find
[18:38] <cachio> zyga, I think in hours I can have that info
[18:39] <zyga> cool, drop me a line or go and fix it if you find the broken test
[18:39] <zyga> I'm no longer always on IRC so mattermost is best for a message box style
[18:39] <cachio> zyga, sure
[18:39] <cachio> I'll let you know
[18:39] <cachio> enjoy your evening
[18:41] <zyga> thank you :)
[20:22] <mup> PR core#116 opened: extra-files/writable-paths: make all /var/lib/systemd writable <Created by anonymouse64> <https://github.com/snapcore/core/pull/116>
[20:23] <cachio> ijohnson, hey
[20:23] <cachio> I see this is uc20 https://paste.ubuntu.com/p/rhzB3sRQyV/
[20:23] <ijohnson> hey cachio
[20:24] <ijohnson> cachio: ah yes that was fixed recently
[20:24] <ijohnson> --purge only works on a single snap
[20:24] <ijohnson> you need to do `snap remove --purge jq` `snap remove --purge jq-core18` etc.
[20:24] <cachio> ijohnson, ah, ok, I'll fix my scripts in that case
[20:24] <cachio> thanks
[22:36] <mup> PR snapcraft#3242 opened: tests: remove expected failure case from legacy integration test <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3242>


[09:13] <pavlushka_> Hello every one!
[09:35] <pavlushka> Hello ahoneybun dipraw Researcher- Tuhin wxl ! have a good day every one, :)
[10:13] <pavlushka> hello bluebird Arnab, !
[12:16] <dipraw> same to u pavlushka
[12:17] <pavlushka> dipraw: the tradition is to say "pong"
[12:17] <pavlushka> in reply
[12:18] <dipraw> got it pong! :/
[12:39] <pavlushka> Hey AudaciousTUX
[12:39] <AudaciousTUX> hei....
[12:40] <AudaciousTUX> i have an idea.... about website
[12:40] <pavlushka> AudaciousTUX: really you cant ask a question in askubuntu? when you are supposed to?
[12:41] <pavlushka> AudaciousTUX: can you give us a screenshot of your logged-in interface of askubuntu?
[12:41] <AudaciousTUX> the time never comes... i always find a answer before asking :p
[12:42] <pavlushka> AudaciousTUX: please talk to the point, dont slip it, can you give us a screenshot of your logged-in interface of askubuntu?
[12:43] <AudaciousTUX> umm... i can ask question.... but can't vote up answers
[12:43] <AudaciousTUX> and too lazy to ask a question :v
[12:48] <pavlushka> AudaciousTUX: so you have no problem then, you have to earn 15 rep by asking useful question to get a upvote (+5 rep), and by editing/correcting others post (+2 rep), and then you can vote up.
[12:48] <pavlushka> +2 rep for every edit
[12:50] <AudaciousTUX> umm
[12:50] <pavlushka> Good afternoon Kilos !
[12:52] <pavlushka> AudaciousTUX: when you tried to up vote, there supposed to flash this notifications which you didn't noticed well.
[12:52] <pavlushka> AudaciousTUX: well, not as explained as I did, :p
[12:54] <Kilos> hi pavlushka
[12:54] <Kilos> and AudaciousTUX
[12:54] <Kilos> and others
[13:00] <AudaciousTUX> bye all... have to study for pre-test exam... :'( btw... i'll work on website after my exam....  :)
[13:04] <Kilos> good luck AudaciousTUX
[13:58] <zaki> hello pavlushka Kilos and others.
[14:00] <pavlushka> zaki: Hello !
[14:00] <pavlushka> zaki: what about https://github.com/lwfinger/rtlwifi_new ?
[14:02] <zaki> hi
[14:03] <zaki> this is for new karnel i think
[14:03] <zaki> may be it will work!
[14:11] <zaki> i will try later, final exam nextday. eng101. been busy with studies.
[14:20] <Kilos> hi zaki
[14:57] <pavlushka> zaki: good luck on your Final exam, :)
[15:03] <Kilos> good luck zaki
[15:03] <Kilos> i wish hyou only complete success
[15:03] <zaki> thank you. :)  pavlushka Kilos
[15:10] <pavlushka> zaki: anytime, :)
[15:13] <Kilos> you guys are my family
[15:13] <Kilos> so of course i wish you only the best in everything
[15:14] <ahoneybun> hey pavlushka
[15:14] <Kilos> ohi ahoneybun
[15:15] <pavlushka> Kilos: I heard this line before, :p, in a song, "adele - someone like you"
[15:15] <Kilos> you are also becoming part of my family
[15:16] <pavlushka> QA ddg adele - someone like you
[15:16] <QA> pavlushka: *blink*
[15:16] <Kilos> after pk we wake up india
[15:16] <ahoneybun> hey Kilos
[15:16] <Kilos> QA isnt upgraded yet pavlushka
[15:16] <QA> Kilos: *blink*
[15:16]  * ahoneybun was sleeping
[15:17] <pavlushka> ahoneybun: what you dreamed about?
[15:17] <pavlushka> in th sleep, :p
[15:17] <Kilos> pavlushka you need to look at the bd wiki page sometime and we discuss what needs changing so it follows ubuntu path
[15:18] <pavlushka> Kilos: sure
[15:18] <Kilos> wikis are hard work for me thats why im collecting all you brainy peeps from all over
[15:19] <ahoneybun> mm idk pavlushka
[15:20] <Kilos> oh pavlushka
[15:20] <pavlushka> Kilos: you are doing the clever part, :p
[15:20] <Kilos> when you have time you can also translate for ahoneybun
[15:20] <Kilos> you can do indian i think
[15:21] <ahoneybun> mm?
[15:22] <Kilos> that thing zaki is gonna do the translation to bengali ahoneybun
[15:22] <Kilos> your script
[15:22] <ahoneybun> well this translation is nothing different then LP
[15:22] <ahoneybun> just .po files
[15:22] <Kilos> i can most likely get some guys to translate to african languages and french as well
[15:23] <ahoneybun> anything I get would be great
[15:24] <Kilos> give me the links or join us on #ubuntu-africa
[15:24] <Kilos> ill introduce you there
[15:25] <ahoneybun> tbh need to find a way to have them all on the one site
[15:25] <ahoneybun> but could still be a good idea to get them anyway
[15:42] <Kilos> hi dipraw
[15:42] <pavlushka> wb dipraw !
[15:43] <dipraw> hello Kilos
[15:43] <dipraw> hello bro pavlushka
[15:44] <pavlushka> whassup dipraw ! what about your cricket?
[15:45] <dipraw> yeah bro its going ok pavlushka
[15:45] <pavlushka> Kilos: remember dipraw  was there in my first Membership board, :)
[15:45] <Kilos> yes
[15:45] <Kilos> he can join in again
[15:45] <dipraw> yeah i was
[15:46] <dipraw> and messed up everything
[15:46] <dipraw> :(
[15:46] <Kilos> things look much better now
[15:46] <pavlushka> dipraw: nope you didn't
[15:46] <dipraw> so nice of u pavlushka
[15:47] <pavlushka> bbl, gotta run,:)
[15:47] <Kilos> nope dipraw he wasnt prepared properly but this time things are being done the right way
[15:48] <Kilos> and support will still be welcome
[15:48] <dipraw> thanx Kilos for backing me up!
[15:48] <dipraw> :)
[15:49] <Kilos> :D
[15:57] <dipraw> btw how's life?? Kilos
[15:57] <Kilos> ok ty young man and there by you?
[15:57] <Kilos> i fly on the 30th to my daughter in australia
[16:14] <dipraw> wow thats a great news
[16:14] <dipraw> u must be very happy
[16:17] <Kilos> yes i have never met her in person
[16:18] <Kilos> hehe
[16:18] <Kilos> but we chat online everyday
[16:35] <dipraw> your daughter and u never met??!!
[16:51] <Kilos> yes
[16:52] <Kilos> her mom and i had a short crazy relationship for three months then had a fight and split
[16:52] <Kilos> now we understand what young arrogant fools we were
[17:06] <ahoneybun> wow
[17:08] <pavlushka> Kilos: you have another blog other than this http://kilosubuntu.blogspot.com, if you please give us the ink, :)
[17:08] <Kilos> hmm...
[17:09] <Kilos> QA kilos.blog
[17:09] <QA> Kilos: kilos.blog is http://mileyssignificantblog.blogspot.com/
[17:09] <Kilos> the crazy name was my daughters idea
[17:09] <pavlushka> AudaciousTUX: you can even earn 10 rep by answering questions in askubuntu, :p
[17:10] <pavlushka> AudaciousTUX: and you were talking about some idea on BD website, :)
[17:11] <Kilos> oh yes
[17:11] <Kilos> i wanna see this site
[17:11] <pavlushka> dipraw: read it, http://mileyssignificantblog.blogspot.com/2015/01/the-pain-in-my-life_28.html
[17:11] <Kilos> just make it basic so its fast with all the important info
[17:25] <AudaciousTUX> za team have any blog site??
[17:25] <Kilos> hmm...
[17:25] <AudaciousTUX> link?
[17:26] <Kilos> im trying to remember
[17:26] <AudaciousTUX> :v
[17:26] <Kilos> i dont think we have one blog
[17:26] <AudaciousTUX> then we can create multilingual blog site with wordpress easily....
[17:27] <Kilos> i started some years bag with wordpress but its for clever guys
[17:27] <zaki> Kilos: https://nlsthzn.com/category/ubuntu-za/
[17:27] <Kilos> you guys must try follow the planet blogs
[17:28] <pavlushka> Kilos:  you mean planetubuntu ?
[17:28] <Kilos> yes
[17:28] <pavlushka> ok
[17:28] <AudaciousTUX> i've tested... and it won't be too much complicated.... we can do this ^_^
[17:28] <Kilos> there should be some old za stuff there
[17:29] <Kilos> think of a good name for a world wide blogsite that can involve all ubuntu users
[17:30] <Kilos> maybe we can even translate other languages to english because thats the world language
[17:32] <AudaciousTUX> hmm
[17:32] <AudaciousTUX> i have to modify my theme a little bit.... but have to wait till my exam finish
[17:34] <Kilos> no rush lad, as long as we keep moving forward
[17:34] <AudaciousTUX> :)
[17:35] <Kilos> my dream is to see all locos return to their former glory and motivation
[17:35] <AudaciousTUX> \o/
[17:36] <pavlushka> AudaciousTUX: FB তে HM Murshed কে help করেন, আমি তে avro-phonetic use করি না!
[17:36] <Kilos> then i will be satisfied with my contribution to ubuntu
[17:37] <AudaciousTUX> অই বেক্তি এক্টু নিজে নিজে খুইজা খুইজা কিছু করতে পারেনা... হেল্প করাও বোরিং... :3
[17:37] <pavlushka> AudaciousTUX: find a xubuntu user who uses avro-phonetic
[17:38] <pavlushka> AudaciousTUX: he is weak in English and just recently moved from windows, we should indulge him a bit, :p
[17:38] <Kilos> lead him gently guys
[17:39] <Kilos> gibberish is fine here
[17:39] <Kilos> hehe
[17:39] <AudaciousTUX> :p
[17:55] <pavlushka> installed avro, now will reboot, brb
[18:24] <Kilos> oh my
[18:24] <Kilos> zakklined
[18:25] <Kilos> zaki klined
[18:25] <Kilos> what did he do wrong
[18:25] <Kilos> now he will have to get freenode to fix it
[18:40] <Kilos> wb zaki
[18:41] <Kilos> why were you klined
[18:41] <Kilos> zaki (~zaki@unaffiliated/zaki) has left this server (K-Lined).
[18:56] <zaki> don't know, w8, checking
[18:56] <Kilos> i asked at #freenode
[18:56] <Kilos> no reply yet
[18:58] <zaki> i was desconnect automatically and can't connect for sometime while my internet connection is ok.
[18:58] <Kilos> go to #freenode and wait there til eir gives you voice then ask
[18:59] <Kilos> sometimes you have to wait a while
[18:59] <zaki> oky
[18:59] <Kilos> i asked eir in pm but no reply yet
[19:22] <Kilos> night bd peeps
[19:43] <zaki> wb eprbata
[19:45] <zaki> pavlushka:
[19:45] <zaki> how are you?
[19:46] <pavlushka> not good, I dont know why I am banned.
[19:46] <zaki> freenode is under attack
[19:47] <zaki> i was k-lined for sometime
[19:47] <zaki> wait , it will be lifted after everything oky, i think.
[19:49] <zaki> pavlushka: i talked about it at #freenode
[19:57] <pavlushka> zaki: did you send them mail on<EMAIL_ADDRESS>to lift the ban?
[19:57] <zaki> lifted automatically.
[19:58] <zaki> now i'm connected from the same ip
[20:10] <zaki> pavlushka: good night
[20:10] <pavlushka> good night zaki
[20:11] <zaki> have a sweet dream. :p


[03:16] <raub> On http://packaging.ubuntu.com/html/fixing-a-bug.html#work-on-a-fix, how do you use edit-patch to edit a file and create appropriate patch?
[04:04] <raub> openssh-server and -client are packages derived from the ssh source. If I wanted to create a ppa for, say openssh-client, how would I do that starting from the ssh source package?
[04:06] <RAOF> raub: Take the ssh source package, upload it to your PPA.
[04:33] <raub> RAOF: the entire thing? What if I want to use the ppa to get just the client?
[04:34] <RAOF> raub: You could change the ssh source package to not build the -server package (that'd be editing debian/control)
[04:36] <Unit193> Or d/rules.
[07:17] <dholbach> good morning
[07:28] <highvoltage> o/
[13:43] <Unit193> asomething: Howdy.  Still interested in Xubuntu some, or was that someone else?
[13:44] <asomething> Must be someone else... I've sponsored a few Xubuntu related packages in the past, but I don't run it myself
[13:47] <Unit193> Ah, I'll blame bad memory.  Thanks.
[15:06] <raub> For those who answered my questions yesterday, I need a bit of help putting sudo-ldap in PPA
[15:06] <raub> I understand (sort of) how to do the deed with the original package, sudo, but still do not understand for the derivative work 9sudo-ldap)
[15:10] <raub> RAOF said to edit the debian/control file, but if there is a sudo-ldap package already, shouldn't it have that done?
[21:15] <sn33zy> im looking on the website for ways to contribute but I do not know where to start.  can someone point me somewhere to start?
[21:30] <Noskcaj> sn33zy, What would you like to do?
[21:30] <Noskcaj> And do you know any programming languages?
[21:31] <sn33zy> I know Java and C++... Im kindof bored right now and was curious if anyone wanted help with something (trying to see if I can help out)
[21:33] <Noskcaj> bugs.launchpad.net/ubuntu has a list of all the bugs that need fixing
[21:33] <Noskcaj> See if a program you use has any bugs
[21:33] <Noskcaj> Also, what DE do you use? (gnome, xfce, etc.
[21:34] <sn33zy> Unity
[21:34] <Noskcaj> #ubuntu-unity is it's channel, although it might not be the best thing to start on
[22:10] <sn33zy> Noskcaj, i dont know enough to fix the bugs that I am finding.... is there a channel i can find any devs that I could offer my assistance to?
[22:10] <Noskcaj> #ubuntu-devel
[22:10] <Noskcaj> maybe #ubuntu-bugs
[22:10] <Noskcaj> We also have a testing team in #ubuntu-quality
[22:11] <Noskcaj> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=bitesize should have some easier to fix bugs
[22:16] <ScottK> sn33zy: If we knew more specifically what bugs, we could probably provide better advice about where to find help.
[22:23] <sn33zy> ok... heres a bitesize bug... https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/723432 .... ScottK  but I really dont know where to start...
[22:25] <ScottK> That's probably not a good choice.  It requires knowing a fair amount about how translations work in Ubuntu (which is not like anything else on the planet).
[22:25] <ScottK> (unless you really want to learn about how translations work)_
[22:26] <ScottK> If so, dpm, who does not seem to be online right now, can probably point you in the right direction.
[22:32] <sn33zy> ScottK, okay so lets say I want to checkout code.... is the best way to do it is through apt-get source <packagename> ?
[22:33] <sn33zy> because i know another is through git...
[22:35] <rbasak> pull-lp-source <packagename> is better. It'll give you the latest development version, which might not necessarily be the same as the version you have available to apt on your system.
[22:50] <ScottK> Right.  I generally point the deb-src line in my sources.list to the development release to solve that problem, but pull-lp-source does it as well.
[23:14] <sn33zy> ScottK, grr.... downloaded the source code for a package but the code is over my head lol


[07:57] <mpt> Femma1, if bug 1377145 is being worked on by Grazina, maybe it should be reassigned to her?
[07:58] <Femma1> mpt:  done


[11:44] <adrien> hi, could someone retry seqkit against openssl https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=seqkit&trigger=openssl%2F3.0.7-1ubuntu1 ? (seqkit doesn't seem very reliable overall)
[11:44] <adrien> thanks :)
[11:52] <ginggs> .
[13:46] <juliank> rbasak: What happened to the whole git-ubuntu upload workflow, I remember doing sth like dpkg-buildpackage $(git ubuntu push-for-upload) <your usual flags here> months ago and that worked but what do I do now?
[13:47] <juliank> I want to upload https://code.launchpad.net/~juliank/ubuntu/+source/command-not-found/+git/command-not-found/+ref/ubuntu/devel
[13:48] <juliank> $ git ubuntu tag
[13:48] <juliank> gitubuntu.git_repository.ChangelogError: Old (23.04.0) and new (22.04.0) changelog values do not agree
[13:49] <juliank> I see git-ubuntu has not been updated in over 2 years on stable channel
[13:50] <rbasak> juliank: please use the edge channel
[13:50] <rbasak> I need to do a stable release
[13:51] <rbasak> Oh, and it's prepare-upload now, not push-for-upload
[13:51] <rbasak> dpkg-buildpackage $(git ubuntu prepare-upload args) ...
[13:51] <rbasak> It's not in stable because the CLI for that is still experimental.
[13:51] <rbasak> I need to sort out some edge case failures
[13:51] <rbasak> To handle them more gracefully
[14:17] <hallyn> hm, so I don't see pitti here ...  stgraber due to the change in lxc, where it has to use libsystemd to use the dbus api to create scopes for unpriv containers, projects which statically link against lxc now also need to statically link against libsystemd, hence
[14:17] <hallyn> https://pastebin.ubuntu.com/p/qg8BW38Y9M/
[14:18] <hallyn> Do you think there's a chance of that being cceptable?  stacker (github.com/project-stacker/stacker) for instance needs it to statically link the lxc-wrapper program which it runs in possibly empty containers to do things.
[14:18] <hallyn> It's systemd's own fault for making it impossible to cleanly create scopes without their library/api any more :)
[14:20] <hallyn> meanwhile - zhsj bluca - thanks, looks like the added deps did help golang-gopkg-lxc-go-lxc.v2 to pass - https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#lxc
[14:20] <juliank> it's been a couple years since pitti has been around in ubuntu lands :D
[14:20] <juliank> it's possible he didn't even migrate from freenode
[14:21] <hallyn> juliank: i saw him *somewhere* very recently, but maybe that was mastodon.
[14:21] <hallyn> anyway i guess i'll push this to a ppa for now to unblock.
[14:24] <hallyn> really, systemd could probably easily publish a separate libsystemd-dbus.so to avoid the rest of libsystemd being static, but that's a lot more work on the front end.
[15:06] <ogayot> hi, could somebody trigger an autopkgtest against my PPA please? I believe the link should be https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=python-exchangelib&ppa=ogayot/lunar-proposed&trigger=python-exchangelib/4.9.0-1ubuntu1%7Eppa1 Thanks!
[16:18] <tsimonq2> ogayot: Done.
[16:19] <ogayot> tsimonq2: appreciated!
[16:19] <tsimonq2> No worries :)
[19:43] <arraybolt3> OK, I'm working on an XScreenSaver regression, and need some advice.
[19:44] <arraybolt3> In versions of Ubuntu before Kinetic, XScreenSaver just worked with or without a default config file at /usr/lib/X11/app-defaults/XScreenSaver. Starting with Kinetic, the included version of XScreenSaver requires a file there in order to work properly, and that file must be configured right.
[19:45] <arraybolt3> In Lubuntu Lunar, we have a file there that works perfectly. However, the default xscreensaver package does not ship with that file, thus breaking XScreenSaver for all flavors on Kinetic, and all flavors except Lubuntu in Lunar.
[19:45] <arraybolt3> To solve the problem in Lubuntu, I just have to backport the right config file. However, we also need to start shipping that file on all other flavors, preferably with a sane default config to make all features work properly while still being distro-agnostic.
[19:45] <arraybolt3> *flavor-agnostic, I mean
[19:46] <arraybolt3> My current plan is to make a new package, xscreensaver-config, that holds this file. xscreensaver will then depend on either xscreensaver-config OR lubuntu-default-settings (which ships the same file).
[19:47] <arraybolt3> That way, when a user installs xscreensaver on a non-Lubuntu flavor, it will normally pull in xscreensaver-config, but on Lubuntu, which already ships with xscreensaver and lubuntu-default-settings, all dependencies will be satisfied.
[19:47] <arraybolt3> Obviously I will be putting the needed Conflicts/Replaces between both the new xscreensaver-config and the existing lubuntu-default-settings.
[19:47] <arraybolt3> Is this an acceptable solution, or does someone else here have a better idea on how to rectify this?
[19:48] <arraybolt3> (Currently the regression breaks the Preview button in XScreenSaver, and I believe it may also break various other functionality.)
[19:49] <arraybolt3> (Also there is not a bug report for this yet, I will be filing one most likely in the near future.)
[20:26] <jbicha> bryceh: are you planning to do the php 8.2 transition for lunar? https://people.canonical.com/~ubuntu-archive/transitions/html/php8.2.html
[20:30] <athos> jbicha: no, we are pushing this one to the next cycle
[20:34] <jbicha> ok, thanks
[21:56] <arraybolt3> tsimonq2: ping wrt above XScreenSaver stuff, would like an opinion on the fix I'm intending to implement
[22:32] <arraybolt3> Might be worth trying to make that happen in Debian first?


[00:01] <msx> hello everywhere, my sincere congratz for the awesome release of 14.04 LTS, amazing indeed. And it's regarding something I found you guys did there why I am here: I run Xubuntu on my laptop, a shi!@$%$% HP with hybrid GPU Intel/ATi, with Xubuntu vgaswitcheroo works great meaning the DIS GPU (ATi) is turned off by default.
[00:03] <msx> Now, when running Ubuntu 14.04 on the same laptop (dual boot) I can't make it turn off the DIS GPU. Could you tell me what's the magic you did to be able to turn off the DIS GPU!?
[00:03] <msx> Or point me to any resource I can read, oc :)
[00:03] <msx> s/everywhere/everyone/g
[00:03] <msx> LOL
[02:25] <int0x666> hello
[02:26] <int0x666> i'm trying to write a kernel mode driver
[02:26] <int0x666> for xubuntu x64
[02:26] <int0x666> my installation doesn't seem to have come with the source?
[02:28] <msx> int0x666: hi, do an apt search linux- to list the name of the package containing the source for your image
[02:29] <int0x666> :0
[02:29] <int0x666> it returned an enormous number of results
[02:30] <msx> let me check
[02:31] <msx> yeah, i really like apt but the way it shows search results is somewaht uncanny
[02:31] <msx> $ aptitude search linux- | grep source
[02:31] <msx> int0x666: ^   ^
[02:32] <msx> provided you have aptitude installed, oc
[02:32] <int0x666> installing it atm
[02:33] <int0x666> hey cool
[02:33] <int0x666> so uh
[02:33] <msx> you can use apt too, but i think aptitude shows results in a tidier way...
[02:33] <int0x666> does this mean i have the source on my hard drive, or is it telling me the name of the package containing the source that i need to download for my version?
[02:34] <int0x666> i've only been a user of xubuntu for two months or so
[02:35] <msx> int0x666: well, debian package management is a bit tricky, at least for me since it's built of a lot of different components being the most notable dpkg and the apt-get/apt/aptitude combo
[02:35] <msx> int0x666: you can check if a package is installed by checking the letter right to the name of the package, like:
[02:35] <msx> p   linux-source-3.13.0             - Linux kernel source for version 3.13.0 wit
[02:35] <int0x666> p means i have it?
[02:35] <msx> the installed packages will show an i instead a p
[02:36] <int0x666> p   linux-source                    - Linux kernel source with Ubuntu patches
[02:36] <int0x666> v   linux-source-3                  -
[02:36] <int0x666> p   linux-source-3.13.0             - Linux kernel source for version
[02:36] <msx> int0x666:  ^   ^
[02:36] <int0x666> so which am i looking for?
[02:36] <msx> int0x666: exactly.
[02:36] <msx> And...
[02:36] <msx> another way to look for installed packages: $ dpkg -l | grep {pattern}
[02:37] <msx> $ dpkg -l | grep linux-
[02:37] <msx> that will answer with the installed packages matching that pattern in their name
[02:37] <msx> dpkg --help for the whole switch list
[02:38] <int0x666> while that does sound handy
[02:38] <int0x666> i would like to know how i should determine which of the three packages it returned should be installed
[02:40] <msx> int0x666: there's not a clear way in debian i'm afraid :P
[02:40] <msx> you have to know what you're looking for
[02:40] <msx> in this particular case I think
[02:40] <msx> linux-source-3.13.0 will do it
[02:40] <int0x666> yeah
[02:40] <int0x666> i just installed that one
[02:41] <int0x666> then i started prying the keys off of my keyboard
[02:41] <int0x666> and damn
[02:41] <int0x666> this is a new keyboard
[02:41] <int0x666> got it about three months ago
[02:41] <int0x666> and there's already filth caked inside of it
[02:42] <int0x666> thank you so much for the help btw
[02:43] <msx> np
[02:43] <msx> i'm enjoying a new kbd too, a logitech
[02:43] <int0x666> is it a mechanical keyboard
[02:43] <msx> a baseline model, but rocks :D will try to keep it in conditions!
[02:43] <msx> awesome!!!
[02:43] <msx> mech kbds are bomb, i'm looking to buy one
[02:44] <msx> *the bomb
[02:44] <int0x666> i <3 it
[02:44] <msx> i can imagine, absolutely
[02:58] <int0x666> hmm
[02:58] <int0x666> yeah i'm giving up
[02:58] <int0x666> thanks for the help though!
[06:58] <elfy> Noskcaj: I see the same thing - gmb and parole both stop audio on seek
[07:22] <Noskcaj> elfy, thanks for confirming.
[07:23] <Noskcaj> I wonder if the issue is in precise and trusty.
[07:26] <elfy> not from memory it's not
[07:27] <elfy> I found it in clementine first - but that appears to be ok now
[07:31] <ochosi> from what i can tell, it's a bug in gstreamer
[07:32] <ochosi> the players do what they do with every other file
[07:32] <ochosi> but seemingly "gst + ogg + seeking = fail"
[07:32] <elfy> I'd assume so ochosi
[07:32] <elfy> gst + whatever + seeking = fail
[07:33] <ochosi> hm, that sounds bad
[07:33] <elfy> actually
[07:33] <ochosi> yeah, i think gst1.0 has gotten worse in that respect
[07:33] <elfy> flac is fine whatever that uses
[07:33] <elfy> mp3 fails
[07:34] <ochosi> well flac is quasi uncompressed
[07:34] <ochosi> anyway, it seems that the issue is worse with gst1.0
[07:34] <elfy> yea
[07:34] <ochosi> (which is what those players are using)
[07:34] <elfy> anwyay - work calls
[07:34] <ochosi> with 0.10 i don't remember big problems with seeking
[07:34] <ochosi> sure, hf elfy
[07:34] <ochosi> (same here in fact)
[07:34] <ochosi> bbl
[07:34] <elfy> I'll try and get those SRU proposes issues onto laptop with trusty this afternoon/evening
[07:45] <ochosi> thanks
[07:45] <ochosi> btw, this one will also need to be verified very soon: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1309744
[07:46] <ochosi> it should land in trusty-proposed sometime today
[07:46] <ochosi> oh and while you're at it, there's also xubuntu-default-settings in trusty-proposed that needs verifying
[07:46] <ochosi> https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1303736
[07:47] <ochosi> see https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1303736/comments/146
[09:08] <forestpiskie> thanks pleia2 :)
[09:09] <pleia2> forestpiskie: sure thing :)
[09:49] <ochosi> weee, xdg-utils is uploaded and accepted in trusty-proposed
[09:51] <slickymasterWork> \o/
[09:51] <slickymasterWork> morning ochosi
[09:51] <ochosi> morning slickymasterWork
[09:51] <ochosi> it's so weird though, first it takes ages and suddenly everything happens lightning-fast
[09:51] <ochosi> from Laney uploading it to cjwatson approving it, that was less than 15mins
[09:51] <slickymasterWork> ochosi care to take a look at http://pad.ubuntu.com/AO7hLk0hFH and see what have I might forget?
[09:52] <ochosi> hm well, the removal of gthumb is highly optional, i
[09:52] <ochosi> 'd say
[09:53] <ochosi> the other things are good, but they need to be described step-by-step
[09:53] <ochosi> especially the things that are more complex, whisker and indicators
[09:53] <slickymasterWork> well the idea behind its removal was that it wasn't necessary, right?
[09:54] <ochosi> yeah, we can mention that we removed it and why (duplication of functionality)
[09:54] <slickymasterWork> yeah, I know. That's just the list that I wnated to be sure if there's nothing missing
[09:55] <ochosi> ok, great
[09:55] <slickymasterWork> if you remember something else please add it to that list ochosi
[09:55] <ochosi> will do
[09:55] <ochosi> has elfy had a look at that yet?
[09:55] <ochosi> i presume he has a bit of experience with that
[09:56] <slickymasterWork> no, I haven't manage to get in touch with him yet
[09:56] <ochosi> ah right
[09:56] <ochosi> forestpiskie: ^ :)
[09:56] <slickymasterWork> :) I know
[10:20] <bluesabre> good job ochosi
[10:20] <bluesabre> :D
[10:21] <ochosi> thanks
[10:21] <ochosi> let's move along with the verification
[10:21] <ochosi> good news is we can verify the things ourselves
[10:22] <ochosi> (which was the context in which i mis-posted that in #shimmer)
[10:51] <bluesabre> cool
[10:51]  * bluesabre will be working on merge requests and reviews this weekend
[11:06] <bluesabre> Noskcaj: I see xfce4-session 4.10.1-7 on debian now, should we merge that instead?
[11:26] <slickymasterWork> thanks knome ;)
[11:59] <elfy> elfy has no idea what you're talking about ...
[12:06] <elfy> ochosi bluesabre - are all the SRU updates now available in -proposed for trusty now?
[12:31] <bluesabre> elfy: yes
[12:32] <bluesabre> menulibre lightdm-gtk-greeter xubuntu-default-settings xdg-utils
[13:45] <slickymasterWork> elfy, we were talking about http://irclogs.ubuntu.com/2014/07/15/%23xubuntu-devel.html#t10:44
[13:46] <slickymasterWork> forestpiskie: ^^
[13:50] <jjfrv8> ochosi, I verified the xdg-utils fix.
[14:52] <ochosi> jjfrv8: thanks a bunch!
[15:00] <ochosi> elfy, jjfrv8: folks, we really need someone to confirm the x-d-s patch for us
[15:00] <ochosi> the problem is there are still "confused" users who have mostly other problems with suspending that keep poking this bugreport
[15:00] <ochosi> they set it to verification-failed
[15:00] <ochosi> which is plain wrong
[15:01] <ochosi> the patch is a no-brainer and only completes an existing sru
[15:27] <jjfrv8> ochosi, I didn't try the x-d-s one because I'm laptop-less atm. Can one simulate it on a desktop?
[15:31] <jjfrv8> I suspend my regular Trusty desktop all the time and have never had the problem.
[15:34] <jjfrv8> Just saw bluesabre's comment on the bug report and he says it only applies to laptops, so I guess I can't help right now.
[15:38] <ochosi> yup, no worries
[15:39] <ochosi> if you don't have a laptop, there's nothing you can do
[16:04] <slickymasterWork> forestpiskie, ochosi, knome, http://pad.ubuntu.com/AO7hLk0hFH
[16:05] <slickymasterWork> regarding indicators in particular I would like your views on it, as I'm not 100% certain that my approach is completely correct
[16:06] <knome> oh poo
[16:06] <knome> forgetting a site in the firefox history makes it also forget the creds
[16:07] <slickymasterWork> I noticed that knome because in Chrome happens the same thing
[16:08] <knome> time to dig back up some files from backups then, i guess
[16:15] <knome> slickymasterWork, no, i think it's correct without an "an"
[16:15] <knome> i'm referring to screen locking in general
[16:16] <slickymasterWork> but ins't 'an' a general article ?
[16:17] <knome> sure, but i don't think it's used in this situation
[16:17] <knome> elfy!
[16:17] <slickymasterWork> and I'm under the impression that is generally used before words beginning with a vowel sound
[16:17] <knome> well that's another way to put it
[16:17] <knome> (see the pad)
[16:18] <slickymasterWork> the use of the action verb "...r brings you,..." is what makes me think of the need of that article
[16:19] <knome> well you don't say
[16:19] <knome> "i need a freedom" either
[16:19] <slickymasterWork> whatie?!
[16:19] <slickymasterWork> that's completely different
[16:20] <knome> (unless you need a specific freedom)
[16:20] <knome> not really...
[16:20] <knome> improved screen locking is not a single thing
[16:20] <knome> it's a bigger entity
[16:20] <slickymasterWork> you're speaking about a concept (even though I know you could use your argument against me) ;P
[16:21] <slickymasterWork> freedom isn't tangible, screen locking is
[16:21] <knome> lol
[16:21] <knome> well let's use another example
[16:21] <knome> you don't say
[16:21] <knome> "i need screen saving"
[16:21] <knome> err
[16:22] <knome> i mean,
[16:22] <knome> you don't say
[16:22] <knome> "i need a screen saving"
[16:22] <knome> you say "i need a screen saver"
[16:22] <slickymasterWork> notice the difference between the verb forms in those setences
[16:22] <knome> see the pad now
[16:22] <knome> now it makes sense to have the "an"
[16:22] <knome> but i think it's clumsy to talk about a "screen locker"
[16:23] <slickymasterWork> i like it better like it's now
[16:23] <knome> yep, but if we made it "screen locking", then we'd have to drop the "an" ;)
[16:24] <slickymasterWork> lol, I won't argue with the grammar and syntax police :P
[16:25] <knome> i'm not perfect in grammar, but what you proposed just didn't sound right
[16:25] <slickymasterWork> do you think of anything else that should be added to that list knome?
[16:26] <knome> do we want to talk about how to get the default 14.04 panel layout etc?
[16:26] <knome> or in other words, removing your current custom user-specific config
[16:27] <slickymasterWork> well the idea behind this list was the things needed to do after that upgrade, do you see that as a need?
[16:28] <knome> some people might want that
[16:28] <knome> it's not something you *need* to do
[16:28] <slickymasterWork> and it was meant to be just a quick list
[16:28] <knome> another question is do we poke people at mugshot
[16:29] <slickymasterWork> I don't think that falls under it, mainly because we're speaking about a new app that isn't replacing anything
[16:29] <knome> well you asked if i had something else in mind :P
[16:29] <knome> sure
[16:29] <slickymasterWork> and mugshot was already covered in the release notes
[16:30] <knome> i know
[16:30] <slickymasterWork> I'll take it as a no, then
[16:30] <elfy> knome: what?
[16:31] <slickymasterWork> elfy, we were summoned to solve a grammar dispute between me and knome ;)
[16:31] <elfy> oh ok
[16:31] <slickymasterWork> see http://pad.ubuntu.com/AO7hLk0hFH please
[16:31] <elfy> not now slickymasterWork - might get to look tomorrow at some point
[16:32] <ssarah> hei guys i'm new. kind of a jack of all trades. you got a little bit of grunt work for me?
[16:32] <slickymasterWork> so tomorrow while you're at it, see also today's logs to see what the dispute was about
[16:32] <elfy> if
[16:32] <elfy> I'm really busy with other stuff atm
[16:33] <slickymasterWork> no problem ;)
[16:39] <ssarah> back :)
[16:39] <slickymasterWork> ssarah: see http://xubuntu.org/contribute/
[16:40] <ssarah> aight
[17:24] <ochosi> ssarah: and if you have questions, you can obviously always ask here
[17:37] <ochosi> knome: fwiw, ppl seem to be still digging the 14.04 wallpaper a lot (seen it on many screenshots on g+), so prepare to create something equally nice for 14.10 ;)
[17:38] <ochosi> (or a variation of the 14.04)
[17:55] <ssarah> hey guys
[17:55] <ssarah> im working on a script for a new version of ubuntu for the government
[17:56] <ssarah> right now it's a couple of bash scripts that remove and put in stuff
[17:56] <ssarah> it's pretty ugly
[17:56] <ssarah> any advices on how i should do it / someone to ask to?
[17:57] <ssarah> well, not just this one, i have to make 3 or 4 more "distros"
[18:19] <Unit193> I have a whole system with different modules, but it's not the most pretty either.  Would you be looking to Do It Properly™?
[18:36] <Unit193> "Iain Lane (laney) has assigned this bug to you for xdg-utils in Ubuntu Trusty:" - Shiny, it got counted as mine and assigned to me. :3
[18:45] <ochosi> heh, a stroke of luck i guess ;)
[18:45] <ochosi> well anyway, thanks for the debdiff Unit193
[18:46] <Unit193> Got it in updates too.
[18:47] <ochosi> fool me once, try again, fool me twice...
[18:47] <ochosi> (or however gwb said that)
[18:48] <Unit193> xubutrello: card 78 move to 14.04.1 Done
[18:48] <xubutrello> Couldn't find any list named: "14". Aborting.
[21:01] <Noskcaj> bluesabre, Do you not have upload rights for xfce4-whiskermenu-plugin?
[21:02] <Noskcaj> And could you please look at bug 1334185
[22:47] <ochosi> ahoi everyone


[00:06] <chrisccoulson> congrats charles :)
[02:59] <nigel_nb> dtchen: how do i know from Card1.Amixer.values.txt whether sound is mute?
[03:03] <dtchen> nigel_nb: you read the mute/cap field
[03:03] <nigel_nb> thanks  :)
[03:03] <dtchen> I hope that isn't too vague
[03:03] <dtchen> I can't tell these days whether I'm assuming too much, since I've been at this stuff over a decade
[03:05] <nigel_nb> that one's not my cup of tea
[03:05] <dtchen> which "one"?
[03:05] <nigel_nb> the report is that reduction in volume not permanent in pulseaudio
[03:05] <nigel_nb> bug 491704
[03:05] <ubot4> Launchpad bug 491704 in pulseaudio "Sound volume is max on startup even when set to less " [Undecided,New] https://launchpad.net/bugs/491704
[03:06] <dtchen> I think I've just asked for more info
[03:06] <dtchen> all bugs are the same -- not enough info
[03:06] <dtchen> that means we need to extend the apport hook, probably
[03:07] <nigel_nb> this one had info, you asked for something about ~/.asoundrc*
[03:07] <nigel_nb> :)
[03:07] <nigel_nb> u added just after I started seeing the page
[03:07] <dtchen> yes, because either/both /etc/asound.conf or/and ~/.asoundrc will preempt pulse
[03:08] <dtchen> this is due to the compatibility added back to retain ALSA precedence
[03:08] <nigel_nb> oh
[03:08] <nigel_nb> sound is still greek and latin to me :(
[03:08] <dtchen> I could remove that compatibility and break the expected, historical behavior of alsa-lib
[03:08] <dtchen> or I could retain that compatibility and face these sorts of bugs
[03:09] <nigel_nb> but breaking the historical behavior means a lot of people become lost?
[03:09] <dtchen> heh, this was an intrepid SRU
[03:09] <nigel_nb> as to how to fix and stuff like that
[03:09] <dtchen> nigel_nb: it would break people's installs that rely solely on ALSA (without PA)
[03:09] <hggdh> hey micahg, what is the PPA for the mozillateam?
[03:09] <micahg> hggdh: which one?
[03:10] <nigel_nb> dtchen: oh :)
[03:10] <hggdh> for thnderbird?
[03:10] <micahg> https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[03:10] <dtchen> again, if we didn't have this horrendous split between Ubuntu and Xubuntu/Kubuntu, it would be easier
[03:10] <micahg> hggdh: for TB3?
[03:10] <micahg> hggdh: we only have dailies right now
[03:10] <hggdh> dailies would be good ;-)
[03:11] <micahg> hggdh: I built the just before release version in my ppa if you want
[03:12] <hggdh> cool -- but fta published today a new daily also. Same?
[03:12] <micahg> hggdh: dailies have been tracking 3.0.1 for a couple weeks
[03:13] <micahg> this was the last RC that I just built
[03:13] <hggdh> ppa:micahg/ppa?
[03:13] <micahg> hggdh: no, ppa:micahg/mozilla-beta
[03:14] <hggdh> thanks
[03:14] <nigel_nb> hggdh: fixed my first bug :)
[03:15] <hggdh> great nigel_nb !
[03:15] <nigel_nb> of course, I got help, but it was fun :) I learned how to deal with that one
[03:16]  * micahg realizes that more people are going to be asking about TB3 soon :)
[03:16]  * hggdh bets on it
[03:16] <micahg> hggdh: you were number 3 I think
[03:16] <hggdh> :-)
[03:16] <nigel_nb> I saw a couple of people talking about it
[03:17] <hggdh> been thinking about it for a while (I mean TB itself); when Evo purged all my accounts from gconf I decided it was time to try
[03:17] <hggdh> now, I am curious if TB3 will be better than TB2
[03:18] <hggdh> nigel_nb: which bug?
[03:20] <nigel_nb> bug 351509
[03:20] <ubot4> Launchpad bug 351509 in vm-builder "vmbuilder should provide an option to choose which libvirt virtual network" [Wishlist,Fix released] https://launchpad.net/bugs/351509
[03:20] <nigel_nb> I just did it
[03:21] <nigel_nb> maco___ helped me with it (actually gave me step-by-step instructions)
[03:22] <nigel_nb> but anything similar I can handle it I think :)
[03:23] <hggdh> nigel_nb: and you told me you did not do python ;-)
[03:24] <nigel_nb> hggdh: I didnt code
[03:24] <nigel_nb> there was a diff attached
[03:24] <nigel_nb> I got it packaged
[03:24] <hggdh> ah, OK.
[03:24] <nigel_nb> it was a low-hanging fruit :)
[03:24] <nigel_nb> and I plucked it :P
[03:25] <hggdh> nevertheless -- great work! first ever bug resolved, and getting also a debdiff accepted!
[03:25] <hggdh> (it took me 2 years to propose my first debdiff)
[03:25] <nigel_nb> oh
[03:26] <hggdh> well, to tell the truth, I did not have the time to invest then. But still
[03:26] <hggdh> hell, I do not have the time now, I should be getting ready to sleep!
[03:26] <nigel_nb> hehe, then go to bed :)
[03:27] <hggdh> heh. not yet, not yet... when I am in a hotel, I get insomnia
[03:29] <nigel_nb> hotel, wassup?
[03:29] <nigel_nb> work?
[03:30] <hggdh> yes. One *has* to work.
[03:30] <hggdh> and, as luck would have it, pretty much all my contracts are anywhere but home
[03:31] <hggdh> micahg: TB3.1 looks interesting. Really
[03:31] <micahg> I haven't tried 3.1 yet
[03:32] <nigel_nb> hggdh: ah.  Been busy the whole day with User Day stuff
[03:32] <hggdh> micahg, I am not sure this is what you had in your PPA, I just grabbed the highest version I found on synaptic
[03:33] <micahg> hggdh: you must have had the mozilla daily ppa enabled
[03:47] <shengie> Ubuntu rdesktop is buggy for me.  There's a patch that whacks the keyboard in ubuntu, not accompanied with rdesktop.sourceforge.net
[03:47] <shengie> I reported a bug once (I thought) but no resolution.
[03:48] <micahg> shengie: bug #?
[03:48] <shengie> Lemme search...
[03:51] <shengie> argh, I don't see one I submitted.
[03:51] <shengie> There are similar bugs reported/open
[03:52] <shengie> maybe I didn't report one, because I needed a fix, which entailed compiling rdesktop.sourceforge.net
[03:53] <malev> hi, I'm new at the team bugsquad! And I'm reading the documentation in the wiki. Where can I see at the bugs lists?
[03:53] <shengie> There's a patch being applied by Ubuntu which breaks caps-lock and the numberpad.
[03:54] <micahg> shengie: well, you can file a bug and submit a patch to fix the patch or a replacement for it
[03:56] <shengie> Actually, I need the patch ubuntu applies (for who knows what reason) to be removed.
[03:56] <shengie> from the rdesktop code.
[03:57] <shengie> That's why I'm here, I don't know how to go about requesting it, but I suppose a bug-report is a good place to start.
[03:57] <shengie> Thanks
[03:58] <micahg> shengie: yes, file a bug, explain which patch is problematic
[03:58] <micahg> shengie: ubuntu-bug rdesktop
[03:58] <hggdh> malev: did you read http://wiki.ubuntu.com/HelpingWithBugs ?
[04:03] <malev> hggdh, yes, i read that
[04:03] <malev> I also read the faq and a class from pedro
[04:03] <malev> and some other things too :D
[04:04] <hggdh> malev: OK. So, how can I help you?
[04:05] <malev> hggdh, i wanted to know where can i found the list of bugs, you know, to start checking then
[04:07] <hggdh> malev: on bugs.launchpad.net -- try https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&search=Search+Bug+Reports&field.scope=project&field.scope.target=ubuntu
[04:08] <hggdh> any bug with status NEW, or (perhaps) INCOMPLETE, is usually fair game
[04:08] <malev> excelent! thanks
[04:08] <malev> when i find something new, i'm gonna come to ask here :D
[04:08] <hggdh> malev: if you have doubts on what do to, please ask
[04:09] <malev> hggdh, i will! don't worry
[04:22] <hggdh> well, this is it for tonight. G'night all
[08:02] <micahg> mr_pouit: do you have a bug # for the battery issue?
[08:05] <mr_pouit> micahg: no, I just noticed & fixed it when merging from debian testing in lucid.
[08:05] <micahg> ok, if you want, I can make the patch
[08:05] <mr_pouit> to sum up: battery notifications lack an icon on karmic
[08:07] <mr_pouit> if you want to update your debdiff, just take the patch xubuntu-notification-something (don't remember the exact name) from lucid.
[08:08] <micahg> ok, I'll build a test package and test in karmic before updating
[08:09] <mr_pouit> nice, thanks.
[08:14] <micahg> mr_pouit: is the test case in each bug, or all in one?
[08:21] <mr_pouit> for the missing icons? Usually, it's better with one issue per bug.
[08:21] <micahg> ok, so the debdiff goes in one, but the test case in each bug separately
[08:22] <micahg> ugh, this should be in -motu I think...
[08:24] <mr_pouit> ah, nevermind
[08:24] <mr_pouit> yeah, it's ok
[08:25] <micahg> ok
[08:49] <mr_pouit> micahg: thanks for the test case. Isn't "4.5. restart xfce4-power-manager" needed?
[08:49] <micahg> mr_pouit: yes, nice catch :)
[08:50] <micahg> mr_pouit: fixed...was thinking of my other case where it quits
[08:51] <micahg> I'm waiting for i386 to publish before I attach the debdiff
[09:09] <^arky^> hi
[09:10] <micahg> hi ^arky^
[09:14] <^arky^> how are you micahg ?
[09:14] <micahg> mr_pouit: do I have to do anything else to test this...it didn't work
[09:14] <micahg> ^arky^: fine
[09:15] <mr_pouit> micahg: icons are still missing?
[09:15] <micahg> mr_pouit: yep, did it work on lucid...did you restart in between?
[09:15] <micahg> I quit before the upgrade
[09:15] <micahg> does OSD need a restart?
[09:15] <mr_pouit> no, only xfce4-power-manager afaik
[09:16] <micahg> mr_pouit: didn't work for me...
[09:16] <mr_pouit> do you have 'notify-osd-icons' package installed?
[09:16] <micahg> yep, 0.3
[09:17] <mr_pouit> mmh, weird
[09:17] <micahg> do you want to try the package?
[09:18] <mr_pouit> yeah, why not
[09:19] <micahg> ppa:micahg/sru-test
[09:22] <mr_pouit> interesting
[09:22] <mr_pouit> works here ^^'
[09:23] <micahg> weird
[09:23] <micahg> let me try quitting again
[09:24]  * micahg has the brightness plugin, I wonder if that's affecting it
[09:24] <^arky^> micahg: Changed Importance of bug 491327 to critical , hope that's right thing to do since it breaks gnome a11y completely
[09:24] <ubot4> Launchpad bug 491327 in at-spi "No module named pyatspi" [Critical,New] https://launchpad.net/bugs/491327
[09:25] <micahg> ^arky^: you still haven't found someone for that
[09:25] <micahg> mr_pouit: it's supposed to be in the notification itself, right?
[09:26] <mr_pouit> micahg: yes, the icon on the left, the text on the right
[09:27] <micahg> mr_pouit: i don't see it, and I didn't see one from pidgin either
[09:27] <^arky^> micahg: I tried Luke the maintainer of the package and on a11y list , no luck
[09:28] <mr_pouit> maybe something related to your icon theme... I don't really know :/
[09:28] <micahg> mr_pouit: is this something that needs to be figured out before the SRU?
[09:31] <mr_pouit> well, I would be more confident if someone else could follow the test case and confirm. Otherwise, I may be the only one to see the improvement, which isn't very good ^^
[14:23] <rob0917> I'm not very technical but how can I help?
[15:09] <bddebian> Boo
[15:12] <malev> ahh
[17:37] <nperry> bug 494608
[17:37] <ubot4> nperry: Bug 494608 on http://launchpad.net/bugs/494608 is private
[17:38] <nperry> Could somone double check this bug, and make public?
[18:42] <Dakon> hi ;)
[18:42] <Dakon> I would like to help with bug 470695 in case anyone is interested
[18:42] <ubot4> Launchpad bug 470695 in kdeutils "Kgpg doesn't run by default" [Undecided,New] https://launchpad.net/bugs/470695
[18:45] <Dakon> this is most likely either just the KGpg icon hidden in systray (because KGpg is inactive)
[18:45] <Dakon> or this one https://bugs.kde.org/show_bug.cgi?id=198483
[18:45] <ubot4> KDE bug 198483 in general "No system tray icon for KGpg after "Close" button is clicked" [Normal,Assigned]
[18:46] <Dakon> the hidden thing is explained in comment #2 there
[19:15] <yofel> can someone set bug 494643 to triaged? thanks
[19:15] <ubot4> Launchpad bug 494643 in kdebase "No kcm_phonon in kdebase-runtime after upgrade to 4.4-beta1" [Undecided,Confirmed] https://launchpad.net/bugs/494643
[19:21] <micahg> pedro_: sorry...that was a silly mistake :)
[19:22] <pedro_> micahg, no worries, the name leads to the confusion :-)
[20:46] <aergasdf> someone there?
[20:49] <davmor2> no
[20:49] <aergasdf> okey
[20:49] <aergasdf> last hope
[20:50] <aergasdf> i have a bug in a game
[20:50] <aergasdf> after a time the sound just stops
[20:50] <aergasdf> this bug is since dist upgrate
[20:51] <davmor2> aergasdf: is a bug with the game and pulse audio
[20:51] <aergasdf> so i have to downgrade pusaudio?
[20:52] <davmor2> what game is it?
[20:52] <aergasdf> heroes of newerth
[20:55] <aergasdf> so?
[20:56] <davmor2> aergasdf: pass, I just know what is causing it :)
[20:57] <aergasdf> what?
[20:57] <aergasdf> come on^^
[20:57] <aergasdf> its a mod of savage2
[20:58] <davmor2> aergasdf: you might want to try on #ubuntu for general help.  As I say I know the cause but not the remedy
[21:01] <aergasdf> warning: The VAD has been replaced by a hack pending a complete rewrite
[21:01] <aergasdf> does this help???
[21:04] <gnomefreak> what package controls system beep? i am looking for package to file bug against


[08:39] <shawarma> @schdule copenhagen
[08:39] <shawarma> @schedule copenhagen
[08:39] <Ubugtu> Schedule for Europe/Copenhagen: 01 Aug 22:00: Technical Board | 02 Aug 22:00: Edubuntu | 03 Aug 09:00: Ubuntu Development Team | 09 Aug 14:00: Edubuntu | 10 Aug 17:00: Ubuntu Development Team | 15 Aug 22:00: Technical Board
[10:27] <tkjacobsen> @schedule copenhagen
[10:27] <Ubugtu> Schedule for Europe/Copenhagen: 01 Aug 22:00: Technical Board | 02 Aug 22:00: Edubuntu | 03 Aug 09:00: Ubuntu Development Team | 09 Aug 14:00: Edubuntu | 10 Aug 17:00: Ubuntu Development Team | 15 Aug 22:00: Technical Board


[02:03] <snap-l> rick_h_: Do you still have power?
[02:37] <_stink_> snap-l: did you lose yours?  we had some dips but nothing else
[03:00] <rick_h_> yes
[03:01] <rick_h_> power is good
[03:49] <greg-g> Mine's good, too.
[12:59] <snap-l> _stink_: We still have power, which is good.
[12:59] <snap-l> Actually changed out the router last night. :)
[12:59] <snap-l> Finally got a chance to spend some time flashing it with Tomato
[20:19] <gamerchick02> how many of the peeps in here are irc-ing from phones because the power's out?
[20:19] <gamerchick02> my apartment is affected by the power plant disruption. i'm currently at my mom's house. :-\
[20:27] <rick_h_> no, there's some areas around my place without power
[20:27] <rick_h_> but all good at my place
[20:37] <_stink_> large chunks of south central Oakland (yes pretty gangsta sounding) are out - we were driving around earlier
[21:06] <gamerchick02> wow
[21:07] <gamerchick02> my apartment is off Walton and Dexter.
[21:07] <gamerchick02> the plant that's not too far from my place took a dump. who knows what's going on there.
[21:08] <gamerchick02> seems like DTE never can keep it's crap together (we don't have these issues in Saginaw)
[21:23] <gamerchick02> power's back on at my place
[21:24] <gamerchick02> but i'm doing laundry here. if i'd waited, the 11:30 PM restore time would have been accurate


[01:50] <bdx> could just be me
[01:51] <bdx> is jujucharms.com bugging out right now for everyone?
[01:51] <dnegreira> ts ok for me
[01:52] <bdx> safari I get https://imgur.com/a/uJgGT, chrome I get https://imgur.com/a/GYSS6
[01:54] <pmatulis> fine here on chrome
[01:54] <bdx> seem to be getting the same waiting/progress bar on chrome and safari now
[01:54] <dnegreira> am logged in fine via firefox
[01:54] <bdx> cool
[01:55] <bdx> must be a personal issue ..
[01:55] <bdx> thx thx
[01:58] <bdx> I try to access https://jujucharms.com and I get redirected to https://jujucharms.com/login/u/jamesbeedy to the spinner/waiting infinity
[01:59] <bdx> it all works for me in a incognito window
[01:59] <bdx> must be squirrels in the cache
[07:39] <ashipika> ping anybody?
[12:42] <rick_h> ashipika: ?
[12:42] <ashipika> rick_h are there any restrictions on who can land PRs in core?
[12:42] <rick_h> ashipika: yes, managed by the github project
[12:43] <ashipika> rick_h hmm.. it's not letting me land my PR
[12:43] <rick_h> ashipika: what's your GH username?
[12:43] <ashipika> rick_h alesstimec
[12:45] <rick_h> ashipika: hmm, so looks like most everyone has read access so maybe that's not it then.
[12:46] <ashipika> rick_h https://github.com/juju/juju/pull/8175
[12:46] <ashipika> rick_h can't land it with $$merge$$ or :shipit:
[12:46] <ashipika> rick_h what am i missing?
[12:46] <rick_h> ashipika: not sure how it's setup :(  cmars is a lead which has more rights so maybe check with him when he's on
[12:46] <ashipika> rick_h will do
[12:47] <rick_h> ashipika: hmm, yea looks like babbageclunk used $$merge$$ in a previous PR.
[12:47] <rick_h> ashipika: there was a rule a while ago that your team membership had to be public or the bot wouldn't auth you
[12:47] <rick_h> ashipika: but in this new UX in GH I can't tell wtf is up with that
[12:47] <rick_h> ashipika: so honestly not sure what's up
[12:47] <ashipika> rick_h np.. thanks anyway
[13:36] <jam> ashipika: so what happened is you did a $$check$$ from a long time ago, which the bot saw but got wedged, and it never replied with a "failed to build" message.
[13:36] <jam> So all follow up $$merge$$ requests are still treated as part of the original request, which it already handled.
[13:37] <ashipika> jam a-ha! right.. how do i resolve this? !!build!! again?
[13:37] <jam> working on it
[13:37] <jam> if you reply with the magic string that the bot replies with, then the bot will accept future $$merge$$ requests, but I always have to go figure out what the magic string is
[13:42] <rick_h> jam: ashipika can you just delete the comment with the $$check$$ ?
[13:45] <jam> rick_h: no. maybe if you deleted the comment from the bot. but hopefully I got the fix in. (got distracted doing a review while trying to find the magic string)
[13:45] <rick_h> jam: yea, I know originally I used to not $$merge$$ again but delete the bot's acceptance so that it would pick it up as a fresh request
[13:45] <rick_h> ashipika: if it's bot related like that I'd suggest just gardening the comment thread
[13:46] <rick_h> the bot's not very smart (at least when I wrote it at the start)
[15:01] <eriklonroth> Hmm, I can successfully deploy charms behind proxies that are downloaded as "juju deploy ./<charm>.zip", but if I try the same thing with "juju deploy cs:<charm>". It times out. What do I need to do to make the juju-client fetch charms from the store? (or do I just need to mess around more with our authenticated proxy at work?
[15:02] <rick_h> eriklonroth: the controller needs to have access to the store, not the client. The client will resolve and find the right url, but the controller will fetch the zip file
[15:03] <rick_h> eriklonroth: is this a maas or openstack or ?
[15:03] <eriklonroth> Its our first installation of maas we're trying to learn
[15:03] <rick_h> eriklonroth: can the nodes in maas reach the internet? e.g. does the maas server proxy requests through?
[15:04] <eriklonroth> The maas nodes can access internet though an unauthenticated proxy
[15:04] <rick_h> eriklonroth: in my maas at home I setup forwarding on the maas server itself and then the controller (running on the maas node) can reach out and contact the store
[15:05] <eriklonroth> When you say "forwarding", what does that means in terms of configuration?
[15:06] <rick_h> eriklonroth: setup NAT on the maas server
[15:06] <rick_h> eriklonroth: I'm looking for the proxy config settings. I thought they were in the controller-config but I'm not seeing it listed :( https://jujucharms.com/docs/devel/controllers-config
[15:07] <rick_h> eriklonroth: but if you can bootstrap, the controller machine must have been able to go out and get to the internet for the agents it downloaded...hmm
[15:07] <rick_h> eriklonroth: I guess try the deploy with --debug and see if that is more useful on where it's getting stuck.
[15:07] <eriklonroth> NAT:ing isnt the problem for us atm, I think it gotta be related to proxy settings somewhere
[15:08] <eriklonroth> I'll try mess around more with it.
[15:08] <rick_h> eriklonroth: but the flow is that the client resolves "juju deploy msyql" into cs:mysql-35 and then the controller is told to go get that
[15:08] <rick_h> eriklonroth: so that the client doesn't have to download/reupload the charms to the controller
[15:08] <eriklonroth> OK, so its not the client that first downloads from cs and then uploads it to the controller?
[15:09] <rick_h> eriklonroth: correct, the client doesn't download it to your client machine.
[15:09] <eriklonroth> OK, then I'm sure its the controller config - "somewhere" - for the proxy I need to figure out.
[15:10] <eriklonroth> That will be the exercise for tomorrow.
[15:10] <eriklonroth> Thanx for the help.
[15:12] <rick_h> eriklonroth: looks like model level config https://jujucharms.com/docs/devel/models-config
[15:13] <eriklonroth> I've successfully managed to configure the "default" model, but perhaps its the "controller" model in maas that needs to be setup ?
[15:13] <eriklonroth> Oh, well, "juju deploy cs:<charm>" isnt' working in the models either. Just from zip-file.
[15:13] <rick_h> eriklonroth: right, in that case the client is sending the charm up.
[15:13] <eriklonroth> But apt, pip etc. works
[15:14] <rick_h> eriklonroth: hmm, well wtf. Yea I guess I'm curious what the --debug output is.
[15:15] <eriklonroth> 16:14:48 DEBUG httpbakery client.go:244 client do GET https://api.jujucharms.com/charmstore/v5/xenial/ubuntu/meta/any?include=id&include=supported-series&include=published {
[15:15] <eriklonroth> .... stuck there
[15:16] <eriklonroth> https://pastebin.com/5MVE1N8F
[15:16] <eriklonroth> https://pastebin.com/5MVE1N8F
[15:18] <eriklonroth> Oh well, I have to run. My girfriend will kill me for letting her wait for 15 minutes while I'm messing around with a proxy
[16:36] <jhobbs> rick_h: do you now if you can use a unit name in a placement directive?
[16:36] <jhobbs> juju deploy blah --to glance/0 for instance?
[16:36] <rick_h> jhobbs: thinking
[16:37] <rick_h> jhobbs: into a container as well?
[16:37] <rick_h> jhobbs: or just the same machine?
[16:37] <jhobbs> same machine, whether it's a container or not
[16:37] <jhobbs> whatever machine is hosting that unit
[16:38] <jhobbs> hulk smashed with the unit
[16:38] <jhobbs> hmm seems to work
[16:38] <rick_h> jhobbs: yea, I don't think so. I was thinking in bundles you can say to colocate with an application name, but you don't get to pick 0/1/2 or such
[16:38] <jhobbs> no
[16:38] <jhobbs> it doesn't work
[16:38] <jhobbs> yeah
[16:38] <jhobbs> ok
[16:39] <jhobbs> thanks rick_h


[14:53] <big_t> good morning
[17:37] <MarkDude> Ok Washington- it appears that Oregon Team has some signs of life
[17:38] <MarkDude> We want to have a meeting in Portland in Feb
[17:38] <MarkDude> If any of you folks are interested in helping- let me know
[17:38]  * MarkDude will send announcement to WA & PNW list once details are sorted
[18:36] <cj> MarkDude: did you send the Oregon info to the WA list on purpose? :)
[18:40] <MarkDude> Um sure I totally meant to
[18:40] <MarkDude> rofl
[18:40] <MarkDude> oops
[18:40] <MarkDude> might as well sent it Cali Team also
[18:40] <MarkDude> Even funnier after I said I would *wait* to fill in WA later
[18:41]  * MarkDude goes to re-send, and triple check difference between *OR* and *WA*
[18:45] <cj> :)
 the digital firehose, one must be careful with where it is pointed


[06:34] <ScottK> OK.  I give.
[06:35] <ScottK> KPackageKit recommends installing an 'advanced' package manager like synaptic or aptitude to fix broken packages (apt-get -f install was sufficient to fix this case).
[06:35] <ScottK> I think I'm just going to install synaptic on any computers I don't admin.
[14:10] <apachelogger> lulz
[14:10] <apachelogger> the ubuntuone applet requires networkmanager
[14:11] <apachelogger> I suppose that tells a lot about the gnome dev platform :P
[14:11] <apachelogger> so, if one wants sensible ubuntuone implementation for KDE a complete reimplementation of the daemon is necessary :S
[14:12]  * apachelogger cant even create a KDE applet because his system aint got no nm
[16:28] <tsimpson> apachelogger: I'd like your opinion on bug #454597 if you're here
[16:28] <tsimpson> I don't think it's a bug, as the proper Qt initialization was not done
[16:32] <apachelogger> from a convenience POV it should not segfault :)
[16:32] <apachelogger> tsimpson: I'd upstream it and close the LP bug
[16:33] <apachelogger> rdale, being obsessed with perfection, probably wants to make it not segfault
[16:33] <tsimpson> ok, that's why I was unsure
[16:35] <apachelogger> tsimpson: technically you could argue both ways, on the one hand there should be no segfault, on the other hand a proper error treatment would also just tell the developer that he did something wrong, which is quite obvious from the segfault as well
[16:35] <apachelogger> so no matter what, the dev screwed up, the presentation is just not very nice currently :D
[16:36] <ScottK> Personally, I think a crash is always a bug.
[16:36] <tsimpson> well it'd probably crash in C++ too
[16:37] <apachelogger> yeah but it throws an error there I think
[16:38] <apachelogger> I suppose it would crash either way, since that issue is particularly nasty and catching the error signal would do no good since the app is defunct as long as Qt was not initialized
[16:38] <apachelogger> possibly irb should not crash though :)
[16:38] <tsimpson> just segfailts here
[16:42]  * apachelogger demands google bookmarks integration in chrome
[16:42]  * apachelogger also still finds the arguing pro-gtk rather weird :P
[16:47] <tsimpson> I would upstream, except bugs.kde.org is not letting me login
[16:47] <tsimpson> even after creating a new account...
[17:28] <JontheEchidna> whoa, next KDE update, all we have to do is to tell users to add: "ppa:kubuntu-ppa/ppa" with software-properties-kde, and that will grab the GPG key automagically
[17:37] <ryanakca> Hmmm... Anybody know if nixternal finished the feature tour for Karmic?
[17:41] <apachelogger> did not AFAIK
[17:42] <apachelogger> unless he worked over hours or something
[17:42] <JontheEchidna> yeah, I didn't hear anything about that either
[18:41] <JontheEchidna> openoffice update! maybe the file dialog bugs are fixed...
[18:53] <JontheEchidna> the places pane looks a bit funky, but no more invisible text
[18:53] <JontheEchidna> context menu text is invisible though :(
[18:59] <ScottK> Riddell: I uploaded the kde4libs fix for Kubuntu Netbook.  It's sitting, waiting for someone from Ubuntu Release to accept it.
[21:53] <ryanakca> apachelogger: bummer :/
[21:59] <markey> hmm, the kubuntu repo for Chromium, does it use the original builds or self-made ones?
[21:59] <markey> I'm asking because Chromium made a strange change since today or yesterday
[22:00] <apachelogger> we do not maintain a chromium repo
[22:00] <markey> ah ok
[22:00] <markey> so it's their standard daily builds
[22:01] <markey> what happened is, many site now come up with german language, although explicitly configured to english
[22:01] <markey> they must have done something to the browser ID
[22:14] <ryanakca> How would one fix bug 448789 ? Make k-n-d-s depend on k-n ?
[22:15] <apachelogger> Xdependency
[22:15] <apachelogger> also
[22:15] <apachelogger> removing kubuntu-desktop does not remove kubuntu-default-settings does it?
[22:38] <lex79> someone can upload ktorrent 3.2.4?  upstream bugfix release
[22:38] <lex79> http://ktorrent.org/?q=node/33
[22:38] <lex79> https://edge.launchpad.net/~alessandro-ghersi/+archive/staging