September 2020 - desktop - Fedora Mailing-Lists

[Fedocal] Reminder meeting : Workstation WG

by catanzaro＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Workstation WG on 2020-09-15 from 09:30:00 to 10:30:00 US/Eastern At https://bluejeans.com/395383051/ The meeting will be about: Regular meeting for the Workstation Working Group Current Topics: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Etherpad: https://etherpad.gnome.org/p/fedora-workstation-wg More information available at: https://fedoraproject.org/wiki/Workstation Source: https://apps.fedoraproject.org/calendar/meeting/9652/

3 years, 7 months

1
0
0 / 0

GNOME 3.37.92 megaupdate landing in testing and tracker3 coming

by Kalev Lember

Hi all, Just a quick heads up that the 3.37.92 megaupdate is all lined up and queued to F33 updates-testing: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7f57486c95 This is likely not going to be pushed through the beta freeze, so next week I'll prepare a final .0 release to replace/obsolete the .92 bodhi update. I'll talk to QA and see how they feel about pulling the .92 update through the beta freeze now that the beta is delayed anyway, but I think the base scenario is that we ship beta without this. The megaupdate also includes new parallel installable tracker3 and tracker3-miners packages. The naming here was difficult but in the end we ended up keeping tracker 2 in the existing 'tracker' package and creating a new 'tracker3' package that's parallel installable with the old one. This makes it easy to port packages over one by one. In F34 perhaps we can drop tracker 2 and get rid of the separate tracker3 package; let's see how fast app porting goes. In default Fedora Workstation, we'll have both 'tracker' and 'tracker3' installed by default, but only tracker3 FS miners are going to be started at session login; tracker 2 miners are autostarted when an app requires them. Everything in the default install is ported to tracker3, with the exception of gnome-photos where the upstream port didn't get ready in time. (I've cross posted this to devel and desktop lists both.) -- Kalev

3 years, 7 months

2
1
0 / 0

Fedora Workstation WG minutes, 2020-09-08

by Chris Murphy

============================================== #fedora-meeting-2: Workstation WG (2020-09-08) ============================================== Meeting started by cmurf at 02:49:27 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2020-09-10/workstation... . Meeting summary --------------- * Rollcall (cmurf, 02:49:39) * present wg members: cmurf, aday, kalev, neal, tpopela, mcatanzaro, jens, otaylor (cmurf, 02:49:41) * regrets wg members: langdon, mclasen (cmurf, 02:49:43) * present guests: (cmurf, 02:49:45) * Approve 1 Sep minutes (cmurf, 02:49:47) * LINK: https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-09-0... (cmurf, 02:49:49) * AGREED: Approved - no objections (cmurf, 02:49:51) * Announcement: btrfs test week (Chris / Neal) (cmurf, 02:49:53) * LINK: https://testdays.fedorainfracloud.org/events/92 (cmurf, 02:49:57) * Announcement: GNOME 3.38.92 (Kalev) (cmurf, 02:49:59) * LINK: https://gitlab.gnome.org/GNOME/Initiatives/-/issues/17 (cmurf, 02:50:03) * Announcement: i18n test day is today/this week (Jens) (cmurf, 02:50:05) * LINK: https://fedoraproject.org/wiki/Test_Day:2020-09-08_I18N_Test_Day (cmurf, 02:50:07) * Google Account doesn't work during initial setup (requires new blocker criterion) (cmurf, 02:50:09) * LINK: https://pagure.io/fedora-workstation/issue/182 (cmurf, 02:50:11) * ACTION: Michael will follow-up (cmurf, 02:50:21) * Remove rngd from default install (cmurf, 02:50:23) * LINK: https://pagure.io/fedora-workstation/issue/184 (cmurf, 02:50:25) * AGREED: Deferred until Chris has spoken to Neil Horman (cmurf, 02:50:31) * Outstanding Fedora 33 UX issues (cmurf, 02:50:33) * LINK: https://pagure.io/fedora-workstation/issue/178 (cmurf, 02:50:35) * Open Floor (cmurf, 02:50:41) Meeting ended at 02:50:53 UTC. Action Items ------------ * Michael will follow-up Action Items, by person ----------------------- * **UNASSIGNED** * Michael will follow-up People Present (lines said) --------------------------- * cmurf (36) * zodbot (7) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

3 years, 7 months

1
0
0 / 0

2020-09-08 MEETING AGENDA

by Chris Murphy

Workstation Working Group Meeting Date and Time: 2020-09-08 9:30 am ET 13:30 UTC Location: https://bluejeans.com/395383051/ https://www.bluejeans.com/numbers == Agenda == Approval of 1 Sep minutes https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-09-0... Announcements Follow-ups & Status reports Topics #182 Google Account doesn't work during initial setup (requires new blocker criterion) https://pagure.io/fedora-workstation/issue/182 #178 Outstanding Fedora 33 UX issues https://pagure.io/fedora-workstation/issue/178 #184 Remove rngd from default install https://pagure.io/fedora-workstation/issue/184 Open Floor -- Chris Murphy

3 years, 7 months

1
0
0 / 0

Btrfs by default status updates, 2020-09-07

by Chris Murphy

+ F33 Btrfs By Default Test Week has concluded Test results page https://testdays.fedorainfracloud.org/events/92 Perhaps the most significant issue discovered is something of an edge case. The installer has performance issues when it encounters a Btrfs file system with many snapshots (500+ in this case). Untested, but since the handling is the same, I'd expect a similar issue with many LVM thin snapshots. https://bugzilla.redhat.com/show_bug.cgi?id=1876162#c23 --- + Subset of test day: There are two new test cases of interest that will hopefully be turned into Quick Docs: QA:Testcase partitioning custom btrfs preserve home https://fedoraproject.org/wiki/QA:Testcase_partitioning_custom_btrfs_pres... Draft: dual boot Fedoras - is a variation on the above test case. This is mostly leveraging BootLoaderSpec. The Btrfs part is incidental. But by using separate subvolumes for the different system roots for each Fedora, we're able to share a single Btrfs file system for much better space utilization. A future feature might be to dedup them. https://fedoraproject.org/wiki/User:Sumantrom/Draft/dualboot_f33_btrfs --- + Documentation: preliminary install-guide updates https://pagure.io/fedora-docs/install-guide/pull-request/55 https://pagure.io/fedora-docs/install-guide/pull-request/56 --- + Communication: repurposing the Fedora Btrfs wiki as a landing page is a work-in-progress https://fedoraproject.org/wiki/Btrfs --- + devel@ discussion on possibly defaulting to noatime https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... -- Chris Murphy

3 years, 7 months

2
1
0 / 0

[Fedocal] Reminder meeting : Workstation WG

by catanzaro＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Workstation WG on 2020-09-08 from 09:30:00 to 10:30:00 US/Eastern At https://bluejeans.com/395383051/ The meeting will be about: Regular meeting for the Workstation Working Group Current Topics: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Etherpad: https://etherpad.gnome.org/p/fedora-workstation-wg More information available at: https://fedoraproject.org/wiki/Workstation Source: https://apps.fedoraproject.org/calendar/meeting/9652/

3 years, 7 months

1
0
0 / 0

services impact on startup times

by Chris Murphy

Hi, These are based on Fedora-Workstation-Live-x86_64-33-20200828.n.0.iso in a VM. The numbers are different on bare metal but correlate. The only standout is rngd.service. That's a pretty big single hit, percentage wise. And I don't know if we even need it anymore. Among the rest, perhaps atd.service and crond.service could be disabled by default on new installations, in favor of systemd timers. Startup finished in 1.320s (kernel) + 1.344s (initrd) + 7.727s (userspace) = 10.392s disable atd.service Startup finished in 1.308s (kernel) + 1.310s (initrd) + 7.557s (userspace) = 10.176s disable dbxtool.service Startup finished in 1.302s (kernel) + 1.291s (initrd) + 7.527s (userspace) = 10.120s disable import-state.service Startup finished in 1.308s (kernel) + 1.326s (initrd) + 7.410s (userspace) = 10.044s disable iscsi.service Startup finished in 1.316s (kernel) + 1.303s (initrd) + 7.177s (userspace) = 9.797s disable libvirtd.service Startup finished in 1.316s (kernel) + 1.266s (initrd) + 6.779s (userspace) = 9.361s disable lvm2-monitor.service Startup finished in 1.315s (kernel) + 1.323s (initrd) + 6.750s (userspace) = 9.389s disable mdmonitor.service Startup finished in 1.316s (kernel) + 1.350s (initrd) + 6.675s (userspace) = 9.342s disable ModemManager.service Startup finished in 1.270s (kernel) + 1.305s (initrd) + 7.052s (userspace) = 9.629s disable nfs-convert.service Startup finished in 1.312s (kernel) + 1.343s (initrd) + 6.958s (userspace) = 9.614s disable rngd.service Startup finished in 1.308s (kernel) + 1.277s (initrd) + 5.247s (userspace) = 7.833s disable switcheroo-control.service Startup finished in 1.308s (kernel) + 1.334s (initrd) + 5.223s (userspace) = 7.867s disable vboxservice.service Startup finished in 1.301s (kernel) + 1.302s (initrd) + 5.176s (userspace) = 7.780s disable crond.service Startup finished in 1.310s (kernel) + 1.278s (initrd) + 5.076s (userspace) = 7.665s preset-all Startup finished in 1.316s (kernel) + 1.312s (initrd) + 7.869s (userspace) = 10.498s ##stopwatch 11.35 disable atd.service crond.service iscsi.service rngd.service vboxservice.service Startup finished in 1.305s (kernel) + 1.294s (initrd) + 5.505s (userspace) = 8.105s ##stopwatch 8.89 All of these times are based on 'systemd-analyze'. The stopwatch method is less precise but still demonstrates the difference is real. It may not be a big enough deal to do anything about it this cycle, but could be something to look at for the next. Maybe more opportunities are available. -- Chris Murphy

3 years, 7 months

5
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop September 2020