Hi,
sorry for not dealing with this earlier. I was somewhat out for a
while, and didn't give the mail much significance.
What happened is that I'll be leaving Red Hat. As a first step, I
changed my FAS email address while explicitly keeping my Red Hat
address for bugzilla for now.
I thought
Hi,
On Wed, 2022-03-30 at 15:55 +0200, Zdenek Dohnal wrote:
> On 3/30/22 03:26, Michael Catanzaro wrote:
> > (removing us...@lists.fedoraproject.org)...
> >
> > On Wed, Mar 23 2022 at 01:58:33 PM +0100, Zdenek Dohnal
> > wrote:
> > > Unfortunately there is no clean upgrade path to solve the
Hi,
On Wed, 2022-03-09 at 12:35 -0500, Robbie Harwood wrote:
> Hi, today I went to build grub2 in rawhide and got this:
>
> DEBUG util.py:444: No matching package to install: 'libusb-devel'
>
> grub2 has a `BuildRequires: libusb-devel`, and suddenly that package
> doesn't exist anymore.
On Thu, 2022-02-24 at 10:14 -0500, Colin Walters wrote:
>
> On Thu, Feb 24, 2022, at 6:17 AM, Benjamin Berg wrote:
>
> > network-online-waitonly.target with
> > After=network-online.target
> > StopWhenUnneeded=yes
> >
> > which is then used inside is
Hi,
On Thu, 2022-02-24 at 07:47 +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Feb 24, 2022 at 12:17:27AM +, Gary Buhrmaster wrote:
> > On Wed, Feb 23, 2022 at 11:55 PM Chris Adams wrote:
> > >
> > > Once upon a time, Zbigniew Jędrzejewski-Szmek said:
> > > > So this is the culprit.
On Fri, 2021-09-03 at 15:57 -0600, Chris Murphy wrote:
> On Fri, Sep 3, 2021 at 1:32 PM Stephen Gallagher wrote:
>
> > So it appears to be an SELinux issue. I suspect but cannot prove that
> > it's related to a number of AVCs related to DBUS that I see in
> > selinux-troubleshooter.
>
> I'm
Hi,
is thermald.service active and running on that machine?
If yes, could you please edit the command line of the systemd unit to
include --loglevel=debug and grab some logs[1]?
Ideally both of a "bad" and "good" case.
Obviously, we shouldn't be running into a critical temperature
situation
Hi,
On Wed, 2021-07-28 at 13:33 +1000, David Airlie wrote:
> > From your description, something obviously went wrong: either
> > assignment of cgroups has failed and everything is in the same big
> > group, or sd-oomd made a bad shot. systemd-cgls should show which it is.
>
> Thanks for the
Hi,
On Fri, 2021-06-25 at 10:21 +, Zbigniew Jędrzejewski-Szmek wrote:
> - Jun 20 22:04:48 krowka systemd[1]: Started Rule-based Manager for Device
> Events and Files.
> + Jun 20 22:04:48 krowka systemd[1]: Started systemd-udevd.service.
>
> [SNIP]
>
> Would people be opposed to making this
On Tue, 2021-04-27 at 20:03 +, Ravindra Kumar wrote:
> > This desktop file need to be replaced by the systemd-user unit,
> > IMO.
>
> Thanks Vitaly. We will look into converting it to systemd-user unit.
> I believe that would work for all other desktop managers as well.
Yeah, you might want
Hi Chris and others,
On Mon, 2021-03-08 at 22:38 -0700, Chris Murphy wrote:
> Do any of the bugs in this thread need to be proposed as blockers or
> freeze exceptions, for beta or final?
>
> This looks like it might have been lost in process because it got
> closed due to a fix for Fedora 33
On Sun, 2021-03-07 at 08:55 -0600, Michael Catanzaro wrote:
> On Sun, Mar 7, 2021 at 11:28 am, Björn Persson
> wrote:
> > Do the ECC-less Intel processors also lack
> > all other MCE support?
>
> No, ABRT used to regularly warn me about thermal events from MCE when
> I
> didn't have a good
On Fri, 2021-03-05 at 18:28 +, Tom Seewald wrote:
> > Could you modify fprintd.service, to set G_MESSAGES_DEBUG=all[1]
> > and
> > then grab a log of that?
>
> Here's what I see from systemctl status fprintd.service:
>
> Getting authorization to perform Polkit action
>
On Fri, 2021-03-05 at 17:20 +, Tom Seewald wrote:
> > Can you please provide output of `authselect current`?
> # authselect current
> Profile ID: sssd
> Enabled features:
> - with-fingerprint
> - with-silent-lastlog
>
> # authselect check
> Current configuration is valid.
>
> I have verified
Hi,
On Tue, 2021-03-02 at 15:31 +0100, Hans de Goede wrote:
> On 3/1/21 9:15 PM, Ray Strode wrote:
>
> [...]
> > > Any debugging options which I can enable somewhere to show the
> > > pam_fprintd error ?
> > you can put "debug" on the ends of the lines that say
> > pam_fprintd.so
> > in
Hi,
On Fri, 2021-01-22 at 09:59 -0600, Michael Catanzaro wrote:
Problem is that multiseat doesn't work when dbus-broker is used. See
https://gitlab.gnome.org/GNOME/at-spi2-core/-/commit/260a4414ac26cc5e91dc56b6a10b5dda3dae22cd
and:
Hi,
On Thu, 2020-12-10 at 12:20 -0700, Chris Murphy wrote:
> On Thu, Dec 10, 2020 at 5:40 AM Benjamin Berg
> wrote:
> > Hi,
> >
> > so, the other day we had a major regression in the PAM stack[1]
> > that,
> > unfortunately, ended up hitting rawhide and the F
Hi,
so, the other day we had a major regression in the PAM stack[1] that,
unfortunately, ended up hitting rawhide and the Fedora 33 testing (not
stable) repository before being unpushed.
In this case it was easy to work around as SSH was still working fine.
But, it seems that rescue mode
On Tue, 2020-11-24 at 21:54 +0100, Miro Hrončok wrote:
> On 11/24/20 9:52 PM, Benjamin Berg wrote:
> > On Tue, 2020-11-24 at 21:26 +0100, Miro Hrončok wrote:
> > > On 11/24/20 9:10 PM, Ben Cotton wrote:
> > > > https://fedoraproject.org/wiki/Changes/Rename_libusb_p
On Tue, 2020-11-24 at 21:30 +0100, Miro Hrončok wrote:
> On 11/24/20 9:10 PM, Ben Cotton wrote:
> > * We begin sunsetting `libusb-compat` (i.e. current `libusb`).
>
> Consider deprecating it as part of the change:
>
>
On Tue, 2020-11-24 at 21:26 +0100, Miro Hrončok wrote:
> On 11/24/20 9:10 PM, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/Rename_libusb_packages_and_deprecated_old_api
> >
> > == Summary ==
> >
> > Rename `libusb` to `libusb-compat` and `libusbx` to `libusb1`. Do
> > '''not'''
On Mon, 2020-09-14 at 20:35 +0900, Alexey A. wrote:
>
> > may be different for GNOME with JIT'ed code
> > potentially getting swapped out
>
> How to recognize JIT'ed code? Do you mean that we shouldn't lock it?
I don't think you can protect it using your tool, as it lives in
anonymous mappings.
On Sun, 2020-09-13 at 16:47 +, Alexey Avramov wrote:
> > So with
> > applications started, you might get higher.
>
> I think we should protect only basic GUI. On computers with 16G+ RAM
> locking 1G memory with apps should not be a problem if it helps to
> improve responsiveness.
Yup, fully
On Sat, 2020-09-12 at 20:53 +, Alexey Avramov wrote:
> > how much memory that amounts to in the usual scenarios
>
> 700M on F32 without any apps started.
That seems like quite a lot. I mean, we get into a similar region of
memory that EarlyOOM would be protecting with no apps started. So
On Mon, 2020-08-17 at 11:00 -0700, Samuel Sieb wrote:
> On 8/17/20 2:54 AM, Benjamin Berg wrote:
> > Note that you can also change the power button action in gnome-
> > control-
> > center, power, "Suspend & Power Button", "Power Button Action".
&g
Hi,
On Sat, 2020-08-08 at 14:30 -0400, Christopher wrote:
> 1. There is no GUI to change the setting.
> 2. The logind.conf settings have no effect on the media keys.
> 3. The key is XF86Sleep (and not XF86Suspend).
> 4. The key is assigned to the 'suspend-static' behavior in
> dconf-editor /
On Mon, 2020-07-20 at 10:55 +0200, Kevin Kofler wrote:
> That said, I do not see how the EarlyOOM heuristic, which allows, depending
> on the exact settings, something like 80-90% of swap to be used IN ADDITION
> to 90+% RAM (and will only start doing anything if BOTH RAM and swap are
> full)
On Fri, 2020-07-17 at 19:44 -0700, John M. Harris Jr wrote:
> On Friday, July 17, 2020 10:06:53 AM MST Benjamin Berg wrote:
> > What we achieve by killing a process is that we give the kernel more
> > flexibility in how it manages the available memory. It really doesn't
> >
re that it is really effective at preventing many
really bad thrashing scenarios.
Benjamin
> This daemon was written recently, published today.
>
> 1. https://github.com/hakavlad/prelockd
>
> вт, 14 июл. 2020 г. в 17:19, Benjamin Berg :
> > On Mon, 2020-07-13 at 19:25 -0600
On Fri, 2020-07-17 at 09:12 -0700, John M. Harris Jr wrote:
> On Tuesday, July 14, 2020 1:18:08 AM MST Benjamin Berg wrote:
> > So, we don't want to get the kernel into the situation where it must
> > remove executables/libraries from main memory. If that happens, you can
>
On Mon, 2020-07-13 at 19:25 -0600, Chris Murphy wrote:
> On Mon, Jul 13, 2020 at 12:00 PM Benjamin Berg wrote:
> > If MemAvailable drops below 250MiB (roughly 6GiB * 4%), then this means
> > that we have less than 500MiB left for file caches. If we can't swap
> > (remember, s
On Tue, 2020-07-14 at 00:55 +0900, Alexey A. wrote:
> > MemAvailable is a bad heuristic, it does *not* represent "free"
> > memory.
>
> MemAvailable is a good heuristic, it does represent available
> memory.
Maybe. But the point is that I expect a system to be in trouble long
before the value
On Mon, 2020-07-13 at 08:21 -0700, John M. Harris Jr wrote:
> On Monday, July 13, 2020 1:58:30 AM MST Benjamin Berg wrote:
> > But, I also think that the people proposing this have done quite a lot
> > of testing to find reasonable values for various scenarios. If they
> >
On Sun, 2020-07-12 at 14:46 -0700, John M. Harris Jr wrote:
> That sounds like an excellent idea, but I'm not convinced that killing users'
> processes, while there's still tons of memory free available, is actually an
> improvement.
I think you should rather think of "MemAvailable" as a
On Thu, 2020-07-09 at 07:51 -0700, John M. Harris Jr wrote:
> What's the KDE SIG's rationale behind supporting this? This actively limits
> the amount of RAM that end users are able to make use of. The more RAM the
> end
> user has, the more RAM is not available for use, because EarlyOOM will
On Sun, 2020-07-12 at 12:46 +0200, Kevin Kofler wrote:
> Neal Gompa wrote:
> > There's a difference between half-baked and a roadmap of incremental
> > improvement. This Change is an example of the latter.
>
> No, it is actually an example of deliberately implementing a simplistic
> "solution"
md. And irrelevant in the
context of systemd-oomd.
Benjamin
> сб, 11 июл. 2020 г. в 17:34, Benjamin Berg :
> > On Sat, 2020-07-11 at 08:43 +0200, Igor Raits wrote:
> > > On Fri, 2020-07-10 at 15:55 -0400, Ben Cotton wrote:
> > > >
> > https://fedoraproject
On Sat, 2020-07-11 at 14:31 -0300, Sergio Belkin wrote:
> My only question is if measuring memory pressure is a better indication.
> If nohang-desktop uses PSI, isn't it a more proper solution?
The basic problem is that PSI can only be reactive. You need to measure
it over a period of time and
On Sat, 2020-07-11 at 07:33 -0500, Michael Catanzaro wrote:
> On Sat, Jul 11, 2020 at 2:28 pm, Igor Raits
> wrote:
> > My question was more targeted whether we are not going to ship anymore
> > earlyoom by default with this change or will they be both shipped at
> > thie moment until something
ge, simpliy modify /etc/uresourced.conf
(and, ideally reboot to ensure it is properly applied to your user
session).
> > See: https://pagure.io/fedora-workstation/issue/154
> >
> > == Owner ==
> > * Name: [[User:benzea|Benjamin Berg]]
> > * Email: bb...@redhat.co
On Wed, 2020-07-01 at 11:07 -0500, Michael Catanzaro wrote:
> So the last two times thermald was proposed (first as a F32 change
> proposal, then more recently to the Workstation WG) it was rejected on
> the grounds that it was not useful without dptfxtract installed. Now
> it's clear that
On Tue, 2020-06-30 at 17:48 +0200, Vitaly Zaitsev via devel wrote:
> On 30.06.2020 15:25, Ben Cotton wrote:
> > Better thermal management and peak performance on Intel CPUs by
> > including thermald in the default install.
>
> Good, but thermald is absolutely useless without configs. Configs can
On Wed, 2020-01-08 at 12:24 -0700, Chris Murphy wrote:
> On Mon, Jan 6, 2020 at 11:09 AM Lennart Poettering
> wrote:
> > - facebook is working on making oomd something that just works for
> > everyone, they are in the final rounds of canonicalizing the
> > configuration so that it can just
On Tue, 2020-01-07 at 11:28 +0100, Lennart Poettering wrote:
> On Mo, 06.01.20 14:53, Michael Catanzaro (mcatanz...@gnome.org) wrote:
>
> > On Mon, Jan 6, 2020 at 7:09 pm, Lennart Poettering
> > wrote:
> > > - facebook is working on making oomd something that just works for
> > > everyone,
Hi,
[resend this older message for the list]
On Mon, 2020-01-06 at 14:53 -0600, Michael Catanzaro wrote:
> On Mon, Jan 6, 2020 at 7:09 pm, Lennart Poettering
> wrote:
> > - facebook is working on making oomd something that just works for
> > everyone, they are in the final rounds of
On Tue, 2020-01-07 at 11:44 +0100, Benjamin Berg wrote:
> On Tue, 2020-01-07 at 10:21 +, Zbigniew Jędrzejewski-Szmek wrote:
> > I'm quoting from my mail from this same thread:
> >
> > │ ├─gnome-shell-wayland.service
> > │ │ ├─1501571 /usr/bin/gnome-shell
> > │
On Tue, 2020-01-07 at 10:21 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Jan 07, 2020 at 11:07:49AM +0100, Benjamin Berg wrote:
> > On Tue, 2020-01-07 at 09:47 +, Zbigniew Jędrzejewski-Szmek wrote:
> > > I wanted to ask about this too... but didn't know where ;)
> &
On Tue, 2020-01-07 at 09:47 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Jan 06, 2020 at 02:53:13PM -0600, Michael Catanzaro wrote:
> > On Mon, Jan 6, 2020 at 7:09 pm, Lennart Poettering
> > wrote:
> > > - facebook is working on making oomd something that just works for
> > > everyone,
On Tue, 2019-01-08 at 09:59 -0500, Owen Taylor wrote:
> On Tue, Jan 8, 2019 at 7:17 AM Benjamin Berg wrote:
> > On Tue, 2019-01-08 at 12:33 +0100, Miroslav Suchý wrote:
> > > Dne 08. 01. 19 v 11:35 Nicolas Mailhot napsal(a):
> > > > *which* *do* *not* *perm
Hi,
On Tue, 2019-01-08 at 10:49 -0500, Matthew Miller wrote:
> On Tue, Jan 08, 2019 at 04:22:39PM +0100, Lennart Poettering wrote:
> > > The additional information could be
> > > 10.5.124.209 - - [31/Dec/2018:09:07:21 +] "GET
> > > /metalink?repo=fedora-28=x86_64==
> > > HTTP/1.1" 200 62200
On Tue, 2019-01-08 at 12:33 +0100, Miroslav Suchý wrote:
> Dne 08. 01. 19 v 11:35 Nicolas Mailhot napsal(a):
> > *which* *do* *not* *permit* *or* *no* *longer* *permit* *the*
> > *identification* *of* *data* *subjects*
>
> How do you identify data subject solely on UUID?
You also inherently
Hi,
On Tue, 2019-01-08 at 10:06 +0100, Nicolas Mailhot wrote:
> You can turn it all the way you like getting accurate counts means
> disambiguating systems which means tracking, regardless if you do it
> in a central way or via system agents.
No, you do not need to track individual machines.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, 2017-12-22 at 09:17 -0800, Adam Williamson wrote:
> On Fri, 2017-12-22 at 07:01 -0500, Solomon Peachy wrote:
> > Especially since Fedora's maintainers *already* compile it, including
> > changing some of the defaults. What's a couple more?
Hi,
we are currently looking into enabling us to test laptops more
effectively. There are two main parts to the issue, which is to
1. have a system to run semi-automated tests on a standalone machine
and submit the results to an online server ("Fedora Tested Laptops")
and to
2.
54 matches
Mail list logo
