Re: Strange behavior with F40 server iso and VM

[Paolo Galtieri]

I did a little more investigating by running fdisk -l and here is what I 
found on my server install:


Disk /dev/nvme0n1: 400 GiB, 429496729600 bytes, 838860800 sectors
Disk model: VMware Virtual NVMe Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FB141BA7-BCC9-4953-85BA-9AE731D845C4

Device   Start   End   Sectors  Size Type
/dev/nvme0n1p1    2048  4095  2048    1M BIOS boot
/dev/nvme0n1p2    4096   2101247   2097152    1G Linux extended boot
/dev/nvme0n1p3 2101248 838858751 836757504  399G Linux LVM


Disk /dev/mapper/fedora-root: 15 GiB, 16106127360 bytes, 31457280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

It does create a 400GB partition it's just not accessible after boot.

On the desktop install fdisk -l shows:

Disk /dev/nvme0n1: 200 GiB, 214748364800 bytes, 419430400 sectors
Disk model: VMware Virtual NVMe Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1ADF4978-4138-465D-A6B0-871EEAF4E90F

Device   Start   End   Sectors  Size Type
/dev/nvme0n1p1    2048  4095  2048    1M BIOS boot
/dev/nvme0n1p2    4096   2101247   2097152    1G Linux extended boot
/dev/nvme0n1p3 2101248 419428351 417327104  199G Linux filesystem

So how do I access that 400 GB partition after I boot my server?

Paolo


On 10/12/24 18:22, Jonathan Billings wrote:

On Oct 12, 2024, at 20:17, Paolo Galtieri  wrote:


Folks,
 this is an issue that has me frustrated.  I created a VM under 
VMware and VirtualBox and allocated 400GB as the disk size.  I 
installed the F40 server iso on the VM, and it showed the disk size 
as 400GB, and the install went fine. However, when I booted the VM 
and looked at the disk size it was 15GB.  This happened on both 
VMware and VirtualBox.  I created another VM and installed MATE-F40 
iso and when I check the disk size there it was in fact 400GB.  So 
for shits and grins I tried running VMware on Windows 11 and created 
a F40-server VM there and it too showed the disk size as 15GB.  Why 
is there this limit?  Is there anyway to make it the size I want?


If you used the Server install ISO I believe it creates a 15 GB root 
(/) filesystem by default, as described in the documentation:


https://docs.fedoraproject.org/en-US/fedora-server/installation/#_storage_organization

This is not a bug and not something related to your virtualization 
software.


--
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange behavior with F40 server iso and VM

[Paolo Galtieri]

That's what I thougt, except it didn't.  After adding other packages it got
to 94% full and I kept getting pop-ups about my disk being full. The
install of the MATE desktop iso showed the disk allocated at the 400GB I
requested.

Paolo

On Sat, Oct 12, 2024, 6:28 PM Jonathan Billings  wrote:

> On Oct 12, 2024, at 20:17, Paolo Galtieri  wrote:
>
>
> Folks,
>  this is an issue that has me frustrated.  I created a VM under VMware and
> VirtualBox and allocated 400GB as the disk size.  I installed the F40
> server iso on the VM, and it showed the disk size as 400GB, and the install
> went fine.  However, when I booted the VM and looked at the disk size it
> was 15GB.  This happened on both VMware and VirtualBox.  I created another
> VM and installed MATE-F40 iso and when I check the disk size there it was
> in fact 400GB.  So for shits and grins I tried running VMware on Windows 11
> and created a F40-server VM there and it too showed the disk size as 15GB.
> Why is there this limit?  Is there anyway to make it the size I want?
>
>
> If you used the Server install ISO I believe it creates a 15 GB root (/)
> filesystem by default, as described in the documentation:
>
>
> https://docs.fedoraproject.org/en-US/fedora-server/installation/#_storage_organization
>
> This is not a bug and not something related to your virtualization
> software.
>
> --
> 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
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
-- 
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange behavior with F40 server iso and VM

[Paolo Galtieri]

I'm using the Fedora-Server-dvd-x86_64-40-1.14.iso which I downloaded 
from the Fedora repository.  After I booted the system I ran df and got:


pgaltieri@localhost:~$ df
Filesystem  1K-blocks    Used Available Use% Mounted on
/dev/mapper/fedora-root  15663104 1763300  13899804  12% /
devtmpfs 4096   0  4096   0% /dev
tmpfs  986020   0    986020   0% /dev/shm
tmpfs  394412    1252    393160   1% /run
tmpfs  986024   0    986024   0% /tmp
/dev/nvme0n1p2 983040  292468    690572  30% /boot
tmpfs  197204   4    197200   1% /run/user/1000

as opposed to the MATE-F40 install

Filesystem 1K-blocks    Used Available Use% Mounted on
/dev/nvme0n1p3 418378752 4283924 412513740   2% /
devtmpfs    4096   0  4096   0% /dev
tmpfs    8167464  12   8167452   1% /dev/shm
tmpfs    3266988    1712   3265276   1% /run
tmpfs    8167464  28   8167436   1% /tmp
/dev/nvme0n1p3 418378752 4283924 412513740   2% /home
/dev/nvme0n1p2    996780  321468    606500  35% /boot
tmpfs    1633492 144   1633348   1% /run/user/1000

Paolo

On 10/12/24 17:30, Samuel Sieb wrote:

On 10/12/24 5:17 PM, Paolo Galtieri wrote:

Folks,
  this is an issue that has me frustrated.  I created a VM under 
VMware and VirtualBox and allocated 400GB as the disk size.  I 
installed the F40 server iso on the VM, and it showed the disk size 
as 400GB, and the install went fine.  However, when I booted the VM 
and looked at the disk size it was 15GB.  This happened on both 
VMware and VirtualBox.  I created another VM and installed MATE-F40 
iso and when I check the disk size there it was in fact 400GB.  So 
for shits and grins I tried running VMware on Windows 11 and created 
a F40-server VM there and it too showed the disk size as 15GB.  Why 
is there this limit?  Is there anyway to make it the size I want?


Which iso did you use?
What are you looking at to see that size?



--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Strange behavior with F40 server iso and VM

[Paolo Galtieri]

Folks,
 this is an issue that has me frustrated.  I created a VM under VMware 
and VirtualBox and allocated 400GB as the disk size.  I installed the 
F40 server iso on the VM, and it showed the disk size as 400GB, and the 
install went fine.  However, when I booted the VM and looked at the disk 
size it was 15GB.  This happened on both VMware and VirtualBox.  I 
created another VM and installed MATE-F40 iso and when I check the disk 
size there it was in fact 400GB.  So for shits and grins I tried running 
VMware on Windows 11 and created a F40-server VM there and it too showed 
the disk size as 15GB.  Why is there this limit?  Is there anyway to 
make it the size I want?


Paolo
--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange issues

[Paolo Galtieri]

Barry,
 I'm using bind and this has been working for years without issues 
until this week. The dns server is running on F40 and this system I have 
upgraded from F35 -> F36 -> F37 -> F38 -> F39 -? F40 without issues.


Of course as soon as report this issue and after installing today's 
updates it all works :-)


Paolo

On 9/16/24 23:50, Barry Scott wrote:



On 17 Sep 2024, at 01:26, Paolo Galtieri  wrote:

Folks,
  recently I've run in to 2 issues that I don't know how to solve.

I have a local dns server on my network.  This has always worked and I've made 
no changes since July. Last week dns lookups from one of the systems on my 
network worked fine.  Now they all fail.

dig truckin

results in

; <<>> DiG 9.18.28 <<>> truckin
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 53771
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;truckin.INA

;; Query time: 4010 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Mon Sep 16 17:15:20 PDT 2024
;; MSG SIZE  rcvd: 36


All lookups return refused. All lookups on the server work fine. The server is 
F40 and the other system is F39. Both systems have been updated to the latest 
set of patches.

The other issue is logrotate.  It no longer seems to run automatically as a 
daily cron job as it used to.  Now in order to have the file in /var/log be 
rotated I have to run logrotate manually.  A related issue is that logrotate 
wont rotate /var/log/boot.log due to the following:

rotating pattern: /var/log/boot.log
  after 1 days (7 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/boot.log
   log /var/log/boot.log has multiple (2) hard links. Rotation of files with 
multiple hard links is not allowed for /var/log/boot.log
  -- skipping.

In order to get it to work you need to add allowhardlink to the 
/etc/logrotate.d/bootlog file.

Any help is appreciated.

Where is the local DNS running?
Is it the fedora server? If so what software are you using to provide DNS?

You might want to test with resolvectl query to see if that provides any 
insights.

Barry



Paolo
--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Strange issues

[Paolo Galtieri]

Folks,
 recently I've run in to 2 issues that I don't know how to solve.

I have a local dns server on my network.  This has always worked and 
I've made no changes since July. Last week dns lookups from one of the 
systems on my network worked fine.  Now they all fail.


dig truckin

results in

; <<>> DiG 9.18.28 <<>> truckin
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 53771
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;truckin.            IN    A

;; Query time: 4010 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Mon Sep 16 17:15:20 PDT 2024
;; MSG SIZE  rcvd: 36


All lookups return refused. All lookups on the server work fine. The 
server is F40 and the other system is F39. Both systems have been 
updated to the latest set of patches.


The other issue is logrotate.  It no longer seems to run automatically 
as a daily cron job as it used to.  Now in order to have the file in 
/var/log be rotated I have to run logrotate manually.  A related issue 
is that logrotate wont rotate /var/log/boot.log due to the following:


rotating pattern: /var/log/boot.log
 after 1 days (7 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/boot.log
  log /var/log/boot.log has multiple (2) hard links. Rotation of files 
with multiple hard links is not allowed for /var/log/boot.log

 -- skipping.

In order to get it to work you need to add allowhardlink to the 
/etc/logrotate.d/bootlog file.


Any help is appreciated.

Paolo
--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange laptop behavior #2

[Paolo Galtieri]

I did and everything worked.  But my apcupsd.conf file has NOLOGON 
disabled so the file should never have been created, or at least so I 
thought.


Paolo

On 8/25/24 11:36, Garry T. Williams wrote:

On Friday, August 23, 2024 5:53:53 PM EDT Paolo Galtieri wrote:

  I previously sent a message regarding my laptop powering off
  unexpectedly.  Here is an update.  Power came back on, but I cannot
  login to my laptop.  When I try to login to the mate gui it replies
  with power failure and authentication failure.

Try removing the /etc/nologin file (as root, of course).



--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange laptop behavior #2

[Paolo Galtieri]

What confuses me is according to the apcupsd.conf file NOLOGON is 
disabled.  So it should never have created the nologin file in /etc to 
block me from being able to login as a normal user.  Also there is no 
way to tell apcupsd that it's a laptop.  So when there is 5 minutes left 
on the UPS battery apcupsd will initiate a system shutdown. This is 
great for one of my systems but not for the laptop which can run without 
mains.


Paolo

On 8/23/24 22:43, Samuel Sieb wrote:

On 8/23/24 2:53 PM, Paolo Galtieri wrote:

Folks,
  I previously sent a message regarding my laptop powering off 
unexpectedly.  Here is an update.  Power came back on, but I cannot 
login to my laptop.  When I try to login to the mate gui it replies 
with power failure and authentication failure.  If I enter 
ctrl-alt-F1, login as root  I can login. If I then enter su - 
pgaltieri I can login as me.  If I then enter su - pgaltieri it 
prompts for password and when I enter my passwd I can login just 
fine.  This problem occurs on both my systems there were shutdown due 
to the power outage.  What do I have to do to be able to log in?  
This is happening with F39 and F40.


This would all make sense if you have the UPS control connected to the 
laptop.  I suggest you unplug that for now to get normal use of your 
laptop.




--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Strange laptop behavior #2

[Paolo Galtieri]

Folks,
 I previously sent a message regarding my laptop powering off
unexpectedly.  Here is an update.  Power came back on, but I cannot login
to my laptop.  When I try to login to the mate gui it replies with power
failure and authentication failure.  If I enter ctrl-alt-F1, login as root
I can login. If I then enter su - pgaltieri I can login as me.  If I then
enter su - pgaltieri it prompts for password and when I enter my passwd I
can login just fine.  This problem occurs on both my systems there were
shutdown due to the power outage.  What do I have to do to be able to log
in?  This is happening with F39 and F40.

Paolo
-- 
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Unexpected laptop behavior

[Paolo Galtieri]

I normally run my laptop on AC power.  I also have it plugged into a UPS.
Today the power went out.  The power applet on the mate desktop reported I
had 7298 hours of laptop run time and 5 minutes of UPS.  The laptop then
powered itself off.  Can someone tell me what I might have have
misconfigured?

Paolo
-- 
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: logrotate service failing

[Paolo Galtieri]

I'm running syslog because that has what has always been running.  This 
was from before systemd.  Why both rsyslog and syslog-ng were running I 
have no idea.  I did not intentionally start both, I assumed only one 
would be running.


Paolo

On 7/21/24 01:15, Barry wrote:



On 21 Jul 2024, at 01:20, Paolo Galtieri  wrote:

Actually I have both running.

That will not work. Only one must be running.

Just to check; are you using syslog because systemd journal is not covering 
your use-case?

If journal is sufficient then remove both the syslog daemons.

Barry




--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: logrotate service failing

[Paolo Galtieri]

Actually I have both running.

Paolo

On 7/20/24 16:37, Todd Zullinger wrote:

Paolo Galtieri wrote:

It's interesting that both packages are available on F39.
Is there a reason to have both?  And if only one should be
installed which?

It's not really different than having multiple web browsers
or desktop environments.  Some folks like rsyslog, some like
syslog-ng.  You don't need both (and they likely conflict if
you try to start them both).  You will need to determine
which syslog daemon you are running to know which you can
remove.




--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: logrotate service failing

[Paolo Galtieri]

It's interesting that both packages are available on F39. Is there a 
reason to have both?  And if only one should be installed which?


Paolo

On 7/20/24 14:27, Todd Zullinger wrote:

Go Canes wrote:

On Sat, Jul 20, 2024 at 3:49 PM Paolo Galtieri  wrote:

I wonder then if this is an issue due to dnf upgrade?  I've used dnf
upgrade to upgrade my system since at least F35.  I wonder if at some
point there was a syslog file which then became rsyslog and the old
syslog file was never removed.

I've upgraded since before F35, and at F39 like Tom Horsely I have
/etc/logrotate.d/rsyslog, but not syslog.

In cases like this, using rpm¹ and/or dnf² to determine what
package provides each file is usually a good place to start.
In this case, rsyslog provides the rsyslog entry (not
surprisingly) and syslog-ng provides the syslog file.

If you are using rsyslog, you can uninstall syslog-ng to
remove the duplicate definitions in /etc/logrotate.d.

¹ rpm -qf /etc/logrotate.d/{,r}syslog
² dnf provides /etc/logrotate.d/{,r}syslog




--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: no sound on bluetooth headphones

[Paolo Galtieri]

I'm running F39 and I can't get any Bluetooth devices to work.  
Bluetooth speakers used to work, but now neither speakers nor headphones 
work.  They do work with Android phone and tablet.


Paolo

On 7/18/24 13:32, Geoffrey Leach wrote:

Using bluetooth on Fedora 40/xcfe4 for the first time

Headphone pair OK
Bluetooth is active and running
Bluetooth Manager sees headphones
Volume Control  does not see the headphones

Testing with mplayer foo.mp3; sound at speakers

I'm assuming that there is some critical enabling that needs to happen.
Suggestions?

Thanks



--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: logrotate service failing

[Paolo Galtieri]

I wonder then if this is an issue due to dnf upgrade?  I've used dnf 
upgrade to upgrade my system since at least F35.  I wonder if at some 
point there was a syslog file which then became rsyslog and the old 
syslog file was never removed.


Paolo

On 7/20/24 12:33, Tom Horsley wrote:

On Sat, 20 Jul 2024 12:05:10 -0700
Paolo Galtieri wrote:


A little investigation showed the following in /etc/logrotate.d

rsyslog:/var/log/messages
syslog:/var/log/messages

I don't have a syslog file in my /etc/logrotate.d, only rsyslog.

I'm running fedora 40 and logrotate seems to be working.


--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

logrotate service failing

[Paolo Galtieri]

I have updated my system using dnf upgrade for several releases.  I am 
currently running F39.  Today I was looking at my running services and 
noticed that the logrotate.service is failing to start due to the 
following error:


Jul 20 11:49:41 caseyjones.homenet192-168-10.com logrotate[307129]: 
error: syslog:1 duplicate log entry for /var/log/cron
Jul 20 11:49:41 caseyjones.homenet192-168-10.com logrotate[307129]: 
error: syslog:1 duplicate log entry for /var/log/maillog
Jul 20 11:49:41 caseyjones.homenet192-168-10.com logrotate[307129]: 
error: syslog:1 duplicate log entry for /var/log/messages
Jul 20 11:49:41 caseyjones.homenet192-168-10.com logrotate[307129]: 
error: syslog:1 duplicate log entry for /var/log/secure
Jul 20 11:49:41 caseyjones.homenet192-168-10.com logrotate[307129]: 
error: syslog:1 duplicate log entry for /var/log/spooler
Jul 20 11:49:41 caseyjones.homenet192-168-10.com logrotate[307129]: 
error: found error in file syslog, skipping



A little investigation showed the following in /etc/logrotate.d

rsyslog:/var/log/messages
syslog:/var/log/messages

with the following info:

-rw-r--r--. 1 root root 221 Aug 24  2023 rsyslog
-rw-r--r--. 1 root root 210 Nov 14  2023 syslog

Why are there 2 entries and which one should I delete?

Paolo


--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 40 virtual machine

[Paolo Galtieri]

anaconda seems to run even after displaying the popup about unable to 
create the pid file.  I tried the install under VirtualBox and I didn't 
see the anaconda error. However, again the install did not complete 
because after rebooting manually it still booted off the ISO rather than 
from disk.


Paolo

On 4/23/24 11:01, Joe Zeff wrote:


On 4/23/24 11:44, Paolo Galtieri wrote:
Anaconda is unable to create /var/run/anaconda.pid because the file 
already exists. Anaconda is already running, or a previous instance 
of anaconda has crashed.


I may have to try several times before I can install it to the drive.



Have you tried deleting that file before trying again?
--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora 40 virtual machine

[Paolo Galtieri]

I tried to create a Fedora 40 virtual machine under VMware version 
17.0.2.  The ISO image boots up fine, but when I double click on the 
"Install to drive" It will often fail withe the following error:


Anaconda is unable to create /var/run/anaconda.pid because the file 
already exists. Anaconda is already running, or a previous instance of 
anaconda has crashed.


I may have to try several times before I can install it to the drive.

When it finishes installation and I click on "Finish Installation" 
nothing happens.  I expect it to say reboot system, but it does 
nothing.  I reboot manually and when it comes back up it initially says 
"Initial setup" but then the screen flashes and the login prompt appears.


Paolo
--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 update

[Paolo Galtieri]

I did do it as root otherwise it most likely wouldn't have uninstalled 
anything due to permissions.


Paolo

On 12/25/22 21:29, Slade Watkins via users wrote:

On Sun, Dec 25, 2022 at 11:30 AM Paolo Galtieri  wrote:

It was VMworkstation Pro 16.1 and it was uninstalled doing

vmware-unistall -u vmware-workstation

Hey Paolo,
Okay probably a stupid question but super important regardless, did
you perform the uninstall command (I assume you meant:
vmware-uninstall -u vmware-workstation) as root (aka su - root)?


On 12/25/22 08:07, George N. White III wrote:

On Sun, Dec 25, 2022 at 11:18 AM Paolo Galtieri  wrote:

[...]

VMware workstation was uninstalled on this system yet some parts remained.


Which vmware product did you install, how was it installed, and how did you 
uninstall it?

This looks like an issue with the vmware package, so you should report the
issue on a vmware forum where you may get help cleaning up your installation
and also trigger changes so other Fedora users don't encounter the same problem.

^^ agreed.


VMware does have uninstall documents with links for reporting problems.

https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-05E4C876-F32C-49D2-82B4-8C759691E7F5.html

Best,


-- Slade
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: F37 update

[Paolo Galtieri]

It was VMworkstation Pro 16.1 and it was uninstalled doing

vmware-unistall -u vmware-workstation

Paolo

On 12/25/22 08:07, George N. White III wrote:
On Sun, Dec 25, 2022 at 11:18 AM Paolo Galtieri  
wrote:


Folks,
   I got the following error during an update to F37

Cloning into 'vmware-host-modules'...
fatal: Remote branch workstation- not found in upstream origin
/etc/kernel/install.d/99-vmmodules.install: line 20: cd:
vmware-host-modules: No such file or directory

[...]

VMware workstation was uninstalled on this system yet some parts
remained.


Which vmware product did you install, how was it installed, and how 
did you uninstall it?


This looks like an issue with the vmware package, so you should report the
issue on a vmware forum where you may get help cleaning up your 
installation
and also trigger changes so other Fedora users don't encounter the 
same problem.


VMware does have uninstall documents with links for reporting problems.

--
George N. White III


___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-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
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

F37 update

[Paolo Galtieri]

Folks,
  I got the following error during an update to F37

Cloning into 'vmware-host-modules'...
fatal: Remote branch workstation- not found in upstream origin
/etc/kernel/install.d/99-vmmodules.install: line 20: cd: 
vmware-host-modules: No such file or directory

make: *** No targets specified and no makefile found.  Stop.
make: *** No rule to make target 'install'.  Stop.
warning: %posttrans(kernel-core-6.0.15-300.fc37.x86_64) scriptlet 
failed, exit status 2


Error in POSTTRANS scriptlet in rpm package kernel-core

This is the output of cat /etc/vmware/config

cat /etc/vmware/config
.encoding = "UTF-8"
installerDefaults.componentDownloadEnabled = "yes"
installerDefaults.autoSoftwareUpdateEnabled.epoch = "8066165664"
installerDefaults.dataCollectionEnabled.epoch = "943658"
installerDefaults.transferVersion = "1"
installerDefaults.autoSoftwareUpdateEnabled = "yes"
product.name = "VMware Workstation"
telemetryUUID = "b0e8b526-887e-11e9-b472-4cd98f6d8721"
acceptEULA = "yes"
acceptOVFEULA = "yes"
installerDefaults.dataCollectionEnabled = "no"
installerDefaults.dataCollectionEnabled.initialized = "yes"

VMware workstation was uninstalled on this system yet some parts remained.

Paolo
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Upgrade to f37 left system in messed up state

[Paolo Galtieri]

I was a little premature in saying thins started working.  It seems to 
be very hit and miss.  Wireshark shows many dns requests as refused, but 
then they start to work for a while and then start failing again.


If I run dig cnn.com from my secondary dns server I get:


; <<>> DiG 9.16.33-RH <<>> cnn.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 43912
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;cnn.com.            IN    A

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sun Nov 27 09:57:17 PST 2022
;; MSG SIZE  rcvd: 36


host cnn.com results in

Host cnn.com not found: 5(REFUSED)

nslookup
> server 192.168.10.66
Default server: 192.168.10.66
Address: 192.168.10.66#53
> cnn.com
Server:        192.168.10.66
Address:    192.168.10.66#53

** server can't find cnn.com: REFUSED
>server 192.168.10.5
Default server: 192.168.10.5
Address: 192.168.10.5#53
> cnn.com
Server:        192.168.10.5
Address:    192.168.10.5#53

Non-authoritative answer:
Name:    cnn.com
Address: 151.101.195.5



If I run

host cnn.com on the primary dns server (192.168.10.66) addresses resolve.

cnn.com has address 151.101.195.5
cnn.com has address 151.101.3.5
cnn.com has address 151.101.131.5
cnn.com has address 151.101.67.5
.
.


running

nslookup
> server 192.168.10.66
Default server: 192.168.10.66
Address: 192.168.10.66#53
> cnn.com
Server:        192.168.10.66
Address:    192.168.10.66#53

** server can't find cnn.com: REFUSED
>

on my F35 system lookups work because according to resolvectl the 
current dns server is the secondary


resolvectl

Global
 Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub
Current DNS Server: 192.168.10.66
   DNS Servers: 192.168.10.66

Link 2 (enp0s20f0u5u2u1)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
 Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS 
DNSSEC=no/unsupported

Current DNS Server: 192.168.10.5
   DNS Servers: 192.168.10.66 192.168.10.5
    DNS Domain: homenet172-16-96.com homenet192-10.com 
homenet192-100.com

    homenet192-203.com

I have no clue as to what to do to make the lookups work with both the 
primary and secondary dns servers.


Paolo


On 11/27/22 07:55, Jeffrey Walton wrote:

On Sun, Nov 27, 2022 at 10:45 AM Paolo Galtieri  wrote:

I just upgraded from fedora 36 to 37.  There were no errors reported but
after the update I get:

dnf list all
Adobe Systems Incorporated 0.0  B/s |   0  B 00:00
Errors during downloading metadata for repository 'adobe-linux-x86_64':
- Curl error (6): Couldn't resolve host name for
http://linuxdownload.adobe.com/linux/x86_64/repodata/repomd.xml [Could
not resolve host: linuxdownload.adobe.com]
Error: Failed to download metadata for repo 'adobe-linux-x86_64': Cannot
download repomd.xml: Cannot download repodata/repomd.xml: All mirrors
were tried
Fedora 37 - x86_64 0.0  B/s |   0  B 00:00
Errors during downloading metadata for repository 'fedora':
- Curl error (6): Couldn't resolve host name for
https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64
[Could not resolve host: mirrors.fedoraproject.org]
Error: Failed to download metadata for repo 'fedora': Cannot prepare
internal mirrorlist: Curl error (6): Couldn't resolve host name for
https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64
[Could not resolve host: mirrors.fedoraproject.org]


