On Saturday, May 21, 2022 2:34:53 AM EDT Samuel Sieb wrote:
> On 2022-05-20 15:23, Garry T. Williams wrote:
> > Anyone know what I managed to mess up here?
> >
> > Update using updates-testing gives this error:
> >
> > Error: Transaction test error:
&
_copr:copr.fedorainfracloud.org:marcdeop:plasma.repo
enabled, but I downgraded everything from there and downgraded back to
original repos and then upgraded before enabling updates-testing.)
--
Garry T. Williams
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email
On Tuesday, May 3, 2022 6:55:45 AM EDT Kamil Paral wrote:
> On Tue, May 3, 2022 at 12:58 AM Garry T. Williams
> wrote:
> > Thanks, Adam. But reinstalling already failed to fix the problem for
> > me.
>
> Gary, have you tried reinstalling just selinux-policy, or ha
On Monday, May 2, 2022 6:17:46 PM EDT Adam Williamson wrote:
> On Mon, 2022-05-02 at 16:51 -0400, Garry T. Williams wrote:
> > How do I fix an F36 system that gets this error:
> >
> > $ sudo setsebool -PV rsync_export_all_ro true
> > Failed to resolve allow
error was created when I upgraded. This bug report was
identified and a duplicate of mine at that time (about a month ago):
https://bugzilla.redhat.com/show_bug.cgi?id=2075651
I have tried uninstalling and reinstalling selinux-policy to no avail.
--
Garry T. Williams
On Wednesday, June 16, 2021 1:50:57 PM EDT Samuel Sieb wrote:
> On 2021-06-16 10:08 a.m., Garry T. Williams wrote:
> > On Wednesday, June 16, 2021 12:46:06 PM EDT Adam Williamson wrote:
> >> Hi folks! Just wanted to flag an F34 update to get tested so we can
> &
fc34 updates-testing 170 k
Installing weak dependencies:
gimp-jxl-plugin x86_64 0.3.7-2.fc34 updates 922 k
jxl-pixbuf-loader x86_64 0.3.7-2.fc34 updates 414 k
mypaint-brushes
his update (pipewire-0.3.25-1.fc34.x86_64), so
maybe that will help. I am pleased to report that it eliminated a
very annoying latency with bluetooth and pulseaudio that I have had
for years.
--
Garry T. Williams
___
test mailing list -- test@lists.fe
ore trying this, sound was immediately gone and the log
showed those errors.
--
Garry T. Williams
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https:
audio.)
--
Garry T. Williams
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
ing it.
https://bugzilla.redhat.com/show_bug.cgi?id=1912150
--
Garry T. Williams
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/p
bleshooting' menu, and see if it successfully reaches the
> desktop. Here's an image you can use:
>
> https://kojipkgs.fedoraproject.org/compose/branched/
Fedora-30-20190301.n.0/compose/Workstation/x86_64/iso/Fedora-
Workstation-Live-x86_64-30-20190301.n.0.iso
Dell XPS-13 laptop i7-8
lem was something else entirely since a
manual change didn't boot Fedora.
I may try the manual downgrade, if I get time. I am usually
physically away from this system so I will retrieve the old versions
and be ready when I can get the time.
Again, thank you for your thoughtful follow-
.x86_64
grub2-pc-2.02-62.fc29.x86_64
grub2-pc-modules-2.02-62.fc29.noarch
grub2-tools-2.02-62.fc29.x86_64
grub2-tools-efi-2.02-62.fc29.x86_64
grub2-tools-extra-2.02-62.fc29.x86_64
grub2-tools-minimal-2.02-62.fc29.x86_64
shim-x64-15-7.x86_64
garry@vfr$
--
Garry T. Williams
On Saturday, October 13, 2018 5:42:15 PM EDT Chris Murphy wrote:
> On Sat, Oct 13, 2018 at 1:30 PM, Garry T. Williams
> wrote:
> > On Saturday, October 13, 2018 3:12:44 PM EDT Samuel Sieb wrote:
> >> On 10/13/18 10:39 AM, Garry T. Williams wrote:
> >>
> >&
On Saturday, October 13, 2018 3:12:44 PM EDT Samuel Sieb wrote:
> On 10/13/18 10:39 AM, Garry T. Williams wrote:
> > What am I doing wrong here that I cannot boot after a system-upgrade?
>
> "Doesn't boot" is no information. What exactly is happening?
Sorry, the
/run/user/1000
--
Garry T. Williams
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines:
13 version restored normal operation.
I gave negative karma[*].
It's usually best to copy and paste error messages.
_
[*] https://bugzilla.redhat.com/show_bug.cgi?id=1064099
--
Garry T. Williams
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://
On Tuesday, August 02, 2011 10:12:54 Dennis Jacobfeuerborn wrote:
> Hi,
> I just stumbled over a strange phenomenon that makes top go bananas.
>
> To reproduce open one shell window (and only one), switch to root
> and run "top". Now close the shell window (without quitting top
> first). top will
On Sunday, May 29, 2011 13:44:56 Garry T. Williams wrote:
> I think the rpm database gets into a state that needs attention. This
> fixed it:
>
> sudo rm -f /var/lib/rpm/__db.001 /var/lib/rpm/__db.002 \
> /var/lib/rpm/__db.003 /var/lib/rpm/__db.004
> su
On Monday, May 30, 2011 06:44:39 He Rui wrote:
> On Sun, 2011-05-29 at 13:44 -0400, Garry T. Williams wrote:
> > I upgraded to F15 from F14 using the DVD yeterday. I experienced a
> > few glitches:
> > 3. The first boot ended at multiuser.target instead of
> > gra
On Sunday, May 29, 2011 13:44:56 Garry T. Williams wrote:
> I upgraded to F15 from F14 using the DVD yeterday. I experienced a
> few glitches:
6. Oh, I forgot to mention that there was no operating system log after
the upgrade. That one was fixed with this:
sudo systemctl
I upgraded to F15 from F14 using the DVD yeterday. I experienced a
few glitches:
1. I was not asked to include the updates repository during the
update process. Sad. Now I will have to do an update after first
boot.
2. This is apparently a general problem not really related to the
specific u
23 matches
Mail list logo
