Re: Regex version mismatch after dnf update

2022-01-17 Thread Michal Schorm
Apparently, there is an long term issue in the selinux policy
  https://bugzilla.redhat.com/show_bug.cgi?id=2013642
and it will hopefully be fixed soon with the next update of the
selinux-policy package.

Thank you for the bugzilla report.

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Sun, Jan 16, 2022 at 5:37 PM Robert Moskowitz  wrote:
>
>
>
> On 1/16/22 11:31, Grumpey wrote:
> > On Sun, Jan 16, 2022 at 11:25 AM Robert Moskowitz  
> > wrote:
> >> Did a dnf update this morning before updating my bios and installing
> >> more memory (more on that in a separate missive)
> ...
>
> >>
> >> 2022-01-16T10:41:04-0500 INFO Regex version mismatch, expected: 10.39
> >> 2021-10-29 actual: 10.37 2021-05-26
> >> Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.37 2021-05-26
> >> Regex version mismatch, expected: 10.39 2021-10-29 actual: 10.37 2021-05-26
> >>
> >>
> >> What should I do about this?
> >>
> >> thanks
> > Bug Report: https://bugzilla.redhat.com/show_bug.cgi?id=2013642
> >
> > sudo semodule -nB
> >
> > resolved it for me.
>
> Works for me.  Thanks will have to look at this bug.
> ___
> 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


kdevelop:: pycodestyle not found

2022-01-17 Thread Adrian Sevcenco

Hi! I have a weird problem with kdevelop: after upgrade to f35 kdevelop no 
longer finds pycodestyle..
in the terminal output i get:
kdevelop.plugins.python.parser: Discarding parts of the code to be parsed 
because of previous errors
IndentationError: unexpected indent (, line 108)
 Parsing FAILED 
python code checker error: "The `pycodestyle` (previously `pep8`) module is not 
installed."

but i have both:
root@hal: ~ # rpm -qa | grep pycodestyle
python3-pycodestyle-2.7.0-2.fc35.noarch

and user side installation:
pip3 freeze | grep pycodestyle
pycodestyle==2.8.0

Does anyone have any idea what is going on? or encountered this?

Thank you!
Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
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: Anyone running F11 on a Dell mini ? (Or another mini ?)

2022-01-17 Thread fernsl kara
I thought GEEKOM mini PCs were higher-end equipment than Dell's.
https://www.geekompc.com
___
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: How to get Fedora 35 to use DNS name as hostname?

2022-01-17 Thread Tim via users
On Mon, 2022-01-17 at 08:42 +0100, Peter Boy wrote:
> The default configuration rather follows the opposite principle. The
> hostname should be well defined and independent of changing IP
> addresses.

I sort-of go along with that.  If you've set a hostname, there's sense
in it not getting changed.  On the other hand, if you use a DHCP server
to centrally manage the allocation of addresses, you might also want it
(or your DNS server) to control hostnames.  I do.  Some devices on my
network obey naming instructions from the DHCP &/or DNS servers, others
ignore it.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: How to get Fedora 35 to use DNS name as hostname?

2022-01-17 Thread Tim via users
On Sun, 2022-01-16 at 23:25 -0600, Thomas Cameron wrote:
> As a dirty hack, I created a file /etc/profile.d/hostname.sh:
> MYIP=`hostname -I`
> MYHOSTNAME=`host $MYIP | awk '{ print $NF }' | sed "s/\.$//"`
> echo $MYHOSTNAME > /etc/hostname
> hostnamectl hostname $MYHOSTNAME
> That sets the hostname correctly but it's a dirty hack in that it
> requires someone to actually log in to run the trigger the profile.d
> stuff. I am trying to find where in the dhclient stuff I should work
> to have the hostname set correctly from dhcp/dns resolution. It's
> frustrating that with F34 and F35, the systemd-hostnamed.service is
> supposed to do this but I'm not seeing where to make it do what I
> want it to. I've played with the
> /etc/NetworkManager/NetworkManager.conf file setting the hostname-
> mode=default in [main] but it's not working.