host mirrors.fedoraproject.org
host: error while loading shared libraries: libjemalloc.so.2: cannot
open shared object file: No such file or directory

libjemalloc.so.2 is found in /opt/nessus/lib/nessus/libjemalloc.so.2

I removed the Nessus package and it removed all these packages:

Nessus-8.15.1-fc20.x86_64 bind-32:9.18.8-1.fc37.x86_64
bind-chroot-32:9.18.8-1.fc37.x86_64
bind-dnssec-utils-32:9.18.8-1.fc37.x86_64
bind-libs-32:9.18.8-1.fc37.x86_64 bind-license-32:9.18.8-1.fc37.noarch
bind-utils-32:9.18.8-1.fc37.x86_64 freeipmi-1.6.10-1.fc37.x86_64
fstrm-0.6.1-5.fc37.x86_64 inxi-3.3.23-1.fc37.noarch
ipmitool-1.8.18-26.fc37.x86_64 perl-Cpanel-JSON-XS-4.32-1.fc37.x86_64
perl-JSON-XS-1:4.03-8.fc37.x86_64
perl-Types-Serialiser-1.01-7.fc37.noarch
perl-XML-Dumper-0.81-45.fc37.noarch
perl-common-sense-3.7.5-10.fc37.x86_64
xrandr-1.5.1-5.fc37.x86_64

After this, running

host cnn.com

results in:

host: error while loading shared libraries: libisc-9.18.8.so: cannot
open shared object file: No such file or directory

I got around the problem by specifying the hostname to ip address
translation in /etc/hosts.

This allowed me to update packages, one of which was to install
jemalloc, and allowed me to re-install the above packages, but I can't

Re: Upgrade to f37 left system in messed up state

[Paolo Galtieri]

The reason there are old repos is because I've been following the 
dnf-system-upgrade docs for a long time. Strangely after I posted the 
message it all started working.  I have no idea why it took so long 
before things started to work.


Paolo

On 11/27/22 07:55, Jeffrey Walton wrote:

On Sun, Nov 27, 2022 at 10:45 AM Paolo Galtieri  wrote:

I just upgraded from fedora 36 to 37.  There were no errors reported but
after the update I get:

dnf list all
Adobe Systems Incorporated 0.0  B/s |   0  B 00:00
Errors during downloading metadata for repository 'adobe-linux-x86_64':
- Curl error (6): Couldn't resolve host name for
http://linuxdownload.adobe.com/linux/x86_64/repodata/repomd.xml [Could
not resolve host: linuxdownload.adobe.com]
Error: Failed to download metadata for repo 'adobe-linux-x86_64': Cannot
download repomd.xml: Cannot download repodata/repomd.xml: All mirrors
were tried
Fedora 37 - x86_64 0.0  B/s |   0  B 00:00
Errors during downloading metadata for repository 'fedora':
- Curl error (6): Couldn't resolve host name for
https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64
[Could not resolve host: mirrors.fedoraproject.org]
Error: Failed to download metadata for repo 'fedora': Cannot prepare
internal mirrorlist: Curl error (6): Couldn't resolve host name for
https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64
[Could not resolve host: mirrors.fedoraproject.org]


host mirrors.fedoraproject.org
host: error while loading shared libraries: libjemalloc.so.2: cannot
open shared object file: No such file or directory

libjemalloc.so.2 is found in /opt/nessus/lib/nessus/libjemalloc.so.2

I removed the Nessus package and it removed all these packages:

Nessus-8.15.1-fc20.x86_64 bind-32:9.18.8-1.fc37.x86_64
bind-chroot-32:9.18.8-1.fc37.x86_64
bind-dnssec-utils-32:9.18.8-1.fc37.x86_64
bind-libs-32:9.18.8-1.fc37.x86_64 bind-license-32:9.18.8-1.fc37.noarch
bind-utils-32:9.18.8-1.fc37.x86_64 freeipmi-1.6.10-1.fc37.x86_64
fstrm-0.6.1-5.fc37.x86_64 inxi-3.3.23-1.fc37.noarch
ipmitool-1.8.18-26.fc37.x86_64 perl-Cpanel-JSON-XS-4.32-1.fc37.x86_64
perl-JSON-XS-1:4.03-8.fc37.x86_64
perl-Types-Serialiser-1.01-7.fc37.noarch
perl-XML-Dumper-0.81-45.fc37.noarch
perl-common-sense-3.7.5-10.fc37.x86_64
xrandr-1.5.1-5.fc37.x86_64

After this, running

host cnn.com

results in:

host: error while loading shared libraries: libisc-9.18.8.so: cannot
open shared object file: No such file or directory

I got around the problem by specifying the hostname to ip address
translation in /etc/hosts.

This allowed me to update packages, one of which was to install
jemalloc, and allowed me to re-install the above packages, but I can't
get dns to work on this system which happens to be my local dns server.
Fortunately I have a secondary dns server.

running dig cnn.com

results in

;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out

; <<>> DiG 9.18.8 <<>> cnn.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51775
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;cnn.com.INA

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sun Nov 27 07:39:07 PST 2022
;; MSG SIZE  rcvd: 36


Has anybody else experienced similar issues, and know how to fix this?

There is one other system I want to update to F37 but it happens to be
my secondary dns server.

I've upgraded 4 machines and 2 servers to F37 without incident.
However, I followed
https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ .

Maybe you can go through the dnf-system-upgrade doc and follow the
section on "Resolving post-upgrade issues"?

Also take a look at `dnf repolist`. Everything should say F37. I think
it is odd you are still using old repos, like for F20. `dnf repoquery
--unsatisfied` may help.

Jeff
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
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 Ar

Upgrade to f37 left system in messed up state

[Paolo Galtieri]

I just upgraded from fedora 36 to 37.  There were no errors reported but 
after the update I get:


dnf list all
Adobe Systems Incorporated 0.0  B/s |   0  B 00:00
Errors during downloading metadata for repository 'adobe-linux-x86_64':
  - Curl error (6): Couldn't resolve host name for 
http://linuxdownload.adobe.com/linux/x86_64/repodata/repomd.xml [Could 
not resolve host: linuxdownload.adobe.com]
Error: Failed to download metadata for repo 'adobe-linux-x86_64': Cannot 
download repomd.xml: Cannot download repodata/repomd.xml: All mirrors 
were tried

Fedora 37 - x86_64 0.0  B/s |   0  B 00:00
Errors during downloading metadata for repository 'fedora':
  - Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64 
[Could not resolve host: mirrors.fedoraproject.org]
Error: Failed to download metadata for repo 'fedora': Cannot prepare 
internal mirrorlist: Curl error (6): Couldn't resolve host name for 
https://mirrors.fedoraproject.org/metalink?repo=fedora-37&arch=x86_64 
[Could not resolve host: mirrors.fedoraproject.org]



host mirrors.fedoraproject.org
host: error while loading shared libraries: libjemalloc.so.2: cannot 
open shared object file: No such file or directory


libjemalloc.so.2 is found in /opt/nessus/lib/nessus/libjemalloc.so.2

I removed the Nessus package and it removed all these packages:

Nessus-8.15.1-fc20.x86_64 bind-32:9.18.8-1.fc37.x86_64
  bind-chroot-32:9.18.8-1.fc37.x86_64 
bind-dnssec-utils-32:9.18.8-1.fc37.x86_64

  bind-libs-32:9.18.8-1.fc37.x86_64 bind-license-32:9.18.8-1.fc37.noarch
  bind-utils-32:9.18.8-1.fc37.x86_64 freeipmi-1.6.10-1.fc37.x86_64
  fstrm-0.6.1-5.fc37.x86_64 inxi-3.3.23-1.fc37.noarch
  ipmitool-1.8.18-26.fc37.x86_64 perl-Cpanel-JSON-XS-4.32-1.fc37.x86_64
  perl-JSON-XS-1:4.03-8.fc37.x86_64 
perl-Types-Serialiser-1.01-7.fc37.noarch
  perl-XML-Dumper-0.81-45.fc37.noarch 
perl-common-sense-3.7.5-10.fc37.x86_64

  xrandr-1.5.1-5.fc37.x86_64

After this, running

host cnn.com

results in:

host: error while loading shared libraries: libisc-9.18.8.so: cannot 
open shared object file: No such file or directory


I got around the problem by specifying the hostname to ip address 
translation in /etc/hosts.


This allowed me to update packages, one of which was to install 
jemalloc, and allowed me to re-install the above packages, but I can't 
get dns to work on this system which happens to be my local dns server.  
Fortunately I have a secondary dns server.


running dig cnn.com

results in

;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out

; <<>> DiG 9.18.8 <<>> cnn.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51775
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;cnn.com.            IN    A

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sun Nov 27 07:39:07 PST 2022
;; MSG SIZE  rcvd: 36


Has anybody else experienced similar issues, and know how to fix this?

There is one other system I want to update to F37 but it happens to be 
my secondary dns server.


Paolo
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can one rescue a dead SSD?

[Paolo Galtieri]

If you're willing to spend the money there are companies that can try to
recover the data from the drive.  If it's just the controller it may cost
around $300 if it requires more work to recover the data it may cost you
around $2000.  I have used one company quite a few years ago and they were
able to recover the data.

Paolo

On Sat, Nov 5, 2022 at 8:39 AM Felix Miata  wrote:

> Not IME.
>
> andreas.fourn...@runbox.com composed on 2022-11-05 15:27 (UTC+0100):
>
> > So, a SSD just dieded on me, the root and home partition was on it. The
> > computer froze and after a cold boot the BIOS doesn't find the disk
> > anymore. I opened up the casing but couldn't see anything suspicious to
> > the naked eye.
>
> I've had several die. When the SSD's internal controller dies, you have a
> lousy
> paperweight, not an SSD, unless it's still under warranty - then it
> amounts to a
> token exchangeable for a working SSD with a shorter warranty.
> --
> Evolution as taught in public schools is, like religion,
> based on faith, not based on science.
>
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata
> ___
> 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
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: suspend on lid closed doesn't work

[Paolo Galtieri]

In my /etc/UPower/UPower.conf I have

IgnoreLid=false

When I close the lid of my laptop it does appear to suspend, the monitor 
goes blank and neither mouse nor keyboard respond, however after a few 
seconds everything resumes and I can login.


Paolo

On 3/21/22 09:35, Wolfgang Pfeiffer wrote:

On Mon, Mar 21, 2022 at 12:32:14AM -0700, Samuel Sieb wrote:

On 3/20/22 16:46, Wolfgang Pfeiffer wrote:

On Thu, Mar 17, 2022 at 08:27:02AM -0700, Paolo Galtieri wrote:


Is there any way to actually suspend a laptop when the lid is closed
regardless of any external devices?


Might be a result of your
/etc/systemd/logind.conf

Default in that file seems to be:
HandleLidSwitchDocked=ignore

Have you tried to set this to:
HandleLidSwitchDocked=suspend

