Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=253630
lexual <lex.lists(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|lex.lists(a)gmail.com |
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Product: Fedora
Version: 34
Component: kf5-akonadi-server
Ben Cotton <bcotton(a)redhat.com> has granted Ben Cotton <bcotton(a)redhat.com>'s
request for fedora_prioritized_bug:
Bug 1953675: Akonadi does not start due to DB failure
https://bugzilla.redhat.com/show_bug.cgi?id=1953675
--- Comment #7 from Ben Cotton <bcotton(a)redhat.com> ---
This was accepted as a Prioritized Bug in today's meeting.
Product: Fedora
Version: 34
Component: dracut
Adam Williamson <awilliam(a)redhat.com> has asked for fedora_prioritized_bug:
Bug 1964879: Boot fails, or slow and partly broken, with dracut 054+ and
bluetooth keyboard (possibly other scenarios also)
https://bugzilla.redhat.com/show_bug.cgi?id=1964879
--- Comment #32 from Adam Williamson <awilliam(a)redhat.com> ---
Flagging for CommonBugs and nominating as a prioritized bug. This seems like a
pretty bad problem.
Product: Fedora
Version: 32
Component: dnf
Miro Hrončok <mhroncok(a)redhat.com> has asked for fedora_prioritized_bug:
Bug 1812596: repoquery suddenly missing results in --whatrequires on Fedora 32+
(seem to be related to virtual provides)
https://bugzilla.redhat.com/show_bug.cgi?id=1812596
--- Comment #5 from Miro Hrončok <mhroncok(a)redhat.com> ---
Proposing this as a prioritized bug.
https://bugzilla.redhat.com/show_bug.cgi?id=250843
Jordan <spiffyclean62(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spiffyclean62(a)gmail.com
--- Comment #10 from Jordan <spiffyclean62(a)gmail.com> ---
It sounds like you've delved deep into the technicalities, specially with the
issues associated with filesystem consistency and metadata validation.
Your approach with the use of xfs_freeze/thaw around grub sell off to clear up
the striking difficulty is interesting, even though you rightly point out its
obstacles, specifically while /boot is part of the foundation filesystem.
Regarding the validation technique in grub-set up, if it aims to make sure
record integrity and area accuracy, perhaps exploring alternatives like FIBMAP
calls may be useful, as you cautioned. These calls might provide a extra
reliable manner to confirm file places with out the want for freezing or
unmounting the filesystem.
I also faced the bug on my site but its solve now :
https://spiffyclean.com.au/commercial-cleaning-company-melbourne/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=250843
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…