cpaelzer | hi party people, I found that I get multiple warnings like these in my journal | 12:25 |
---|---|---|
cpaelzer | update-notifier.desktop[9661]: [9661:9661:1122/132442.703817:ERROR:page_load_metrics_update_dispatcher.cc(120)] Invalid parse_blocked_on_script_execution_duration 0.731 s for parse duration 0.636 s | 12:25 |
cpaelzer | search for this leads me to chromium https://chromium.googlesource.com/chromium/src/+/66.0.3359.158/chrome/browser/page_load_metrics/page_load_metrics_update_dispatcher.cc#108 and probably anything that renders via it | 12:26 |
cpaelzer | sadly even killing update-notifier (not yet restarting) makes this not go away | 12:26 |
cpaelzer | Since Nov 15th I have that way picked up 583175 of such log entries which is a bit too frequent for my taste | 12:27 |
cpaelzer | any suggestions what to check/restart/debug? | 12:27 |
seb128 | hey cpaelzer! Urg, that seems problematic indeed | 12:29 |
cpaelzer | tracking the pid it is actually chrome itself, maybe update-notifier is a red herring | 12:29 |
cpaelzer | restarting that ... | 12:29 |
seb128 | right, I do wonder what update-notifier has to do with that | 12:30 |
cpaelzer | ok, restarting chrome has stopped the flood | 12:30 |
seb128 | I will check with Nathan (he doesn't seem to be on IRC atm) | 12:30 |
cpaelzer | the puzzle I'd like to understand is why it reported that as update-notifier.desktop in the journal | 12:31 |
cpaelzer | 0 1000 8559 7280 20 0 498100 23012 do_pol Sl ? 0:28 | \_ update-notifier | 12:31 |
cpaelzer | 4 1000 9661 9660 20 0 35126560 717728 do_pol SLl ? 395:06 | \_ /opt/google/chrome/chrome | 12:31 |
seb128 | I would like to understand that as well | 12:31 |
cpaelzer | I can see that 9661 was chromes pid and update-notifier was 8559 | 12:32 |
cpaelzer | but the log above says ... update-notifier.desktop[9661] | 12:32 |
seb128 | is systemd/journalctl getting confused about pids somehow? | 12:33 |
cpaelzer | for what it is worth, this is reliable | 12:33 |
cpaelzer | the new pid of chrome is this | 12:33 |
cpaelzer | 4 1000 4100307 7049 20 0 34370744 444984 do_pol SLl ? 0:12 \_ /opt/google/chrome/chrome --origin-trial-disabled-features=WebGPU --restart | 12:33 |
cpaelzer | and on restart it emitted some to the log | 12:33 |
cpaelzer | Nov 22 13:29:20 Keschdeichel update-notifier.desktop[4100307]: [4100307:4100307:1122/132920.667640:ERROR:CONSOLE(1)] "Uncaught SyntaxError: Unexpected token '<'", source: chrome://version//about_version.js (1) | 12:33 |
cpaelzer | so it declared itself as "update-notifier.desktop" again | 12:33 |
seb128 | cpaelzer, https://github.com/systemd/systemd/issues/28499 | 12:34 |
-ubottu:#ubuntu-desktop- Issue 28499 in systemd/systemd "Some log messages reported with the wrong sender in the journal" [Open] | 12:34 | |
seb128 | not much details which are of use there though | 12:34 |
cpaelzer | could be it, yep | 12:34 |
seb128 | but it seems similar | 12:35 |
seb128 | so I guess the conclusion is that chrome is spamming your log and systemd for some reason matches the wrong pid for those messages | 12:36 |
seb128 | I will check with Nathan if he's aware of those log spams/if he knows of a workaround | 12:37 |
cpaelzer | from journalctl -v it not only believes it is update-notifier | 13:42 |
cpaelzer | SYSLOG_IDENTIFIER=update-notifier.desktop | 13:42 |
cpaelzer | but also groups it in the same scope | 13:43 |
cpaelzer | _SYSTEMD_CGROUP=/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-update\x2dnotifier-8559.scope | 13:43 |
cpaelzer | _SYSTEMD_USER_UNIT=app-gnome-update\x2dnotifier-8559.scope | 13:43 |
cpaelzer | systemd-cgls lists chrome just there, under app-gnome-update\x2dnotifier-8559.scope | 13:45 |
cpaelzer | so the question is how did it get there in the first place | 13:46 |
lissyx | bandali, seb128, can you verify the build process ? https://bugzilla.mozilla.org/show_bug.cgi?id=1866057 | 13:58 |
-ubottu:#ubuntu-desktop- Mozilla bug 1866057 in Testing "Snap upstream builds missing SourceRepository / SourceStamp" [--, New] | 13:58 | |
lissyx | I'm stretched thin those days, and this is making mozregression broken :( | 13:59 |
lissyx | and we dont have access to the build dir from the launchpad builds to investigate what was done there | 13:59 |
seb128 | lissyx, I've no idea what SourceRepository and SourceStamp are and I'm also quite busy with other things | 14:00 |
seb128 | bandali, ^ could you perhaps check that? | 14:00 |
KGB-X | tracker-miners ubuntu/jammy 9da215c Jeremy Bícha (41 files in 8 dirs) * Import Upstream version 3.3.3 * https://deb.li/iUBSh | 14:43 |
KGB-X | tracker-miners ubuntu/jammy b2616de Marc Deslauriers (47 files in 10 dirs) * Import Debian changes 3.3.3-0ubuntu0.20.04.1 * https://deb.li/lrkN | 14:43 |
KGB-X | tracker-miners signed tags b010d86 Jeremy Bicha ubuntu/3.3.3-0ubuntu0.20.04.1 * tracker-miners Debian release 3.3.3-0ubuntu0.20.04.1 * https://deb.li/5bFg | 14:43 |
KGB-X | tracker-miners ubuntu/jammy ab6071a Jeremy Bícha debian/gbp.conf * Branch for jammy * https://deb.li/3XXNl | 14:44 |
KGB-X | tracker-miners signed tags ee9ed76 Jeremy Bicha ubuntu/3.4.6-0ubuntu0.23.10.1 * tracker-miners Debian release 3.4.6-0ubuntu0.23.10.1 * https://deb.li/qlyD | 14:58 |
KGB-X | tracker-miners ubuntu/mantic 3717711 Jeremy Bicha * pushed 39 commits (first 5 follow) * https://deb.li/38mDz | 14:59 |
KGB-X | tracker-miners ubuntu/mantic 3a46114 Carlos Garnacho NEWS meson.build * Release 3.4.5 * https://deb.li/HmGl | 14:59 |
KGB-X | tracker-miners ubuntu/mantic 2176094 Jeremy Bícha (40 files in 7 dirs) * New upstream version 3.4.5 * https://deb.li/3R4jI | 14:59 |
KGB-X | tracker-miners ubuntu/mantic f3f7b54 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add custom rules through a define * https://deb.li/97Gn | 14:59 |
KGB-X | tracker-miners ubuntu/mantic 9aa5d26 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Improve "bail out" error loading seccomp rules * https://deb.li/diZC | 15:00 |
KGB-X | tracker-miners ubuntu/mantic 338a15e Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add more seccomp rules * https://deb.li/31CoG | 15:00 |
KGB-X | tracker-miners ubuntu/mantic ece14df Jeremy Bícha debian/gbp.conf * Branch for mantic * https://deb.li/NoME | 15:00 |
KGB-X | tracker-miners signed tags 804f6b9 Jeremy Bicha ubuntu/3.4.6-0ubuntu0.23.04.1 * Debian release 3.4.6-0ubuntu0.23.04.1 * https://deb.li/i3lRe | 15:02 |
KGB-X | tracker-miners ubuntu/lunar e390e68 Jeremy Bicha * pushed 35 commits (first 5 follow) * https://deb.li/2Nw7 | 15:02 |
KGB-X | tracker-miners ubuntu/lunar 3a46114 Carlos Garnacho NEWS meson.build * Release 3.4.5 * https://deb.li/HmGl | 15:02 |
KGB-X | tracker-miners ubuntu/lunar 2176094 Jeremy Bícha (40 files in 7 dirs) * New upstream version 3.4.5 * https://deb.li/3R4jI | 15:02 |
KGB-X | tracker-miners ubuntu/lunar f3f7b54 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add custom rules through a define * https://deb.li/97Gn | 15:02 |
KGB-X | tracker-miners ubuntu/lunar 9aa5d26 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Improve "bail out" error loading seccomp rules * https://deb.li/diZC | 15:02 |
KGB-X | tracker-miners ubuntu/lunar 338a15e Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add more seccomp rules * https://deb.li/31CoG | 15:02 |
KGB-X | tracker-miners ubuntu/lunar b3a4619 Jeremy Bícha debian/gbp.conf * debian/gbp.conf: Update upstream-branch name * https://deb.li/3HlYd | 15:03 |
KGB-X | tracker-miners ubuntu/mantic 14ca62e Jeremy Bícha debian/gbp.conf * debian/gbp.conf: Update upstream branch name * https://deb.li/V4rF | 15:03 |
KGB-X | tracker-miners signed tags 228697d Jeremy Bicha upstream/3.3.3 * Upstream version 3.3.3 * https://deb.li/3NRT1 | 15:04 |
KGB-X | tracker-miners upstream/3.3.x 9da215c Jeremy Bícha (41 files in 8 dirs) * Import Upstream version 3.3.3 * https://deb.li/iUBSh | 15:04 |
KGB-X | tracker-miners pristine-tar 757662d Jeremy Bícha tracker-miners_3.3.3.orig.tar.xz.delta tracker-miners_3.3.3.orig.tar.xz.id * pristine-tar data for tracker-miners_3.3.3.orig.tar.xz * https://deb.li/RLth | 15:04 |
KGB-X | tracker-miners ubuntu/jammy 79d47d5 Jeremy Bícha debian/gbp.conf * debian/gbp.conf: Update upstream branch name * https://deb.li/3zoBc | 15:05 |
=== JanC is now known as Guest2081 | ||
=== JanC_ is now known as JanC | ||
lissyx | seb128, bandali, ok it looks to affect only nightlies, so I suspect it is because we are removing .hg directory | 17:24 |
lissyx | I'm testing this right now | 17:24 |
lissyx | bandali, https://github.com/canonical/firefox-snap/pull/38 | 20:40 |
-ubottu:#ubuntu-desktop- Pull 38 in canonical/firefox-snap "Bug 1866057 - Force MOZ_SOURCE_REPO/CHANGESET on Snap Nightly" [Open] | 20:40 | |
lissyx | bandali, I'm runnign a build but I wont have time to test before tomorrow, if you can check on your side this patch | 20:41 |
lissyx | bandali, verify in about:buildconfig, you should see a link to hg repo + rev (you can see it on beta/release) | 20:41 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!