After changes you may need to logout/login, or simply reboot your
machine. If unsure, I'd reboot.

From man logind.conf(5):

"If the system is inserted in a docking station, or if more than one
display is connected, the action specified by HandleLidSwitchDocked=
occurs"


That option doesn't make any difference.  Gnome has its own inhibitor:
gsd-power  handle-lid-switch    External monitor attached or
configuration changed recently    block

There's no way around it.


 ... except one posting on the gitlab page you mentioned suggests the
solution I recommended, and for Gnome, it seems ... ;)

Works here still on F34, X11, i3, too: single monitor connected via
HDMI to a laptop.  Except I only changed logind.conf, back in 2018,
nothing more, it seems.

In /etc/UPower/UPower.conf tho' I have this, different from what was
suggested on the gitlab page:
IgnoreLid=false

Just tested it again - works: closing the lid with a connected monitor
switches off both; resuming switches on both without issues.

Wolfgang
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: suspend on lid closed doesn't work

[Paolo Galtieri]

This is a known issue

https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/111

However it's 3 years old, and no one seems to be doing anything. I'm 
running MATE and this issue still applies, I wonder how many other DE's 
it affects.


Paolo


On 3/20/22 16:46, Wolfgang Pfeiffer wrote:

On Thu, Mar 17, 2022 at 08:27:02AM -0700, Paolo Galtieri wrote:


Is there any way to actually suspend a laptop when the lid is closed
regardless of any external devices?


Might be a result of your
/etc/systemd/logind.conf

Default in that file seems to be:
HandleLidSwitchDocked=ignore

Have you tried to set this to:
HandleLidSwitchDocked=suspend

After changes you may need to logout/login, or simply reboot your
machine. If unsure, I'd reboot.

From man logind.conf(5):

"If the system is inserted in a docking station, or if more than one
display is connected, the action specified by HandleLidSwitchDocked=
occurs"

Wolfgang
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: maybe OT

[Paolo Galtieri]

The host OS is also F34.

On 3/20/22 08:14, George N. White III wrote:

On Fri, 18 Mar 2022 at 19:47, Paolo Galtieri  wrote:

I'm having issues with a VM.


It would be useful to mention the host OS.  From the name, I guess your
VM is running Fedora 34.


The VM was originally created under VMware and has worked fine for a
while.  Today when I booted it up instead of seeing the usual MATE
login
screen I get a login prompt:

f34-01-vm:

no matter what I enter, root or pgaltieri as login it never asks for
password and immediately says login incorrect.  While it's booting
I see
several [FAILED]... messages, e.g. [FAILED] to start CUPS Scheduler

I booted the system again and this time it dropped into emergency
mode.
In emergency mode I see the following messages in dmesg:

BTRFS info (device sda2): flagging fs with big metadata feature
BTRFS info (device sda2): disk space caching is enabled
BTRFS info (device sda2): has skinny extents
BTRFS info (device sda2): start tree-log replay
BTRFS info (device sda2): parent transid verify failed on 61849600
wanted 145639 fount 145637
BTRFS info (device sda2): parent transid verify failed on 61849600
wanted 145639 fount 145637
BTRFS: error (device sda2) in btrfs_replay_log:2423 errno=-5 IO
failure
(Failed to recover log tree)
BTRFS error (device sda2) open_ctree failed

I ran btrfs check in emergency mode and it came up with a lot of
errors.

How do i recover the partition(s) so I can boot the system, or at
least
mount them?


The underlying problem could be the physical disk that holds the VM's
virtual disk file, or a corrupt btrfs.   Avoid doing anything that 
would write to the
virtual disk.  Make a backup copy of the virtual disk. If the physical 
drive

is OK, use a separate VM to mount the Fedora 34 virtual disk for repair
attempts.

Try: https://btrfs.wiki.kernel.org/index.php/FAQ
How do I recover from a  parent transid verify failed error?

At one time VirtualBox had issues with btrfs.  You should check for 
similar

reports for VMWare and btrfs.

--
George N. White III


___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-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
Do not reply to spam on the list, report 
it:https://pagure.io/fedora-infrastructure
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

maybe OT

[Paolo Galtieri]

I'm having issues with a VM.

The VM was originally created under VMware and has worked fine for a 
while.  Today when I booted it up instead of seeing the usual MATE login 
screen I get a login prompt:


f34-01-vm:

no matter what I enter, root or pgaltieri as login it never asks for 
password and immediately says login incorrect.  While it's booting I see 
several [FAILED]... messages, e.g. [FAILED] to start CUPS Scheduler


I booted the system again and this time it dropped into emergency mode.  
In emergency mode I see the following messages in dmesg:


BTRFS info (device sda2): flagging fs with big metadata feature
BTRFS info (device sda2): disk space caching is enabled
BTRFS info (device sda2): has skinny extents
BTRFS info (device sda2): start tree-log replay
BTRFS info (device sda2): parent transid verify failed on 61849600 
wanted 145639 fount 145637
BTRFS info (device sda2): parent transid verify failed on 61849600 
wanted 145639 fount 145637
BTRFS: error (device sda2) in btrfs_replay_log:2423 errno=-5 IO failure 
(Failed to recover log tree)

BTRFS error (device sda2) open_ctree failed

I ran btrfs check in emergency mode and it came up with a lot of errors.

How do i recover the partition(s) so I can boot the system, or at least 
mount them?


Also in emergency mode:

vi /run/initramfs/rdsosreport.txt

results in:

/usr/bin/vi: line 23: /usr/libexec/vi: No such file or directory

/usr/bin/vi is a script:

if test -f /usr/bin/vim
then
    exec /usr/bin/vim "$@"
fi

exec /usr/libexec/vi "$@"

neither /usr/bin/vim nor /usr/libexec/vi exist.

==

I tried booting the vm under VirtualBox with the same result.

I converted the image:

qemu-img convert -O qcow ../VMware/VMs/f34-01-vm/f34-01-vm.vmdk 
f34-01-vm.qcow2


which worked without errors.  I then ran virt-manager to try to boot the 
image.  This fails with this error


Unable to complete install: 'internal error: process exited while 
connecting to monitor: 2022-03-18T19:13:15.196710Z qemu-system-x86_64: 
-blockdev 
{"driver":"file","filename":"/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: 
Could not open 
'/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2': 
Permission denied'


Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in 
cb_wrapper

    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/createvm.py", line 2001, in 
_do_async_install

    installer.start_install(guest, meter=meter)
  File "/usr/share/virt-manager/virtinst/install/installer.py", line 
701, in start_install

    domain = self._create_guest(
  File "/usr/share/virt-manager/virtinst/install/installer.py", line 
649, in _create_guest

    domain = self.conn.createXML(install_xml or final_xml, 0)
  File "/usr/lib64/python3.9/site-packages/libvirt.py", line 4366, in 
createXML

    raise libvirtError('virDomainCreateXML() failed')
libvirt.libvirtError: internal error: process exited while connecting to 
monitor: 2022-03-18T19:13:15.196710Z qemu-system-x86_64: -blockdev 
{"driver":"file","filename":"/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: 
Could not open 
'/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2': 
Permission denied



I added my user id to both the qemu and libvirt entries in /etc/group 
and logged out and logged back in and I get the same error.  I also get 
SELinux alerts:


The first alert:

You need to change the label on f34-01-vm.qcow2'
# semanage fcontext -a -t virt_image_t 
'/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2'
# restorecon -v 
'/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2'


subsequent alerts tell me to run:

# /sbin/restorecon -v 
/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2


I have run these commands, especially the restorecon, several times and 
I still get the alerts.


One thing the semanage command as shown fails with:

ValueError: File spec 
/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2 
conflicts with equivalency rule '/run /var/run'; Try adding 
'/var/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/KVM/f34-01-vm.qcow2' 
instead


If I add the /var then it works.

here is the context of the file:

-rwxrwxrwx. 1 pgaltieri pgaltieri system_u:object_r:fusefs_t:s0 
15041695744 Mar 18 11:46 f34-01-vm.qcow2*


So how the heck do I boot the image and get it running?


Paolo
___
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: http

Re: suspend on lid closed doesn't work

[Paolo Galtieri]

In my case there is an external mouse and keyboard.  It's the presence 
of the external monitor that causes the problem.  All my systems share 
keyboard and mouse via kvm switch.  One system shares the monitor via 
the kvm switch (it's VGA) while the laptop in question is directly 
connected to the laptop via HDMI cable.


Paolo

On 3/17/22 11:48, Barry wrote:



On 17 Mar 2022, at 15:27, Paolo Galtieri  wrote:

Folks,
   I have 2 laptops, one running F31 the other F34.  When I close the lid on 
the F31 system it suspends as it is supposed to.  I can ping the system and I 
get no response.  On the F34 system I close the lid and the system continues 
running.  I can still login to the system from the external monitor.  The power 
management configuration says suspend on lid closed on both systems.  I 
discovered that the reason it doesn't suspend on the F34 system is the external 
monitor.  My systems share an external monitor via a kvm switch.  Depending on 
which system the external monitor is connected to that system will not suspend 
on lid closure.  I verified the same thing happens with the F31 system.  There 
is nothing in the power management configuration that says anything about an 
external devices.

My guess is that the lid closed is ignored because you can “obviously”
use the system on the external display. Is there and external keyboard or
Mouse connected as well?

MacOS allows the system to run with the lid closed only if,
power, keyboard and screen and connected. I wonder if the DE is doing the same?

Barry


Is there any way to actually suspend a laptop when the lid is closed regardless 
of any external devices?

One thing I should mention is that the external monitor is directly connected 
to the F34 system via an HDMI cable, it's only the keyboard and mouse that go 
through the kvm switch. If I directly connect the monitor to the F31 system, 
also via HDMI, then it also fails to suspend on lid closure.

Any help is appreciated.

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: suspend on lid closed doesn't work

[Paolo Galtieri]

I guess this bug also applies to MATE, because I don't run Gnome.  I 
wonder how many other desktops this problem applies to.


Paolo

On 3/17/22 15:43, Samuel Sieb wrote:

On 3/17/22 08:27, Paolo Galtieri wrote:
Is there any way to actually suspend a laptop when the lid is closed 
regardless of any external devices?


https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/111
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

suspend on lid closed doesn't work

[Paolo Galtieri]

Folks,
  I have 2 laptops, one running F31 the other F34.  When I close the 
lid on the F31 system it suspends as it is supposed to.  I can ping the 
system and I get no response.  On the F34 system I close the lid and the 
system continues running.  I can still login to the system from the 
external monitor.  The power management configuration says suspend on 
lid closed on both systems.  I discovered that the reason it doesn't 
suspend on the F34 system is the external monitor.  My systems share an 
external monitor via a kvm switch.  Depending on which system the 
external monitor is connected to that system will not suspend on lid 
closure.  I verified the same thing happens with the F31 system.  There 
is nothing in the power management configuration that says anything 
about an external devices.


Is there any way to actually suspend a laptop when the lid is closed 
regardless of any external devices?


One thing I should mention is that the external monitor is directly 
connected to the F34 system via an HDMI cable, it's only the keyboard 
and mouse that go through the kvm switch. If I directly connect the 
monitor to the F31 system, also via HDMI, then it also fails to suspend 
on lid closure.


Any help is appreciated.

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: dns lookup behavior

[Paolo Galtieri]

On 2/21/22 15:56, Jamie Fargen wrote:




dig 172.16.96.20


Do you mean dig -x 172.16.96.20


dig 1.1.1.1 doesn't return the host name:




dig -x 172.16.96.20

returns

; <<>> DiG 9.16.24-RH <<>> -x 172.16.96.20
;; global options: +cmd
;; connection timed out; no servers could be reached

but

dig centos8-opstcore-vm.homenet172-16-96.com

returns

; <<>> DiG 9.16.24-RH <<>> centos8-opstcore-vm.homenet172-16-96.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31140
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;centos8-opstcore-vm.homenet172-16-96.com. IN A

;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16-96.com. 259200 IN A 172.16.96.20

;; Query time: 2 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Feb 22 16:04:46 PST 2022
;; MSG SIZE  rcvd: 85

Paolo

You can see running dig followed by an IP doesn't return anything, to 
do a reverse DNS lookup, or to resolve the hostname from the IP, you 
can see in the second example dig -x followed by the IP returns the 
hostname one.one.one.one.


$ dig 1.1.1.1

; <<>> DiG 9.16.24-RH <<>> 1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42214
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.1.1.1. IN A

;; AUTHORITY SECTION:
. 60 IN SOA a.root-servers.net . 
nstld.verisign-grs.com . 2022022101 
1800 900 604800 86400


;; Query time: 241 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 18:53:50 EST 2022
;; MSG SIZE  rcvd: 111


# dig -x 1.1.1.1

; <<>> DiG 9.16.24-RH <<>> -x 1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63485
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.1.1.1.in-addr.arpa. IN PTR

;; ANSWER SECTION:
1.1.1.1.in-addr.arpa. 1131 IN PTR one.one.one.one.

;; Query time: 74 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 18:53:57 EST 2022
;; MSG SIZE  rcvd: 78


; <<>> DiG 9.16.24-RH <<>> 172.16.96.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47273
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;172.16.96.20.            IN    A

;; AUTHORITY SECTION:
.            6751    IN    SOA a.root-servers.net
. nstld.verisign-grs.com
. 2022022101 1800 900 604800 86400

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 14:39:02 PST 2022
;; MSG SIZE  rcvd: 116

dig centos8-opstcore-vm.homenet172-16-96.com


; <<>> DiG 9.16.24-RH <<>>
centos8-opstcore-vm.homenet172-16-96.com

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26457
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;centos8-opstcore-vm.homenet172-16-96.com
. IN A

;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16-96.com
. 4778 IN A
172.16.96.20

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 14:40:16 PST 2022
;; MSG SIZE  rcvd: 85

I tried stopping and restarting systemd-resolved to no avail as
well as restarting the network interface also to no avail.

What's curious is for example

host 192.168.10.2 will return a host name most likely because it's
cached.

host 172.16.96.20 results in host not found on one F34 system and
no servers could be reached on the other F34 system

I ran wireshark on the DNS server and it showed the query to
127.0.0.53 with the hostname and a response of the ip address. 
But a query to 127.0.0.53 with the ip address returned a not found
error.


At first I didn't like this new way to manage DNS, but I am
finding some of the features to work very well. Like the split
dns feature is working really well with the multiple vpn clients
run simultaneously, no more hacking on /etc/resolv.conf each time
a new VPN is started, it just works.


1 - https://fedoraproject.org/wiki/Changes/systemd-resolved

 Regards,
-Jamie

___
users mailing

Re: dns lookup behavior

[Paolo Galtieri]

On 2/21/22 14:09, Jamie Fargen wrote:



On Mon, Feb 21, 2022 at 4:52 PM Barry  wrote:



> On 21 Feb 2022, at 20:15, Paolo Galtieri 
wrote:
>
> Folks,
>  I have 3 Linux systems, one running F31 and 2 running F34.  On
one of the F34 systems I have a local DNS server running.  This
has worked fine in the past, but now I'm seeing strangeness on the
2 F34 systems.
>
> I added a host to the DNS server for normal lookup and reverse
lookup.  On the F31 system both:
>
> host centos8-opstcore-vm.homenet172-16-96.com
<http://centos8-opstcore-vm.homenet172-16-96.com>
>
> and
>
> host 172.16.96.20
>
> work. The first returns 172.16.96.20 and the second returns
centos8-opstcore-vm.homenet172-16-96.com
<http://centos8-opstcore-vm.homenet172-16-96.com>.
>
> On the F34 which is the DNS server the first works, but the
second fails with:
>
> Host 20.96.16.172.in-addr.arpa. not found: 3(NXDOMAIN)
>
> On the other F34 system I get:
>
> host 172.16.96.20
>
> ;; connection timed out; no servers could be reached
>
> The interface has the DNS server pointing to the correct system.
If I run:
>
> nslookup
> > server 192.168.10.66
> Default server: 192.168.10.66
> Address: 192.168.10.66#53
> > 172.16.96.20
> 20.96.16.172.in-addr.arpa    name =
centos8-opstcore-vm.homenet172-16-96.com
<http://centos8-opstcore-vm.homenet172-16-96.com>.
> >

Nslookup has been replaced by the dig program.

Barry

>
> Then it works.
>
> What do I need to do on F34 systems to get DNS lookups working?

Might you be using systemd-resolved on the f34 to cache for you?
What does resolvectl report?



Yes I am


Barry


On the DNS server resolvectl shows:

resolvectl
Global
   Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (eno1)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
 Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS 
DNSSEC=no/unsupported

Current DNS Server: 192.168.10.66
   DNS Servers: 192.168.10.66 8.8.8.8
    DNS Domain: homenet172-16-96.com homenet172-22-6.com 
homenet192-10.com


On the other F34 system

resolvecttl
Global
   Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp0s20f0u1u1u1)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
 Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS 
DNSSEC=no/unsupported


Link 3 (enp0s20f0u1u1u4)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
 Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS 
DNSSEC=no/unsupported

Current DNS Server: 192.168.10.66
   DNS Servers: 192.168.10.66
    DNS Domain: homenet172-16-96.com homenet172-22-6.com 
homenet192-10.com


In all cases it points to the correct DNS server


>
> Any help is appreciated.
>
> Paolo
>



In Fedora 33 DNS resolution was changed (1)adding a DNS server to 
/etc/resolv.conf using systemd-resolve.


There is still an /etc/resolv.conf and it is configured to use a name 
service running on a loopback device where a local DNS service is 
listening.


# grep -v '#' /etc/resolv.conf

nameserver 127.0.0.53
options edns0 trust-ad
search domain.com <http://domain.com>


If you are using the NetworkManager service just add the DNS server 
address and it should start working.


The entry for the network device includes the DNS server address



Something like this "nmcli con mod $connectionName ipv4.dns "1.1.1.1 
9.9.9.9".



I tried this, but reverse lookup still doesn't work.

dig 172.16.96.20

; <<>> DiG 9.16.24-RH <<>> 172.16.96.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47273
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;172.16.96.20.            IN    A

;; AUTHORITY SECTION:
.            6751    IN    SOA    a.root-servers.net. 
nstld.verisign-grs.com. 2022022101 1800 900 604800 86400


;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Feb 21 14:39:02 PST 2022
;; MSG SIZE  rcvd: 116

dig centos8-opstcore-vm.homenet172-16-96.com

; <<>> DiG 9.16.24-RH <<>> centos8-opstcore-vm.homenet172-16-96.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26457
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;centos8-opstcore-vm.homenet172-16-96.com. IN A

;; ANSWER SECTION:
centos8-opstcore-vm.homenet172-16

dns lookup behavior

[Paolo Galtieri]

Folks,
 I have 3 Linux systems, one running F31 and 2 running F34.  On one of 
the F34 systems I have a local DNS server running.  This has worked fine 
in the past, but now I'm seeing strangeness on the 2 F34 systems.


I added a host to the DNS server for normal lookup and reverse lookup.  
On the F31 system both:


host centos8-opstcore-vm.homenet172-16-96.com

and

host 172.16.96.20

work. The first returns 172.16.96.20 and the second returns 
centos8-opstcore-vm.homenet172-16-96.com.


On the F34 which is the DNS server the first works, but the second fails 
with:


Host 20.96.16.172.in-addr.arpa. not found: 3(NXDOMAIN)

On the other F34 system I get:

host 172.16.96.20

;; connection timed out; no servers could be reached

The interface has the DNS server pointing to the correct system. If I run:

nslookup
> server 192.168.10.66
Default server: 192.168.10.66
Address: 192.168.10.66#53
> 172.16.96.20
20.96.16.172.in-addr.arpa    name = 
centos8-opstcore-vm.homenet172-16-96.com.

>

Then it works.

What do I need to do on F34 systems to get DNS lookups working?

Any help is appreciated.

Paolo

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

exfat vs fuseblk

[Paolo Galtieri]

I have several external disk drives from the same vendor.  According to 
the vendor recent drives are formatted exfat while prior ones where 
formatted ntfs.  According to what I find on the web file system type 
fuseblk should work for both exfat and nfts. I have a new 12TB drive and 
when I plug it in mate-system-monitor reports it as type exfat not fuseblk.


What determines whether a file system type is reported as exfat, ntfs, 
or fuseblk?


The drive works fine and is accessible from F34, I'm just curious why 
mate-system-monitor does not report it as type fuseblk.


Any help is appreciated.

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: why are / and /home the same filesystem?

[Paolo Galtieri]

The system is x86_64 and I'm using brtfs.  So that clears that up:

findmnt --notruncate /

TARGET SOURCE   FSTYPE OPTIONS
/  /dev/nvme0n1p10[/root00]
    btrfs 
rw,relatime,seclabel,ssd,space_cache,subvolid=276,subvol=/root00


findmnt --notruncate /home

TARGET SOURCE   FSTYPE OPTIONS
/home  /dev/nvme0n1p10[/home]
    btrfs 
rw,relatime,seclabel,ssd,space_cache,subvolid=257,subvol=/home


However, it's still confusing to me having df show that both /home and / 
are filled up when du -s shows that /home is only using 96G.  I found 
the problem by doing du -s /usr/* and saw that /usr/local was consuming 
a lot of space.


du -s /home
96971060    /home

du -s /
5436965761    /

Paolo

On 2/6/22 08:49, francis.montag...@inria.fr wrote:

Hi.

On Sun, 06 Feb 2022 11:42:22 -0500 "Garry T. Williams" wrote:


You probably have / and /home on subvolumes of a btrfs file system.

+1

The clearer way to see that is probably to use:

   findmnt --notruncate /
   findmnt --notruncate /home

Example: see the subvol= option:

findmnt --notruncate /
TARGET SOURCEFSTYPE OPTIONS
/  /dev/mapper/luks-c92191d5-7811-49f9-867c-1e300d1e9410[/root]
  btrfs  
rw,relatime,compress=lzo,ssd,space_cache,subvolid=258,subvol=/root

findmnt --notruncate /home
TARGET SOURCEFSTYPE OPTIONS
/home  /dev/mapper/luks-c92191d5-7811-49f9-867c-1e300d1e9410[/home]
  btrfs  
rw,relatime,compress=lzo,ssd,space_cache,subvolid=257,subvol=/home


That is the current default configuration now.

But it was not in F31 ...


___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

why are / and /home the same filesystem?

[Paolo Galtieri]

Folks,
  today I ran into a strange problem.  Both the root file system and 
the /home filesystem showed 100% usage:


df -l
Filesystem  1K-blocks  Used Available Use% Mounted on
devtmpfs 4096 0  4096   0% /dev
tmpfs    32793004 0  32793004   0% /dev/shm
tmpfs    13117204  2512  13114692   1% /run
/dev/nvme0n1p10 283625472 281920988    735540 100% /
tmpfs    32793008 11612  32781396   1% /tmp
/dev/nvme0n1p10 283625472 281920988    735540 100% /home
/dev/nvme0n1p8 463826    258874    176485  60% /boot
/dev/nvme0n1p7 487160 14280    472880   3% /boot/efi
tmpfs 6558600   196   6558404   1% /run/user/1000
tmpfs 6558600    88   6558512   1% /run/user/0

When I did a du -s of my home directory it showed only 96GB used.

sudo du -s /home/*

96910360    /home/pgaltieri

The problem turned out to be a large file in /usr/local.  When I removed 
this file both / and /home dropped in their usage:


Filesystem   1K-blocks   Used  Available Use% Mounted on
devtmpfs  4096  0   4096   0% /dev
tmpfs 32793004  0   32793004   0% /dev/shm
tmpfs 13117204   2616   13114588   1% /run
*/dev/nvme0n1p10*  283625472  187104116   95417980  67% /
tmpfs 32793008  11860   32781148   1% /tmp
*/dev/nvme0n1p10*  283625472  187104116   95417980  67% /home
/dev/nvme0n1p8  463826 258874 176485  60% /boot
/dev/nvme0n1p7  487160  14280 472880   3% /boot/efi
tmpfs  6558600    204    6558396   1% /run/user/1000

so why are / and /home the same device?  In the past / and /home where 
separate devices.  This is for F31


Filesystem   1K-blocks   Used Available Use% Mounted on
devtmpfs   8121488  0   8121488   0% /dev
tmpfs  8142632  97596   8045036   2% /dev/shm
tmpfs  8142632   2000   8140632   1% /run
*/dev/mapper/fedora-root*   51475068   36099716  12737528 74% /
tmpfs  8142632 171148   7971484   3% /tmp
*/dev/mapper/fedora-home*  645292064  391044160 221445908 64% /home
/dev/sda8   487652 203435    254521  45% /boot
/dev/sda1   507904  61176    446728  13% /boot/efi

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pluma and ISO-8859 text

[Paolo Galtieri]

When I use caja, or any file browser, to read a text file that is 
encoded in ISO-8859 it uses pluma to read the file.  Pluma, however, 
fails with this message:


pluma has not been able to detect the character encoding.
Please check that you are not trying to open a binary file.
Select a character encoding from the menu and try again.

I need to explicitly choose ISO-8859 from the Character Encoding drop 
down box.


The file program is able to detect that the text file is in ISO-8859 
encoding.


How does pluma determine the character encoding, why is it not able to 
detect the encoding and display the text file contents?


This is on both F34 and F35.

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

graphics support on f34

[Paolo Galtieri]

Folks,
  I recently reported an issue with booting recent kernels.  All 
kernels after 5.14.18 fail with "Input not supported" being displayed on 
the monitor.  Originally it was suggested that it might be the KVM 
switch I use to connect my systems.  Today I removed the switch and 
directly connected the monitor to the system.  I still get the "Input 
not supported" message.  The system is a Dell T440 server and it uses a 
Matrox G200eR2 graphics card with 16 MB capacity.


I have 2 systems running F34 and the problem only occurs on this system.

I really would like to get this working so any help is appreciated.

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: several issues with f34

[Paolo Galtieri]

I have disabled chronyd.  The main problem is the graphical.target vs 
multi-user.target.  ntpd only starts in multi-user.target.


Paolo

On 12/5/21 13:59, Ed Greshko wrote:

On 06/12/2021 01:48, Paolo Galtieri wrote:

systemctl status ntpd
○ ntpd.service - Network Time Service
 Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; 
vendor preset: disabled)

 Active: inactive (dead)
   Docs: man:ntpd(8)


As Tom has already indicated, this is what you'd get if you have both 
ntpd and chronyd enabled.


So, make sure only one time sync service is enabled.

--
Did 황준호 die?
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: several issues with f34

[Paolo Galtieri]

It turned out chronyd was also enabled, but marked as dead.

○ chronyd.service - NTP client/server
 Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; 
vendor preset: enabled)

 Active: inactive (dead) since Sun 2021-12-05 09:47:14 PST; 23h ago
   Docs: man:chronyd(8)
 man:chrony.conf(5)
    Process: 1047 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, 
status=0/SUCCESS)

   Main PID: 1053 (code=exited, status=0/SUCCESS)
    CPU: 42ms

Dec 05 09:37:31 truckin.homenet192-10.com chronyd[1053]: Frequency 
-3.984 +/- 0.061 ppm read from /var/lib/chrony/drift
Dec 05 09:37:31 truckin.homenet192-10.com chronyd[1053]: Using right/UTC 
timezone to obtain leap second data
Dec 05 09:37:31 truckin.homenet192-10.com systemd[1]: Started NTP 
client/server.
Dec 05 09:41:40 truckin.homenet192-10.com chronyd[1053]: Selected source 
213.154.236.182 (2.fedora.pool.ntp.org)
Dec 05 09:41:40 truckin.homenet192-10.com chronyd[1053]: System clock 
TAI offset set to 37 seconds
Dec 05 09:43:52 truckin.homenet192-10.com chronyd[1053]: Selected source 
95.81.173.74 (2.fedora.pool.ntp.org)

Dec 05 09:47:14 truckin.homenet192-10.com chronyd[1053]: chronyd exiting
Dec 05 09:47:14 truckin.homenet192-10.com systemd[1]: Stopping NTP 
client/server...
Dec 05 09:47:14 truckin.homenet192-10.com systemd[1]: chronyd.service: 
Deactivated successfully.
Dec 05 09:47:14 truckin.homenet192-10.com systemd[1]: Stopped NTP 
client/server.


I think the problem is the target.  My default target is listed as 
graphical.target and ntpd (and chronyd) only run in multi-user.target.  
I did not explicitly choose graphical target so I assume it is what was 
configured when I installed the system some time ago.  Are there going 
to be any issues changing the target from graphical to multi-user?


Paolo

On 12/5/21 11:27, Tom Horsley wrote:

On Sun, 05 Dec 2021 20:18:13 +0100
francis.montag...@inria.fr wrote:


Sorry: I was comparing with chronyd

Actually that's a good thing to look at. Have you disabled chrony?
If not, they will fight over the NTP port.
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: several issues with f34

[Paolo Galtieri]

Here's the output:

systemctl cat ntpd.service
# /usr/lib/systemd/system/ntpd.service
[Unit]
Description=Network Time Service
Documentation=man:ntpd(8)
Wants=network.target
ConditionCapability=CAP_SYS_TIME
After=network.target nss-lookup.target
Conflicts=systemd-timesyncd.service

[Service]
Type=forking
PrivateTmp=true
ExecStart=/usr/sbin/ntpd -g -N -u ntp:ntp
# Specifying -g on the command line allows ntpd to make large adjustments to
# the clock on boot.  However, if Restart=yes is set, a malicious (or 
broken)

# server could send the incorrect time, trip the panic threshold, and when
# ntpd restarts, serve it the incorrect time (which would be accepted).
Restart=no

[Install]
WantedBy=multi-user.target
[pgaltieri@truckin ~]$ systemctl status systemd-timesyncd.service
○ systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; 
disable>

 Active: inactive (dead)
   Docs: man:systemd-timesyncd.service(8)

systemctl status systemd-timesyncd.service
○ systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; 
disable>

 Active: inactive (dead)
   Docs: man:systemd-timesyncd.service(8)

Paolo

On 12/5/21 11:18, francis.montag...@inria.fr wrote:

systemctl status systemd-timesyncd.service

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: several issues with f34

[Paolo Galtieri]

Here's the output:

[pgaltieri@truckin ~]$ systemctl get-default
graphical.target
[pgaltieri@truckin ~]$ find /etc/systemd/system -name chronyd.service -ls
  4195823  0 lrwxrwxrwx   1 root root   39 Apr 25 2019 
/etc/systemd/system/multi-user.target.wants/chronyd.service -> 
/usr/lib/systemd/system/chronyd.service


find /etc/systemd/system -name ntpd.service -ls
  4196557  0 lrwxrwxrwx   1 root root   36 Sep  4 19:19 
/etc/systemd/system/multi-user.target.wants/ntpd.service -> 
/usr/lib/systemd/system/ntpd.service


Paolo

On 12/5/21 10:55, francis.montag...@inria.fr wrote:

find /etc/systemd/system -name chronyd.service -ls

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: several issues with f34

[Paolo Galtieri]

Here's the info:

systemctl status ntpd
○ ntpd.service - Network Time Service
 Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; 
vendor preset: disabled)

 Active: inactive (dead)
   Docs: man:ntpd(8)

At this point here's the current network config:

