[02:06] <bigjools> Someone remind my tired brain, can a non-team-admin create a team PPA or is it restricted to team admins?
[07:57] <cjwatson> bigjools: Team admins only.  (You need launchpad.Edit on the PPA owner.)


[00:03] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Currently building (xenial/telepathy-qt). Failed to build (vivid/messaging-app, vivid/messaging-framework, xenial/history-service, xenial/messaging-framework, zesty/history-service, zesty/messaging-framework, zesty/telepathy-qt, zesty/telephony-service). Pending binary packages (vivid/telepathy-qt). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telep
[00:08] <boiko> robru: can you please trigger a rebuild of telepathy-qt5/amd64/zesty on silo 1319? I want to check if a failure there is transient
[00:08] <robru> boiko: sure
[00:11] <boiko> robru: thanks!
[00:11] <robru> boiko: you're welcome!
[00:22] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Currently building (zesty/telepathy-qt). Diff missing (vivid/telepathy-qt, xenial/telepathy-qt). Failed to build (vivid/messaging-app, vivid/messaging-framework, xenial/history-service, xenial/messaging-framework, zesty/history-service, zesty/messaging-framework, zesty/telephony-service). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telepathy-ofono,
[00:42] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Diff missing (vivid/telepathy-qt, xenial/telepathy-qt, zesty/telepathy-qt). Failed to build (vivid/messaging-app, vivid/messaging-framework, xenial/history-service, xenial/messaging-framework, zesty/history-service, zesty/messaging-framework, zesty/telephony-service). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telepathy-ofono, vivid/telephony-serv
[00:55] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Preparing packages
[01:22] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Currently building (xenial/messaging-framework, zesty/messaging-framework). Failed to build (vivid/history-service, vivid/messaging-app, vivid/telepathy-ofono, xenial/history-service, xenial/telepathy-ofono, xenial/telephony-service, zesty/history-service, zesty/telepathy-ofono). Pending binary packages (vivid/messaging-framework, vivid/telephony-service, zesty/telephony
[01:42] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/history-service, vivid/messaging-app, vivid/telepathy-ofono, xenial/history-service, xenial/telepathy-ofono, xenial/telephony-service, zesty/history-service, zesty/telepathy-ofono). Successfully built (vivid/dialer-app, vivid/messaging-framework, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/messaging-app, xenial/messaging-
[01:56] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Preparing packages
[02:42] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, xenial/history-service, xenial/telephony-service). Pending binary packages (vivid/telepathy-ofono, xenial/telepathy-ofono). Successfully built (vivid/dialer-app, vivid/history-service, vivid/messaging-framework, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/messaging-app, xenial/messaging-framework, xenial/te
[03:03] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, xenial/history-service, xenial/telephony-service). Successfully built (vivid/dialer-app, vivid/history-service, vivid/messaging-framework, vivid/telepathy-ofono, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/messaging-app, xenial/messaging-framework, xenial/telepathy-ofono, xenial/telepathy-qt, zesty/dialer-a
[03:48] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Preparing packages
[03:48] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2130 Preparing packages
[04:13] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Currently building (vivid/unity-scopes-shell, xenial/unity-scopes-shell). Failed to build (zesty/unity-scopes-shell). Successfully built (vivid/unity-scopes-api, xenial/unity-scopes-api, zesty/unity-scopes-api)
[04:13] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2130 Currently building (xenial/unity-scopes-shell). Failed to build (zesty/unity-scopes-shell). Successfully built (xenial/unity-scopes-api, zesty/unity-scopes-api)
[04:33] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Failed to build (zesty/unity-scopes-shell). Successfully built (vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-api, xenial/unity-scopes-shell, zesty/unity-scopes-api)
[04:34] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2130 Failed to build (zesty/unity-scopes-shell). Successfully built (xenial/unity-scopes-api, xenial/unity-scopes-shell, zesty/unity-scopes-api)
[08:04] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2130 Preparing packages
[08:16] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2130 Preparing packages
[09:12] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2130 Dependency wait (zesty/unity-scopes-shell). Pending binary packages (xenial/unity-scopes-shell). Successfully built (xenial/unity-scopes-api, zesty/unity-scopes-api)
[09:32] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2130 Dependency wait (zesty/unity-scopes-shell). Successfully built (xenial/unity-scopes-api, xenial/unity-scopes-shell, zesty/unity-scopes-api)
[09:54] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://bileto.ubuntu.com/#/ticket/2131 Needs rebuild due to new commits (zesty/account-plugins). Successfully built (vivid/account-plugins, xenial/account-plugins)
[10:53] -queuebot:#ubuntu-ci-eng- dednick, https://bileto.ubuntu.com/#/ticket/2026 Preparing packages
[11:08] -queuebot:#ubuntu-ci-eng- dednick, https://bileto.ubuntu.com/#/ticket/2026 Currently building (vivid/unity8). Dependency wait (zesty/unity8). Failed to build (xenial/unity8). Pending binary packages (vivid/qtubuntu, vivid/qtubuntu-gles, xenial/qtubuntu-gles, zesty/qtubuntu-gles). Ready to build (zesty/qmenumodel, zesty/ubuntu-touch-meta, zesty/unity8-desktop-session). Successfully built (vivid/qmenumodel, vivid/ubuntu-touch-meta, vivid/unity8-desktop-session, xenial/qm
[11:13] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://bileto.ubuntu.com/#/ticket/2131 Preparing packages
[11:29] -queuebot:#ubuntu-ci-eng- dednick, https://bileto.ubuntu.com/#/ticket/2026 Dependency wait (zesty/unity8). Failed to build (xenial/unity8). Ready to build (zesty/qmenumodel, zesty/ubuntu-touch-meta, zesty/unity8-desktop-session). Successfully built (vivid/qmenumodel, vivid/qtubuntu, vivid/qtubuntu-gles, vivid/ubuntu-touch-meta, vivid/unity8, vivid/unity8-desktop-session, xenial/qmenumodel, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-touch-meta, xenial/unity8-d
[11:29] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Preparing packages
[11:30] <mzanetti> oSoMoN, hey, had to leave yesterday. what was the outcome with the oxide issue?
[11:31] <oSoMoN> mzanetti, not solved yet as the version in the silo is < the version in xenial-security, but chrisccoulson is going to upload a new version to the silo shortly
[11:31] <mzanetti> ok, great, thanks
[11:31] <mzanetti> ltinkl, ^
[11:32] <ltinkl> cool, ty
[11:34] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Preparing packages
[11:35] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://bileto.ubuntu.com/#/ticket/2131 Successfully built
[11:49] -queuebot:#ubuntu-ci-eng- Wellark, https://bileto.ubuntu.com/#/ticket/2119 Publishing packages
[11:50] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Currently building (vivid/unity8, zesty/unity8). Failed to build (xenial/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components)
[11:50] -queuebot:#ubuntu-ci-eng- Wellark, https://bileto.ubuntu.com/#/ticket/2120 Abandoning ticket
[11:55] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Currently building (vivid/unity8, zesty/unity8). Failed to build (xenial/unity8). Successfully built (vivid/indicator-power, xenial/indicator-power, zesty/indicator-power)
[12:02] -queuebot:#ubuntu-ci-eng- Wellark, https://bileto.ubuntu.com/#/ticket/2119 Proposed pocket (zesty/indicator-network). Release pocket (xenial/indicator-network)
[12:10] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Failed to build (xenial/unity8). Pending binary packages (zesty/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components)
[12:15] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Destination version missing from changelog (zesty/indicator-network). Failed to build (xenial/ubuntu-app-launch, xenial/url-dispatcher, zesty/unity-scopes-shell, zesty/url-dispatcher). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-network, xenial/indicator-power,
[12:16] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Failed to build (xenial/unity8). Successfully built (vivid/indicator-power, vivid/unity8, xenial/indicator-power, zesty/indicator-power, zesty/unity8)
[12:25] -queuebot:#ubuntu-ci-eng- dbarth, https://bileto.ubuntu.com/#/ticket/2139 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[12:29] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Failed to build (xenial/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components, zesty/unity8)
[13:00] <jgdx> robru, do I need to save a new ticket before building?
[13:00] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Preparing packages
[13:01] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 zesty/ubuntu-system-settings: Failed to commit https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/displays-mir. You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[13:16] <Elleo> trainguards: how can I sort out the missing changelog error on this ticket https://bileto.ubuntu.com/#/ticket/2033? I updated the MR to include the changelog that had been manually uploaded to zesty, but it still reports it as missing
[13:21] <mardy> Mirv: hi! The autopkgtest results in https://bileto.ubuntu.com/#/ticket/2135 seem due to wrong package deps (temporary glitch?), is there a way to force re-running the tests?
[13:21] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Ready to build
[13:24] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Preparing packages
[13:25] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Preparing packages
[13:32] <dobey> mardy: anyone with upload rights to the package in question, or the package which triggered the autopkgtests, can click the re-run button next to the failed tests on the excuses page, to re-run a test
[13:32] <mardy> dobey: eh, not me unfortunately :(
[13:33] <dobey> Elleo: 2016-11-03 13:14:55,174 ERROR Commit this to TRUNK, then rebuild!
[13:34] <dobey> Elleo: so i'm pretty sure you need to get that changelog entry into trunk rather than in your MP
[13:35] <Mirv> mardy: I have clicked the retries for the xenial failures now
[13:36] <mardy> Mirv: thanks
[13:36] <Mirv> mardy: http://autopkgtest.ubuntu.com/running#pkg-ubuntu-system-settings-online-accounts
[13:37] <Elleo> dobey: ah, okay; thanks
[13:37] <Mirv> Elleo: as dobey said, there's disparency between what trunk says and what archive says, even though they should be identical
[13:41] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2033 Preparing packages
[13:42] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, xenial/telephony-service). Pending binary packages (zesty/history-service). Successfully built (vivid/dialer-app, vivid/history-service, vivid/messaging-framework, vivid/telepathy-ofono, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/history-service, xenial/messaging-app, xenial/messaging-framework, xenial/tel
[13:45] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Currently building (vivid/unity8, zesty/unity8). Failed to build (xenial/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components)
[13:51] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Preparing packages
[13:56] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Preparing packages
[13:57] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Preparing packages
[14:05] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Failed to build (xenial/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components, zesty/unity8)
[14:10] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2142 Abandoning ticket
[14:15] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2033 Successfully built
[14:17] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Currently building (vivid/unity8, zesty/unity8). Failed to build (xenial/unity8)
[14:20] -queuebot:#ubuntu-ci-eng- charles mterry ted, https://bileto.ubuntu.com/#/ticket/2138 Preparing packages
[14:23] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, xenial/telephony-service). Successfully built (vivid/dialer-app, vivid/history-service, vivid/messaging-framework, vivid/telepathy-ofono, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/history-service, xenial/messaging-app, xenial/messaging-framework, xenial/telepathy-ofono, xenial/telepathy-qt, zesty/dialer-a
[14:38] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Failed to build (xenial/unity8). Pending binary packages (vivid/unity8, zesty/unity8)
[14:43] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Failed to build (vivid/ubuntu-system-settings). Successfully built (vivid/qtmir, vivid/qtmir-gles, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-system-settings, zesty/qtmir, zesty/qtmir-gles, zesty/ubuntu-system-settings)
[14:49] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 This ticket must be migrated to zesty+xenial+vivid before it can be built
[14:51] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Preparing packages
[14:58] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Failed to build (xenial/unity8). Successfully built (vivid/unity8, zesty/unity8)
[14:59] -queuebot:#ubuntu-ci-eng- dbarth, https://bileto.ubuntu.com/#/ticket/2139 Ready to build
[15:03] -queuebot:#ubuntu-ci-eng- charles mterry ted, https://bileto.ubuntu.com/#/ticket/2138 Destination version missing from changelog (zesty/indicator-network). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-network, xenial/indicator-power, xenial/indicator-printers, xenial/indicator-session, xenial/indicator-sound, xenial/indicator-transfer, zest
[15:05] -queuebot:#ubuntu-ci-eng- koza, https://bileto.ubuntu.com/#/ticket/2004 Diff missing (yakkety/bluez). Pending binary packages (vivid/bluez). Successfully built (xenial/bluez)
[15:07] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Failed to build (vivid/url-dispatcher, zesty/url-dispatcher). Pending binary packages (xenial/url-dispatcher)
[15:19] <mardy> Mirv: mmm... it failed again with the same error, so maybe it's not a temporary glitch... however, I have no idea what's wrong<EMAIL_ADDRESS>[15:25] -queuebot:#ubuntu-ci-eng- koza, https://bileto.ubuntu.com/#/ticket/2004 Diff missing (yakkety/bluez). Successfully built (vivid/bluez, xenial/bluez)
[15:27] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Failed to build (vivid/url-dispatcher, zesty/url-dispatcher). Successfully built (xenial/url-dispatcher)
[15:35] <dobey> mardy: it's the oxide issue
[15:37] <mardy> dobey: thanks, I was not aware of such an issue; I should just ignore it, I guess?
[15:38] <dobey> mardy: does your silo link to oxide?
[15:39] <dobey> mardy: you might need to rebuild after oSoMoN's silo lands i guess
[15:46] <mardy> dobey: ah ok, I'll try that
[15:51] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Successfully built
[16:11] -queuebot:#ubuntu-ci-eng- Laney, https://bileto.ubuntu.com/#/ticket/2089 Updates pocket
[16:15] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Preparing packages
[16:28] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Currently building (xenial/url-dispatcher). Failed to build (vivid/url-dispatcher). Successfully built (zesty/url-dispatcher)
[16:29] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Preparing packages
[16:45] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Currently building (vivid/unity8, zesty/unity8). Failed to build (xenial/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components)
[16:51] -queuebot:#ubuntu-ci-eng- dbarth, https://bileto.ubuntu.com/#/ticket/2139 Abandoning ticket
[17:02] <dobey> robru: i think you need to get rid of the [SAVE] button next to "Add a comment" erhaps
[17:02] <dobey> perhaps
[17:03] <robru> dobey: why?
[17:04] <dobey> robru: it's confusing. i edited MP urls, then hit save, and then got an error about malformed request
[17:04] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Needs rebuild due to new commits (zesty/ubuntuone-credentials). Ready to build (xenial/unity-scope-click, zesty/unity-scope-click). Successfully built (xenial/ubuntuone-credentials)
[17:04] <dobey> robru: so what does the save button actually do?
[17:05] <robru> dobey: the save button submits your comment.
[17:05] <robru> which is why it's next to the comment field there
[17:05] <robru> dobey: the fields on the ticket autosave when the input loses focus
[17:06] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Failed to build (xenial/unity8). Pending binary packages (vivid/unity8, zesty/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components)
[17:06] <dobey> robru: maybe only make it clickable if there is a comment to save, and/or change it "save comment" (or maybe make it more like LP's CSS for editing the summary line of a bug report)
[17:07] <dobey> i saw jgdx ask a similar question this morning about saving a request before building
[17:07] <robru> dobey: ok, just working on something else, will get to that in a sec
[17:08] <dobey> robru: np. just offering my experience :)
[17:08] <robru> dobey: thanks
[17:23] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Preparing packages
[17:25] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Failed to build (xenial/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components, zesty/unity8)
[17:25] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 zesty/unity-scope-click: Failed to branch https://code.launchpad.net/~dobey/unity-scope-click/u1-no-delete
[17:31] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Preparing packages
[17:32] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Preparing packages
[17:33] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 zesty/unity-scope-click: Failed to branch https://code.launchpad.net/~dobey/unity-scope-click/u1-no-delete
[17:35] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Preparing packages
[17:39] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2143 QA Signoff: N/A
[17:43] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2143 Preparing packages
[18:04] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Successfully built
[18:05] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Successfully built
[18:05] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2143 Successfully built
[18:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2124 Preparing packages
[18:30] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Cancelled build (xenial/url-dispatcher). Successfully built (vivid/url-dispatcher, zesty/url-dispatcher)
[18:46] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Needs rebuild due to new commits (zesty/libertine). Successfully built (vivid/libertine, xenial/libertine)
[18:48] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Successfully built
[18:56] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Preparing packages
[19:00] -queuebot:#ubuntu-ci-eng- robru, https://bileto.ubuntu.com/#/ticket/2144 Abandoning ticket
[19:07] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2124 Pending binary packages
[19:30] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Pending binary packages (vivid/libertine, xenial/libertine). Successfully built (zesty/libertine)
[19:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2124 Successfully built
[19:30] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2145 Preparing packages
[19:30] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Preparing packages
[19:40] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2143 Publishing packages
[19:41] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2143 Publish failed: Bad merges
[19:44] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Pending binary packages (xenial/ubuntuone-credentials, zesty/ubuntuone-credentials). Successfully built (xenial/unity-scope-click, zesty/unity-scope-click)
[19:45] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Successfully built
[19:59] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2143 Preparing packages
[20:04] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Successfully built
[20:04] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Needs rebuild due to new commits (zesty/libertine). Successfully built (vivid/libertine, xenial/libertine)
[20:05] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Preparing packages
[20:08] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2145 Pending binary packages
[20:13] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2111 Proposed pocket
[20:27] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Successfully built
[20:27] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2143 Successfully built
[20:27] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2145 Successfully built
[20:39] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2077 Bad merges (yakkety/qtmir). Dependency wait (vivid/qtmir, vivid/qtmir-gles). Failed to build (vivid/miral, vivid/unity-api, xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, yakkety/qtmir-gles, yakkety/unity-api). Needs rebuild due to new commits (yakkety/miral). Successfully built (xenial/miral)
[20:43] <larryprice> trainguards: is this the right place to ask about possibly getting a new package in overlay?
[20:44] <robru> larryprice: yes
[20:44] <larryprice> robru, cool
[20:45] <larryprice> robru, in particular i'm looking to use gir1.2-appstream-1.0
[20:45] <larryprice> currently there is a separate package for the older implementation called gir1.2-appstream (no -1.0)
[20:46] <larryprice> which is available in xenial, vivid
[20:46] <robru> larryprice: use it where? on a phone?
[20:46] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Preparing packages
[20:47] <larryprice> robru, any device? we'd like to integrate it as part of libertine, which runs x apps in unity 8
[20:48] <robru> larryprice: ok so what's the situation? the package in overlay is older than the one in xenial/vivid? or it's not in overlay at all?
[20:52] <larryprice> robru, from what i can tell the >=0.9 series of the package is called gir1.2-appstream and is available on xenial,vivid,trusty
[20:52] <larryprice> robru, what we're using is the 0.10 series of the package which seems to have been renamed to gir1.2-appstream-1.0 and is only available on yakkety,zesty
[20:52] <robru> larryprice: ok so you're wanting to backport zesty to xenial & vivid then is what you're saying?
[20:55] <larryprice> robru, yes we'd like to use the zesty version of the package on xenial+overlay/vivid+overlay
[20:56] <robru> larryprice: ok, so what you're going to want to do is create your own PPA, then do the backport there. you'll also have to backport any dependencies. then once you have that built, make a ticket and I'll copy the packages from your ppa to the ticket ppa. then we submit to qa to make sure it doesn't explode the phone.
[20:58] <robru> larryprice: wait, is canonical upstream of this project?
[20:59] <larryprice> robru, you mean package i want to backport?
[21:00] <robru> larryprice: yeah. nm it looks like we aren't.
[21:00] <larryprice> nope
[21:00] <robru> larryprice: anyway yeah prep the backport in your own ppa and then ping me once you got it building for xenial and vivid
[21:00] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/2137 Failed to build (xenial/unity8). Ready to build (vivid/unity8-desktop-session, xenial/unity8-desktop-session, zesty/unity8-desktop-session). Successfully built (vivid/unity8, zesty/unity8)
[21:01] <larryprice> robru, willdo thanks for the tips!
[21:01] <robru> larryprice: you're welcome!
[21:13] -queuebot:#ubuntu-ci-eng- charles mterry ted, https://bileto.ubuntu.com/#/ticket/2138 Preparing packages
[21:13] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2124 Publishing packages
[21:13] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2124 Publish failed: Packaging diff requires ACK
[21:15] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2134 Diff missing
[21:25] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Successfully built
[21:27] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2124 Successfully built
[21:35] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Destination version missing from changelog (zesty/indicator-network). Failed to build (xenial/ubuntu-app-launch, xenial/url-dispatcher, zesty/unity-scopes-shell, zesty/url-dispatcher). Ready to build (xenial/unity8-desktop-session, zesty/unity8-desktop-session). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-location,
[21:45] -queuebot:#ubuntu-ci-eng- charles mterry ted, https://bileto.ubuntu.com/#/ticket/2138 Successfully built


[06:18] <rbansal> Hi Guys, I need a MIPS32 toolchain with NPTL support, so can anyone help me in this regard?


[03:34] <TunaCan> Heyyy
[03:34] <TunaCan> https://wiki.ubuntu.com/UEFI/SecureBoot
[03:35] <TunaCan> "Ubuntu installs its own BootEntry at installation time and may update it any time the GRUB bootloader is updated." That quote kind of bugs me. can I disable that feature for my ubuntu?
[03:35] <arraybolt3[m]> I think you need that in order to boot Ubuntu at all.
[03:36] <TunaCan> I have grub chainloaded into another grub
[03:36] <TunaCan> ubuntu's grub
[03:38] <TunaCan> Ever since I installed ubuntu, I've been screwing with keys ALOT
[03:44] <enigma9o7[m]> well you dont have to run update-grub, it requires sudo so it cant run itself anyway
[03:45] <enigma9o7[m]> grub3 tho boots win10/11 directly right?
[03:45] <enigma9o7[m]> grub2 can boot win7/8.1 but not 10 i dont think
[03:46] <enigma9o7[m]> definkately grub2 can boot xp
[03:46] <TunaCan> oh. My bad, I've been key hashing secure boot land for a couple days
[03:46] <TunaCan> lots of pixels
[03:47] <TunaCan> Windows XP
[03:47] <TunaCan> yes
[04:44] <huffman> hi
[04:45] <lotuspsychje> welcome huffman
[05:15] <jaco> hi
[05:17] <jaco> i need help on how to make anbox stable
[05:17] <arraybolt3[m]> jaco: How's it misbehaving?
[05:19] <enigma9o7[m]> give up on anbox.  try waydroid.
[05:20] <enigma9o7[m]> install deb get then `sudo deb-get install waydroid`
[05:20] <arraybolt3[m]> jaco: enigma9o7 has a good idea, if you're using Ubuntu 22.04. However, if you're using 20.04, you won't have Wayland, which will keep you from using Waydroid.
[05:20] <enigma9o7[m]> https://github.com/wimpysworld/deb-get
[05:21] <enigma9o7[m]> with 20.04 you can still use wayland
[05:21] <enigma9o7[m]> and with 18.04 you can use weston
[05:23] <jaco> thank u
[05:24] <enigma9o7[m]> if you run into issues trying whatever you try, let us know, we may be able to help
[05:25] <enigma9o7[m]> there's also a waydroid channel on matrix that may be able to help waydroid specific issues
[05:26] <enigma9o7[m]> (as thats not official ubuntu)
[05:29] <lotuspsychje> jaco: you can also try androidx86 on virtualbox, i would agree with enigma9o7[m] anbox is a bit flaky
[06:12] <plugger> Hi all am running vanilla Ubuntu 22.04 desktop and noticed that its(applications) all snaps. What does terminal and apt install (flatpack or is it called an apt package or something)
[06:23] <ThinkT510> ubuntu uses both snaps and traditional .deb packages. even when you use app it may install a snap (depending what package you are trying to install)
[06:23] <ThinkT510> *when you use apt
[06:27] <plugger> thanks
[06:28] <plugger> if i wanted to strip out all snaps and replace with .deb would i run into many issues as at today(and moving forward) any suggestions on expediting that process from terminal
[06:30] <ThinkT510> to be blunt, if you don't want snaps you are better off not using ubuntu. they seem dead set on going snap only
[06:30] <lotuspsychje> plugger: as user you have the choice of installing wich packages you want/need apt or snap or ppa's,..etc
[06:30] <plugger> i see and thank you for getting to the point its appreciated
[06:30] <lotuspsychje> ThinkT510: ubuntu can still be tweaked the way a user want right, with as less snaps as desired
[06:31] <lotuspsychje> on -desktop snapd can be purged
[06:33] <plugger> i'd like to give that a try as well. so would i purge snapd and all snaps installed after installing my .deb replacements? Or doesn't matter? Do i need to stop systemd snapd service or will purge take care of all (plus autoremove)
[06:34] <lotuspsychje> plugger: thats your choice really, if you're sure you never need a snap in the future
[06:35] <guiverc> ThinkT510, If you use package managers for installing software (eg. synpatic, muon, aptitude..) as they handle only deb packages you won't be offered snap packages.. Yes some (gnome software, discover, software boutique) offer both & thus have more options, but just using specific package managers will limit snap packages (exceptions being chromium, firefox where deb will force snap to install)
[06:35] <plugger> a better question would be if i purge snapd that wouldnt remove any of my currently installed snap's would it? eg firefox
[06:36] <plugger> also thanks for all the comments has been very informative
[06:36] <plugger> props lotuspsychje guiverc ThinkT510
[06:37] <guiverc> plugger, `apt-cache rdepends snapd` can show you some effects of removing snapd; ie. many packages rely on it
[06:37] <plugger> ty
[06:37] <plugger> nice
[06:43] <plugger> that list is kinda huge =( and my hardware is old; im noticing the lag on my system during boottimes and even browser launches, Any thoughts ppl? would really like to bring down my boottimes
[06:43] <lotuspsychje> plugger: what kind of system specs do you have?
[06:43] <ThinkT510> it is a bit disingenuous to say you can tweak the system for wanting snaps vs debs. while technically true it will always be an uphill battle since ubuntu are heavily invested and intent on pushing snaps forward
[06:45] <plugger> https://pastebin.com/3RS7iLkW
[06:46] <arraybolt3[m]> plugger: You could try Lubuntu - you can successfully remove snapd from it without problems (at least I had no problems doing it).
[06:46] <plugger> i dont know if i can ThinkT510 but im inclined to have a crack at making it faster
[06:46] <plugger> unless told its a waste of time
[06:47] <arraybolt3[m]> GNOME is heavy. That is what it is. Other Ubuntu flavooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooours are much lighter.
[06:47] <arraybolt3[m]> (Wow, thanks lag.)
[06:47] <arraybolt3[m]> flavors*
[06:47] <lotuspsychje> i would agree with arraybolt3[m] plugger your system would benefit lubuntu
[06:48] <plugger> i'll give it a go
[06:50] <lotuspsychje> ThinkT510: perhaps, but its not like apt packages are gonna vanish any time soon neither, sow e always have to leave the end user the choice right?
[06:51] <lotuspsychje> its not for us to decide to say ubuntu is not reccomended if you dont like snaps
[06:52] <plugger> i really have loved Ubuntu for some time but im thinking with this hw at least ill probably end up jumping to a tiling manager or debian, am not so big into snaps
[06:53] <plugger> my boot times are driving me nuts
[06:54] <lotuspsychje> !flavors | plugger pick one
[06:55] <ThinkT510> if a person didn't want an .rpm based distro then I certainly wouldn't suggest fedora. same principle with snaps.
[06:55] <plugger> yeah very fair comment
[06:56] <arraybolt3[m]> OK, just jumping in to say, Ubuntu is **not** all Snap. It's only got a few snaps by default, Firefox being the "big one". You can still easily replace Firefox with the apt package, and if you're using a flavor like Lubuntu, you can do away with Snap entirely.
[06:56] <lotuspsychje> i dont think thats the same comparison ThinkT510 but feel free to discuss that in -discuss
[06:57] <ThinkT510> yet
[06:57] <lotuspsychje> +1 arraybolt3[m]
[06:57] <arraybolt3[m]> Even Canonical recognizes that going "full force" into Snap mode would go poorly - in fact the one OS they have that does go full force into Snap mode is Ubuntu Core, and Ubuntu Core has a very specific use case that does not include desktop use.
[06:58] <arraybolt3[m]> (It's designed for IOT stuff.)
[06:59] <plugger> If i removed Gnome DE and replaced with i3wm, would that have any impact on my boot times?
[07:00] <plugger> or just after login
[07:00] <ThinkT510> that wouldn't affect boot time
[07:01]  * plugger cluches at straws =(
[07:01] <lotuspsychje> i3 boots the fastest of all on ubuntu, isnt it ducasse
[07:01] <lotuspsychje> surely affects boot times
[07:01] <ThinkT510> whether you use a desktop environment or a window manager doesn't affect how long it takes to get from a cold boot to the login screen
[07:02] <plugger> =(
[07:02] <plugger> dam it
[07:02] <ThinkT510> i3 will certainly be lighter after login that gnome, yes
[07:03] <lotuspsychje> graphical target will be much faster
[07:04] <plugger> whats the command your run for boottime information
[07:05] <arraybolt3[m]> Given how heave GNOME is, quite possibly.
[07:05] <arraybolt3[m]> heavy* (not heave, golly)
[07:05] <lotuspsychje> plugger: systemd-analyze
[07:05] <plugger> lol im in it now
[07:05] <plugger>   792ms snapd.seeded.service
[07:06] <plugger> 24.646s plymouth-quit-wait.service
[07:06] <arraybolt3[m]> ThinkT510: While that might be true, background services that come with a DE will most likely affect boot time.
[07:06] <plugger> this list is nasty compared to how fast it was in days gone by(but not to many versions ago)
[07:07] <arraybolt3[m]> plugger: (From experience, lotuspsychje is a trusted member of the channel - however I've only seen ThinkT510 once, and that's in this exact chat.)
[07:07] <arraybolt3[m]> plugger: systemd-analyze blame
[07:08] <plugger> thanks im very much aware of lotuspsychje he/she has helped me out many times
[07:08] <plugger> but still thanks to all contributing
[07:11] <plugger> https://pastebin.com/Mw0rZWZ7
[07:12] <plugger> just wondering what other peoples boottime experience is clocking in around for a desktop?
[07:12] <plugger> is mine average, poor, or beyond help lols?
[07:12] <arraybolt3[m]> plugger: https://termbin.com/fjuvl
[07:13] <lotuspsychje> plugger: can you paste systemd-analyze too please
[07:15] <arraybolt3[m]> plugger: Yours are a bit worse than mine - I'm on standard Ubuntu too. I know Lubuntu boots faster.
[07:15] <plugger> https://pastebin.com/sMirh9z5
[07:15] <plugger> =) cheers
[07:16] <arraybolt3[m]> Wait - 3 1/2 minutes in the kernel? Yikes, Lubuntu might not be a total fix after all.
[07:16] <plugger> ha ha
[07:16] <arraybolt3[m]> Why... is it doing that?
[07:16] <plugger> i know its not a happy camper
[07:17] <plugger> Im not sure why
[07:17] <arraybolt3[m]> systemd-analyze critical-chain
[07:17] <lotuspsychje> plugger: hd is a spinner?
[07:17] <plugger> no ssd
[07:18] <arraybolt3[m]> I wonder if the system is trying to find a drive or partition that doesnt exist and is finally giving up?
[07:18] <lotuspsychje> plugger: did you just file a bug against gnome-shell?
[07:19] <plugger> https://pastebin.com/6B8Z7YSV
[07:19] <plugger> no i did not
[07:20] <plugger> lotuspsychje, why did you ask that?
[07:20] <lotuspsychje> plugger: nvm
[07:21] <plugger> its a fresh install
[07:21] <arraybolt3[m]> plugger: Someone was able to solve a similar problem as you by adding swap to their system. Do you have a swapfile?
[07:21] <arraybolt3[m]> (Open the system monitor and see if there's any swap space.)
[07:21] <plugger> with not much added (anything that was added was a snap)
[07:21] <ice9> hi lotuspsychje , do you remember my issue about closing laptop lid which does nothing however suspend is enabled in gnome-tweeks?
[07:22] <lotuspsychje> yes ice9
[07:22] <ice9> lotuspsychje, so you need the full dmesg right?
[07:22] <arraybolt3[m]> plugger: (Actually, scratch that, the swap thingy was related to something else.)
[07:23] <lotuspsychje> ice9: not sure where we stopped last time
[07:23] <ice9> lotuspsychje, https://bin.linux.pizza/?294bf8ec31ec1f14#DBjaaRqbcFpSrVGh7vnKJFqb9XncDrYE8piWyTJVpwqx
[07:25] <ice9> lotuspsychje, last time I closed the lid with journalctl -f and there were lid-close/open actions in the log
[07:27] <plugger> sorry children
[08:21] <alocer> hello all
[08:31] <SteelRose> hi there! stupid question about certificates... My employer has its own CA to sign certs. Windows machines access internal websites fine, the https:// thing looks green. But on Ubuntu 20.04 LTS I see https:// in red, "connection is not secure", etc... is there anything I must do to trust the company's certificates? Thanks!
[08:32] <ravage> SteelRose, https://ubuntu.com/server/docs/security-trust-store
[08:33] <ravage> you will also have to add it to applications like Firefox that use their own CS store
[08:35] <ravage> *CA
[08:39] <SteelRose> ravage: thanks
[08:39] <SteelRose> let me check
[08:41] <Duality> hey all
[08:42] <Duality> I am re installing ubuntu but This time I want to seperate my Home directory from the Root Filesystem and I am wondering how much space to allocated for the Root Filesystem (exclude the home) any input?
[08:44] <ravage> 20 to 25GB
[08:44] <SteelRose> Duality: do you have a 2nd disk in your system?
[08:44] <ravage> you can get some flexibility with LVM
[08:47] <ravage> but a second device (external for example) for backups is much more helpful
[08:47] <ravage> you have backups and you just reinstall everything
[08:47] <ravage> win win
[08:47] <Duality> SteelRose: no but I was planning to seperate the home into a seperate partition
[08:50] <SteelRose> Duality: if you can get a secondary disk and use it for /home only, that'd be nice... then you can reinstall and still keep your stuff safe
[08:50] <Duality> That might be a better solution :)
[08:52] <BlackMage> i have problems with flameshot
[08:53] <BlackMage> the window doesn't open and only blank icon appears
[09:02] <SteelRose> ravage: I've imported the Root-CA but still the browser shows "connection is not secure" ... :-/
[09:16] <alocer> SteelRose: if you press the lock icon it shows you what certificate is missing, not exactly sure how , but i know its possible.
[09:22] <ogra> BlackMage, https://forum.snapcraft.io/t/help-with-flameshot-icon/21134 ... try asking the maintainer in that thread ... (seems to be a known issue he never resolved)
[09:30] <SteelRose> alocer: let me check that
[09:32] <SteelRose> alocer: I have all the files needed... so perhaps I need to wait for some TTL to expire? no idea
[09:32] <SteelRose> I even logged out and back in again
[09:37] <alocer> SteelRose: it should work after importing, maybe you imported it to wrong place.
[09:37] <alocer> idk
[09:39] <SteelRose> alocer: I followed the instructions here https://ubuntu.com/server/docs/security-trust-store
[09:39] <SteelRose> nevermind... I can live with a "certificate is invalid" thing
[10:07] <yverx> hey all o/
[10:08] <yverx> have some (hopefully minor) networking issues, cant get anything to work on my pc anymore. so i also cant googkle my way out of it ...
[12:19] <goddard> any way to have applications grouped as tabs
[12:21] <goddard> sometimes i have 2 or 3 windows that are the same open and it would be cool if it was just 1 window with tabs
[12:36] <BluesKaj> Hi all
[13:04] <lotuspsychje> goddard: spread your applications over workspaces?
[13:05] <lotuspsychje> !info x-tile | goddard or
[15:02] <barg> I have ubuntu 20.04 I want to alt-get install ugrep, it says "unable to locate package".    I see it listed https://packages.ubuntu.com/search?keywords=ugrep&searchon=names&suite=all&section=all   impish (21.10)   and jammy (22.04LTS) and kinetic (utils).  Should I add all three of those repos? Or just kinetic (since my ubuntu version is before the one specified by impish and jammy)?
[15:04] <lotuspsychje> !info ugrep focal
[15:04] <oerheks> barg, no, tha package is just not available for 20.04, trying to install can give a dependencie problem
[15:04] <barg> ok, thanks
[15:04] <oerheks> wait for a week to get the upgrade notice to 22.04.1
[15:05] <oerheks> 4 august
[15:05] <lotuspsychje> good idea
[15:08] <tarzeau> lotuspsychje: are you on 22.10 already?
[15:09] <lotuspsychje> tarzeau: sorry no, i debug only LTS releases usualy
[15:09] <ravage> non LTS-releses are debug releases :P
[15:09] <lotuspsychje> :p
[15:10] <tarzeau> i would've liked to hear from new packages i've done
[15:10] <goddard> gnome online accounts are giving me issues
[15:10] <goddard> (gnome-control-center:78878): Gdk-CRITICAL **: 11:10:01.638: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
[15:11] <goddard> Segmentation fault (core dumped)
[15:11] <lotuspsychje> tarzeau: i think there are many of the volunteers in #ubuntu-next and #ubuntu-quality willing to test on kinetic
[15:15] <tarzeau> lotuspsychje: thanks, will ask there
[17:25] <forgotmynick> I'm trying to get ssh logs into one location and sftp logs into another through rsyslog (which sends to graylog). sshd is configured with `SyslogFacility LOCAL6` and `LogLevel INFO`. sftp `ForceCommand internal-sftp -f LOCAL5 -l INFO`. There are logs being generated for ssh and sftp, but there's still log entries coming in from systemd but not sure why or what i can do about this https://i.imgur.com/D0iESZf.png - I don't want
[17:25] <forgotmynick> all systemd logs going  to ssh or sftp logs. Please advise?
[17:32] <sarnold> forgotmynick: maybe LogLevelMax ? https://www.freedesktop.org/software/systemd/man/systemd.exec.html#LogLevelMax=
[17:43] <transhumanist> anyone know if nvidia gpu accelleration options are enabled by default when nvidia driver is installed? for desktop rendering and video acceleration I mean?
[17:48] <BarnabasDK> transhumanist, you can check it with the glxinfo tool - glxinfo | grep "direct rendering" and glxinfo | grep vendor
[17:49] <transhumanist> thanks
[18:24] <deego> in /etc/default/grub, i have GRUB_TIMEOUT_STYLE=menu  and GRUB_TIMEOUT=60  and I did sudo update-grub. Yet, it shows no menu and jumps straight to the boot sequence
[18:24] <deego> this is 22
[18:25] <hggdh> check /etc/default/grub.d/ instead, values there override anything set in /etc/default/grub
[18:25] <sarnold> do you have any GRUB_DEFAULT settings?
[18:28] <deego> thaks! GRUB_DEFAULT=saved and grub.d has an empty file (comments)
[18:29] <deego> changed it to 0. works now. thanks!
[18:31] <deego> now, if i could just figure out why the resolution is always 1366x768. I thought nvidia t500 supports higher resolutions. have blacklisted nouveau, etc.
[18:31] <deego> nvidia-settings shows just that one choice of resolutions.
[18:46] <deego> https://bpa.st/EU7Q  - prime-select query does show nvidia. Does that resolution: line mean that only 1366x768 is actually supported?
[18:47] <sarnold> try xrandr -- it'll dump a bunch of modes that the device reports it can do, perhaps filtered by what the card can do
[18:48] <deego> sarnold: i did xrandr --prop  - the highest it shows is 1366...
[18:48] <sarnold> o_O
[18:48] <sarnold> how's your cables?
[18:48] <deego> but, again, the card is advertized to support really high resolutions, as high as 3500x..
[18:48] <deego> sarnold: this is a laptop
[18:49] <sarnold> deego: count the pixels on your screen?
[19:19] <bray90820> So i'm having an issue here I have an RDP setup on 22.04 but when I connect sometimes it just disconnects imeditally and I need to restart the computer for it to work again
[19:23] <horse9> @bray90820 I've only used RDP to hop onto Windows machines so far and it worked pretty well.
[19:24] <bray90820> I am connectung one ubuntu machine to connect to another
[19:25] <bray90820> horse9:
[19:25] <BarnabasDK> bray90820,  - I suggest you look into an RDP server with session control - I use xRDP
[19:26] <horse9> I used the flatpak image of Remmina (the snap one has permission issues)
[19:26] <BarnabasDK> also from ubuntu to ubuntu
[19:26] <BarnabasDK> also use reminna as client here
[19:26] <bray90820> Isn't XRDP only for connectung to a connect to a windows machine?
[19:27] <horse9> @BarnabasDK which store did you get it from? or repository? I had issues with the snap one. It kept crashing.
[19:27] <BarnabasDK> apt install xrdp
[19:27] <bray90820> It is the default one built into ubuntu
[19:27] <bray90820> It was preinstalled
[19:28] <bray90820> But I can connect to other ubuntu machines fine
[19:28] <bray90820> And teamviewer also shows a black screen which makes me think it's not a remmina issue
[19:29] <BarnabasDK> bray90820, thats a teamviewer issue with wayland
[19:29] <BarnabasDK> try X
[19:29] <bray90820> I am using X
[19:29] <horse9> yeah wanted to say the same
[19:30] <bray90820> I'm using X11
[19:30] <horse9> is someone else maybe also using the remote machine and drops your connection?
[19:30] <bray90820> No one else is using it
[19:30] <horse9> can you tpy 'snap list'
[19:31] <horse9> and see if remmina is there
[19:31] <bray90820> I really don't think remmina is the issue since the issue happens with ubuntu as well
[19:32] <bray90820> But in any case remmina is not in the snaped list
[19:32] <horse9> k, thx
[19:33] <bray90820> If it happens with teamviewer why would it be a remmina issue tho
[19:34] <BarnabasDK> bray90820, you may have more than one issue here :-)
[19:34] <horse9> x_x
[19:34] <BarnabasDK> one is your disconnect - another the black screen
[19:34] <bray90820> Aaahhh alright
[19:35] <bray90820> I do thimk there related tho because a restart fixes both
[19:37] <horse9> you could ssh into to machine and look at the logs
[19:37] <horse9> and reproduce the crash
[19:38] <horse9> I can't tell you which exactly to look at though but network, x, rdp and there is this one kernel thingy. This could get you closer.
[19:40] <BarnabasDK> if you are using the new built in RDP server (In place of xrdp) I also think you need to consider your power saving settings - make sure your black screen is not because it does a monitor off or something
[19:48] <horse9> @BarnabasDK oh wow that is a good insight. I read a lot about the new gnome power saving options. It seems to be very complex.
[20:00] <bray90820> BarnabasDK: That's intresting still doing testing but it looks like screen timeout might actually be my issue
[20:04] <bray90820> It's crazy how complex that is
[20:06] <BarnabasDK> xrdp lets me chose a specific window manager for remoting (lightweight through xfce) and run it all over ssh via remminas ssh tunnelling capability - I find gnome to be a little too heavy for good desktop response using it remotely
[20:07] <horse9> nice
[20:30] <horse9> is this the best ubuntu irc channel?
[20:35] <coconut> horse9, the main and biggest
[20:35] <horse9> thanks. That's the answer I was looking for.
[21:14] <Guest57> i don't know wtf i did but i can't run absolutely anything in bash anymore - everything gives me "no such file or directory"
[21:14] <jhutchins> There is also a channel on OFTC, and there may still be something on Freenode (can anybody confirm?)
[21:14] <Guest57> i can't even figure out if i blew away root or something
[21:15] <jhutchins> Guest57: What did you try to do?  How did you try to do it?  What did you expect to happen?  What happened instead?
[21:16] <MonkZ> Hiho, seems like de.archive.ubuntu.com serves empty files for "http://de.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages" is this just me or are there repo problems?
[21:16] <jhutchins> MonkZ: First try removing "de."
[21:16] <Guest57> jhutchins last thing i did was tar -C / ghdl.tgz
[21:17] <Guest57> where ghdl had the directory structure lib bin share etc
[21:17] <Guest57> so obv bad idea
[21:17] <MonkZ> Guest57: is your $PATh Modified?
[21:17] <Guest57> it is but resetting doesn't do anything
[21:17] <forgotmynick> jhutchins: only fans? :D
[21:17] <MonkZ> jhutchins: thx i'll try
[21:17] <Guest57> eg `PATH=/usr/bin ls` doesn't work
[21:19] <Guest57> is there no way to see what's in a directory just using bash commands?
[21:19] <jhutchins> Guest57: You answered about 1.4 out of 4 questions.   Thanks a lot
[21:21] <jhutchins> MonkZ: You're letting the resolver pick the best site this way.  The de mirror may not be feeling well today.
[21:21] <jhutchins> I don't know of a handy mirror status page.
[21:21] <jhutchins> Guest57: The only possible damage a tar command can do is a full disk.
[21:22] <Guest57> clearly it overwrote *something*
[21:22] <ikonia> simple test /usr/bin/ls
[21:23] <BarnabasDK> Guest57, if you are on the console crtl+alt+F(n) gives you a new console
[21:23] <ikonia> sorry /bin/ls
[21:23] <BarnabasDK> see if you can login
[21:23] <Guest57> can't open a new console
[21:23] <ikonia> Guest57: /bin/ls
[21:23] <Guest57> `bash: /bin/ls: No such file or directory`
[21:23] <ikonia> re-install your OS then
[21:23] <ikonia> if ls is gone - you don't know what you've done to cause damage
[21:23] <BarnabasDK> ikonia, maybe a little drastic
[21:23] <Guest57> fml that is indeed what happened it somehow overwrote all of /bin
[21:23] <ikonia> it's fundementally broke
[21:24] <BarnabasDK> ikonia, what about a boot device?
[21:24] <ikonia> BarnabasDK: what about it
[21:24] <BarnabasDK> create an ubuntu boot device on a usb stick
[21:24] <ikonia> and what will that achieve
[21:24] <BarnabasDK> copy in the files you need to the disk
[21:24] <ikonia> that will break the OS more
[21:24] <ikonia> as files will be out of sync from hte package manager
[21:25] <ravage> im sure there is an existing backup already. nobody ever operates a main system without backups
[21:25] <Guest57> is boot disk + restore an option?
[21:25] <ikonia> no
[21:25] <ikonia> re-install your OS
[21:26] <ravage> in case you do not have a backup yet you can use a live system and an external drive to backup stuff
[21:26] <Guest57> i don't understand why reinstalling ontop won't fix
[21:26] <ravage> there is no such thing
[21:26] <Guest57> yes there is i've done it before
[21:26] <ikonia> may as well cut to the chase and re-install
[21:27] <ikonia> rather then debate things that don't matter
[21:27] <BarnabasDK> Guest57, I would not start by doing that - I am not so fatalistic - have made systems work again that was much worse of than that without defaulting to
[21:27] <BarnabasDK> that
[21:27] <ikonia> you can make systems work again
[21:27] <ikonia> no-one is disputing that
[21:28] <ikonia> however looking at the level of maturatiy operating a system (doesn't know how it was broke using tar) is that really a good approach
[21:28] <ikonia> re-install, get a system working as a stable base, learn from mistake
[21:28] <BarnabasDK> its never too late to reinstall is what I am trying to convey
[21:28] <BarnabasDK> but once you do so - it is too late to go back
[21:31] <cbreak> BarnabasDK: nah
[21:31] <cbreak> you can always go back, unless your backup failed
[21:32] <cbreak> if you actually want to rescue a system, the first step should be to validate, or create a backup
[21:32] <cbreak> (well, at least if you want to minimize risk)
[21:34] <BarnabasDK> the user said nothing about a backup being available
[21:34]  * cbreak really likes zfs boot
[21:34] <cbreak> BarnabasDK: backups being available should be the default. Or at least snapshots. Unless it's a throw-away system.
[21:35] <BarnabasDK> yeah - I agree - but I do not think the user mentioned zfs either
[21:35] <BarnabasDK> so asume ext
[21:50] <cbreak> hmm... seems that ubuntu's snap stuff is still broken
[21:51] <ikonia> that's a pretty wide statement
[21:51] <cbreak> it keeps complaining about having to restart firefox (and now even lxd) for updates, but when I restart it, it resumes complaining about it.
[21:51] <cbreak> and I bet the only way to fix this is to manually force snap to update
[21:51] <cbreak> just like the past five times this happened
[21:52] <ikonia> is there a bug logged for it ?
[21:52] <cbreak> I have no idea.
[21:52] <ikonia> can you get others to validate it ?
[21:52] <ikonia> ok - they seem like two good steps to getting it resolved
[21:52] <cbreak> everyone can validate it.
[21:52] <cbreak> it's apparently working as designed.
[21:52] <ikonia> well, getting someone to validate it would be a start
[21:52] <ikonia> then logging a bug and showing the validation
[21:52] <ikonia> and providing the details of the bug
[21:53] <yourname> I have a similiar issue with the nextcloud client
[21:53] <horse9> I had to close down my desktop session and change into command mode and then update
[21:53] <horse9> this allowed it to properly update
[21:54] <ogra> cbreak is righ, it works as designed ... prob is that the design is unfinished 😛
[21:55] <cbreak> for me, usually forcing the update (with the program closed) is enough. And interestingly, forcing the update with 'snap refresh' gives the result: All snaps up to date.
[21:55]  * ogra points to https😕/forum.snapcraft.i👋t/wip-refresh-app-awareness/10736/90
[21:55] <ogra> bah !... emoji plugin galore
[21:55] <sarnold> lol
[21:56] <cbreak> :/
[21:56] <horse9> thank god I thought it was only me with the emojis lol
[21:56] <ogra> the post i tried to link tells you that notification has been disabled again until the design is actually finished
[21:58] <cbreak> so... firefox will just never update? :/ I suppose that's less annoying, but not really as secure as the 20.04 solution
[21:58] <ogra> there is a valid reason to tell you to close the app ... snaps use versioned "app homedirs" ... during update the home directory changes to the new one ...
[21:58] <ogra> ... and apparmor denies access to the old one ...
[21:58] <ogra> so if the app is open, you might lose history
[21:59] <cbreak> shouldn't app armor changes only apply to new processes?
[21:59] <cbreak> hmm...
[21:59] <ogra> firefox will update
[21:59] <tomreyn> https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736/90 seems to be the link you meant to post ;)
[21:59] <ogra> yeah, thanks
[21:59] <cbreak> also, firefox seems to store most stuff in the common part
[22:00] <ogra> i should use bit.ly to avoid teh plugin (or simply remove i from my hexchat) 🙂
[22:00] <yourname> anyone using keepassXC with firefox? It was the reason for me to drop from the snap version ;(
[22:01] <sarnold> cbreak: during the snap lifecycle the apparmor profiles are refreshed; I see it often with matterhorn, I show up in the morning and matterhorn has hung, can't open attachments, can't open links, can't save history, etc :(
[22:01] <cbreak> I use 1password, and the snap-ening of firefox also broke that half-way :(
[22:01] <horse9> (sorry, still having trouble yourname is me)
[22:02] <horse9> anyway. yeah. apparently it's a snap thing with the password managers and browser integration.
[22:02] <ogra> github.com/flatpak/xdg-desktop-portal/issues/655
[22:03] <ogra> ^^^
[22:03] <cbreak> from what I read, it's related to snap breaking (intentionally of course, because, why not?) Native Messaging
[22:03] <ogra> that will fix it
[22:03] <ogra> "breaking"
[22:03] <ogra> heh
[22:04] <cbreak> ogra: hmm... switching to flatpack firefox? :)
[22:04] <ogra> native messaging breaks any sandboxing concept ... so you can not "just allow it" withtough completely breaking snap security
[22:04] <ogra> *without
[22:04] <cbreak> firefox has its own sandbox
[22:04] <cbreak> and native messaging could presumably be "firewalled"
[22:04] <horse9> we heard you like sandboxes, so we put a sandbox...
[22:05] <ogra> right, which is essentially what the portal i linked above will do
[22:05] <cbreak> (on Mac OS, the equivalent of messaging can be restricted to only work between properly signed applications for example)
[22:06] <horse9> good link, thanks
[22:07] <cbreak> even more annoying than 1password is the crappy software we use at work. f5 vpn (utter garbage) and aspera file transfer both fail for similar reasons
[22:08] <cbreak> on that topic: How can I convince ubuntu to read / process a .desktop file?
[22:09] <cbreak> (if it makes a difference, I'm running kde plasma)
[22:09] <ogra> all XDG compliant desktops should pick them up from ~/.local/share/applications/
[22:10] <cbreak> hmm ... that seems reasonable
[22:10] <bobdobbs> I'm using ubuntu 22.04. I want to use an application whose vendor highly recommends that it be used in docker. Is it best to install docker from the ubuntu repo? Or should I install it directly?
[22:12] <cbreak> bobdobbs: I think it's generally recommended to install the one from docker itself
[22:12] <cbreak> since the one in ubuntu might not be as up-to-date
[22:13] <cbreak> (https://docs.docker.com/engine/install/ubuntu/ (do not get docker desktop, just the engine)).
[22:14] <cbreak> I've read some people recommend podman over docker. I never tried that one though, no idea if it's good.
[22:14] <sarnold> yeah I hear a lot of love for podman


 So what happens if we only have 2 standing for 3 spots?
 Hello everyone, this came in this morning.
 Hi, … couldn't find a general email address for the Kubuntu Team so I would like to pass on my gratitude in this way. … I've been working with computers, electronics and software for well over 30 years. However, in recent years got more and more frustrated with the "mainstream" systems like Apple and Microsoft and their ignorance of computer users in preference over profits. … About two and a half years ago started l
 How, wonderful to receive. Well done to everyone :-)
[16:26] <yofel> valorie, acheronuk: Nope, I have no intention of extending my council membership this time
 Once mine is out next year I don't plan on doing it either.
[18:41] <valorie> yikes
[18:42] <valorie> thanks for your long years of work, yofel
[18:42] <valorie> how are ya, ahoneybun?
[18:43]  * valorie is still battling jetlag/smoky air
 I'm doing fine valorie now that I have help ;_)
[21:20] <valorie> how is Thomas fitting in with the crew?
[21:21] <valorie> I know he's good, after the numerous times he's helped me over the years
 He's fitting very well I believe.
[21:23] <valorie> that's good to hear
 Yep!
[21:24] <acheronuk> yofel: sad to hear, but I understand. thank you


[08:25] <xubuntu84i> Hi every body. I plan to use Ubuntu 16 insted of Debian jessie because after trying debian since three months. I used to have many problems with dongle Bluetooth. I think Ubuntu is more user friendly than debian, and I hope i could use bluetooth without problems, or am´i wrong?


[00:00] <mbruzek> You have clicked on propose for merging?
[00:00] <apuimedo> basically to enable cassandra to work in lxc
[00:00] <apuimedo> yup
[00:00] <apuimedo> should I press again?
[00:00] <mbruzek> hrmm... usually that creates a new bug
[00:00] <mbruzek> I can't find the bug.
[00:00] <apuimedo> ok
[00:01] <apuimedo> I'll press again
[00:01] <apuimedo> I see "Charles Butler: Pending requested 2015-04-22 "
[00:01] <mbruzek> I will review it right away
[00:01] <apuimedo> I'll propose for merging putting you as a reviewer now
[00:01] <mbruzek> Yes I see that too.  I don't see how to approve or review these changes
[00:02] <mbruzek> Propose for merging and I will have a look
[00:03] <apuimedo> it tells me "There is already a branch merge proposal registered for branch lp:~celebdor/charms/precise/cassandra/hostname_resolve to land on lp:charms/cassandra that is still active."
[00:03] <mbruzek> OK let me check by that branch
[00:03] <apuimedo> let's see if I can just add you as a reviewer of the current proposal
[00:03] <mbruzek> I just need a link to the merge proposal
[00:03] <apuimedo> there
[00:04] <apuimedo> added
[00:04] <apuimedo> https://code.launchpad.net/~celebdor/charms/precise/cassandra/hostname_resolve/+merge/257120
[00:04] <mbruzek> OK that is a different link
[00:04] <mbruzek> The reason this one is not in the review queue, is because the status is in "Work in progress"
[00:04] <mbruzek> It needs to be in "Fix committed" for the queue to pick it up.
[00:06] <apuimedo> try now
[00:06] <apuimedo> I can only move it to "needs review"
[00:06] <mbruzek> Oh my mistake
[00:07] <apuimedo> mbruzek: if you want to try the pinning
[00:07] <apuimedo> you can run it like so
[00:08] <apuimedo> mbruzek: http://paste.ubuntu.com/11833500/
[00:08] <apuimedo> configuration yaml for deploying
[00:08] <apuimedo> and target an lxc machine
[00:15] <mbruzek> apuimedo: I found a problem.
[00:16] <mbruzek> apuimedo: Adding a configuration option like this must be added to config-changed.
[00:17] <apuimedo> mmm
[00:17] <apuimedo> let me see
[00:18] <apuimedo> where's config-changed? mbruzek
[00:19] <mbruzek> apuimedo: It is cassandra-common.  Let me comment  in the bug and
[00:19] <mbruzek> I will explain.
[00:19] <apuimedo> ok
[00:23] <mbruzek> OK.
[00:24] <mbruzek> This new configuration option is ONLY read on the install hook.
[00:24] <apuimedo> yes
[00:24] <mbruzek> If cassandra charm is installed and a user changes the package_version  only the config-changed hook is called.
[00:25] <mbruzek> So the user would not see any error and *assume* the version has changed
[00:25] <mbruzek> juju set cassandra package_version=2.11
[00:26] <mbruzek> apuimedo: I put my review in the Merge Proposal  https://code.launchpad.net/~celebdor/charms/precise/cassandra/hostname_resolve/+merge/257120
[00:27] <apuimedo> thanks for the review
[00:28] <apuimedo> I'll look into the changes you propose tomorrow
[00:28] <apuimedo> I was under the impression that as it stood, the charm didn't reinstall even if you changed the repo
[00:29] <apuimedo> (which is an already present configuration option) so that's why I did not consider the need for taking the config change into account
[00:29] <apuimedo> mbruzek: ^^
[00:31] <mbruzek> apuimedo: I understand your point, but the immutable configuration breaks user expectations
[00:32] <mbruzek> If the user sets the version after install they would have no way to know the version was not changed.
[00:32] <mbruzek> You could have the same logic in the configure_cassandra function to run apt-get to get a specific version.
[00:34] <mbruzek> Once you have the change put the Merge Proposal back in Ready for Review and give me a ping I will review it straight away.
[13:08] <caribou> Hi, is there some specific helper to add debconf values before installing a package or we should just shell out the debconf-set-selections command ?
[15:07] <caribou> Is the juju-reboot statement still valid in a charm ? If so does it require a prior import in python ?
[15:16] <caribou> nevermind, I was just being stoopid
[17:10] <cory_fu> stub: I think we lost you
[19:59] <wolverineav> hi, I have a question related to quantum-gateway charm, I hope this is the right channel for it.
[20:00] <wolverineav> I see the TODO item on https://jujucharms.com/trusty/quantum-gateway : 'Support VLAN in addition to GRE+OpenFlow for L2 separation.'
[20:01] <wolverineav> does that mean that currently you cannot override the default and set it to VLAN only?
[20:03] <wolverineav> if that's the case, I guess the first step would be to submit an upstream patch to add a new configurable property, right?
[20:04] <wolverineav> oh, some context - this property would apply to the ML2 plugin in neutron (quantum-gateway for juju), which is currently set to 'type_drivers = gre,vxlan,vlan,flat'
[20:15] <lazyPower> wolverineav: this is the correct channel, but most of our openstack charmers are EU based. That would be a great question for the list - and I'll make sure to circle back and piont them at it
[20:20] <wolverineav> lazyPower: thanks, appreciate it! i'm in  pacific time, so i would still be around late evening - midday EU.
[20:20] <lazyPower> yeah - we have some fresh blood just now ramping up in the OS charm space that should be able to lend a hand moving forward
[20:20] <lazyPower> but its too soon to tap on them for questions like that :)
[20:20] <lazyPower> ddellav: ^ we're coming for you @_@
[20:21] <ddellav> lol
[20:21] <ddellav> i'll do what I can
[20:30] <wolverineav> haha..I guess this might be the perfect fit for ramping up - how to add a new config property which is set in the *.ini file before the charm is first applied ;-)
[20:32] <wolverineav> i'm just browsing through the 'hooks' to see how its passed around..
[20:39] <marcoceppi> wolverineav: we don't really use quantum-gateway anymore,a nd instead use nuetron-api
[20:39] <marcoceppi> is there a reason you need quantum?
[20:40] <marcoceppi> fwiw, I believe the neutron charm supports VLAN with openvswitch
[20:42] <wolverineav> ah, I guess the example I saw was an old one which used quantum-gateway. and since it had 'trusty' and supported juno, I assumed its up to date
[20:43] <wolverineav> marcoceppi: let me try it out with neutron-api. thanks!
[21:23] <wolverineav> marcoceppi: when specifying 'network-manager: Neutron' in nova-cloud-controller, it is mentioned "When using the Neutron option you will most likely want to use the neutron-gateway charm to provide L3 routing and DHCP Services."
[21:24] <wolverineav> when I search for neutron-gateway: https://jujucharms.com/q/neutron-gateway , I see three relevant charms - quantum-gateway, neutron-openvswitch and neutron-api
[21:25] <wolverineav> what is the recommended combination when deploying with L3 and DHCP service?
[21:26] <wolverineav> I'm guessing its nova-cloud-controller + quantum-gateway + neutron-api. and the last one (neutron-api) is what I was missing earlier
[21:35] <wolverineav> ah, actually no - nova-cloud-controller + neutron-api are part of openstack controller. neutron-openvswitch is on every compute node and the node where we deploy quantum-gateway.
[23:39] <marcoceppi> wolverineav: yes, sorry, seems liek you've gotten it now
[23:39] <marcoceppi> if it helps I can give you a bundle that is a reference architecture for OpenStack which includes how neutron-api works
[23:41] <wolverineav> marcoceppi: yes, that would be helpful :)
[23:42] <marcoceppi> wolverineav: https://jujucharms.com/openstack-base/
[23:43] <marcoceppi> wolverineav: and here's the actual bundle https://api.jujucharms.com/charmstore/v4/bundle/openstack-base-34/archive/bundle.yaml
[23:55] <wolverineav> marcoceppi: this is great! thanks!


[08:19] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths added bug to [issue #2465](https://github.com/MirServer/mir/issues/2465): ABI breakage of libmircore.so.1 with v2.8.0 vs v1.8.2
[09:07] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths drafted [pull request #2466](https://github.com/MirServer/mir/pull/2466): Bump mircore soname
[09:07] -GitHub[m]:#mir-server-
[09:07] -GitHub[m]:#mir-server- > Fixes: #2465
[09:12] <Saviq> Good morning o/
[09:13] <alan_g[m]> Saviq: Good morning, how are you this week?
[09:14] <Saviq> All good, thanks. Weekend too short :)
[09:14] <Saviq> You?
[09:14] <alan_g[m]> Much the same. Too much of it spent weeding
[09:24] -GitHub[m]:#mir-server- **[MirServer/mir]** frank-dspeed opened [issue #2467](https://github.com/MirServer/mir/issues/2467): Bug: Starting mirserver with nvidia-470... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/f3d8ec881d5c765906a19c83e19a8bf4f3fabcaa)
[09:29] -GitHub[m]:#mir-server- **[MirServer/mir]** frank-dspeed edited [issue #2467](https://github.com/MirServer/mir/issues/2467): Bug: Starting mirserver with nvidia-470
[09:32] -GitHub[m]:#mir-server- **[MirServer/mir]** frank-dspeed edited [issue #2467](https://github.com/MirServer/mir/issues/2467): Bug: Starting mirserver with nvidia-470 maybe also 515 as it turns out
[09:32] -GitHub[m]:#mir-server- **[MirServer/mir]** frank-dspeed edited [issue #2467](https://github.com/MirServer/mir/issues/2467): Bug: Starting mirserver with nvidia-470 even 515
[10:43] <alan_g[m]> Huh, why do we have a rebuild?
[10:43] <alan_g[m]> $ diff -qr /snap/ubuntu-frame_beta/2*
[10:43] <alan_g[m]> Files /snap/ubuntu-frame_beta/2294/meta/snap.yaml and /snap/ubuntu-frame_beta/2561/meta/snap.yaml differ
[10:43] <alan_g[m]> Files /snap/ubuntu-frame_beta/2294/snap/manifest.yaml and /snap/ubuntu-frame_beta/2561/snap/manifest.yaml differ
[10:44] <Saviq> > Huh, why do we have a rebuild?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/451addcc77702b78a2d1c176d42daa58fc25ab2c)
[10:45] <Saviq> I refreshed the help text
[10:47] <alan_g[m]> Saviq: Ah, right
[11:47] <Saviq> alan_g thanks for the review, will fix. I'm going to need a bit of assistance please:
[11:47] <Saviq> https://github.com/MirServer/mir/pull/2464/files#diff-c5e7495f2b7719ad72c650438650bd4723471bf7034b7a4b2b9aea3e0de2b37bR66-R71
[11:48] <Saviq> I'm having trouble understanding how does `StreamLogger::out` end up pointing to nullptr…
[11:58] <alan_g[m]> It isn't, you are reusing the out parameter after moving from it
[12:09] <Saviq> Oh so it's a name clash :duh:
[12:45] <Saviq> alan_g did you wanted to add something here?
[12:45] <Saviq> https://github.com/MirServer/mir/pull/2464/files/5191eb0ac8ac6d9e8cc1f5a9f3e5fbc82e29ae32#r895545035
[12:45] <Saviq> *want
 "alan_g did you wanted to add..." <- https://github.com/MirServer/mir/pull/2464/files/5191eb0ac8ac6d9e8cc1f5a9f3e5fbc82e29ae32#r895545035
[13:02] <alan_g[m]> Well, you said it was going away and it didn't
[13:11] <Saviq> alan_g I'm likely, again, missing something obvious here, but I wanted for the stream to be owned by the StreamLogger, since it outlives where the stream is opened. What is the better choice here?
[13:12] <alan_g[m]> Just moving the fstream?
[13:12] -GitHub[m]:#mir-server- **[MirServer/mir]** frank-dspeed edited [issue #2467](https://github.com/MirServer/mir/issues/2467): Proposal: Better handling for ubuntu with nativ drivers from nvidia 470 even 515
[13:13] <Saviq> Oh. Duh.
[13:15] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths edited [issue #2467](https://github.com/MirServer/mir/issues/2467): Auto-selection of X11 platforms fails with Nvidia drivers (470 and 515)
[13:30] <Saviq> alan_g ah but that would mean FileLogger can _only_ do `ofstream`s, and as is it can do other streams as well, WDYT?
[13:30] <Saviq> (why I now renamed it `StreamLogger`…)
[13:33] <alan_g[m]> I can imagine using, say, `stringstream` during testing, so there is some arguement for generalizing it. But not sure it justifies the complexity
[15:03] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths marked [pull request #2466](https://github.com/MirServer/mir/pull/2466): Bump mircore soname as ready for review
[15:09] <Saviq> alan_g unless you have something in mind lined up for grayson-g, I thought he could start looking at the status screen feature for Frame?
[15:10] <Saviq> (after he's done with the touch filters)
[15:10] <alan_g[m]> I was thinking he should progress some of the documentation work we have piled up. (With a bit more guidance)
[15:12] <Saviq> FWIW I don't want for that to take more than a day of anyone's week, as that can get tiring quickly, and should be a team job
[15:13] <Saviq> I will get the meta-documentation going as my next TODO so everyone can pitch in
[15:32] <sophie-w> Going to move my remote assistance efforts from gnome-remote-desktop to wayvnc: https://github.com/any1/wayvnc
[15:32] <sophie-w> Not as featureful as GRD (doesn't support RDP, probably other stuff as well), but might be simpler to get running
[15:35] <Saviq> So no dice with GRD?
[15:36] <Saviq> It does look like there will be little wayvnc-specific work here, so we could move to a more featureful solution in the future
[15:37] <Saviq> RDP, vaapi/vdpau come to mind as things we should think of
[15:38] <sophie-w> GRD isn't unworkable, but I think it might be a pretty big sink of time.
[15:39] <sophie-w> And I'm starting to rethink my stance that we shouldn't build our own
[15:39] <Saviq> And sounds like a lot of the plumbing is GNOME-specific
[15:39] <sophie-w> But if there's something else that can work for us then we should try that first
[15:39] <alan_g[m]> I'm for gettings something simple to work to gain experience if nothing else
[15:39] <sophie-w> Agreed
[15:40] <sophie-w> GRD might actually be the most generic thing, since some of the work will be hooking into D-Bus interfaces that either are or at least are similar to the XDG desktop portal ones
[15:43] <sophie-w> What would be ideal (from a certain perspective) is to build a remote desktop server that uses only the generic XDG desktop portal interfaces, and then have those interfaces implemented for Mir in a way that also works on Sway/wlroots, because then the the same remote desktop server would work everywhere
[15:44] <sophie-w> The downside of that though is that implementing the D-Bus interfaces and implementing a remote desktop server using them might be quite a bit more work than just implementing a remote desktop server that consumes Wayland protocols.
[15:45] <sophie-w> And add a lot more complexity to the system. With the latter approach (which is I think what waypipe uses), D-Bus need not be involved at all.
[15:51] <Saviq> We will need the portals in the long run so we can support screen casting/recording from desktop apps - but +1 on starting simple
[15:52] <Saviq> alan_g re: `std::unique_ptr<mir::logging::Logger>`, that's unhappy b/c `mir::logging::~Logger` is protected. Think it worth reworking that, or better sticking with `std::shared_ptr`?
[15:53] <sophie-w> Saviq: Well the XDG ScreenCast portal already works with xdg-desktop-portal-wlr
[15:53] <alan_g[m]> Saviq: That's a pain (the deleter being part of the pointer type).
[15:54] <sophie-w> sophie-w: (Firefox screen sharing works)
[15:55] <alan_g[m]> alan_g[m]: The alternative is to make `~Logger` public. I see no downside
[16:01] <sophie-w> Out of the box wayvnc works with Mir for a single frame, then stalls (`--disable-input` option is needed, since we don't support virtual pointer yet)
 "The alternative is to make `~..." <- Yeah, that decision comes from pre-c++-11 days, about time to review it ;)
[16:35] <Saviq> OK, good night for today o/
[16:55] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths closed [issue #1316](https://github.com/MirServer/mir/issues/1316): Firefox/Wayland flickers badly
[17:03] <alan_g[m]> And goodnight from me 👋
[18:12] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww opened [pull request #2468](https://github.com/MirServer/mir/pull/2468): Add --add-all-wayland-extensions option
[18:12] -GitHub[m]:#mir-server-
[18:12] -GitHub[m]:#mir-server- > Convenient for development and debugging, as well as running in contexts where all clients are fully trusted
[19:36] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww opened [pull request #2469](https://github.com/MirServer/mir/pull/2469): wlr-screencopy-v: send .damage event when required
[19:36] -GitHub[m]:#mir-server-
[19:36] -GitHub[m]:#mir-server- > The `.copy_with_damage` request still isn't implemented fully (it does not wait for there to be damage or report the damaged area of the screen), but with this change it works well enough for wayvnc to work (albeit with higher than needed CPU load)