Doesn't work with GNOME 3.38

[tim77]

How to reproduce:

flatpak install flathub org.gnome.Logs

Actual results:

System version of package (RPM):

---

OS: Fedora 33
systemd: 246.6-3
flatpak: 1.8.2

[Eonfge]

Sorry for not coming back to you any sooner, but I found it difficult to reproduce the issue. Fear no though, For I have no stumbled into it myself.

[kevin@kevin-at-fedora ~]$ flatpak run org.gnome.Logs 
Gtk-Message: 16:33:04.599: Failed to load module "canberra-gtk-module"
Gtk-Message: 16:33:04.599: Failed to load module "pk-gtk-module"
Gtk-Message: 16:33:04.600: Failed to load module "canberra-gtk-module"
Gtk-Message: 16:33:04.600: Failed to load module "pk-gtk-module"

** (gnome-logs:2): WARNING **: 16:33:04.817: Error retrieving the sender timestamps: Cannot assign requested address

** (gnome-logs:2): WARNING **: 16:33:09.418: Error retrieving the sender timestamps: Cannot assign requested address

** (gnome-logs:2): WARNING **: 16:33:09.946: Error retrieving the sender timestamps: Cannot assign requested address

** (gnome-logs:2): WARNING **: 16:36:02.984: Error retrieving the sender timestamps: Cannot assign requested address

** (gnome-logs:2): WARNING **: 16:36:04.978: Error retrieving the sender timestamps: Cannot assign requested address

I can tell you that it does (still) work on other devices that I use, so it must be something system specific

[Mershl]

Just tested on a fresh Fedora 33 installation (btrfs) vs an upgraded ext4 installation. The issue is reproducible on the fresh btrfs system, NOT the ext4 system. May it be related to btrfs?

[Eonfge]

I'm running on Fedora 33, using an LVM ext4 partition. I've been doing in-place updates of Fedora since Fedora 30, so I doubt that it's related.

[Mershl]

I'm running on Fedora 33, using an LVM ext4 partition. I've been doing in-place updates of Fedora since Fedora 30, so I doubt that it's related.

Just to be sure and avoid a misunderstanding. I could ONLY reproduce the issue desribed by tim77 on Fedora 33 with btrfs.
On Fedora 33 with ext4 org.gnome.Logs from flathub is working as expected.

[tim77]

Sorry for delay here. Can't add anything useful at this moment except one more user have the same issue on F33 as well - cc: @ivan-tretyak.

I am on btrfs as well.

[x80486]

Logs is also showing nothing for me:

