Re: running browser as user different than root

[Samuel Sieb]

On 5/31/20 8:35 PM, bruce wrote:

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


The user doesn't have permission to connect to the X server.  There are 
probably ways around that, but why?


"man xhost" might help.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: running browser as user different than root

[Roberto Ragusa]

On 2020-06-01 05:35, bruce wrote:


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.


The new user must have the EXPORT variable set to :0
  export DISPLAY=:0
but you probably already have it, given the error message above.

The new user must also be authorized to connect to the X server,
you have to run this as the OLD user, in your case it would be the
(very unsafe) root user.
  xhost si:localuser:thenameofthenewuser

This should be enough to open a new browser, then additional steps
are needed if you want for example ability to play sound.

Having different browsers running as different users for different tasks
is a good idea (better cookie privacy, different config and extensions, ...),
but running your main session as root is something being considered
a really bad idea for at least 25 years.

Regards.
--
   Roberto Ragusamail at robertoragusa.it
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Noticed in change in action after upgrade from 30 to 31.

[Michael D. Setzer II via users]

> On 5/31/20 10:41 PM, Michael D. Setzer II via users wrote:
>> Just upgraded a machine and noticed that with version
>> 30, when I had a process running in a terminal window,
>> when it completed it would report that the command
>> finished, and would provide the scripts name. After the
>> upgrade, the messages now just show bash completed
>> rather than the specific command?
>
> I'm using Gnome on F31 and the notification includes the command that
> completed.

Did a little more testing.
Found that somethings did report the program that just completed rather
than just saying that bash completed.
Had one command that did the bash thing, and know that with fc30 it would
say that dnfup completed.

The file just had the lines
dnf clean all
dnf update -y

Have discovered that adding
#!/usr/bin/bash

to the file does have it report
Command completed
/usr/bin/bash /usr/bin/dnfup


> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Patrick Dupre]

Thank again,

with the -v option, I have
BootCurrent: 
Timeout: 1 seconds
BootOrder: ,0002,0001
Boot* fedora
HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
Boot0001* Hard DriveBBS(HD,,0x0)..GO..NOo.I.N.T.E.L. 
.S.S.D.S.C.2.K.W.1.8.0.H.6A...>..Gd-.;.A..MQ..L.V.C.T.L.2.6.4.6.4.0.6.Z.8.1.B.0.N.G.
 . BO..NOo.W.D.C. 
.W.D.1.0.E.Z.E.X.-.2.2.M.F.C.A.0A...>..Gd-.;.A..MQ..L.
 . . . .W. .-.D.C.W.6.C.3.Y.E.Z.2.S.K.PBO..NOo.M.a.x.t.o.r. 
.6.Y.0.8.0.M.0A...>..Gd-.;.A..MQ..L.2.Y.C.3.H.3.E.2.
 . . . . . . . . . . . BO
Boot0002* CD/DVD Drive  
BBS(CDROM,,0x0)..GO..NOo.D.R.W.-.2.4.D.5.M.TA...>..Gd-.;.A..MQ..L.3.K.G.F.Q.6.2.G.2.8.
 .7. . . . . . . . BO

If I understand correctly,
I boot on Boot  which is on partition 3 (hd0) using 
/boot/efi/EFI/fedora/grubx64.efi

However, I do not understand how does this work with multi disks.
We have
/boot/efi/EFI/fedora/grubx64.efi
on each disk ?
Which does not seem to be the case.

If I run
grubby --info=ALL

I get only the boot system available on the mounted system

What bothers me also is the date of /boot/efi/EFI/fedora/grub.cfg
-rwx--. 1 root root 15119 Jun  9  2019

I can regenerate it and I have
set default_kernelopts="root=/dev/mapper/VolSys_1-root ro 
rd.lvm.lv=VolSys_1/root "
I guess from
cat /etc/default/grub 
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys_1/root"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true

But the rest of /boot/efi/EFI/fedora/grub.cfg is not coherent:
There is no menuentry matching the kernels which are on this disk.
There are mixing which old kernels (fc28) from other disks.

Now,
I boot on another disk (fc30)
There is no
/boot/efi/EFI/fedora/grub.cfg
It means that after update of the kernel, 
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
has not been run.

Thus, I am confuse.

In case of multidisks, what does what?


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===

>
> On 5/31/20 1:45 PM, Patrick Dupre wrote:
> > Thanks,
> > You are correct.
> > I also have Boot000F* Fedora
> > from this distribution (BootCurrent: 000F)
> > and
> > BootCurrent: 
> > Timeout: 1 seconds
> > BootOrder: ,0002,0001,0003,0004,0005
> > Boot* fedora
> >  From another one.
> > I wanted to understand what this means.
> > There is logic in this numbers.
> 
> I assume you're looking at the output of "efibootmgr", use "efibootmgr 
> -v" for more info.  That gives you the list of configured boot entries 
> in the EFI which will be different in each computer.  Fedora will take 
> the first available slot it finds.  Those are 4 digit hex numbers.  The 
> BootCurrent indicates which entry is currently booted.  The BootOrder 
> shows which entries it will try in order until it gets one that works.
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

upgrade from .iso

[Patrick Dupre]

Hello,

dnf system-upgrade download --releasever=32

make the upgrade through internet

How can I do the same from a .iso file ?

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: running browser as user different than root

[bruce]

Hi Roberto

Thanks for the reply.

On Mon, Jun 1, 2020 at 4:38 AM Roberto Ragusa  wrote:
>
> On 2020-06-01 05:35, bruce wrote:
>
> > 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.
>
> The new user must have the EXPORT variable set to :0
>export DISPLAY=:0
> but you probably already have it, given the error message above.
>
> The new user must also be authorized to connect to the X server,
> you have to run this as the OLD user, in your case it would be the
> (very unsafe) root user.
>xhost si:localuser:thenameofthenewuser
>

I tried to implement your suggestion as follows:

logged in as root
in a "root" term window
echo $DISPLAY   (shows)
:0.0

xhost si:root:test

(generates)

root:test being added to access control list
X Error of failed request:  BadValue (integer parameter out of range
for operation)
  Major opcode of failed request:  109 (X_ChangeHosts)
  Value in failed request:  0x9
  Serial number of failed request:  7
  Current serial number in output stream:  9

which doesnt appear to "succeed"!

And yes, I know logging/running as root is "bad".

I'd still like to know how to resolve this issue, as opposed to just
saying don't do this.

thanks
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: running browser as user different than root

[Roberto Ragusa]

On 2020-06-01 12:31, bruce wrote:

Hi Roberto

Thanks for the reply.

On Mon, Jun 1, 2020 at 4:38 AM Roberto Ragusa  wrote:


xhost si:localuser:thenameofthenewuser



xhost si:root:test


"localuser" is a string that you do not have to change, it specifies the kind 
of rule
we are doing.

Try:

  xhost si:localuser:test

Regards.

--
   Roberto Ragusamail at robertoragusa.it
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Aplay problem -

[Bob Goodwin]

On 2020-05-31 22:12, Samuel Sieb wrote:


If you rebooted, then the runaway script is gone and won't be 
affecting anything.  I'm confused how you say some things can run 
aplay and make audio, but you can't run it directly.

_

°
Yes, confusing to me too, I try only to query when I reach the end of my 
limited skill set.


It seems to me like a path through Pulseaudio is broken. I will go back 
and try again with all I have there, the pavolume GUI. Will report back 
if I find anything, day just begins here ...


Thanks all for the suggestions,   Bob

--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
FEDORA-32/64bit LINUX XFCE Fastmail POP3
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: running browser as user different than root

[bruce]

Hi Roberto

You are 'da man!

this worked   xhost si:localuser:test

using this in the "root" term window,

and then running the cmd to fire up the test firefox browser generated
the process.

when i now run "xhost" from the root term, i see the different values.
I suppose I can "safely" delete the added item with no damage!

thanks

On Mon, Jun 1, 2020 at 6:46 AM Roberto Ragusa  wrote:
>
> On 2020-06-01 12:31, bruce wrote:
> > Hi Roberto
> >
> > Thanks for the reply.
> >
> > On Mon, Jun 1, 2020 at 4:38 AM Roberto Ragusa  wrote:
> >>
> >> xhost si:localuser:thenameofthenewuser
> >>
> >
> > xhost si:root:test
> >
> "localuser" is a string that you do not have to change, it specifies the kind 
> of rule
> we are doing.
>
> Try:
>
>xhost si:localuser:test
>
> Regards.
>
> --
> Roberto Ragusamail at robertoragusa.it
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[stan via users]

On Mon, 1 Jun 2020 11:20:31 +0200
"Patrick Dupre"  wrote:

> If I run
> grubby --info=ALL
> 
> I get only the boot system available on the mounted system
> 
> What bothers me also is the date of /boot/efi/EFI/fedora/grub.cfg
> -rwx--. 1 root root 15119 Jun  9  2019
> 
> I can regenerate it and I have
> set default_kernelopts="root=/dev/mapper/VolSys_1-root ro
> rd.lvm.lv=VolSys_1/root " I guess from
> cat /etc/default/grub 
> GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
> GRUB_DEFAULT=saved
> GRUB_DISABLE_SUBMENU=true
> GRUB_TERMINAL_OUTPUT="console"
> GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys_1/root"
> GRUB_DISABLE_RECOVERY="true"
> GRUB_ENABLE_BLSCFG=true
> 
> But the rest of /boot/efi/EFI/fedora/grub.cfg is not coherent:
> There is no menuentry matching the kernels which are on this disk.
> There are mixing which old kernels (fc28) from other disks.
> 
> Now,
> I boot on another disk (fc30)
> There is no
> /boot/efi/EFI/fedora/grub.cfg
> It means that after update of the kernel, 
> grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
> has not been run.
> 
> Thus, I am confuse.
> 
> In case of multidisks, what does what?

I do not fully understand this, but Chris Murphy explained that there
is only the *one* /boot/efi/ per system and only *one* entry for fedora
in /boot/efi/EFI/. As I understand it, this is because of the efi
standard.  So, if booting more than one version of fedora using efi,
the grub.cfg in /boot/efi/EFI/fedora has to be changed to point to the
correct /boot/loader/entries for that fedora. You could have several
versions of the grub.cfg and just swap them to boot other versions.
Messy. Apparently, this can be solved by using systemd bootctl, an
alternative to grub2, but fedora does not use that and I haven't
investigated further.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Patrick Dupre]

Thanks,

Actually, I am lost.
I am upgrading one of the systems on a multi-disks system.
1) I realized that one system is not efi, while the other ones are.
2) After I upgraded this system. I can boot it, but it is weird.
a) There was no update of the grub menu (I boot fc32, while the invitation
is still fc30)
b) grub2-mkconfig has not been run
c) grub2-mkconfig (manually) did not recognized by the booted system except 
through
set root='hd2,msdos3', but no menuentry for this system.


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===


> Sent: Monday, June 01, 2020 at 2:55 PM
> From: "stan via users" 
> To: users@lists.fedoraproject.org
> Cc: "stan" 
> Subject: Re: boot/grub
>
> On Mon, 1 Jun 2020 11:20:31 +0200
> "Patrick Dupre"  wrote:
> 
> > If I run
> > grubby --info=ALL
> > 
> > I get only the boot system available on the mounted system
> > 
> > What bothers me also is the date of /boot/efi/EFI/fedora/grub.cfg
> > -rwx--. 1 root root 15119 Jun  9  2019
> > 
> > I can regenerate it and I have
> > set default_kernelopts="root=/dev/mapper/VolSys_1-root ro
> > rd.lvm.lv=VolSys_1/root " I guess from
> > cat /etc/default/grub 
> > GRUB_TIMEOUT=5
> > GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
> > GRUB_DEFAULT=saved
> > GRUB_DISABLE_SUBMENU=true
> > GRUB_TERMINAL_OUTPUT="console"
> > GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys_1/root"
> > GRUB_DISABLE_RECOVERY="true"
> > GRUB_ENABLE_BLSCFG=true
> > 
> > But the rest of /boot/efi/EFI/fedora/grub.cfg is not coherent:
> > There is no menuentry matching the kernels which are on this disk.
> > There are mixing which old kernels (fc28) from other disks.
> > 
> > Now,
> > I boot on another disk (fc30)
> > There is no
> > /boot/efi/EFI/fedora/grub.cfg
> > It means that after update of the kernel, 
> > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
> > has not been run.
> > 
> > Thus, I am confuse.
> > 
> > In case of multidisks, what does what?
> 
> I do not fully understand this, but Chris Murphy explained that there
> is only the *one* /boot/efi/ per system and only *one* entry for fedora
> in /boot/efi/EFI/. As I understand it, this is because of the efi
> standard.  So, if booting more than one version of fedora using efi,
> the grub.cfg in /boot/efi/EFI/fedora has to be changed to point to the
> correct /boot/loader/entries for that fedora. You could have several
> versions of the grub.cfg and just swap them to boot other versions.
> Messy. Apparently, this can be solved by using systemd bootctl, an
> alternative to grub2, but fedora does not use that and I haven't
> investigated further.
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Jonathan Billings]

