![]() Neither snap changes, snap change or snap tasks is helpful while changes are in flight:-ĥ427 Doing today at 23:46 GMT - Refresh snaps "syncthing", "youtube-dl", "gedit", "gnome-characters", "vokoscreen-ng", "core", "fluffychat", "mame", "beebeep", "chromium", "mindustry", "waterfox-snap", "pick-colour-picker", "obs-studio", "simplenote", "thelounge", "qownnotes", "epicpinball", "spt", "opentoonz", "slack", "helm", "review-tools", "code", "wine-platform-runtime", "x16emu", "wire", "irccloud-desktop", "brackets", "irssi", "stress-ng", "insomnia", "lemmings-christmas", "starship", "makemkv", "mdl", "inkscape", "mumble", "minetest", "spek", "mgba", "libreoffice", "cobalt", "gitter-desktop", "irccloud", "olivia", "ubuntu-mate-welcome" The only way I can see that changes are actually happening is having dmesg -Tw running in another terminal and see apparmor changes being applied. The above example (to me) indicates a further reason our snap logging needs a re-think.Īs I understand it snap tasks is just a synonym for snap changes and as such is equally blocked and unhelpful while changes are in flight. Given there are no log files for me to tail (think /var/log/dpkg.log) to see what’s going on, is it time to re-think the way we log changes? I have previously lamented the problem that snap changes is held in memory and thus lost after a while, so there’s no historical archive of changes (e.g. So, given snap changes and snap change (changeid) are likely to be used to answer the questions “What changed on my system recently?” and “What’s changing right now?” it feels like it can only be serviceably used for the former, not the latter. INFO cannot auto-connect slot core:avahi-observe to plug firefox:avahi-observe, candidates found: avahi:avahi-observe, core:avahi-observeĬonsider re-refresh of "qownnotes", "azimuth", "gnome-3-32-1804", "lxd", "chromium", "rslauncher", "wire", "gtk2-common-themes", "youtube-dl", "waterfox-snap", "mumble", "ddgr", "epicpinball", "figma-linux", "minetest", "olivia", "opensurge", "core", "doctl", "review-tools", "thunderbird", "caprine", "lemmings-christmas", "starship", "simplenote", "gedit", "inkscape", "mame", "shellcheck", "mgba", "gnome-characters", "hugo", "obs-studio", "yakyak", "mindustry" INFO cannot auto-connect slot core:avahi-observe to plug remmina:avahi-observe, candidates found: avahi:avahi-observe, core:avahi-observe Now it’s finished, snap change (changeid) is fast again: time snap change 5223 | tail total-cpu-usage-dsk/total-net/total-paging-system. You did not select any stats, using -cdngy by default. Granted, the system is quite busy while these snaps are refreshing… dstat ![]() The output of snap change 5223 is too long for this forum, so it’s here ![]() ![]() 5223 Doing today at 08:46 GMT - Refresh snaps "qownnotes", "azimuth", "gnome-3-32-1804", "lxd", "chromium", "rslauncher", "wire", "gtk2-common-themes", "youtube-dl", "waterfox-snap", "mumble", "ddgr", "epicpinball", "figma-linux", "minetest", "olivia", "opensurge", "core", "doctl", "review-tools", "thunderbird", "caprine", "lemmings-christmas", "starship", "simplenote", "gedit", "inkscape", "mame", "shellcheck", "mgba", "gnome-characters", "hugo", "obs-studio", "yakyak", snap change time snap change 5223 It took 2 mins 41 seconds to return the output of the snap change (changeid) command. I wanted to see what’s happening, so I thought I’d use snap changes and snap change (changeid). It’s still chugging away (as you can see, it’s refreshing quite a few snaps). Not sure this is a bug or just my laptop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |