Re: port forwarding and RDP or ssh

2024-03-12 Thread Ron Flory via users

On 3/11/24 12:45, Alex wrote:
I now have his PC with me on my local network, and commands executed 
through ssh -X still display on his screen instead of mine.


 From his gnome-terminal on my PC:
[gary@fedora ~]$ echo $DISPLAY
localhost:10.0

How do I set the display for commands executed remotely to appear on 
my screen?


 This is a feedback report only-

 For me, all this seems to work fine when connecting between multiple 
FC39 machines (as I would expect), but I can duplicate the reported 
issue with an old ubuntu machine (22.04.2 LTS) I keep in the dungeon for 
cross-distro compatibility testing of things like this.


 X11 fwding seems ok when ssh'ing from the ubunto machine into FC39, 
but does not work when ssh'ing from FC39 into ubuntu.  The graphical 
output and mouse control (incorrectly) remains on the remote ubunto 
machine, and the originating FC39 session sees nothing graphical.


 This seems to suggest FC39 ssh -X handling might have introduced a 
backward incompatibly.  Somebody might try "ssh -X" from FC39 into 
systems with earlier version(s) of Fedora to see if the same thing happens.


--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


dmesg suddenly fails when run as normal user on FC39

2024-03-13 Thread Ron Flory via users

Hi-

 does not happen on FC38, or any prior RedHat/Fedora version since 
forever.


   dmesg
   dmesg: read kernel buffer failed: Operation not permitted

 Userspace scripts (such as used to read pics from cameras & sdcards) 
and many progs often use dmesg to detect or identify things like startup 
probe info, USB devs, partition numbers etc.


 I worked around this by setting the suid bit of `which dmesg`, but it 
would be rude to force everybody to manually do this as part of 
post-install cleanup.


 Hopefully an unintended side-effect and not a new "feature" that 
wasn't thought through completely.  A web-search suggests debian/ubuntu 
may have been doing this for awhile- but we really don't need to be just 
like them...    ;)
--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: dmesg suddenly fails when run as normal user on FC39

2024-03-13 Thread Ron Flory via users

On 3/13/2024 6:54 PM, Sam Varshavchik wrote:

Ron Flory via users writes:


»Hi-

 does not happen on FC38, or any prior RedHat/Fedora version since 
forever.


Sounds like this has landed:

https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/U2XA6J5BGPKMS54YM7DTOI4QHUXQTARI 



 Thanks for the link.

 I can see both sides of it.  At the same time, I can neither 
fully condemn, nor enthusiastically support this.  Subtle side-effects 
with existing practices and applications will haunt us for a long time.


--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [EXTERNAL] Re: Is there an officially Fedora supported replacement for,>,> the old rc.local? - still an issue

2022-07-20 Thread Ron Flory via users

On 7/20/2022 10:16 AM, Joe Zeff wrote:
> On 7/20/22 07:45, Patrick O'Callaghan wrote:
> > We couldn't even run vi at the time on our PDP-11/45 with 6th Edition
> > UNIX. IIRC it was too big for the address space. I wrote my PhD thesis
> > in Nroff using George Coulouris' em ('editor for mortals'), the
> > precursor to ex, which eventually became vi. It had a single-line
> > display but unlike ed you could see what you were doing.
>
> And because you had to do that decades ago new Linux users today should
> be using vi instead of all the more user friendly editors available for
> use in a terminal?

 Careful there-  even today, a very large number of new Linux devices 
don't run a GUI at all, so a text-based editor (and knowing how to drive 
it) is a necessity.


 Also, I think you mean 'shell' instead of 'terminal'-   a 'terminal' 
is an external piece of hardware that terminates a serial line, like an 
ADM-3A or TVI-912C, etc.  We generally haven't used terminals since the 
1980's.


;)

___
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: How do I do a group reinstall of Xfce?

2023-04-09 Thread Ron Flory via users

Hopefully reactivating an old thread whose reply does not work with FC37...

 I have an x86 FC37 XFCE-spin whose GUI setups had a kind of creeping 
