sen to be as
broadly compatible with as much as possible, and frankly Wayland is
currently not that.
That said, if my whole life was Linux, I would move to a QEMU/KVM only
workflow, but I still have one pesky Win box in my life that I can't get
rid of (at work) so VirtualBox for me still makes sense
. However, it is fickle,
depending on the GNOME stack, there have been times when 3D on was
better. With 3D off, and GNOME in an Xorg session, it almost works.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
___
devel mailing list
the exact same VM install works flawlessly. So it wasn't that
my installation went wrong.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
___
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
On 3/21/24 03:36, Mattia Verga via devel wrote:
I will be following the procedure for completely removing a package [3],
however there are a couple of things that I'd like to ask:
I think the Astronomy Labs version of Fedora ships with Celestia so
their group will needs a heads up.
--
Ian
I have my dnf configured with installonly_limit=6 and now and then find
it useful to get rid of old kernels (for example after a move from
Fedora n to n+1).
I know in the early days of DNF5 you couldn't do this, but can you do it
now?
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia
.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
___
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
this fix so quickly, it is greatly appreciated.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct
still using elementary-code-6.2.0-2.fc37 which interestingly does
actually work on 37/38/39 and even Rawhide. Looking forward to an update.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
___
devel mailing list -- devel
I realize exa is still in the EPEL9 repos, was wondering if there is an
intention to move to its replacement eza as was done in F39 and F40?
Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
epel-devel mailing list -- epel-devel
On 9/18/23 07:48, Kevin Kofler via devel wrote:
SDDM was switched to Wayland for F38 and newer. If you want it to use X11,
you have to edit /etc/sddm.conf and set:
[General]
DisplayServer=x11
*sigh*
Well... setting DisplayServer=x11 works, the greeter works properly now.
Thanks.
--
Ian
in VirtualBox, but now even the greeter has issues,
and I think that's newish.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
On 9/14/23 09:48, Neal Gompa wrote:
On Wed, Sep 13, 2023 at 7:45 PM Ian Laurie wrote:
I'm an Xfce user so my care factor is minimal. I've not tried Plasma on
Wayland in the 39 branch yet but I do intend to.
Would you please report this to bugs.kde.org if it shows up in Fedora
39 KDE Beta
on X11 works
as expected.
I'm an Xfce user so my care factor is minimal. I've not tried Plasma on
Wayland in the 39 branch yet but I do intend to.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel
://bugzilla.redhat.com/show_bug.cgi?id=2236321
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
propose it as a Beta
FE...
OK I have filed a BZ [1] and a freeze exception request against it,
hopefully I've done it correctly.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2236321
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel
late to get 9.4 into 39, is it possible to locally include
this specific reverting patch?
[1] https://github.com/coreutils/coreutils/blob/master/NEWS
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel
not install the newest
packages,
I think you may need a --nogpgcheck in there to allow it to work.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On 6/22/23 19:01, Matthew Miller wrote:
Sure, but... that's the _opposite_ of the direction things are going.
Awesome post.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel@lists.fedoraproject.org
On 2/24/23 10:17, Ian Laurie wrote:
On 2/22/23 20:30, Miroslav Suchý wrote:
Do you want to make Fedora 38 better? Please spend 1 minute of your
time and try to run:
Looked good here, just some downgrades as follows:
Downgrading:
fwupd x86_64 1.8.10-1.fc38
1.8.10-1.fc38
fwupd-plugin-modem-manager x86_64 1.8.10-1.fc38
fwupd-plugin-uefi-capsule-data x86_64 1.8.10-1.fc38
inxi noarch 3.3.24-2.fc38
mock-core-configsnoarch 38.1-1.fc38
Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
On 2/9/23 07:38, Richard Shaw wrote:
I know upgrades are not supported but its for a small home server that
really only does two things:
For a home server you can use RHEL, the real deal, why mess with
downstream rebuilds?
Just a thought.
Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ
ather than the "correct"
"VMSVGA" setting.
The old setting produces a configuration alert with Linux systems
(although it does work). This feels like a kernel problem to me rather
than a VirtualBox problem at this point.
Anyone else seeing this, I can't be the only one?
On 11/9/22 01:18, Fedora Rawhide Report wrote:
OLD: Fedora-37-20221107.n.0
NEW: Fedora-37-20221108.n.0
[big snip]
This seems to have all the gnome fixes, plus a load of KDE fixes, and
the 6.0.7 kernel shouldn't this be a release candidate?
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ
?
Are we not fixing Fedora 35? It won't be EOL until mid December
(delays in 37 pushed it out a few times).
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel
may have dated back to May for all I know.
I became aware of the QT conflict when I used the command line to do
updates from a virtual console, but the issue could have been there from
any time in the past.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
activation point (long before the beta was released). I recall some
non-show-stopping complaints from dnf, but the upgrades happened without
a blocking incident and all machines are functioning normally now.
Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
On 6/16/22 06:36, Hans de Goede wrote:
Hi,
On 6/15/22 07:01, Ian Laurie wrote:
On 6/12/22 14:34, Sérgio Basto wrote:
On Sun, 2022-06-12 at 13:59 +1000, Ian Laurie wrote:
On 6/12/22 11:20, Ian Laurie wrote:
On 6/12/22 09:46, Ian Laurie wrote:
On 6/12/22 00:58, Hans de Goede wrote:
Hi
On 6/12/22 14:34, Sérgio Basto wrote:
On Sun, 2022-06-12 at 13:59 +1000, Ian Laurie wrote:
On 6/12/22 11:20, Ian Laurie wrote:
On 6/12/22 09:46, Ian Laurie wrote:
On 6/12/22 00:58, Hans de Goede wrote:
Hi,
On 6/11/22 01:02, Alexander G. M. Smith wrote:
On 2022-06-08 15:00, Alexander G. M
On 6/12/22 11:20, Ian Laurie wrote:
On 6/12/22 09:46, Ian Laurie wrote:
On 6/12/22 00:58, Hans de Goede wrote:
Hi,
On 6/11/22 01:02, Alexander G. M. Smith wrote:
On 2022-06-08 15:00, Alexander G. M. Smith wrote:
Ian Laurie wrote on Friday, 3 June 2022 at 11:17 p.m.:
Is anyone else
On 6/12/22 09:46, Ian Laurie wrote:
On 6/12/22 00:58, Hans de Goede wrote:
Hi,
On 6/11/22 01:02, Alexander G. M. Smith wrote:
On 2022-06-08 15:00, Alexander G. M. Smith wrote:
Ian Laurie wrote on Friday, 3 June 2022 at 11:17 p.m.:
Is anyone else seeing crashes and other strange events
On 6/12/22 00:58, Hans de Goede wrote:
Hi,
On 6/11/22 01:02, Alexander G. M. Smith wrote:
On 2022-06-08 15:00, Alexander G. M. Smith wrote:
Ian Laurie wrote on Friday, 3 June 2022 at 11:17 p.m.:
Is anyone else seeing crashes and other strange events in VirtualBox
6.1.34 (from RPMFusion
On 6/6/22 20:25, Paul Black via devel wrote:
On Sat, 4 Jun 2022 at 05:17, Ian Laurie wrote:
Is anyone else seeing crashes and other strange events in VirtualBox
6.1.34 (from RPMFusion) with Linux guests when the Linux host is
running
Fedora 36 with kernel-5.17.12?
I do
On 6/4/22 14:17, Ian Laurie wrote:
Is anyone else seeing crashes and other strange events in VirtualBox
6.1.34 (from RPMFusion) with Linux guests when the Linux host is
running Fedora 36 with kernel-5.17.12?
When I first started to see problems on my first host I blamed my SSD
drive, memory
have this on 2 host was
wondering if others are already some way along in working out the problem.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
On 4/4/22 10:09, Brandon Nielsen via devel wrote:
On 4/3/22 6:45 PM, Ian Laurie wrote:
I noticed in VirtualBox with GNOME and 20220401.n.0 that if I resized
the VM window when logged into GNOME it slammed me back to the
greeter, apparently without killing my login session.
I still had a VM
On 4/4/22 10:00, Samuel Sieb wrote:
On 4/3/22 16:45, Ian Laurie wrote:
I noticed in VirtualBox with GNOME and 20220401.n.0 that if I resized
the VM window when logged into GNOME it slammed me back to the
greeter, apparently without killing my login session.
What video device does VirtualBox
a BZ ticket for it I think.
I logged this as a warning for now:
https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0_Installation
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel
e. I can understand that RHEL 9 changes may have
introduced "difficulties" but some response, any response, would be nice.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
epel-devel mailing list -- epel-devel@lists.fedorap
On 3/16/22 01:13, Vitaly Zaitsev via devel wrote:
On 15/03/2022 01:25, Ian Laurie wrote:
Sadly it's not able to boot graphically, but I think the issue is
with my RPMFusion NVIDIA drivers. I can login fine to a virtual
console however, and lightdm is running, just not working. The
startx
ems are relatively legacy unfortunately, but still looking good
here.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.
On 3/15/22 11:25, Ian Laurie wrote:
On 3/14/22 20:55, Vitaly Zaitsev via devel wrote:
On 14/03/2022 10:49, Ian Laurie wrote:
Yeah I'm thinking I should, and not just because of this. Mainly
for on-time kernel support.
Also, since Fedora 36 the NVIDIA and VirtualBox kmods can
On 3/14/22 20:55, Vitaly Zaitsev via devel wrote:
On 14/03/2022 10:49, Ian Laurie wrote:
Yeah I'm thinking I should, and not just because of this. Mainly for
on-time kernel support.
Also, since Fedora 36 the NVIDIA and VirtualBox kmods can be
automatically signed after the build to support
On 3/14/22 20:55, Vitaly Zaitsev via devel wrote:
On 14/03/2022 10:49, Ian Laurie wrote:
Yeah I'm thinking I should, and not just because of this. Mainly for
on-time kernel support.
Also, since Fedora 36 the NVIDIA and VirtualBox kmods can be
automatically signed after the build to support
On 3/14/22 19:15, Vitaly Zaitsev via devel wrote:
On 14/03/2022 04:39, Ian Laurie wrote:
Problem: package VirtualBox-6.1-6.1.32_149290_fedora33-1.x86_64
requires libvpx.so.6()(64bit), but none of the providers can be installed
Use VirtualBox from the RPM Fusion repository.
Yeah I'm
33-1.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
--
Ian Laurie
ilau...@bigpond.net.au
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Cond
Just FYI kernel 5.11.5 still doesn't work for me, 5.11.2 does work.
Didn't check 5.11.4 however.
On 3/10/21 7:50 AM, Ian Laurie wrote:
Thanks Milan, turns out our generated passphrase is exactly 64 bytes long.
If your passphrase is longer than 63 characters, please read
https://gitlab.com
--
Ian Laurie
ilau...@bigpond.net.au
___
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
Fedora 34 with latest updates (kernel-5.11.3-300.fc34.x86_64) won't
mount Veracrypt volumes. I can boot with the previous kernel 5.11.2 and
it works fine.
kernel-5.11.3-300.fc34.x86_64
cryptsetup-2.3.4-2.fc34.x86_64
Commands I'm using are:
sudo cryptsetup open /dev/sdb1 vcvolume --type
Sorry, fixed, I'll send just plain text.
Ian
On 15/02/2021 5:18 am, Kevin Fenzi wrote:
On Sun, Feb 14, 2021 at 12:24:12PM +1100, Ian Laurie wrote:
Hey Ian... would it be possible for you to adjust your mail client to
send text and html instead of just html? Many on this list expect the
text
fonts-ISO8859-1-100dpi"
Ian
On 14/02/2021 1:29 pm, Ian Laurie
wrote:
It looks like the perf-5.11.0-0.rc7 dependency issue was caused by
selecting the "C Development Tools and Libraries" option on the
right side, so presumably MA
It looks like the perf-5.11.0-0.rc7 dependency issue was caused by
selecting the "C Development Tools and Libraries" option on the
right side, so presumably MATE would have worked without that
selected.
--
Ian
On 14/02/2021 12:24 pm,
I tried testing out
Fedora-Everything-netinst-x86_64-34-20210213.n.0.iso with an Xfce
and MATE install, both failed.
I've attached screen shots of the error my software selection gave
me for each attempt.
--
Ian
,
Hans
Hi Hans,
I did file a bug report against rc2 but I suspect it may be a different
issue, most of the crashes that appeared in the abrt mechanism were not
reportable.
FWIW here it is:
https://bugzilla.redhat.com/show_bug.cgi?id=1914598
But I think it's a different issue.
--
Ian Laurie
something weird happened in the update, I reverted to a backed
up copy of the vm (also reasonably up to date) and updated kernel* and
rebooted with the exact same results.
Is anyone else seeing this problem with VirtualBox guests?
--
Ian Laurie
ilau...@bigpond.net.au
55 matches
Mail list logo
