Re: isues with f40 install

[Stephen Morris]

On 5/7/24 02:29, François Patte wrote:

Le 2024-07-04 18:18, Mike Wright a écrit :

On 7/4/24 09:09, François Patte wrote:

Should I understand that if you have a windows installation on a 
disk with some (big) space left, you cannot install f40 as a dual 
boot system? (because anaconda is unable to ignore the windows 
partition)


I *think* that there can be only one /boot/efi partition on a disk.


So how can we proceed when you want a dual (fedora/fedora, 
fedora/debian, fedora.ubuntu) boot on the same disk?


I am booting between Windows 11, Fedora f40 and Ubuntu 22.04 with a 
single 100MB efi partition on an SSD, which is being used by all 3 
operating systems, where the installation of each system installs the 
efi components in a folder on that partition named for the operation system.
When installing Fedora and Ubuntu I pointed the installer at the efi 
partition with mount point /boot/efi, also with two separate partitions 
on the SSD for Fedora /boot and Ubuntu /boot.

For both Fedora and Ubuntu I have the / partition on separate HDD's.


regards,

Steve



OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 40 Mate ALMOST can't be installed

[Samuel Sieb]

On 7/5/24 6:36 AM, Tide Ka via users wrote:

On 7/5/24 3:22 AM, Tim via users wrote:


So I typed sync, and that stayed doing something until the
flashdrive stopped blinking, then the cursor returned immediately.  So,
I'm tempted to think that the caching delay was part of the OS rather
than the drive. 


Your reaction is likely to be right. There is cache in the OS. And it is 
causing sync to block for a while.


Samuel Sieb:

 >> The writing is finished when dd exits, but the drive might keep 
flashing

 >> briefly after that.  Or maybe the drive has some internal caching that
 >> it doesn't advertise (that would be very bad).

I have gone through man pages of `dd` and find executing `sync` right 
after the writing finished may not be enabled by default. That requires 
passing `oflag=sync` or passing nocache to `conv=`, but non of the above 
is done in the command you provided. I guess probably dd did leave 
kernel cache behind and exit.


Running `sync` and just wait for lights to not blink any more is always 
very wise. And it also indicates that your installation medium is 
probably OK.


I just tested this:
# dd if=Fedora-MATE_Compiz-Live-x86_64-40-1.14.iso of=/dev/sda bs=4M 
status=progress

2332033024 bytes (2.3 GB, 2.2 GiB) copied, 2 s, 1.2 GB/s
585+1 records in
585+1 records out
2454198272 bytes (2.5 GB, 2.3 GiB) copied, 302.866 s, 8.1 MB/s

The first "copied" line is from the progress status.  After it got to 
there, it sat there until all the data was actually written to the 
drive, at which point it wrote the last 3 lines including the real write 
speed.


--
___
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: issue with f40 installer [2]

[François Patte]

Le 2024-07-06 23:20, Samuel Sieb a écrit :

On 7/6/24 3:13 AM, François Patte wrote:

Le 2024-07-06 09:43, Mike Wright a écrit :

On 7/6/24 00:37, François Patte wrote:

Bonjour,

On another post I complained that I couldn't install f40 due, I 
thought, to existing partitions on a disk...


I tried to install on new disks without anything on them and used 
blivet-gui to define the partitions: I want RAID1 arrays, so I 
defined each of them asking for RAID1 on two disks and ext4 or luks 
file system.


Here is the error message given when I press the Done button:

https://www.bertuccio.homelinux.net/IMG_20240705_194641.jpg

It is in French, I am sorry but I think that it understable

The song is "device RAID cannot be of luks type, ext4 type...  
device RAID cannot be mounted on device /boot/efi,... partition EFI 
cannot be of type mdmember and so on...


It is telling you that it wants a separate partition for /boot/efi 
and

that separate partition cannot be part of a raid array.


Thank you for answering.

I changed my config and defined a separate partition boot-efi, and the 
message is still the same.


Here what I have done:

sda1  file system boot-efi mounted on /boot


That is not correct.  You need a FAT32 EFI partition mounted at 
/boot/efi.


The installer offer boot efi as a partition and does not say anything 
about the file system nor it says what should be the mount point!


I'll try /boot/efi next time.

Thank you.

--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte
--
___
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: issue with f40 installer [2]

[Samuel Sieb]

On 7/6/24 3:13 AM, François Patte wrote:

Le 2024-07-06 09:43, Mike Wright a écrit :

On 7/6/24 00:37, François Patte wrote:

Bonjour,

On another post I complained that I couldn't install f40 due, I 
thought, to existing partitions on a disk...


I tried to install on new disks without anything on them and used 
blivet-gui to define the partitions: I want RAID1 arrays, so I 
defined each of them asking for RAID1 on two disks and ext4 or luks 
file system.


Here is the error message given when I press the Done button:

https://www.bertuccio.homelinux.net/IMG_20240705_194641.jpg

It is in French, I am sorry but I think that it understable

The song is "device RAID cannot be of luks type, ext4 type...  device 
RAID cannot be mounted on device /boot/efi,... partition EFI cannot 
be of type mdmember and so on...


It is telling you that it wants a separate partition for /boot/efi and
that separate partition cannot be part of a raid array.


Thank you for answering.

I changed my config and defined a separate partition boot-efi, and the 
message is still the same.


Here what I have done:

sda1  file system boot-efi mounted on /boot


That is not correct.  You need a FAT32 EFI partition mounted at /boot/efi.

--
___
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: VirtualBox does not run on Wayland

[Samuel Sieb]

On 7/6/24 11:07 AM, Jeffrey Walton wrote:

Yeah, Wayland is not quite ready for prime time. It is still missing
features. I do my best to avoid it.

(This is one of the most important features (for me). X11 has it,
Wayland does not: ).


To be clear, that's a KDE issue, not Wayland.  Gnome supports that 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: VirtualBox does not run on Wayland

[Jeffrey Walton]

On Sat, Jul 6, 2024 at 4:51 AM Frédéric  wrote:
>
> It took me a while to understand that Wayland was the source of my
> problem so I share my experience so that others can be quicker to
> solve this issue.
>
> I moved to F40 and Plasma came only with Wayland. Then, everything
> seemed OK apart that my Windows VM running in VirtualBox did not
> capture the mouse (quite annoying!). I run VirtualBox 7.0.18-1.fc40
> from rpmfusion-free-updates.
>
> I tried all options for the mouse (PS/2 mouse, USB tablet, multi-touch
> USB tablet and USB MT TouchScreen and TouchPad) but nothing worked.
> The VirtualBox menu above the VM was also not accessible.
>
> After one week of research, I found this post:
> https://askubuntu.com/questions/1512787/ubuntu-22-04-2-virtualbox-7-0-18-captured-mouse-is-not-contained-when-integrat
>
> and installed plasma-workspace-x11. I now run X11 Plasma and
> VirtualBox works fine.

Yeah, Wayland is not quite ready for prime time. It is still missing
features. I do my best to avoid it.

(This is one of the most important features (for me). X11 has it,
Wayland does not: ).

Jeff
-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: apache won't start after upgrade - read-only filesystem

[Jonathan Billings]

On Jul 5, 2024, at 13:40, Alex  wrote:Hi,> I've just upgraded from fedora38 to fedora39 and directly to fedora40 and now  
> apache won't start:
>
>
> (30)Read-only file system: AH00091: httpd: could not open error log file  
> /home/httpd/http://www.mysite.com/logs/error_log>www.mysite.com/logs/err 
> or_log.
> AH00015: Unable to open logs
>
>
>
> It has something to do with /home, as it seems it is unable to write anywhere  
> on /home, even after changing the document root for any virtual host to  
> various directories on /home it still fails with the same message, even  
> though I'm confident the path exists and is writable.

I know exactly what this is. I ran into it myself. Say hello to systemd:

ProtectHome=read-only

Do:

systemctl edit httpd

And add:

[Service]
ProtectHome=false

This'll turn this whole thing off.That indeed was the fix. Thanks so much. That's crazy.Do you have any idea why this option isn't part of the systemd service file on the other systems I upgraded? The document root for the other systems uses/var/www, but they didn't have this problem, and their home directories are also defined with this path.I'll work on moving the logs out of the same general tree as the document root, but this seems like a big change. Maybe I missed it in the changelog?This change is largely because it protects user home directories from malicious httpd attacks against poorly written executable code that would allow remote login (such as dropping a pubkey into a user’s authorized_keys) or by altering an admin’s login environment (replacing their .bashrc). Running web sites out of /home is still possible, they just can’t also write to /home.-- Jonathan Billings-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: VirtualBox does not run on Wayland

[John Pilkington]

On 06/07/2024 09:50, Frédéric wrote:

Hi,

It took me a while to understand that Wayland was the source of my
problem so I share my experience so that others can be quicker to
solve this issue.

I moved to F40 and Plasma came only with Wayland. Then, everything
seemed OK apart that my Windows VM running in VirtualBox did not
capture the mouse (quite annoying!). I run VirtualBox 7.0.18-1.fc40
from rpmfusion-free-updates.

I tried all options for the mouse (PS/2 mouse, USB tablet, multi-touch
USB tablet and USB MT TouchScreen and TouchPad) but nothing worked.
The VirtualBox menu above the VM was also not accessible.

After one week of research, I found this post:
https://askubuntu.com/questions/1512787/ubuntu-22-04-2-virtualbox-7-0-18-captured-mouse-is-not-contained-when-integrat

and installed plasma-workspace-x11. I now run X11 Plasma and
VirtualBox works fine.

Thanks,

F


plasma-workspace-x11 in F40 may be auto-erased by later kde updates. 
Playground dispute.


https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/thread/M45QTYTM52LQNMJCW5UX3VQYQHDWUV42/

John P

--
___
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: VirtualBox does not run on Wayland

[Sérgio Basto]

Hi,
Thank you for the report 

On Sat, 2024-07-06 at 10:50 +0200, Frédéric via rpmfusion-users wrote:
> Hi,
> 
> It took me a while to understand that Wayland was the source of my
> problem so I share my experience so that others can be quicker to
> solve this issue.
> 
> I moved to F40 and Plasma came only with Wayland. Then, everything
> seemed OK apart that my Windows VM running in VirtualBox did not
> capture the mouse (quite annoying!). I run VirtualBox 7.0.18-1.fc40
> from rpmfusion-free-updates.

Running VirtualBox as server ? and what are the guest systems ? 


> I tried all options for the mouse (PS/2 mouse, USB tablet, multi-
> touch
> USB tablet and USB MT TouchScreen and TouchPad) but nothing worked.
> The VirtualBox menu above the VM was also not accessible.
> 
> After one week of research, I found this post:
> https://askubuntu.com/questions/1512787/ubuntu-22-04-2-virtualbox-7-0-18-captured-mouse-is-not-contained-when-integrat
> 
> and installed plasma-workspace-x11. I now run X11 Plasma and
> VirtualBox works fine.
> 
> Thanks,
> 
> F
> ___
> rpmfusion-users mailing list -- rpmfusion-us...@lists.rpmfusion.org
> To unsubscribe send an email to
> rpmfusion-users-le...@lists.rpmfusion.org

-- 
Sérgio M. B.
-- 
___
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: issue with f40 installer [2]

[François Patte]

Le 2024-07-06 09:43, Mike Wright a écrit :

On 7/6/24 00:37, François Patte wrote:

Bonjour,

On another post I complained that I couldn't install f40 due, I 
thought, to existing partitions on a disk...


I tried to install on new disks without anything on them and used 
blivet-gui to define the partitions: I want RAID1 arrays, so I defined 
each of them asking for RAID1 on two disks and ext4 or luks file 
system.


Here is the error message given when I press the Done button:

https://www.bertuccio.homelinux.net/IMG_20240705_194641.jpg

It is in French, I am sorry but I think that it understable

The song is "device RAID cannot be of luks type, ext4 type...  device 
RAID cannot be mounted on device /boot/efi,... partition EFI cannot be 
of type mdmember and so on...


It is telling you that it wants a separate partition for /boot/efi and
that separate partition cannot be part of a raid array.


Thank you for answering.

I changed my config and defined a separate partition boot-efi, and the 
message is still the same.


Here what I have done:

sda1  file system boot-efi mounted on /boot
sd[ab]2 RAID1 file system ext4 mounted on /
sd[ab]3 RAID1 file system swap
sd[ab]4 RAID1 file system ext4 mounted on /var
sd[ab]5 RAID1 file system luks mounted on /crypt
sd[ab]6 RAID1 file system ext4 mounted on /home


Disks are 4Tib. I suppose that anaconda will define GPT partitions as I 
did not see any options allowing to choose this way.


I did not see any option allowing to define primary or extended 
partitions


I did not see any option allowing to combine RAID1 and lvm (which I 
would like to do!).


Thank you for attention.

--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte
--
___
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 ShareHost Files With KVM

[ToddAndMargo via users]

On 6/27/24 03:25, ToddAndMargo via users wrote:

On 6/26/24 01:09, ToddAndMargo via users wrote:

Hi All,

Fedora 39
qemu-kvm-8.1.3-5.fc39.x86_64
virt-manager-4.1.0-3.fc39.noarch

Windows 11

How do I Share Host Files (Fedora 39) with
Windows 11 (client) with KVM?

I have been reading this virt-manager how to:
 https://chrisirwin.ca/posts/sharing-host-files-with-kvm/

He is leaving out how to mount in Windows
and his "Filesystem Passthrough"

https://chrisirwin.ca/posts/sharing-host-files-with-kvm/add-filesystem.png
is a lot different than mine
 https://imgur.com/pqPcLo0.png

Anyone have a better howto?
-T


Found a much better How To:

Share Files Between the KVM Host and Windows Guest Using Virtiofs

https://sysguides.com/share-files-between-the-kvm-host-and-windows-guest-using-virtiofs


And it is working beautifully


But only in Windows 11.

In Windows 10 and 7, winfsp-2.0.23075 installs something
called
 "WinFsp.Launcher"
which fired off to
 "C:\Program Files 
(x86)\WinFsp\SxS\sxs.20240706T091144Z\bin\launcher-x64.exe"


And no shared drive

In windows 11, winfsp-2.0.23075 installs
 "VirtioFsSvc"
which fires off
 "C:\Program Files\Virtio-Win\VioFS\virtiofs.exe"

And sharing works well.

What the heck
-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

VirtualBox does not run on Wayland

[Frédéric]

Hi,

It took me a while to understand that Wayland was the source of my
problem so I share my experience so that others can be quicker to
solve this issue.

I moved to F40 and Plasma came only with Wayland. Then, everything
seemed OK apart that my Windows VM running in VirtualBox did not
capture the mouse (quite annoying!). I run VirtualBox 7.0.18-1.fc40
from rpmfusion-free-updates.

I tried all options for the mouse (PS/2 mouse, USB tablet, multi-touch
USB tablet and USB MT TouchScreen and TouchPad) but nothing worked.
The VirtualBox menu above the VM was also not accessible.

After one week of research, I found this post:
https://askubuntu.com/questions/1512787/ubuntu-22-04-2-virtualbox-7-0-18-captured-mouse-is-not-contained-when-integrat

and installed plasma-workspace-x11. I now run X11 Plasma and
VirtualBox works fine.

Thanks,

F
-- 
___
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: issue with f40 installer [2]

[Mike Wright]

On 7/6/24 00:37, François Patte wrote:

Bonjour,

On another post I complained that I couldn't install f40 due, I thought, 
to existing partitions on a disk...


I tried to install on new disks without anything on them and used 
blivet-gui to define the partitions: I want RAID1 arrays, so I defined 
each of them asking for RAID1 on two disks and ext4 or luks file system.


Here is the error message given when I press the Done button:

https://www.bertuccio.homelinux.net/IMG_20240705_194641.jpg

It is in French, I am sorry but I think that it understable

The song is "device RAID cannot be of luks type, ext4 type...  device 
RAID cannot be mounted on device /boot/efi,... partition EFI cannot be 
of type mdmember and so on...


It is telling you that it wants a separate partition for /boot/efi and 
that separate partition cannot be part of a raid array.


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

issue with f40 installer [2]

[François Patte]

Bonjour,

On another post I complained that I couldn't install f40 due, I thought, 
to existing partitions on a disk...


I tried to install on new disks without anything on them and used 
blivet-gui to define the partitions: I want RAID1 arrays, so I defined 
each of them asking for RAID1 on two disks and ext4 or luks file system.


Here is the error message given when I press the Done button:

https://www.bertuccio.homelinux.net/IMG_20240705_194641.jpg

It is in French, I am sorry but I think that it understable

The song is "device RAID cannot be of luks type, ext4 type...  device 
RAID cannot be mounted on device /boot/efi,... partition EFI cannot be 
of type mdmember and so on...


I don't understand: my f36 use RAID1 arrays with ext4 and luks file 
systems and lvm volumes.


What did I do wrong?

Than k you.


--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte
--
___
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