death, then went bonkers.


 I'd like to force-reinstall XFCE completely (no desire to save any 
X/XFCE configs-  would like all that re-initialized, like a XFCE-spin 
fresh-install (at least for the X-stuff only).


 I tried some online suggestions, but XFCE is still not right, the 
background image does not show (only black screen), the 'pager' does not 
work (only 1 page is shown when there it says there should be 8 
workspaces).  also, desktop and progs are not remembered when i 
leave/restart the session.


 Attempting to reinstall from thread and online-article suggestions;  
one problem is that running the suggested:


    dnf groupremove 'Xfce Desktop'

 Results in a dnf error about it would result in removing dnf and 
sudo.  using the suggested '--skip-broken' does not work.



 Note: I start FC37 in text-mode (lightdm), and only run X when I need 
it by running 'startx'.


___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: How do I do a group reinstall of Xfce?

2023-04-09 Thread Ron Flory via users
 yes, also tried startxfce4 (which I imagine startx also indirectly 
calls).  both act the same, and same xfc* processes are running.


 No good.  XFCE display is just 'not right', and most gui apps refuse 
to allow resize, etc.


 Interestingly, the xscreensaver (with password prompt) seems to look 
just fine.


 Somehow, i expect the XFCE/FC37-specific configs just aren't being 
restored.  I also deleted all ~/.configs/xfce4* files, etc before XFCE 
removal and reinstall.  Perhaps this extends into the base X11 stuff as 
well?


  (I wonder why/when dnf removed their "-force" switch (for install) ?)

ron



On 4/9/2023 4:11 PM, Joe Zeff wrote:

On 04/09/2023 02:34 PM, Ron Flory via users wrote:


  Note: I start FC37 in text-mode (lightdm), and only run X when I 
need it by running 'startx'.


First, you should really be using startxfce4, but if startx works, 
it's not important.  Second, are you doing this in text mode, without 
ever having started Xfce?  If not, try it that way as it might make a 
difference.

___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: How do I do a group reinstall of Xfce?

2023-04-09 Thread Ron Flory via users
 that would be a bad thing, but you misunderstand-   force 'install' 
(ala 'rpm' command), even if already installed...  I see now that dnf 
supports 'reinstall'.


ron



On 4/9/2023 6:20 PM, Samuel Sieb wrote:

On 4/9/23 14:51, Ron Flory via users wrote:

   (I wonder why/when dnf removed their "-force" switch (for install) ?)


dnf never had a "force" option, just rpm.  Why do you need it? What 
would it do?  Do you really want it to remove itself?

___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Missing "standard" headers in FC37 arm (aarch64) C/C++ cross-compiler RPMs ??

2023-06-01 Thread ron flory via users
Hi- am hopefully missing something dumb/obvious here---

 Am trying to cross-compile for raspberry-pi, but some basic headers appear to 
be missing, or not redirecting to 'generics'. 

-
Install the cross-compiler(s):
dnf install gcc-aarch64-linux-gnu  gcc-c++-aarch64-linux-gnu

-
Compile hello_world sample:
aarch64-linux-gnu-gcc  hello_world.cpp -o hello_world

Results:
hello_world.c:1:10: fatal error: stdio.h: No such file or directory
1 | #include 
  |  ^
compilation terminated.

-
Hello_world sample consists of:

#include 
#include 

int main(int argc, char *argv[])
{
printf("Hello World\n");
return(0);
}
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Missing "standard" headers in FC37 arm (aarch64) C/C++ cross-compiler RPMs ??

2023-06-04 Thread Ron Flory via users

On 6/3/23 08:55, stan via users wrote:
On Thu, 01 Jun 2023 20:29:54 - ron flory via users 
 wrote:
Results: hello_world.c:1:10: fatal error: stdio.h: No such file or 
directory 1 | #include  | ^ compilation terminated. 
- Hello_world sample consists of: #include  #include 
 int main(int argc, char *argv[]) { printf("Hello 
World\n"); return(0); } 
I find at this link 
https://stackoverflow.com/questions/19580758/gcc-fatal-error-stdio-h-no-such-file-or-directorythis 
comment, You can see where gcc is looking for header files by doing 
echo "#include " | gcc -v -x c - and examining the search 
paths. – Christian Ternus Oct 25, 2013 at 3:53 It is old, and when I 
tried it, it didn't work. But it might give you an idea for things to 
try. This also seems relevant, "it seems implausible that there would 
be a release which generated errors upon importing stdio" Is the file 
present in /usr/include? If it is, you could use the -I option to 
point there, -I /usr/include, and see if it works. If it does, that 
indicates that it is a problem in the configuration of gcc; it isn't 
looking in the system include directory. 


 it was sloppy of me to assume everybody understood the host is x86-64.

 There are only 3 relevant compiler/binutils RPMs for aarch64 in FC37: 
(excluding other langs/libs)


dnf list all | grep aarch | grep -v "^rust\|^qemu\|^edk2\|^ipxe"
  gcc-aarch64-linux-gnu
  gcc-c++-aarch64-linux-gnu
  binutils-aarch64-linux-gnu

 ...the binutils is automatically installed as a dependency (similar 
deal for the "gcc-arm-linux" sibling).



The (very few) related headers are installed in 
/usr/lib/gcc/aarch64-linux-gnu/12/include/ as confirmed by 1)
  dnf repoquery -l gcc-aarch64-linux-gnu gcc-c++-aarch64-linux-gnu | 
grep /st | grep "\.h$" | sort


and 2) which are not present when the cross-compiler is removed, but are 
present when the cross-compiler is re-installed.


  Having built many cross-compilers over the years, a look at this 
header include directory is very, very sparse, missing the majority of 
our usual .h friends.


  It --may-- be the RPMs were just built 'for successful compilation' 
without running a minimal test suite to confirm the output artifacts are 
functional-  ...maybe.   ( at least a 'hello-world' should be 
cross-compiled to confirm output-artifacts are produced, and for the 
correct target arch )


 If another noarch or arm header-only RPM happens to contain the 
missing headers (which I have not stumbled upon yet), it would be 
helpful for this to be marked a co-dependency so dnf can install it too.


- - -

 As a side note, for reference only, please no flames intended; the 
corresponding two aarch64 gcc/c++ packages for the popular debian-based 
distro beginning with "U" (which shall not be spoken here) does compile 
and link C/C++ programs correctly, which is why I suspect it could be an 
RPM packaging issue.


ron___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: question: does "diff" use short cuts?

2023-07-07 Thread Ron Flory via users

On 7/7/2023 12:42 PM, home user wrote:
When I try to verify a back-up, I use "diff -r".  The directory trees 
being compared contain about 870 files (mostly binary, like PNG, JPG, 
and so on), and take up about 707 megabytes.  The trees being compared 
are on the hard drive and on a USB-3 stick.  When I run the "diff -r" 
command, it seems to finish too quickly - it seems like less than a 
half of a second.  I saw similar results a few weeks ago comparing 
about 30 gigabyte trees on the hard drive vs. on a USB-3.1 stick; the 
results were practically instantaneous.  Is diff actually checking 
every bit (or byte), or is it using some "short cut"?


 Was this immediately after your backup/copy completed?  You may be 
comparing against the in-memory disk caches.
 You may (simply) flush the in-memory disk caches to force reads from 
the external disk with (run as root or sudo):


  sync ; echo 3 > /proc/sys/vm/drop_caches

then try your diff again.

___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Help needed: disabling system wide the Caps lock key in GNOME/Xwayland

2023-08-02 Thread Ron Flory via users

On 8/2/2023 10:42 AM, Thomas wrote:

Hello,

I had that issue recently, the way I sorted it was with gsettings/dconf:

gsettings set org.gnome.desktop.input-sources xkb-options "['ctrl:nocaps']"