May 29 07:24:41 uplink dbus-daemon[1017]: [session uid=1000 pid=1017] Activating service name='org.gnome.Logs' requested by ':1.11' (uid=1000 pid=1063 comm="/usr/bin/gnome-shell ")
May 29 07:24:41 uplink systemd[445]: Started app-flatpak-org.gnome.Logs-50743.scope.
May 29 07:24:41 uplink dbus-daemon[1017]: [session uid=1000 pid=1017] Successfully activated service 'org.gnome.Logs'
May 29 07:24:41 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:24:41 uplink gnome-shell[1063]: Can't update stage views actor Gjs_ui_windowPreview_WindowPreview is on because it needs an allocation.
May 29 07:24:41 uplink gnome-shell[1063]: Can't update stage views actor ClutterActor is on because it needs an allocation.
May 29 07:24:41 uplink gnome-shell[1063]: Can't update stage views actor ClutterClone is on because it needs an allocation.
May 29 07:24:41 uplink gnome-shell[1063]: Can't update stage views actor StIcon is on because it needs an allocation.
May 29 07:24:41 uplink gnome-shell[1063]: Can't update stage views actor ClutterActor is on because it needs an allocation.
May 29 07:24:41 uplink gnome-shell[1063]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed
May 29 07:24:48 uplink kernel: [UFW AUDIT] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=47857 DF PROTO=UDP SPT=56893 DPT=53 LEN=44 
May 29 07:24:48 uplink kernel: [UFW ALLOW] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=47857 DF PROTO=UDP SPT=56893 DPT=53 LEN=44 
May 29 07:24:48 uplink kernel: [UFW AUDIT] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=47858 DF PROTO=UDP SPT=56893 DPT=53 LEN=44 
May 29 07:24:48 uplink kernel: [UFW ALLOW] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=47858 DF PROTO=UDP SPT=56893 DPT=53 LEN=44 
May 29 07:24:48 uplink kernel: [UFW AUDIT] IN= OUT=enp3s0 SRC=192.168.0.17 DST=95.216.195.133 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=48408 DF PROTO=TCP SPT=37894 DPT=80 WINDOW=64240 RES=0x00 SYN URGP=0 
May 29 07:24:48 uplink kernel: [UFW ALLOW] IN= OUT=enp3s0 SRC=192.168.0.17 DST=95.216.195.133 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=48408 DF PROTO=TCP SPT=37894 DPT=80 WINDOW=64240 RES=0x00 SYN URGP=0 
May 29 07:24:54 uplink kernel: [UFW AUDIT] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=48434 DF PROTO=UDP SPT=34637 DPT=53 LEN=44 
May 29 07:24:54 uplink kernel: [UFW ALLOW] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=48434 DF PROTO=UDP SPT=34637 DPT=53 LEN=44 
May 29 07:24:54 uplink kernel: [UFW AUDIT] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=48435 DF PROTO=UDP SPT=34637 DPT=53 LEN=44 
May 29 07:24:54 uplink kernel: [UFW ALLOW] IN= OUT=enp3s0 SRC=192.168.0.17 DST=1.1.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=48435 DF PROTO=UDP SPT=34637 DPT=53 LEN=44 
May 29 07:24:54 uplink kernel: [UFW AUDIT] IN= OUT=enp3s0 SRC=2600:8806:0601:d300:64a9:05d9:8a11:3d50 DST=2a01:04f9:c010:2636:0000:0000:0000:0001 LEN=80 TC=0 HOPLIMIT=64 FLOWLBL=1007609 PROTO=TCP SPT=53364 DPT=80 WINDOW=64800 RES=0x00 SYN URGP=0 
May 29 07:24:54 uplink kernel: [UFW ALLOW] IN= OUT=enp3s0 SRC=2600:8806:0601:d300:64a9:05d9:8a11:3d50 DST=2a01:04f9:c010:2636:0000:0000:0000:0001 LEN=80 TC=0 HOPLIMIT=64 FLOWLBL=1007609 PROTO=TCP SPT=53364 DPT=80 WINDOW=64800 RES=0x00 SYN URGP=0 
May 29 07:24:55 uplink kernel: [UFW AUDIT] IN= OUT=enp3s0 SRC=192.168.0.17 DST=239.255.255.250 LEN=194 TOS=0x00 PREC=0x00 TTL=1 ID=61898 DF PROTO=UDP SPT=58448 DPT=1900 LEN=174 
May 29 07:24:55 uplink kernel: [UFW ALLOW] IN= OUT=enp3s0 SRC=192.168.0.17 DST=239.255.255.250 LEN=194 TOS=0x00 PREC=0x00 TTL=1 ID=61898 DF PROTO=UDP SPT=58448 DPT=1900 LEN=174 
May 29 07:24:55 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:24:57 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:24:59 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:01 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:02 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:04 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:05 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:06 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:06 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:07 uplink gnome-logs[50752]: Error retrieving the sender timestamps: Cannot assign requested address
May 29 07:25:12 uplink systemd[445]: app-flatpak-org.gnome.Logs-50743.scope: Deactivated successfully.
May 29 07:25:12 uplink systemd[445]: app-flatpak-org.gnome.Logs-50743.scope: Consumed 1.115s CPU time.

That's me clicking all the options on the left 😅

I'm under Arch Linux Linux uplink 5.10.40-1-lts #1 SMP Wed, 26 May 2021 11:47:57 +0000 x86_64 GNU/Linux with GNOME 40.1.0.

Probably update the runtime to 40?

[nedrichards]

I've upgraded to the 41 runtime. This works for me in local testing on Endless 4

[tim77]

I'll test this ASAP in Fedora 34...

[Mershl]

Can confirm. Issue is fixed on Fedora 34 (btrfs) with the latest update.

[tim77]

Works for me on Fedora 35. I hope it safe to close now. TY @nedrichards

[Eonfge]

Be a bit careful. We previously couldn't identify the cause, so other users with other setups might still have this issue: I never had this issue on my desktop, but I did have this issue on my work-laptop.