Any useful clues from these pages:
https://forum.manjaro.org/t/how-to-set-the-hostname-assigned-by-dhcp-server/35569/2
https://www.linuxsecrets.com/1675-configure-linux-to-broadcast-dhcp-client-hostname-in-linux
https://askubuntu.com/questions/104918/how-to-get-the-hostname-from-a-dhcp-server
https://www.google.com/search?q=fedora+dhcp+client+accepting+hostname+from+server
 

What we've been discussing is something I've often meant to get around
to doing, myself.  But I just persevere with manually adjusting a few
things, here.  I only have a small network, so it hasn't bugged me
sufficiently, yet.  And my brain is going on strike, at the moment
(migraine brain fog).  But the first link I supplied suggested simply
delete /etc/hostname

-- 
 
uname -rsvp
Linux 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


gnome-shell-extension-window-list

2022-01-17 Thread Winfried de Heiden

Hi all,

Sice a couple of days, the Gnome Shell Extension "Window List" seems 
broken; the icons are missing. Switching the extension off and on will 
make icons appear again. However, after opening a new application, the 
(new) icons is missing.


On https://gitlab.gnome.org/GNOME/gnome-shell-extensions someone is 
facing exactly the same problem.


Is someone aware of this problem?

Workaround available?

I cannot find a Bugzilla on this, so I will create one...

Winfried


___
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: gnome-shell-extension-window-list

2022-01-17 Thread Winfried de Heiden

And just created: https://bugzilla.redhat.com/show_bug.cgi?id=2041448


Hi all,

Sice a couple of days, the Gnome Shell Extension "Window List" seems 
broken; the icons are missing. Switching the extension off and on will 
make icons appear again. However, after opening a new application, the 
(new) icons is missing.


On https://gitlab.gnome.org/GNOME/gnome-shell-extensions someone is 
facing exactly the same problem.


Is someone aware of this problem?

Workaround available?

I cannot find a Bugzilla on this, so I will create one...

Winfried




___
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


Re: F35 - zram on auto install?

2022-01-17 Thread Robert Moskowitz



On 1/16/22 15:03, John Mellor wrote:

On 2022-01-16 11:53 a.m., Grumpey wrote:

Um, I did not know I set up zram?  How did that happen.  Is zram now
part of the basic Fedora install?

It has been a while my using zram.  How do I disable it for now? With
16GB real memory and 16GB real swap partition, I want to see how things
are working...

thanks

https://fedoraproject.org/wiki/Changes/SwapOnZRAM

Immediately:
sudo systemctl stop swap-create@zram0

Permanently:
sudo touch /etc/systemd/zram-generator.conf or sudo dnf remove
zram-generator-defaults


Asking the interesting question: Why would you want to ever do this?  
RAM is ~10x faster than SSD and 100x faster than spinning disk.  
Unless your system is so ancient and CPU-constrained that you are 
unable to afford the relatively low compression costs, making use of 
all available RAM at all times seems like a better move than stopping 
ZRAM swap.


For what it is worth

Prior to my memory upgrade, when I had only 8GB memory and Firefox just 
growing, I was seeing the following:


$ free
   total    used    free  shared buff/cache   
available

Mem: 7380668 6930852  262676    1492 187140  221144
Swap:   24157176    12044096    12113080

I did not know then about zram being the default, so I don't know how 
much of that 12GB swap was zram and how much was SSD.


But I can tell you that my system regularly 'hesitated' when I switched 
tasks.  I had real wait time before I could do something. And at times I 
would be typing and the system did not respond.  I had to wait a couple 
seconds before the screen was updated with whatever I was typing.  Now 
this is on a Lenovo x140e with an SSD drive, using Xfce; granted an 
older platform but quad-core.  Since the memory upgrade, there has been 
none of this hesitation.  And I am right now seeing:


free
   total    used    free  shared buff/cache   
available

Mem:    15625916    10489292  598484  183664 4538140 4617552
Swap:   25165816 512    25165304

zramctl
NAME   ALGORITHM DISKSIZE  DATA  COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lzo-rle 8G  496K 122.1K  380K   4 [SWAP]


this is after being running only 21hr. We will see how the system is 
doing in a few days, but swap was killing me.  Was it real SSD r/w or 
zram compression?

___
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: Making dnf install ssh:// work

2022-01-17 Thread Richard W.M. Jones
On Sun, Jan 16, 2022 at 04:57:34PM +, Michael Young wrote:
> On Sun, 16 Jan 2022, Richard W.M. Jones wrote:
> 
> >
> ># dnf install ssh://foo/tmp/bar.rpm
> >Last metadata expiration check: 0:00:41 ago on Sun 16 Jan 2022 09:21:19 GMT.
> >[MIRROR] bar.rpm: Curl error (1): Unsupported protocol for 
> >ssh://foo/tmp/bar.rpm [Protocol "ssh" not supported or disabled in libcurl]
> 
> Have you tried sftp://foo/tmp/bar.rpm ? curl at least seems to
> recognise the protocol.

Oh indeed that works!  Which is weird because sftp isn't
in the list at all :-)

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
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: ssd keeps dying??