ifconfig
eno1: flags=4163  mtu 1500
    inet 192.168.10.66  netmask 255.255.255.0  broadcast 192.168.10.255
    inet6 fe80::4741:dbcc:7824:9f5  prefixlen 64  scopeid 0x20
    ether 4c:d9:8f:6d:87:21  txqueuelen 1000  (Ethernet)
    RX packets 1067  bytes 125274 (122.3 KiB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 725  bytes 95167 (92.9 KiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    device interrupt 17

eno2: flags=4099  mtu 1500
    ether 4c:d9:8f:6d:87:22  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 0  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    device interrupt 18

lo: flags=73  mtu 65536
    inet 127.0.0.1  netmask 255.0.0.0
    inet6 ::1  prefixlen 128  scopeid 0x10
    loop  txqueuelen 1000  (Local Loopback)
    RX packets 503  bytes 40302 (39.3 KiB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 503  bytes 40302 (39.3 KiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099  mtu 1500
    inet 192.168.122.1  netmask 255.255.255.0  broadcast 
192.168.122.255

    ether 52:54:00:ba:c1:00  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 0  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

The wifi interface does not exist, at this point I started ntpd

sudo systemctl start ntpd

● ntpd.service - Network Time Service
 Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; 
vendor preset: disabled)

 Active: active (running) since Sun 2021-12-05 09:09:37 PST; 2s ago
   Docs: man:ntpd(8)
    Process: 3288 ExecStart=/usr/sbin/ntpd -g -N -u ntp:ntp 
(code=exited, status=0/SUCCESS)

   Main PID: 3289 (ntpd)
  Tasks: 2 (limit: 37863)
 Memory: 11.8M
    CPU: 52ms
 CGroup: /system.slice/ntpd.service
 └─3289 /usr/sbin/ntpd -g -N -u ntp:ntp

Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen 
normally on 3 eno1 192.168.10.66:123
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen 
normally on 4 lo [::1]:123
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listen 
normally on 5 eno1 [fe80::4741:dbcc:7824:9>
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: IO: Listening on 
routing socket on fd #22 for interfa>
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: SYNC: Found 5 
servers, suggest minsane at least 3
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: MRU 10922 
entries, 13 hash bits, 65536 bytes
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Built with 
OpenSSL 1.1.1k  FIPS 25 Mar 2021, 10>
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: INIT: Running with 
OpenSSL 1.1.1l  FIPS 24 Aug 2021, >
Dec 05 09:09:37 truckin.homenet192-10.com ntpd[3289]: NTSc: Using system 
default root certificates.
Dec 05 09:09:38 truckin.homenet192-10.com ntpd[3289]: DNS: dns_probe: 
0.pool.ntp.org, cast_flags:1, flags:2>


I went and looked in /var/log/messages to see if there was anything 
there that might indicate the problem.  What I found is that the only 
time I see:


Dec  5 09:09:37 truckin systemd[1]: Starting Network Time Service...

is when I do it manually.

I rebooted the system at 9:37 AM and there is no entry indicating ntpd 
was started after this time.


Paolo

On 12/4/21 09:38, Ed Greshko wrote:

On 05/12/2021 00:27, Paolo Galtieri wrote:
This isn't true.  I stopped ntpd, stopped the wifi connection and 
restarted ntpd and ntpd started fine with no wifi connection.  It 
should only need a network connection to synchronize the time.


That is why I asked you to provide the output of

systemctl status ntpd

before you restart manually.  That way we may see the error causing it 
to fail to start initially.





Paolo

On 12/3/21 10:15, Joe Zeff wrote:

On 12/3/21 11:05 AM, Paolo Galtieri wrote:
Next issue. This same system is configured to start ntpd at boot, 
but it doesn't start.  I need to start it manually after the system 
is booted.


Of course it doesn't.  That service requires a network connection 
and can't start until you've unplugged your wireless adapter and 
plugged it back in.  Fix that and this issue should solve itself.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedo

Re: several issues with f34

[Paolo Galtieri]

This isn't true.  I stopped ntpd, stopped the wifi connection and 
restarted ntpd and ntpd started fine with no wifi connection.  It should 
only need a network connection to synchronize the time.


Paolo

On 12/3/21 10:15, Joe Zeff wrote:

On 12/3/21 11:05 AM, Paolo Galtieri wrote:
Next issue. This same system is configured to start ntpd at boot, but 
it doesn't start.  I need to start it manually after the system is 
booted.


Of course it doesn't.  That service requires a network connection and 
can't start until you've unplugged your wireless adapter and plugged 
it back in.  Fix that and this issue should solve itself.

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: several issues with f34

[Paolo Galtieri]

The "Input not supported" error occurs on the active connection. But 
what has changed recently to introduce this problem since booting on 
older kernels does not exhibit it?


Paolo

On 12/4/21 05:54, Tom Horsley wrote:

On Sat, 4 Dec 2021 15:16:05 +0800
Ed Greshko wrote:


So, you have a common keyboard, and monitor?  I've not used a KVM switch in a 
long time but they sometimes would cause
problems.

A lot of KVM switches don't pass through EDID info correcly (especially
for connections not currently active), there is a kernel option you
can add to the kernel boot line to point at a binary blob of EDID
info that will override whatever incorrect nonsense it is getting from
the KVM. Usually you just want to save the EDID from the real monitor
when it is properly connected, then point the kernel at that so it
will always know the right stuff.
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

several issues with f34

[Paolo Galtieri]

Folks,
  I have 2 systems running F34.  These 2 systems connect to a common 
monitor via a keyboard-video-mouse switch.


First issue. One of these systems, when I boot any of the 3 most recent 
kernels, when it gets to multi user mode displays "Input not supported" 
but works fine when I boot kernel 5.14.18-200.fc34.x86_64. The other 
system boots fine. So what do I need to look at in order to get it to 
display the login screen?



Next issue. This same system connects to the internet via a USB wireless 
adapter.  This adapter never comes up at boot time.  In order to get it 
to work I need to unplug it and plug it back in.


Next issue. This same system is configured to start ntpd at boot, but it 
doesn't start.  I need to start it manually after the system is booted.


Next issue. Here is the output of df

Filesystem   1K-blocks   Used Available 
Use% Mounted on
devtmpfs  16155236  0 16155236   
0% /dev
tmpfs 16175828  70840 16104988   
1% /dev/shm
tmpfs  6470332   1960 6468372   
1% /run
/dev/mapper/fedora_localhost--live-root   71724152   39066764 28970988  
58% /
tmpfs 16175832   5196 16170636   
1% /tmp
/dev/mapper/fedora_localhost--live-home  871075068   77722284 749034884  
10% /home
/dev/sdc1   999320 305456 625052  
33% /boot
tmpfs  3235164    136 3235028   
1% /run/user/1000
/dev/sdb1   1953512032   68907808 
1884604224   4% /run/media/pgaltieri/LOGS
/dev/sda2   3906885628 1275040388 
2631845240  33% /run/media/pgaltieri/TRUCKIN-EX
tmpfs  3235164 88 3235076   
1% /run/user/0


When I run

sudo tune2fs -l /dev/mapper/fedora_localhost--live-root | grep Last\ c

I get

Last checked: Wed Jun  5 06:15:41 2019

when I do touch /forcefsck, reboot and run tune2fs again it still shows 
last checked as 2019.  Here's the fstab


/dev/mapper/fedora_localhost--live-root / ext4    defaults    1 1
UUID=e5521a04-3b65-4ceb-998d-6d4cc0a4d69e /boot ext4    defaults    1 2
/dev/mapper/fedora_localhost--live-home /home ext4    defaults    1 2

What do I need to do to get the system to check my filesystems at boot?

Here is the full output of tune2fs:

tune2fs 1.45.6 (20-Mar-2020)
Filesystem volume name:   
Last mounted on:  /
Filesystem UUID:  1d5272bc-1524-4ddf-a5d8-cf40499a9432
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery extent 64bit flex_bg sparse_super large_file 
huge_file dir_nlink extra_isize metadata_csum

Filesystem flags: signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  4587520
Block count:  18350080
Reserved block count: 917504
Free blocks:  8150468
Free inodes:  3814351
First block:  0
Block size:   4096
Fragment size:    4096
Group descriptor size:    64
Reserved GDT blocks:  1024
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:   Wed Jun  5 06:15:41 2019
Last mount time:  Fri Dec  3 09:15:31 2021
Last write time:  Fri Dec  3 09:15:25 2021
Mount count:  180
Maximum mount count:  -1
Last checked: Wed Jun  5 06:15:41 2019
Check interval:   0 ()
Lifetime writes:  1996 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:      256
Required extra isize: 32
Desired extra isize:  32
Journal inode:    8
First orphan inode:   3410261
Default directory hash:   half_md4
Directory Hash Seed:  d178b832-2df2-4163-8d99-aa806b8838b7
Journal backup:   inode blocks
Checksum type:    crc32c
Checksum: 0x67b77b7d


One thing I should mention is that the system that is having the 
problems started as a Fedora 32 system and has been upgraded to Fedora 
34 using dnf upgrade.


Any help is appreciated.

Paolo
___
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
Do not reply to spam on the list, report it: 
htt

Re: module loading problem

[Paolo Galtieri]

Thank you for the hint.  The problem is that the vbox modules are being 
rebuilt on boot, despite the fact I've already built them. It's 
interesting that when I run /sbin/vboxconfig to rebuild the modules it 
tells me that the modules may need to be signed.  After it builds the 
modules it tries to load them and fails due to the modules not being 
signed.  I don't know why vboxconfig doesn't check to see if the modules 
already exist before trying to build them.


Paolo

On 8/9/21 6:11 AM, stan via users wrote:

On Sun, 8 Aug 2021 09:34:36 -0700
Paolo Galtieri  wrote:


I even tried rebuilding both the virtual box and vmware modules from
source, resigned all the modules and rebooted and again only the
vmware modules are loaded.  The virtual box modules no longer show
they are signed.

Can anybody tell me why the virtual box modules are no longer signed
after rebooting?

Any help is appreciated.

I don't know for sure, but do you have akmod installed?  Is it possible
that the kernel is rebuilding the virtual box modules on boot using
akmod?  Why it wouldn't use the existing modules that you have built, I
don't know.  SELinux contexts incorrect?  This is just a long shot, but
the kernel would never *unsign* modules, so they have to somehow be
replaced. Have you checked the dates on the modules, the signed and
unsigned?
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

module loading problem

[Paolo Galtieri]

Folks,
  I'm having an issue with loading kernel modules after a kernel 
update.  Specifically I'm having an issue with loading virtual box 
kernel modules.  After an update I sign the modules according to the 
information listed here


https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/kernel-module-driver-configuration/Working_with_Kernel_Modules/

After signing the modules and verifying them via

modinfo  | grep "^sig"

I reboot the system.  After booting the system I run lsmod to check if 
the modules have been loaded and they have not.  I go check the modules 
again and I find they are no longer signed.


I resign the modules and rather than rebooting I run insmod to install 
them and this works.


Now I also have vmware installed on the system and I follow the exact 
same procedure to sign the vmware kernel modules and reboot the system 
and when I do an lsmod after rebooting the vmware modules are loaded.


I even tried rebuilding both the virtual box and vmware modules from 
source, resigned all the modules and rebooted and again only the vmware 
modules are loaded.  The virtual box modules no longer show they are signed.


Can anybody tell me why the virtual box modules are no longer signed 
after rebooting?


Any help is appreciated.

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

file associations for OVF files

[Paolo Galtieri]

I recently ran into an issue with files with .ovf extension.  The issue 
is that VMware Workstation will not import files that end in .ovf.  A 
file that ends in .ovf shows up as follows of Fedora 34:


file *.ovf returns

XML 1.0 document, ASCII text

What's interesting is that if you have VirtualBox installed and then try 
to open a .ovf file with VMware workstation it works because according 
to the VirtualBox documentation:


Oracle VM VirtualBox creates file type associations automatically for 
any OVF and OVA files on your host OS.


In fact if I run caja and click my way to the OVF file, right click on 
the file and look at the properties I get:


Type: Open Virtualization Format (application/x-virtualbox-ovf)

If I don't have VirtualBox installed I get

Type: XML document (application/xml)

So who should setup the file association for .ovf files?  How do I go 
about changing the association for .ovf files from XML document to 
something else so that I can associate it with VMware Workstation?


Any help is appreciated.

I have reported this issue to VMware also.

Thanks,
Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

zabbix server/agent on F34

[Paolo Galtieri]

I installed F34 in a VM and installed the zabbix server and agent.  I 
have updated the system to the latest.  When I run the zabbix server and 
agent I get a lot of SELinux alerts.


SELinux is preventing zabbix_agentd from getattr access on the fifo_file 
/run/initctl

  Source Context system_u:system_r:zabbix_agent_t:s0
  Target Context    system_u:object_r:initctl_t:s0
  Target Objects    /run/initctl [ fifo_file ]
  Source    zabbix_agentd
  Source Path   zabbix_agentd

SELinux is preventing zabbix_agentd from getattr access on the sock_file 
/run/systemd/journal/dev-log.

  Source Context system_u:system_r:zabbix_agent_t:s0
  Target Context    system_u:object_r:devlog_t:s0
  Target Objects    /run/systemd/journal/dev-log [ sock_file ]
  Source    zabbix_agentd
  Source Path   zabbix_agentd

SELinux is preventing zabbix_agentd from getattr access on the file 
/proc/kcore

  Source Context system_u:system_r:zabbix_agent_t:s0
  Target Context    system_u:object_r:proc_kcore_t:s0
  Target Objects    /proc/kcore [ file ]
  Source    zabbix_agentd
  Source Path   zabbix_agentd

SELinux is preventing sh from execute_no_trans access on the file 
/usr/bin/rpm

  Source Context system_u:system_r:zabbix_agent_t:s0
  Target Context    system_u:object_r:rpm_exec_t:s0
  Target Objects    /usr/bin/rpm [ file ]
  Source    sh
  Source Path   sh

Here are the installed packages

zabbix.x86_64 1:5.0.10-1.fc34 @updates
zabbix-agent.x86_64 1:5.0.10-1.fc34 @updates
zabbix-dbfiles-mysql.noarch 1:5.0.10-1.fc34 @updates
zabbix-selinux.noarch 1:5.0.10-1.fc34 @updates
zabbix-server.noarch 1:5.0.10-1.fc34 @updates
zabbix-server-mysql.x86_64 1:5.0.10-1.fc34 @updates
zabbix-web.noarch 1:5.0.10-1.fc34 @updates
zabbix-web-mysql.noarch 1:5.0.10-1.fc34 @updates
selinux-policy-targeted.noarch 34.3-1.fc34 @updates
selinux-policy.noarch 34.3-1.fc34 @updates

So is this a bug in the zabbix-selinux package or the zabbix_agentd 
package?


Any help is appreciated.

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

can't upgrade from fedora 31 to Fedora 32

[Paolo Galtieri]

Folks,
  I was trying to upgrade my Fedora 31 system to F32, but it failed due 
to conflicts.  Here's the output:


sudo dnf system-upgrade download --skip-broken --refresh --releasever=32
Before you continue ensure that your system is fully upgraded by running 
"dnf --refresh upgrade". Do you want to continue [y/N]: y

Adobe Systems Incorporated   27 kB/s | 2.9 kB 00:00
Fedora Modular 32 - x86_64   60 kB/s |  14 kB 00:00
negativo17 - Nvidia 4.9 kB/s | 3.9 kB 00:00
Fedora Modular 32 - x86_64 - Updates 30 kB/s | 8.1 kB 00:00
Fedora 32 - x86_64 - Updates 34 kB/s | 9.9 kB 00:00
Fedora 32 - x86_64 - Updates    841 kB/s | 3.3 MB 00:03
Fedora 32 - x86_64   35 kB/s |  14 kB 00:00
google-chrome    12 kB/s | 1.3 kB 00:00
google-earth-pro 28 kB/s | 1.3 kB 00:00
google-earth 29 kB/s | 1.3 kB 00:00
RPM Fusion for Fedora 32 - Free - Updates    13 kB/s | 3.4 kB 00:00
RPM Fusion for Fedora 32 - Free 5.8 kB/s | 3.0 kB 00:00
RPM Fusion for Fedora 32 - Nonfree - Updates 12 kB/s | 3.0 kB 00:00
RPM Fusion for Fedora 32 - Nonfree  4.6 kB/s | 2.6 kB 00:00
skype (stable)  3.9 kB/s | 2.9 kB 00:00
Fedora 32 - x86_64 - VirtualBox  62 kB/s | 2.9 kB 00:00
Visual Studio Code   24 kB/s | 3.0 kB 00:00
Modular dependency problem:

 Problem: conflicting requests
  - nothing provides module(platform:f31) needed by module 
gimp:2.10:3120191106095052:f636be4b-0.x86_64

Error:
 Problem 1: package erlang-libguestfs-1:1.40.2-8.fc31.x86_64 requires 
libguestfs(x86-64) = 1:1.40.2-8.fc31, but none of the providers can be 
installed
  - libguestfs-1:1.40.2-8.fc31.x86_64 does not belong to a distupgrade 
repository

  - problem with installed package erlang-libguestfs-1:1.40.2-8.fc31.x86_64
 Problem 2: package php-recode-7.3.24-1.fc31.x86_64 requires 
php-common(x86-64) = 7.3.24-1.fc31, but none of the providers can be 
installed
  - php-common-7.3.24-1.fc31.x86_64 does not belong to a distupgrade 
repository

  - problem with installed package php-recode-7.3.24-1.fc31.x86_64
 Problem 3: package pyorbit-devel-2.24.0-29.fc31.x86_64 requires 
pyorbit = 2.24.0-29.fc31, but none of the providers can be installed
  - pyorbit-2.24.0-29.fc31.x86_64 does not belong to a distupgrade 
repository

  - problem with installed package pyorbit-devel-2.24.0-29.fc31.x86_64

Note that packages erlang-libguestfs, php-recode, and pyorbit-devel do 
not exist in F32.


So how do I go about upgrading to F32?

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: can't find wireless

[Paolo Galtieri]

Folks,
  I finally found the resolution to F33 not finding my wireless. I 
found it on an Ubuntu list


https://askubuntu.com/questions/1083369/ubuntu-18-04-cannot-recognized-intel-wireless-ac-9260

In short the issue is with Windows 10.  Under the setup for what the 
power buttons do it has the "Turn on fast startup" feature enabled.  If 
you disable this and reboot the wireless works.


Paolo

On 2/19/21 2:36 PM, George N. White III wrote:

lspic -k

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: can't find wireless

[Paolo Galtieri]

On 2/19/21 10:38 AM, Roger Heflin wrote:

Do an ethtool -i

ethtool -i enp0s20f0u1u4

driver: r8152
version: v1.11.11
firmware-version: rtl8153a-4 v2 02/07/20
expansion-rom-version:
bus-info: usb-:00:14.0-1.4
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: can't find wireless

[Paolo Galtieri]

Here's the info

ip link show
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s20f0u1u4:  mtu 1500 qdisc 
fq_codel state UP mode DEFAULT group default qlen 1000

    link/ether 00:e0:4c:68:0b:68 brd ff:ff:ff:ff:ff:ff
3: vmnet1:  mtu 1500 qdisc fq_codel 
state UNKNOWN mode DEFAULT group default qlen 1000

    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
4: vmnet8:  mtu 1500 qdisc fq_codel 
state UNKNOWN mode DEFAULT group default qlen 1000

    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
5: virbr0:  mtu 1500 qdisc noqueue 
state DOWN mode DEFAULT group default qlen 1000

    link/ether 52:54:00:d9:35:63 brd ff:ff:ff:ff:ff:ff
6: virbr0-nic:  mtu 1500 qdisc fq_codel master 
virbr0 state DOWN mode DEFAULT group default qlen 1000

    link/ether 52:54:00:d9:35:63 brd ff:ff:ff:ff:ff:ff

No wireless device listed

iw list

shows nothing

rfkill
ID TYPE  DEVICE  SOFT  HARD
 0 bluetooth hci0   unblocked unblocked

I know wireless works because I can boot the laptop to Windows 10 and it 
sees the available wireless networks.


On another note the Ethernet device keeps changing name is there any way 
to stop this?


Here's what it's been named so far:

enp0s20f0u1u4
enp0s20f0u5u3
enp0s20f0u1u1
enp0s20f0u3
enp55s0u2u3

The current name is enp0s20f0u1u4.  Every time it changes name I have to 
go fix up the DNS info.


Paolo

On 2/18/21 7:33 AM, Jonathan Billings wrote:

On Wed, Feb 17, 2021 at 02:54:19PM -0800, Paolo Galtieri wrote:

So the appropriate wireless driver is loaded, however ifconfig shows the
following devices:

Instead of using the 'ifconfig' tool, try running 'ip link show'.
Perhaps the interface is just down.  Also, many Dells have a
keypress/switch to disable the wifi device, make sure it hasn't been
disabled.

(In fact, stop using ifconfig entirely on Linux, ip is a much better
tool to use these days.)


___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

can't find wireless

[Paolo Galtieri]

I have a Dell XPS 15 9500 laptop.  I've already listed other issues with 
this laptop running Fedora 33. Here's a new one :(


lspic -k shows the following:

0:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
    Subsystem: Rivet Networks Device 1651
    Kernel modules: iwlwifi

lsmod shows the following:

lsmod | grep iwl
iwlwifi   344064  0
cfg80211  954368  1 iwlwifi

So the appropriate wireless driver is loaded, however ifconfig shows the 
following devices:


enp0s20f0u1u4: flags=4163 mtu 1500
    inet 192.168.10.2  netmask 255.255.255.0  broadcast 192.168.10.255
    inet6 fe80::7484:4652:d8fb:2914  prefixlen 64  scopeid 0x20
    ether 00:e0:4c:68:0b:68  txqueuelen 1000  (Ethernet)
    RX packets 22169  bytes 20677661 (19.7 MiB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 20374  bytes 7329505 (6.9 MiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
    inet 127.0.0.1  netmask 255.0.0.0
    inet6 ::1  prefixlen 128  scopeid 0x10
    loop  txqueuelen 1000  (Local Loopback)
    RX packets 25  bytes 3400 (3.3 KiB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 25  bytes 3400 (3.3 KiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099  mtu 1500
    inet 192.168.122.1  netmask 255.255.255.0  broadcast 
192.168.122.255

    ether 52:54:00:d9:35:63  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 0  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmnet1: flags=4163  mtu 1500
    inet 192.168.203.1  netmask 255.255.255.0  broadcast 
192.168.203.255

    inet6 fe80::250:56ff:fec0:1  prefixlen 64  scopeid 0x20
    ether 00:50:56:c0:00:01  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 142  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmnet8: flags=4163  mtu 1500
    inet 172.16.96.1  netmask 255.255.255.0  broadcast 172.16.96.255
    inet6 fe80::250:56ff:fec0:8  prefixlen 64  scopeid 0x20
    ether 00:50:56:c0:00:08  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 142  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Note there is no wireless device listed.

So what do I need to do to get wireless working on this laptop under Fedora?

Paolo
___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 33 and HDMI KVM switch

[Paolo Galtieri]

What's interesting is when I plug the USB to HDMI dongle into my Fedora 
32 system a window pops up that allows me to install a driver for the 
dongle.  There are two options, one for the MAC and one for Windows.  
The Windows driver is dated 2017 the MAC driver is dated Jan 7 2020.  So 
a driver must exist for the dongle.  The dongle is a RayCue USB to HDMI.


Paolo

On 2/8/21 8:58 AM, D. Hugh Redelmeier wrote:

| From: Samuel Sieb 

| On 2/6/21 5:44 PM, Paolo Galtieri wrote:
| >  I'm having an issue running Fedora 33 and an external monitor connected to
| > an HDMI KVM switch.  Here is the way it's connected:
| >
| > Laptop thunderbolt 3 connector -> 4 port USB c to USB 3.0 hub -> USB to HDMI
| > adapter -> HDMI KVM switch.
|
| I don't think there are any USB3 video adapters that work with Linux.

The standards are quite confusing.

Among the USB standards, apparently USB4 (note the lack of space in the
name) is the first to (optionally) support HDMI.
<https://en.wikipedia.org/wiki/USB>

On the other hand, a USB-c connector can support a whole bunch of
standards, only some of which are USB (!!!).
<https://en.wikipedia.org/wiki/USB-C>

So: there is no way your setup would work.

You need to use a use a dongle to connect to your laptop port and output
HDMI.  Many of those dongles also break out USB 3 and ethernet.

I have a ThinkCentre Tiny that came with a USB-c to HDMI dongle.  It
works under Fedora 33 to drive an UltraHD TV.  I am having a problem with
the video, but surely it is unrelated to the dongle:
   <https://bugzilla.redhat.com/show_bug.cgi?id=1925815>

___
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

Fedora 33 and HDMI KVM switch

[Paolo Galtieri]

Folks,
 I'm having an issue running Fedora 33 and an external monitor 
connected to an HDMI KVM switch.  Here is the way it's connected:


Laptop thunderbolt 3 connector -> 4 port USB c to USB 3.0 hub -> USB to 
HDMI adapter -> HDMI KVM switch.


The mouse and keyboard work, however Fedora 33 does not detect the 
external monitor.


Even if I take the KVM switch out of the equation Fedora 33 still does 
not find the external monitor.


This laptop also boots to Windows 10 and everything works fine there.

I have an older laptop running Fedora 31 connected as follows:

laptop HDMI port -> HDMI KVM switch.

This works fine.

Any help is appreciated.

The KVM switch is a 4 port AV Access HDMI 2.0 KVM Switch

Paolo
___
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: Key was rejected by service

[Paolo Galtieri]

Jorge,
  thank you for the information, however, since there is a good reason 
to have secure boot enabled and since Fedora 33 boots with it enabled I 
would like to find a solution that does not require this.  Additionally 
this system boots to Windows so I really don't want to mess around with 
issues booting Windows.


Paolo

On 2/3/21 10:36 AM, Jorge Fábregas wrote:

On 2/3/21 2:33 PM, Paolo Galtieri wrote:

vmmon: Loading of unsigned module is rejected

This looks like you're booting off UEFI in "secure mode" where kernel
and its modules need to be signed.  Try disabling "secure mode" in the
machine's firmware setup.

HTH,
Jorge
___
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

Key was rejected by service

[Paolo Galtieri]

Folks,
 I have installed vmware on Fedora 33.  It does not start due to the 
following error:


modprobe vmmon

modprobe: ERROR: could not insert 'vmmon': Key was rejected by service

modprobe vmnet

modprobe: ERROR: could not insert 'vmnet': Key was rejected by service

dmesg shows

vmmon: Loading of unsigned module is rejected

The modules have been compiled from source.  How do I get around this 
issue so I can run vmware?


Any help is appreciated.

Paolo

___
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

why no glade module for python 3?

[Paolo Galtieri]

Folks,
  for years I've been using sbackup for doing my backups.  I've tried 
others and none come close to being as easy to use as sbackup.  
Unfortunately there doesn't seem to be any further development occurring 
on it. It was written originally to work with python2 and I have managed 
to get it to work with python2 on FC31 and FC32.  However, with the 
removal of most of the necessary python2 packages from FC33 it no longer 
works.  So I tried to get it to run under python3, and the first problem 
I encountered is the following:


Traceback (most recent call last):
  File "/usr/sbin/simple-backup-config", line 30, in 
    import gtk.glade
ImportError: No module named glade

With python2 this module was located in

/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/glade.so

from package

pygtk2-libglade-2.24.0-27.fc31.x86_64

This package does not exist in FC33 nor is there a corresponding package 
for FC33.  So why is there no glade.so module/package for python2 or 
python3?


Since there is no pygtk2-libglade in FC33 I tried to port it, but it 
fails if using with both python2 and python3 due to various errors, e.g. 
the following when using python3


  File "/usr/share/pygobject/2.0/codegen/codegen.py", line 429
    except argtypes.ArgTypeError, ex:
    ^
SyntaxError: invalid syntax
make: *** [Makefile:1151: pango.c] Error 1


I don't want to try to port all the f31 python2 packages which are 
needed, I tried and it's a pain :(


Any help is appreciated.

Paolo
___
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: Windows 10 + F33 + SSD + RAID

[Paolo Galtieri]

Folks,
  I tried the process described in the article and it worked for me.  I 
can now boot up into Windows and Linux without issues.


Thank you very much for the pointer.

Paolo

On 1/29/21 7:44 PM, Greg Woods wrote:



On Fri, Jan 29, 2021 at 6:25 PM Kevin Becker > wrote:


I had the same issue and this article worked for me.


https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci




Dell seems to be the "culprit". I have a Dell desktop where I had 
almost the same problem, except it was only with the NVME drive. If 
the BIOS was set to RAID mode, Windows boots and runs normally. Linux 
will also boot and run, since it is installed on a separate non-NVME 
drive, but it can't see the Windows partitions, which unfortunately 
includes /boot/efi. So I can't do any kernel updates (and who knows 
what else) unless I manually set the SATA mode to AHCI in the BIOS, in 
which case Linux will boot and see all the drives, but Windows will 
not boot. This has led to the very annoying position of having to 
fiddle with the BIOS every time I want to switch OS's. I'll try the 
process in that article. Thanks for the pointer!


Now if I can only figure out why this damn machine won't resume from 
hibernation properly. Windows can do it, so I'll bet it's a 
configuration issue somewhere.


--Greg

___
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

Windows 10 + F33 + SSD + RAID

[Paolo Galtieri]

Folks,
  I have a new dell laptop.  I tried to install Fedora 33 on it, but it 
failed to find any disks.  I searched the internet and discovered that 
if my BIOS has RAID enabled F33 is unable to find any drives.  I 
disabled RAID and enable AHCI and was then able to install and boot 
F33.  I then tried to boot Windows 10.  This failed until I entered the 
bitlock key.  I then went back into the BIOS and re-enabled RAID and 
verified Windows 10 boots without error, but Fedora 33 no longer does 
since it can't find any drives.  What if I want RAID enabled?  Is there 
a solution to this problem?


Paolo
___
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: (root) FAILED (loading cron table)

[Paolo Galtieri]

Yes that looks like the same problem.  I did an update yesterday and 
there was no selinux update, but there was one today.  This fixed my 
problem.


Paolo

On 10/1/20 12:56 PM, Jonathan Billings wrote:

On Thu, Oct 01, 2020 at 11:53:00AM -0700, Paolo Galtieri wrote:

Folks,
since August 13 my backups have failed to run due the following errors:

Oct  1 11:10:01 terrapin CROND[110219]: (root) CMD
(/usr/local/bro/bin/zeekctl cron)
Oct  1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context
(/etc/crontab)
Oct  1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)
Oct  1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context
(/etc/cron.d/0hourly)
Oct  1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)
Oct  1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context
(/etc/cron.d/sbackup)
Oct  1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)

Is your issue related to this BZ?

https://bugzilla.redhat.com/show_bug.cgi?id=1862823

If so, it appears there's an issue with the selinux policy on your
system.


___
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

(root) FAILED (loading cron table)

[Paolo Galtieri]

Folks,
since August 13 my backups have failed to run due the following errors:

Oct  1 11:10:01 terrapin CROND[110219]: (root) CMD 
(/usr/local/bro/bin/zeekctl cron)
Oct  1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security 
context (/etc/crontab)

Oct  1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)
Oct  1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security 
context (/etc/cron.d/0hourly)

Oct  1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)
Oct  1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security 
context (/etc/cron.d/sbackup)

Oct  1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)

