Re: Need system to run 24/7

[Robert McBroom via users]

On 5/25/24 11:25, Robert McBroom via users wrote:


On 5/25/24 8:39 AM, Patrick O'Callaghan wrote:

On Sat, 2024-05-25 at 07:51 -0400, Robert McBroom via users wrote:

On 5/25/24 4:01 AM, Barry wrote:

On 24 May 2024, at 22:47, Michael D. Setzer II via users
 wrote:

Seems it was related to Lenova wanting to get
some kind of higher power saving rating with Linux?? Don't know
why they made it the default settings.

I recall the default of suspend after 15 mins is a legal/regulatory
driven change.

The owner has to opt into keeping a device on by turning off the
power saving defaults.

Barry

None of the various desktop powers setting menus that I could find
showed such an option.

I use KDE, where the various options are under the Power menu in
Settings. I've never had the system power down autonomously.


Finally found the setting for "do nothing"
--

Then the system went to sleep
--
___
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: Need system to run 24/7

[Robert McBroom via users]

On 5/25/24 8:39 AM, Patrick O'Callaghan wrote:

On Sat, 2024-05-25 at 07:51 -0400, Robert McBroom via users wrote:

On 5/25/24 4:01 AM, Barry wrote:

On 24 May 2024, at 22:47, Michael D. Setzer II via users
 wrote:

Seems it was related to Lenova wanting to get
some kind of higher power saving rating with Linux?? Don't know
why they made it the default settings.

I recall the default of suspend after 15 mins is a legal/regulatory
driven change.

The owner has to opt into keeping a device on by turning off the
power saving defaults.

Barry

None of the various desktop powers setting menus that I could find
showed such an option.

I use KDE, where the various options are under the Power menu in
Settings. I've never had the system power down autonomously.


Finally found the setting for "do nothing"
--
___
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: Need system to run 24/7

[Robert McBroom via users]

On 5/25/24 4:01 AM, Barry wrote:



On 24 May 2024, at 22:47, Michael D. Setzer II via users 
 wrote:

Seems it was related to Lenova wanting to get
some kind of higher power saving rating with Linux?? Don't know
why they made it the default settings.

I recall the default of suspend after 15 mins is a legal/regulatory driven 
change.

The owner has to opt into keeping a device on by turning off the power saving 
defaults.

Barry
None of the various desktop powers setting menus that I could find 
showed such an option.

--
___
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: Need system to run 24/7

[Robert McBroom via users]

On 5/24/24 11:57 PM, Tim via users wrote:

On Thu, 2024-05-23 at 18:37 -0400, Robert McBroom via users wrote:

This thread has been on before but I lost it. I need my system to run
long simulations without my intervention. It keeps going to a reboot
intermittently.  The program has recovery that all is not lost with a
shutdown but the time getting back to check on the system.  Don't
remember the setting to tell fedora what to do for always on systems.

There's some info about systems suspending after a certain amount of
(perhaps ill-conceived ideas of) idleness:

https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801

But if it's rebooting rather than simply shutting down, I wonder if
something is crashing?
Quirk of multi os system. Windows is first in the boot/efi list so a 
restore from sleep starts windows not any of the linux systems

--
___
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: Need system to run 24/7

[Robert McBroom via users]

Thanks Michael, those changes to sleep.conf seem to have done the trick
--
___
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: 2 installations on the same PC - Add partition in Ftab

[Robert McBroom via users]

On 5/24/24 5:23 AM, Patrick O'Callaghan wrote:

On Thu, 2024-05-23 at 19:43 -0300, soles.g wrote:

I did two installations of Fedora40
on the same hard drive.


¿Esto fue a propósito o por error? No está claro para qué necesitas dos
instalaciones de F40.

Was this on purpose or by mistake? It's not clear why you would need
two installations of F40.


I didn't know how to do it
so you don't have to create
in each of the facilities
the directory? /efi.


Lo usual es tener una sola partición EFI (la cual no está dentro de
Fedora sino es accesible desde el BIOS. El comando efibootmanager te
permite configurar las opciones. No hace falta montarla en Fedora
porque dicho comando lo manipula directamente. Puedes especificar el
disco duro a usar.

The usual setup is to have one EFI partition (not a Fedora
directory). You can use the efibootmanager command to change
options. You don't need to mount the EFI in Fedora as the command
accesses it directly. You can specify which hard drive it should
use.


├─sda1 vfat FAT16 EFI 0B9B-8F19

├─sda8 vfat FAT32 boot 0566-61F4
/dev/sda8: LABEL_FATBOOT="boot" LABEL="boot" UUID="0533-61F4"
BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="
EFI System Partition" PARTUUID="916a4cb1-8f50-42c7-92be-dc53d80a4bdb"

So when the machine starts up it tells me something about two
'journal'... I don't know what...


No está claro si puedes usar el sistema o no, pero en caso que sí
sugeriría deshabilitar el boot de una de las particiones usando el
efibootmanager.

It's unclear if you have a working system, but if so I'd suggest
disabling one of the boot partitions using efibootmanager,

Two installations of Fedora can be run on the same system With each 
installation on a separate drive. The installation to be executed can 
then be started from the bios. The partitions /boot/efi, /boot and /root 
are all unique to the installation. Can even include Windows.

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

Need system to run 24/7

[Robert McBroom via users]

This thread has been on before but I lost it. I need my system to run 
long simulations without my intervention. It keeps going to a reboot 
intermittently.  The program has recovery that all is not lost with a 
shutdown but the time getting back to check on the system.  Don't 
remember the setting to tell fedora what to do for always on systems.


--
___
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: MS Bitlocker Blue Screen on Reboot

[Robert McBroom via users]

On 5/21/24 8:38 AM, George N. White III wrote:

On Mon, May 20, 2024 at 6:47 PM Tim Evans  wrote:

[...]

.Does Fedora
re-package vendor firmware updates? Will give your suggestion a
try when
I have a chance.


Fedora has `fwdupd` to install vendor firmware updates. Use fwupdtool 
to check for
available updates.   Documentation for fwupd is minimal, but man 
fwupdtool should
get you going if your vendor (a) participates in the program and (b) 
supports linux
for your model.  Some vendors provide firmware updates using bootable 
USB key images.

--
George N. White III

dnf whatprovides fwdupd
Fedora 40 - x86_64 
3.1 
MB/s | 3.8 MB 00:01
Fedora 40 - x86_64 - Updates 
   11 MB/s | 
 23 MB 00:02
Error: No matches found. If searching for a file, try specifying the 
full path or using a wildcard prefix ("*/") at the

beginning.

dnf whatprovides fwdupdtool
Last metadata expiration check: 0:01:34 ago on Wed 22 May 2024 12:53:42 
AM EDT.
Error: No matches found. If searching for a file, try specifying the 
full path or using a wildcard prefix ("*/") at the

beginning.

--
___
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: What is Castor ? Att.Jonathan Billings.

[Robert McBroom via users]

On 5/11/24 08:36, John Pilkington wrote:

On 10/05/2024 15:51, John Pilkington wrote:

On 10/05/2024 15:00, George N. White III wrote:
On Wed, May 8, 2024 at 5:13 PM John Pilkington 
mailto:johnpilk...@gmail.com>> wrote:


    On 08/05/2024 20:13, Samuel Sieb wrote:
 > On 5/8/24 10:50 AM, John Pilkington wrote:
 >> The harware was working well, before my recent upgrades from 
f38,

 >> briefly to f39 and now to f40.  Then I was using the rpmfusion
    470xx
 >> builds of the nvidia legacy drivers.   Now the dual-boot box 
has no

 >> nvidia or nouveau rpms installed  (rpm -qa) although I suppose
    bits of
 >> config might remain;  inxi still finds nvidia traces:
 >
 > Nouveau is included with the kernel, it doesn't have its own 
package.


    xorg-x11-drv-nouveau is supplied by fedora, but I was told that the
    kernel driver was more up to date, so I removed the fformer.


I have a late 2012 iMac with Nvidia that was using 470xx.  I mostly 
use nouveau

with wayland, but do have xorg-x11-drv-nouveau.

There were issues with 470xx failing to build in F40 with the akmods 
install from
rpmfusion, but now there is a testing version that does install.  
Some users have
success with the Nvidia installer. I have the rpmfusion-testing 
package installed

but haven't had time to test it.  I don't think it supports Wayland.



Thanks for your comment.  I posted later, in this thread but with a 
subject-line change. It does show in HyperKitty and I've put a link 
to it on the rpmfusion list.


I have just updated that, re the dual-boot box.  See below:

I have removed all nouveau packages and installed all *470xx" 
packages, which installed the new versions.  That gave HDMI and vga 
screens with their expected resolutions but essentially no user 
interactivity because active kwin_wayland runs all cpus at full 
throttle. Perhaps that's 'not supported'.


Ctrl/Alt/F3 still works, and I have 6.8.9 now.  That complained that 
there was "no space on /boot/efi/EFI/Linux/Fedora " (200 MB) but 
seems to run (with the same cpu runaway) after I deleted several f39 
files.


I hope this doesn't offend any 'religious' beliefs.  Installing

plasma-workspace-x11

(in the updates repo but NOT supported by the Fedora KDE SIG)

and selecting "Desktop Session: Plasma (X11)" in the login screen, has 
apparently restored this system to a usable state.  At present 
password entry still has a sluggish keyboard.



The single-boot box is still running nouveau.


Same experience here with a gt710. Mouse action in wayland is very 
hesitant. Still on X11.


--
___
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: Any clue what I did to nouveau?

[Robert McBroom via users]

On 5/6/24 1:14 PM, Tom Horsley wrote:

This is just curiosity since I fixed it by installing nvidia drivers
from rpmfusion, but here's what happened:

When I installed fedora 40 workstation, I saw that the nouveau drivers
(for the first time in years) had correctly decided to run at the
native 3840x2160 resolution of the TV I use as a monitor. I figured
I'd give them a chance this time.

I installed a bazillion or so packages (OK 4400 :-) to get the new
f40 to have the same packages as f39.

The next time I rebooted into fedora40, nouveau was now insisting
that 800x600 and 1024x768 were the only two resolutions available.
Any idea what I might have installed to make nouveau forget how
to support the proper screen resolution?

Whatever it was has no effect on nvidia, installing nvidia and
rebooting got me back to 3840x2160 with no other actions required
by me.
After a long while rpmfusion now has drivers for NVIDIA for the 6.8 
kernels, I use the 360 and 470 drivers

--
___
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 messages from DNF

[Robert McBroom via users]

The last update had something happen.  What is happening with dracut? 
Anyone see such?


88x2bu.ko.xz:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.8.8-300.fc40.x86_64/extra/
depmod.
dkms autoinstall on 6.8.8-300.fc40.x86_64/x86_64 succeeded for 8812au 88x2bu
dkms: autoinstall for kernel 6.8.8-300.fc40.x86_64 Done.
dracut-install: ERROR: installing '/etc/fcoe/cfg-*'
dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D 
/var/tmp/dracut.S7Deba/initramfs -a /etc/fcoe/cfg-*

dkms: running auto installation service for kernel 6.8.8-300.fc40.x86_64
dkms: autoinstall for kernel 6.8.8-300.fc40.x86_64 Done.

  Running scriptlet: selinux-policy-targeted-40.17-1.fc40.noarch 137/137
  Running scriptlet: kernel-modules-6.8.8-300.fc40.x86_64 137/137
  Running scriptlet: passt-selinux-0^20240426.gd03c4e2-1.fc40.noarch 
137/137

  Running scriptlet: swtpm-selinux-0.8.1-7.fc40.noarch 137/137
  Running scriptlet: ed-1.20.1-1.fc40.x86_64 137/137
Creating group 'gnome-remote-desktop' with GID 959.
Creating user 'gnome-remote-desktop' (GNOME Remote Desktop) with UID 959 
and GID 959.

Creating group 'passim' with GID 958.
Creating user 'passim' (Local Caching Server) with UID 958 and GID 958.
Failed to add existing group "input" to temporary group file: Invalid 
argument


/usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:2: Failed to 
resolve user 'gnome-remote-desktop': No such process
/usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:3: Failed to 
resolve user 'gnome-remote-desktop': No such process
/usr/lib/tmpfiles.d/sphinx.conf:1: Failed to resolve user 'sphinx': No 
such process


I don't use gnome
--
___
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 - KeePass fails to run

[Robert McBroom via users]

On 4/28/24 10:41 PM, John List wrote:
Thanks.  I just looked at the other versions to see how they differ.  
They are forks off the original.  I prefer to stay with the main one.  
I did open a bug and they traced it to "Confirmed this is caused by 
zlib-ng migration.".  I am not sure when it will get fixed.  It is an 
inconvenience to me as all of my passwords are in the application.  
But my machine is dual boot.  So I was able to copy my vault over to 
windows and retrieve my passwords there.


It was running fine on all the pre-release updates to f40.  The last 
updates with the release broke keepass

--
___
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 - KeePass fails to run

[Robert McBroom via users]

On 4/25/24 10:11, John List wrote:

Hi,

Just an FYI that KeePass is failing to run on my recently upgraded 
Fedora 40 machine.  I'm not sure of the correct place to report the issue.


image.png


Run the zipped keepass with mono with no problems.--
___
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: how long does dnf system-upgrade take?

[Robert McBroom via users]

On 4/14/24 14:20, Tim via users wrote:

On Sun, 2024-04-14 at 09:49 -0400, Fulko Hew wrote:

Then in corporate life, I needed to ensure a stable development
environment.

This is one of the big problems with computers in the work place.  You
may have single-task computers which you want to work, and not mess
around with.  You may have a need for particular jobs that will always
work in a certain way.  Things in development can take ages to
complete, and that's just sorting out your own needs, never mind having
to deal with a system changing as well.  System updates can pull the
rug out from under you.

Computer systems with long life spans are essential in such
environments, things that require replacing every 6 months or so are a
real nuisance (to put it mildly).

Let's be clear, we're not talking about annoying changes to how the
desktop looks, that can be put up with.  But when you find essential
software and/or hardware doesn't work anymore, or doesn't exist
anymore, and support libraries are incompatible, that's a deal-breaker.

It's a part of the reasons Linux gets minimal support with hardware
(printers, graphics cards, scanners, whatever).  Those manufacturers
don't want to be dealing with ever-changing infrastructure where
someone else is making all these changes.  And there's every chance
that by the time they've developed their gadget and software for it, a
Linux distro has changed OSs twice.


After F33, it became an issue that I didn't want to migrate because
I'd typically be losing functionality or user-convenience.

During F33 to 34/35 migration I remember losing all of my KiCad
customizations for chips and connectors I had downloaded.
During this F35 to F39 migration, I've lost the convenience of a
Fedora supported FreeCAD.

Addressing an issue someone else replied with:  While one can try
installing old software onto new systems, you often find it cannot be
installed or run.  It's not compatible.

Even the newer idea of the big-blob appimage (and their ilk) that's
mostly self-contained without relying (much) on system libraries, and
one blob is supposed to work on various different distros can fail to
work on different versions of an OS.

So yes, change is a pain.  In certain environments computers will never
get updates.  Once it's working, they'll keep it in that condition.
It's not a problem with non-networked systems, but risky with networked
ones.

I have a very old Mac in that boat (changes stuffed things up).  It's
used for video editing with Final Cut Pro, and that's its sole task.  I
kept updating for a while, but it can't be any more.  They limit the
newest OS you can put on it.  And somewhere along the way, one of the
Final Cut Pro updates became very crashy, and no further updates fixed
that issue, and it wasn't possible to go back to a prior version that
was stable.


P.S. And with every upgrade, software just gets slower.

I certainly noticed that with Windows.  They seemed to just cobble
patch upon patch, rather than replace borked things with working ones.

I can't say I've *directly* encountered upgrade slowdowns with Linux
software.  Though I have in the sense that Gnome and KDE developers
seem to think everyone has a PC with an insanely powerful graphics card
and oodles of RAM to just run the desktop.  I don't care about the damn
desktop, it's applications I want to use.


Real problem for scientific systems. Scientific Linux that was going to 
provide some stability died. CERN is trying to roll their own version of 
CENTOS 8,9 since its promise of more stability was moot. Seen many 
instances of measurement hardware dependent on systems that passed away, 
OS/2. Now we are being told that our cars will die when the software is 
unavailable!

--
___
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 is available

[Robert McBroom via users]

On 4/24/24 22:48, Jeffrey Walton wrote:
It looks like Fedora 40 just dropped! Upgrade instructions at 
.


RPMFushion folks should wait about a month before upgrading. There 
always seems to be a lot of video problems after a new release while 
RPMFusion is rebuilding their packages.


NVIDIA drivers came out with the release. Also for the 6.8 kernels on 
Fedora 39. Been quite a wait from 6.8.0 to 6.8.7 but now here.

--
___
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: Failed to find a suitable stage1 device

[Robert McBroom via users]

On 4/3/24 5:45 PM, Stephen Morris wrote:

On 4/4/24 00:50, Michael Hennebry wrote:

On Tue, 2 Apr 2024, Samuel Sieb wrote:

The efi partition probably needs to be bigger than that, but it also 
has to be mounted at /boot/efi as indicated.


Ah!  With custom partitioning,
anaconda needs to be explicitly told
the EFI partition is the EFI partition.
Anaconda needs to have all the partitions you are going to install to 
mounted and to be told what the partition format is, hence you would 
need to tell anaconda to mount the efi partition as /boot/efi and its 
format is efi. Having done that don't specify to format that partition 
as with Windows installed, Windows is potentially also using that 
partition as its efi partition.


regards,
Steve


Fedora and Windows can share an EFI partition with no difficulties
--
___
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: libvirtd.service start

[Robert McBroom via users]

On 3/22/24 6:30 AM, Barry Scott wrote:



On 22 Mar 2024, at 00:54, Robert McBroom via users 
 wrote:


looking at the status it shows preset:disabled


As I understand it preset is used somewhere in the initial 
installation of fedora to figure
out which services should be enabled by default. After installation 
it's not used normally.


As a user you can symlink services into the right place in 
/etc/systemd/system or use

the systemctl enable/disable commands to do the symlinking for you.

I don't see any entry for libvirtd in /etc/systemd/system after having 
started it. There is an entry in 
/etc/systemd/system/multi-user.target.wants pointing to 
/usr/lib/systemd/system/libvirtd.service which looks unchanged.


What symlink would be expected?

After a system boot


[  ~]# systemctl status libvirtd
○ libvirtd.service - libvirt legacy monolithic daemon
 Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
preset: disabled)

    Drop-In: /usr/lib/systemd/system/service.d
 └─10-timeout-abort.conf
 Active: inactive (dead)
TriggeredBy: ○ libvirtd-ro.socket
 ○ libvirtd.socket
 ○ libvirtd-admin.socket
   Docs: man:libvirtd(8)
https://libvirt.org/
[  ~]# systemctl start libvirtd
[  ~]# systemctl status libvirtd
● libvirtd.service - libvirt legacy monolithic daemon
 Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
preset: disabled)

    Drop-In: /usr/lib/systemd/system/service.d
 └─10-timeout-abort.conf
 Active: active (running) since Sat 2024-03-23 13:06:24 EDT; 7s ago
TriggeredBy: ● libvirtd-ro.socket
 ● libvirtd.socket
 ● libvirtd-admin.socket
   Docs: man:libvirtd(8)
https://libvirt.org/
   Main PID: 10683 (libvirtd)
  Tasks: 20 (limit: 32768)
 Memory: 42.1M (peak: 42.7M)
    CPU: 500ms
 CGroup: /system.slice/libvirtd.service
 └─10683 /usr/sbin/libvirtd --timeout 120

Mar 23 13:06:23 HPZ440.attlocal.net systemd[1]: Starting 
libvirtd.service - libvirt legacy monolithic daemon...
Mar 23 13:06:24 HPZ440.attlocal.net systemd[1]: Started libvirtd.service 
- libvirt legacy monolithic daemon.
--
___
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: libvirtd.service start

[Robert McBroom via users]

On 3/21/24 4:51 PM, Samuel Sieb wrote:

On 3/21/24 12:20, Robert McBroom via users wrote:


On 3/20/24 10:32 AM, Jerry James wrote:

On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users
  wrote:

Recently libvirtd.service is not starting on boot. I have to manually
start it with systemctl start libvirtd.

Do I need to put that command in a startup script?

libvirtd.service is socket activated, so it should run automatically
when needed.  Does something not work if you don't start it manually?


virt- manager starts but says it cannot connect to anything. I have 
six virtual machines I use for various purposes.


systemctl status libvirtd

shows disabled and dead. After starting it manually all machines are 
present.


Status then shows

systemctl status libvirtd
●libvirtd.service - libvirt legacy monolithic daemon
 Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; 
enabled; preset: disabled)


Thought

systemctl enable libvirtd

would change the preset notation but it didn't


It doesn't.  That's the system preset.  "enable" only changes the 
first enabled/disable option, but that overrides the preset, so it 
should be starting at boot if you've rebooted since changing that 
setting.


You can use "journalctl -b -u libvirtd" to find out what has happened.
--


Saw no indication that any setting had changed.

Nothing from the journal tells anything that I understand

# journalctl -b -u libvirtd
Mar 21 09:31:17 HPZ440.attlocal.net systemd[1]: Starting 
libvirtd.service - libvirt legacy monolithic daemon...
Mar 21 09:31:18 HPZ440.attlocal.net systemd[1]: Started libvirtd.service 
- libvirt legacy monolithic daemon.
Mar 21 09:33:18 HPZ440.attlocal.net systemd[1]: libvirtd.service: 
Deactivated successfully.
Mar 21 09:56:36 HPZ440.attlocal.net systemd[1]: Starting 
libvirtd.service - libvirt legacy monolithic daemon...
Mar 21 09:56:36 HPZ440.attlocal.net systemd[1]: Started libvirtd.service 
- libvirt legacy monolithic daemon.
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: libvirt version: 
10.1.0, package: 1.fc40 (Fedora Project, 2024-03-01-18:35:13, )
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: hostname: 
HPZ440.attlocal.net
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-alpha for probing: 
/usr/bin/qemu-system-alpha: error while l>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-alpha: internal error: Failed to 
start QEMU binary /usr/bin/qemu-system>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-arm for probing: 
/usr/bin/qemu-system-arm: error while loadi>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-arm: internal error: Failed to 
start QEMU binary /usr/bin/qemu-system-a>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-arm for probing: 
/usr/bin/qemu-system-arm: error while loadi>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-arm: internal error: Failed to 
start QEMU binary /usr/bin/qemu-system-a>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-aarch64 for probing: 
/usr/bin/qemu-system-aarch64: error whi>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-aarch64: internal error: Failed to 
start QEMU binary /usr/bin/qemu-syst>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-cris for probing: 
/usr/bin/qemu-system-cris: error while loa>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-cris: internal error: Failed to 
start QEMU binary /usr/bin/qemu-system->
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-lm32 for probing: 
/usr/bin/qemu-system-lm32: error while loa>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-lm32: internal error: Failed to 
start QEMU binary /usr/bin/qemu-system->
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-m68k for probing: 
/usr/bin/qemu-system-m68k: error while loa>
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-m68k: internal error: Failed to 
start QEMU binary /usr/bin/qemu-system->
Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu-system-microblaze for probing: 
/usr/bin/qemu-system-microblaze: err>
Mar

Re: libvirtd.service start

[Robert McBroom via users]

On 3/21/24 4:29 PM, Jerry James wrote:

On Thu, Mar 21, 2024 at 1:20 PM Robert McBroom via users
 wrote:

virt- manager starts but says it cannot connect to anything. I have six virtual 
machines I use for various purposes.

In virt-manager, if you select the Edit menu and then "Connection
Details", is the "Autoconnect" item selected?

It is
--
___
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: libvirtd.service start

[Robert McBroom via users]

On 3/21/24 4:15 PM, Barry wrote:



On 21 Mar 2024, at 19:21, Robert McBroom via users 
 wrote:


systemctl enable libvirtd

would change the preset notation but it didn't



Did this add libvirtd to the multi user target?
If so it will start when you boot fedora.

Is that what you mean by preset?

Barry


looking at the status it shows preset:disabled

Maybe have to stop libvirtd and then enable it
--
___
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: libvirtd.service start

[Robert McBroom via users]

On 3/20/24 10:32 AM, Jerry James wrote:

On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users
  wrote:

Recently libvirtd.service is not starting on boot. I have to manually
start it with systemctl start libvirtd.

Do I need to put that command in a startup script?

libvirtd.service is socket activated, so it should run automatically
when needed.  Does something not work if you don't start it manually?


virt- manager starts but says it cannot connect to anything. I have six 
virtual machines I use for various purposes.


systemctl status libvirtd

shows disabled and dead. After starting it manually all machines are 
present.


Status then shows

systemctl status libvirtd
●libvirtd.service - libvirt legacy monolithic daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
preset: disabled)

   Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running)since Thu 2024-03-21 09:56:36 EDT; 5h 13min 
ago

TriggeredBy: ●libvirtd-ro.socket
●libvirtd-admin.socket
●libvirtd.socket
  Docs: man:libvirtd(8)
https://libvirt.org/
  Main PID: 10039 (libvirtd)
 Tasks: 21 (limit: 32768)
Memory: 40.6M (peak: 92.4M)
   CPU: 25.975s
CGroup: /system.slice/libvirtd.service
└─10039 /usr/sbin/libvirtd --timeout 120

Mar 21 09:56:38 HPZ440.attlocal.net libvirtd[10039]: internal error: 
Failed to start QEMU binary /usr/bin/qemu->
Mar 21 09:56:38 HPZ440.attlocal.net libvirtd[10039]: Failed to probe 
capabilities for /usr/bin/qemu-system-xten>
Mar 21 09:56:50 HPZ440.attlocal.net libvirtd[10039]: operation failed: 
Multiple USB devices for 781:5581, use <>
Mar 21 09:56:50 HPZ440.attlocal.net libvirtd[10039]: Unable to find 
device 000.000 in list of active USB devices
Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10306]: 2024-03-21 
13:57:54.273+: 10306: info : libvirt versio>
Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10306]: 2024-03-21 
13:57:54.273+: 10306: info : hostname: HPZ4>
Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10306]: 2024-03-21 
13:57:54.273+: 10306: warning : virSecurity>
Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10307]: 2024-03-21 
13:57:54.275+: 10307: info : libvirt versio>
Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10307]: 2024-03-21 
13:57:54.275+: 10307: info : hostname: HPZ4>
Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10307]: 2024-03-21 
13:57:54.275+: 10307: warning : virSecurity>


Thought

systemctl enable libvirtd

would change the preset notation but it didn'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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

libvirtd.service start

[Robert McBroom via users]

Recently libvirtd.service is not starting on boot. I have to manually 
start it with systemctl start libvirtd.


Do I need to put that command in a startup script?
--
___
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: [need help] Grub does not find my Fedora39 anymore

[Robert McBroom via users]

On 2/29/24 09:08, Karlderletzte wrote:

On 2/28/24 08:54, karlderletzte wrote:

Am 27.02.24 um 22:41 schrieb Samuel Sieb:

On 2/27/24 07:58, karlderletzte wrote:
two days ago, i installed fedora jam 39 on an external drive. This 
runs successfully.


BUT after restart and plug off the external drive Grub from my 
internal drive does not show my fedora39 installation.


You installed Fedora on the external drive, but you also have an 
installation on the internal drive?
Yes this is correct. If i plugin the drive, fedora jam is correctly 
booting.


When you installed to the external drive, it replaced the Fedora entry 
in the EFI boot list to point to that instead of the internal drive.


Yes i understand that.
But unconnected drive and running grub2-mkinstall i thought, that an 
Entry with my fedora 39 from infernal disk is generated. But it doesnt.



What did you use to do the installation?
i installed from live iso downloaded from fedora. selecting the 
external drive and partition. then automatic install. Works all.

Are you booting with the external drive connected or not?

the problem is only, if i boot without the drive connected.

What options does the grub menu show?
1. only system setup from the orginal recovery debian. this is a 
normal entry.


You have a Debian install on there as well?

Yes this is because i bought the laptop without Windows. The Debian 
Entry just runs a Dokumentation of freedos, nothing else.



2 boot UEFI File. this is also a normal entry.

i use the second option and select the correct file. then fedora39 
starts correctly.


Is this with the external drive connected or not?
No without it.
it seems, that the recovery scripts from the different tutorials 
(mostly in end grub2-mkinstall) are not recognizing the fedora39 
installation. i do not understand why.


Go into the BIOS and check the boot list.  I'm wondering if you have a 
Debian entry that is being used.  You can also add another Fedora 
entry that points to the internal hard drive.


Yes i have an Debian Entry and a Windows Bootmanager, but no fedora.
Before installing fedora Jam i Bad three: Debian, Windows and fedora. 
And fedora was in the first place, so it starts from there.
But how could i insert a New Entry? I think, the BIOS does not 
recognize the fedora one, or it is not there.
If i can install the Boot loader for fedora, then it will work again. 
But how could i do that?

t recognize the fedora one, or it is not there.
If i can install the Boot loader for fedora, then it will work again. 
But how could i do that?


From your earlier note that you could boot fedora from the bios, do 
that. Then with privilege run efibootmgr. You will see the boot order 
and the list of entries. The usb drive is probably the first in the 
order and fedora down the list. You can use an editor to create a text 
of the boot order with a reordered list with fedora 2nd. The command 
"efibootmgr -o " will write the new order to the bios.


--
___
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: [need help] Grub does not find my Fedora39 anymore

[Robert McBroom via users]

On 2/27/24 11:25, Robert McBroom via users wrote:


On 2/27/24 10:58, karlderletzte wrote:


Hello,

two days ago, i installed fedora jam 39 on an external drive. This 
runs successfully.


BUT after restart and plug off the external drive Grub from my 
internal drive does not show my fedora39 installation.


i have to choose the efi file directly via bios and loading efi file. 
then it runs.


tried the different tips and tutorials from fedora, but in the end 
after running the script grub2-mkconfig it always recreates the grub 
menu without my fedora.


very annoying.

does anyone know, in which way this script identify the different os 
on my disk?


here is the output of lsblk

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda   8:0    1 483,9M  0 disk
└─sda1    8:1    1 483,7M  0 part 
/run/media/held/40f020fb-33eb-406b-a3b0-7f7ba297557b

zram0   252:0    0 8G  0 disk [SWAP]
nvme0n1 259:0    0 476,9G  0 disk
├─nvme0n1p1 259:1    0   512M  0 part
├─nvme0n1p2 259:2    0   4,9G  0 part
├─nvme0n1p3 259:3    0   510M  0 part [SWAP]
├─nvme0n1p4 259:4    0   600M  0 part /boot/efi
├─nvme0n1p5 259:5    0 1G  0 part /boot
└─nvme0n1p6 259:6    0 469,5G  0 part /var/lib/docker/btrfs
  /home
  /
if any further infos are neccessary, then pls ask.

i will try to deliver.

hope i will, i am not a developer.


Regards

Karl


boot up and rerun grub2-install from the internal system.


When you installed to the external disk, the 
/boot/efi/EFI/fedora/grub.cfg file was written to point to the external 
disk grub.cfg.using the uuid of that disk. The contents of the file are 
in the form of


--

search --no-floppy --fs-uuid --set=dev 61ee38e0-19db-4122-b49c-23794abe1479

set prefix=($dev)/grub2
export $prefix

configfile $prefix/grub.cfg

---

This file should have the uuid of your boot partition. The correct grub 
install program should repair it but there are a number of them.  You 
can use blkid to get the uuid of your boot partition and edit the 
/boot/efi/EFI/fedora/grub.cfg file to point to the internal drive.


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

gnome-disks

[Robert McBroom via users]

Attaching a drive with gnome-disks used to use the accessing user. It 
now brings up a drop down menu of the list of all the users in /home. Is 
there a configuration to tell it to use the active user?

--
___
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: [need help] Grub does not find my Fedora39 anymore

[Robert McBroom via users]

On 2/27/24 10:58, karlderletzte wrote:


Hello,

two days ago, i installed fedora jam 39 on an external drive. This 
runs successfully.


BUT after restart and plug off the external drive Grub from my 
internal drive does not show my fedora39 installation.


i have to choose the efi file directly via bios and loading efi file. 
then it runs.


tried the different tips and tutorials from fedora, but in the end 
after running the script grub2-mkconfig it always recreates the grub 
menu without my fedora.


very annoying.

does anyone know, in which way this script identify the different os 
on my disk?


here is the output of lsblk

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda   8:0    1 483,9M  0 disk
└─sda1    8:1    1 483,7M  0 part 
/run/media/held/40f020fb-33eb-406b-a3b0-7f7ba297557b

zram0   252:0    0 8G  0 disk [SWAP]
nvme0n1 259:0    0 476,9G  0 disk
├─nvme0n1p1 259:1    0   512M  0 part
├─nvme0n1p2 259:2    0   4,9G  0 part
├─nvme0n1p3 259:3    0   510M  0 part [SWAP]
├─nvme0n1p4 259:4    0   600M  0 part /boot/efi
├─nvme0n1p5 259:5    0 1G  0 part /boot
└─nvme0n1p6 259:6    0 469,5G  0 part /var/lib/docker/btrfs
  /home
  /
if any further infos are neccessary, then pls ask.

i will try to deliver.

hope i will, i am not a developer.


Regards

Karl


boot up and rerun grub2-install from the internal 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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Thunderbird Mystery

[Robert McBroom via users]

On 2/27/24 10:12, Thomas Cameron wrote:

On 2/27/24 09:08, Tim via users wrote:

Is Thunderbird one of those apps that always runs once started, and
never quits when you close the window?


There have been times in the past where this is the case, but they're 
few and far between these days. Not saying it doesn't happen, but I 
haven't seen it close but not kill the process in a long time. But 
when it does do that, it will often leave the lock file and cause the 
error that it's already running.



If so, I wonder if it's bad at handling users logging out and/or
rebooting their computer?  (Not removing the lock as it quits, or not
being able to.)


That's pretty much the only time I've seen it happen. If you shut down 
your system while apps are running, there's a decent chance one of the 
apps will not close gracefully. I always just make sure I don't have 
anything running when I reboot.


Power failure is what left Thunderbird in a state. The lock was in the 
".thunderbird" tree as a link to a nonexistent file 
"192.168.1.218:+7103".  Deleting the entry enabled Thunderbird to start.


Thanks to all
--
___
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

Thunderbird Mystery

[Robert McBroom via users]

On one of my f39 systems Thundebird fails to start claiming that it is 
already running. "ksyguard" from root doesn't show anything I can 
recognize as having to do with Thunderbird. Rebooting does not get it to 
work. Looked at the ".thunderbird" file in the user directory and there 
are lots of entries there to make sense about. I can't close an instance 
that I can't find. The pop up window suggests using a different profile 
but I don't see any way to select a profile.


Tried erasing Thunderbird and installing it again but the problem remains.
--
___
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 message on boot

[Robert McBroom via users]

On 2/11/24 10:30, Jonathan Billings wrote:

On Feb 10, 2024, at 19:05, Robert McBroom via 
users  wrote:

I typically boot in mode 3 to a terminal. Fedora f39 going to lxde as the 
desktop. Today with a cold boot and entering  the user login the following 
message showed

--

System is going down. Unprivileged users are not permitted to log in anymore , 
for technical details see pam_nologin(8)

--

Further messages indicated that some updates were being installed. After some 
minutes the system rebooted.

Everything known has been done to prevent any automatic updates with manual dnf 
being used as needed. The pam_login module looks for the existence of

/etc/nologin or

/var/run/nolongin

What is updating files without a command  and writing these entries?

You mentioned you disabled DNF auto updates, but is the 
packagekit-offline-updates.service unit running?  That can also perform updates 
(via PackageKit->dnf) and reboot.  Perhaps the login shell was somehow added to 
the system-update.target?

It’s worth looking at the journal at that time to see what was running.  This 
isn’t a completely unsolvable mystery, all the actions will be in the journal.

]# systemctl status packagekit
○ packagekit.service - PackageKit Daemon
Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead)

~]# systemctl status system-update.target
○ system-update.target - Offline System Update
Loaded: loaded (/usr/lib/systemd/system/system-update.target; static)
Active: inactive (dead)

--
___
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 message on boot

[Robert McBroom via users]

On 2/11/24 05:19, Barry wrote:



On 11 Feb 2024, at 04:07, Robert McBroom via users 
 wrote:

There was plenty of time after the update. Are you saying that dnf update is 
not done when it is finished?

Some installs trigger building kernel modules, which can only happen after dnf 
is finished.
For example the rpmfusion nvidia driver is built by akmods that way.
You can check to see if there are jobs running using:

 sudo systemctl --list-jobs

Barry

System time out shutdown to cold boot should have cleared those rebuilds
--
___
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 message on boot

[Robert McBroom via users]

On 2/10/24 22:00, Tim wrote:

On Sat, 2024-02-10 at 19:05 -0500, Robert McBroom via users wrote:

What is updating files without a command  and writing these entries?

Had you done any manual updates anytime before you shutdown?  Perhaps
they were completing their install.
  
There was plenty of time after the update. Are you saying that dnf 
update is not done when it is finished?

--
___
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 message on boot

[Robert McBroom via users]

I typically boot in mode 3 to a terminal. Fedora f39 going to lxde as 
the desktop. Today with a cold boot and entering  the user login the 
following message showed


--

System is going down. Unprivileged users are not permitted to log in 
anymore , for technical details see pam_nologin(8)


--

Further messages indicated that some updates were being installed. After 
some minutes the system rebooted.


Everything known has been done to prevent any automatic updates with 
manual dnf being used as needed. The pam_login module looks for the 
existence of


/etc/nologin or

/var/run/nolongin

What is updating files without a command  and writing these entries?
--
___
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

Problem with chown

[Robert McBroom via users]

While installing a virtual machine I get a message that the files cannot 
be read by uid104,gid104 these correspond to qemu:qemu. Tried to use 
chown to explicitly assign the directories to qemu:qemu but chown 
doesn't recognize qemu as valid or the uid:gid combination. tried 
setfacl to add qemu permission to read the files, There were no messages 
but the virtual machine setup still could not read the files.


Any clues to what is going on?
--
___
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: rfkill??

[Robert McBroom via users]

On 12/31/23 13:00, Beartooth wrote:

Updating F39 just now on a laptop, I got a request for root to
authorize rfkill. I had just also updated F39 on a PC, with no such
request. (Both machines are connected to a KVM switch and a router by
cables, not wireless.)

I didn't authorize it, and shut the laptop down.

Is there something I should do next??
Since it is a laptop the hardware usually has a wifi module builtin 
which would be recognized by the install and the drivers and support 
software installed eventhough you weren't using that feature. The 
desktop program you use should have an information program that will 
give you your hardware details.

--
___
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: sudo problem on restore from archive

[Robert McBroom via users]

On 12/30/23 18:18, Mike Wright wrote:

On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says 
/usr/bin/sudo  needs to be owned by 0 with the suid bit set. Root 
owns the file and is 0. Looking at a working system directory list shows


   -rwsr-xr-x.  1 root root   57456 Aug 16 20:00 su
   ---s--x--x.  1 root root  202872 Jul 24 20:00 sudo

How does that s bit get set?


man chmod, paragraph 2

The error message is about an suid bit while the man page talks about 
setuid, trying it works. Not a clear extension over the old 777.

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

sudo problem on restore from archive

[Robert McBroom via users]

On a system restore from a tar archive sudo won't work. Says 
/usr/bin/sudo  needs to be owned by 0 with the suid bit set. Root owns 
the file and is 0. Looking at a working system directory list shows


  -rwsr-xr-x.  1 root root   57456 Aug 16 20:00 su
  ---s--x--x.  1 root root  202872 Jul 24 20:00 sudo

How does that s bit get set?
--
___
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: Network problems with f39

[Robert McBroom via users]

On 12/20/23 04:38, Samuel Sieb wrote:

On 12/19/23 21:31, Robert McBroom via users wrote:


On 12/19/23 01:53, Samuel Sieb wrote:

This is the problem you need to resolve.
I don't know why.  You'll need to find out why the dbus broker can't 
run.  I would have expected more details in the log.

--

I'm not sure what to look for in the journal. Does this section show 
the problem? Sequence repeats several times


Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** 
Warning -- SELinux targeted policy relabel is required.
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** 
Relabeling could take a very long time, depending on file
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** 
system size and speed of hard drives.
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running: 
/sbin/fixfiles -T 0  restore
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up 
NSS user entry for 'systemd-oom'...
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS 
returned no entry for 'systemd-oom'
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid 
user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: 
user="systemd-oom"
Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started 
dbus-broker.service - D-Bus System Message Bus.
Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15 
callbacks suppressed
Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130 
audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295 
subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR 
launcher_run_child @ ../src/launch/launcher.c +347: Permission denied
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR 
service_add @ ../src/launch/service.c +1011: Transport endpoint is 
not connected


What have you done to your system?
For some reason it's doing a relabel.  It should be done, you can try 
rebooting and see if things go better.  But things look quite broken.

--


After the upgrade there were some messages about selinux errors. 
Restarted the system set for a relabel. The relabel completed 
satisfactorily as far as I could tell.


Will try again with permissive set as suggested.
--
___
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: Network problems with f39

[Robert McBroom via users]

On 12/19/23 01:53, Samuel Sieb wrote:

On 12/18/23 22:12, Robert McBroom via users wrote:
Upgraded legacy bios laptop from f37 to f39.  Use command line boot. 
User login cycles and returns to login prompt.


Can boot system on command line as root. The network does not connect 
with a dependency failure on NetworkManager. Not cleared on a 
reinstall of NetworkManager.


It's not a NetworkManager issue.

Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: 
Start request repeated too quickly.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: 
Failed with result 'exit-code'.

Dec 18 09:46:38 dv7t.attlocal.net audit: BPF prog-id=74 op=UNLOAD
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Failed to start 
dbus-broker.service - D-Bus System Message Bus.


This is the problem you need to resolve.
I don't know why.  You'll need to find out why the dbus broker can't 
run.  I would have expected more details in the log.

--

I'm not sure what to look for in the journal. Does this section show the 
problem? Sequence repeats several times


Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning 
-- SELinux targeted policy relabel is required.
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** 
Relabeling could take a very long time, depending on file
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system 
size and speed of hard drives.
Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running: 
/sbin/fixfiles -T 0  restore
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up 
NSS user entry for 'systemd-oom'...
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned 
no entry for 'systemd-oom'
Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid 
user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: 
user="systemd-oom"
Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started 
dbus-broker.service - D-Bus System Message Bus.
Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15 
callbacks suppressed
Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130 
audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295 
subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR 
launcher_run_child @ ../src/launch/launcher.c +347: Permission denied
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR 
service_add @ ../src/launch/service.c +1011: Transport endpoint is not 
connected
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: 
launcher_add_services @ ../src/launch/launcher.c +804
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_run 
@ ../src/launch/launcher.c +1415
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: run @ 
../src/launch/main.c +152
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: main @ 
../src/launch/main.c +178
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: Exiting due 
to fatal error: -107
Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Main 
process exited, code=exited, status=1/FAILURE
Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: 
Failed with result 'exit-code'.
Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=failed'
Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1131 
audit(1702909631.164:132): pid=1 uid=0 auid=4294967295 ses=4294967295 
subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Dec 18 09:27:11 dv7t.attlocal.net audit: BPF prog-id=57 op=LOAD
Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1334 
audit(1702909631.171:133): prog-id=57 op=LOAD

Dec 18 09:27:11 dv7t.attlocal.net audit: BPF prog-id=56 op=UNLOAD
Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1334 
audit(1702909631.173:134): prog-id=56 op=UNLOAD
Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Starting 
dbus-broker.service - D-Bus System Message Bus...
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: Looking up 
NSS user entry for 'systemd-oom'...
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: NSS returned 
no entry for 'systemd-oom'
Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: Invalid 
user-name in /usr/share/dbus-1/system.d/org.freedeskt

Network problems with f39

[Robert McBroom via users]

Upgraded legacy bios laptop from f37 to f39.  Use command line boot. 
User login cycles and returns to login prompt.


Can boot system on command line as root. The network does not connect 
with a dependency failure on NetworkManager. Not cleared on a reinstall 
of NetworkManager.


Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Start 
request repeated too quickly.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: 
Failed with result 'exit-code'.

Dec 18 09:46:38 dv7t.attlocal.net audit: BPF prog-id=74 op=UNLOAD
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Failed to start 
dbus-broker.service - D-Bus System Message Bus.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Dependency failed for 
NetworkManager.service - Network Manager.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Dependency failed for 
NetworkManager-wait-online.service - Network Manager Wait Online.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: 
NetworkManager-wait-online.service: Job 
NetworkManager-wait-online.service/start failed with result 'dependency'.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: NetworkManager.service: 
Job NetworkManager.service/start failed with result 'dependency'.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus.socket: Failed with 
result 'service-start-limit-hit'.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: accounts-daemon.service: 
Deactivated successfully.
Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Started 
accounts-daemon.service - Accounts Service



Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: Starting 
NetworkManager.service - Network Manager...
Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: dbus-broker.service: Main 
process exited, code=exited, status=1/FAILURE
Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: dbus-broker.service: 
Failed with result 'exit-code'.
Dec 18 19:09:23 dv7t.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=failed'

Dec 18 19:09:23 dv7t.attlocal.net audit: BPF prog-id=86 op=UNLOAD
Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: NetworkManager.service: 
Deactivated successfully.
Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: Stopped 
NetworkManager.service - Network Manager.
Dec 18 19:09:23 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
Dec 18 19:09:23 dv7t.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'


Dec 18 19:13:59 dv7t.attlocal.net NetworkManager[2850]:   
[1702944839.5428] NetworkManager (version 1.44.2-1.fc39) is starting... 
(boot:65b94e65-710c-4203-9817-fb8f92cb8ebb)
Dec 18 19:13:59 dv7t.attlocal.net NetworkManager[2850]:   
[1702944839.5434] Read config: /etc/NetworkManager/NetworkManager.conf 
(lib: 20-connectivity-fedora.conf) (run: 15-carrier-timeout.conf)
Dec 18 19:13:59 dv7t.attlocal.net NetworkManager[2850]:  
[1702944839.5588] bus-manager: cannot connect to D-Bus: Could not 
connect: Connection refused


Hardware works fine on dual boot to windows. How can I debug the 
NetworkManager problems?


--
___
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: how to remove unwanted old kernels. [SOLVED]

[Robert McBroom via users]

On 12/5/23 17:54, home user wrote:




menuentry 'Windows 7 (on /dev/sda2)' --class windows --class os
be the culprit?  If yes, what's the correct way to get that 
permanently out?


Yes, and same answer as the previous.
--


Here we go...
-
-bash.2[~]: grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found Windows 7 on /dev/sda1
Found Windows 7 on /dev/sda2
Adding boot menu entry for UEFI Firmware Settings ...
done
-bash.3[~]:
-
saving message draft and rebooting.
I'm back.
The unwanted memory test entry is gone from the grub menu.  The 
grub.cfg lines that I pasted into my previous post are gone.


The sda2 windows-7 entry is still in the grub menu, and the 
corresponding lines are still in grub.cfg.  I get the impression from 
the grub2-mkconfig output that deleting those lines from grub.cfg 
won't help; they'll just be restored.  That menu entry is active, but 
when I select it, the windows-7 boot starts, and later gets stuck.  I 
believe that that problem is out of the scope of this thread, so I'll 
go no further with it.  The sda1 windows-7 entry works fine.


What I started this thread for is fixed, so I'm tagging this thread 
SOLVED.  I thank everyone who tried to help.





Bill.

Windows has a startup partition as well as the main partition, windows 
starts from the first. The grub2-mkconfig process picks up both. You can 
delete it from grup2.cfg with a text editor. With the current primary 
grub menu generation by blscfg usage grub2.cfg rarely gets rebuilt on 
updates so the change will stay.

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

Apple camera formats heic and hevc

[Robert McBroom via users]

Apple new formats for photos and videos are giving me trouble just 
transferring files from the phone. Keep getting invalid format in 
transfer even though the functions on the phone are fine. Anyone else 
having problems? Any editors? Gimp seems to overlap parts of the live 
photo to a ragged fixed photo.

--
___
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: f39 emacs strange behavior?

[Robert McBroom via users]

On 11/12/23 11:12, Ranjan Maitra via users wrote:

On Sat Nov11'23 06:21:48PM, Tom Horsley wrote:

From: Tom Horsley 
Date: Sat, 11 Nov 2023 18:21:48 -0500
To: Fedora List 
Reply-To: Community support for Fedora users 
Subject: f39 emacs strange behavior?

I have by no means finished tweaking my fedora 39 boot partition,
but the last time I was booted there, emacs was a complete mess.

It seemed to take forever to respond to keystrokes. Scrolling the
screen would leave random characters in various places which would
disappear if I moved the cursor over them. Probably other weirdness
I didn't figure out.

Anyone else seen this?

I've used alternatives to make emacs-lucid the default. I'll see
if it works better then next time I boot f39...

Did you have any better luck with this. Upgrading to Fedora 39 appears to have 
made my Emacs unusable in that I can no longer open any existing file.

Right, now, trying my luck with nvim for writing this email (because mutt for 
me is linked to an editor, in my case, it was emacs).

Working fine on five separate installs using x11. One install didn't 
have the circular links through /etc/alternatives for whatever they are 
worth

___
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 Fedora 38 to Fedora 39 . Install problem with FFmeg.

[Robert McBroom via users]

On 11/10/23 11:26, Ger van Dijck wrote:


On 11/9/23 21:16, Ger van Dijck wrote:


On 11/8/23 18:54, Samuel Sieb wrote:

On 11/8/23 08:51, Ger van Dijck wrote:
While upgrading I had one problem : I had to allowerasing ffmpeg : 
dnf advised to use skip-broken.


When I want to install (dnf install ffmpeg) there seem to be problems.


To get better answers you need to provide more details, like what 
exactly was the "problem", including all the messages from dnf.



The message from dnf is as follows:

Error/Problem

ffmpeg.6-0-16.fc39.x86_64 from rpmfusion requires 
ffmpeg-libs(x86_64)=6.0-16.fc39 but none of the profiderscan be 
installed.


Conflicting/Requests

Nothing provides libopenh264.so7 (64 bit) neede by 
ffmpeg-lib.6.0-16.fc39.x86_64 from rpm fusion.


try to add --skip-broken : I did but no results.


What now ?


use the dnf option

 --exclude=ffmpeg

to get the bulk upgrade done. Then you can woke on ffmpeg
___
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: grub options

[Robert McBroom via users]

On 10/4/23 12:49, Joe Zeff wrote:

On 10/04/2023 04:24 AM, Thomas wrote:
I had this issue and it's referred in a number of bugs on bugzilla, 
such as:https://bugzilla.redhat.com/show_bug.cgi?id=1925776


Either edit /etc/kernel/cmdline to remove the option or use grubby 
that updates both sets of files and the entries on /boot as well


Neither option, alas, is available from the grub command line on a 
flash drive.

___


If you have a time delay set on the boot menu you can use the e command 
to change the cmdline. ctl/x then boots. The change is then persistent 
the nest time a kernel is installed.


___
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

Couple of Thunderbird pains

[Robert McBroom via users]

In the past I would just enter "users" in the "To " space and would get 
the list entry users@lists.fedoraproject.org. Somehow that now gets 
attached to send to a person instead of the list. Have to explicitly 
type in the list address. Is there a fix?


Thunderbird keeps continually telling me it wants to compact the mails 
storage for what is a trivial amount of space, Is there a way to make it 
use a reasonable size to do the prompt?


I set the font size to small but it always reverts to medium, where 
would a permanent setting be located?


___
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: EFI and fedora

[Robert McBroom via users]

On 9/25/23 20:44, Chris Adams wrote:

Once upon a time, Bill Cunningham  said:

On 9/25/2023 4:44 PM, Chris Adams wrote:

Once upon a time, Bill Cunningham  said:
...
There's no magic reserved space outside partitions that is used for
booting anymore.  The firmware finds the device, reads the partition
table to find the correct partition, mounts that partition and reads the
configured executables from it.

OK I see, thanks exactly what I was asking. So if for some reason
you wanted to save boot code, I guess, you would save partitions and
files?

Yes.  And maybe I guess dump out the EFI boot variables somewhere
(output of "efibootmgr").

all in /boot/efi, save as a package
___
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: Hung Virtual Machine

[Robert McBroom via users]

On 9/26/23 10:16, stan via users wrote:

On Mon, 25 Sep 2023 10:12:46 -0400
Robert McBroom via users  wrote:


Power outage dropped my f38 system while a virtual Rawhide system was
running. On restart the virtual machine is paused and none of the
virt-manager shutdown, reset or delete work. It wasn't supposed to
come up on a host restart. What can be done to clear the lock?



Error resetting domain: Timed out during operation: cannot acquire
state change lock (held by monitor=remoteDispatchDomainCreate)

Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72,
in cb_wrapper
      callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108,
in tmpcb
      callback(*args, **kwargs)
    File
"/usr/share/virt-manager/virtManager/object/libvirtobject.py", line
57, in newfn ret = fn(self, *args, **kwargs)
    ^
    File "/usr/share/virt-manager/virtManager/object/domain.py", line
1393, in reset
      self._backend.reset(0)
    File "/usr/lib64/python3.11/site-packages/libvirt.py", line 2408,
in reset
      raise libvirtError('virDomainReset() failed')
libvirt.libvirtError: Timed out during operation: cannot acquire
state change lock (held by monitor=remoteDispatchDomainCreate)

Was curious, so did some searching.  Not familiar with qemu or libvirt,
so might or might not help you.

This seems to have happened in the past, as well.  What I can glean
from this bug report is that libvirt and qemu being out of synch caused
it.
https://bugzilla.redhat.com/show_bug.cgi?id=1530346

This bug report in arch seems to support that it is a mismatch.
https://bugs.archlinux.org/task/63516

Both of these are older, so it might be a regression because something
else was fixed.  You could try reinstalling qemu on the host.  One
comment mentioned restarting libvirt was successful.

A really old link, but it sounds a lot like your problem, so the
solution might still work.

https://stackoverflow.com/questions/16763240/libvirt-cannot-stop-reboot-force-shutdown-or-destroy-guest

upgraded to f39 beta and the problem was cured. Sledgehammer approach___
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

Hung Virtual Machine

[Robert McBroom via users]

Power outage dropped my f38 system while a virtual Rawhide system was 
running. On restart the virtual machine is paused and none of the 
virt-manager shutdown, reset or delete work. It wasn't supposed to come 
up on a host restart. What can be done to clear the lock?




Error resetting domain: Timed out during operation: cannot acquire state 
change lock (held by monitor=remoteDispatchDomainCreate)


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

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

    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", 
line 57, in newfn

    ret = fn(self, *args, **kwargs)
  ^
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 
1393, in reset

    self._backend.reset(0)
  File "/usr/lib64/python3.11/site-packages/libvirt.py", line 2408, in 
reset

    raise libvirtError('virDomainReset() failed')
libvirt.libvirtError: Timed out during operation: cannot acquire state 
change lock (held by monitor=remoteDispatchDomainCreate)
___
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: How do I install the rescue kernel for fc38?

[Robert McBroom via users]

On 8/29/23 07:14, ToddAndMargo via users wrote:

Hi All,

Fedora 38

My rescue kernel is FC30.

How do I install the FC38 rescue kernel?

# dnf whatprovides kernel\* | grep -i rescue


And my search engine is not helping.

Many thanks,
-T

Saw a while back that all you need to do is delete the rescue image from 
/boot and the /boot/loader entry. Then a rescue image will be created 
with the installation of a new kernel. blscfg will put it in the menu.


It has worked several times for me.
___
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: Wrestling with UEFI

[Robert McBroom via users]

On 8/22/23 09:46, stan via users wrote:

On Tue, 22 Aug 2023 08:11:02 -0400
Robert McBroom via users  wrote:


looked in system settings, screensaver settings, powermanager
settings and did not find the magic button. Using LXDE.

I had this happen to me at one point because the XFCE screensaver
started automatically, even if XFCE wasn't running.  I have all the
desktops installed so I can use their programs even if I'm not running
them directly, and boot them if I choose.  So, if you have any other
desktop installed, or even other desktop applications, this might be
the case for you as well. It seems that Gnome has a default to go to
sleep automatically after 15 minutes of idle time, regardless of any
other settings.  The thread Tim pointed to has tips on how to turn that
off.
Followed that thread as it grew, didn't see a connection as using SDDM, 
and LXDE.___
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: Wrestling with UEFI

[Robert McBroom via users]

On 8/22/23 01:04, Samuel Sieb wrote:

On 8/21/23 21:06, Robert McBroom via users wrote:
Added a Fedora 37 and Fedora 38 installations on separate drives to a 
Windows system. Default boot is the Windows 10 system. Using the boot 
menu gets me to grub which can boot the system of my choice.


When the Fedora 38 install goes to sleep it doesn't come back to 
Fedora but boots to the Windows install. Keeps going to sleep in a 
frustratingly short time. The screensaver time setting don't seem to 
interact with the powermanagement settings. Never doesn't seem to be 
never.


It's not the screensaver time, it's the sleep time setting.  But also, 
if it's booting again, then the sleep isn't even working.



What will make fedora stay in its own neighborhood?


If the default boot is windows, then any time it reboots, it will go 
there.  You either need to disable the sleeping or figure out why it's 
not working properly.


looked in system settings, screensaver settings, powermanager settings 
and did not find the magic button. Using LXDE.

___
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

Wrestling with UEFI

[Robert McBroom via users]

Added a Fedora 37 and Fedora 38 installations on separate drives to a 
Windows system. Default boot is the Windows 10 system. Using the boot 
menu gets me to grub which can boot the system of my choice.


When the Fedora 38 install goes to sleep it doesn't come back to Fedora 
but boots to the Windows install. Keeps going to sleep in a 
frustratingly short time. The screensaver time setting don't seem to 
interact with the powermanagement settings. Never doesn't seem to be never.


What will make fedora stay in its own neighborhood?
___
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: Starting LXDE from xinit -- :0 xterm window

[Robert McBroom via users]

On 8/5/23 08:45, stan via users wrote:

On Fri, 4 Aug 2023 13:09:35 -0400
Robert McBroom via users  wrote:


Been having problems with f38 startup going to a blank screen with no
response to the keyboard, mouse. Was using sddm as the display
manager. Can get around it by by booting in terminal mode. Starting
the graphical mode with xinit -- :0 and lxsession in the resulting
xterm window. Get the following messages in the window--
  

The system is sthen somewhat usable but occasionally locks up. Is
there a command to start a desktop environment before the session?

I always boot to multiuser / runlevel 3 and start X from there.  For
LXDE I use the following to put the correct command in ~/.Xclients
echo 'exec startlxde' >> $XCLIENTS
If you are always going to start LXDE, you should only have to do that
once.
Once that is in place, it is only necessary to run
startx -- vt10
to put the desktop on F10, so that messages will appear on F1.  You can
just run startx if you want the desktop on F1.

I am using openbox as the desktop manager when I start LXDE
(set in the LXDE configuration file,
.config/lxsession/LXDE/desktop.conf).  I haven't tried sddm, it might
just work if it is your default if you use the above procedure.


What shell are you using? In Bash--

~]$ echo 'exec startlxde' >> $XCLIENTS

bash: $XCLIENTS: ambiguous redirect

~]$ XCLIENTS="exec startlxde"
~]$ echo $XCLIENTS
exec startlxde

~]$ cat .config/lxsession/LXDE/desktop.conf
[Session]
window_manager=openbox-lxde
disable_autostart=no
polkit/command=lxpolkit
clipboard/command=lxclipboard
xsettings_manager/command=build-in
proxy_manager/command=build-in
keyring/command=ssh-agent
quit_manager/command=lxsession-logout
lock_manager/command=lxlock
terminal_manager/command=lxterminal
quit_manager/image=/usr/share/lxde/images/logout-banner.png
quit_manager/layout=top

[GTK]
sNet/ThemeName=Adwaita
sNet/IconThemeName=Adwaita
sGtk/FontName=Sans 10
iGtk/ToolbarStyle=3
iGtk/ButtonImages=1
iGtk/MenuImages=1
iGtk/CursorThemeSize=18
iXft/Antialias=1
iXft/Hinting=1
sXft/HintStyle=hintslight
sXft/RGBA=rgb
iNet/EnableEventSounds=1
iNet/EnableInputFeedbackSounds=1
sGtk/ColorScheme=
iGtk/ToolbarIconSize=3
sGtk/CursorThemeName=DMZ-White
sGtk/IMModule=ibus:xim

[Mouse]
AccFactor=20
AccThreshold=10
LeftHanded=0

[Keyboard]
Delay=500
Interval=30
Beep=1

[State]
guess_default=true

[Dbus]
lxde=true

[Environment]
menu_prefix=lxde-


___
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

Starting LXDE from xinit -- :0 xterm window

[Robert McBroom via users]

Been having problems with f38 startup going to a blank screen with no 
response to the keyboard, mouse. Was using sddm as the display manager. 
Can get around it by by booting in terminal mode. Starting the graphical 
mode with xinit -- :0 and lxsession in the resulting xterm window. Get 
the following messages in the window--


 ~]$ lxsession &
[1] 4047
 ~]$ ** Message: 12:00:19.020: main.vala:113: Session is (null)
** Message: 12:00:19.021: main.vala:114: DE is (null)
** Message: 12:00:19.021: main.vala:118: No session set, fallback to 
LXDE session
** Message: 12:00:19.021: main.vala:124: No desktop environnement set, 
fallback to LXDE
** Message: 12:00:21.473: main.vala:145: log directory: 
/home/rm3/.cache/lxsession/LXDE
** Message: 12:00:21.473: main.vala:146: log path: 
/home/rm3/.cache/lxsession/LXDE/run.log


The system is sthen somewhat usable but occasionally locks up. Is there 
a command to start a desktop environment before the session?

___
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: libvirtd.service won't start

[Robert McBroom via users]

On 7/9/23 00:16, ToddAndMargo via users wrote:

On 7/8/23 20:57, Samuel Sieb wrote:

On 7/8/23 18:45, ToddAndMargo via users wrote:

# libvirtd --daemon
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not 
found (required by /lib64/libvirt-lxc.so.0)
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not 
found (required by /lib64/libvirt-qemu.so.0)


Actually, it might be the right "libvirtd", but the problem appears 
to be in "/lib64/libvirt-lxc.so.0" and "/lib64/libvirt-qemu.so.0" 
which are likely pointing to non-Fedora libraries.




# rpm -qf /usr/lib64/libvirt.so.0.9005.0
file /usr/lib64/libvirt.so.0.9005.0 is not owned by any package

Note: but it is required for libvirt-lxc.so.0
and libvirt-qemu.so.0.  see below

# rm libvirt.so.0
rm: remove symbolic link 'libvirt.so.0'? y

# ln -s libvirt.so.0.9000.0 libvirt.so.0

# libvirtd --daemon
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not 
found (required by /lib64/libvirt-lxc.so.0)
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_9.5.0' not 
found (required by /lib64/libvirt-qemu.so.0)




AHHH POOP!!  Right under my noise

libvirt-lxc.so.0 and and libvirt-qemu.so.0's links
are bad:


# ls -al libvirt-lxc.so*
lrwxrwxrwx. 1 root root    16 Jan 18 16:00 libvirt-lxc.so -> 
libvirt-lxc.so.0
lrwxrwxrwx. 1 root root    23 Jul  8 20:55 libvirt-lxc.so.0 -> 
libvirt-lxc.so.0.9005.0

-rwxr-xr-x. 1 root root 20384 Jan 18 16:00 libvirt-lxc.so.0.9000.0
-rwxr-xr-x. 1 root root 20288 Jul  4 17:00 libvirt-lxc.so.0.9005.0

# rm libvirt-lxc.so.0
rm: remove symbolic link 'libvirt-lxc.so.0'? y

# ln -s libvirt-lxc.so.0.9000.0 libvirt-lxc.so.0

# ls -al libvirt-qemu.so*
lrwxrwxrwx. 1 root root    17 Jan 18 16:00 libvirt-qemu.so -> 
libvirt-qemu.so.0
lrwxrwxrwx. 1 root root    24 Jul  8 20:55 libvirt-qemu.so.0 -> 
libvirt-qemu.so.0.9005.0

-rwxr-xr-x. 1 root root 20288 Jan 18 16:00 libvirt-qemu.so.0.9000.0
-rwxr-xr-x. 1 root root 20192 Jul  4 17:00 libvirt-qemu.so.0.9005.0

# rm libvirt-qemu.so.0
rm: remove symbolic link 'libvirt-qemu.so.0'? y

# ln -s libvirt-qemu.so.0.9000.0 libvirt-qemu.so.0
[root@rn6 lib64]# ls -al libvirt-qemu.so*
lrwxrwxrwx. 1 root root    17 Jan 18 16:00 libvirt-qemu.so -> 
libvirt-qemu.so.0
lrwxrwxrwx. 1 root root    24 Jul  8 21:09 libvirt-qemu.so.0 -> 
libvirt-qemu.so.0.9000.0

-rwxr-xr-x. 1 root root 20288 Jan 18 16:00 libvirt-qemu.so.0.9000.0
-rwxr-xr-x. 1 root root 20192 Jul  4 17:00 libvirt-qemu.so.0.9005.0

# systemctl start  libvirtd


And status shows good too !!

"virsh-manager" still does ont work. but...

typo should be virt-manager



And restarting libvirtd.service and it is back
to complaining again.  But I will reboot
and get back



Other things you asked about.


# which libvirtd
/usr/sbin/libvirtd

# find / -iname libvirtd
/etc/logrotate.d/libvirtd
/usr/lib/python3.11/site-packages/libvirttestapi/repos/libvirtd
/usr/sbin/libvirtd


And starting libvirtd the correct way:

# systemctl start  libvirtd
Job for libvirtd.service failed because the control process exited 
with error code.
See "systemctl status libvirtd.service" and "journalctl -xeu 
libvirtd.service" for details.



# systemctl status libvirtd.service
× libvirtd.service - Virtualization daemon
 Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; 
disabled; preset: disabled)

    Drop-In: /usr/lib/systemd/system/service.d
 └─10-timeout-abort.conf
 Active: failed (Result: exit-code) since Sat 2023-07-08 21:05:56 
PDT; 1min 15s ago

TriggeredBy: × libvirtd-admin.socket
 × libvirtd.socket
 ○ libvirtd-tcp.socket
 ○ libvirtd-tls.socket
 × libvirtd-ro.socket
   Docs: man:libvirtd(8)
 https://libvirt.org
    Process: 40020 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS 
(code=exited, status=1/FAILURE)

   Main PID: 40020 (code=exited, status=1/FAILURE)
    CPU: 5ms

Jul 08 21:05:56 rn6.rent-a-nerd.local systemd[1]: libvirtd.service: 
Scheduled restart job, restart counter is at 5.
Jul 08 21:05:56 rn6.rent-a-nerd.local systemd[1]: Stopped 
libvirtd.service - Virtualization daemon.
Jul 08 21:05:56 rn6.rent-a-nerd.local systemd[1]: libvirtd.service: 
Start request repeated too quickly.
Jul 08 21:05:56 rn6.rent-a-nerd.local systemd[1]: libvirtd.service: 
Failed with result 'exit-code'.
Jul 08 21:05:56 rn6.rent-a-nerd.local systemd[1]: Failed to start 
libvirtd.service - Virtualization daemon.




# journalctl -xeu libvirtd.service
░░ the configured Restart= setting for the unit.
Jul 08 21:05:56 rn6.rent-a-nerd.local systemd[1]: Stopped 
libvirtd.service - Virtualization daemon.

░░ Subject: A stop job for unit libvirtd.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit libvirtd.service has finished.
░░
░░ The job identifier is 29512 and the job result is done.
Jul 08 21:05:56 rn6.rent-a-nerd.local systemd[1]: libvirtd.service: 
Start request 

Re: xfce4 desktop problem

[Robert McBroom via users]

On 7/5/23 15:18, Mike Wright wrote:

On 7/5/23 11:02, Robert McBroom via users wrote:
Running xfce4 desktop on f38 terminal the desktop windows have lost 
the window bar at the top. Can't reposition open windows.


They are fine if I switch to LXDE or kde. What part of xfce needs to 
be reinstalled?


The WindowManager takes care of borders and title bars, etc.  The 
sizes and colors are determined by which theme the WindowManager is 
using.


Xfce4 uses Settings->WindowManager.  Once there select the Style tab. 
That gives you options for Title font and font-size, alignment, and 
buttons (Minimize, Maximize, Close, etc) and Themes.  Try selecting a 
different theme than the one that is highlighted (the current 
setting). If that fixes the windows go ahead and click on the 
originally highlighted Theme and you should be back to where you started.


If the WM is so badly hosed that doesn't work you could try restarting 
the WindowManager, which is probably "xfwm4".


  killall -HUP xfwm4  or pkill -HUP xfwm4  or kill -HUP $(pidof xfwm4)

If none of that works a reboot might get whatever is tangled up 
straightened out.



There have been multiple boots with to try alternate desktops.
Finally you could just install xfwm4 again which will bring in 
anything that may have gone walkies on you.


All of this is assuming that the fault lies with the window manager.  
In fact, if you're feeling adventurous you could even install a 
different window manager.  There is no hard and fast rule tying a 
specific window manager to a desktop environment, which in your case 
is xfce4.

How could xfce4 be told to use Openbox?
___
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

xfce4 desktop problem

[Robert McBroom via users]

Running xfce4 desktop on f38 terminal the desktop windows have lost the 
window bar at the top. Can't reposition open windows.


They are fine if I switch to LXDE or kde. What part of xfce needs to be 
reinstalled?

___
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: Anyone else seeing libvirtd refusing connections after a day?

[Robert McBroom via users]

On 6/28/23 03:21, Barry wrote:



On 28 Jun 2023, at 00:15, Robert McBroom via 
users  wrote:

Seems like a red herring

I know there are systemd changes that are supposed to fix this in testing.
I thought that was referred to in the discuss thread.


From man virtnetworkd

   It is one of a collection of modular daemons that replace 
functionality  previously

   provided by the monolithic libvirtd daemon.

Looks like pieces haven't made it through the update process. with 
libvirtd still providing all the services.
___
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: Mounting host directory on VM to load on VM startup

[Robert McBroom via users]

On 6/27/23 12:54, Chris Adams wrote:

Once upon a time, Robert McBroom  said:

Put the mount command

mount -t virtiofs hostfiles /user/local/src

in /etc/profile.d/mnthst.sh

to connect when the virtual machine is started. Every time I start a
terminal session in the VM I get the message

Yeah, that's not at all right.

/etc/profile.d is intended for shell snippets that are run when shells
start (so every login and also when you start additional shells).

You don't need a script at all to mount a filesystem at boot, you need
to put it in /etc/fstab.  For this, add an entry like:

hostfiles /user/local/src virtiofs defaults 0 0


Thanks Chris

I don't see virtiofs as a file type in man fstab. Is there documentation?

___
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: Anyone else seeing libvirtd refusing connections after a day?

[Robert McBroom via users]

On 6/27/23 14:02, Barry wrote:



On 27 Jun 2023, at 17:51, Robert McBroom via users 
 wrote:


Putting

VIRTNETWORKD_ARGS=

in  /etc/sysconfig/virtnetworkd

does nothing. Stopping libvirtd allows virt-manager to connect. 
Before connection


Does the info here help? 
https://discussion.fedoraproject.org/t/libvirtd-stop-responding-after-some-time/84324/3


Seems like a red herring

systemctl stop libvirtd

works a lot simpler and keeps working even with

~]# systemctl status virtnetworkd
○ virtnetworkd.service - Virtualization network daemon
 Loaded: loaded (/usr/lib/systemd/system/virtnetworkd.service; 
disabled; preset: disabled)

    Drop-In: /usr/lib/systemd/system/service.d
 └─10-timeout-abort.conf
 Active: inactive (dead)
TriggeredBy: ○ virtnetworkd-ro.socket
 ○ virtnetworkd-admin.socket
 ○ virtnetworkd.socket
   Docs: man:virtnetworkd(8)
 https://libvirt.org

Additional VMs start without problems. so what is the function of 
virtnetworkd?

___
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: Anyone else seeing libvirtd refusing connections after a day?

[Robert McBroom via users]

Putting

VIRTNETWORKD_ARGS=

in  /etc/sysconfig/virtnetworkd

does nothing. Stopping libvirtd allows virt-manager to connect. Before 
connection


~]# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
 Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
preset: disabled)

    Drop-In: /usr/lib/systemd/system/service.d
 └─10-timeout-abort.conf
 Active: active (running) since Tue 2023-06-27 11:05:46 EDT; 23min ago
TriggeredBy: ● libvirtd-ro.socket
 ● libvirtd.socket
 ● libvirtd-admin.socket
   Docs: man:libvirtd(8)
 https://libvirt.org
   Main PID: 2859 (code=exited, status=0/SUCCESS)
  Tasks: 2 (limit: 32768)
 Memory: 29.0M
    CPU: 625ms
 CGroup: /system.slice/libvirtd.service
 ├─2979 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>
 └─2980 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>


Jun 27 11:05:46 HPZ440.attlocal.net systemd[1]: Started libvirtd.service 
- Virtualization dae>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: started, version 2.89 
cachesize 150
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: compile time options: 
IPv6 GNU-getopt DBus>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq-dhcp[2979]: DHCP, IP range 
192.168.122.2 -- 192.1>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq-dhcp[2979]: DHCP, sockets 
bound exclusively to in>

Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: reading /etc/resolv.conf
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: using nameserver 
127.0.0.53#53

Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: read /etc/hosts - 8 names
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: read 
/var/lib/libvirt/dnsmasq/default.addn>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq-dhcp[2979]: read 
/var/lib/libvirt/dnsmasq/default>


virt-manager and cockpit cannot connect to the virtual machines

~]# systemctl stop libvirtd
Warning: Stopping libvirtd.service, but it can still be activated by:
  libvirtd-ro.socket
  libvirtd.socket
  libvirtd-admin.socket

Running  virt-manager then connects and works fine.

~]# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
 Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
preset: disabled)

    Drop-In: /usr/lib/systemd/system/service.d
 └─10-timeout-abort.conf
 Active: active (running) since Tue 2023-06-27 11:29:52 EDT; 28s ago
TriggeredBy: ● libvirtd-ro.socket
 ● libvirtd.socket
 ● libvirtd-admin.socket
   Docs: man:libvirtd(8)
 https://libvirt.org
   Main PID: 8385 (libvirtd)
  Tasks: 22 (limit: 32768)
 Memory: 62.4M
    CPU: 694ms
 CGroup: /system.slice/libvirtd.service
 ├─2979 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>
 ├─2980 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>

 └─8385 /usr/sbin/libvirtd --timeout 120

Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>


Binaries that show as failing to start are for minor use processors
___
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

Mounting host directory on VM to load on VM startup

[Robert McBroom via users]

Put the mount command

mount -t virtiofs hostfiles /user/local/src

in /etc/profile.d/mnthst.sh

to connect when the virtual machine is started. Every time I start a 
terminal session in the VM I get the message


mount: /usr/local/src: must be superuser to use mount

The directory is mounted so not problem there. Where should the command 
be placed to be just executed on startup? Doesn't seem to fit in fstab 
on the VM but haven't tried that yet.

___
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: logging in as root

[Robert McBroom via users]

On 6/21/23 17:56, Bill Cunningham wrote:


On 6/21/2023 4:39 PM, Samuel Sieb wrote:

On 6/20/23 17:33, Bill Cunningham wrote:
 I have uploaded the tar.gz file to my cloud VM and try to use 
the system and it will not let me have root privledges. I use 'su' 
and the system wants me to enter a password. IDK what the password 
is. IS there a way around this?


You said in a later email that you didn't set a personal password, 
but you must be running as some user.  How did you get a prompt as 
that user and did you try "sudo"?


Yes I am logged in as a user and the user is my email address. I 
uploaded to a bucket the gzipped tarball and created an image for the 
VM instance. But I am logged in a user and not root.
Try changing the password to the user you have, then see what groups are 
assigned. Some cloud installs initially have an empty password.

___
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: Anyone else seeing libvirtd refusing connections after a day?

[Robert McBroom via users]

On 6/19/23 14:57, Thomas Cameron wrote:

On 6/19/23 12:33, Jonathan Billings wrote:

On Mon, Jun 19, 2023 at 11:55:26AM -0500, Thomas Cameron wrote:
I have a dedicated Fedora 38 KVM hypervisor that I use for testing, 
and I
also use my desktop to run VMs. When I leave the virtualization 
manager app
open (typically overnight), it has disconnected from the remote 
hypervisor
and from my local hypervisor. When I double click the connection, it 
just

hangs. If I restart libvirtd on the hypervisor and on my desktop, it
connects instantly.

Is anyone else seeing this?

I have seen something like this, only connecting to the local service.

I was able to resolve it using the fix in Comment 4 of this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2213660#c4


Many thanks, Jonathan. I've implemented that config file, we'll see 
how to goes!


Had this problem start sometime last week. Found that stopping libvirtd 
would let virt-manager connect. Saw that it has occurred in the past and 
setting a variable in /etc/conf.d was suggested. Didn't help.


Trying the /etc/sysconfing/virtnetworkd variable from the bugzilla link.
___
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: What causes mailing list bounce?

[Robert McBroom via users]

On 6/19/23 10:19, stan via users wrote:

On Sat, 17 Jun 2023 10:49:48 -0400
Robert McBroom via users  wrote:


Received a strange message from the kde list.

-

Your membership in the mailing list kde-linux has been disabled due to
excessive bounces The last bounce received from you was dated
09-Jun-2023.  You will not get any more messages from this list until
you re-enable your membership.  You will receive 2 more reminders like
this before your membership in the list is deleted.

To re-enable your membership, you can simply respond to this message
(leaving the Subject: line intact), or visit the confirmation page at

  
https://mail.kde.org/mailman/confirm/kde-linux/79e4115aeba3fe910fe5322ff3dc34246fb5cd6c

_
As far as I can tell mail from all the other traffic on other lists
is coming through with no problems. I'm using Thunderbird with
Yahoo.com as my mail service.

I think bounces are when a destination rejects email for transit.
Usually this is because of the rules they have implemented to filter
spam.  I've read that Yahoo is notorious for this.  Maybe someone else
can shed more light.  From the perspective of the kde list, this
appears to be a mail address that has gone stale, and so they stop
sending to it.
Replying to their mail apparently re-enabled my membership as I've 
received more entries from the list. Hopefully the threshold won't be 
exceeded 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

What causes mailing list bounce?

[Robert McBroom via users]

Received a strange message from the kde list.

-

Your membership in the mailing list kde-linux has been disabled due to
excessive bounces The last bounce received from you was dated
09-Jun-2023.  You will not get any more messages from this list until
you re-enable your membership.  You will receive 2 more reminders like
this before your membership in the list is deleted.

To re-enable your membership, you can simply respond to this message
(leaving the Subject: line intact), or visit the confirmation page at


https://mail.kde.org/mailman/confirm/kde-linux/79e4115aeba3fe910fe5322ff3dc34246fb5cd6c

_
As far as I can tell mail from all the other traffic on other lists is coming 
through with no problems. I'm using Thunderbird with Yahoo.com as my mail 
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Startup Problems

[Robert McBroom via users]

On 6/10/23 09:35, stan via users wrote:

On Sat, 10 Jun 2023 00:26:09 -0400
Robert McBroom via users  wrote:


The original install went to  the 495.44 version of the nvidia driver
but my card GT 710 requires  the 470 version. I see in the journal

May 23 13:26:58 HPZ440.attlocal.net systemd[2911]: Started
app-nvidia\x2dsettings\x2d470xx\x2duser@autostart.service  -
nvidia-settings. May 23 13:26:59 HPZ440.attlocal.net kernel: NVRM:
API mismatch: the client has the version 495.44, but
      NVRM: this kernel module
has the version 470.182.03.  Please
      NVRM: make sure that
this kernel module and all NVIDIA driver
      NVRM: components have
the same version.

So, if your video card requires the 470 driver, and you have the 495
driver installed, how is the multiuser console working?  Is it using
nouveau?  How is XFCE able to use the wrong driver, but kde isn't?
Are there base features in all nvidia drivers, and kde uses features
of the 470 not in the base features of 495?


The installer tried to use the 495.44 driver which of course failed. 
Using the terminal mode the 470 driver from rpmfusion was installed. 
NVIDIA has moved on and no longer has a 495 series. Couldn't figure out 
what client is being referred to by the messages.


The question is what is the meaning of the messages in the journal?

___
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: Startup Problems

[Robert McBroom via users]

On 6/9/23 12:53, stan via users wrote:

On Fri, 9 Jun 2023 00:30:06 -0400
Robert McBroom via users  wrote:


What do I need to do to get the system to boot to the desktop?

Does journalctl show anything from the failed boot to a desktop?  There
should be some kind of underlying error that is reported.  1
What would be something to search to find? I get a little window with a 
sad face that says an error occurred, try again. The crash reporter app  
shows a string of system failure but says The backtrace  does not 
contain enough meaningful function frames to be reported

You could try another desktop manager / greeter.  You would have to
remove the 3 from the kernel startup line.  You should be able to use
The 3 comes from a grub edit, without it the boot locks to a blank 
screen requiring power off.Tried sddm and lightdm.

dnf from multiuser, and do a search for desktop,
dnf search desktop
to find other greeters.

Installed Environment Groups:
   Fedora Server Edition
   KDE Plasma Workspaces
   Xfce Desktop
Installed Groups:
   Administration Tools
   Headless Management
   GNOME Desktop Environment
   KDE (K Desktop Environment)
   Fonts

   Hardware Support

Prefer kde but xfce works.


How did you get to f38?  Upgrade, or install?  If upgrade, did it
complete successfully?  Were there lots of conflicts?


upgrade from f37 no problems

The original install went to  the 495.44 version of the nvidia driver 
but my card GT 710 requires  the 470 version. I see in the journal


May 23 13:26:58 HPZ440.attlocal.net systemd[2911]: Started 
app-nvidia\x2dsettings\x2d470xx\x2duser@autostart.service - nvidia-settings.
May 23 13:26:59 HPZ440.attlocal.net kernel: NVRM: API mismatch: the 
client has the version 495.44, but
    NVRM: this kernel module 
has the version 470.182.03.  Please
    NVRM: make sure that this 
kernel module and all NVIDIA driver
    NVRM: components have the 
same version.



If there is a specific desktop you want, try running
dnf group install --with-optional [name of the desktop group]
to pick up any missing packages
___
___
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

Startup Problems

[Robert McBroom via users]

F38 starts to a blank screen with a cursor in the upper left corner of 
the screen. Does not respond to keyboard or mouse. The display manager 
is supposed to be sddm. Editing the grub entry to start in single user 
mode gets me to a terminal screen where I can login. startx begins but 
fails to connect to the X server.


--

            xf86EnableIOPorts: failed to set IOPL for I/O 
(Operation not permitted)


xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully 
(0). Closing log file.

---

xinit brings up a terminal window where a lxsession will give a 
graphical desktop. gnome and kde plasma fail to start. xfce gives a 
desktop with no window bar on windows and mouse window operations Which 
is not really usable.


]# systemctl get-default
graphical.target
Note: found "3" on the kernel commandline, which overrides the default unit.



What do I need to do to get the system to boot to the desktop?
___
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: Thunderbird quirk

[Robert McBroom via users]

On 6/7/23 00:28, Samuel Sieb wrote:

On 6/6/23 21:23, Robert McBroom via users wrote:
The flame icon on a message in the Inbox used to send the message 
immediately to "Bulk Mail". It has stopped doing that. Messages that 
the email provider flags do go to the "Bulk Mail". Now the message 
has to be manually trashed. It was very nice to just flag messages 
and have them go away.


Is there a setting I've missed that has changed?


See the Junk section under Privacy & Security in the settings.
There's an option for that.
___
Got it.

Thanks Samuel
___
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

Thunderbird quirk

[Robert McBroom via users]

The flame icon on a message in the Inbox used to send the message 
immediately to "Bulk Mail". It has stopped doing that. Messages that the 
email provider flags do go to the "Bulk Mail". Now the message has to be 
manually trashed. It was very nice to just flag messages and have them 
go away.


Is there a setting I've missed that has changed?
___
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: Boot failure with 6.3.4-101.fc37

[Robert McBroom via users]

I just tried 'sudo akmods --force' and it failed.  An updated package


nvidia-470xx-kmod-470.182.03-2.fc37

was placed in testing on 27 May.  I haven't tried it yet. 


fails to compile on f38 kernel 6.3.4


akmod-nvidia-470xx-470.182.03-2.fc38.x86_64

is now good on kernels up to the current 6.3.5
___
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: Boot failure with 6.3.4-101.fc37

[Robert McBroom via users]

On 5/31/23 15:47, John Pilkington wrote:

On 31/05/2023 20:21, John Pilkington wrote:

On 31/05/2023 18:39, home user wrote:

On 5/31/23 10:20 AM, Barry Scott wrote:






When there's a new kernel I usually let the akmods build finish 
before 'systemctl reboot'.  Usually the shutdown.service doesn't then 
delay the shutdown.


Today I didn't see the akmods build after installation.  On 
'systemctl reboot' the shutdown.service ran for 5 minutes before 
getting to the (blue HP) bootscreen and eventually hanging.


Simple answer:  it has been ok but now seems unpredictable.

The system has been through many version upgrades.  nvidia 470xx.


I just tried 'sudo akmods --force' and it failed.  An updated package

nvidia-470xx-kmod-470.182.03-2.fc37

was placed in testing on 27 May.  I haven't tried it yet. 


fails to compile on f38 kernel 6.3.4

___
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: System networking confusion

[Robert McBroom via users]

On 5/21/23 01:08, Tim via users wrote:

On Sun, 2023-05-21 at 00:43 -0400, Robert McBroom via users wrote:

Recently the f37 system is unable to access the internet. It accesses
the local network. The web page for the isp router is there and it
accesses my NAS. Tried a USB WIFI adapter and get the same situation.
Can connect to the router and the local network but nothing outside.
What setting is blocking the internet?

Do you manually configure networks, or is it automatic from DHCP?

It sounds like it's missing the gateway address (the address of your
path through to the internet, your router).


I let NetworkManager do its thing. The router address and the gateway 
address are the same. Compare the working system now at f38 to the 
problem system and see some differences with references to systemd and 
network-scripts. Looking with nm-connection-editor they booth seem to be 
the same. The old usage if ifcfg scripts seems to have changed.


~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref    Use 
Iface
default _gateway    0.0.0.0 UG    100    0    0 
eno1
192.168.1.0 0.0.0.0 255.255.255.0   U 100    0    0 
eno1
192.168.122.0   0.0.0.0 255.255.255.0   U 0  0    0 
virbr0


I don't understand what it is telling me about the gateway. _gateway is 
not a linux variable that is set. In the past used route to declare the 
gateway but that seems to have changed.


___
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

System networking confusion

[Robert McBroom via users]

System is a multiboot with three OS. Originally with win 10 and fedora 
36 then installed fedora 37 server on a nvme drive. The f37 server 
install created a separate /boot/efi.


Win 10 and Fedora 36 have full functioning access to the network.

Recently the f37 system is unable to access the internet. It accesses 
the local network. The web page for the isp router is there and it 
accesses my NAS. Tried a USB WIFI adapter and get the same situation. 
Can connect to the router and the local network but nothing outside.


What setting is blocking the internet?

___
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

Virtual Machine USB WIFI adapter

[Robert McBroom via users]

Fedora 38 host with CentOS8 in a virtual machine. Wrestling with 
networking. I would like to use a USB WIFI adapter dedicated to the 
virtual machine. The adapter works from the host. When added to the 
hardware of the virtual machine it is seen by NetworkManager but 
entering the SSID and password does not connect.


Tried restart with the set hardware configuration. NetworkManager shows 
the WIFI connection as "Last Used" never.


~]$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp3s0:  mtu 1500 qdisc fq_codel 
state UP group default qlen 1000

    link/ether 52:54:00:d0:98:95 brd ff:ff:ff:ff:ff:ff
3: virbr0:  mtu 1500 qdisc noqueue 
state DOWN group default qlen 1000

    link/ether 52:54:00:eb:41:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
   valid_lft forever preferred_lft forever

A virtual machine with Fedora 38 does not connect either even though the 
host does. There is no problem connecting to the adapter with that other 
operating system in a virtual machine.


Any ideas on getting a WIFI connection on a virtual machine?
___
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: FC38 - missing kernel-headers-6.2.12-300.fc38 in fedora-updates

[Robert McBroom via users]

On 4/25/23 09:40, Nils Smeds wrote:

Upgrading to FC38 I could not get a working kernel because akmod could not 
build the necessary tainted kernel modules for my NVidia card.

The only available kernel-header RPM is from the initial release kernel in the 
fedora repo
Which NVIDIA card? The AKMOD from rpmfusion WAS just updated for some of 
the legacy cards. For GEFORCE GT 710 and more recent cards they have 
worked from the start of the 6.2.x kernels

___
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: Virtual Machine Network Connection Confusion

[Robert McBroom via users]

On 4/4/23 12:44, Peter Boy wrote:

Am 04.04.2023 um 17:51 schrieb Robert McBroom via 
users:

Fedora 37 with four qemu/kvm virtual machines. Trying to get internet access 
from the vm's. Found some advice about using systemd-networkd instead of 
NetworkManager.

Following „some advice“ is usually a good chance for adventure. What was wrong 
with using Fedora documentation?

didn't find anything useful

  Lost internet connection with the host. Restored with NetworkManager. Further 
research on NetworkManager gets into a tangle with ifcfg scripts and the 
apparent migration to keyfiles.

Totally confused.

Can only start the virtual machines if the network device is removed.

--

VM centos8 failed to start

Requested operation is not valid: network 'default' is not active
-
 From cockpit on the web interface tried some of the options with bond looking 
like a possibility
-
11:37 AM
 [1680622647.3084] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34
NetworkManager
11:27 AM
 [1680622058.5768] manager: (vnet4): new Tun device 
(/org/freedesktop/NetworkManager/Devices/9)
NetworkManager
11:07 AM
 [1680620850.7934] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34
NetworkManager
11:02 AM
 [1680620556.1938] manager: (vnet3): new Tun device 
(/org/freedesktop/NetworkManager/Devices/8)
NetworkManager
11:01 AM
 [1680620475.6234] manager: (vnet2): new Tun device 
(/org/freedesktop/NetworkManager/Devices/7)
NetworkManager
10:40 AM
 [1680619204.0043] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34
NetworkManager

but

VM centos8 failed to start

Unable to add bridge bond0 port vnet5: Operation not supported
--

The options seem to be endless with no success.
Advice?


All these messages are nice, but meaningless for troubleshooting. The first 
thing is how the host was installed and how the network was configured, as a 
first start the output of „ip a“. The second one is, how you configured the 
virtual internet connection of a vm.


The host is a general use server installation with kde desktop added.

First round was from a virt-manager start with add hardware 
device->network. First selection "Virtual Network 
'default':NAT(Inactive)" with "Hypervisor default" That gave the message 
first quoted.


Requested operation is not valid: network 'default' is not active
The bridge setup selection in virt-manager didn't work either.

looked at the networking from cockpit. Got a connection on a vm from cockpit 
unable to replicate on a second. From the successful connection

from host

~]# ip a 1: lo:  mtu 65536 qdisc noqueue state 
UNKNOWN group default qlen 1000    link/loopback 00:00:00:00:00:00 brd 
00:00:00:00:00:00    inet 127.0.0.1/8 scope host lo   valid_lft 
forever preferred_lft forever    inet6 ::1/128 scope host 
  valid_lft forever preferred_lft forever 2: eno1: 
 mtu 1500 qdisc fq_codel master virbr0 
state UP group default qlen 1000    link/ether 18:60:24:b1:dc:82 brd 
ff:ff:ff:ff:ff:ff    altname enp0s25 6: virbr1: 
 mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000    link/ether 52:54:00:28:a4:bf brd 
ff:ff:ff:ff:ff:ff 20: virbr0:  mtu 1500 
qdisc noqueue state UP group default qlen 1000    link/ether 
b6:8e:92:80:04:f2 brd ff:ff:ff:ff:ff:ff    inet 192.168.1.155/24 brd 
192.168.1.255 scope global dynamic noprefixroute virbr0   valid_lft 
45172sec preferred_lft 45172sec    inet6 2600:1702:4860:9dd0::2b/128 
scope global dynamic noprefixroute   valid_lft 2904sec preferred_lft 
2904sec    inet6 2600:1702:4860:9dd0:f790:2432:acf9:c8e8/64 scope global 
dynamic noprefixroute   valid_lft 3601sec preferred_lft 3601sec 
   inet6 fe80::c7d1:6569:1c43:14ff/64 scope link noprefixroute 
  valid_lft forever preferred_lft forever 25: vnet2: 
 mtu 1500 qdisc noqueue master virbr0 
state UNKNOWN group default qlen 1000    link/ether fe:54:00:19:3b:a3 
brd ff:ff:ff:ff:ff:ff    inet6 fe80::fc54:ff:fe19:3ba3/64 scope link 
  valid_lft forever preferred_lft forever -- From VM _ ~]# 
ip a 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 
00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever 
preferred_lft forever inet6 ::1/128 scope host valid_lft forever 
preferred_lft forever 2: virbr0:  mtu 
1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 
52:54:00:eb:41:ac brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 
192.168.122.255 scope global virbr0 valid_lft forever preferred_lft 
forever 3: enp3s0:  mtu 1500 qdisc 
fq_codel state UP group default qlen 1000 link/ether 52:54:00:19:3b:a3 
brd ff:ff:ff:ff:ff:ff inet 192.168.1.167/24 brd 192.168.1.255 scope 
global dynamic noprefixroute enp3s0 valid_lft 45641sec preferred_lft 
45641sec inet6 2600:1702:4860:9dd0::3b/128 scope global dynamic 
noprefixroute valid_lft 2252sec preferred_lft 2252sec inet6 
2600:1

Virtual Machine Network Connection Confusion

[Robert McBroom via users]

Fedora 37 with four qemu/kvm virtual machines. Trying to get internet 
access from the vm's. Found some advice about using systemd-networkd 
instead of NetworkManager. Lost internet connection with the host. 
Restored with NetworkManager. Further research on NetworkManager gets 
into a tangle with ifcfg scripts and the apparent migration to keyfiles.


Totally confused.

Can only start the virtual machines if the network device is removed.


   --


   VM centos8 failed to start

Requested operation is not valid: network 'default' is not active
-
From cockpit on the web interface tried some of the options with bond 
looking like a possibility

-
11:37 AM
 [1680622647.3084] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34

NetworkManager
11:27 AM
 [1680622058.5768] manager: (vnet4): new Tun device 
(/org/freedesktop/NetworkManager/Devices/9)

NetworkManager
11:07 AM
 [1680620850.7934] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34

NetworkManager
11:02 AM
 [1680620556.1938] manager: (vnet3): new Tun device 
(/org/freedesktop/NetworkManager/Devices/8)

NetworkManager
11:01 AM
 [1680620475.6234] manager: (vnet2): new Tun device 
(/org/freedesktop/NetworkManager/Devices/7)

NetworkManager
10:40 AM
 [1680619204.0043] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34

NetworkManager

but



   VM centos8 failed to start

Unable to add bridge bond0 port vnet5: Operation not supported
--

The options seem to be endless with no success.
Advice?
___
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: Problems with New kernel 6.2.7

[Robert McBroom via users]

On 3/23/23 04:45, Qiyu Yan wrote:

在 2023/3/23 11:22, Robert McBroom via users 写道:

Total strangeness with the new kernel series on fedora 37. My update 
was from 6.1.14 to the 6.2.7, missing several editions. With the new 
kernel the display was only 1024x768 on the 27" monitor. Even though 
x11 is selected in the display-manager the system comes up in 
wayland. Settings says that the monitor does not support any thing 
but the 1024x768 resolution. Patently untrue. Reverted to the 6.1.14 
kernel.


Suspect that there is not a driver IN RPMFUSION for the geforce gt610 
ON THE 6.2.7 and getting thrown back to VGA, but why wayland?


If you are using driver from RPMFUSION is should be akmod driver that 
will be compiled every time you update your kernel, or to say, it is 
not really for a specific version.


But, it can be the problem if the kernel module compilation somehow 
failed on your machine with new kernel. There is something to confirm 
like is the output of


$ lsmod | grep -E "(nouveau|nvidia)"

If you get nouveau in the output, it can be the problem like new 
kernel module failed to compile for the new kernel.


Exactly, the 6.2.7 kernel doesn't compile from the akmod.

~]# lsmod | grep -E "(nouveau|nvidia)"
nouveau 3403776  0
mxm_wmi    16384  1 nouveau
video  73728  1 nouveau
wmi    45056  3 video,mxm_wmi,nouveau
drm_ttm_helper 16384  1 nouveau
ttm   102400  2 drm_ttm_helper,nouveau
drm_display_helper    200704  1 nouveau

As noted, reverted to earlier kernel.

rpm -qa|grep kmod
kmodtool-1.1-5.fc37.noarch
kmod-libs-30-2.fc37.x86_64
kmod-30-2.fc37.x86_64
akmods-0.5.7-9.fc37.noarch
xorg-x11-drv-nvidia-390xx-kmodsrc-390.157-2.fc37.x86_64
akmod-nvidia-390xx-390.157-1.fc37.x86_64
kmod-nvidia-390xx-390.157-1.fc37.x86_64
kmod-nvidia-390xx-6.1.10-200.fc37.x86_64-390.157-1.fc37.x86_64
kmod-nvidia-390xx-6.1.12-200.fc37.x86_64-390.157-1.fc37.x86_64
kmod-nvidia-390xx-6.1.13-200.fc37.x86_64-390.157-1.fc37.x86_64
kmod-nvidia-390xx-6.1.14-200.fc37.x86_64-390.157-1.fc37.x86_64

Not yet for 6.2 series kernels

___
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

Problems with New kernel 6.2.7

[Robert McBroom via users]

Total strangeness with the new kernel series on fedora 37. My update was 
from 6.1.14 to the 6.2.7, missing several editions. With the new kernel 
the display was only 1024x768 on the 27" monitor. Even though x11 is 
selected in the display-manager the system comes up in wayland. Settings 
says that the monitor does not support any thing but the 1024x768 
resolution. Patently untrue. Reverted to the 6.1.14 kernel.


Suspect that there is not a driver IN RPMFUSION for the geforce gt610 ON 
THE 6.2.7 and getting thrown back to VGA, but why wayland?


Is this the situation?
___
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 37 qemu/kvm Centos 8 virtual machine Problem

[Robert McBroom via users]

On 3/10/23 01:25, Peter Boy wrote:



Am 10.03.2023 um 07:00 schrieb Robert McBroom via 
users:


On 3/10/23 00:41, Jeffrey Walton wrote:

On Fri, Mar 10, 2023 at 12:36 AM Robert McBroom via users
  wrote:

Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially the
reboot went only to a blank display. Editing the grub menu to give a
terminal boot was successful.

Succeeded  to get a graphical screen with xinit and a terminal to
explore the options. Was able to install xfce for a graphical desktop
but gnome fails. The display managers gdm and sddm both fail with a
blank screen with the mouse cursor. The others lxdm and lighdm don't
show as being available.

How do I get the session to start properly?

I do not see a problem with Fedora 37. The guest seems to run Ok.
Perhaps a CentOS forum would be a better place for the question?

Or, install Fedora Server and stop putzing around with the antique
software RHEL and CentOS provides.

My apologies if I mis-parsed something.

Jeff

Fedora 37 is the host

Which Fedora variant?

I use server because it allows more freedom.


I just installed CentOS Stream cloud following the Fedora Server documentation 
(https://docs.fedoraproject.org/en-US/fedora-server/virtualization/vm-install-cloudimg-centos9/)
 and it works seamlessly.

Works for me also but I need CentOS 8 to run some legacy $$$ software.


What did you do exactly?


From virt-manager-> New virtual machine ->attached host 
~/Downloads/CentOS-Stream-8-x86_64-latest-dvd1.iso->booted install


switched boot to VirtIO Disk and rebooted to blank screen. Initially the 
network was set to bridge which did not connect. Changed to virtual 
network and from a terminal boot updated CentOS 8. Added xinit and xterm 
and was able to install xfce4, switchdesk. Desktop now starts from a 
terminal boot with startx.



Your description is typical of a mismatched console configuration between 
virtual machine properties and guest OS configuration and independent of Fedora 
or any specific Fedora release.


Compared the CentOS 8 machine to the CentOS 9 machine. CentOS 8 uses 
'Video Virtio' and 'Display Spice'. CentOS 9 uses 'Video VGA' and 
'Display VNC'. Tried changes to the CentOS 8 machine to the same but get 
an error about an "unsupported configuration: 'spicevmc' not supported 
without spice graphics". Compared the --qemu/centos8.xml file withthe 
--qemu/centos9.xml file. Understand some of the differences but not all.






  centos8
  a9cc9bad-4f7d-4c1a-9aed-97fd0464dca8
  
http://libosinfo.org/xmlns/libvirt/domain/1.0;>
  http://centos.org/centos/8"/>

  
  4644864
  4644864
  


  
  4
  
hvm

  
  



  
  
qemu64
  
  



  
  destroy
  restart
  destroy
  


  
  
/usr/bin/qemu-system-x86_64

  
  
  
  
  


  
  
  
  
  


  


  



  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  
  
  


  


  
  
  
  


  

  


  


  
  


  
  


  




  


  



  
  


  


  
  


  


  


  


  /dev/urandom
  

  

___
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 37 qemu/kvm Centos 8 virtual machine Problem

[Robert McBroom via users]

On 3/10/23 00:41, Jeffrey Walton wrote:

On Fri, Mar 10, 2023 at 12:36 AM Robert McBroom via users
 wrote:

Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially the
reboot went only to a blank display. Editing the grub menu to give a
terminal boot was successful.

Succeeded  to get a graphical screen with xinit and a terminal to
explore the options. Was able to install xfce for a graphical desktop
but gnome fails. The display managers gdm and sddm both fail with a
blank screen with the mouse cursor. The others lxdm and lighdm don't
show as being available.

How do I get the session to start properly?

I do not see a problem with Fedora 37. The guest seems to run Ok.
Perhaps a CentOS forum would be a better place for the question?

Or, install Fedora Server and stop putzing around with the antique
software RHEL and CentOS provides.

My apologies if I mis-parsed something.

Jeff

Fedora 37 is the host
___
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 37 qemu/kvm Centos 8 virtual machine Problem

[Robert McBroom via users]

Installed CentOS-STREAM 8 ON A QEMU/KVM virtual machine. Initially the 
reboot went only to a blank display. Editing the grub menu to give a 
terminal boot was successful.


Succeeded  to get a graphical screen with xinit and a terminal to 
explore the options. Was able to install xfce for a graphical desktop 
but gnome fails. The display managers gdm and sddm both fail with a 
blank screen with the mouse cursor. The others lxdm and lighdm don't 
show as being available.


How do I get the session to start properly?
___
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: Drivers for Realtec USB wifi adapters

[Robert McBroom via users]

On 2/28/23 23:04, Slade Watkins via users wrote:

On 2/23/23 12:30, Robert McBroom via users wrote:

I have two Realtec USB wifi adapters an rtl8812au and rtl8822bu. For a
while I tracked driver updates on git with varying degrees of success.
Haven't seen anything since the 5.6 kernels. There was some note about a
generalized driver but I don't see anything in ../kernel/drivers or get the
devices enabled on boot.

For your rtl8812au, I was able to track down
https://github.com/morrownr/8812au-20210629

For your rtl8822bu, https://github.com/morrownr/88x2bu-20210702

I'm not sure what kernel version you're running (on Fedora 37 I'm running
6.1.13) but it might be worth a shot, if you haven't tried either already?
They seem to have been updated fairly recently.

Might be worth asking the maintainers to get them into the kernel itself,
though...

Saw those from an earlier response and they have worked on updates to 
present. The readme notes that the drivers ae expected to be in the 6.2 
kernel.


Waiting expectantly
___
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

CentOS8 VM

[Robert McBroom via users]

Installed CentOS8 on a VM from

CentOS-8.1.1911-x86_64-dvd1.iso

Trying to update it gives

Failed to download metadata for repo 'appstream'
Error: Failed to download metadata for repo 'appstream'

I have the rpm's on a local repository but disabling the repos has no 
effect on the error and will no proceed with the update.


is there a fix?

___
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: Drivers for Realtec USB wifi adapters

[Robert McBroom via users]

On 2/24/23 04:45, t_pol wrote:

On Thu, 23 Feb 2023 12:30:21 -0500
Robert McBroom via users  wrote:


I have two Realtec USB wifi adapters an rtl8812au and rtl8822bu. For a
while I tracked driver updates on git with varying degrees of success.
Haven't seen anything since the 5.6 kernels. There was some note about a
generalized driver but I don't see anything in ../kernel/drivers or get
the devices enabled on boot.

Has anyone had any updates on these devices?

]# lsusb
Bus 001 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu
[AC1200 Techkey]


I have a similar adapter:

Bus 001 Device 006: ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]

Indeed it's annoying to keep it up to date.
I do it every kernel update cloning "...github.com/morrownr/88x2bu-20210702" and
re-installing the driver,
The 'dkms' installation script works fine,

Ciao
Installation was successful. The readme indicates the driver is to be in 
the 6.2 kernels. I see there is a companion driver for the rtl8812au

___
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: Drivers for Realtec USB wifi adapters

[Robert McBroom via users]

On 2/24/23 04:45, t_pol wrote:

On Thu, 23 Feb 2023 12:30:21 -0500
Robert McBroom via users  wrote:


I have two Realtec USB wifi adapters an rtl8812au and rtl8822bu. For a
while I tracked driver updates on git with varying degrees of success.
Haven't seen anything since the 5.6 kernels. There was some note about a
generalized driver but I don't see anything in ../kernel/drivers or get
the devices enabled on boot.

Has anyone had any updates on these devices?

]# lsusb
Bus 001 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu
[AC1200 Techkey]


I have a similar adapter:

Bus 001 Device 006: ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]

Indeed it's annoying to keep it up to date.
I do it every kernel update cloning "...github.com/morrownr/88x2bu-20210702" and
re-installing the driver,
The 'dkms' installation script works fine,

Ciao
Thanks, I did not find that source. It seems to be active and more up to 
date. Will try it out.

___
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

Drivers for Realtec USB wifi adapters

[Robert McBroom via users]

I have two Realtec USB wifi adapters an rtl8812au and rtl8822bu. For a 
while I tracked driver updates on git with varying degrees of success. 
Haven't seen anything since the 5.6 kernels. There was some note about a 
generalized driver but I don't see anything in ../kernel/drivers or get 
the devices enabled on boot.


Has anyone had any updates on these devices?

]# lsusb
Bus 001 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu 
[AC1200 Techkey]


___
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: connecting using wireless usb

[Robert McBroom via users]

On 2/15/23 22:39, Bill Cunningham wrote:
Does anyone have any idea how to turn on wireless from the cli? ip add 
is extremely complicated as well as ifconfig which is I guess 
deprecated. I had to reinstall everything and it was detected when 
rebooting no wifi. Can I get online in a simple manner. One can I 
guess use iw somehow too. I have only used fedora with an ethernet, 
now I am having to use wifi.
What wireless usb are you using? Drivers can be a major problem. Many 
long stories with Realtec

___
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: lxd on Fedora for virtual machine

[Robert McBroom via users]

On 1/31/23 06:06, Patrick O'Callaghan wrote:

On Tue, 2023-01-31 at 00:00 -0500, Robert McBroom via users wrote:

I see discussions of container tech with lxd and docker on ubuntu.
dnf
will install docker. Anyone have experience with a windows virtual
machine with these systems?

If you mean running a Windows VM with a container as the hypervisor,
AFAIK that's not possible. A container is much lighter than a full VM
environment and won't in general allow emulation of a completely
different OS, which is one reason they are popular.


There is a tutorial for ubuntu,

https://ubuntu.com/tutorials/how-to-install-a-windows-11-vm-using-lxd#1-overview
___
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

lxd on Fedora for virtual machine

[Robert McBroom via users]

I see discussions of container tech with lxd and docker on ubuntu. dnf 
will install docker. Anyone have experience with a windows virtual 
machine with these systems?

___
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: Installed Fedora 37 on older Dell with Windows 10, but doen't show windows as boot option??

[Robert McBroom via users]

Michael

Have a Dell Studio XPS system of about that vintage that has migrated 
from Windows 7 to version 10. Migrated from the original disk drive to 
an SSD. No problem with accessing the windows system from Fedora 37. The 
system predates the uefi bios. Have three drives with different os on 
each one. The fedora os's boot from the files in /boot and /boot/loader 
with the windows os as a stanza in /boot/grub2/grub.cfg from 
/etc/grub.d/40_custom. Windows is still on a MBR drive while the other 
two are GPT.


Robert

PS Graduated before my school got a hard drive for the IBM 1130

On 1/10/23 09:18, Michael D. Setzer II via users wrote:

On 10 Jan 2023 at 8:16, Go Canes wrote:

From:   Go Canes
Date sent:  Tue, 10 Jan 2023 08:16:05 -0500
Subject:Re: Installed Fedora 37 on older Dell with
Windows 10, but doen't
show windows as boot option??
To: mi...@guam.net,
Community support for Fedora users

Send reply to:  Community support for Fedora
users


On Tue, Jan 10, 2023 at 2:08 AM Michael D. Setzer II via users
  wrote:

Don't use windows much at all. So probable not worth doing for me. Windows was 
pre-install so have no windows media, and would have to find method to get the 
key code.

Do a google search for "download windows 10 iso" and there are links
to download the install media directly from Microsoft.

Older Dell systems had a sticker with the Windows license key.  You
can use "sudo strings /sys/firmware/acpi/tables/MSDM" to extract a
license key that is embedded in the firmware.  There is also a Windows
program I have used that extracts the license key along with other
useful info, but I don't remember what it is, and I don't have any of
my Windows VM booted at the moment.

Strange.. Looked all over the machine, and Only 2
stickers I find on machine are one that says Windows 7,
and another one that says Intel i5 inside??
But when I got machine, it had Windows 10 installed,
and CPU-z and lshw-gui both show the CPU as an i3 not
an i5? Think I've used belarc advisor before and think it
actually displays the windows key. Think it is Optiplex
9020 small form..

Since the Windows 10 was installed on regular bios boot,
don't think the firmware would have any info. Just had a
small sda1partition with recovery, and sda2 was the c
drive on the 1T drive with 8G of ram. Had done a check
on upgrading cpu, but the socket and bios it reported
wouldn't support above the i3, or above the  chips
generation. Recently upgraded CPU in one of my ASUS
motherboards from and AMD 2 core to AMD 8 core with
no issues. Did require a much better fan to keep temp
down. First computer was a Heathkit H-120 with 8088
and 8080 cpus. Had 768K of Ram with separate video
board with 192K of ram from video. Way back in 1983.
Old dos 1 with dual 320K floppies. So, lots of changes
over years..

Thanks for info.




___
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

++
  Michael D. Setzer II - Computer Science Instructor
(Retired)
  mailto:mi...@guam.net 
  mailto:msetze...@gmail.com

  Guam - Where America's Day Begins
  G4L Disk Imaging Project maintainer
  http://sourceforge.net/projects/g4l/
++


___
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

Re: need perm. fix for monitor/display problem.

[Robert McBroom via users]

On 12/15/22 16:03, home user wrote:

On 12/15/22 9:09 AM, Robert McBroom via users wrote:

On 12/14/22 22:45, home user wrote:

[... snip ...]
 set /etc/dnf.conf to retain the kernels of several updates to give 
rpmfusion time to catch up to new kernels in a new major grouping. 
Can take a couple of weeks.


[main]
gpgcheck=1
installonly_limit=5
max_parallel_downloads=10
fastestmirror=True
clean_requirements_on_remove=true
keepcache=0



No such file...
--
-bash.9[~]: cat /etc/dnf.conf
cat: /etc/dnf.conf: No such file or directory
-bash.10[~]:
--
Do you mean /etc/dnf/dnf.conf?...
--
-bash.10[~]: cat /etc/dnf/dnf.conf
# see `man dnf.conf` for defaults and possible options

[main]
gpgcheck=True
installonly_limit=3
clean_requirements_on_remove=True
best=False
skip_if_unavailable=True
-bash.11[~]:
--
Is your suggestion to edit the "installonly_limit" value?  If yes, is 
my current setting (3) of that value sufficient?


I am not clear on what you mean by "in a new major grouping".  Has RPM 
Fusion already caught up to the current f36 kernel (6.0.5-200.fc36 or 
whatever is now current) in a way that fixes the problems I 
encountered on Nov. 03?


Current kernel is up to 6.0.12 going from 6.0.5 to current has tracked 
without a problem of the drivers with rpmfusion. The change from 5 to 6 
is the major kernel change where driver delays typically but not 
exclusively occur.

___
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: need perm. fix for monitor/display problem.

[Robert McBroom via users]

On 12/14/22 22:45, home user wrote:
f36; workstation is 9 years old; dual boot (the other OS is the nearly 
useless windows-7); dual monitor; stand-alone (not a part of a LAN, 
WAN, etc.); I don't have other hardware to fall back on, not even a 
cell phone; nvidia geforce gtx 660 graphics card; driver is from RPM 
Fusion non-free.


Note: I have no training or significant experience in sys. admin.

original problem:
On Nov. 03, I did my weekly "dnf upgrade".  This resulted in only one 
monitor working, and the display on that monitor looking fuzzy and 
horizontally stretched out.


diagnosis (from the Fedora users list):
The driver version installed by the "dnf upgrade" is not compatible 
with the latest kernel and needs updating.  The kernel version was 
6.0.5-200.fc36.  The fixed nvidia 470 drivers were still in testing.


work-around until fixed nvidia 470 drivers pass testing and reach 
rpmfusion-nonfree-updates (from the Fedora users list):

1. back-up the initrd being used before the Nov. 03 "dnf upgrade".
2. use the kernel in use (5.19) before the Nov. 03 "dnf upgrade".
The recommended back-up was done on Nov. 04.  I've been using the 5.19 
kernel exclusively since then.  I have not run "dnf upgrade" since 
Nov. 03.


current situation:
I'm using the 5.19 kernel exclusively.
I have not run "dnf upgrade" since Nov. 03.
The RPM Fusion web site page
"https://mirror.fcix.net/rpmfusion/nonfree/fedora/updates/36/x86_64/repoview/index.html; 
now shows this...

---
Latest packages:

    2022-11-29: nvidia-settings-470xx-470.161.03-1.fc36
    2022-11-29: akmod-nvidia-470xx-470.161.03-1.fc36
    2022-11-29: kmod-nvidia-470xx-470.161.03-1.fc36
    2022-11-29: xorg-x11-drv-nvidia-470xx-470.161.03-1.fc36
    2022-11-29: xorg-x11-drv-nvidia-470xx-cuda-470.161.03-1.fc36
    2022-11-29: xorg-x11-drv-nvidia-470xx-cuda-libs-470.161.03-1.fc36
    2022-11-29: xorg-x11-drv-nvidia-470xx-devel-470.161.03-1.fc36
    2022-11-29: xorg-x11-drv-nvidia-470xx-kmodsrc-470.161.03-1.fc36
    2022-11-29: xorg-x11-drv-nvidia-470xx-libs-470.161.03-1.fc36
    2022-11-29: xorg-x11-drv-nvidia-470xx-power-470.161.03-1.fc36
(and other things not relevant to this issue)
---

The original problem left my workstation quite crippled.  It took a 
lot of time and effort to research, construct, and post messages in 
the original list thread.  I don't have other hardware to fall back 
on, not even a cell phone.  Proceeding with the fix to the problem 
strikes me as risky.


first question:
Is what is currently in RPM Fusion non-free 36 updates everything I 
need to really fix the problem for f36?


Please don't jump the gun.  Just answer that first question.  If the 
answer is positive, I'll follow up with more questions.


further information:
Anyone wanting to view the original Nov. 03-04 thread, it's here:
"https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/X6QCDYEIFO7DKZE5ENCHBCW776TC26WF/;. 



Thank-you in advance.
Bill. 
 set /etc/dnf.conf to retain the kernels of several updates to give 
rpmfusion time to catch up to new kernels in a new major grouping. Can 
take a couple of weeks.


[main]
gpgcheck=1
installonly_limit=5
max_parallel_downloads=10
fastestmirror=True
clean_requirements_on_remove=true
keepcache=0


I have a system with a gtx 610 which uses the even older 390xx drivers. 
Another uses the gt 710 with the 470xx drivers, both have been updated 
on rpmfusion for weeks. Upgrades to f37 went smoothly


___
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: Weird selinux message

[Robert McBroom via users]

On 12/7/22 13:04, Jeffrey Walton wrote:

On Wed, Dec 7, 2022 at 11:16 AM Robert McBroom via users
  wrote:

SELinux is preventing gdb from read access on the chr_file pcmC0D0p.

What would call debug on boot sequence?

More information may be found in /var/log/audit/audit.log. `sealert -l
"*"` might also provide more information.

I think chr_file is part of a SELinux macro. I'm not used to seeing it
in an alert. Is that rule Ok?

Maybe relabel the filesystem with `fixfiles -B onboot`?

Jeff


There is nothing in audit.log referring to any of the files or processes 
in the alerts.


I've run the relabel command several times and the alerts are still there.

~]# sealert -l "*"
SELinux is preventing gdb from read access on the chr_file pcmC0D0p.

*  Plugin catchall (100. confidence) suggests 
  **


If you believe that gdb should be allowed read access on the pcmC0D0p 
chr_file by default.

Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'gdb' --raw | audit2allow -M my-gdb
# semodule -X 300 -i my-gdb.pp


Additional Information:
Source Context    system_u:system_r:abrt_t:s0-s0:c0.c1023
Target Context    system_u:object_r:sound_device_t:s0
Target Objects    pcmC0D0p [ chr_file ]
Source    gdb
Source Path   gdb
Port  
Host  RobertPC.attlocal.net
Source RPM Packages
Target RPM Packages
SELinux Policy RPM    selinux-policy-targeted-35.11-1.fc35.noarch
Local Policy RPM  selinux-policy-targeted-35.11-1.fc35.noarch
Selinux Enabled   True
Policy Type   targeted
Enforcing Mode    Permissive
Host Name RobertPC.attlocal.net
Platform  Linux RobertPC.attlocal.net
 5.15.16-200.fc35.x86_64 #1 SMP Thu Jan 20 
15:38:18

 UTC 2022 x86_64 x86_64
Alert Count   2
First Seen    2022-01-30 01:27:15 EST
Last Seen 2022-01-30 01:31:02 EST
Local ID  ecbe31dd-1a2a-4daf-bd46-8ef565e6b227

Raw Audit Messages
type=AVC msg=audit(1643524262.137:695): avc:  denied  { read } for 
 pid=74330 comm="gdb" name="pcmC0D0p" dev="devtmpfs" ino
=532 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 
tcontext=system_u:object_r:sound_device_t:s0 tclass=chr_file permissi

ve=1


Hash: gdb,abrt_t,sound_device_t,chr_file,read

SELinux is preventing gdb from open access on the chr_file 
/dev/snd/pcmC0D0p.


*  Plugin catchall (100. confidence) suggests 
  **


If you believe that gdb should be allowed open access on the pcmC0D0p 
chr_file by default.

Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'gdb' --raw | audit2allow -M my-gdb
# semodule -X 300 -i my-gdb.pp


Additional Information:
Source Context    system_u:system_r:abrt_t:s0-s0:c0.c1023
Target Context    system_u:object_r:sound_device_t:s0
Target Objects    /dev/snd/pcmC0D0p [ chr_file ]
Source    gdb
Source Path   gdb
Port  
Host  RobertPC.attlocal.net
Source RPM Packages
Target RPM Packages
SELinux Policy RPM    selinux-policy-targeted-35.11-1.fc35.noarch
Local Policy RPM  selinux-policy-targeted-35.11-1.fc35.noarch
Selinux Enabled   True
Policy Type   targeted
Enforcing Mode    Permissive
Host Name RobertPC.attlocal.net
Platform  Linux RobertPC.attlocal.net
 5.15.16-200.fc35.x86_64 #1 SMP Thu Jan 20 
15:38:18

 UTC 2022 x86_64 x86_64
Alert Count   2
First Seen    2022-01-30 01:27:15 EST
Last Seen 2022-01-30 01:31:02 EST
Local ID  fdbfada1-c6ac-42a3-990d-f574024ef660

Raw Audit Messages
type=AVC msg=audit(1643524262.137:696): avc:  denied  { open } for 
 pid=74330 comm="gdb" path="/dev/snd/pcmC0D0p" dev="devt
mpfs" ino=532 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 
tcontext=system_u:object_r:sound_device_t:s0 tclass=chr_file

permissive=1


Hash: gdb,abrt_t,sound_device_t,chr_file,open

___
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/arc

Weird selinux message

[Robert McBroom via users]

SELinux is preventing gdb from read access on the chr_file pcmC0D0p.

What would call debug on boot sequence?
___
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: monitor/display problem.

[Robert McBroom via users]

On 11/5/22 14:30, stan via users wrote:

On Fri, 4 Nov 2022 12:27:21 -0600
home user  wrote:
  

Am I correct in assuming that I should not do weekly patches until
the proper updated NVidia 470 drivers reach rpmfusion-nonfree-updates?

Since the next update of the nvidia 470 drivers will probably be to
fix this issue, it should be okay to do so.  If you want to avoid
updates until certain, you could use
dnf -x [nvidia driver]
so it doesn't update.


How will I know when the proper updated NVidia 470 drivers reach
rpmfusion-nonfree-updates?

You could go to the website and look at the versions in their
repositories, or subscribe to their mailing list at rpmfusion.org.  They
send out emails with pending updates.

See a new 470 driver with dnf update. No 390 for legacy nvidia card as yet.
___
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: Nouveau Blacklisting not in /etc/default/grub

[Robert McBroom via users]

On 11/1/22 16:46, Barry Scott wrote:



On 1 Nov 2022, at 11:53, greg  wrote:

On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris  wrote:

I've just managed to get the 6.0.5 kernel to load the nvidia driver.
There is potentially a defect in the akmod-nvidia (or relevant package)
scripts in that it seems that they no longer add the blacklisting
statements for nouveau into the kernel parameters in /etc/default/grub,
I had to put those statements in there manually before the nvidia driver
was loaded instead of the nouveau driver.

I think it is because it is no longer needed. My memory on this prompted by 
reply in another thread.
If nvidia fails to be available, not install or did not build, then nouveau is 
used.

Barry


/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=
which refers to
/boot/loader/entries/.conf
which contains kernel options for the entry (which are actually used)
which get modified when editing kernel options via grub menu (thus becom
ing persistent)

/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault


Things seem to be in quite a mess. The grub.cfg file is almost 
irrelevant with only the Windows chainloader stanza having any meaning. 
It doesn't get updated with new kernals. Only 
/boot/loader/entries/*.conf. With the appropriate entries in /boot and 
/boot/loader/entries/*.conf multiple fedora invocations and centOS8 show 
in the menu and are boot-able. Not sure where blscfg comes in to the 
process. Dynamic change is far out stripping documentation.


___
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: grub2 Question

[Robert McBroom via users]

On 10/31/22 17:26, Felix Miata wrote:

Robert McBroom via users composed on 2022-10-31 17:17 (UTC-0400):


Running Fedora 35 and trying to fix installed boot files on a third drive.
~]# grub2-install /dev/sdc
grub2-install: error: this utility cannot be used for EFI platforms
because it does not support UEFI Secure Boot.
Secure Boot is turned off in the bios. The boot is from UEFI.

MBR is not a component of UEFI booting. The UEFI BIOS looks to the \EFI 
directory
on the ESP partition. Instead of grub2-install, do:

dnf reinstall grub2-efi grub2-efi-modules shim

after appropriately following the directions on
<https://forums.fedoraforum.org/showthread.php?313609-How-to-reinstall-Grub-EFI-in-Fedora-with-Fedora-Workstation-Live-media>


No mention of MBR as the drive is GPT. Totally UEFI system, four drives 
three OS. I was suspecting a problem with the boot sector, but on 
removal of all drives but the one, it boots. Adding the drives one by 
one to see the point of digression.

___
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