DNF Error with package Conflicts.

[Stephen Morris]

Hi,
    When I did a dnf upgrade today I got the following messages at the 
beginning of dnf output.


Error:
 Problem: cannot install the best update candidate for package 
qt5-qtbase-5.13.2-5.fc32.x86_64

  - problem with installed package qt5-qtbase-5.13.2-5.fc32.x86_64
  - cannot install the best update candidate for package 
qgis-3.12.3-1.fc32.x86_64

  - problem with installed package qgis-3.12.3-1.fc32.x86_64
  - package qgis-3.12.3-1.fc32.x86_64 requires 
libQt5Core.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers 
can be installed
  - package qgis-3.12.3-1.fc32.x86_64 requires 
libQt5Sql.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers 
can be installed
  - cannot install both qt5-qtbase-5.14.2-5.fc32.x86_64 and 
qt5-qtbase-5.13.2-5.fc32.x86_64
  - cannot install both qt5-qtbase-5.13.2-4.fc32.x86_64 and 
qt5-qtbase-5.14.2-5.fc32.x86_64


Is this because qt5-qtbase-5.14.2-5.fc32.x86_64 doesn't supercede 
qt5-qtbase-5.13.2-4.fc32.x86_64?


regards,
Steve
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 17/6/20 1:52 am, Tom H wrote:

On Tue, Jun 16, 2020 Stephen Morris  wrote:

On 16/6/20 9:06 am, Ed Greshko wrote:

On 2020-06-16 07:01, Tom H wrote:

The kernel options are in the BLS entries, so it doesn't matter
what you have in grubenv.

 From the grub2 changelog on may 13th:

Store cmdline in BLS snippets instead of using a grubenv variable

The kernel cmdline was stored as a kernelopts variable in the
grubenv file and the BLS snippets used that. But this turned out to
be fragile since the grubenv file could be removed or get corrupted
easily.

To prevent the entries to not have a cmdline if the grubenv can't
be read, a fallback variable was set in the GRUB config file. But
this still caused issues since the config needs to be re-generated
to change the parameters.

Instead, let's store the cmdline in the BLS snippets. This will
make the configuration more robust, since it will work even without
the grubenv file and the BLS entries will contain all the
information needed to boot.

Thanks for that.

Just to complete my understanding, by the BLS snippets you mean the

