#18

Heads-up: Geary bug is w fixed, but Maps in Flatpak still cannot load anything. And I’ve somehow missed the fact that Weather cannot load anything as well.

#19

Does anyone have experiences with f29 silverblue? How is it working? I have still f28 atomic-workstation-ostree

#20

If possible let’s try to keep comments on topic so that it doesn’t get too chatty and people stop reading.

#21

okay! I’ll keep this in mind

1 Like
#22

So, as far as I can see, things that look like part of the operating system - whether Clocks or Nautilus - need to stay in the Silverblue image.

i have a hard time seeing Clocks or Weather as ‘part of the OS’.

The Maps breakage is probably due to the network monitor issues that are hopefully finally fixed, in this weeks portal and glib releases.

And yelp is inside the gnome runtime, so Help works fine in flatpaked gnome apps (just tried here with Boxes - works).

#23

As described in the original post, Clocks and Polari integrate with gnome-shell, which flatpak-ed apps don’t do. (Though that can probably be fixed). And while Help works fine in flatpaked apps, it doesn’t work with host apps, and also doesn’t pop up after initial setup. (Which maybe could also work with flatpaked yelp)

#24

They do, but the absence of that integration is not breaking either the shell or the app. The integration
breaks because the shell relies on seeing the apps’ settings schemas, which are not exported by Flatpak.

Arguably, settings that are shared between the shell and apps like this are not app-specific in the first place, and should be in a desktop-wide shared schema. In the past, these things could just be muddled through.
The proper isolation of Flatpak exposes this for what it is: a hack

This is worth filing a bug about. We should fix up the first-login experience, one way or another.

#25

I just submitted gnome-font-viewer on flathub. It was easy! Maybe somebody else wants to get their hands dirty with some of the other candidates ?

#26

Oh, I see.

Hmm, where to? Silverblue, Fedora, GNOME?

#27

It is a Silverblue issue, so https://pagure.io/teamsilverblue/issues would be good.

#28

Done: https://pagure.io/teamsilverblue/issue/31

#29

Slightly off topic - should we file all Silverblue issues on Pagure or on the Red Hat Bugzilla? I’ve got a WiFi issue that exists already in Bugzilla for Fedora 28 Workstation on my Silverblue 28 install too. I have no plans to bring up regular Fedora 28 and troubleshoot it but I would do that on Silverblue.

#30

If the issue is specifc to Sivlerblue only, I’d file it on the Pagure tracker. If the issue affects traditional Workstation and Silverblue, I’d use Bugzilla.

#31

OK … in this case it affects both - and it’s already in Bugzilla for Fedora 28 (https://bugzilla.redhat.com/show_bug.cgi?id=1591162). So I’ll post there.

#32

Someone on IRC has reported that their system wouldn’t boot after a rebase to 29 because lvm2 was removed from the system image. Was this intentional or an accident?

#33

lvm2 was removed from the system image

Wasn’t intentional, see https://pagure.io/workstation-ostree-config/c/75314ee3d7d2655cc441addbe1f862a4aaaf0434?branch=master
Should be fixed tomorrow.

#34

That was me. :upside_down_face:

#35

@mclasen Would it be possible to have ansible added to the base image please for Fedora SB29?

1 Like
#36

The shell extensions of /usr/share/gnome-shell/extensions/ cause some trouble because of being RO in SB. Can these be blacklisted by for example [0]? There already is gnome-shell-extension-background-logo mentioned. (Although this is present on my F29SB system…?)

[0] https://pagure.io/workstation-ostree-config/blob/04c703cede3d8c2e7c41bc94ea98951dcdae70b4/f/comps-sync-blacklist.yml

#37

This is unrelated, and you can disable any extension regardless of where it’s installed anyway.