Is anyone working on, or able to assist with the fact that nouveau suffers
crashes potentially causing data loss on all versions of kernel 5.12 with
Fedora 34? It's a pretty serious regression especially as the update from 5.11
to 5.12 happened in the middle of the F34 cycle.
I'm unfortunately
On 25/05/2021 17:20, Otto Urpelainen wrote:
[..]
type=AVC msg=audit(1621790705.033:963): avc: denied { write } for
pid=136319 comm="gnome-shell" name="dbus-QyPy1X95QF" dev="tmpfs" ino=368
scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=system_u:object_r:tmp_t:s0 tclass=sock_file per
Since upgrading from a fairly clean F33 (installed from scratch a few months
ago) to F34 I get regular (upon each desktop login, I believe) SELinux denials
on what appears to be a dbus socket from gnome-shell and other components:
type=AVC msg=audit(1621790705.033:963): avc: denied { write }
On 31/01/2020 11:22, Richard W.M. Jones wrote:
Anyway the news is that none of these branches can be compiled with
our OCaml 4.10.0-beta-1 compiler.
Thanks for picking this up. FWIW (in my limited role as the one who built
unison227 for EPEL6), I have no interest (or ability) to engage in th
I realise this is not exactly news, but when replacing Ask Fedora, was there a
reason to break all the links on the entire web to existing solutions, rather
than just putting the new system on a different domain? Or, failing that, at
least adding (conditional) redirects and/or links to the "old"
On 30/09/2019 21:02, Stephen John Smoogen wrote:
On Mon, 30 Sep 2019 at 14:54, Tim Jackson wrote:
Where is the canonical source these days for establishing package
(co-)ownership, in particular in relation to individual branches?
branch ownership died 2-3 years ago. a replacement was
Old, irregular maintainer here; apologies if this is a stupid question.
Where is the canonical source these days for establishing package
(co-)ownership, in particular in relation to individual branches?
I looked pretty much everywhere I could think of, including the following:
- https://src.
On 11/05/18 21:23, Björn Persson wrote:
Tim Jackson wrote:
Firstly, could the error message "invalid path: ~/.fedora-server-ca.cert" be
improved? There _is_ a CA certificate in that location, untouched since August
2014.
I think that error message is probably correct. Tilde expa
On 11/05/18 19:23, Patrick マルタインアンドレアス Uiterwijk wrote:
You very likely have an /etc/koji.conf.rpmnew.
Could you please move that over /etc/koji.conf?
If not, maybe you have a ~/.koji, with custom config, you might need to remove.
Thanks! That solved it. I had a ~/.koji/config, last modified
On 11/05/18 14:39, Chenxiong Qi wrote:
On Fri, May 11, 2018 at 5:35 PM, Tim Jackson wrote:
As an example, today's error is something to do with logging
into Koji when running "fedpkg build":
For "fedpkg build", should just need "kinit [FAS username]@FEDORAPR
As an infrequent contributor, I have unfortunately had to resign myself to the
fact that every time I try to make a change to a package, something has
broken/changed, and thus 95% of the time goes on fixing the environment and 5%
on the package in question. However, I do wonder whether, when ref
gphpedit has been FTBFS for a while, due to the fact that its dependency
gtkhtml2 was also FTBFS and is now orphaned.
As a consequence (and due to limited resources) I'm planning to orphan
gphpedit.
If anyone would like to do the necessary work to fix and take over
gtkhtml2, or remove the depende
On 28/01/10 01:03, Jesse Keating wrote:
> Unblocked orphan backintime
In principle I'll take this to keep it in Fedora since I use it and it's a
nice app. However with limited time I wasn't in a great rush to add any more
packages to my list so if anyone else would like to take over I'd happily
Today Bugzilla seems to be missing bugs from my "front page"; it shows zero
for "Open Issues: Assigned to You" and many other areas where yesterday there
were quite a few bugs (and there are definitely ones that are open and
assigned to me). Even clicking the "show list" doesn't show any, e.g.:
14 matches
Mail list logo