/boot/loader/entries/*.conf

files?

If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how
does one disable BLS if we don't want it?

You MAY be right in assuming that Fedora might choose only to support BLS.

If that day comes, we'll use BLS. I hope that, by then, we'll have a
way to customize the snippets, for example, not to use the machine-id
UUIDs.
My issue with BLS is the way it displays the kernel menu entries in 
grub, it is exactly the same as the way grubby showed the entries which 
I also hated, consequently I refuse to use BLS until such time as they 
provide an option to get the menus displayed as an entry for the current 
kernel and an expandable menu for all other kernels and the recovery 
entries.


regards,
Steve


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: frama-c can't start up on simple example

[Richard W.M. Jones]

On Thu, Jun 18, 2020 at 03:15:13PM -0600, Jerry James wrote:
> On Thu, Jun 18, 2020 at 9:01 AM Jerry James  wrote:
> > I see this in the log:
> >
> > [wp] User Error: Prover 'alt-ergo' not found in why3.conf
> >
> > which is a lie.  Prover alt-ergo is most definitely listed in
> > why3.conf.  I'll debug this.  Stand by.
> 
> Run "why3 config --full-config", then start frama-c again.

That works, thanks!

> For the
> long version of the story, read
> https://git.frama-c.com/pub/frama-c/-/issues/12

Subscribed.  Thanks for the detective work!

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: DNF Error with package Conflicts.

[Samuel Sieb]

On 6/19/20 12:01 AM, Stephen Morris wrote:

Hi,
     When I did a dnf upgrade today I got the following messages at the 
beginning of dnf output.


Error:
  Problem: cannot install the best update candidate for package 
qt5-qtbase-5.13.2-5.fc32.x86_64

   - problem with installed package qt5-qtbase-5.13.2-5.fc32.x86_64
   - cannot install the best update candidate for package 
qgis-3.12.3-1.fc32.x86_64

   - problem with installed package qgis-3.12.3-1.fc32.x86_64
   - package qgis-3.12.3-1.fc32.x86_64 requires 
libQt5Core.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers 
can be installed


Is this because qt5-qtbase-5.14.2-5.fc32.x86_64 doesn't supercede 
qt5-qtbase-5.13.2-4.fc32.x86_64?


More likely that qgis still needs to be rebuilt with the new qt5.  If 
you don't need it, try adding "--allowerasing" to the dnf command.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: DNF Error with package Conflicts.

[Ed Greshko]

On 2020-06-19 16:43, Samuel Sieb wrote:
> On 6/19/20 12:01 AM, Stephen Morris wrote:
>> Hi,
>>  When I did a dnf upgrade today I got the following messages at the 
>> beginning of dnf output.
>>
>> Error:
>>   Problem: cannot install the best update candidate for package 
>> qt5-qtbase-5.13.2-5.fc32.x86_64
>>    - problem with installed package qt5-qtbase-5.13.2-5.fc32.x86_64
>>    - cannot install the best update candidate for package 
>> qgis-3.12.3-1.fc32.x86_64
>>    - problem with installed package qgis-3.12.3-1.fc32.x86_64
>>    - package qgis-3.12.3-1.fc32.x86_64 requires 
>> libQt5Core.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers can 
>> be installed
>
>> Is this because qt5-qtbase-5.14.2-5.fc32.x86_64 doesn't supercede 
>> qt5-qtbase-5.13.2-4.fc32.x86_64?
>
> More likely that qgis still needs to be rebuilt with the new qt5.  If you 
> don't need it, try adding "--allowerasing" to the dnf command.

FWIW, I installed qgis on a fully updated VM to see if I could reproduce the 
failure.  It installed OK.

[root@f32k ~]# rpm -q qgis qt5-qtbase
qgis-3.12.1-4.fc32.x86_64
qt5-qtbase-5.14.2-5.fc32.x86_64

I noticed the qgis package version differs from mine.  Wonder if the OP is 
getting the package
from a non-fedora source?


-- 
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Microphone trouble [SOLVED] [CLOSED]

[Tim via users]

On Thu, 2020-06-18 at 22:19 -0600, Joe Zeff wrote:
> It sounded just fine.  However, when I hooked up to Zoom to attend
> my weekly meeting, everybody complained about the static to the point
> that I was forced to leave because it's impossible for me to
> participate.  At this point, I'm sure that it's not my equipment. 
> It's either the Zoom software, or the server.

I'd tend to agree.  At least Skype had a test server that you could
make a fake call to, and hear a replay to know how well your end
worked.  I've never used Zoom to see what it offers.

If anyone forces me to do a Zoom conference when I don't want to, I'll
make sure I have a crappy mike.
 
-- 
 
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Microphone trouble [SOLVED] [CLOSED]

[Patrick O'Callaghan]

On Fri, 2020-06-19 at 19:23 +0930, Tim via users wrote:
> On Thu, 2020-06-18 at 22:19 -0600, Joe Zeff wrote:
> > It sounded just fine.  However, when I hooked up to Zoom to attend
> > my weekly meeting, everybody complained about the static to the point
> > that I was forced to leave because it's impossible for me to
> > participate.  At this point, I'm sure that it's not my equipment. 
> > It's either the Zoom software, or the server.
> 
> I'd tend to agree.  At least Skype had a test server that you could
> make a fake call to, and hear a replay to know how well your end
> worked.  I've never used Zoom to see what it offers.

For testing, you can also try Google Meet (http://meet.google.com),
which IIRC lets you check your equipment without setting up a meeting
(you tell it to set up a meeting, then not actually follow through).

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: DNF Error with package Conflicts.

[Ed Greshko]

On 2020-06-19 17:03, Ed Greshko wrote:
> On 2020-06-19 16:43, Samuel Sieb wrote:
>> On 6/19/20 12:01 AM, Stephen Morris wrote:
>>> Hi,
>>>  When I did a dnf upgrade today I got the following messages at the 
>>> beginning of dnf output.
>>>
>>> Error:
>>>   Problem: cannot install the best update candidate for package 
>>> qt5-qtbase-5.13.2-5.fc32.x86_64
>>>    - problem with installed package qt5-qtbase-5.13.2-5.fc32.x86_64
>>>    - cannot install the best update candidate for package 
>>> qgis-3.12.3-1.fc32.x86_64
>>>    - problem with installed package qgis-3.12.3-1.fc32.x86_64
>>>    - package qgis-3.12.3-1.fc32.x86_64 requires 
>>> libQt5Core.so.5(Qt_5.13.2_PRIVATE_API)(64bit), but none of the providers 
>>> can be installed
>>> Is this because qt5-qtbase-5.14.2-5.fc32.x86_64 doesn't supercede 
>>> qt5-qtbase-5.13.2-4.fc32.x86_64?
>> More likely that qgis still needs to be rebuilt with the new qt5.  If you 
>> don't need it, try adding "--allowerasing" to the dnf command.
> FWIW, I installed qgis on a fully updated VM to see if I could reproduce the 
> failure.  It installed OK.
>
> [root@f32k ~]# rpm -q qgis qt5-qtbase
> qgis-3.12.1-4.fc32.x86_64
> qt5-qtbase-5.14.2-5.fc32.x86_64
>
> I noticed the qgis package version differs from mine.  Wonder if the OP is 
> getting the package
> from a non-fedora source?
>
>

It would seem the OP's version comes from the copr/danis repository.

The page https://copr.fedorainfracloud.org/coprs/dani/qgis/

indicates The following unofficial repositories are provided as-is by owner of 
this project. Contact the owner directly for bugs or issues (IE: not bugzilla).

So, the owner will probably need to update their package.


-- 
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Random crashes/reboots under F32

[Justin Moore]

About four weeks ago I upgraded from F30 to F32. I've been using this same
hardware for a few years now, and it worked fine* under multiple versions
of Fedora.

However since I upgraded to F32 I've been finding my system randomly
rebooting about every 8-14 days. I'll just come back to it and it'll be
sitting at the encrypted partition unlock screen. When I check system logs
(journalctl -b [bootID] -r) there's no indication that something went
horribly wrong. No error messages, no nothing. It's just fine until I'm
staring at a reboot screen.

It hasn't (yet) happened while I've been sitting at the computer so I can't
tell if it's a clean shutdown or a hard reboot. Googling for "fedora" or
"F32" and "random reboots" or "random crashes" doesn't bring up anything
particularly helpful.

Tips? Suggestions?

Thanks in advance.
-justin

*Standard disclaimer about things like systemd and journalctl being an
absolute dumpster fire
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Random crashes/reboots under F32

[Richard Shaw]

On Fri, Jun 19, 2020 at 8:43 AM Justin Moore 
wrote:

> About four weeks ago I upgraded from F30 to F32. I've been using this same
> hardware for a few years now, and it worked fine* under multiple versions
> of Fedora.
>
> However since I upgraded to F32 I've been finding my system randomly
> rebooting about every 8-14 days. I'll just come back to it and it'll be
> sitting at the encrypted partition unlock screen. When I check system logs
> (journalctl -b [bootID] -r) there's no indication that something went
> horribly wrong. No error messages, no nothing. It's just fine until I'm
> staring at a reboot screen.
>
> It hasn't (yet) happened while I've been sitting at the computer so I
> can't tell if it's a clean shutdown or a hard reboot. Googling for "fedora"
> or "F32" and "random reboots" or "random crashes" doesn't bring up anything
> particularly helpful.
>
> Tips? Suggestions?
>

Purely a SWAG but newer kernels may either have a bug, or may be exposing a
problem which a previous kernel ignored or didn't trigger. For random stuff
like this I would look to see if there's a firmware update for your BIOS.

Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Random crashes/reboots under F32

[George N. White III]

On Fri, 19 Jun 2020 at 10:43, Justin Moore  wrote:

> About four weeks ago I upgraded from F30 to F32. I've been using this same
> hardware for a few years now, and it worked fine* under multiple versions
> of Fedora.
>

> However since I upgraded to F32 I've been finding my system randomly
> rebooting about every 8-14 days. I'll just come back to it and it'll be
> sitting at the encrypted partition unlock screen. When I check system logs
> (journalctl -b [bootID] -r) there's no indication that something went
> horribly wrong. No error messages, no nothing. It's just fine until I'm
> staring at a reboot screen.
>

Start keeping a log.   For years I was going in to work 7 days a week to
babysit an unreliable system used to capture "irreplacable" data.   From
the logs I determined that the system never failed on Sunday, so I went
from a 7-day work week to 6 days.


>
> It hasn't (yet) happened while I've been sitting at the computer so I
> can't tell if it's a clean shutdown or a hard reboot. Googling for "fedora"
> or "F32" and "random reboots" or "random crashes" doesn't bring up anything
> particularly helpful.
>
> Tips? Suggestions?
>

"last" should show if you had an orderly shutdown or a crash.

There is a good reason that linux distros include a memory test -- use it.
Sometimes reseating memory cards is enough to get past a test failure.

After memory common old PC random crashes are due to bad cables,
connectors, or power supplies.   Particularly if you live in a hot, humid,
area (or take your PC to sea) you may find green corrosion on some
connections.   You can buy "contact enhancer" that is really helpful for
seagoing or ocean adjacent gear.   At my work we generally had a stack of
old PC's "all made out of ticky tacky. And they all look just the same…",
so I could swap cables and power supplies to keep a few running.   Before
retiring I managed a 7x24 industrial PC used to control a satellite dish.
Twice the system started having random crashes.  Inspection of the system
board revealed bulging capacitors.
   I bought a new MB and
replaced the bad capacitors on the original.   Then the new MB failed the
same way, so when I retired it was running on the repaired board.  That MB
supported a range of CPU clock speeds.  Normally I run 7x24 systems at the
lowest clock speed for longevity, but we were using time consuming software
decryption so the system used the fastest available CPU.


-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: flatpak question

[David]

The flatpak message that I described is no longer appearing.My "sudo
flatpak update" is back to normal.

For those of you brave enough or curious enough to try Rawhide, it is now
on kernel
5.8.0-0.rc1. So far so good on my install.I bet there are a whole
lot of GNU/Linux users that do not know the specific differences between
Fedora Rawhide and OpenSUSE Tumbleweed.I hope to be able to learn that
topic and explain it to less-savvy GNU/Linux users what the hoopla is all
about - at least from my perspective - as a user and not a developer or
packager or tester. I like them both, but trying to focus on learning
the very basics of Rawhide.   I haven't really used Tumbleweed in almost a
year though.Supposedly OpenSUSE has a version more cutting-edge than
Tumbleweed.I plan to look into that someday. For those of you who
have never used Rawhide, when you run "sudo dnf update," the packages are
sometimes the git-version.   Many of the packages are labelled in their
filename and version something like: "LibRaw.x86_64
0.20-0.beta1.fc33.1"
and are usually in one of two repositories:Rawhide and Anaconda.
Feel free to correct me on all this. I have been advised numerous times
that I should not be using Rawhide, evening though I have been using it as
my daily-driver and only operating system for almost a year. One
alleged reason, is that debugging programs are running, which hinder
performance.

I had hopes of building my first AMD computer this week, but the stress
from all the virus hysteria and civil unrest where I am has taken a toll on
me.Anybody out there using the
ASUS Prime X570-Pro with Fedora Workstation on hardware ?

David Locklear
Arcola, Texas USA
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How do I change the grub kernel boot parameters in F32 ?

[Jonathan Billings]

On Jun 19, 2020, at 03:34, Stephen Morris  wrote:
> 
> My issue with BLS is the way it displays the kernel menu entries in grub, it 
> is exactly the same as the way grubby showed the entries which I also hated, 
> consequently I refuse to use BLS until such time as they provide an option to 
> get the menus displayed as an entry for the current kernel and an expandable 
> menu for all other kernels and the recovery entries.


Do you mean something like changing:

GRUB_DISABLE_SUBMENU=true

... to ...

GRUB_DISABLE_SUBMENU=false

... in your /etc/default/grub?

(and of course regenerate the grub.cfg)

--
Jonathan Billings___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org