desktop October 2019

desktop@lists.fedoraproject.org

16 participants
16 discussions

Initial F31 flatpak runtime and further plans
by Kalev Lember 23 Nov '19

23 Nov '19

Hi all, I've built an initial version of F31 flatpak runtime and SDK, and built a set of GNOME flatpaks against it. At the same time, I've also updated them to 3.34.x. I'll build more of the apps against F31 runtime in the coming days. Right now the set of apps include: org.gnome.Baobab org.gnome.Calculator org.gnome.Calendar org.gnome.Characters org.gnome.clocks org.gnome.Contacts org.gnome.eog org.gnome.Evince org.gnome.font-viewer org.gnome.gedit org.gnome.Logs org.gnome.Maps org.gnome.Screenshot org.gnome.Weather This set was chosen for the initial port because this is what we want to preinstall on Silverblue. This should hopefully go stable around the same time as F31 goes live, so people should be able to install 3.34 flatpaks on F31. Karma in Bodhi and testing welcome: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2019-addc7ab077 Right now they are available in the fedora-testing flatpak repository. To enable the remote, 'flatpak remote-modify --enable fedora-testing' or if you don't have the remote for some reasons, then: 'flatpak remote-add fedora-testing oci+https://registry.fedoraproject.org#testing' Thanks, Kalev

2 1

flatpak local storage location
by Chris Murphy 06 Nov '19

06 Nov '19

The subject of disk space and flatpaks came up in the most recent workstation meeting, and I'd like to separately discuss that in this thread before creating a flatpak issue. The full log: https://meetbot.fedoraproject.org/teams/workstation/workstation.2019-10-28-… Excerpts: 13:16:07 <langdon> allocating enough disk if you have your drive sliced up is tough 13:16:36 <Son_Goku> and yeah, the disk space issue is a huge problem ... 13:16:47 <kalev> "the disk space issue" ? 13:16:58 <otaylor> Son_Goku: why would disk space be an issue? flatpaks store data in $HOME ... 13:17:19 <langdon> that's the problem.. normally I have a "games disk" 13:17:27 <Son_Goku> likewise Neither sysroot nor $HOME fits the above use case, where the user wants to store games on a separate volume entirely. And another use case is where it's desirable to use the much larger /home volume storage pool, but permit sharing of apps among users. Could there be a /home/share/flatpak with the appropriate permissions, that meets both use case requirements? Alternatively, Workstation could do what Silverblue does, with /var/home bind mounted to /home - and therefore system and user flatpaks go on the same volume. But there should also be a way to set the default location for flatpak files. Users wanting a games volume could bind mount it to /var/lib/flatpak, but then they need a way to set system as the default location instead of users. -- Chris Murphy

5 13

Re: What's new in F31 Workstation
by Paul Frields 28 Oct '19

28 Oct '19

Awesome, thanks Ryan. On Mon, Oct 28, 2019 at 6:57 AM Ryan Lerch <rlerch(a)redhat.com> wrote: > > > On Fri, Oct 25, 2019 at 10:47 AM Paul Frields <stickster(a)gmail.com> wrote: > >> Ryan, looks like F31 is on for this coming Tuesday release. Do you have >> time to do a quick "What's New in F31 Workstation" article and image? >> >> >> Have done a draft for this post. Added the desktop list to this thread to > check if there are any more items that should be added (quickly) before > release day. > > https://fedoramagazine.org/?p=29531&preview=1&_ppp=29a7e5fada > > cheers, > ryanlerch > > > >> >> -- >> Paul >> _______________________________________________ >> Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org >> To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraproject.… >> >

1 0

Back port the fix related to stylus bug on Gnome Wayland
by Luya Tshimbalanga 28 Oct '19

28 Oct '19

