desktop March 2018

desktop@lists.fedoraproject.org

38 participants
42 discussions

Adding container-management (podman, docker, origin-clients) to workstation by default
by Colin Walters 03 Apr '18

03 Apr '18

PR in: https://pagure.io/fedora-comps/pull-request/248 This came out of various discussions; see https://pagure.io/workstation-ostree-config/pull-request/74 and in particular: https://pagure.io/workstation-ostree-config/pull-request/74#comment-47627 The high level goal here is to make Workstation more container oriented by default, reducing the delta from Atomic. In particular I'd like to flesh out the "pet/dev container" pattern discussed in various places and encourage people to do that rather than installing things in their root filesystem by default. It's a tremendous change - it was painful for me at first. But there are a lot of compelling advantages. By having e.g. `podman` (and `docker` for people used to that) installed by default we take a step towards encouraging that by default. A simple example here: At some point `fpaste` was added to @standard in comps and hence installed on Workstation by default. It's small and harmless, but those types of things pile up. Instead, `fpaste` is exactly the kind of thing that should live in your dev container. Along with several other things from @standard like tcpdump, traceroute, and telnet. And gcc, golang, cargo, ansible, pip, etc.

6 8

gnome-session with koji
by Takao Fujiwara 31 Mar '18

31 Mar '18

I'd like to run gnome-shell with koji for the GUI test. I referred https://fedoraproject.org/wiki/PackageMaintainers/GraphicalTests +BuildRequires: xorg-x11-drv-dummy +BuildRequires: gnome-session +BuildRequires: gnome-shell +$Xorg -noreset +extension GLX +extension RANDR +extension RENDER -logfile ./xorg.log -config ./xorg.conf -configdir . :99 & +export DISPLAY=:99 +gnome-session & When I run gnome-session with koji, /usr/libexec/gnome-session-check-accelerated outputs an error: gnome-session-binary[18713]: WARNING: software acceleration check failed: Child process exited with code 1 Unable to init server: Could not connect: Connection refused I can run gnome-session on console with the same way but koji outputs the above error. Do you have any ideas to succeed the acceleration check? However I'd like to run GNOME Wayland finally instead of Xorg but I don't know how to run gnome-session on console.

3 6

urgent: please help expand F28 talking points
by Matthew Miller 30 Mar '18

30 Mar '18

Right now, https://fedoraproject.org/wiki/Fedora_28_talking_points#Fedora_Workstation just says "Improved battery life: power-saving features are enabled by default." What else do we have for F28? In particular, what things would we like * users to look at in the beta * the press to write about * Fedora Ambassadors to learn about and "sell"? And, could we expand on the above? What power-saving features are we talking about? If I say just that, and a journalist asks me for more detail, what do I need to know? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

7 11

2018-04-02 @ 16:00 UTC - Fedora 28 Blocker Review Meeting
by Adam Williamson 30 Mar '18

30 Mar '18

# F28 Blocker Review meeting # Date: 2018-04-02 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 3 proposed blockers and 4 proposed freeze exception issues for Final to review, so let's have a review meeting on Monday. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F28 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Fedora 28 minimum memory requirement, review
by Chris Murphy 28 Mar '18

28 Mar '18

For Fedora 27 it says this: Fedora Workstation to a laptop or desktop computer that has at least 1 GHz processor, 1 GB RAM, and 10 GB space available https://getfedora.org/en/workstation/download/ When I set a VM to 1G it's always unusable. Sometimes it's PackageKit that crashes first, which causes systemd-coredump to spin up and run out of memory next, and then oom killers start killing off various processes. Sometimes the oom killing just starts happening without a prior crash. In any case I never get a desktop. With 1.5G RAM I usually get a desktop but then if anything crashes, and it seems like PackageKit is crashing often when under memory pressure (?), it kicks off systemd-coredump which makes the memory problem worse, and a bunch of oom killers start killing off various processes. In any case, I cannot successfully run the installer or Firefox by themselves. https://bugzilla.redhat.com/show_bug.cgi?id=1559176 -- Chris Murphy

12 26

live media install performance, loop1 and gnome-shell processes
by Chris Murphy 27 Mar '18

27 Mar '18

This is not a new problem, it happens since I can recall in a default virt-manager qemu-kvm VM using qxl video. It's easy to reproduce in VM as well as baremetal. See screenshot here: https://drive.google.com/open?id=1TK-QnaBDzbcu7hxVEN40x2DlA4NyDMB2 The questions are: is it expected these processes take up this much CPU? is there low hanging fruit here? Even cutting it in half would be huge. How to profile and file a bug against these likely separate problems? Maybe it's worth in the next cycle trying zstd for squashfs.img compression in lieu of xz. That might be related to loop1 taking such a big hit, but I don't know for sure that loop1 rather than loop0 is really the process taking the xz decompression hit. -- Chris Murphy

4 5

[Fwd: [Test-Announce] Fedora 28 Candidate Beta-1.1 Available Now!]
by Adam Williamson 27 Mar '18

27 Mar '18

I really should make the robot send these announcements to more lists, but until I remember to do that, here's a forward! Please help us test this compose in your areas, folks. This is Beta RC1. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Touchpad only works after entering standby
by rugk 26 Mar '18

26 Mar '18

I am on Fedora 27 here and the touchpad of my laptop works, but only if I go to standby and wake up from standby after each system restart. That is a kinda curious behaviour and definitively a bug. I just don't know where to report it? What component is responsible for this? Is it GNOME? Is it some other thing?

3 2

Package gnome-usage
by rugk 26 Mar '18

26 Mar '18

It would be nice if someone can package gnome-usage (https://gitlab.gnome.org/GNOME/gnome-usage) for Fedora. Would anyone do so?

3 3

Remote display via pipiewire in Wayland with GNOME (3.26)?
by rugk 26 Mar '18

26 Mar '18

https://fedoraproject.org/wiki/Wayland_features#remote_display says: > Remote display, using pipewire, has been included as an "experimental-feature" in GNOME-3.26 I am running GNOME 3.26, so if it has been included, how do I enable this experimental feature? (Maybe the wiki also needs to be expanded here.)

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop March 2018