I suspect this is what gnome-tweaks does. Actually as far as I know, Wayland 
still sources xkb files, it's not very much documented but I recall having 
found a few places suggesting that (I use stock F38 with Gnome and Wayland).

And thus see: man xkeyboard-config for a list of options which can be set, 
which is a bit wider than what gnome-tweaks propose.

On Wed, 2 Aug 2023, at 15:56, murph nj wrote:

Gnome tweaks has a simple solution to this.

Install Tweaks through "Software" or
dnf install gnome-tweaks

Run Tweaks and go to the "Keyboard and Mouse" section.
The 4th option down is an "Additional Layout options" button.
There are many things you can remap the CapsLock key to, like Esc, ctrl, or
my preference a Super key, since I usually use an IBM model M keyboard
which does not have one.

No need to revert back to X11, or any kind of hardware solution.



On Tue, Aug 1, 2023 at 3:31 PM Joachim Backes 
wrote:


Hi gys,
I'm running F38 with *Gnome/X-Wayland*, and in my environment I do not need 
(hate it) the *Caps Lock* key.Question: How to realize the disabling system 
wide, and how to get it working again?

Regards

Joachim Backes

--

Fedora release 38 (Thirty Eight)
6.4.7-200.fc38.x86_64

Joachim Backes  
https://www-user.rhrk.uni-kl.de/~backes/




 (hmmm, much top-posting up there)

 Since nobody else has mentioned this (apologies if this does not 
address your needs, and you *really* hate the presence of the Caps-Lock 
key), but most motherboard BIOS's have a setting for startup "numlock 
state".  I always set mine to "Disabled" and it keeps the unwanted Caps 
keys away unless/until I explicitly (temporarily) enable them by hitting 
the Caps-Lock key.


ron

___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Problem with SD card

2023-08-07 Thread Ron Flory via users

On 8/7/2023 10:18 AM, Geoffrey Leach wrote:

I have a 1TB SanDisk XC SD card, which has developed a reluctance to
create files.

UUID=0fd984c4-cf88-408a-8ba5-15b64500bd5c  /Media/SDXC   ext4
noauto,rw,user 0 0

% sudo mount /Media/SDXC
% touch /Media/SDXC/foo
% ls /Media/SDXC/foo
/Media/SDXC/foo
% sudo umount /Media/SDXC
% sudo mount /Media/SDXC
% ls /Media/SDXC/foo
/bin/ls: cannot access '/Media/SDXC/foo': No such file or directory

I used root to mount, just to be sure. User mount has the same problem.
gparted reported a problem with the superblock which was resolved by
re-formatting and re-creating the partition table. The card has just
one partition.

Suggestions for further diagnosis would be appreciated.


 Are you able to read existing files off the SD flash?

 Did the "touch /Media/SDXC/foo" operation above fail due to Read-Only 
filesystem?


 I do have a lot of experience with managed/unmanaged flash filesystems 
under Linux, but don't assume the following applies to your particular 
case.  Higher-quality "Managed Flash" devices (like SD/uSD/MMC/eMMC) 
self-monitor their own "health status" over time. When the flash array 
begins to develop a sufficient number of bad sectors, many will mark 
themselves Read-Only to prevent loss of future data (but allow you the 
opportunity to off-load existing files before total failure occurs).  
Cheap-o units aren't as well-behaved- they just fail to retain new 
files.  You might see some flash/disk related messages in the syslog 
during the "sync".


 Does this problem occur with any other flash devices you have?

 If this problem seems to affect only that single flash device, I would 
suggest permanently retiring it and moving to an alternate. experience here-   make sure you clearly mark it "BAD!!" and throw it 
away, otherwise it WILL unexpectedly reappear in the future and provide 
the same entertaining learning-experience, again and again...   ;)  >


___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: thunderbird problem

2025-02-13 Thread Ron Flory via users

On 2/13/2025 1:49 AM, fed...@eyal.emu.id.au wrote:

It is me, the OP. To simplify the story.
- start TB. OK
- fetch POP3 mail. A few times in a few hours. All OK.
- do a "Compact Folders".
messages say it completed. The blue activity line remains wavy(*).
TB is idle yet it shows 60-70% CPU in "top".
If I minimize TB then it stops using CPU.
If I select a folder (but do nothing) the %CPU goes up to around 
120%.

Turning off the status bar also stops using CPU!

This last item probably points at the source of the problem!

TIA

(*) the item at the right side of the bottom status line shows a 
rolling blue/white pattern, as if it is active.




 Yeah-  similar issues seem to be a persistent theme reported for TBird 
over several years now.  Search the TBird bugzilla and you'll see it 
popping up again and again.  I reported pretty much the same thing 2..3 
years back- my guess was a tight display-update loop that continuously 
called the display-manager (X11 at that time) for an unchanged status.


ron

--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: e2fsck malfunction?

2025-03-14 Thread Ron Flory via users

On 3/14/2025 6:34 AM, Tim via users wrote:

On Thu, 2025-03-13 at 22:05 -0700, Dave Close wrote:

"e2fsck -c" said it didn't find any bad blocks. If it didn't find any,
why would it modify the card at all? "e2fsck -y" (by itself) did not
report any problem.

Perhaps it didn't.  If the card was failing, a read operation could be
enough to trigger another failure.  It wouldn't matter what was doing
the read.


 I have a lot of experience with bad/flaky USB/SDCards- often they seem 
just fine as the onboard controller conceals signs of creeping-death, 
until they suddenly take a nose-dive.


 I'm not sure about your case, but each time I run "e2fsck -v -c -y 
/dev/sde1" (note -v Verbose switch), the summary always reports "* 
FILE SYSTEM WAS MODIFIED *".  So the filesystem IS being modified, 
but the media still mounts successfully in my case.


 Do you see the same issue if you try other SDCards or USB 
FlashDrives?  Any difference if you format the media as plain ext2 vs 
ext4 FS?  Any difference if you use "e2fsck -cc" (Write+Read/Verify) 
test?  As asked earlier, does running f3probe, f3write, f3read produce 
anything interesting?



-- 
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


How to select text-based "system-upgrade reboot" progress indication?

2025-04-22 Thread Ron Flory via users

Hi-

 Am just now getting around to upgrading a secondary HP laptop from 
FC39 -> FC40.


 The post-reboot upgrade process for FC40 appears to display a sterile 
windoze-style GUI progress-indication now.  It initially sat there at 0% 
for a long, LONG time, which scared the [bleep] out of me.


 I don't launch my Linux systems into GUI-mode by default, preferring 
text-mode until/if I decide to manually 'startx' - so the new silent 
upgrade process (with no indication of progress) probably looks slick to 
new users, but is a loss-of-functionality from a developer point of view.


 Is there a way to request the upgrade process revert to the 
(comforting) noisy/verbose text-based mode?


 Thanks-

ron


--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: How to select text-based "system-upgrade reboot" progress indication?

2025-04-22 Thread Ron Flory via users

On 4/22/2025 3:40 PM, Samuel Sieb wrote:

On 4/22/25 2:26 PM, Ron Flory via users wrote:

Hi-

  Am just now getting around to upgrading a secondary HP laptop from 
FC39 -> FC40.


  The post-reboot upgrade process for FC40 appears to display a 
sterile windoze-style GUI progress-indication now.  It initially sat 
there at 0% for a long, LONG time, which scared the [bleep] out of me.


  I don't launch my Linux systems into GUI-mode by default, 
preferring text-mode until/if I decide to manually 'startx' - so the 
new silent upgrade process (with no indication of progress) probably 
looks slick to new users, but is a loss-of-functionality from a 
developer point of view.


  Is there a way to request the upgrade process revert to the 
(comforting) noisy/verbose text-based mode?


Press the ESC key.



 ;)  Hilarious...   I was afraid to do anything that rude for fear of 
leaving things in an indeterminate state.


Thanks again.


--
___
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue