boot/grub
by Patrick Dupre
Hello,
On a multi-boot PC, how grub is updated?
In the past /etc/grub2.cfg was updated.
and now?
It seems that there are 2 tools: bootctl, and efibootmgr
What are the files managed by these tools?
How to understand?
BootCurrent: 000F
Which tool is run after an update of the kernel?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
3 years, 10 months
Prevent locking screen
by Beartooth
How do I tell Fedora (currently 32 fully upgraded) never to lock
the screen??
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is
3 years, 10 months
gnome-system-monitor with IO?
by ToddAndMargo
Hi All,
Anyone know of a substitute /usr/bin/gnome-system-monitor
that will show IO, like iotop, but with a gui?
Many thanks,
-T
3 years, 10 months
upgrade 30 to 32
by Patrick Dupre
Hello,
running:
dnf system-upgrade download --releasever=32
I get:
Modular dependency problem:
Problem: conflicting requests
- nothing provides module(platform:f31) needed by module gimp:2.10:3120191106095052:f636be4b-0.x86_64
Error:
Problem 1: package perl-PDL-LAPACK-0.12-1-1.fc30.x86_64 requires libperl.so.5.28()(64bit), but none of the providers can be installed
- package perl-PDL-LAPACK-0.12-1-1.fc30.x86_64 requires perl(:MODULE_COMPAT_5.28.2), but none of the providers can be installed
- perl-libs-4:5.28.2-444.fc30.x86_64 does not belong to a distupgrade repository
- problem with installed package perl-PDL-LAPACK-0.12-1-1.fc30.x86_64
- package perl-libs-4:5.28.2-442.module_f32+8059+8a5cccba.x86_64 is filtered out by modular filtering
- package perl-libs-4:5.28.2-442.module_f32+8111+66b92dcd.x86_64 is filtered out by modular filtering
- package perl-libs-4:5.28.2-444.module_f32+8513+01a85d28.x86_64 is filtered out by modular filtering
However
gimp is not installed
dnf remove perl-PDL-LAPACK
Modular dependency problem:
Problem: conflicting requests
- nothing provides module(platform:f31) needed by module gimp:2.10:3120191106095052:f636be4b-0.x86_64
No match for argument: perl-PDL-LAPACK
No packages marked for removal.
Dependencies resolved.
Nothing to do.
Complete!
How to solve the issue?
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
3 years, 10 months
windows10 disk not showing up
by Neal Becker
Today my wife's windows10 lenovo laptop was not starting normally, cycling through various "repair" screens. It does seem to work at least
minimally though.
I tried booting of my f32 usb stick and thought maybe I could take a look at the SSD. But when I start gnome disks, the internal SSD doesn't
show up! lsblk doesn't show it. I looked through journalctl and saw some reference to ATA1, and I believe some kind of error.
Anyone have any idea what's going on? The SSD is working enough to boot windows and run various things like file manager, so why doesn't it
show in linux?
3 years, 10 months
F32 Upgrade From F31 Produces Never Seen Before Error Message in
Gnome on Xorg and Possibly also KDE.
by Stephen Morris
HI,
I have a config file in /etc/X11/xorg.conf.d to start up DM's on
Xorg in 4K monitor resolution, as in F31 both Xorg and Wayland would
start up in 800x600 resolution and I would then have to minimize then
maximize the VM window for the DM to switch into 4K resolution as I
desired. After upgrading from F31 to F32 (there were lots of issues with
the upgrade that I will detail in other threads), when the Gnome on Xorg
DM starts up (I am using Virtualbox on Wndows 10) I get a message at the
top of the DM screen specifying 'VBOxClient: Failed to Register Resizing
Support'. What exactly does this message mean?
Looking at dmesg I also get lots of the following messages:
[ 2457.520753] Service: Shared Clipboard
[ 2457.532708] Service: Host Version Check
[ 2457.543366] Service: Seamless
[ 2457.568504] Service: Drag and Drop (DnD)
[ 2457.574146] Service: Display SVGA X11
[ 2457.593861] Running service failed: VERR_RESOURCE_BUSY
[ 2458.363216] rfkill: input handler disabled
[ 2476.932326] rfkill: input handler enabled
[ 2477.087703] A fatal guest X Window error occurred. This may just
mean that the Window system was shut down while the client was still runn
[ 2477.088440] A fatal guest X Window error occurred. This may just
mean that the Window system was shut down while the client was still runn
[ 2477.089249] A fatal guest X Window error occurred. This may just
mean that the Window system was shut down while the client was still runn
[ 2477.089476] Terminating threads ...
[ 2477.298103] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.298113] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.306374] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.306386] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2477.307899] Error waiting for HGCM thread to terminate: VERR_TIMEOUT
[ 2477.530080] Error waiting for X11 thread to terminate: VERR_TIMEOUT
[ 2477.530218] Terminating threads done
[ 2478.064888] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2478.064895] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.487676] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.487683] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.704766] Service: Shared Clipboard
[ 2734.706763] Service: Host Version Check
[ 2734.708109] Shared Clipboard: Starting X11 event thread
[ 2734.709898] Service: Seamless
[ 2734.711912] Service: Drag and Drop (DnD)
[ 2734.714049] Service: Display SVGA X11
[ 2734.716013] VMWARE's ctrl extension is available. Major Opcode is 128.
[ 2734.716183] Worker loop running
[ 2734.716706] Proxy window=6291457, root window=349 ...
[ 2734.716858] Started
[ 2734.716976] 6.1.8_Fedorar137981
[ 2734.717337] Failed to register resizing support, rc=VERR_RESOURCE_BUSY
[ 2734.834519] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.834527] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.878953] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2734.878961] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2735.068488] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2735.068496] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2736.203451] Service: Shared Clipboard
[ 2736.214513] Service: Host Version Check
[ 2736.257245] Service: Seamless
[ 2736.261294] Service: Drag and Drop (DnD)
[ 2736.262580] Running service failed: VERR_RESOURCE_BUSY
[ 2736.269149] Service: Display SVGA X11
[ 2736.272574] VMWARE's ctrl extension is available. Major Opcode is 128.
[ 2736.273835] Failed to register resizing support, rc=VERR_RESOURCE_BUSY
[ 2736.370194] Running service failed: VERR_RESOURCE_BUSY
[ 2736.612437] rfkill: input handler disabled
[ 2783.634779] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2783.634786] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2815.140895] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2815.140902] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2822.904030] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[ 2822.904038] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
regards,
Steve
3 years, 10 months
Re: Fedora 30 EOL
by Suvayu Ali
On Tue, May 26, 2020 at 4:23 PM Mohan Boddu <mboddu(a)bhujji.com> wrote:
>
> As of the 26th of May 2020, Fedora 30 has reached its end of life for
https://bugzilla.redhat.com/show_bug.cgi?id=1742960
Lately all my bug reports tend to go like this. Are others having the
same experience? I have been using Fedora a long time, and part of
the pleasure was I could contribute to making the distro better. Now
it seems to have reduced to "wait until it fixes itself", how is that
any different from Windows/Mac? It's very disappointing to see the
community aspect of Fedora go down this way while the OS has improved
by so much compared to when I started using Fedora.
--
Suvayu
Open source is the future. It sets us free.
3 years, 10 months
Pycharm repository package crashes on me
by Anil Felipe Duggirala
hello,
I am new to Fedora, and am happy about it. I installed Fedora 32 and was
offered to "install" third party repositories by the Software
application. There is one repository included in this list, which
contains the Pycharm IDE software. I have 2 questions:
1. What can you gain from installing from this repository? Considering
this is a Java app, it basically requires its own customized JRE. And
installing and running it (using the author's package) is as easy as
unpacking an archive.
2. As a follow up to the first question. What makes this particular
repository special in being included in this list?
I am complaining because I installed the app using this repository and
it was crashing, requiring a hard reboot. Running or "installing" this
app using the directly downloaded package works better. And installing
using the repository could (probably does) make changes to your system
Java installation.
thank you,,
Anil
3 years, 10 months
running browser as user different than root
by bruce
Hi.
Trying to understand/figure out some things.
I've logged in as root
I can start a browser -- FF, or chromium, no issue. (I know.. I
shouldn't. but I can.
However, if I fire up a term as another user, and then from the
cmdline, fire up chromium, I get an err msg
No protocol specified
Gtk-WARNING **: cannot open display: :0
I've been researching trying to figure out how to resolve this.
Any thoughts/pointers?
thanks
3 years, 10 months