On Mon, Jun 01, 2020 at 11:20:31AM +0200, Patrick Dupre wrote:
> with the -v option, I have
> BootCurrent: 
> Timeout: 1 seconds
> BootOrder: ,0002,0001
> Boot* fedora  
> HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
> [...]
> However, I do not understand how does this work with multi disks.
> We have
> /boot/efi/EFI/fedora/grubx64.efi
> on each disk ?
> Which does not seem to be the case.

If you see in the Fedora entry, it has:
HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800\
,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)

That means to look for a volume with the 3rd GPT partition, with the
UUID of a5c3bc11-e83b-48d0-be96-783af37228f1 (and some other data).
On that disk, look for the /EFI/FEDORA/GRUBX64.EFI executable
(remember, this is a DOS filesystem so it's case-insensitive).

Run 'blkid' on a running system, and you'll see that the PARTUUID of
the EFI volume matches the UUID in the above EFI entry.

You can have an EFI volume on multiple disks.  EFI also supports
things like network boot, which has a different syntax EFI entry.  The
efibootmgr command does a lot of the hard work of figuring that out
for you, so you don't need to manually enter that information.

-- 
Jonathan Billings 
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[George N. White III]

On Mon, 1 Jun 2020 at 01:23, Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:

> On Fri, 29 May 2020, George N. White III wrote:
>
> > Have you tried the vga= kernel boot parameter?   For Xwindows it would be
> > good to get something other than VESA running, either i915 or by adding a
> > graphics card.
>
> I have now.
> No go.
>
> > I had a look at the dmesg log on an old system with Nvidia card.   It was
> > set to display
> > the startup messages, which were initially at low res then switched to
> the
> > resolution of
> > the monitor.  The switch appears to occur when dmesg reports that nouveau
> > has started.
> > Have you looked in dmesg for any indication of why it doesn't load the
> i915
> > driver?
>
> It does load the i915 driver.
> [   60.044675] pci :00:00.0: detected 8192K stolen memory
> [   60.054985] checking generic (e000 7f) vs hw (f010 8)
> [   60.054987] checking generic (e000 7f) vs hw (e000 1000)
> [   60.054988] fb0: switching to inteldrmfb from VESA VGA
> [   60.065317] Console: switching to colour dummy device 80x25
> [   60.065381] i915 :00:02.0: vgaarb: deactivate vga console
> [   60.066924] [drm] ACPI BIOS requests an excessive sleep of 4022337523
> ms, using 1500 ms instead
> [   60.066933] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [   60.066936] [drm] Driver supports precise vblank timestamp query.
> [   60.067241] i915 :00:02.0: vgaarb: changed VGA decodes:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [   60.084775] [drm] Initialized overlay support.
> [   60.086225] [drm] Initialized i915 1.6.0 20200114 for :00:02.0 on
> minor 0
> [   60.086456] ACPI: Video Device [GFX0] (multi-head: no  rom: yes  post:
> no)
> [   60.086568] input: Video Bus as
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
> [   60.118670] fbcon: i915drmfb (fb0) is primary device
>

But the snippet from Xorg.0.log had:


[   109.570] (EE) Unable to find a valid framebuffer device
[   109.571] (EE) open /dev/fb0: No such file or directory
[   109.571] (EE) Screen 0 deleted because of no matching config section.



> [   60.163409] Console: switching to colour frame buffer device 180x56
> [   60.183707] i915 :00:02.0: fb0: i915drmfb frame buffer device
>

If you edit the options in the boot command line to remove what ever "rhgb
quiet" has morphed to you should see the first few lines in low res. and
then the 180x56 text output.   Have a look at
https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen


> Is this bit from dmesg relevant?
> [0.676375] PCI: Using host bridge windows from ACPI; if necessary, use
> "pci=nocrs" and report a bug
> [0.677023] ACPI: Enabled 11 GPEs in block 00 to 3F
> [0.685546] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
> [0.68] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM
> ClockPM Segments MSI HPX-Type3]
> [0.685562] ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments -
> ASL declared 5, ACPI requires 4 (20200110/nsarguments-160)
> [0.685616] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PCI0._OSC.CAPD], AE_ALREADY_EXISTS (20200110/dsfield-181)
> [0.685625] ACPI Error: Aborting method \_SB.PCI0._OSC due to previous
> error (AE_ALREADY_EXISTS) (20200110/psparse-529)
>

https://bugzilla.kernel.org/show_bug.cgi?id=198003  I've seen this before,
probably on boxes similar to yours.
https://access.redhat.com/solutions/58790 explains workarounds and
their consequences, also useful is
https://www.kernel.org/doc/html/v5.6/admin-guide/kernel-parameters.html


I'm calling it a night.
> Frustration is exhausting.
>

I was lucky that I didn't really need X11 to work on the similar boxes
(they ran lightweight batch processing
in a machine room and also managed the UPS's via serial ports).   Some
people actually repair the buggy BIOS:
https://forums.freebsd.org/threads/acpi-error-excess-arguments-asl-declared-5-acpi-requires-4.71283/
.


--
George N. White III
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: windows10 disk not showing up

[Neal Becker]

Thanks for all the suggestions.  Just to review, the issue was the drive
didn't even appear in lsblk, so nothing can be done to fix it.
It is possible it was partially failing, it seems after multiple windows
reboots and repairs it is working again, although
at least one app had to be reinstalled.  I only use linux myself, so I know
nothing about windows or how to diagnose it.
So my real question was not how to fix the drive, but why it doesn't even
show up on linux.
Thanks
Neal

On Sat, May 30, 2020 at 6:26 PM George N. White III 
wrote:

> On Sat, 30 May 2020 at 10:37, Neal Becker  wrote:
>
>> 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've seen this with older version of Windows.  The "repair" may have
> repaired the "original" Windows boot configuration, but the
> need for the repair is most likely due to a failing drive.   Using the USB
> live stick you should be able to install smartmontools to check the drive.
>
>
>> 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?
>>
>
> Windows may have messed with "BIOS" settings in an attempt to recover from
> a problem.
>
> How old is the drive?  SSD bits have a limited lifetime.   Some workloads
> (video production) that fill, empty, and refill the drive  very hard on
> SSD's. Wear leveling strategies try to make the wear even across all the
> bits, and there are spares when a bit goes bad, but eventually the spares
> are used up and you lose data in some high-wear area.  You should use
> ddrescue to image the drive and attempt repairs on the image rather than
> tying to do repairs on a failing drive.
>
> --
> George N. White III
>
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>


-- 
*Those who don't understand recursion are doomed to repeat it*
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: upgrade from .iso

[Samuel Sieb]

On 6/1/20 3:05 AM, Patrick Dupre wrote:

dnf system-upgrade download --releasever=32

make the upgrade through internet

How can I do the same from a .iso file ?


You can't.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How to install Wifi firmware so it's not overwritten?

[Richard Shaw]

On Sat, May 30, 2020 at 12:36 PM George N. White III 
wrote:

> On Sat, 30 May 2020 at 13:17, Richard Shaw  wrote:
>
>> I installed Fedora 32 on an SD card on my MS Surface GO. I can get it to
>> boot up fine (but the surface has a funky UEFI bios) but no Wifi.
>>
>
> Normally dmesg should give some indication of why the wifi fails.
>

Yeah, but it's a known issue that you need the board file from
killernetworking. I went ahead and ordered a USB-C to Ethernet adapter
which also give you 3 regular USB ports. I was having to use Fedora Media
Writer to put F32 on my ONLY USB-C compatible stick and then restore it so
I could copy the board file over. Got too tedious. Ethernet will make it a
lot easier to get updates and perhaps install reFIND so I can get it to
boot linux without having to use the Windows Advanced Recovery method.

It would be useful to find out why your system needs a different board
> file.   https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174 was
> updated more recently than the links, so the update might not break
> anything.
> You can try the board files from github the same way you would with above
> links (and compare them to see if they
> really are different).
>
>
>> Is there another method that would work better?
>>
>
> Submit a board file that works to upstream:
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
>

I'll take a look, thanks.

Thanks,
Richard
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Roger Heflin]

When the policy is not being followed and/or not enforced it means
nothing.  Only someone who is in love with
the policy would say otherwise and actively defend it.  I am going to
guess you helped write large parts of the policy
and that is why you defined it.  Yes, lets enforce the policy against
the everyone until you have no community.
Since there are packages going unmaintained it not like they are that
easily replaceable.  It is you as a "insider"
that seems to be denying the "perfect" policy is not functioning as
often as you like and not admitting that it can
be made to work with the staff you had.  If the maintainer for the
kernel package is not following it,
I doubt many are following it.

And while you are calling me an outsider, I have been using what
became fedora for years before the first fedora
version was released, and have been using it almost every version since then.

On the fedora side we should probably be directing anyone with
software bugs to upstream.  I am going to guess
that the guidelines were copied from the enterprise side where they
are maintaining packages that are years behind
upstream, were as fedora would rarely be in that position, and it
would be best to direct them to upstream.  And
then create a BZ to backport a patch and/or uplift to the new version.
Getting the package maintainer in the middle
seems to only add either failure or at best friction to the process.

Setting the standards too high removes viable resources of people that
may have just retired from a job
and don't want a job with hard defined guidelines.

Don't get me started about generally negative value automated response
from the PAID distribution vendors,
they seem to be an extension of the generally worthless process were
the exact same information is asked to be
collected for each bug for it to progress to the next level, even if
that information is not pertinent to the given bug.
The automation does not solve the problem, it only pisses everyone off
more with its negative value added messages,
and arbitrary requirements that may have no useful reason to be done
for the bug in question.  The distribution vendors
love sosreport for anything even for clear bugs that an sosreport is useless.


On Sun, May 31, 2020 at 3:14 AM Michael Schwendt  wrote:
>
> On Sat, 30 May 2020 16:42:10 -0500, Roger Heflin wrote:
>
> > The policy means nothing when
>
> Only an "outsider" would say that. That policy has been refined multiple
> times since the fedora.us era with its strict QA policies. That policy is
> also reason why potential "maintainers" shy away from the community
> project, because as volunteers they can't tell whether they would be able
> to meet the requirements. I could point you at the related "non-responsive
> maintainer policy", but so far you aren't listening.
>
> > the staffing is not there to actually do the tasks.
>
> Sweet how you try to dance around the problem. Where bugzilla components
> are literally flooded with tickets, automation would be the way to go.
> That has been pointed out before. Meaningful, early responses that give
> bug reporters some guidance on where and how they could escalate an issue,
> where they could discuss an issue in order to gather more details and to
> confirm a problem, and and and.
>
> > And clearly there is limited staffing.  And if they are a volenteer
> > then tell them they arent doing their job and kick them out.  Repeat until
> > there is no community and you have no staff.
>
> Key components are still maintained by Red Hat. That is an essential and
> important contribution to this project. Offer a distribution that doesn't
> satisfy users, and you lose (or reduce) the user part of the community
> including most of the guinea pigs.
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[stan via users]

On Mon, 1 Jun 2020 15:23:26 +0200
"Patrick Dupre"  wrote:

> Thanks,
> 
> Actually, I am lost.
> I am upgrading one of the systems on a multi-disks system.
> 1) I realized that one system is not efi, while the other ones are.
> 2) After I upgraded this system. I can boot it, but it is weird.
> a) There was no update of the grub menu (I boot fc32, while the
> invitation is still fc30)
> b) grub2-mkconfig has not been run
> c) grub2-mkconfig (manually) did not recognized by the booted system
> except through set root='hd2,msdos3', but no menuentry for this
> system.

I've exhausted my knowledge.  I'll make some suggestions, but no
guarantees.

Check /etc/default/grub on the F32 system, and make sure that all the
entries are correct for the F32 system.  It needs to have
GRUB_ENABLE_BLSCFG=true
somewhere in there so that boot loader snippets will work.

Look in /boot/loader/entries/ on the F32 system, and make sure that
there is an entry for each of the F32 kernels that you have installed.

Go into /boot/efi/EFI/fedora/ and run
grub2-mkconfig -o grub.cfg

A reboot should now show F32 as a viable boot option, and as the
default.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[stan via users]

On Mon, 1 Jun 2020 10:10:41 -0400
Jonathan Billings  wrote:

> If you see in the Fedora entry, it has:
> HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800\
> ,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
> 
> That means to look for a volume with the 3rd GPT partition, with the
> UUID of a5c3bc11-e83b-48d0-be96-783af37228f1 (and some other data).
> On that disk, look for the /EFI/FEDORA/GRUBX64.EFI executable
> (remember, this is a DOS filesystem so it's case-insensitive).
> 
> Run 'blkid' on a running system, and you'll see that the PARTUUID of
> the EFI volume matches the UUID in the above EFI entry.
> 
> You can have an EFI volume on multiple disks.  EFI also supports
> things like network boot, which has a different syntax EFI entry.  The
> efibootmgr command does a lot of the hard work of figuring that out
> for you, so you don't need to manually enter that information.
> 
You seem knowledgeable, so I'll ask you.  How does the efi firmware
decide which /boot/efi to use as the source when the computer is
started?  Does it have to be selected from the efi firmware menu at
each boot?
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Patrick Dupre]

Hello,

I guess that very think is more or less, OK, I have just some difficulties
to understand the logic.
> How does the efi firmware decide which /boot/efi to use as the source when 
> the computer is started

I realized that I have only one EFI System Partition on sda
By default, the system goes to grub, where I can choose the OS.
I do not use the efi options to go there (at least intentionally).

> Does it have to be selected from the efi firmware menu at each boot?
I do not think so. As I said, I go directly to the grub menu (by default).
I guess that if I active the efi menu, I could choose other options to boot.


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===


>
> On Mon, 1 Jun 2020 10:10:41 -0400
> Jonathan Billings  wrote:
> 
> > If you see in the Fedora entry, it has:
> > HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800\
> > ,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
> > 
> > That means to look for a volume with the 3rd GPT partition, with the
> > UUID of a5c3bc11-e83b-48d0-be96-783af37228f1 (and some other data).
> > On that disk, look for the /EFI/FEDORA/GRUBX64.EFI executable
> > (remember, this is a DOS filesystem so it's case-insensitive).
> > 
> > Run 'blkid' on a running system, and you'll see that the PARTUUID of
> > the EFI volume matches the UUID in the above EFI entry.
> > 
> > You can have an EFI volume on multiple disks.  EFI also supports
> > things like network boot, which has a different syntax EFI entry.  The
> > efibootmgr command does a lot of the hard work of figuring that out
> > for you, so you don't need to manually enter that information.
> > 
> You seem knowledgeable, so I'll ask you.  How does the efi firmware
> decide which /boot/efi to use as the source when the computer is
> started?  Does it have to be selected from the efi firmware menu at
> each boot?
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Kevin Becker]

My system has two efi boot partitions on separate drives.  I rarely
boot to Windows and I wanted it on its own completely separate
drive.  I configured a default in the firmware settings and then for a
while I would choose an alternate when I needed to by hitting a key to
bring up the efi boot menu.  Eventually I got around to adding a boot
entry for my second (WIndows) drive to grub on the main drive and now I
can just select Windows from grub if I need to boot into it.

On Mon, 2020-06-01 at 20:13 +0200, Patrick Dupre wrote:
> Hello,
> I guess that very think is more or less, OK, I have just some
> difficultiesto understand the logic.
> > How does the efi firmware decide which /boot/efi to use as the
> > source when the computer is started
> 
> I realized that I have only one EFI System Partition on sdaBy
> default, the system goes to grub, where I can choose the OS.I do not
> use the efi options to go there (at least intentionally).
> > Does it have to be selected from the efi firmware menu at each
> > boot?
> I do not think so. As I said, I go directly to the grub menu (by
> default).I guess that if I active the efi menu, I could choose other
> options to boot.
> 
> =
> == Patrick DUPRÉ | | email: 
> pdu...@gmx.com
>  Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain
> Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33
> (0)380395988=
> ==
> 
> > On Mon, 1 Jun 2020 10:10:41 -0400Jonathan Billings <
> > billi...@negate.org> wrote:
> > > If you see in the Fedora entry, it has:HD(3,GPT,a5c3bc11-e83b-
> > > 48d0-be96-
> > > 783af37228f1,0x2001800\,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
> > > That means to look for a volume with the 3rd GPT partition, with
> > > theUUID of a5c3bc11-e83b-48d0-be96-783af37228f1 (and some other
> > > data).On that disk, look for the /EFI/FEDORA/GRUBX64.EFI
> > > executable(remember, this is a DOS filesystem so it's case-
> > > insensitive).
> > > Run 'blkid' on a running system, and you'll see that the PARTUUID
> > > ofthe EFI volume matches the UUID in the above EFI entry.
> > > You can have an EFI volume on multiple disks.  EFI also
> > > supportsthings like network boot, which has a different syntax
> > > EFI entry.  Theefibootmgr command does a lot of the hard work of
> > > figuring that outfor you, so you don't need to manually enter
> > > that information.
> > You seem knowledgeable, so I'll ask you.  How does the efi
> > firmwaredecide which /boot/efi to use as the source when the
> > computer isstarted?  Does it have to be selected from the efi
> > firmware menu ateach
> > boot?___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: 
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> > 
> ___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: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Systemd-boot for MS Surface GO?

[Richard Shaw]

So I want to dual boot Windows 10 and Fedora on my MS Surface GO but the
funky Microsoft UEFI REALLY doesn't like grub.

I've read up a bit on systemd-boot and found references that it should work
with the Surface GO but one of the requirements is that the kernel be
compiled to be compatible with EFI executables and that the kernel and
initrd are on the EFI partition.

I get the idea, but practically speaking how would I accomplish that?

1. resize the EFI partition to be 1GB?
2. Somehow update /etc/fstab to make /boot and /boot/efi the same
partition? Bind mount?
3. Install systemd-boot (How do I stop grub from messing things up?)

Anyone done this?

Thanks,
Richard
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[stan via users]

On Mon, 01 Jun 2020 14:28:46 -0400
Kevin Becker  wrote:

> My system has two efi boot partitions on separate drives.  I rarely
> boot to Windows and I wanted it on its own completely separate
> drive.  I configured a default in the firmware settings and then for a
> while I would choose an alternate when I needed to by hitting a key to
> bring up the efi boot menu.  Eventually I got around to adding a boot
> entry for my second (WIndows) drive to grub on the main drive and now
> I can just select Windows from grub if I need to boot into it.

Thanks, that's how I thought it would work.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Systemd-boot for MS Surface GO?

[stan via users]

On Mon, 1 Jun 2020 14:13:35 -0500
Richard Shaw  wrote:

> So I want to dual boot Windows 10 and Fedora on my MS Surface GO but
> the funky Microsoft UEFI REALLY doesn't like grub.
> 
> I've read up a bit on systemd-boot and found references that it
> should work with the Surface GO but one of the requirements is that
> the kernel be compiled to be compatible with EFI executables and that
> the kernel and initrd are on the EFI partition.
> 
> I get the idea, but practically speaking how would I accomplish that?
> 
> 1. resize the EFI partition to be 1GB?
> 2. Somehow update /etc/fstab to make /boot and /boot/efi the same
> partition? Bind mount?
> 3. Install systemd-boot (How do I stop grub from messing things up?)
> 
> Anyone done this?

No, but I look forward to your journey as I would like to know also.
:-)  The part about being able to make the system unbootable because
of an error in installing bootctl has made me hesitant to experiment.