Hello team, I filed a bug report[1] related to the stylus crashing applications on the default Gnome Wayland session on Fedora 31 Workstation. At the time of writing, bugzilla is currently down thus unable to link the report. It turned out upstream already fixed the issue [2] and it will be nice to back port it after the Fedora 31 release. References ---------------- [1] https://gitlab.gnome.org/GNOME/mutter/issues/890 [2] https://gitlab.gnome.org/GNOME/gtk/commit/e997ef60da5388e51e0d1afc2f72443a5… -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer

1 0

[Fedocal] Reminder meeting : Workstation WG
by catanzaro＠fedoraproject.org 27 Oct '19

27 Oct '19

Dear all, You are kindly invited to the meeting: Workstation WG on 2019-10-28 from 09:00:00 to 10:00:00 US/Eastern At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Regular meeting for the Workstation Working Group. Agenda: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Chair: * Sep 30 - Michael Catanzaro * Oct 14 - Matthias Clasen * Oct 28 - Allan Day * Nov 11 - Neal Gompa * Nov 25 - Kalev Lember * Dec 9 - Chris Murphy * Jan 13 - Jens Petersen * Jan 27 - Christian Schaller * Feb 10 - Owen Taylor * Feb 24 - Langdon White More information available at: https://fedoraproject.org/wiki/Workstation Source: https://apps.fedoraproject.org/calendar/meeting/9550/

2 1

Re: encrypting user homes by default, meeting summary
by Chris Murphy 22 Oct '19

22 Oct '19

(cc: desktop@ list too) Not sure. Lennart is out until ~Nov 1 on paternity leave. And then his first priority is merging all the systemd-homed stuff and a bunch of fix ups. He says it will be production ready by then. One thing I got from Lennart that I don't have a complete assessment on, is to what degree he's replicated fscrypt (userspace tool from Google) functionality. He's hooking into fscrypt (kernel code) directly, and doesn't have any of the fancier key management that Google fscrypt has - i.e. Google fscrypt let's you change the user master passphrase, which is a wrapped key, separate from the secret key (let's call it a DEK, even though there is one DEK and then there are many derived DEK's for each file), so that it's not necessary to reencrypt everything. Whereas systemd-homed lacks this feature, so it requires 50% free space to reencrypt everything in case of user passphrase changes. I already told Lennart I personally think that's close to a deal killer, if I'm really understanding this limitation correctly. It's weird behavior. And such a burden for resources, space and time and likely would need to be done offline (user is not logged in and can't be using their home while the reencryption happens), that it would inhibit users from changing their passphrase when they probably should, which makes it anti-security, i.e. "I should change my login passphrase after that work trip; oh crap I have to reencrypt 250G?! No way. Guess I won't change the passphrase." I think it's unworkable, and I said so. Casually some people might use it. But I can't recommend that. Someone who can read the code needs to look at it and give an independent assessment: is it really production worthy, is the use case too narrow or just right, and if too narrow what kind of work would be needed to broaden it? Etc. I can't really do any of those things. But for example, to what degree will homed support FreeIPA/AD domains? Is that a small problem or big problem, is there some other way to handle those cases? How? I'm also concerned about performance implications of e.g. GNOME Boxes in the case where it creates qcow2 file, on top of user home which is on a file system backed by a loopback mounted encrypted file, which is on another file system. So that VM is basically pushing writes through three file systems. I've done quite a lot of brutal testing over years where I do bat guano crazy things like Btrfs on qcow2, on Btrfs home on encrypted loop file, on Btrfs, and I'll use the VM and crash the host and everything survives - that is, the file systems don't break. There is data loss but that's sorta expected for any file system. But a consequence of that arrangement is, Btrfs is shit when it comes to fsync. So if the GNOME Boxes default cache of writeback continues to be used, which is reasonable, Btrfs performance gets bad with fsync heavy workloads. Otherwise it performs the same, and occasionally better, than other file systems. So yeah - who wants to help dig into the dirty work and actually make a recommendation? We don't have enough R&D done yet probably to decide on this but I'm gonna guess it makes a lot more sense to try to use systemd-homed and convince Lennart, as early adopters, we want it to be successful and in order to be successful he's gonna have to let it grow into something that'll actually do what we want and need. But for that to be convincing, we have to know what we want and need. Chris On Tue, Oct 22, 2019 at 1:39 PM Michael Catanzaro <mcatanzaro(a)gnome.org> wrote: > > > What should be do to unblock this? Would another meeting be helpful, or > do we need to do further investigation/research first, or...? > > -- Chris Murphy

