Re: f31:: thunderbird/kde:: extension of window below desktop

On 11/3/20 1:43 AM, Adrian Sevcenco wrote: the thunderbird window cannot be resized in vertical size and also cannot be moved vertically ... Not exactly, but I'd expect you to be able to resize a window from any visible corner.  Can you resize windows if you zoom out?

Re: USB error: vendor cannot be 0

On 2020-11-06 20:20, Ed Greshko wrote: On 07/11/2020 10:40, ToddAndMargo via users wrote: This flash drive has a full version of Fedora 32 installed on it and does boot into Fedora 32 when booted natively. Oh, I see.  You want to boot F32 from the usb? I've had the need to try that.

Re: USB error: vendor cannot be 0

On 07/11/2020 10:40, ToddAndMargo via users wrote: This flash drive has a full version of Fedora 32 installed on it and does boot into Fedora 32 when booted natively. Oh, I see.  You want to boot F32 from the usb? I've had the need to try that. Redirect usb devices: AFAIK, redirection is

Re: USB error: vendor cannot be 0

On 2020-11-06 13:21, ToddAndMargo via users wrote: Hi All, Anyone know a work around for this?    Fedroa 32, x64    $ rpm -qa virt-manager    virt-manager-3.1.0-1.fc32.noarch    $ rpm -qa qemu-device-usb-redirect    qemu-device-usb-redirect-5.1.0-7.fc32.x86_64 Bug I filed on

Oh God! More helpful software :-).

For as long as I can remember I've run dnf update in a root xterm and when all the akmod activity and wot-not is finished, I've run reboot from another terminal. Now, it won't reboot "because root is logged in". Gah! Who cares if root is logged in? Can I disable this helpful feature any way?

Re: USB error: vendor cannot be 0

On 2020-11-06 14:57, Ed Greshko wrote: On 07/11/2020 05:53, ToddAndMargo via users wrote: On 2020-11-06 13:37, Ed Greshko wrote: On 07/11/2020 05:21, ToddAndMargo via users wrote: Anyone know a work around for this?

Re: USB error: vendor cannot be 0

On 2020-11-06 14:57, Ed Greshko wrote: On 07/11/2020 05:53, ToddAndMargo via users wrote: On 2020-11-06 13:37, Ed Greshko wrote: On 07/11/2020 05:21, ToddAndMargo via users wrote: Anyone know a work around for 

Re: USB error: vendor cannot be 0

On 2020-11-06 14:44, Ed Greshko wrote: On 07/11/2020 05:53, ToddAndMargo via users wrote: On 2020-11-06 13:37, Ed Greshko wrote: On 07/11/2020 05:21, ToddAndMargo via users wrote: Anyone know a work around for this?    Fedroa 32, x64    $ rpm -qa virt-manager    

Re: USB error: vendor cannot be 0

On 07/11/2020 05:53, ToddAndMargo via users wrote: On 2020-11-06 13:37, Ed Greshko wrote: On 07/11/2020 05:21, ToddAndMargo via users wrote: Anyone know a work around for this?    Fedroa 32, x64    $ rpm -qa virt-manager    virt-manager-3.1.0-1.fc32.noarch    $ rpm -qa 

Re: USB error: vendor cannot be 0

On 07/11/2020 05:53, ToddAndMargo via users wrote: On 2020-11-06 13:37, Ed Greshko wrote: On 07/11/2020 05:21, ToddAndMargo via users wrote: Anyone know a work around for this?    Fedroa 32, x64    $ rpm -qa virt-manager    virt-manager-3.1.0-1.fc32.noarch    $ rpm -qa 

Re: Anaconda RAID levels

On 11/6/20 1:38 PM, Matti Pulkkinen wrote: I tried looking at the documentation for installing Fedora[1], but didn't see an explanation of what raid level "single" means in Anaconda. If I select two disks for a volume, and then select single level RAID, does this mean I'm actually only using

Re: Swap on BTRFS

On Fri, 2020-11-06 at 12:50 -0400, George N. White III wrote: > > # chattr +C swapfile > > chattr: Invalid argument while setting flags on swapfile > > > > Mybe we are no lnpger meant to use chattr: Manual page btrfs- > property(8) > says: > > "btrfs property provides an unified and

Re: Swap on BTRFS

On Fri, 2020-11-06 at 10:59 -0800, Samuel Sieb wrote: > On 11/6/20 3:36 AM, Patrick O'Callaghan wrote: > > On Thu, 2020-11-05 at 15:23 -0800, Samuel Sieb wrote: > > > On 11/5/20 2:23 PM, Patrick O'Callaghan wrote: > > > > On Thu, 2020-11-05 at 10:47 -0800, Samuel Sieb wrote: > > > > > Yes. But

Re: USB error: vendor cannot be 0