ls -lZ /etc/cron.d/sbackup
-rw-r--r--. 1 root root unconfined_u:object_r:system_cron_spool_t:s0 76 
Oct  1 11:11 /etc/cron.d/sbackup


ls -lZ /etc/cron.d/0hourly
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 128 Jul 
24  2019 /etc/cron.d/0hourly


ls -lZ /etc/crontab
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 451 Jul 
24  2019 /etc/crontab


ls -lZ /usr/sbin/sbackupd
-rwxr-xr-x. 1 root root system_u:object_r:usr_t:s0 21024 Apr 29 08:53 
/usr/sbin/sbackupd*


I ran:

sudo sesearch -A -s unconfined_t -t user_cron_spool_t -c file

allow application_domain_type user_cron_spool_t:file { append getattr 
ioctl lock read write };
allow crontab_domain user_cron_spool_t:file { append create getattr 
ioctl link lock open read rename setattr unlink write };

allow domain file_type:file map; [ domain_can_mmap_files ]:True
allow files_unconfined_type file_type:file execmod; [ 
selinuxuser_execmod ]:True
allow files_unconfined_type file_type:file { append audit_access create 
execute execute_no_trans getattr ioctl link lock map mounton open 
quotaon read relabelfrom relabelto rename setattr swapon unlink write };
allow unconfined_t user_cron_spool_t:file entrypoint; [ 
cron_userdomain_transition ]:True

allow unconfined_t user_cron_spool_t:file { getattr ioctl read write };

This made no difference, my backups still don't run.  The last backup 
ran Aug 13.


What do I need to change to get my backups to start running 
automatically again?


Paolo

___
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: Python2 package build

[Paolo Galtieri]

After doing a little more investigation here's the issue.  When rpmbuild 
runs the compile phase it does the following:


./configure --build=x86_64-redhat-linux-gnu 
--host=x86_64-redhat-linux-gnu --program-prefix= 
--disable-dependency-tracking --prefix=/usr --exec-prefix=/usr 
--bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc 
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 
--libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib 
--mandir=/usr/share/man --infodir=/usr/share/info --disable-static


When this completes every Makefile has this entry in it.

PYTHON = /usr/bin/python
PYTHON_CC = gcc -pthread
PYTHON_EMBED_LIBS = -L/usr/lib64 -lm -lpthread -ldl  -lutil -lpython2.7
PYTHON_EXEC_PREFIX = ${exec_prefix}
PYTHON_INCLUDES = *-I/usr/include/python3.7m -I/usr/include/python3.7m*
PYTHON_LDFLAGS =
PYTHON_LIBS =
PYTHON_PLATFORM = linux2
PYTHON_PREFIX = ${prefix}
PYTHON_VERSION = 2.7

Note the PYTHON_INCLUDES entry.  The problem is that on Jul 1 the 
following program was added:


/usr/bin/python-config

The configure program has this code in it:

if test -x "$PYTHON-config"; then
PYTHON_INCLUDES=`$PYTHON-config --includes 2>/dev/null`
else
PYTHON_INCLUDES="-I${py_prefix}/include/python${PYTHON_VERSION}"

So on May 6 when I ran the rpmbuild the first time python-config did not 
exist hence it dropped into the else case.  In the else case 
PYTHON_VERSION is determined by the output of


$PYTHON -c "import sys; print sys.version[:3]"

where PYTHON is python2.  python-config is linked to python3-config.  
There is a python2-config which is dated July 20.  There is nothing 
configured to use alternatives to switch between versions of 
python-config as there is to switch between versions of python.  One way 
to fix this is for python-config to determine the version of python that 
is currently active and then call the appropriate python*-config, since 
there is a python3.7m-config.  This way one doesn't have to remember to 
go change the python-config link every time you change versions of python.


Paolo

On 8/13/20 11:18 AM, Felix Schwarz wrote:

Am 13.08.20 um 18:51 schrieb Paolo Galtieri:

Back in May I built several python2 packages that I needed to make sbackup
work on F32.  sbackup is the python2 application I use to do daily backups.

The source packages I rebuilt are

   gnome-python2-2.28.1-23.fc29.src.rpm
   pyorbit-2.24.0-28.fc30.src.rpm

Back in May the packages built fine.  I recently upgraded one system from F30
to F31, so I tried to rebuild the packages on F31.  The build fails.  Here is
one of the messages:

Not sure what you are actually doing but this works for me:

fedpkg clone --anonymous gnome-python2
cd gnome-python2
git checkout f31
fedpkg --release=f32 mockbuild
(same for pyorbit)

Besides that you should try to use sbackup with Python 3 somehow as it is
pretty likely that you won't be able to use the gnome/pyorbit libraries
anymore due to newer external dependencies in a few months/years.

Felix
___
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: Python2 package build

[Paolo Galtieri]

I did try to port it to python 3.  The problem I encountered was that 
one of the modules sbackup used had no corresponding one in python 3.


As I said in my email this all worked back on May 6 when I built the 
modules I needed to get sbackup to work with python 2.


All I'm trying to do is use rpmbuild to build the binary packages from 
the source RPMs.


Paolo

On 8/13/20 11:18 AM, Felix Schwarz wrote:

Am 13.08.20 um 18:51 schrieb Paolo Galtieri:

Back in May I built several python2 packages that I needed to make sbackup
work on F32.  sbackup is the python2 application I use to do daily backups.

The source packages I rebuilt are

   gnome-python2-2.28.1-23.fc29.src.rpm
   pyorbit-2.24.0-28.fc30.src.rpm

Back in May the packages built fine.  I recently upgraded one system from F30
to F31, so I tried to rebuild the packages on F31.  The build fails.  Here is
one of the messages:

Not sure what you are actually doing but this works for me:

fedpkg clone --anonymous gnome-python2
cd gnome-python2
git checkout f31
fedpkg --release=f32 mockbuild
(same for pyorbit)

Besides that you should try to use sbackup with Python 3 somehow as it is
pretty likely that you won't be able to use the gnome/pyorbit libraries
anymore due to newer external dependencies in a few months/years.

Felix
___
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

Python2 package build

[Paolo Galtieri]

Folks,
  an issue has come up recently that I don't understand.  This problem 
applies to both F31 and F32.


Back in May I built several python2 packages that I needed to make 
sbackup work on F32.  sbackup is the python2 application I use to do 
daily backups.


The source packages I rebuilt are

  gnome-python2-2.28.1-23.fc29.src.rpm
  pyorbit-2.24.0-28.fc30.src.rpm

Back in May the packages built fine.  I recently upgraded one system 
from F30 to F31, so I tried to rebuild the packages on F31.  The build 
fails.  Here is one of the messages:


gnomemodule.c:55:57: warning: passing argument 3 of 
'PyDict_SetItemString' makes pointer from integer without a cast 
[-Wint-conversion]
   55 | PyDict_SetItemString(dict, "POPT_CONTEXT_ARG_OPTS", 
PyInt_FromLong(POPT_CONTEXT_ARG_OPTS));

  | ^
  | |
  | int
In file included from */usr/include/python3.7m/Python.h*:109,
 from /usr/include/pygtk-2.0/pygobject.h:5,
 from gnomemodule.c:8:


Note that despite having python set to python2 during the build it's 
pulling a file from python3 directory.  This same failure occurs now on 
F32 as well.  How can I get the compile to pull in python2 files?


[root@terrapin rpmbuild]# python -V
Python 2.7.18

The build is done:

rpmbuild -ba SPECS/gnome-python2.spec

This is dependent on also building pyorbit

rpmbuild -ba SPECS/pyorbit.spec

note that pyorbit will not build if python is python2, but will build if 
you use python3


It seems to me that the whole build setup for python2 is all messed up 
on both F31 and F32 and I don't know what I need to do to fix things so 
I can compile both pyorbit and gnome-python2 with python set to python2.


Any help is appreciated.

Paolo
___
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

python3 and gnome packages

[Paolo Galtieri]

Folks,
  about a week ago I posted an email regarding bindings to libgnome, 
but I never did see the post on the list, just one person's response.  
The issue is that the program I use for doing backups, sbackup, fails 
with python 3.  The 2 main failures are in regard to the following:


import gnome.ui

and

import gnome.vfs

or more specifically the packages:

gnome-python2-gnomevfs-2.28.1-23.fc29.x86_64
gnome-python2-gnome.x86_64

so my question is how do I get the same features in python 3?

The gnome.vfs failure occurred after I upgraded from F31 to F32. Under 
F31 the front end of sbackup fails because of the lack of gnome.ui.  
Under F32 the back end now fails due to the lack of gnome.vfs.


Any help is appreciated.

Paolo
___
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

python 3 bindings for libgnome

[Paolo Galtieri]

Folks,
  I have an issue that has cropped up in F31 and F32 and I hope someone 
can help me.


I have been using sbackup for years to do backups on my system. It has 
worked great up to and including F30.  This program is a python2 
program.  The issue though has to do with bindings to libgnome.  The 
sbackup program consists of 2 parts, a front end and a back end which 
actually does the backup.  As long as I add #!/usr/bin/python2 to the 
back end backups work fine.  The issue I have is with the front end.  
When I run the front end simple-backup-config on an F32 system I get the 
following:


Traceback (most recent call last):
  File "/usr/sbin/simple-backup-config", line 36, in 
    import gnome.ui
ImportError: No module named gnome.ui

In F30 this module is provided by the package

gnome-python2-gnome-2.28.1-23.fc29.x86_64

Is there a corresponding package for python 3?  I know python 2 is end 
of life, and I know I need to port sbackup to python 3 going forward, 
but I don't know what the python 3 equivalent to the gnome-python2-gnome 
package.


Any help is appreciated.

Paolo
___
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: No visible mouse pointer

[Paolo Galtieri]

Ranjan,
  what's interesting about this problem is that it only happens on a new Dell 
server system.  Everything used to work just fine until some update introduced 
the problem.  I have a Dell laptop running F30 and I don't see the problem on 
that system.

Paolo


On 12/30/19 10:41 AM, Ranjan Maitra wrote:

Paolo,

I have had this problem, with one old Thinkpad, but only after wakeup from 
hibernate. Another student has reported the same problem on a Dell laptop.

What works for me is to click on the right mouse button (I use openbox WM) and 
then the pointer works.

I have not this issue with two other laptops and one desktop workstation (all 
Dells).

HTH, but it would be nice to get this resolved more holistically.

Ranjan


On Mon, 30 Dec 2019 10:25:59 -0800 Paolo Galtieri  wrote:


I have successfully upgraded one system to F31, however, it still
exhibits the same problem it has had under F30, namely no visible mouse
pointer.  The mouse does work since I have configured my MATE desktop to
display the mouse pointer location when I press the ctrl key.  This only
works once I am logged in, until then I have to move the mouse until I
see something change to know where the mouse is.  Does anyone have a
solution to this problem?

Paolo
___
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: Upgrading to f31

[Paolo Galtieri]

When the failure occurs this is the error I get:

Error:
 Problem: package cmake-fedora-2.9.3-5.fc31.noarch requires 
packagedb-cli, but none of the providers can be installed

  - problem with installed package cmake-fedora-2.9.3-4.fc30.noarch
  - packagedb-cli-2.14.1-9.fc30.noarch does not belong to a distupgrade 
repository
  - cmake-fedora-2.9.3-4.fc30.noarch does not belong to a distupgrade 
repository

(try to add '--skip-broken' to skip uninstallable packages)

Paolo

On 12/30/19 10:59 AM, Samuel Sieb wrote:

On 12/30/19 7:47 AM, Paolo Galtieri wrote:
Using --allowerasing instead of --skip-broken, which is what was 
recommended, has allowed the upgrade to continue. It seems to me that 
the documentation should be changed to include --allowerasing by 
default.


Where did you see that recommendation?
___
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

No visible mouse pointer

[Paolo Galtieri]

I have successfully upgraded one system to F31, however, it still 
exhibits the same problem it has had under F30, namely no visible mouse 
pointer.  The mouse does work since I have configured my MATE desktop to 
display the mouse pointer location when I press the ctrl key.  This only 
works once I am logged in, until then I have to move the mouse until I 
see something change to know where the mouse is.  Does anyone have a 
solution to this problem?


Paolo
___
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: Upgrading to f31

[Paolo Galtieri]

Using --allowerasing instead of --skip-broken, which is what was 
recommended, has allowed the upgrade to continue. It seems to me that 
the documentation should be changed to include --allowerasing by default.


Paolo

On 12/30/19 6:52 AM, Robert McBroom via users wrote:

On 12/30/19 12:39 AM, Paolo Galtieri wrote:

Folks,
?? I was trying to upgrade one of my systems to f31 by running:

sudo dnf system-upgrade download --skip-broken --refresh --releasever=31

but the attempt fails with:

Error:
??Problem: package cmake-fedora-2.9.3-5.fc31.noarch requires 
packagedb-cli, but none of the providers can be installed

?? - problem with installed package cmake-fedora-2.9.3-4.fc30.noarch
?? - packagedb-cli-2.14.1-9.fc30.noarch does not belong to a 
distupgrade repository
?? - cmake-fedora-2.9.3-4.fc30.noarch does not belong to a 
distupgrade repository


removing these 2 packages results in the removal of over 50 other 
packages.


So what do I need to do to do the upgrade?


Some options start to get very ambiguous.?? I used--


dnf --releasever=31 --setopt=deltarpm=false distro-sync --allowerasing -y
___
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

Upgrading to f31

[Paolo Galtieri]

Folks,
  I was trying to upgrade one of my systems to f31 by running:

sudo dnf system-upgrade download --skip-broken --refresh --releasever=31

but the attempt fails with:

Error:
 Problem: package cmake-fedora-2.9.3-5.fc31.noarch requires 
packagedb-cli, but none of the providers can be installed

  - problem with installed package cmake-fedora-2.9.3-4.fc30.noarch
  - packagedb-cli-2.14.1-9.fc30.noarch does not belong to a distupgrade 
repository
  - cmake-fedora-2.9.3-4.fc30.noarch does not belong to a distupgrade 
repository


removing these 2 packages results in the removal of over 50 other packages.

So what do I need to do to do the upgrade?

Any help is appreciated.

Paolo
___
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

importing photos from camera

[Paolo Galtieri]

Folks,
  I am having an issue with importing photos from my Nikon D90 under F30.

Under F29 when I right click on the camera icon on the desktop and look 
at the "Open With Other Application" there was an entry for "Open With 
gThumb Photo Import Tool".  This option is missing from F30.  So I 
decide to use a custom command, the command being gthumb 
--import-photos.  Now when I right click on the camera icon and look at 
the possible commands there is one called gthumb, with no description of 
what this command does, and there was no way to specify a description 
when I entered the command.  When I select it it now allows me to import 
my photos.  The box that says "Remember this application for 
"application/x-caja-link type" files is also checked.  However it does 
not remember my selection.  It continues to show "Open With gThumb Image 
Viewer" as the application to use when I plug my camera into my laptop.


I'm using the MATE desktop.

So what do I need to do to get gthumb --import-photos to actually run 
when I plug my camera in?


Any help is appreciated.

Paolo
___
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: WiFi now disabled by radio killswitch

[Paolo Galtieri]

Toggling the disable wifi button on the laptop keyboard did fix the 
problem.  Now if I close the lid and lift it the wireless is still 
enabled.  I still don't understand why the wifi is killed while using it.


Thanks for the help.

Paolo

On 10/28/19 4:48 PM, Ed Greshko wrote:

On 10/29/19 7:31 AM, Paolo Galtieri wrote:

I ran

rfkill list:

0: dell-rbtn: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

I then tried running

sudo rfkill unblock wlan

and then

rfkill list:

0: dell-rbtn: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

It still shows that it's hard blocked.




Pretty sure "hard" means blocked in the hardware.  A few years ago a 
friend of mine had what I
recall was the same sort of issue.  He fixed it by toggling the switch 
on the laptop repeatedly.

Apparently it was a "sticky" problem.



___
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: WiFi now disabled by radio killswitch

[Paolo Galtieri]

I ran

rfkill list:

0: dell-rbtn: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

I then tried running

sudo rfkill unblock wlan

and then

rfkill list:

0: dell-rbtn: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

It still shows that it's hard blocked.


Paolo

On 10/28/19 9:16 AM, Tom Horsley wrote:

On Mon, 28 Oct 2019 09:04:28 -0700
Paolo Galtieri wrote:


Any idea what I can do to get around this issue?

Don't know what it causing it, but you should be
able to run "rfkill" to turn it back on rather than
having to reboot.
___
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

WiFi now disabled by radio killswitch

[Paolo Galtieri]

Folks,
  several months ago I was getting the following error:

WiFi now disabled by radio killswitch

forcing a reboot to get my wifi back.  Then the problem went away, but 
now it's back.  Every time I close the lid of my laptop and then reopen 
it several minutes later the wifi is dead and requires a reboot to fix.  
The problem has happened while running. This is really annoying.


Is this a hardware issue or software?

Any idea what I can do to get around this issue?

I'm running f29.
___
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

ccache on f30

[Paolo Galtieri]

Folks,
  I installed the ccache package on F30.  Doing a rpm -ql on the 
package show a long list of files that are part of the package, but if I do


ls -l  /usr/lib64/ccache/

it shows

total 576
-rwxr-xr-x. 1 root root 193392 Jan 31 07:23 cc
-rwxr-xr-x. 1 root root 193392 Jan 31 07:23 gcc
-rwxr-xr-x. 1 root root 193392 Jan 31 07:23 x86_64-redhat-linux-gcc

where are all the other files, e.g. /usr/lib64/ccache/c++?

Paolo





















___
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: sound device initialization?

[Paolo Galtieri]

Have you tried using pavucontrol?

I have an issue with sound on my laptop with the MATE desktop and an 
external monitor.  Often when I login to the laptop I'll have no sound 
and the mate_volume_applet doesn't change the volume. Using pavucontrol 
I determined that the problem was the monitor plugged into the HDMI port 
of my laptop. pavucontrol shows 2 entries under the configuration tab 
for built in audio, one for the HDMI port and one for the actual built 
in audio.  As soon as I disable the HDMI entry the mate_volume_applet 
works and I have sound.  That is until for some reason the HDMI entry 
gets turned on again and I have to disable it again.


Paolo

On 7/4/19 8:53 AM, Tom Horsley wrote:

Lately when I install updates and reboot, I'll randomly
have no sound when I log back in. I'm supposed to get
sound output on my HDMI interface (being run by the
nvidia binary driver from rpmfusion).

If I run "gnome-control-center sound", it will show
as currently using a dummy device, and if I try to switch
to HDMI output (which is listed as a choice), it won't
allow me to test the audio out.

Rebooting and hoping I'll have sound when I come back
has been the only way I've found to fix this so far.

Anyone know if there is some way to re-initialize
audio devices less drastic than rebooting?
___
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: external USB drives

[Paolo Galtieri]

I managed to figure that out after I sent the email.  What confused me 
was that for 1 and 2 TB drives fdisk -l says the drives are:


Device Boot Start    End    Sectors  Size Id Type
/dev/sdc1  * 2048 3907029166 3907027119  1.8T  7 HPFS/NTFS/exFAT

for 4 and 8 TB drives dfisk -l shows

Device  Start End Sectors  Size Type
/dev/sdd1  34  262177  262144  128M Microsoft reserved
/dev/sdd2  264192 15628052479 15627788288  7.3T Microsoft basic data

so I assumed (incorrectly) FAT.  It was only afterwards that I thought NTFS.

Oh well, live and learn :-)

Paolo

On 7/3/19 3:42 PM, ToddAndMargo via users wrote:

On 7/3/19 1:50 PM, Paolo Galtieri wrote:

Folks,
  I recently purchased a 4TB external USB drive.  I have purchased 
USB drives in the past and have run dosfslabel to set the drive 
label.  When I tried this on F29 I get the following:


dosfslabel /dev/sdc2 NEW_LABEL

Currently, only 1 or 2 FATs are supported, not 0.

I have 2 8TB drives which I labeled some time ago without a problem, 
but now I get the same error when I try to print out the drive label


dosfslabel /dev/sdd2

Currently, only 1 or 2 FATs are supported, not 0.

The new drive shows up on the desktop as:

"Seagate Expansion Drive"

I tried the same thing on F30 with the same result.

Can someone tell me what's going on?

Paolo


Hi Paolo,

It is probably formatted in NTFS.

The best way I have found for setting drive labes is
gparted

 # dnf install gparted

It is a graphical interface4 and gives you tons of information.
First thing I would do it check to see if it is NTFS.

The label is under the "partition" drop down.

And you can always wipe and create whatever partition type
you want.

HTH,
-T



___
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

external USB drives

[Paolo Galtieri]

Folks,
 I recently purchased a 4TB external USB drive.  I have purchased USB 
drives in the past and have run dosfslabel to set the drive label.  When 
I tried this on F29 I get the following:


dosfslabel /dev/sdc2 NEW_LABEL

Currently, only 1 or 2 FATs are supported, not 0.

I have 2 8TB drives which I labeled some time ago without a problem, but 
now I get the same error when I try to print out the drive label


dosfslabel /dev/sdd2

Currently, only 1 or 2 FATs are supported, not 0.

The new drive shows up on the desktop as:

"Seagate Expansion Drive"

I tried the same thing on F30 with the same result.

Can someone tell me what's going on?

Paolo
___
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

mariadb vs community-mysql on F30

[Paolo Galtieri]

Folks I have an issue with mariadb and community-mysql.  I installed 
mysql-workbench.  When I run it it shows a conflict between it and the 
running mysql server, namely mysql-workbench is version 8.0.16 and 
mariadb is 10.3.12.  So I decided to remove mariadb, i.e. I did:


yum remove mariadb-common mariadb-connector-c mariadb-embedded 
mariadb-errmsg


In doing this a total of 62 packages were removed:

Removing:
 mariadb-common   x86_64 3:10.3.12-10.fc30 @fedora   179 k
 mariadb-connector-c  x86_64 3.0.10-1.fc30 @updates  712 k
 mariadb-embedded x86_64 3:10.3.12-10.fc30 @fedora    22 M
 mariadb-errmsg   x86_64 3:10.3.12-10.fc30 @fedora   2.3 M
Removing dependent packages:
 freeradius-mysql x86_64 3.0.19-1.fc30 @fedora    78 k
 kf5-akonadi-server-mysql x86_64 18.12.2-2.fc30 @fedora   3.4 k
 libreoffice-calc x86_64 1:6.2.4.2-1.fc30 @updates   46 M
 libreoffice-draw x86_64 1:6.2.4.2-1.fc30 @updates   65 k
 libreoffice-emailmerge   x86_64 1:6.2.4.2-1.fc30 @updates   26 k
 libreoffice-impress  x86_64 1:6.2.4.2-1.fc30 @updates  2.9 M
 libreoffice-math x86_64 1:6.2.4.2-1.fc30 @updates  2.1 M
 perl-DBD-MySQL   x86_64 4.050-2.fc30 @fedora   367 k
Removing unused dependencies:
 autocorr-en  noarch 1:6.2.4.2-1.fc30 @updates  467 k
 clucene-contribs-lib x86_64 2.3.3.4-34.20130812.e8e3d20git.fc30
@anaconda 516 k
 gstreamer1-plugins-good-gtk  x86_64 1.16.0-1.fc30 @updates   69 k
 hyphen-en    noarch 2.8.8-11.fc30 @anaconda 104 k
 libabw   x86_64 0.1.2-4.fc30 @anaconda 501 k
 libcdr   x86_64 0.1.5-4.fc30 @anaconda 983 k
 libcmis  x86_64 0.5.2-2.fc30 @anaconda 2.2 M
 libe-book    x86_64 0.1.3-9.fc30 @anaconda 861 k
 libeot   x86_64 0.01-11.fc30 @anaconda  99 k
 libepubgen   x86_64 0.1.1-3.fc30 @anaconda 613 k
 libetonyek   x86_64 0.1.9-3.fc30 @anaconda 4.2 M
 libexttextcat    x86_64 3.4.5-4.fc30 @anaconda 438 k
 libfbclient2 x86_64 3.0.4.33054-2.fc30 @fedora   2.2 M
 libfreehand  x86_64 0.1.2-4.fc30 @anaconda 547 k
 liblangtag   x86_64 0.6.2-7.fc30 @anaconda 268 k
 liblangtag-data  noarch 0.6.2-7.fc30 @anaconda 1.9 M
 libmspub x86_64 0.1.4-7.fc30 @anaconda 536 k
 libmwaw  x86_64 0.3.15-1.fc30 @updates  9.0 M
 libnumbertext    x86_64 1.0.5-2.fc30 @anaconda 1.0 M
 libodfgen    x86_64 0.1.7-4.fc30 @anaconda 1.2 M
 liborcus x86_64 0.14.1-3.fc30 @anaconda 1.9 M
 libpagemaker x86_64 0.0.4-6.fc30 @anaconda 313 k
 libqxp   x86_64 0.0.2-3.fc30 @anaconda 525 k
 libreoffice-core x86_64 1:6.2.4.2-1.fc30 @updates  346 M
 libreoffice-data noarch 1:6.2.4.2-1.fc30 @updates  7.4 M
 libreoffice-graphicfilter    x86_64 1:6.2.4.2-1.fc30 @updates  1.5 M
 libreoffice-gtk3 x86_64 1:6.2.4.2-1.fc30 @updates  2.3 M
 libreoffice-help-en  x86_64 1:6.2.4.2-1.fc30 @updates   25 M
 libreoffice-langpack-en  x86_64 1:6.2.4.2-1.fc30 @updates  187 k
 libreoffice-opensymbol-fonts noarch 1:6.2.4.2-1.fc30 @updates  623 k
 libreoffice-pdfimport    x86_64 1:6.2.4.2-1.fc30 @updates  960 k
 libreoffice-pyuno    x86_64 1:6.2.4.2-1.fc30 @updates  1.1 M
 libreoffice-ure  x86_64 1:6.2.4.2-1.fc30 @updates  9.6 M
 libreoffice-ure-common   noarch 1:6.2.4.2-1.fc30 @updates  854 k
 libreoffice-writer   x86_64 1:6.2.4.2-1.fc30 @updates   20 M
 libreoffice-x11  x86_64 1:6.2.4.2-1.fc30 @updates  1.1 M
 librevenge   x86_64 0.0.4-13.fc30 @anaconda 932 k
 libstaroffice    x86_64 0.0.6-3.fc30 @anaconda 3.3 M
 libvisio x86_64 0.1.6-8.fc30 @anaconda 910 k
 libwpd   x86_64 0.10.3-2.fc30 @anaconda 1.2 M
 libwpg   x86_64 0.3.3-2.fc30 @anaconda 221 k
 libwps   x86_64 0.4.10-2.fc30 @anaconda 3.0 M
 libzmf   x86_64 0.0.2-9.fc30 @anaconda 269 k
 lpsolve  x86_64 5.5.2.0-22.fc30 @anaconda 1.3 M
 mythes   x86_64 1.2.4-11.fc30 @anaconda  24 k
 mythes-en    noarch 3.0-26.fc30 @anaconda  21 M
 neon x86_64 0.30.2-10.fc30 @anaconda 360 k
 pakchois x86_64 0.4-19.fc30 @anaconda  32 k
 qt5-qtbase-mysql x86_64 5.12.1-7.fc30 @updates  117 k
 xmlsec1-nss  x86_64 1.2.27-2.fc30 @anaconda 246 k

Transaction Summary

Remove  62 Packages

I then did an install of community mysql:

yum install community-mysql-common.x86_64 community-mysql-devel.x86_64 
community-mysql-errmsg.x86_64 community-mysql-libs.x8

WiFi now disabled by radio killswitch

[Paolo Galtieri]

Folks,
  on both June 2 and June 4 I have seen the following message in the logs:

Jun  4 13:35:53 terrapin NetworkManager[1529]:  [1559680553.5293] 
manager: rfkill: WiFi now disabled by radio killswitch


Until I shutdown my system and reboot I cannot connect to my WiFi network.

Has anyone else seen this and can tell why I'm getting it?  The first 
time this message appears is on June 2.


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

Can't use MATE desktop with F29

[Paolo Galtieri]

Folks,
  I upgraded one of my F28 systems to F29.  I installed th Gnome 
Classic and MATE desktops.  When the system boots up and I login using 
the MATE desktop the screen is completely garbled.  A message appears 
saying something like "required virtual size does not fit", however it 
goes away almost immediately so I can't get all the text.  If I login 
using Gnome or Gnome Classic everything works fine.  I also tries gdm 
and I get the same thing.  Anyone know what's going on?


Here's my video card:

01:00.0 VGA compatible controller: NVIDIA Corporation G72 [GeForce 7300 
GS] (rev a1)


cat /proc/meminfo
MemTotal:    8098456 kB
MemFree: 4787340 kB
MemAvailable:    7303280 kB
Buffers:  157360 kB
Cached:  2512716 kB
SwapCached:    0 kB
Active:  188 kB
Inactive:    1619888 kB
Active(anon): 284176 kB
Inactive(anon):    16844 kB
Active(file):    1049212 kB
Inactive(file):  1603044 kB
Unevictable:  32 kB
Mlocked:  32 kB
SwapTotal:   8142844 kB
SwapFree:    8142844 kB
Dirty:    32 kB
Writeback: 0 kB
AnonPages:    283276 kB
Mapped:   256576 kB
Shmem: 17828 kB
KReclaimable: 167784 kB
Slab: 271804 kB
SReclaimable: 167784 kB
SUnreclaim:   104020 kB
KernelStack:    5312 kB
PageTables:    10536 kB
NFS_Unstable:  0 kB
Bounce:    0 kB
WritebackTmp:  0 kB
CommitLimit:    12192072 kB
Committed_AS:    2335964 kB
VmallocTotal:   34359738367 kB
VmallocUsed:   0 kB
VmallocChunk:  0 kB
Percpu: 3072 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages:    0 kB
ShmemPmdMapped:    0 kB
CmaTotal:  0 kB
CmaFree:   0 kB
HugePages_Total:   0
HugePages_Free:    0
HugePages_Rsvd:    0
HugePages_Surp:    0
Hugepagesize:   2048 kB
Hugetlb:   0 kB
DirectMap4k:  207400 kB
DirectMap2M: 8114176 kB

cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 15
model        : 4
model name    : Intel(R) Pentium(R) D CPU 3.20GHz
stepping    : 4
microcode    : 0x6
cpu MHz        : 3192.210
cache size    : 1024 KB
physical id    : 0
siblings    : 2
core id        : 0
cpu cores    : 2
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 5
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc pebs bts nopl cpuid pni dtes64 monitor ds_cpl est cid 
cx16 xtpr pti

bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips    : 6384.42
clflush size    : 64
cache_alignment    : 128
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 15
model        : 4
model name    : Intel(R) Pentium(R) D CPU 3.20GHz
stepping    : 4
microcode    : 0x6
cpu MHz        : 3192.210
cache size    : 1024 KB
physical id    : 0
siblings    : 2
core id        : 1
cpu cores    : 2
apicid        : 1
initial apicid    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 5
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc pebs bts nopl cpuid pni dtes64 monitor ds_cpl est cid 
cx16 xtpr pti

bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips    : 6384.42
clflush size    : 64
cache_alignment    : 128
address sizes    : 36 bits physical, 48 bits virtual
power management:

Any help is appreciated.

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

Re: Can't play video dvd

[Paolo Galtieri]

I installed vlc from the F28 repo, dnf -y install vlc.

I tried using vlc to view a different video DVD, "Great Migrations," and 
that works fine.  There is something about "Free Solo" which appears to 
confuse all 3 video players I've tried on F28.


Paolo

On 3/15/19 7:32 AM, Ger van Dijck wrote:

On Thu, 14 Mar 2019 21:46:44 +0100, Paolo Galtieri 
wrote:

I tried totem and mplayer and both fail. I tried vlc and it displayed 
a bunch of messages and crashed with a segmentation fault.  Here are 
the messages:


VLC media player 3.0.6 Vetinari (revision 3.0.6-0-g5803e85f73)
[56301c2b49e0] main libvlc: Running vlc with the default 
interface. Use 'cvlc' to use vlc without interface.

[56301c2b3f30] main playlist: playlist is empty
libdvdnav: Using dvdnav version 6.0.0

*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:572 ***
*** for vmgi_mat->vmg_last_sector != 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:574 ***
*** for vmgi_mat->vmgi_last_sector * 2 <= vmgi_mat->vmg_last_sector ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:575 ***
*** for vmgi_mat->vmgi_last_sector * 2 <= vmgi_mat->vmg_last_sector ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:588 ***
*** for vmgi_mat->vmgm_vobs == 0 || (vmgi_mat->vmgm_vobs > 
vmgi_mat->vmgi_last_sector && vmgi_mat->vmgm_vobs < 
vmgi_mat->vmg_last_sector) ***


libdvdread: data mismatch: info_length (7)!= nr_of_srpts (8). 
Truncating.


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1091 ***
*** for tt_srpt->title[i].nr_of_angles != 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1091 ***
*** for tt_srpt->title[i].nr_of_angles != 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1098 ***
*** for tt_srpt->title[i].vts_ttn != 0 ***

libdvdnav: DVD Title: FREE_SOLO
libdvdnav: DVD Serial Number: 772D6927APPLEDSP
libdvdnav: DVD Title (Alternative): FREE_SOLO
libdvdnav: DVD disk reports itself with Region mask 0x0040. 
Regions: 1 2 3 4 5 6 8


libdvdread: Attempting to retrieve all CSS keys
libdvdread: This can take a _long_ time, please be patient

libdvdread: Get key for /VIDEO_TS/VIDEO_TS.VOB at 0x0133
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_01_0.VOB at 0x497e
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_01_1.VOB at 0x4c8f
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_02_0.VOB at 0x5c57
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_02_1.VOB at 0x5c90
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_03_0.VOB at 0x5cfd
libdvdread: Elapsed time 0
libdvdread: Found 2 VTS's
libdvdread: Elapsed time 0

*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1260 ***
*** for vts_ptt_srpt->title[i].ptt[j].pgcn != 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1904 ***
*** for pgcit->pgci_srp[i].pgc_start_byte + PGC_SIZE <= 
pgcit->last_byte+1 ***


libdvdread: Unable to read invalid PCG

*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1260 ***
*** for vts_ptt_srpt->title[i].ptt[j].pgcn != 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1904 ***
*** for pgcit->pgci_srp[i].pgc_start_byte + PGC_SIZE <= 
pgcit-&

Re: Can't play video dvd

[Paolo Galtieri]

r_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***


*** libdvdread: CHECK_VALUE failed in src/ifo_read.c:1672 ***
*** for c_adt->cell_adr_table[i].vob_id > 0 ***

Segmentation fault (core dumped)

Paolo

On 3/14/19 11:34 AM, Ger van Dijck wrote:

Op Thu, 14 Mar 2019 19:17:21 +0100 schreef Samuel Sieb :


On 3/14/19 11:05 AM, Paolo Galtieri wrote:
   I recently purchased the DVD "Free Solo".  When I try to play it 
on my Fedora 28 system it fails.  I get the following error "An 
error occurred The movie could not be read".  I did some web 
searching and I found that someone also encountered this error and 
that I needed to install libdvdcss for things to work.  I installed 
this library and rebooted and I still get the error.  I have 
verified that the DVD works by playing it on a Windows system. So 
what am I missing in order to get this to work?  When I put the DVD 
in it does read it, because I get the title page, but when I click 
on the play movie link I get the error.


What program are you using to play it?  I would recommend trying vlc.
_

I installed vlc and it works fine and perfect : I can advice it.




Ger van Dijck.



__

users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Can't play video dvd

[Paolo Galtieri]

Folks,
  I recently purchased the DVD "Free Solo".  When I try to play it on 
my Fedora 28 system it fails.  I get the following error "An error 
occurred The movie could not be read".  I did some web searching and I 
found that someone also encountered this error and that I needed to 
install libdvdcss for things to work.  I installed this library and 
rebooted and I still get the error.  I have verified that the DVD works 
by playing it on a Windows system. So what am I missing in order to get 
this to work?  When I put the DVD in it does read it, because I get the 
title page, but when I click on the play movie link I get the error.


The "Free Solo" DVD is from National Geographic, so I tried another DVD, 
also from National Geographic, and that one worked fine.  So the problem 
seems to be with how F28 processes the "Free Solo" DVD.


Any help is appreciated.

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

Can't boot kernel-4.19.6-200.fc28.x86_64

[Paolo Galtieri]

Folks,
  this morning I rebooted one of my systems.  The system ended up 
dropping into emergency mode.  I ran journalctl -xb to see why it failed 
to boot and I saw the following errors:


Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol gfn_to_memslot 
(err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_pin_pages 
(err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
vfio_info_cap_shift (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
vfio_set_irqs_validate_and_prepare (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_device_put 
(err -2)

Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol gfn_to_pfn (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_from_dev 
(err -2)

Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_put_kvm (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_write_guest 
(err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
kvm_slot_page_track_remove_page (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
kvm_page_track_register_notifier (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_parent_dev 
(err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_unpin_pages 
(err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
kvm_is_visible_gfn (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
kvm_page_track_unregister_notifier (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
vfio_device_get_from_dev (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
kvm_slot_page_track_add_page (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
vfio_register_notifier (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
vfio_info_add_capability (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_get_drvdata 
(err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
mdev_register_device (err -2)

Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_dev (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
mdev_unregister_device (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol 
vfio_unregister_notifier (err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_read_guest 
(err -2)
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_set_drvdata 
(err -2)

Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_get_kvm (err -2)

I'm sure I booted up on 4.19.6 on this system before without errors.  In 
fact my other system is running 4.19.6 so what might have changed to 
cause this failure?  The system booted fine on 4.19.5.


Any help is appreciated.

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

strange issues on F28

[Paolo Galtieri]

I have 2 systems running F28, one is a laptop the other a desktop.  I 
rebooted both onto 4.19.2 last week. On the laptop I'm having some 
strange issues.


1)  When I rebooted the laptop this morning it failed to boot and 
dropped into emergency mode.  Looking at the logs I see at lot of these 
messages:


systemd-udevd[610]: could not find module by name='i2c_i801'
systemd-udevd[612]: could not find module by name='lpc_ich'
.
.
.

The system boots fine on 4.18.18-200.fc28.x86_64

The other system is running 4.19.2-200.fc28.x86_64 without issues.

2)  When I view a video with chrome I get no sound, but the same video 
played on firefox has sound.


3)  When I run pavucontrol the configuration shows 2 entries for built 
in audio.  It shows "Digital Stereo (HDMI) OUtput" for one and "Analog 
Stereo Duplex" for the other.  Under "Output Devices" it shows 
"HDMI/Display Port (plugged in)" and "Speakers".  The only thing I have 
plugged into the HDMI port is my monitor so I don't why it should show 
up here since it has no speakers.  The strange behavior I'm seeing is 
that I will turn the HDMI configuration off, but some time later it's 
been turned back on.


4)  I still can't get chrome to work on the desktop.  If I connect to 
non https sites chrome connects fine, but connecting to https sites 
results in "Your connection is not private" messages.  This has been 
going on now for over a week.


Anyone else seeing any of these issues?

Any help is appreciated.

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

Re: strange problem

[Paolo Galtieri]

Chrome was working fine on this system yesterday.  The upgrade went 
fine, so I'm really stumped as to why it has stopped working.


Paolo

On 11/11/18 2:47 PM, stan wrote:

On Sun, 11 Nov 2018 14:03:31 -0800
Paolo Galtieri  wrote:


What I don't understand about this problem is why it affects only one
system.  Chrome on my other system works fine as does chrome on my
android tablet.

Plugins?  Configuration?  Were some packages rejected for update
because of dependencies?  Try to remove chrome on the system that
doesn't work, and the system that works (be sure to say no to
confirmation). Does dnf want to delete the same packages, and the same
versions?

If the chrome is the same version, then it has to be something else.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: strange problem

[Paolo Galtieri]

What I don't understand about this problem is why it affects only one 
system.  Chrome on my other system works fine as does chrome on my 
android tablet.


Paolo

On 11/11/18 12:12 PM, stan wrote:

On Sun, 11 Nov 2018 09:55:06 -0800
Paolo Galtieri  wrote:


I encountered a strange problem today I'm wondering if someone can
explain what's going on.

Here's the problem, I have 2 systems running F28, one system was
upgraded from F27 two days ago, the other upgraded yesterday. Both
systems were working fine yesterday.  Today the second system will
not connect to any website using chrome, I get the following error


Your connection is not private

with the following detail

NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM

If I use firefox I don't get this error.  I have killed and restarted
chrome and the problem persists.  I have even rebooted the system and
the problem still persists.  What's curious is that the other system
doesn't show this failure.  The system that fails is the one that
actually connects to the internet, the other system routes through
the failing system to connect to the internet.

Anyone have any idea why I'm seeing this error and how to fix it?

Any help is appreciated.

I vaguely recall that chrome and firefox were going to start refusing
to connect to sites using certificates that were generated with an
algorithm that is now considered too weak.  It must be something in the
chrome configuration of the failing system doing this.  What happens if
you create a new user, and run chrome as that user?  When I saw this in
firefox, it was possible to override the refusal.  I don't know chrome,
so can't say if it also has that ability.

Try a web search using 'chrome weak certificate refusal' or similar and
you should find what other people did to get around this.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: SElinux error

[Paolo Galtieri]

The issue is normally the SElinux alert gives me the name of the process 
causing the problem, not a long string of characters.


Paolo

On 11/11/18 12:43 PM, Joe Zeff wrote:

On 11/11/2018 12:28 PM, Paolo Galtieri wrote:

Folks,
   I got the fllowing SElinux error today:

SELinux is preventing 72733A6D61696E20513A526567 from using the 
dac_override capability.


Anyone know what this refers to?


Are you getting this through sealert, the SELinux trouble shooter?  If 
so, use it to report the bug, and if you think it's reasonable, follow 
the instructions to create a custom policy to allow this.  I don't 
know what's causing this, but I do know what to do about it.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

SElinux error

[Paolo Galtieri]

Folks,
  I got the fllowing SElinux error today:

SELinux is preventing 72733A6D61696E20513A526567 from using the 
dac_override capability.


Anyone know what this refers to?

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

strange problem

[Paolo Galtieri]

I encountered a strange problem today I'm wondering if someone can 
explain what's going on.


Here's the problem, I have 2 systems running F28, one system was 
upgraded from F27 two days ago, the other upgraded yesterday. Both 
systems were working fine yesterday.  Today the second system will not 
connect to any website using chrome, I get the following error



Your connection is not private

with the following detail

NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM

If I use firefox I don't get this error.  I have killed and restarted 
chrome and the problem persists.  I have even rebooted the system and 
the problem still persists.  What's curious is that the other system 
doesn't show this failure.  The system that fails is the one that 
actually connects to the internet, the other system routes through the 
failing system to connect to the internet.


Anyone have any idea why I'm seeing this error and how to fix it?

Any help is appreciated.

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

issues with F27

[Paolo Galtieri]

I have F27 running on a couple of systems.  On one of them I have 
encountered the following 2 issues.


1) System crashes with "System not configured for semaphores". This 
error results in the system halting.  It has occurred several times over 
the last few months.


2) I have a Linksys AE1200 wireless adapter.  Every time I reboot my 
system this device does not come up.  I have to unplug it and plug it 
back in before the system sees it and configures it.


Both issues have occurred on different kernels over the last few 
months.  I also happen to have a Linksys AE1000 plugged into the same 
system and it comes up every time.


I updated to the AE1000 because I started experiencing problems where my 
internet connection would go away even though I was still connected to 
the cable modem via wireless.  I thought I was having problems with the 
wireless adapter so I bought a new one.  This has not solved the problem 
completely, but it has reduced the problem considerably.


Any ideas on what might be causing these issues?

Any help is appreciated.

Paolo

cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
stepping    : 11
microcode    : 0xba
cpu MHz        : 1604.067
cache size    : 4096 KB
physical id    : 0
siblings    : 4
core id        : 0
cpu cores    : 4
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf 
pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti 
tpr_shadow vnmi flexpriority dtherm

bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips    : 4788.02
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
stepping    : 11
microcode    : 0xba
cpu MHz        : 1637.657
cache size    : 4096 KB
physical id    : 0
siblings    : 4
core id        : 1
cpu cores    : 4
apicid        : 1
initial apicid    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf 
pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti 
tpr_shadow vnmi flexpriority dtherm

bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips    : 4788.02
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 2
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
stepping    : 11
microcode    : 0xba
cpu MHz        : 1673.092
cache size    : 4096 KB
physical id    : 0
siblings    : 4
core id        : 2
cpu cores    : 4
apicid        : 2
initial apicid    : 2
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf 
pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti 
tpr_shadow vnmi flexpriority dtherm

bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips    : 4788.02
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 3
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
stepping    : 11
microcode    : 0xba
cpu MHz        : 1629.113
cache size    : 4096 KB
physical id    : 0
siblings    : 4
core id        : 3
cpu cores    : 4
apicid        : 3
initial apicid    : 3
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf 
pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti 
tpr_shadow vnmi flexpriority dtherm

bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips    : 4788.02
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:


lspci
00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controll

Upgrade to f29

[Paolo Galtieri]

Folks,
  I tried to upgrade a system to F29 this AM.  The upgrade failed with 
the following error:


Last metadata expiration check: 0:00:00 ago on Wed 31 Oct 2018 09:27:12 
AM PDT.

Error:
 Problem: problem with installed package 
pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-15.fc28.x86_64
  - package 
pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-15.fc29.x86_64 
requires libcryptopp.so.6()(64bit), but none of the providers can be 
installed
  - 
pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-15.fc28.x86_64 
does not belong to a distupgrade repository
  - cryptopp-6.1.0-2.fc28.x86_64 does not belong to a distupgrade 
repository



Any ideas on how to fix this?

Any assistance is appreciated.

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

strange error on shutdown

[Paolo Galtieri]

I was in the process of rebooting my system after doing an update and 
got the following:



error: unexpectedly disconnected from boot status daemon

dracut Warning:

/lib/dracut-lib.sh: line 1088: /sbin/rdsosreport: No such file or directory
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick 
or /boot

after mounting them and attach to a bug report.

To get more debug information in the report,
reboot with "rd.debug" added to the kernel command line.

Dropping to debug shell.

shutdown:/#

At this point anything I type is not displayed, but the output is.

For example

shutdown:/# sh: child setpgid (4318 to 4318): Permission denied

It then displayed the output of the ls command which I had typed.


So what does this mean, and what should I do if I see this again?

Any help is appreciated.

Thanks,
Paolo
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/EVD7LGGJHCNYNQNMHVD2SHFFKD6X5GGY/