I think the way to go is to create another efi partition as /boot/test
and make all the changes there.  When you are ready to test, change
fstab to point to that partition in fstab, as /boot using the UUID.
That will mask the boot in the already installed fedora, and if you have
/boot/test set up correctly, should boot into the existing fedora.  You
will also have to have the windows setup in /boot/test in order to boot
it.  Some hand waving in there, but could work with tweaking, I think.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: running browser as user different than root

[Roberto Ragusa]

On 2020-06-01 10:37, Roberto Ragusa wrote:


The new user must have the EXPORT variable set to :0
   export DISPLAY=:0

Replying to myself to fix a mistake that would remain in the ML archives.

The new user must have an exported DISPLAY variable set to :0
   export DISPLAY=:0

--
   Roberto Ragusamail at robertoragusa.it
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Pycharm repository package crashes on me

[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
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Pycharm repository package crashes on me

[Samuel Sieb]

On 6/1/20 1:20 PM, Anil Felipe Duggirala wrote:
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.


It can be installed system-wide.  All the files are managed by the 
package manager which lets you cleanly upgrade or remove it later.


2. As a follow up to the first question. What makes this particular 
repository special in being included in this list?


I'm curious about that as well.

I am complaining because I installed the app using this repository and 
it was crashing, requiring a hard reboot. Running or "installing" this 


That seems unlikely.  Can you provide more details?

app using the directly downloaded package works better. And installing 
using the repository could (probably does) make changes to your system 
Java installation.


No, that would be another benefit of using the Fedora packaging.  It 
will be setup to not mess up any other part of the Fedora installation.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 30 EOL

[Michael Schwendt]

On Mon, 1 Jun 2020 12:09:36 -0500, Roger Heflin wrote:

> When the policy is not being followed and/or not enforced it means
> nothing.  Only someone who is in love with
> the policy would say otherwise and actively defend it.

You're still not getting it.

> I am going to guess you helped write large parts of the policy
> and that is why you defined it.

???

> Yes, lets enforce the policy against
> the everyone until you have no community.

See above. You're not getting it. You talk about "enforcing" something,
you preach stagnation. That isn't helpful and not a way forward for Fedora.

> Since there are packages going unmaintained it not like they are that
> easily replaceable.

???

> It is you as a "insider"
> that seems to be denying the "perfect" policy is not functioning as
> often as you like and not admitting that it can
> be made to work with the staff you had.  If the maintainer for the
> kernel package is not following it,
> I doubt many are following it.

Please stop guessing. It can't generalized like that. Quite obviously,
there are _many_ packages that are much easier to maintain than the kernel
package (with its ticket linked earlier in this thread). There are
different aspects of maintenance. Handling bug reports is just one of many
tasks.

> And while you are calling me an outsider, I have been using what
> became fedora for years before the first fedora
> version was released, and have been using it almost every version since then.

The question about your "background" was necessary because it becomes
apparent that you comment on things as one who either doesn't know how
things work at the Fedora Project (or how things are supposed to work) or
you deliberately ignore it. You don't seem to care about project policies
and guidelines, and you brush aside what's there as a base. You even ignore
what different levels of maintenance are needed for different packages.

> On the fedora side we should probably be directing anyone with
> software bugs to upstream.

Should? Probably? And you expect upstream to not be understaffed,
especially not if being flooded with bug reports which may be
distribution-specific?

> Don't get me started about [...]

Thread is closed for me.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Systemd-boot for MS Surface GO?

[Samuel Sieb]

On 6/1/20 12:13 PM, Richard Shaw wrote:
So I want to dual boot Windows 10 and Fedora on my MS Surface GO but the 
funky Microsoft UEFI REALLY doesn't like grub.


In what way?  The UEFI boot shouldn't care what you're booting.  It just 
takes the signed boot binary and runs it.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

upgrade 30 to 32

[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: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Michael Young]

On Mon, 1 Jun 2020, Patrick Dupre wrote:


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


This can be solved by
dnf module reset \*


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


It looks like there is no  perl-PDL-LAPACK package in Fedora 32, so you 
will probably have to delete that package for the update to work.


Michael Young
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Samuel Sieb]

On 6/1/20 2:00 PM, Patrick Dupre wrote:

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


This can be ignored.  dnf will resolve it in the end.


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


This must be something you installed yourself.  It's not from Fedora.


dnf remove perl-PDL-LAPACK
No match for argument: perl-PDL-LAPACK


You can either try adding "--allowerasing" to the system-upgrade command 
or try:

dnf remove perl-PDL-LAPACK*
Maybe the version number is part of the name.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Patrick Dupre]

This has been solved by

rpm -e perl-PDL-LAPACK-0.12-1-1.fc30.x86_64

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===


> Sent: Monday, June 01, 2020 at 11:09 PM
> From: "Samuel Sieb" 
> To: users@lists.fedoraproject.org
> Subject: Re: upgrade 30 to 32
>
> On 6/1/20 2:00 PM, Patrick Dupre wrote:
> > 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
> 
> This can be ignored.  dnf will resolve it in the end.
> 
> > 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
> 
> This must be something you installed yourself.  It's not from Fedora.
> 
> > dnf remove perl-PDL-LAPACK
> > No match for argument: perl-PDL-LAPACK
> 
> You can either try adding "--allowerasing" to the system-upgrade command 
> or try:
> dnf remove perl-PDL-LAPACK*
> Maybe the version number is part of the name.
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Patrick Dupre]

Every time that I upgrade my system I have to do remove
all my own packages (40).

Would dnf module reset \*
do the job?

This is really annoying.



===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===


> Sent: Monday, June 01, 2020 at 11:08 PM
> From: "Michael Young" 
> To: "Community support for Fedora users" 
> Subject: Re: upgrade 30 to 32
>
> On Mon, 1 Jun 2020, Patrick Dupre wrote:
> 
> > 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
> 
> This can be solved by
> dnf module reset \*
> 
> > 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
> 
> It looks like there is no  perl-PDL-LAPACK package in Fedora 32, so you 
> will probably have to delete that package for the update to work.
> 
>   Michael Young
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: windows10 disk not showing up

[George N. White III]

On Mon, 1 Jun 2020 at 12:58, Neal Becker  wrote:

> Thanks for all the suggestions.  Just to review, the issue was the drive
> didn't even appear in lsblk, so nothing can be done to fix it.
>

until you find a way to make it visible to linux.The ATA1 you mentioned
is a hint that the BIOS may have lost the settings.   Windows repair may
have reconfigured the settings after detecting a problem, in which case the
drive should probably be replaced.   Best case is that the BIOS settings
(which are maintained in CMOS by a replaceable battery) were lost due to
failure of the battery (there are lots of youtube videos for Lenovo CMOS
battery replacement).


> It is possible it was partially failing, it seems after multiple windows
> reboots and repairs it is working again, although
> at least one app had to be reinstalled.  I only use linux myself, so I
> know nothing about windows or how to diagnose it.
> So my real question was not how to fix the drive, but why it doesn't even
> show up on linux.
> Thanks
> Neal
>

Drives rarely "partially fail".   They work until they fall off a cliff, so
yours may be falling into the abyss and the
end result won't be pretty.

Some systems have multiple drive support modes, with names like IDE and
AHCI.   Both Windows and linux don't deal well with changes to BIOS.   One
post mentioned raid.
https://askubuntu.com/questions/696413/ubuntu-installer-cant-find-any-disk-on-dell-xps-13-9350
gives
another example.
https://hetmanrecovery.com/recovery_news/how-to-enable-ahci-mode-for-sata-in-the-bios-without-reinstalling-windows.htm
has
enough detail that a linux user should be able to survive a a bit of
windows exposure.

It is tricky (and tedious) to change the BIOS setting without causing
problems for Windows, so your best bet would be to run drive diagnostics (
I use smartmontools, but
https://www.windowscentral.com/how-check-if-hard-drive-failing-smart-windows-10
has
other options) in Windows to decide if the drive is viable.

Computer manufacture these days is quite reproducible, so given model can
suffer from some commonly encountered failure mode that you can find on
Google.




> On Sat, May 30, 2020 at 6:26 PM George N. White III 
> wrote:
>
>> On Sat, 30 May 2020 at 10:37, Neal Becker  wrote:
>>
>>> 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've seen this with older version of Windows.  The "repair" may have
>> repaired the "original" Windows boot configuration, but the
>> need for the repair is most likely due to a failing drive.   Using
>> the USB live stick you should be able to install smartmontools to check the
>> drive.
>>
>>
>>> 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?
>>>
>>
>> Windows may have messed with "BIOS" settings in an attempt to recover
>> from a problem.
>>
>> How old is the drive?  SSD bits have a limited lifetime.   Some workloads
>> (video production) that fill, empty, and refill the drive  very hard on
>> SSD's. Wear leveling strategies try to make the wear even across all the
>> bits, and there are spares when a bit goes bad, but eventually the spares
>> are used up and you lose data in some high-wear area.  You should use
>> ddrescue to image the drive and attempt repairs on the image rather than
>> tying to do repairs on a failing drive.
>>
>> --
>> George N. White III
>>
>> ___
>> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>>
>
>
> --
> *Those who don't understand recursion are doomed to repeat it*
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>


-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of

Re: upgrade 30 to 32

[Samuel Sieb]

On 6/1/20 2:15 PM, Patrick Dupre wrote:

Every time that I upgrade my system I have to do remove
all my own packages (40).


If they are compiled against versions of libraries that are getting 
replaced, then yes.  You could setup a vm to compile the libraries on 
the new release and include those in the update.



Would dnf module reset \*
do the job?

This is really annoying.


It's also unnecessary.  dnf will automatically do that for this release.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: windows10 disk not showing up

[Joe Zeff]

On 06/01/2020 03:21 PM, George N. White III wrote:
Best case is that the BIOS settings (which are maintained in CMOS by a 
replaceable battery) were lost due to failure of the battery (there are 
lots of youtube videos for Lenovo CMOS battery replacement).


If the CMOS battery is going bad, there will be a lot more problems than 
just losing the settings of one drive!  If none of the other settings 
are giving trouble, it's not the battery.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Patrick Dupre]

Hello,

What I would like is to have an automatic removing of my own packages
telling me which packages have been removed.

Then I will rebuild my packages.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===


> Sent: Monday, June 01, 2020 at 11:37 PM
> From: "Samuel Sieb" 
> To: users@lists.fedoraproject.org
> Subject: Re: upgrade 30 to 32
>
> On 6/1/20 2:15 PM, Patrick Dupre wrote:
> > Every time that I upgrade my system I have to do remove
> > all my own packages (40).
> 
> If they are compiled against versions of libraries that are getting 
> replaced, then yes.  You could setup a vm to compile the libraries on 
> the new release and include those in the update.
> 
> > Would dnf module reset \*
> > do the job?
> > 
> > This is really annoying.
> 
> It's also unnecessary.  dnf will automatically do that for this release.
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: F32 Upgrade From F31 Produces Never Seen Before Error Message in Gnome on Xorg and Possibly also KDE.

[Stephen Morris]

On 29/5/20 7:38 pm, Stephen Morris wrote:

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?
Since adding modelines statements into the xorg configuration file for 
all resolutions supported by the monitor/driver this message has stopped 
being displayed. Why is this new with F32 and why does adding the extra 
modelines make any difference?


regards,
Steve



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
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fe

Re: Systemd-boot for MS Surface GO?

[Richard Shaw]

On Mon, Jun 1, 2020 at 3:47 PM Samuel Sieb  wrote:

> On 6/1/20 12:13 PM, Richard Shaw wrote:
> > So I want to dual boot Windows 10 and Fedora on my MS Surface GO but the
> > funky Microsoft UEFI REALLY doesn't like grub.
>
> In what way?  The UEFI boot shouldn't care what you're booting.  It just
> takes the signed boot binary and runs it.
>

Well standard UEFI doesn't care, but a little googling will show that it's
apparently non-standard. If I boot a Fedora Live USB I can see the entry
using efibootmgr but IF you can get the EFI menu to show, it does not list
Fedora, the only options are Windows Boot Manager or Setup. However, others
have reported success using reFIND or systemd-boot, both of which that the
caveat that the kernel and initrd are on the EFI partition.

Thanks,
Richard
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Stephen Morris]

On 2/6/20 3:44 am, stan via users wrote:

On Mon, 1 Jun 2020 15:23:26 +0200
"Patrick Dupre"  wrote:


Thanks,

Actually, I am lost.
I am upgrading one of the systems on a multi-disks system.
1) I realized that one system is not efi, while the other ones are.
2) After I upgraded this system. I can boot it, but it is weird.
a) There was no update of the grub menu (I boot fc32, while the
invitation is still fc30)
b) grub2-mkconfig has not been run
c) grub2-mkconfig (manually) did not recognized by the booted system
except through set root='hd2,msdos3', but no menuentry for this
system.

