no memory tester.
Chris Murphy
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code
Also there's below:
https://github.com/facebookincubator/below
Hopefully it'll get packaged soon.
https://discussion.fedoraproject.org/t/article-proposal-below-an-interactive-resource-monitor-for-modern-linux-systems/31176/2
Chris Murphy
___
devel
thout repair capability. Currently it flips the file system
read-only to stop further confusion and keep data safe.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject
idered safe to run. So if you're not using
Workstation edition you might want to install and enable uresourced,
which is itself intended to be temporary.
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to de
hat everyone is doing including if there's anything else especially
busy that's maybe slowing down whatever dnf is up to. It's
sufficiently verbose that it will fill up the kernel message buffer,
and likely a lot of messages will be dropped, so use journalctl -k
rat
iB to max
Single device btrfs resize is straightforward. But with multiple
device Btrfs, you need to specify the devid you want resized,
otherwise it defaults to devid 1.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubsc
On Mon, Jul 26, 2021 at 3:25 AM Eyal Lebedinsky wrote:
>
> Is this an intentional change?
You might search https://lore.kernel.org/linux-usb/ and see if
anything pops up; and if not then ask on the same list,
linux-...@vger.kernel.org.
--
Chris
On Fri, Jul 23, 2021 at 1:56 PM Chris Murphy wrote:
>
> Even better is if you can reproduce the high load and try to capture
> one or more of the following: sysrq+l which will dump the result into
Actually, sysrq+w is also useful. The root user can use:
echo l > /proc/sysrq-tr
load and try to capture
one or more of the following: sysrq+l which will dump the result into
dmesg and will end up in the journal, which you can filter similarly:
journalctl -b -k -o short-monotonic --no-hostname > dmesg-cpustack.txt
And attach to the bug report.
Also, you can cc me bugzilla at
5 :00:02.0: [drm] *ERROR* Stolen
reserved area [mem 0xdf10-0xdf1f] outside stolen memory [mem
0x9f20-0xc11f]
[1.903856] kernel: i915 :00:02.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=io+mem:owns=io+mem
hmmm.
Chris Murphy
_
> On Sun, Jul 18, 2021 at 11:12 AM Joe Zeff wrote:
> >
> > On 7/18/21 7:38 AM, John Mellor wrote:
Oh nice, the previous email is meant for John, not Joe.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To u
> 13.711s systemd-journal-flush.service
All three of these are suspiciously long.
Post /etc/fstab, /proc/cmdline, and the output from 'journalctl -b -o
short-monotonic --no-hostname > journal.log'
--
Chris Murphy
___
users mailing list -- users@l
@lists.fedoraproject.org/
And the docs project list of sub projects
https://pagure.io/group/fedora-docs
Which includes the accessibility guide sub project
https://pagure.io/accessibility-guide
--
Chris Murphy
___
users mailing list -- users@lists.fedorap
s for
> > > that, but you can also add nofail to the fstab for it so at least boot
> > > won't hang.
Did you add nofail to fstab options for the /boot/efi line?
Can you post 'journalctl -b -o short-monotonic --no-hostname' somewhere?
--
Chris Murphy
_
rmation
> ESP: n/a
> File: └─n/a
>
>
> Is this normal ?
Yes, bootctl is for the systemd-boot bootloader, which Fedora doesn't
use right now.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To
.
The gist of what you need is one f34 bootloader in
/boot/efi/EFI/fedora/ and its grub.cfg points to the real grub.cfg at
/boot/grub2 which in turn loads blscfg.mod which finds and reads
/boot/loader/entries and then creates a GRUB menu from all the
snippets found there.
--
Chris Murphy
https://bugs.kde.org/show_bug.cgi?id=439805
Chris Murphy changed:
What|Removed |Added
Summary|RFE: move individual|RFE: move individual
|tabbed
https://bugs.kde.org/show_bug.cgi?id=439805
Bug ID: 439805
Summary: RFE: move individual tabbed/windowed processes into
their own system scope
Product: konsole
Version: master
Platform: Other
OS: Linux
for that I use the blockerbugs app [3] to propose
it.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?h=v5.14-rc1
[2]
https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
[3]
https://qa.fedoraproject.org/blockerbugs/propose_bug
--
Chris Mu
for that I use the blockerbugs app [3] to propose
it.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?h=v5.14-rc1
[2]
https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
[3]
https://qa.fedoraproject.org/blockerbugs/propose_bug
-
dding this
kind of layer just be asking for more things to maintain,
troubleshoot, test, and break?
https://github.com/tianocore/tianocore.github.io/wiki/DuetPkg
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
?rd=Grub2#Changing_kernel_command-line_parameters_with_grubby
--
Chris Murphy
___
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.
an be any size. Of course, it needs to be
at least as large as the data usage on the seed. [1]
--
Chris Murphy
[1]
Sorta :) Once the 2nd device is added, you are allowed to delete
things you don't want replicated. They are retained on the read-only
seed, but are not replicated when you remove the see
al; that was kernel 5.8 through 5.11.
--
Chris Murphy
___
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
and a work
around is published in the bug. Or just install the proprietary driver
via RPM Fusion repo.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora
PackageKit uses libdnf. libdnf is the core library for dnf,PackageKit
and rpm-ostree.
You should generally get the same results using either dnf or PackageKit.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
kind
of layout change, and we need to consider upgrades. It has to work for dnf
and PackageKit, etc.
--
Chris Murphy
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedo
o installable payload, they boot a sort of live image and
run the installer program. That's it. Server has different
partitioning defaults from Everything, but otherwise they're the same.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.
, it doesn't work even when the network link is
> active.
Both of these are probably usability bugs, it should probably fail
faster when it's not finding something it recognizes... "is not a
valid source" or something to that effect. But before filing a bug it
might be better to ask about
d SCSI disk
>
> The uas message is again from device 6:0:0:1 as before, even though the
> disks have been swapped. IOW the issue definitely comes from the dock,
> not from the physical drives themselves.
I don't know if it's coming from the dock's usb chipset or the
u
motherboard with no intervening hub or splitter. It is independently
> powered via a wall socket and power block.
Does the error messages I referred to happen when the system is booted
with the drives attached separately? Or does it happen when only
connected to a particular port on the dock?
-
r terminate signal at shutdown, but it's become sufficiently busy
that it ignores it. And then systemd hits a time out 1m30s later and
kills it anyway. There is a Workstation ticket about shortening
shutdown times.
https://pagure.io/fedora-workstation/issue/163
ts, would the root be switched to the updated snapshot, and
reboot. And the user can choose when that happens.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora C
ges but no
> luck.
>
> Is it just my laptop that's somehow broken?
I've got a similar regression where the session starts in X instead of
Wayland, with a huge stack trace in the journal. So I don't think it's
hardware related.
--
Chris Murphy
___
ges but no
> luck.
>
> Is it just my laptop that's somehow broken?
I've got a similar regression where the session starts in X instead of
Wayland, with a huge stack trace in the journal. So I don't think it's
hardware related.
--
Chris Murphy
__
Save it out, and when the unit restarts (logout and login or do the
daemon-reload followed by service restart dance) you'll see packagekit
uses this value as a maximum.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
T
run as an opt in for other desktops, though we want
to keep an eye on possible regressions.
There is still more work to do in this area, in particular wiring up
the IO isolation. Any time there's memory pressure it'll quickly lead
to IO pressure: reclaim and swap.
--
Chris Murphy
_
e to use an elrepo
kernel you could try changing nothing else and see if the kernel 5.8+
changes help your workload all by themselves. And if not you could
look at either zram based swap or zswap.
--
Chris Murphy
___
users mailing list -- u
On Mon, Jun 21, 2021 at 10:58 AM Chris Murphy wrote:
>
> Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2 uas_eh_abort_handler
> 0 uas-tag 2 inflight: IN
> Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2 CDB: Mode Sense(6) 1a
> 00 08 00 18 00
Yeah and in the install-boot log i
t
becomes something you apply every boot.
--
Chris Murphy
___
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/pro
On Mon, Jun 21, 2021 at 9:43 AM Chris Murphy wrote:
>I don't think GRUB has exclusivity over this guid,
> and was always intended to be generic, I'm just not aware of any
> bootloader that uses it.
any ^other bootloader
--
Chris Murphy
nded to be generic, I'm just not aware of any
bootloader that uses it.
Also, the scope of the hybrid UEFI/BIOS change is limited to x86_64,
while we could incidentally add BIOS Boot to the aarch64 images, I
don't expect we'd actually put anything there. It'd be outside the
sco
On Sun, Jun 20, 2021 at 6:54 PM Chris Murphy wrote:
>
> 197 of these in the non-working instance
>
> 08:18:38,802 WARNING
> org.fedoraproject.Anaconda.Modules.Storage:WARNING:blivet:device/model
> is not a valid attribute
>
> 2 in the working instance. Seems suspiciou
, has an ESP and UEFI GRUB. But it's being tested
in openqa in a BIOS VM so it fails. But I'm not sure why it's being
created in a UEFI VM...
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le
/vda
So it should be in the 34 log too, right? And yet it's not. So that'd
explain why it doesn't have a bootloader. Not sure why it wasn't even
executed though, almost like the installation is just missing a bunch
of steps?
--
Chris Murphy
___
test
On Sun, Jun 20, 2021 at 6:21 PM Chris Murphy wrote:
>
> https://openqa.fedoraproject.org/tests/912650
>
> Does openqa only do qcow2 tests? I'm not seeing raw tests. I'm just
> curious for another data point. :P
>
> I'm seeing Rawhide and 33 images passing (couple warn, no fa
at the firmware as if it's not finding a bootloader at all. Hence
wondering if there might be a difference between raw and qcow2...
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le
bus appearing,
drive on bus appearing, partition map appearing. I couldn't open the
previous journal log provided, it wasn't publicly visible or I'd have
taken a gander.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscrib
I make fstab mount options include:
nofail,noauto,x-systemd.automount
That way it is only mounted on demand, i.e. when the mount point is "touched".
It's also possible to use x-systemd.idle-timeout=300 which will
unmount it after 5 minutes idle.
--
Ch
on the bus shared by sysroot.
I'm suspicious that something is trying to mount it, or otherwise access
it, but I haven't seen the logs.
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists
many folks have TPMs at all, if they're 1.2
enabled or 2.0; whether the system is Secure Boot capable, enabled or
disabled; whether the firmware is BIOS, UEFI, coreboot.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsub
ly not because it'll step on valid bootloader things with stale
copies. If you avoid stepping on anything in:
/boot
/etc/grub*
It might work... but you'll still have kernels that rpm database says
are installed that aren't installed; you'll have stale boot entries
for kernels that aren't installed and
of it after the restore.
And to my knowledge no tool knows how to do that except the installer.
And the installer only knows how to do it in the context of a clean
install. Not a repair.
--
Chris Murphy
___
users mailing list -- u
hat in detail is tedious,
but maybe someone knows of a guide how to do all that.
But this process is the same whether the source is btrfs, xfs or
already ext4 and you need to migrate it to new file systems/layout.
--
Chris Murphy
___
users mailing list -- u
", \
ENV{ID_SERIAL_SHORT}=="WDZ47F0A", \
RUN+="/usr/sbin/hdparm -B 100 -S 252 /dev/disk/by-id/wwn-0x5000c500a93cae8a"
$
Chris Murphy
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
in 055 or something? I'm not
sure yet...still kinda in the dark on what's going wrong.
Also, it is possible it's not related to this btrfs file system at
all, but I'm throwing it out there just as something to be aware of.
--
Chris Murphy
___
users mail
On Sat, Jun 12, 2021 at 11:20 AM Patrick O'Callaghan
wrote:
>
> On Sat, 2021-06-12 at 07:25 -0600, Chris Murphy wrote:
> > Both problems need logs. It's quite a bit over kill but these boot
> > parameters will help provide enough info.
> >
> > systemd.log_level
avoiding the dracut shell. But better to
get the shell than an indefinite hang.
journalctl -b -o short-monotonic --no-hostname > journal.log
Copy that out to a file sharing service, and post the URL.
Chris Murphy
___
users mailing list -- us
https://bugs.kde.org/show_bug.cgi?id=438378
--- Comment #3 from Chris Murphy ---
I did test it in Fedora and the file system was not renamed even though
Partition Manager claims it was done. But that'd be a separate bug report; any
tips on getting verbose information from partition manager
https://bugs.kde.org/show_bug.cgi?id=438378
Bug ID: 438378
Summary: RFE: support for FS_IOC_SETFSLABEL
Product: partitionmanager
Version: Git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=438376
Bug ID: 438376
Summary: consider btrfs by default for Linux systems
Product: partitionmanager
Version: Git
Platform: Other
OS: Linux
Status: REPORTED
Severity:
it. But there are features that old kernels don't
support, like for example zstd compression which arrived in kernel
4.14, thus not mountable (incompatible) with older kernels. Free space
tree v2 exists since kernel 4.5, but its flag permits ro mount with
old kernels.
--
Chris Murphy
__
hics
stack. But, near term such a thing would be btrfs only unless we
dedicate a literal partition and stick a Live OS ISO image on it
(effectively).
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to us
ing
damaged even worse.
But anyway there's not much to go on here yet. We need to see dmesg
for these problems. I personally prefer to see the entire dmesg
because isolated errors don't tell me about what was going on
immediately prior to the Btrfs error which is almost alw
ance issues on Btrfs, but I don't know the significance, in
particular with today's kernel. Interested parties could create a
micro-SIG, I'm happy to help coordinate, and do some testing and
document best practices.
--
Chris Murphy
___
devel mailing list --
On Fri, May 28, 2021 at 1:45 AM Peter Boy wrote:
> > Am 27.05.2021 um 00:59 schrieb Chris Murphy :
> > Whereupon Server SIG/WG perform an evaluation of Btrfs for their use
> > cases, and decide Btrfs should be the default in a compelling manner,
> > FESCo will approv
ents).
>
That does look like what we're after. Thanks!
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.
/grubenv only for that purpose. I'd like to see
more consistency, fewer exceptions.
And that also means the old argument about the MBR gap. GRUB should
have its own partition here too.
Chris Murphy
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
On Thu, May 27, 2021 at 2:59 AM Michael Chang wrote:
>
> On Wed, May 26, 2021 at 08:36:05PM -0600, Chris Murphy wrote:
> > So is the next era going to be we recommend /boot on FAT?
>
> No. I meant a new partition type only for grubenv files and keep
> everything else as i
On Thu, May 27, 2021 at 2:05 PM Chris Murphy wrote:
>
> On Thu, May 27, 2021 at 3:58 AM Mauricio Tavares wrote:
> >
> > On Thu, May 27, 2021 at 5:49 AM e wrote:
> > >
> > > sounds unintuitive, but he just speaks truth to power:
> > >
> > &
omplicated material, and having a fairly good grasp
of GRUB behavior in Fedora, along with many conversations with
Fedora's bootloader team. It's strictly an opinion to fellow doc
writers, to help them assess where to put their own limited resources.
If people want to do it anyway, I wish them a lot of luck be
partition, and run a post install script that does
`grub2-install --target=i386-pc` to add the BIOS bootloader?
Thoughts?
[1]
https://pagure.io/cloud-sig/issue/330
[2]
https://pagure.io/cloud-sig/issue/309
--
Chris Murphy
___
Anaconda-devel-list mailing
be generally useful, if/when the
existing bootloader UI bits go away.)
I'll start a new thread on anaconda-devel@ about that.
--
Chris Murphy
>
> Brian
>
> --
> Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
> _
On Wed, May 26, 2021 at 3:17 AM Michael Chang via Grub-devel
wrote:
>
> On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
> > Hi,
> >
> > It's not possible for GRUB pre-boot environment to write to grubenv
> > when it's on Btrfs, ZFS, LVM, mdadm rai
On Wed, May 26, 2021 at 2:08 AM Konrad Rzeszutek Wilk
wrote:
>
> On Tue, May 25, 2021 at 04:58:23PM -0600, Chris Murphy wrote:
> > Hi,
> >
> > It's not possible for GRUB pre-boot environment to write to grubenv
> > when it's on Btrfs, ZFS, LVM, mdadm raid, or LUKS. A
On Wed, May 26, 2021 at 5:30 AM Peter Boy wrote:
> > Am 26.05.2021 um 08:51 schrieb Chris Murphy :
> > What controversial discussion is being referenced? Currently before us
> > is a proposal to switch to Btrfs for Cloud edition.
>
> I’m quite sure you know that discus
ies since day 1. Today is the first I've heard
that there should be, could be, would be, some kind of realignment
where Cloud uses LVM or Server uses ext4, or some other combination.
But you are now asserting that this alignment should happen? And are
you asserting that this is a central question n
nts, which is the point of
grubenv, but it can't work much of the time due to the above
limitations.
--
Chris Murphy
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
face,
making it impossible to directly control them per channel. In effect,
the print driver is becoming part of the printer's firmware.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@
that is to create a new / mount
point rather than clicking on an existing one; also helpful is to not
specify a size for this mount point, just leave that 2nd field empty.
There is a test case that describes this in detail and hopefully
someone will turn it i
What do you get for:
sudo systemctl status earlyoom.service
I see:
Loaded: loaded (/usr/lib/systemd/system/earlyoom.service;
disabled; vendor preset: disabled)
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
18.162089360600.zst"
> is not a core dump: file format not recognized
Yes, file a bug against gdb.
Thanks,
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedora
number of a file in /usr that should be compress but
isn't and then plug that inode number into
btrfs insp dump-t -t 257 /dev/xyz | grep -C 20 $INUM
This may expose file names for other files. Doesn't matter to me if
you include the whole output of the above comment or trim to just the
cluster of i
ent ideas about
> which grub.cfg is in use.
>
> See also https://bugzilla.redhat.com/show_bug.cgi?id=1958540
A grubx64.efi created by grub2-install, on any version of Fedora, will
use /boot/grub2/grub.cfg
--
Chris Murphy
___
devel mailing list -
have rawhide kernels, because the kernel is special. Your other
packages won't get f34 versions because that would be a downgrade.
I think.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le
e EFI system partition and path to shimx64.efi or shim.efi.
Boot order can be reset by:
efibootmgr --bootorder $
Where $ is the four digit boot number for the Fedora boot entry.
No other entries need to be specified but you could optionally add a
fallback entry, e.g. --bootorder 0006,00
On Sat, May 8, 2021 at 3:51 PM Björn Persson wrote:
>
> Chris Murphy wrote:
> > Does /etc/default/grub contain
> > GRUB_ENABLE_BLSCFG=false
> > ?
>
> No, it says "GRUB_ENABLE_BLSCFG=true".
>
> > There have been two big GRUB changes and
On Sat, May 8, 2021 at 11:36 AM Chris Murphy wrote:
>
> If you have BLS disabled, enable it. Recreate /boot/grub2/grub.cfg
> (this is now the correct location on UEFI and BIOS). If you've
> accidentally stepped on the forwarding /boot/efi/EFI/fedora/grub.cfg
If you have accidentally
.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https
. This assumes a dedicated ext4 volume for /boot, which is
the Fedora default. If you have a different configuration you might
need to specify a different UUID for the file system containing
/boot/grub2/grub.cfg which might also need a modified line 2 to point
to a boot directory, i.e. ($dev)/boot/gr
there's test cases to make sure these are tested.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
esktops,
and I still don't know why we don't just do either what upstream or
Silverblue are doing.
So I'm kinda curious if plocate will have issues related to bind
mounts or if it does things differently.
--
Chris Murphy
___
devel mailing list --
9d1?branch=rawhide
It references five upstream commits.
--
Chris Murphy
rompt following upgrades.
--
Chris Murphy
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-cond
On Thu, Apr 29, 2021 at 3:44 PM Matti Pulkkinen wrote:
>
> to, 2021-04-29 kello 15:32 -0600, Chris Murphy kirjoitti:
> >
> > Looks like you found it?
> > https://bugzilla.redhat.com/show_bug.cgi?id=1955162
> >
>
> Yup. As for your earlier question about why I
On Thu, Apr 29, 2021 at 3:32 PM Chris Murphy wrote:
>
> On Thu, Apr 29, 2021 at 3:30 PM Chris Murphy wrote:
> >
> > On Thu, Apr 29, 2021 at 2:51 PM Matti Pulkkinen wrote:
> > >
> > > to, 2021-04-29 kello 23:38 +0300, Matti Pulkkinen kirjoitti:
> > >
On Thu, Apr 29, 2021 at 3:30 PM Chris Murphy wrote:
>
> On Thu, Apr 29, 2021 at 2:51 PM Matti Pulkkinen wrote:
> >
> > to, 2021-04-29 kello 23:38 +0300, Matti Pulkkinen kirjoitti:
> > > In the installer the keymap was definitely the Finnish one. It's only
> > >
making sure the resulting installation works, and installer folks
know more about the potential trouble spots below the installer.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists
On Thu, Apr 29, 2021 at 2:40 PM Matti Pulkkinen wrote:
>
> to, 2021-04-29 kello 13:54 -0600, Chris Murphy kirjoitti:
> > I guess I'm confused about why US keymapping is needed to enter the
> > LUKS passphrase during boot. The keymappings need to be the same for
&g
On Thu, Apr 29, 2021 at 6:41 AM Matti Pulkkinen wrote:
>
> ke, 2021-04-28 kello 21:49 -0600, Chris Murphy kirjoitti:
> > Could you provide details about the installation choices made related
> > to language and key mapping? Was it also a Finnish keyboard being
> > used
>
401 - 500 of 8365 matches
Mail list logo