2 1

Workstation WG meeting, Oct 14
by Matthias Clasen 14 Oct '19

14 Oct '19

Meeting ended Mon Oct 14 14:00:26 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . Minutes: https://meetbot.fedoraproject.org/fedora-meeting-2/2019-10-14/workstation.2… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-2/2019-10-14/workstation.2… Log: https://meetbot.fedoraproject.org/fedora-meeting-2/2019-10-14/workstation.2…

1 0

workstation status report for Council
by Chris Murphy 14 Oct '19

14 Oct '19

These are the notes I've jotted down for the status report for the Fedora Council. I'll assume acks, so just reply if you've got a nack or patch, including additions. * Currently there are no major/unexpected issues. * Working group at 10 members, organization improvements proposed and in discussion https://pagure.io/fedora-workstation/issue/106 * Desire to improve third party repo installs, open questions about including fedora-workstation-repositories on install media. https://pagure.io/fedora-workstation/issue/105 * Work on automated infrastructure to build flatpaks on-going * 31 schedule is on track * OpenH264 improvements will land in 31, includes High and Advanced profiles * Better support for non-English users coming to 31 * Additional detail of efforts in Workstation 31 https://blogs.gnome.org/uraeus/2019/09/23/fedora-workstation-31-whats-new/ * Hopeful for Wayland on Nvidia by default for Workstation 32 -- Chris Murphy

1 0

[Fedocal] Reminder meeting : Workstation WG
by catanzaro＠fedoraproject.org 13 Oct '19

13 Oct '19

Dear all, You are kindly invited to the meeting: Workstation WG on 2019-10-14 from 09:00:00 to 10:00:00 US/Eastern At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Regular meeting for the Workstation Working Group. Agenda: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Chair: * Sep 30 - Michael Catanzaro * Oct 14 - Matthias Clasen * Oct 28 - Allan Day * Nov 11 - Neal Gompa * Nov 25 - Kalev Lember * Dec 9 - Chris Murphy * Jan 13 - Jens Petersen * Jan 27 - Christian Schaller * Feb 10 - Owen Taylor * Feb 24 - Langdon White More information available at: https://fedoraproject.org/wiki/Workstation Source: https://apps.fedoraproject.org/calendar/meeting/9550/

2 1

F31 blocker / FE fix update testing requests
by Adam Williamson 11 Oct '19

11 Oct '19

Hi folks! We have a few updates pending to fix F31 blocker/FE bugs that could do with some testing and karma, if anyone has time to look at them: * https://bodhi.fedoraproject.org/updates/FEDORA-2019-1265db97c0 : grub2 fix for xen issues, ideal if you can test the actual xen bug it fixes, but just checking it doesn't break on your system would be good too. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1703700 * https://bodhi.fedoraproject.org/updates/FEDORA-2019-eaf25b8182 : gnome-control-center fix for display switching issues, install it and try switching between displays if you have more than one. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1756553 * https://bodhi.fedoraproject.org/updates/FEDORA-2019-d9b994c6bc : probably for expert ARM testers, pwhalen? not sure exactly what needs doing to test a uboot-tools update. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1759358 * https://bodhi.fedoraproject.org/updates/FEDORA-2019-688ba1f947 : gnome-session fix for not unloading units at logout time, just check that a gnome session works normally and you don't have any problems logging out and rebooting. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1760366 Thanks a lot everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop October 2019