I've exhausted my knowledge.  I'll make some suggestions, but no
guarantees.

Check /etc/default/grub on the F32 system, and make sure that all the
entries are correct for the F32 system.  It needs to have
GRUB_ENABLE_BLSCFG=true
somewhere in there so that boot loader snippets will work.
GRUB_ENABLE_BLSCFG=true is in /etc/default/grub by default to use the 
new BLS boot loader standard, which as I understand it if this is active 
then grub menus are not used, hence /boot/efi/EFI/fedora/grub.cfg would 
never be updated on new kernel installs, as again as I understand it BLS 
writes the boot loader rather than it being written by grub. I don't 
like the menu display created by BLS as it is the same as the menus 
created by grubby, which I also hated. Consequently I have 
GRUB_ENABLE_BLSCFG=false in /etc/default/grub and I manually issue the 
command grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg so that I get 
the boot menu structure that I want.


regards,
Steve


Look in /boot/loader/entries/ on the F32 system, and make sure that
there is an entry for each of the F32 kernels that you have installed.

Go into /boot/efi/EFI/fedora/ and run
grub2-mkconfig -o grub.cfg

A reboot should now show F32 as a viable boot option, and as the
default.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Stephen Morris]

On 2/6/20 12:10 am, Jonathan Billings wrote:

On Mon, Jun 01, 2020 at 11:20:31AM +0200, Patrick Dupre wrote:

with the -v option, I have
BootCurrent: 
Timeout: 1 seconds
BootOrder: ,0002,0001
Boot* fedora
HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
[...]
However, I do not understand how does this work with multi disks.
We have
/boot/efi/EFI/fedora/grubx64.efi
on each disk ?
Which does not seem to be the case.

If you see in the Fedora entry, it has:
HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800\
,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
I am confused by this process as well. If I issue the command efibootmgr 
-v I get the following output, and, I don't understand how that 
information relates to the segmented disk image that is being used when 
Fedora is run from a virtualbox vm running under windows, and in 
particular when I am booting Fedora via grub.


efibootmgr -v
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,,0001,0003,0004
Boot* UiApp 
FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI VBOX CD-ROM VB0-01f003f6 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(0,0,0)N.YMR,Y.
Boot0003* UEFI VBOX HARDDISK VB86498f1a-4c6a0da4 
PciRoot(0x0)/Pci(0xd,0x0)/Sata(0,65535,0)N.YMR,Y.
Boot0004* EFI Internal Shell 
FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0005* Fedora 
HD(1,GPT,5a166b43-c099-429b-9587-4cc29389e1cf,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)


regards,
Steve


That means to look for a volume with the 3rd GPT partition, with the
UUID of a5c3bc11-e83b-48d0-be96-783af37228f1 (and some other data).
On that disk, look for the /EFI/FEDORA/GRUBX64.EFI executable
(remember, this is a DOS filesystem so it's case-insensitive).

Run 'blkid' on a running system, and you'll see that the PARTUUID of
the EFI volume matches the UUID in the above EFI entry.

You can have an EFI volume on multiple disks.  EFI also supports
things like network boot, which has a different syntax EFI entry.  The
efibootmgr command does a lot of the hard work of figuring that out
for you, so you don't need to manually enter that information.


___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: upgrade 30 to 32

[Samuel Sieb]

On 6/1/20 3:25 PM, Patrick Dupre wrote:

What I would like is to have an automatic removing of my own packages
telling me which packages have been removed.


Add "--allowerasing" to the dnf command and check the list of removed 
packages.  It will also be in the dnf history.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Samuel Sieb]

On 6/1/20 4:05 PM, Stephen Morris wrote:

On 2/6/20 3:44 am, stan via users wrote:

Check /etc/default/grub on the F32 system, and make sure that all the
entries are correct for the F32 system.  It needs to have
GRUB_ENABLE_BLSCFG=true
somewhere in there so that boot loader snippets will work.


GRUB_ENABLE_BLSCFG=true is in /etc/default/grub by default to use the 
new BLS boot loader standard, which as I understand it if this is active 
then grub menus are not used, hence /boot/efi/EFI/fedora/grub.cfg would 
never be updated on new kernel installs, as again as I understand it BLS 
writes the boot loader rather than it being written by grub. I don't 
like the menu display created by BLS as it is the same as the menus 
created by grubby, which I also hated. Consequently I have 
GRUB_ENABLE_BLSCFG=false in /etc/default/grub and I manually issue the 
command grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg so that I get 
the boot menu structure that I want.


That's not quite correct.  The base grub.cfg file isn't updated because 
it is configured to load the boot loader snippets and use those.  The 
grub menu shows the entries from those files.  A kernel update only adds 
and removes snippet files.  I don't know what template is used to 
generate the titles in those files or maybe it's hardcoded somewhere.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: boot/grub

[Samuel Sieb]

On 6/1/20 4:10 PM, Stephen Morris wrote:
I am confused by this process as well. If I issue the command efibootmgr 
-v I get the following output, and, I don't understand how that 
information relates to the segmented disk image that is being used when 
Fedora is run from a virtualbox vm running under windows, and in 
particular when I am booting Fedora via grub.


What part of it do you not understand?


efibootmgr -v
BootCurrent: 0005


This is the entry you're currently running.


Timeout: 0 seconds
BootOrder: 0005,,0001,0003,0004


This is the order that the entries will be tried in.

Boot0005* Fedora 
HD(1,GPT,5a166b43-c099-429b-9587-4cc29389e1cf,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi) 


I don't know the all the specific details, but this entry describes how 
to load the grub bootloader to start Fedora:
"HD(1,GPT,5a166b43-c099-429b-9587-4cc29389e1cf,0x800,0x12c000)" 
identifies the hard drive and EFI partition to use.
"File(\EFI\fedora\shimx64.efi)" gives the path to the executable file on 
that partition to load and run.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: windows10 disk not showing up

[Tim via users]

On Mon, 2020-06-01 at 15:55 -0600, Joe Zeff wrote:
> If the CMOS battery is going bad, there will be a lot more problems
> than just losing the settings of one drive!  If none of the other
> settings are giving trouble, it's not the battery.

I do wonder about that.  How many BIOS settings are ignored post-boot? 
And how many things are left at default by users who never customise
their system?
 
-- 
 
uname -rsvp
Linux 3.10.0-1127.8.2.el7.x86_64 #1 SMP Tue May 12 16:57:42 UTC 2020 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

gnome-system-monitor with IO?

[ToddAndMargo via users]

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
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org