| seb128 | goood morning desktopers! | 08:22 |
|---|---|---|
| lissyx | seb128, hello | 08:23 |
| seb128 | lissyx, hey, how are you today? | 08:24 |
| lissyx | can you try to run a nightly build on launchapd? | 08:24 |
| lissyx | https://bugzilla.mozilla.org/show_bug.cgi?id=1855351 | 08:24 |
| -ubottu:#ubuntu-desktop- Mozilla bug 1855351 in Firefox Build System "Perma [tier 2] snap-nightly with failure 'override-build' in part 'firefox' failed with code 1." [--, New] | 08:24 | |
| lissyx | PGO is broken on our side :( | 08:24 |
| lissyx | and I'm stuck bisecting something else so I can't investigate further for now | 08:24 |
| seb128 | lissyx, ack | 08:25 |
| seb128 | started on https://launchpad.net/~mozilla-snaps/firefox/+snap/firefox-snap-nightly | 08:25 |
| seb128 | the previous builds earlier today failed but that seemed like a connectivity issue | 08:26 |
| lissyx | amd64 would have been enough | 08:26 |
| seb128 | lissyx, right, it's a limitation of the webUI which didn't give me the choice (I could have done if from a command line instead and specified the arch but I'm busy with other things and it was easier to do from the browser) | 08:48 |
| lissyx | seb128, https://bugzilla.mozilla.org/show_bug.cgi?id=1855395 | 09:10 |
| -ubottu:#ubuntu-desktop- Mozilla bug 1855395 in Core "Crash in [@ g_cclosure_marshal_BOOLEAN__BOXED_BOXEDv]" [--, New] | 09:10 | |
| lissyx | first reports on sept 20th | 09:11 |
| lissyx | and it's hitting all versions, even a 111.0 ? | 09:11 |
| seb128 | fun | 09:25 |
| seb128 | lissyx, this 111.0 build isn't a snap right? | 09:28 |
| lissyx | I think it might be: https://buildhub.moz.tools/?q=20230314153037 | 09:28 |
| lissyx | or it's a deb | 09:29 |
| lissyx | err no it'rs a snap. | 09:29 |
| lissyx | https://crash-stats.mozilla.org/report/index/fe726f7b-7b7e-455f-8f43-93ff80230921#tab-telemetryenvironment | 09:29 |
| lissyx | distribution id shows canonical-002 | 09:29 |
| seb128 | lissyx, I've difficulties to make sense of it | 09:35 |
| seb128 | firefox is a confined snap and it gets its glib from the sdk | 09:35 |
| seb128 | it's not the switch to core22 since it impacts some old versions like 111 also | 09:36 |
| lissyx | but it started around sept 20th on multiple versions | 09:36 |
| seb128 | and afaik core20/gnome-3-38 didn't have recent glib changes | 09:36 |
| lissyx | wait it shows 20th because it's the limit on the searrch ... | 09:38 |
| lissyx | seb128, https://crash-stats.mozilla.org/signature/?product=Firefox&signature=g_cclosure_marshal_BOOLEAN__BOXED_BOXEDv&date=%3E%3D2023-02-27T08%3A59%3A00.000Z&date=%3C2023-09-27T08%3A59%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=startup_crash&_sort=date&_sort=&page=1 | 09:39 |
| lissyx | seb128, but still crashes at the same time on different versions | 09:39 |
| seb128 | lissyx, so the oldest report is on 2023-06-20? | 09:44 |
| lissyx | yes | 09:44 |
| lissyx | see the link | 09:44 |
| lissyx | multiple versions affected at the same time | 09:44 |
| seb128 | lissyx, which is around the time of that security update, https://launchpad.net/ubuntu/+source/glib2.0/2.64.6-1~ubuntu20.04.6 | 09:44 |
| seb128 | I wonder if there is either some regression in that glib fix | 09:45 |
| seb128 | or if firefox is doing something stupid with glib which happened to work before but doesn't anymore after the fix | 09:45 |
| seb128 | anyway my guess would be that it has to do with the glib changes from that upload (it was a security fix issues to the different Ubuntu series and which would have been picked up by a gnome sdk rebuild) | 09:46 |
| lissyx | the stacks I can see on several bugs shows different paths from libxul | 09:46 |
| lissyx | so I'm a bit skeptical we are doing something wrong | 09:47 |
| seb128 | lissyx, can you see from the metrics if there are reports from core22 versions of the snap? | 09:47 |
| lissyx | seb128, do you have the dates for uploads to 23.04 and 22.04 ? | 09:47 |
| seb128 | lissyx, https://launchpad.net/ubuntu/+source/glib2.0 | 09:47 |
| seb128 | 2023-06-14 was the date for 20.04 and 22.04 | 09:48 |
| seb128 | there was no upload to 23.04 but maybe that's because the version there already had the fix? | 09:48 |
| seb128 | also those are updates to the deb, we would need to see when the sdk snaps were rebuild to pick up that security update | 09:48 |
| lissyx | this lack of public history :( | 09:49 |
| lissyx | seb128, https://crash-stats.mozilla.org/report/index/8bc01b5d-fc81-46a4-b7aa-b324d0230620#tab-modules | 09:51 |
| lissyx | we have links to the debug symbols of libglib and others | 09:51 |
| seb128 | lissyx, the build dates of https://code.launchpad.net/~desktop-snappers/+snap/gnome-3-38-2004 suggest we didn't have a sdk update to include the new glib before July-8 | 10:03 |
| seb128 | I'm a bit puzzled | 10:04 |
| lissyx | seb128, unrelated, but it looks like pipewire-bin and pipewire-pulse can't be co-installed for amd64/arm64 | 10:24 |
| lissyx | https://treeherder.mozilla.org/logviewer?job_id=430461964&repo=try&lineNumber=266-271 | 10:24 |
| lissyx | others seems fine | 10:24 |
| lissyx | aptitude might be able to do it? | 10:28 |
| lissyx | seb128, for the PGO, it looks like I reproduced locally and that after removing `--enable-linker=gold` as suggested by glandium, I dont have a problem anymore: https://phabricator.services.mozilla.com/D189362 | 10:35 |
| seb128 | lissyx, the nightly job I retried also failed, https://launchpad.net/~mozilla-snaps/firefox/+snap/firefox-snap-nightly/+build/2242499 | 10:47 |
| seb128 | lissyx, pipewire, seems like a multiarch issue in the package maybe, worth reporting to Debian or on launchpad | 10:48 |
| lissyx | seb128, awesome, the pgo failure is the same as us and my desktop repro | 11:05 |
| seb128 | lissyx, is building without gold what we usually want or just a temporary workaround for that problem? | 11:44 |
| lissyx | seb128, I dont know | 11:44 |
| lissyx | seb128, glandium told me it's not required anymore | 11:44 |
| lissyx | > glandium | 11:45 |
| lissyx | --enable-linker=gold should be removed | 11:45 |
| lissyx | I can ask him more details, but he's in japan so wont get the answer now | 11:45 |
| seb128 | I would still be interested by the reply even if it's later | 11:45 |
| seb128 | we can disable for now but I want to know if that's something we should keep or only do temporarly | 11:45 |
| lissyx | it's not mentionned anymore on https://firefox-source-docs.mozilla.org/build/buildsystem/pgo.html | 11:47 |
| seb128 | I wonder why Olivier used gold to start with | 11:47 |
| lissyx | seb128, --enable-lto=cross is also not referred to anymore in any of our build config | 12:11 |
| lissyx | seb128, and the try opt build failed on linkage, while try debug succeeded (we remove this flag on debug) | 12:11 |
| lissyx | seb128, cf https://treeherder.mozilla.org/jobs?repo=try&revision=c31950211c4f2556ffe31180835a198e6b95c2a7 | 12:12 |
| lissyx | so maybe we need to just keep MOZ_PGO=1 | 12:12 |
| lissyx | (as the doc states, btw) | 12:12 |
| KGB-2 | nautilus upstream/latest 395768f Jeremy Bicha * pushed 13 commits (first 5 follow) * https://deb.li/3g52g | 12:44 |
| KGB-0 | nautilus pristine-tar 00ae195 Jeremy Bícha nautilus_45.0.orig.tar.xz.delta nautilus_45.0.orig.tar.xz.id * pristine-tar data for nautilus_45.0.orig.tar.xz * https://deb.li/k16h | 12:44 |
| KGB-2 | nautilus upstream/latest b7e51d3 Changwoo Ryu po/ko.po * Update Korean translation * https://deb.li/3hCh4 | 12:44 |
| KGB-2 | nautilus upstream/latest b10b186 Balázs Úr po/hu.po * Update Hungarian translation * https://deb.li/873M | 12:44 |
| KGB-2 | nautilus upstream/latest be42ce2 Alan Mortensen po/da.po * Update Danish translation * https://deb.li/3o1cj | 12:44 |
| KGB-2 | nautilus upstream/latest 48181e3 Changwoo Ryu po/ko.po * Update Korean translation * https://deb.li/S1TN | 12:45 |
| KGB-2 | nautilus upstream/latest c2bbb6c Alan Mortensen po/da.po * Update Danish translation * https://deb.li/3z3Cx | 12:45 |
| KGB-0 | glib pipeline Simon McVittie 584331 * pending (extract-source: pending; build: created; build i386: created; build armhf: created; build arm64: created; build source: created; test-build-any: created; test-build-all: created; reprotest: created; lintian: created; autopkgtest: created; blhc: created; piuparts: created) | 13:39 |
| KGB-0 | glib pipeline Simon McVittie 584331 * running (extract-source: running; build: created; build i386: created; build armhf: created; build arm64: created; build source: created; test-build-any: created; test-build-all: created; reprotest: created; lintian: created; autopkgtest: created; blhc: created; piuparts: created) | 13:40 |
| lissyx | seb128, bandali, so, we can get armhf and arm64 cross-built even on our current docker setup: https://treeherder.mozilla.org/jobs?repo=try&revision=b0272dc3322ea7fb826c629872da2b02e01515ad | 14:16 |
| seb128 | great | 14:16 |
| lissyx | it's a bit hacky, and hopefully I should get provided workers without docker soon | 14:16 |
| KGB-0 | glib pipeline Simon McVittie 584331 * [45 minutes and 13 seconds] failed (extract-source: success; build: success; build i386: success; build armhf: failed; build arm64: failed; build source: success; test-build-any: skipped; test-build-all: skipped; reprotest: success; lintian: failed; autopkgtest: success; blhc: success; piuparts: failed) | 15:00 |
| KGB-0 | GNOME / nautilus builds Jeremy Bicha * Build #4745908 (extract-source) stage: provisioning, status: created | 15:16 |
| KGB-2 | GNOME / nautilus builds Jeremy Bicha * Build #4745910 (build i386) stage: build, status: created | 15:16 |
| KGB-0 | GNOME / nautilus builds Jeremy Bicha * Build #4745911 (build source) stage: build, status: created | 15:16 |
| KGB-2 | GNOME / nautilus builds Jeremy Bicha * Build #4745915 (reprotest) stage: test, status: created | 15:16 |
| KGB-0 | GNOME / nautilus builds Jeremy Bicha * Build #4745912 (test-build-any) stage: test, status: created | 15:16 |
| KGB-2 | GNOME / nautilus builds Jeremy Bicha * Build #4745918 (blhc) stage: test, status: created | 15:16 |
| KGB-0 | GNOME / nautilus builds Jeremy Bicha * Build #4745914 (test-crossbuild-arm64) stage: test, status: created | 15:16 |
| KGB-0 | GNOME / nautilus builds Jeremy Bicha * Build #4745913 (test-build-all) stage: test, status: created | 15:16 |
| KGB-2 | nautilus pipeline Jeremy Bicha 584352 * running (extract-source: running; build: created; build i386: created; build source: created; test-build-any: created; test-build-all: created; test-crossbuild-arm64: created; reprotest: created; lintian: created; autopkgtest: created; blhc: created; piuparts: created) | 15:16 |
| KGB-0 | GNOME / nautilus builds Jeremy Bicha * Build #4745916 (lintian) stage: test, status: created | 15:16 |
| KGB-0 | GNOME / nautilus builds Jeremy Bicha * Build #4745919 (piuparts) stage: test, status: created | 15:17 |
| KGB-2 | nautilus pipeline Jeremy Bicha 584352 * [21 minutes and 51 seconds] failed (extract-source: success; build: success; build i386: success; build source: success; test-build-any: failed; test-build-all: success; test-crossbuild-arm64: failed; reprotest: failed; lintian: success; autopkgtest: success; blhc: success; piuparts: success) | 15:38 |
| lissyx | bandali, can we merge https://github.com/canonical/firefox-snap/pull/29 to unblock https://bugzilla.mozilla.org/show_bug.cgi?id=1855351 ? | 15:52 |
| -ubottu:#ubuntu-desktop- Pull 29 in canonical/firefox-snap "Bug1855351 pog failure" [Open] | 15:52 | |
| -ubottu:#ubuntu-desktop- Mozilla bug 1855351 in Firefox Build System "Perma [tier 2] snap-nightly with failure 'override-build' in part 'firefox' failed with code 1." [--, New] | 15:52 | |
| KGB-0 | nautilus pipeline Jeremy Bicha 584352 * [21 minutes and 51 seconds] running (extract-source: success; build: success; build i386: success; build source: success; test-build-all: success; lintian: success; autopkgtest: success; blhc: success; piuparts: success; test-build-any: pending; test-crossbuild-arm64: pending; reprotest: pending) | 15:53 |
| bandali | lissyx, sure, now done, thank you! | 16:08 |
| lissyx | :p | 16:08 |
| KGB-0 | gnome-shell pipeline Simon McVittie 584373 * pending (extract-source: pending; build: created; build i386: created; build source: created; test-build-any: created; test-build-all: created; test-crossbuild-arm64: created; reprotest: created; lintian: created; autopkgtest: created; blhc: created; piuparts: created) | 16:34 |
| KGB-0 | gnome-shell pipeline Simon McVittie 584374 * pending (extract-source: pending; build: created; build i386: created; build source: created; test-build-any: created; test-build-all: created; test-crossbuild-arm64: created; reprotest: created; lintian: created; autopkgtest: created; blhc: created; piuparts: created) | 16:38 |
| lissyx | bandali, I'm abou to go to sleep, but I could use your input on https://bugzilla.mozilla.org/show_bug.cgi?id=1854374 ; this is reported by someone using snap package on kde/opensuse and he always hit weird issues, I'm skeptical of the KDE/OpenSUSE integration itself ... | 20:13 |
| -ubottu:#ubuntu-desktop- Mozilla bug 1854374 in Core "'(null)' displayed instead of 'Firefox' in Snap Location Access permission prompt." [--, Unconfirmed] | 20:13 | |
| PLTrace | hello! can somebody please help me diagnosing a problem? When using a plain "old" Ubuntu 22.04 live pen I'm able to see my Brother MFC-J6530DW printer and use it (both printer and scanner). From my installed version, after some update which I'm unable to identify, it suddenly stopped being found. I'm using it in a "driverless" way. Any ideas on how | 23:23 |
| PLTrace | to diagnose it? | 23:23 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!