On 2020-11-06 13:37, Ed Greshko wrote: On 07/11/2020 05:21, ToddAndMargo via users wrote: Anyone know a work around for this?    Fedroa 32, x64    $ rpm -qa virt-manager    

Anaconda RAID levels

Hello! I tried looking at the documentation for installing Fedora[1], but didn't see an explanation of what raid level "single" means in Anaconda. If I select two disks for a volume, and then select single level RAID, does this mean I'm actually only using one disk, or is it somehow

Re: USB error: vendor cannot be 0

On 07/11/2020 05:21, ToddAndMargo via users wrote: Anyone know a work around for this?    Fedroa 32, x64    $ rpm -qa virt-manager    virt-manager-3.1.0-1.fc32.noarch    $ rpm -qa qemu-device-usb-redirect    qemu-device-usb-redirect-5.1.0-7.fc32.x86_64 Bug I filed on 2020-06-23:    

USB error: vendor cannot be 0

Hi All, Anyone know a work around for this? Fedroa 32, x64 $ rpm -qa virt-manager virt-manager-3.1.0-1.fc32.noarch $ rpm -qa qemu-device-usb-redirect qemu-device-usb-redirect-5.1.0-7.fc32.x86_64 Bug I filed on 2020-06-23: libvirt.libvirtError: internal error: vendor cannot

Re: Migration strategy to F33 w/ btrfs?

On 11/6/20 11:59 AM, Richard Shaw wrote: On Fri, Nov 6, 2020 at 1:56 PM Samuel Sieb > wrote: On 11/6/20 11:48 AM, Richard Shaw wrote: > On Fri, Nov 6, 2020 at 1:27 PM sixpack13 mailto:sixpac...@online.de> >

Re: Migration strategy to F33 w/ btrfs?

On Fri, Nov 6, 2020 at 1:56 PM Samuel Sieb wrote: > On 11/6/20 11:48 AM, Richard Shaw wrote: > > On Fri, Nov 6, 2020 at 1:27 PM sixpack13 > > wrote: > > > > thanks for clarification. > > I wasn't sure. > > It want hurt to put the disks in the right place

Re: Migration strategy to F33 w/ btrfs?

On 11/6/20 11:48 AM, Richard Shaw wrote: On Fri, Nov 6, 2020 at 1:27 PM sixpack13 > wrote: thanks for clarification. I wasn't sure. It want hurt to put the disks in the right place even it is planed to do so in any case afterwards. For EFI, won't

Re: Migration strategy to F33 w/ btrfs?

On Fri, Nov 6, 2020 at 1:27 PM sixpack13 wrote: > thanks for clarification. > I wasn't sure. > It want hurt to put the disks in the right place even it is planed to do > so in any case afterwards. > For EFI, won't the bios find the EFI partition anyway? Thanks, Richard

Re: Migration strategy to F33 w/ btrfs?

thanks for clarification. I wasn't sure. It want hurt to put the disks in the right place even it is planed to do so in any case afterwards. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

Re: Migration strategy to F33 w/ btrfs?

On 11/6/20 11:00 AM, sixpack13 wrote: I currently don't know if the installer could be forced to install grub to an destined disk/ssd when two are in the box: so I would place the new ssd in the right place *before* installation. There is an option, somewhat obscure, to set the boot loader

Re: Migration strategy to F33 w/ btrfs?

I currently don't know if the installer could be forced to install grub to an destined disk/ssd when two are in the box: so I would place the new ssd in the right place *before* installation. I also don't know if "over-provisioning" is (still) necessary. is that on your radar ? hint: I'm used

Re: Swap on BTRFS

On 11/6/20 3:36 AM, Patrick O'Callaghan wrote: On Thu, 2020-11-05 at 15:23 -0800, Samuel Sieb wrote: On 11/5/20 2:23 PM, Patrick O'Callaghan wrote: On Thu, 2020-11-05 at 10:47 -0800, Samuel Sieb wrote: Yes. But have you enabled zram yet for swap? This is a clean install, so it's enabled by

Re: Migration strategy to F33 w/ btrfs?

On Fri, Nov 6, 2020 at 9:21 AM Tom Horsley wrote: > On Fri, 6 Nov 2020 09:02:06 -0600 > Richard Shaw wrote: > > > 2. Perform a clean install to it > > You don't necessarily need a clean install. You can > partition and format the new ssd then just rsync > everything to it and use grub2-install

Re: Swap on BTRFS

On Fri, 2020-11-06 at 23:03 +0800, Qiyu Yan wrote: > Okay, I think I get it now, just don't set > btrfs property set /SWAP compression no > seems that this lead to something strange, while I can't tell why but > it is totally fine to do so, since nocow means no datacsum and no > compression OK,

Re: Swap on BTRFS

