Adding container-management (podman, docker,
origin-clients) to workstation by default
by Colin Walters
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.
5 years, 8 months
gnome-session with koji
by Takao Fujiwara
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.
5 years, 8 months
urgent: please help expand F28 talking points
by Matthew Miller
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
5 years, 8 months
Fedora 28 minimum memory requirement, review
by Chris Murphy
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
5 years, 8 months
live media install performance, loop1 and gnome-shell processes
by Chris Murphy
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
5 years, 8 months
Touchpad only works after entering standby
by rugk
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?
5 years, 8 months