2022-01-17 Thread Roger Heflin
On Sun, Jan 16, 2022 at 6:11 PM George N. White III  wrote:
>
> On Sun, 16 Jan 2022 at 16:32, Neal Becker  wrote:
>>
>> Well I guess I can try reseating it, good idea.
>> Unfortunately this server is remote from me, so might as well collect ideas 
>> before driving over.
>
>
> Have you seen: Fix your dead SSD with the power cycle method - The Silicon 
> Underground (dfarq.homeip.net
>
> I wonder if some workloads designed for rotating disks end up rewriting the 
> same storage
> location resulting in early death of SSD's

The ssd firmware plays games to make wear leveling work.  Because of
that it is very unlikely that 2 blocks written to the same "block" at
the fs level are going to be written to the same block on the ssd.

Make sure the SSD has some cache memory, I bought (and since returned)
a crucial ssd that did not have ram/cache.  I killed 2 of the (orig
and replacement) in under 2 weeks, before I returned it.  I killed
them such that they would no longer even answer on the sata bus.
However the firmware for these works, they seem to be a lot less
reliable.  And there are a lot of similar reviews that under some set
of conditions these devices are unreliable.Whatever algorithm
choices that a few dollars cheaper/no cache ram causes seems to be a
problem.

I have also been known to carefully and lightly use a pencil eraser on
the contacts to clean off anything that could cause it to not have a
good contact, and then wipe it with alcohol.
___
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: How to get Fedora 35 to use DNS name as hostname?

2022-01-17 Thread Sam Varshavchik

Peter Boy writes:

Usually you set the static hostname once using "hostnamectl set-hostname  
“.  „fedora“ is the transient hostname. DHCP client uses the static  
hostname to request an IP.


But maybe I didn't get what exactly you want to do.


dhcpd's configuration file uses MAC addresses to assign reserved IP  
addresses to specific DHCP clients. It doesn't matter what hostname the  
client sends.


I suppose that the DHCP server might keep track of hostnames and for MAC  
addresses that don't have fixed IP addresses it might use the client's  
hostname to keep leasing out the same IP address, if possible. But the same  
can be done with MAC address entirely, instead of hostnames, too.




pgpgXnXayua_B.pgp
Description: PGP signature
___
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: How to get Fedora 35 to use DNS name as hostname?

2022-01-17 Thread Peter Boy


> Am 17.01.2022 um 16:22 schrieb Sam Varshavchik :
> 
> Peter Boy writes:
> 
>> Usually you set the static hostname once using "hostnamectl set-hostname 
>> “.  „fedora“ is the transient hostname. DHCP client uses the static 
>> hostname to request an IP.
>> 
>> But maybe I didn't get what exactly you want to do.
> 
> dhcpd's configuration file uses MAC addresses to assign reserved IP addresses 
> to specific DHCP clients. It doesn't matter what hostname the client sends.

Yes, my wording was way too short. It uses the static hostname to enter the IP 
generated for the MAC address along with the hostname into the DNS part (in 
dnsmasq, which is used in Fedora KVM/libwirt) that is used to retrieve the 
hostname.

But Thomas uses a static host table, so the DNS delivered hostname is 
independent from any MAC address and any transient or static hostname of the 
client.   


> I suppose that the DHCP server might keep track of hostnames and for MAC 
> addresses that don't have fixed IP addresses it might use the client's 
> hostname to keep leasing out the same IP address, if possible. But the same 
> can be done with MAC address entirely, instead of hostnames, too.

At least dnsmasq does not, but relies on the MAC address alone.

Peter


___
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: Machine won't finish booting after update

2022-01-17 Thread stan via users
On Sun, 16 Jan 2022 21:07:29 -0500
Fulko Hew  wrote:

> I decided to log out and log back in to my X11 based KDE session just
> now, and I saw that 'Discover' was telling me I had updates available.
> So I said 'go ahead'.
> Eventually, it said I needed to reboot, so I did.
> After 4 (or 5) reboots that the machine drove itself through,
> the last reboot failed to start up to a GUI session.

Suspicious that this is not deterministic.  It should either fail
identically every time or restart every time (in my opinion).

> As a matter of fact, it dropped me down and told me it needed to
> enter an emergency boot
> and asked for my root password.
> The message also told me to look at 'journalctl -xb'
> After a few thousand lines of info, I saw nothing of significance
> other than it hadn't finished.

You could try 
journalctl -rxb
so that the last messages are presented first.  It is likely that that
is where the error will be.

> The other suggestion was 'systemctl default'.
> That resulted in the following:
> 
> Failed to mount /boot/efi
> Dependency failed for Local File System
> Dependency failed for Mark the need to relabel after reboot
> Failed to mount RPC File System
> Dependency failed for rpc-pipefs.target
> Dependency failed for RPC security service for NFS client and server
> Failed to start Load Kernel Modules
> Failed to mount Arbitrary Executable File Formats File System
> Failed to mount Arbitrary Executable File Formats File System
> Failed to mount Arbitrary Executable File Formats File System
> Failed to mount Arbitrary Executable File Formats File System
> Failed to mount Arbitrary Executable File Formats File System
> Failed to start Set Up Additional Binary Formats
> 
> ... and then nothing.  I had to cold start

It seems like a hardware error to me from the symptoms.  How can the
kernel not mount /boot/efi unless the drive has either power issues or
seek errors / bad sectors.  This is really basic.

> and that brings me back to the same issues.
> Trying to reboot a previous kernel doesn't even result in any boot
> messages.
> 
> I now have a 'non-working' machine.
> Suggestions are welcome (and needed)!

Long shots.

It might be software, but it could be just a coincidence that it chose
this time for a hardware error to expose itself.

Do you have a list of what was updated?  It would be good to see if
there are any updates that might have caused this to happen via
software.  I'm not sure what would stop /boot/efi from being mounted.

Did you power down completely at any point?  That will allow components
to lose any retained state.

You could, while completely powered down, try reseating internal
components, especially drive connectors.

If you can reach the BIOS menu, look at the power supply numbers.  Are
they at or near spec?

Can you boot a livecd / usb so you can do checks of the drives to see
if they are still functioning properly, maybe a smartctl (smartctl -a
/dev/[drive designation])? If a live image boots and runs, it will
indicate that your memory is (probably) not the issue as well.
___
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: How to get Fedora 35 to use DNS name as hostname?

2022-01-17 Thread Sam Varshavchik

Peter Boy writes:


> Am 17.01.2022 um 16:22 schrieb Sam Varshavchik :
>
> Peter Boy writes:
>
>> Usually you set the static hostname once using "hostnamectl set-hostname  
“.  „fedora“ is the transient hostname. DHCP client uses the static  
hostname to request an IP.

>>
>> But maybe I didn't get what exactly you want to do.
>
> dhcpd's configuration file uses MAC addresses to assign reserved IP  
addresses to specific DHCP clients. It doesn't matter what hostname the  
client sends.


Yes, my wording was way too short. It uses the static hostname to enter the  
IP generated for the MAC address along with the hostname into the DNS part  
(in dnsmasq, which is used in Fedora KVM/libwirt) that is used to retrieve  
the hostname.


Ok, so this is basically trusted DDNS stacked on top of DHCP.

But Thomas uses a static host table, so the DNS delivered hostname is  
independent from any MAC address and any transient or static hostname of the  
client.


It should be possible to hack up a script that gets run when an IP address  
is assigned that does a reverse IP lookup and sets the hostname. However  
that should be done in a manner that does not permanently save the hostname  
so that it gets reverted to a static stub name on the next reboot.




pgp8y8nbhsECP.pgp
Description: PGP signature
___
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: How to get Fedora 35 to use DNS name as hostname?

2022-01-17 Thread Petr Menšík

On 1/17/22 11:27, Tim via users wrote:
> On Mon, 2022-01-17 at 08:42 +0100, Peter Boy wrote:
>> The default configuration rather follows the opposite principle. The
>> hostname should be well defined and independent of changing IP
>> addresses.
> I sort-of go along with that.  If you've set a hostname, there's sense
> in it not getting changed.  On the other hand, if you use a DHCP server
> to centrally manage the allocation of addresses, you might also want it
> (or your DNS server) to control hostnames.  I do.  Some devices on my
> network obey naming instructions from the DHCP &/or DNS servers, others
> ignore it.
>  

I think it might make more sense to correctly detect hostname during
installation. If you define hostname on installation from network, it
should be kept. I expect it should keep the same hostname during
reboots. I think only diskless terminals may want always obtaining
hostname on every boot. Anything storing state on local disk should want
to keep its name.

I think more tight integration with libvirt names would be useful. I
admit I know little of that. I usually define name AFTER installation
for my VMs, which would not work with what I propose. I would like easy
way to set hostname from libvirt during installation. I don't need
always fixed IP, but I want fixed DNS name for given VM. I expect that
is common requirement.

dnsmasq from libvirt would provide hostname to machine in case it has
static lease for given DUID/hwaddr. Is there tool to create static lease
from machine name on VM creation? For example libvirt can detect name of
distribution from ISO image. It would be nice if it could propagate it
forward.

I am afraid I did not help much.

Regards,
Petr

-- 
Petr Menšík
Software Engineer
Red Hat, http://www.redhat.com/
email: pemen...@redhat.com
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
___
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: F35 - zram on auto install?

2022-01-17 Thread Robert Moskowitz



On 1/16/22 15:03, John Mellor wrote:

On 2022-01-16 11:53 a.m., Grumpey wrote:

Um, I did not know I set up zram?  How did that happen.  Is zram now
part of the basic Fedora install?

It has been a while my using zram.  How do I disable it for now? With
16GB real memory and 16GB real swap partition, I want to see how things
are working...

thanks

https://fedoraproject.org/wiki/Changes/SwapOnZRAM

Immediately:
sudo systemctl stop swap-create@zram0

Permanently:
sudo touch /etc/systemd/zram-generator.conf or sudo dnf remove
zram-generator-defaults


Asking the interesting question: Why would you want to ever do this?  
RAM is ~10x faster than SSD and 100x faster than spinning disk.  
Unless your system is so ancient and CPU-constrained that you are 
unable to afford the relatively low compression costs, making use of 
all available RAM at all times seems like a better move than stopping 
ZRAM swap.


For what it is worth

Prior to my memory upgrade, when I had only 8GB memory and Firefox just 
growing, I was seeing the following:


$ free
   total    used    free  shared buff/cache   
available

Mem: 7380668 6930852  262676    1492 187140  221144
Swap:   24157176    12044096    12113080

I did not know then about zram being the default, so I don't know how 
much of that 12GB swap was zram and how much was SSD.


But I can tell you that my system regularly 'hesitated' when I switched 
tasks.  I had real wait time before I could do something. And at times I 
would be typing and the system did not respond.  I had to wait a couple 
seconds before the screen was updated with whatever I was typing.  Now 
this is on a Lenovo x140e with an SSD drive, using Xfce; granted an 
older platform but quad-core.  Since the memory upgrade, there has been 
none of this hesitation.  And I am right now seeing:


free
   total    used    free  shared buff/cache   
available

Mem:    15625916    10489292  598484  183664 4538140 4617552
Swap:   25165816 512    25165304

zramctl
NAME   ALGORITHM DISKSIZE  DATA  COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lzo-rle 8G  496K 122.1K  380K   4 [SWAP]


this is after being running only 21hr. We will see how the system is 
doing in a few days, but swap was killing me.  Was it real SSD r/w or 
zram compression?

___
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


fttconv2

2022-01-17 Thread Patrick Dupre
Hello,

I get the following error:

error: feval: function 'fftconv2' not found

octave-image provide fftconv2.m

can I use it? If yes, How?

Thanks

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988| | Room# D114A
===
___
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: Machine won't finish booting after update

2022-01-17 Thread Fulko Hew
On Mon, Jan 17, 2022 at 2:00 PM stan via users <
users@lists.fedoraproject.org> wrote:

> On Sun, 16 Jan 2022 21:07:29 -0500
> Fulko Hew  wrote:
>
> > I decided to log out and log back in to my X11 based KDE session just
> > now, and I saw that 'Discover' was telling me I had updates available.
> > So I said 'go ahead'.
> > Eventually, it said I needed to reboot, so I did.
> > After 4 (or 5) reboots that the machine drove itself through,
> > the last reboot failed to start up to a GUI session.
>
> Suspicious that this is not deterministic.  It should either fail
> identically every time or restart every time (in my opinion).
>

I don't think you understand what I was saying.
The update process that 'Discover' performed was 'strange' to me.
For the last 20 years, I've used rpm, yum and dnf to download and
install updates, and if I wanted... I'd reboot to use any new kernel
that may have been updated.

This time I chose to use 'Discover', because (for a change) it actually
told me there was new stuff.  (I'm getting the feeling that 'discover' only
runs at
login time.  Something I do only once every few months.  ie. at every power
failure.)

So after 'discover' downloaded and (apparently) updated everything, it
asked me
to reboot.  So I used discover's reboot button to proceed.  During the first
reboot cycle I watched the boot messages go by, and I saw words to the
effect
that it was doing some post reboot additional updates.  It finished them
and then
said it was rebooting.

On that next boot, I watched again, while it talked about other updates it
needed to do,
and... and another reboot.

After the n'th reboot, I no longer saw any 'installing' activity, and it
went all the
way through and then ... nothing.  No more boot messages, and no GUI either.

So I DID do a cold reboot and then it went through the standard boot
messages
until those errors I mentioned and it dropped me into that emergency boot
prompt.


> As a matter of fact, it dropped me down and told me it needed to
> > enter an emergency boot
> > and asked for my root password.
> > The message also told me to look at 'journalctl -xb'
> > After a few thousand lines of info, I saw nothing of significance
> > other than it hadn't finished.
>
> You could try
> journalctl -rxb
> so that the last messages are presented first.  It is likely that that
> is where the error will be.
>

journalctl -xb gave me those error messages I provided.
So yes, the first error was that it couldn't mount /boot/efi.


> The other suggestion was 'systemctl default'.
> > That resulted in the following:
> >
> > Failed to mount /boot/efi
> > Dependency failed for Local File System
> > Dependency failed for Mark the need to relabel after reboot
> > Failed to mount RPC File System
> > Dependency failed for rpc-pipefs.target
> > Dependency failed for RPC security service for NFS client and server
> > Failed to start Load Kernel Modules
> > Failed to mount Arbitrary Executable File Formats File System
> > Failed to mount Arbitrary Executable File Formats File System
> > Failed to mount Arbitrary Executable File Formats File System
> > Failed to mount Arbitrary Executable File Formats File System
> > Failed to mount Arbitrary Executable File Formats File System
> > Failed to start Set Up Additional Binary Formats
> >
> > ... and then nothing.  I had to cold start
>
> It seems like a hardware error to me from the symptoms.  How can the
> kernel not mount /boot/efi unless the drive has either power issues or
> seek errors / bad sectors.  This is really basic.
>


I read other postings that people have had issues with missing VFAT
support in their kernel, that's needed to mount that filesystem.

> and that brings me back to the same issues.
> > Trying to reboot a previous kernel doesn't even result in any boot
> > messages.
> >
> > I now have a 'non-working' machine.
> > Suggestions are welcome (and needed)!
>
> Long shots.
>
> It might be software, but it could be just a coincidence that it chose
> this time for a hardware error to expose itself.
>
> Do you have a list of what was updated?  It would be good to see if
> there are any updates that might have caused this to happen via
> software.  I'm not sure what would stop /boot/efi from being mounted.
>


Sadly I don't have that list.  There were about 60 components
including the kernel that were updated.

Did you power down completely at any point?  That will allow components
> to lose any retained state.
>
> You could, while completely powered down, try reseating internal
> components, especially drive connectors.
>
> If you can reach the BIOS menu, look at the power supply numbers.  Are
> they at or near spec?
>
> Can you boot a livecd / usb so you can do checks of the drives to see
> if they are still functioning properly, maybe a smartctl (smartctl -a
> /dev/[drive designation])? If a live image boots and runs, it will
> indicate that your memory is (probably) not the issue as well.
>


After a lot of experimentation, I did get

Re: kdevelop:: pycodestyle not found

2022-01-17 Thread Samuel Sieb

On 1/17/22 01:55, Adrian Sevcenco wrote:

but i have both:
root@hal: ~ # rpm -qa | grep pycodestyle
python3-pycodestyle-2.7.0-2.fc35.noarch

and user side installation:
pip3 freeze | grep pycodestyle
pycodestyle==2.8.0


That's certainly a big potential for trouble.
___
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: Machine won't finish booting after update

2022-01-17 Thread Joe Zeff

On 1/17/22 11:59 AM, stan via users wrote:

Suspicious that this is not deterministic.  It should either fail
identically every time or restart every time (in my opinion).


If it's really nnondeterministic, it's what's called a mandelbug.
___
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: Machine won't finish booting after update

2022-01-17 Thread Fulko Hew
On Mon, Jan 17, 2022 at 6:06 PM Joe Zeff  wrote:

> On 1/17/22 11:59 AM, stan via users wrote:
> > Suspicious that this is not deterministic.  It should either fail
> > identically every time or restart every time (in my opinion).
>
> If it's really nnondeterministic, it's what's called a mandelbug.
>

When booting the new kernel, it fails the same way every time.
Very deterministic.

mount: /boot/efi: unknown filesystem type 'vfat'.

What I don't remember is what this multi-stage install-reboot was trying to
accomplish.
Looking back in messages or journalctl, I don't see anything.
But it was doing something explicitly.
___
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: Machine won't finish booting after update

2022-01-17 Thread Joe Zeff

On 1/17/22 6:31 PM, Fulko Hew wrote:
What I don't remember is what this multi-stage install-reboot was trying 
to accomplish.

Looking back in messages or journalctl, I don't see anything.
But it was doing something explicitly.



If you were installing something, try dnf history.
___
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