On Fri, 6 Nov 2020 at 08:42, Patrick O'Callaghan wrote: > On Fri, 2020-11-06 at 20:27 +0800, Qiyu Yan wrote: > > Patrick O'Callaghan 于2020年11月6日周五 下午8:14写道： > > > > > > On Fri, 2020-11-06 at 11:18 +, Patrick O'Callaghan wrote: > > > > On Fri, 2020-11-06 at 05:43 +, Qiyu Yan wrote: > > >

Re: Migration strategy to F33 w/ btrfs?

On Fri, 6 Nov 2020 09:02:06 -0600 Richard Shaw wrote: > 2. Perform a clean install to it You don't necessarily need a clean install. You can partition and format the new ssd then just rsync everything to it and use grub2-install to make it bootable and edit all the grub.conf, grub env files,

Re: Swap on BTRFS

Okay, I think I get it now, just don't set btrfs property set /SWAP compression no seems that this lead to something strange, while I can't tell why but it is totally fine to do so, since nocow means no datacsum and no compression ___ users mailing list

Migration strategy to F33 w/ btrfs?

I've already done a dnf upgrade to F33 on my system that hasn't had a "clean" install since at least F24, but at some point I'd like to migrate to btrfs w/o LVM. My current plan is to replace my current SSD (500GB Samsung EVO 970 m.2) to a 1GB version with the process being loosely: 1. Add the

Re: Swap on BTRFS

On Fri, 2020-11-06 at 21:08 +0800, Qiyu Yan wrote: > see > lsattr swapfile # lsattr swapfile swapfile # poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Swap on BTRFS

see lsattr swapfile ___ 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:

Re: Swap on BTRFS

On Fri, 2020-11-06 at 20:27 +0800, Qiyu Yan wrote: > Patrick O'Callaghan 于2020年11月6日周五 下午8:14写道： > > > > On Fri, 2020-11-06 at 11:18 +, Patrick O'Callaghan wrote: > > > On Fri, 2020-11-06 at 05:43 +, Qiyu Yan wrote: > > > > You can use swapfile on btrfs with nocow > > > > [...] > > > >

Re: Swap on BTRFS

Patrick O'Callaghan 于2020年11月6日周五 下午8:14写道： > > On Fri, 2020-11-06 at 11:18 +, Patrick O'Callaghan wrote: > > On Fri, 2020-11-06 at 05:43 +, Qiyu Yan wrote: > > > You can use swapfile on btrfs with nocow > > > [...] > > > https://wiki.archlinux.org/index.php/btrfs#Swap_file for

Re: Swap on BTRFS

On Fri, 2020-11-06 at 11:18 +, Patrick O'Callaghan wrote: > On Fri, 2020-11-06 at 05:43 +, Qiyu Yan wrote: > > You can use swapfile on btrfs with nocow > > [...] > > https://wiki.archlinux.org/index.php/btrfs#Swap_file for instructions > > Great. I was actually wondering about precisely

Re: Swap on BTRFS

On Thu, 2020-11-05 at 15:23 -0800, Samuel Sieb wrote: > On 11/5/20 2:23 PM, Patrick O'Callaghan wrote: > > On Thu, 2020-11-05 at 10:47 -0800, Samuel Sieb wrote: > > > Yes. But have you enabled zram yet for swap? > > > > This is a clean install, so it's enabled by default and has reserved > >

Re: Swap on BTRFS

On Fri, 2020-11-06 at 05:43 +, Qiyu Yan wrote: > You can use swapfile on btrfs with nocow > > See: > https://btrfs.wiki.kernel.org/index.php/FAQ#Does_btrfs_support_swap_files.3F > > And > > https://wiki.archlinux.org/index.php/btrfs#Swap_file for instructions Great. I was actually

Re: Swap on BTRFS

On Thu, 2020-11-05 at 17:46 -0600, Gabriel Ramirez wrote: > On 11/5/20 4:23 PM, Patrick O'Callaghan wrote: > > This is a clean install, so it's enabled by default and has reserved > > 4GB. I think that's what's actually causing the OOMs. I have 16GB of > > RAM. On F32 I could run an 8GB VM with

Re: Display Manager Configuration Files

On 5/11/20 10:50 pm, Ed Greshko wrote: On 05/11/2020 11:07, Stephen Morris wrote: found it is not a good idea to use systemctl to stop the current DM before enabling and starting the new DM. For future reference, the best way to change to a different DM is to use systemctl --force enable (DM

F33 XFCE Evolution Printing Problem Fix

Just in case anyone has problems printing from F33 evolution the fix given on the evolution-l...@gnome.org list is as follows > I suppose your Fedora 32 has a different (2.28) version of webkit2gtk3 > package than the Fedora 33 installation (2.30). When you update the > Fedora 32 you'll get the