Feedback requested on potential change to hosts line in nsswitch.conf
by Michael Catanzaro
Hi,
If you're interested in name resolution or mDNS, please review this bug
report:
Default authselect profiles break `hostname --fqdn`
https://bugzilla.redhat.com/show_bug.cgi?id=2257197
We are looking for feedback on whether to move nss-myhostname, and
possibly also nss-mdns4_minimal.
I wonder if anybody has recently tested systemd-resolved's ability to
handle mDNS resolution. Previously we decided it was broken, which is
why nss-mdns4_minimal is currently run before nss-resolve. But I don't
know if that's still the case.
Michael
4 months, 2 weeks
Figure out what killed an app (rhbz#2253099)
by Milan Crha
Hi,
I tried to investigate a rawhide bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2253099
which is about Evolution being killed "by something". That's the thing,
I do not know what killed it, thus even why it had been killed. It's
even not killed after certain steps, it's killed "randomly", on various
occasions.
I did search the internet, but they usually expect the killer is the
OOM service, which logs about the action either in the dmesg or in the
journal, but in this case there is no sign about whom killed it in
either of these logs.
The evolution terminal just says:
Killed
and the `dmesg | grep -i kill` only shows:
[ 3.435200] systemd[1]: Listening on systemd-oomd.socket - Userspace
Out-Of-Memory (OOM) Killer Socket.
[ 6.051242] rfkill: input handler disabled
[ 22.579276] rfkill: input handler enabled
[ 23.539350] rfkill: input handler disabled
and `journalctl -xb | grep -i kill` doesn't reveal anything useful. The
`journalctl -xb | grep -i evolution` has as its last line:
Jan 31 10:49:22 localhost.localdomain rtkit-daemon[826]:
Successfully made thread 4820 of process 4640 (/usr/bin/evolution)
owned by '1000' RT at priority 5.
which does not explain anything. Grepping for the 4640 (evo's PID)
didn't show anything either.
That being said, is there a way to figure out what killed the app,
please?
Thanks and bye,
Milan
P.S.: the above-pasted journalctl line is followed by these three,
which look suspicious, but maybe they are unrelated. I even do not know
whether they had been added immediately after the app was killed or
before it. At least the terminal should not matter, because evo is
killed when being started from the GUI too. Three log lines follow:
Jan 31 10:49:23 localhost.localdomain xdg-desktop-por[2697]: Realtime
error: Could not map pid: Could not determine pid namespace: Could not
find instance-id in process's /.flatpak-info
Jan 31 10:50:46 localhost.localdomain gnome-terminal-[2939]: void
terminal_screen_shell_preexec(VteTerminal*): assertion
'!priv->between_preexec_and_precmd' failed
Jan 31 10:50:49 localhost.localdomain gnome-terminal-[2939]: void
terminal_screen_shell_preexec(VteTerminal*): assertion
'!priv->between_preexec_and_precmd' failed
4 months, 2 weeks
fedrq - new repoquerying tool
by Maxwell G
Hi Fedorians,
I've been working on a repoquerying tool called fedrq [1] that I'd like
to share with you. Here's the elevator pitch: fedrq provides a friendly
interface to query the Fedora repositories. It makes it really easy to
query across Fedora and EPEL branches. It uses the dnf Python bindings
(libdnf5 backend is almost done) and doesn't shell out to dnf repoquery.
Amongst other things, fedrq allows querying for reverse dependencies,
packages that contain a certain Provide or file, subpackages of an SRPM,
and general package metadata. My favorite features are the easy branch
switching, `fedrq subpkgs` (there's no real equivalent in dnf
repoquery), and the ability to dump package metadata as JSON. The many
threads about how to properly query for dependencies when doing SO name
bump rebuilds and my own frustrations with dnf repoquery inspired this
tool.
You can install fedrq from PyPI or from gotmax23/fedrq [2] on Copr. The
EXAMPLES section of fedrq(1) [3] provides a good intro and demonstration
of fedrq's functionality. The tool is very much a WIP and any feedback
is appreciated.
For reverse dependency rebuilds, you probably want the following
command:
```
$ fedrq whatrequires -X -F source $(fedrq subpkgs SRCNAME) # equivalent
$ fedrq subpkgs SRCNAME | fedrq whatrequires -X -i -F source # equivalent
```
This accounts for any package that depends on any subpackage/binary RPM
produced by SRCNAME at buildtime and/or runtime, and spits out the names
of the source packages that need to be rebuilt. For simple packages that
output only one RPM, `fedrq whatrequires -F source PKGNAME` is
sufficient.
[1] https://sr.ht/~gotmax23/fedrq/
[2] https://copr.fedorainfracloud.org/coprs/gotmax23/fedrq/
[3] https://gotmax23.srht.site/fedrq/fedrq.1.html#EXAMPLES
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/They
4 months, 2 weeks
libextractor soname bump
by Gwyn Ciesla
libextractor 1.13 is coming to rawhide, which fixes the FTBFS and brings exiv2 compatibility. It also bumps the soname, but as there seem to be no Fedora consumers, it shouldn't be an eventful update.
--
Gwyn Ciesla
she/her/hers
------------------------------------------------
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with Proton Mail secure email.
4 months, 2 weeks
Re: just to let you know FESCo agreed to a preliminary injunction
while we consider this issue
by Jonathan Bennett
Hey folks, outside observer, and long-time Fedora user weighing in with
some thoughts. First off, I've been hyped to see Fedora lead the way
with finally making a real move to Wayland, and retire X11. And now I'm
fairly disappointed to hear that there's a real chance that move will
get killed. And especially that it's not because of a technical problem
or blocker bug.
It really seems like KDE-x11 would do better to live in a copr, with
whatever packages needs rebuilt to make it work. Probably a better
experience for everyone.
The proposal was to go to KDE 6 and drop X11 support. " KDE Plasma will
not offer an X11 session" That change was approved by FESCo. And from my
perspective running Fedora Rawhide and KDE 6, it looks great. We even
have HDR working! That's amazing! So let's go all in.
--Jonathan Bennett
4 months, 2 weeks
Introduction
by Luis Correia
Hi, I'm a long time Fedora user and used to help develop the Ralink
Wireless driver (rt2x00) that's been present in the kernel for a long time.
I'm now entering the process of helping maintain the mixxx package over at
rpmfusion.
Hope to be useful with this new venture.
Luis Correia
4 months, 2 weeks
Problems setting up environment
by Luis Correia
Hi,
please excuse my probable clumsiness but I'm having issues while trying to
get ssh access to a package I'm now co-maintaining on RPM Fusion Free.
I have followed all steps in
https://rpmfusion.org/Contributors#Co-maintaining_an_existing_package, and
am pretty sure my ssh key was uploaded correctly.
If I try to clone the repo, I get this
$ rfpkg clone free/mixxx
Cloning into 'mixxx'...
luisfcorreia(a)pkgs.rpmfusion.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.
Thanks in advance!
Luis
4 months, 2 weeks
