the command : $ dnf grouplist -v show mw I have this:
The env command show me most KDE variables and run the KDE environment
The Fedora 28 start with plasma KDE
I don't install kde , why is on my distro ?
Is this a bug ?
On Fri, Mar 30, 2018 at 8:41 AM Robert Van Voorhees <rcvanvo(a)gmail.com>
> While on the topic of Node.js versions, do we plan on moving Fedora 28 to
> Node 10, since their release dates coincide, or will Node 10 be pushed
> until Fedora 29?
> For those not aware, Node 10 is the next LTS, however it's LTS support
> does not start until October even though the release is slated for April:
My plan is for Fedora 28 traditional RPM repositories to ship Node.js 8
because I don't like changing defaults after Beta release. However, as
Fedora 28 is now the first release with support for Fedora Modularity, you
may have noticed that it is also providing a non-default module for Node.js
6.x and 9.x that one can switch to. So what I intend to do is package up
Node.js 10.x as quickly as possible and make that a non-default module in
F28 and the default for F29.
So, you'll be able to use it in Fedora 28 by doing `dnf module install
nodejs:10` if you want to. Also available as a module will be 6.x and 9.x
if you really want or need them, though they won't carry updates past
upstream's EOL, which is in April 2019 for 6.x and June 2018 for 9.x).
Just a general notice to anyone using Node.js in Fedora. We're not going to
be rebuilding for the releases in the Subject because there's no need. The
X.Y.1 releases were created because of a compilation mistake made by the
upstream binary release process and contain no additional commits. Since
Fedora and EPEL rebuild all of the sources in our own build environment,
there is no need to issue an update at this time.
Good Evening everyone!
So, I've been looking for a reliable way to handle Nvidia Optimus devices on Linux. Previously, I did a little work with bumblebee and rewrote quite a bit of the wiki page.
Recently however, I was told about this: https://github.com/solus-project/linux-driver-management
Based on a quick glance, this looks very similar to Ubuntu's implementation of Nvidia PRIME profiles and in my experience that is a very reliable way to handle the drivers on Optimus devices without breaking too many things.
Looking at Pagure, I found that the linux-driver-management package already exists, but it hasn't been integrated into Fedora yet.
I took a look at linux-driver-management's "distro integration" section (https://github.com/solus-project/linux-driver-management#distro-integration) and I feel a little lost about how exactly I should go about helping integrating it.
Could anyone please point me in the right direction?
So, I've been seeing this problem recently where every time I update the
Fedora kernel (currently F27), my grub configuration gets mangled.
I have tuned installed, so it has installed /etc/grub.d/00_tuned, which
executes /etc/tuned/bootcmdline, which in turn spits out when
grub2-mkconfig is run.
### BEGIN /etc/grub.d/00_tuned ###
### END /etc/grub.d/00_tuned ###
However, every time I update the F27 kernel, it mangles the params line, to
The =1" can be repeated many times. (I saw it go up to something like a
I do not know if this is related to the "broken pipe" error I see during
every kernel update, but it does seem to be a problem with tuned and grub
configuration updates during postinstall for kernel-core.
Every time this happens, I have to edit /etc/grub2.cfg (which points to
'../boot/grub2/grub.cfg') to remove the extra =1" characters before I
reboot. If I forget, the configuration file can't be read properly, and
grub stops at the. grub> prompt (this is a big pain on AWS EC2, because I
have to detach the drives and mount them elsewhere to fix, and then
I have not seen the same problem on F27 where I run grub2-efi... I've only
seen this in AWS EC2, which has grub2 installed in the MBR.
I've tried to track this down to the post-install scripts, and grubby, and
such, but I'm not really sure how all those tie together, and there's a lot
of pieces. I did try to run shellcheck:
[root@localhost ~]# shellcheck /usr/lib/kernel/install.d/*
/etc/kernel/postinst.d/* /etc/grub.d/* /etc/tuned/bootcmdline
It found a lot of things, but nothing stood out to me as obviously broken.
I'm not sure whether to file a bug against tuned, the kernel, or grub2 (for
failure to tolerate the config error), or if I should do more
troubleshooting first. If more troubleshooting, I'm not sure where to start.
Has anybody else seen this or know what I should try next? It does not
appear to be a problem with F26. It's annoying to manually edit the grub
configuration file every time I update my kernel... but currently, it's my