Re: The best way to still use Fedora + Xorg ... even after version 40

[Ranjan Maitra via users]

On Mon Apr22'24 09:05:51PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Mon, 22 Apr 2024 21:05:51 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: The best way to still use Fedora + Xorg + Gnome ... even after
>  version 40
>
> On 4/22/24 20:57, Ranjan Maitra via users wrote:
> > Btw, does all this discussion about F40 dropping support for X11 mean that 
> > openbox (the window manager, also behind LXDE) also stop working with F40?
>
> F40 isn't dropping support for X11.  The big thing about F40 is that the
> Fedora KDE Plasma 6 is dropping support for X11.  But there are some people
> that are going to maintain the X11 support separately so you can still use
> it if you want.
>
> There are still some window managers that don't support Wayland (yet) and
> those will continue to work with X11.
>
> I don't know why Gnome is in the subject.  I haven't seen any mention of
> support being dropped so I believe there's still X11 support, although I
> haven't used it (X11) for a long time, other than XWayland.

My apologies for my confusion, and thank you for the clarification. I really 
like using my WM (openbox) and am glad to know that I can still continue to use 
that. (However, I think that openbox may not be ported to Wayland, if I 
understood correctly what was discussed some time ago in that mailing list.)

Best wishes,
Ranjan
--
___
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: The best way to still use Fedora + Xorg + Gnome ... even after version 40

[Ranjan Maitra via users]

On Mon Apr22'24 07:36:16AM, Sam Varshavchik wrote:
> From: Sam Varshavchik 
> Date: Mon, 22 Apr 2024 07:36:16 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: The best way to still use Fedora + Xorg + Gnome ... even after
>  version 40
>
> Wolfgang Pfeiffer via users writes:
>
> > On Mon, Apr 22, 2024 at 12:01:58PM +0200, Wolfgang Pfeiffer via users wrote:
> > > On Sun, Apr 21, 2024 at 10:00:02AM -0400, Sam Varshavchik wrote:
> > > > Wolfgang Pfeiffer via users writes:
> > > >
> > > > > I can't buy these repeatedly and ad nauseam asserted ideas of x11/xorg
> > > > > vulnerabilities as an excuse for dumping the Xorg/X11 system as a
> > > > > whole.
> > > >
> > > > I don't see much value is discussing the validity of those excuses. It
> > > > is what it is. They don't want to work on X any more. [ ... ]
> > >
> > > Xorg is still being maintained and patched, it seems:
> >
> > Forgot to mention: it's not exactly clear to me what you mean to say
> > by /"They" don't want to work on X any more/
>
> It has been stated, repeatedly, that the X.org maintainers have no desire to
> do any further development on X11, and they are only working on Wayland.
>
>
> > But anyways: Hoping the links are helpful.
> >
> > >
> > > https://lists.x.org/archives/xorg-commit/
> > > https://lists.x.org/archives/xorg/
>
> It's certainly possible that an occasional patch/minor fix gets committed.
> But it's been reportedly, repeatedly, that "they" don't want to work on X11
> any more. If you go back to the top of this thread you will find that stated
> by more than one person, who's in position to know.

Btw, does all this discussion about F40 dropping support for X11 mean that 
openbox (the window manager, also behind LXDE) also stop working with F40?

Many thanks,
Ranjan
--
___
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: finding missing font file (eurm10.map)

[Ranjan Maitra via users]

On Thu Feb08'24 09:47:29PM, Jerry James wrote:
> From: Jerry James 
>
> On Thu, Feb 8, 2024 at 9:43 PM Ranjan Maitra via users
>  wrote:
> > Thanks, this did not do anything different. Are you sure that this font is 
> > in this package?
>
> $ rpm -ql texlive-amsfonts
> ...
> /usr/share/texlive/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
> ...
> /usr/share/texlive/texmf-dist/fonts/tfm/public/amsfonts/euler/eurm10.tfm
> ...
> /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfb
> /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfm
> ...
>
> Maybe the "at 600" part is significant?  We have reached the limits of
> my knowledge, I'm afraid.  Hopefully somebody else will know what is
> going on.

Yes, I hope so too.

Thank you again!

Best wishes,
Ranjan
--
___
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: finding missing font file (eurm10.map)

[Ranjan Maitra via users]

On Thu Feb08'24 05:56:26PM, Jerry James wrote:
> From: Jerry James 
> Date: Thu, 8 Feb 2024 17:56:26 -0700
> To: Community support for Fedora users 
> CC: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Re: finding missing font file (eurm10.map)
>
> On Thu, Feb 8, 2024 at 5:10 PM Ranjan Maitra via users
>  wrote:
> > Thanks, yes, I do have it installed!
> >
> >  $ sudo dnf install texlive-amsfonts
> >  Last metadata expiration check: 1:15:21 ago on Thu 08 Feb 2024 04:52:50 PM 
> > CST.
> >  Package texlive-amsfonts-11:svn61937-69.fc39.noarch is already installed.
> >  Dependencies resolved.
> >  Nothing to do.
> >  Complete!
>
> In that case I suggest reinstalling it so that the texlive triggers fire 
> again.

Thanks, this did not do anything different. Are you sure that this font is in 
this package?

Thanks again for your help!

Best wishes,
Ranjan
--
___
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: finding missing font file (eurm10.map)

[Ranjan Maitra via users]

On Thu Feb08'24 04:52:13PM, Jerry James wrote:
> From: Jerry James 
> On Thu, Feb 8, 2024 at 4:48 PM Ranjan Maitra via users
>  wrote:
> > On a fully updated F39 system, I get the following font error when I run 
> > LaTeX:
> >
> >  kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 
> > eurm10
> >  mktexpk: don't know how to create bitmap font for eurm10.
> >  mktexpk: perhaps eurm10 is missing from the map file.
> >  kpathsea: Appending font creation commands to missfont.log.
> >  (see the transcript file for additional information)
> >  !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 600 not found
> >
> > I looked around and came across a post from 2020 on Arch forums that says 
> > that I potentially need texlive-most, however this is not available on F39.
> >
> > How do I get around the above error?
>
> On my system, that font file is in the texlive-amsfonts package.  Do
> you have that installed already?

Thanks, yes, I do have it installed!

 $ sudo dnf install texlive-amsfonts
 Last metadata expiration check: 1:15:21 ago on Thu 08 Feb 2024 04:52:50 PM CST.
 Package texlive-amsfonts-11:svn61937-69.fc39.noarch is already installed.
 Dependencies resolved.
 Nothing to do.
 Complete!

Best wishes,
Ranjan
--
___
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

finding missing font file (eurm10.map)

[Ranjan Maitra via users]

Hi,

On a fully updated F39 system, I get the following font error when I run LaTeX:

 kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 eurm10
 mktexpk: don't know how to create bitmap font for eurm10.
 mktexpk: perhaps eurm10 is missing from the map file.
 kpathsea: Appending font creation commands to missfont.log.
 (see the transcript file for additional information)
 !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 600 not found

I looked around and came across a post from 2020 on Arch forums that says that 
I potentially need texlive-most, however this is not available on F39.

How do I get around the above error?

Many thanks for your suggestions, and my very best wishes,
Ranjan
--
___
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: Network problems with f39

[Ranjan Maitra via users]

On Wed Dec20'23 02:11:00AM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Wed, 20 Dec 2023 02:11:00 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: Network problems with f39
>
> On 12/20/23 01:47, Ranjan Maitra via users wrote:
> > This may be thoroughly unrelated, but my wife has had this problem on a 
> > Dell for years (largely regularly), and me only intermittently over the 
> > past few months (F38 or F39). I think it may be dependent on the service 
> > provider because the same setup has worked without a hitch in some hotel 
> > rooms, not in others (for me).
> >
> > I usually get this working by doing:
> >
> > sudo systemctl restart systemd-resolved.service
> >
> > and things work flawlessly (at least apparently) after that.
> >
> > Again, not sure if this is related.
>
> That is completely unrelated.

OK, thanks! ANy idea what may cause this?

Ranjan
--
___
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: Network problems with f39

[Ranjan Maitra via users]

This may be thoroughly unrelated, but my wife has had this problem on a Dell 
for years (largely regularly), and me only intermittently over the past few 
months (F38 or F39). I think it may be dependent on the service provider 
because the same setup has worked without a hitch in some hotel rooms, not in 
others (for me).

I usually get this working by doing:

sudo systemctl restart systemd-resolved.service

and things work flawlessly (at least apparently) after that.

Again, not sure if this is related.

Best wishes,
Ranjan


On Wed Dec20'23 01:38:01AM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Wed, 20 Dec 2023 01:38:01 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: Network problems with f39
>
> On 12/19/23 21:31, Robert McBroom via users wrote:
> >
> > On 12/19/23 01:53, Samuel Sieb wrote:
> > > This is the problem you need to resolve.
> > > I don't know why.  You'll need to find out why the dbus broker can't
> > > run.  I would have expected more details in the log.
> > > --
> > >
> > I'm not sure what to look for in the journal. Does this section show the
> > problem? Sequence repeats several times
> >
> > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning
> > -- SELinux targeted policy relabel is required.
> > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: ***
> > Relabeling could take a very long time, depending on file
> > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system
> > size and speed of hard drives.
> > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running:
> > /sbin/fixfiles -T 0  restore
> > Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up
> > NSS user entry for 'systemd-oom'...
> > Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned
> > no entry for 'systemd-oom'
> > Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid
> > user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9:
> > user="systemd-oom"
> > Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started
> > dbus-broker.service - D-Bus System Message Bus.
> > Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0
> > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> > msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd"
> > hostname=? addr=? terminal=? res=success'
> > Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15
> > callbacks suppressed
> > Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130
> > audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295
> > subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd"
> > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR
> > launcher_run_child @ ../src/launch/launcher.c +347: Permission denied
> > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR
> > service_add @ ../src/launch/service.c +1011: Transport endpoint is not
> > connected
>
> What have you done to your system?
> For some reason it's doing a relabel.  It should be done, you can try
> rebooting and see if things go better.  But things look quite broken.
> --
> ___
> 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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Sun Dec03'23 01:51:24PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Sun, 3 Dec 2023 13:51:24 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
> On 11/19/23 08:25, Ranjan Maitra via users wrote:
> > I was running the code here: 
> > https://github.com/maitra/Visual-Information-Fidelity---Python3
> >
> > However, the code runs in F38 (python 3.11) without error, but not in F39 
> > (python 3.12) where it
> > ends with a segmentation fault (after doing the calculations).
>
> I just upgraded my system to F39, so I tested this code and it worked fine
> with no crashes.  Did you rebuild the shared library after upgrading?

Wow, that is weird! But good to know. As to your question, yes I did rebuild 
the shared object (library) several times, but that should not matter, right? I 
guess this is local to my F39 machines, but all (three) of them appear to be 
dumping core.

Thanks again, I will try and get to the bottom of it. Perhaps by trying the 
code on a clean F39 installation.

Best wishes,
Ranjan



> --
> ___
> 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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Sun Dec03'23 01:47:46PM, Barry Scott wrote:
> From: Barry Scott 
> Date: Sun, 3 Dec 2023 13:47:46 +
> To: Community support for Fedora users 
> CC: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
>
>
> > On 2 Dec 2023, at 15:24, Ranjan Maitra via users 
> >  wrote:
> >
> > However, the following: 
> > /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
> >  file is where the segfault is, and that is in python3-devel. Perhaps  I 
> > just report it there and see where that gets me.
>
> That the victim not the cause.
>
> Its in here that you need to report the problem
>
> #3  0x7fff9e5e292f in sip_api_free (mem=) at 
> /usr/src/debug/sip-4.19.25-9.fc39.x86_64/siplib/siplib.c:2239
> #4  sipOMFinalise (om=0x7fff9e5ff9a0 ) at 
> /usr/src/debug/sip-4.19.25-9.fc39.x86_64/susr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pylifecycle.c:1977
>
> It's this "sip" that you need to report against.
>
> Not sure what you mean by it was not installed, its in the back trace.

Thanks, I never installed it earlier (and now I installed sip6 -- see other 
subthread), The issue is still the same, though. That is what I meant.


> Barry
>
>

> --
> ___
> 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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Sun Dec03'23 09:38:20AM, Jeffrey Walton wrote:
> From: Jeffrey Walton 
> Date: Sun, 3 Dec 2023 09:38:20 -0500
> To: Community support for Fedora users 
> CC: Ranjan Maitra 
> Reply-To: noloa...@gmail.com, Community support for Fedora users
>  
> Subject: Re: Python code error in F39, but not in F38
>
> On Wed, Nov 22, 2023 at 5:21 PM Ranjan Maitra via users
>  wrote:
> >
> > On Wed Nov22'23 09:49:49PM, Barry Scott wrote:
> > > [...]
> > > > On 22 Nov 2023, at 21:32, Barry Scott  wrote:
> > > >
> > > >> Any suggestions as to what is going wrong here?
> > > >
> > > > At this point you need get more information.
> > > >
> > > > What do the folllowing GDB commands print?
> > > >
> > > > p tstate
> > > > p tstate->interp
> > > > thread allow all bt
> > > Doh...
> > >
> > >   thread apply all bt
> > >
> > > I always type:
> > >   t a a bt
> > >
> > > and typo'ed the expansion.
> >
> > Thanks, here is what comes out:
> >
> >  (gdb)  p tstate->interp
> >
> >  value has been optimized out
> >  (gdb) thread apply all bt
> >
> >  Thread 1 (Thread 0x77ec7740 (LWP 387946) "python"):
> >  #0  0x779e4b5b in _PyInterpreterState_GET () at 
> > /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
> >  #1  get_state () at 
> > /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:866
> >  #2  _PyObject_Free (ctx=, p=0x56d898a0) at 
> > /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:1850
> >  #3  0x7fff9e5e292f in sip_api_free (mem=) at 
> > /usr/src/debug/sip-4.19.25-9.fc39.x86_64/siplib/siplib.c:2239
> >  #4  sipOMFinalise (om=0x7fff9e5ff9a0 ) at 
> > /usr/src/debug/sip-4.19.25-9.fc39.x86_64/susr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pylifecycle.c:1977
>
> sip-4.19 is from 2018. The Python folks will probably tell you to
> update to something newer, like sip-6.7. Also see
> <https://pypi.org/project/sip/#history>.

Thank you for this! I have no idea where sip gets pulled from, because
it was not installed in the system.

So I went ahead and installed sip6 via:

sudo dnf install sip6
 # brings in sip-6.7.12.

I get:

(gdb) run ./test.py statlab.tiff statlab-8-rgb.png 1 5
 Starting program: /usr/bin/python ./test.py statlab.tiff statlab-8-rgb.png 1 5
 Downloading separate debug info for system-supplied DSO at 0x77fc7000
 [Thread debugging using libthread_db enabled]
 Using host libthread_db library "/lib64/libthread_db.so.1".
 [New Thread 0x7fff9c39b6c0 (LWP 6832)]<2-t_��>ý 
v:lua.cmp.utils.feedkeys.call.run(12)
,
 [New Thread 0x7fff9bb9a6c0 (LWP 6833)]
 [New Thread 0x7fff9b3996c0 (LWP 6834)]
 [New Thread 0x7fff91d856c0 (LWP 6835)]
 [New Thread 0x7fff915846c0 (LWP 6836)]
 [New Thread 0x7fff90d836c0 (LWP 6837)]
 [New Thread 0x7fff905826c0 (LWP 6838)]
 0.5003370299685227

 Thread 1 "python" received signal SIGSEGV, Segmentation fault.
 0x779e4b5b in _PyInterpreterState_GET ()
 at 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
 118 return tstate->interp;

(gdb) p tstate
 $1 = 

(gdb) p tstate->interp
 value has been optimized out

I get:

(gdb) thread apply all bt

 Thread 8 (Thread 0x7fff905826c0 (LWP 6838) "python"):
 #0  futex_wait (val=128, addr=0x55d99b84) at 
../../../libgomp/config/linux/x86/futex.h:97
 #1  do_wait (val=128, addr=) at 
../../../libgomp/config/linux/wait.h:67
 #2  gomp_barrier_wait_end (bar=0x55d99b80, state=128) at 
../../../libgomp/config/linux/bar.c:48
 #3  0x7fffe95cdd28 in gomp_simple_barrier_wait (bar=0x55d99b80) at 
../../../libgomp/config/posix/simple-bar.h:60
 #4  gomp_thread_start (xdata=) at ../../../libgomp/team.c:133
 #5  0x776ac897 in start_thread (arg=) at 
pthread_create.c:444
 #6  0x777336bc in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

 Thread 7 (Thread 0x7fff90d836c0 (LWP 6837) "python"):
 #0  futex_wait (val=128, addr=0x55d99b84) at 
../../../libgomp/config/linux/x86/futex.h:97
 #1  do_wait (val=128, addr=) at 
../../../libgomp/config/linux/wait.h:67
 #2  gomp_barrier_wait_end (bar=0x55d99b80, state=128) at 
../../../libgomp/config/linux/bar.c:48
 #3  0x7fffe95cdd28 in gomp_simple_barrier_wait (bar=0x55d99b80) at 
../../../libgomp/config/posix/simple-bar.h:60
 #4  gomp_thread_start (xdata=) at ../../../libgomp/team.c:133
 #5  0x776ac897 in start_thread (arg=) at 
pthread_create.c:444
 #6  0x777336bc in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S

Re: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Sat Dec02'23 09:34:08AM, Barry Scott wrote:
> From: Barry Scott 
> Date: Sat, 2 Dec 2023 09:34:08 +
> To: Community support for Fedora users 
> CC: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
>
>
> > On 1 Dec 2023, at 03:44, Ranjan Maitra via users 
> >  wrote:
> >
> > So, it seems, so is this a bug that needs to be reported?
>
> Start by reporting on fedora bugzilla against the sip package with all the 
> info you have collected in this email thread.
>

Thank you! Interestingly enough, the sip or sip6 packages were not even 
installed on my system, (though I should add that installing either made no 
difference).

However, the following: 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
 file is where the segfault is, and that is in python3-devel. Perhaps  I just 
report it there and see where that gets me.

Thanks very much again!

Best wishes,
Ranjan
--
___
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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

Hi,

Sorry to bring this back up, but I can not find any error yet in the legacy C 
code.

gdb with python 3.11 gives no error (on F38, program exited normally) but gdb 
with python 3.12 segfaults.

On Thu Nov23'23 08:18:05AM, Community Support for Fedora Users wrote:
> From: Ranjan Maitra via users 
> Date: Thu, 23 Nov 2023 08:18:05 -0600
> To: Community support for Fedora users 
> Cc: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
> On Thu Nov23'23 08:28:36AM, Barry wrote:
> > From: Barry 
> > Date: Thu, 23 Nov 2023 08:28:36 +
> > To: Community support for Fedora users 
> > CC: Ranjan Maitra 
> > Reply-To: Community support for Fedora users 
> > Subject: Re: Python code error in F39, but not in F38
> >
> >
> >
> > > On 22 Nov 2023, at 22:21, Ranjan Maitra via users 
> > >  wrote:
> > >
> > > #4  sipOMFinalise (om=0x7fff9e5ff9a0 ) at 
> > > /usr/src/debug/
> >
> > It is a bug in the sip code is my strong expectation.

So, it seems, so is this a bug that needs to be reported? Where to? I am not 
even sure how to build a small reproducible example because I do not understand 
what part of the C or the python code is resulting in this bug. All the files 
referenced in the valgrind output are in the system(?) python files. The code 
files do not even appear to show up.

> > I would also guess that tstate is likely 0 and causing a SEGV.

The segfault is here (per gdb):

at 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
118 return tstate->interp;

> > What did sip do to damage the tstate (thread state I think).

I don't know what sip is, and how it comes into that code.

Any suggestions on what I should do?

Many thanks and best wishes,
Ranjan


> >
> > Barry
>
> From another thread:
>
> (gdb) p tstate
>
> $1 = 
>
> Sorry, I forgot this (also posted on another sub-thread).
>
> And here are the complete valgrind errors from
>
> valgrind --leak-check=full  --track-origins=yes --show-leak-kinds=all python 
> ./test.py ~/Datasets/Images/tiffs/ultadanga.tiff 
> ../results/ultadanga-64-rgb.png 1 7
>
> at:
>
> https://raw.githubusercontent.com/maitra/Visual-Information-Fidelity---Python3/master/valgrind.errors.txt
>
> One aspect to note is that the C code (not by me) is from 1988, though last 
> updated in 1997. It is not clear to me if that is a plus (because programmers 
> had the time to be more careful in those days) or a minus (because more 
> sophisticated environments are available now). I do compile with -Wall 
> -pedantic and there are no complaints. However, that does not mean that there 
> can not be some memory leak or something else that has stayed dormant all 
> these years and have surfaced with the changes to Python 3.12.
>
> Many thanks and best wishes,
> Ranjan
>
> >
> > --
> > ___
> > 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
--
___
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: vlc alternative?

[Ranjan Maitra via users]

Alex,

I am not sure it does whatever you want, but for streaming youtube and similar 
videos online, I find mpv to be quite sufficient and good for my needs.

HTH!

Best wishes,
Ranjan

On Mon Nov27'23 06:46:04PM, Mario Marietto wrote:
> From: Mario Marietto 
> Date: Mon, 27 Nov 2023 18:46:04 +0100
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: vlc alternative?
>
> obs studio ?
>
> On Mon, Nov 27, 2023 at 6:31 PM Alex  wrote:
>
> > Hi,
> > I'm using vlc with my hdhomerun TV tuner, but vlc has a problem that
> > hasn't been fixed for a really long time. Does anyone have a recommendation
> > for a similar app I can use for streaming?
> >
> > I'm really only otherwise familiar with mplayer, but I don't think it
> > supports streaming in this way where I can connect it to a socket like I
> > can with vlc.
> >
> > btw, the vlc error involves messages like these:
> >
> > [7fb3a4001130] ts demux error: libdvbpsi error (PSI decoder): TS
> > discontinuity (received 10, expected 9) for PID 112
> >
> > Thanks,
> > Alex
> >
> > --
> > ___
> > 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
> >
>
>
> --
> Mario.

> --
> ___
> 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: OT: X11: how to make cut-and-paste with mouse also work on every window

[Ranjan Maitra via users]

On Thu Nov23'23 04:01:08PM, Tom Horsley wrote:
> From: Tom Horsley 
> Date: Thu, 23 Nov 2023 16:01:08 -0500
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: OT: X11: how to make cut-and-paste with mouse also work on
>  every window
>
> On Thu, 23 Nov 2023 14:03:14 -0600
> Ranjan Maitra via users wrote:
>
> > Is there a way to set this up so that it can work reliably on every window?
>
> I'm pretty sure the answer is "no" unfortunately. How windows operate
> on keystrokes and mouse buttons is up to the individual apps.
>
> Some apps can be convinced to work differently. For instance I have
> this xterm line in my .Xdefaults:
>
> XTerm*VT100.Translations: #override : select-end(PRIMARY, CLIPBOARD, 
> CUT_BUFFER0)
>
> That makes xterm place anything I select in every possible form
> of cut buffer or selection (why are there 3, who knows? :-). so I
> can at least paste things from xterm into any other app using whatever
> technique that app wants.

I see, thank you very much for this! I will try this and see how things go. It 
used to be the case, that the cut and paste using the mouse left button  and 
the middle button (also shift-insert keys) used to work pretty much everywhere, 
and now, it is a hit-or-miss depending on the application.

Too bad!

Thanks again!

Best wishes,
Ranjan

--
___
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

OT: X11: how to make cut-and-paste with mouse also work on every window

[Ranjan Maitra via users]

Hi,

I know this is OT, but someone here might know the answer to this.

So, I like the ability to highlight with my mouse left button, and paste with 
my middle (scroll) button. It works on `xterm` but not necessarily on my 
firefox window (some other windows too, but I do not recall now). Is there a 
way to set this up so that it can work reliably on every window?

Many thanks and best wishes,
Ranjan
--
___
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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Thu Nov23'23 08:28:36AM, Barry wrote:
> From: Barry 
> Date: Thu, 23 Nov 2023 08:28:36 +
> To: Community support for Fedora users 
> CC: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
>
>
> > On 22 Nov 2023, at 22:21, Ranjan Maitra via users 
> >  wrote:
> >
> > #4  sipOMFinalise (om=0x7fff9e5ff9a0 ) at 
> > /usr/src/debug/
>
> It is a bug in the sip code is my strong expectation.
> I would also guess that tstate is likely 0 and causing a SEGV.
> What did sip do to damage the tstate (thread state I think).
>
> Barry

From another thread:

(gdb) p tstate

$1 = 

Sorry, I forgot this (also posted on another sub-thread).

And here are the complete valgrind errors from

valgrind --leak-check=full  --track-origins=yes --show-leak-kinds=all python 
./test.py ~/Datasets/Images/tiffs/ultadanga.tiff 
../results/ultadanga-64-rgb.png 1 7

at:

https://raw.githubusercontent.com/maitra/Visual-Information-Fidelity---Python3/master/valgrind.errors.txt

One aspect to note is that the C code (not by me) is from 1988, though last 
updated in 1997. It is not clear to me if that is a plus (because programmers 
had the time to be more careful in those days) or a minus (because more 
sophisticated environments are available now). I do compile with -Wall 
-pedantic and there are no complaints. However, that does not mean that there 
can not be some memory leak or something else that has stayed dormant all these 
years and have surfaced with the changes to Python 3.12.

Many thanks and best wishes,
Ranjan

>
> --
> ___
> 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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Wed Nov22'23 02:36:35PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Wed, 22 Nov 2023 14:36:35 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
> On 11/22/23 14:20, Ranjan Maitra via users wrote:
> > On Wed Nov22'23 09:49:49PM, Barry Scott wrote:
> > > From: Barry Scott 
> > > Date: Wed, 22 Nov 2023 21:49:49 +
> > > > At this point you need get more information.
> > > >
> > > > What do the folllowing GDB commands print?
> > > >
> > > > p tstate
> > > > p tstate->interp
> > > > thread allow all bt
> > > Doh...
> > >
> > >   thread apply all bt
> > >
> > > I always type:
> > >   t a a bt
> > >
> > > and typo'ed the expansion.
> >
> > Thanks, here is what comes out:
> >
> >   (gdb)  p tstate->interp
> >
> >   value has been optimized out
> >   (gdb) thread apply all bt
>
> You missed the first one: "p tstate".
>

My apologies, I did not include this in my cut-and-paste:

(gdb) p tstate

$1 = 

Sorry about that. All this in F39 (python 3.12, of course).

Ranjan



--
___
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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Wed Nov22'23 09:49:49PM, Barry Scott wrote:
> From: Barry Scott 
> Date: Wed, 22 Nov 2023 21:49:49 +
> To: Community support for Fedora users 
> CC: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
>
>
> > On 22 Nov 2023, at 21:32, Barry Scott  wrote:
> >
> >> Any suggestions as to what is going wrong here?
> >
> > At this point you need get more information.
> >
> > What do the folllowing GDB commands print?
> >
> > p tstate
> > p tstate->interp
> > thread allow all bt
> Doh...
>
>   thread apply all bt
>
> I always type:
>   t a a bt
>
> and typo'ed the expansion.

Thanks, here is what comes out:

 (gdb)  p tstate->interp

 value has been optimized out
 (gdb) thread apply all bt


 Thread 1 (Thread 0x77ec7740 (LWP 387946) "python"):
 #0  0x779e4b5b in _PyInterpreterState_GET () at 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
 #1  get_state () at 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:866
 #2  _PyObject_Free (ctx=, p=0x56d898a0) at 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Objects/obmalloc.c:1850
 #3  0x7fff9e5e292f in sip_api_free (mem=) at 
/usr/src/debug/sip-4.19.25-9.fc39.x86_64/siplib/siplib.c:2239
 #4  sipOMFinalise (om=0x7fff9e5ff9a0 ) at 
/usr/src/debug/sip-4.19.25-9.fc39.x86_64/susr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Python/pylifecycle.c:1977
 #8  0x77ab6337 in Py_RunMain () at 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:691
 #9  0x77a7185c in Py_BytesMain (argc=, argv=) at /usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Modules/main.c:743
 #10 0x7764614a in __libc_start_call_main 
(main=main@entry=0x5160
 --Type  for more, q to quit, c to continue without paging--

 , argc=argc@entry=4, argv=argv@entry=0x7fffdfd8) at 
../sysdeps/nptl/libc_start_call_main.h:58
 #11 0x7764620b in __libc_start_main_impl (main=0x5160 , 
argc=4, argv=0x7fffdfd8, init=, fini=, 
rtld_fini=, stack_end=0x7fffdfc8) at ../csu/libc-start.c:360
 #12 0x5095 in _start ()
(gdb)

Many thanks and best wishes,
Ranjan

--
___
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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Tue Nov21'23 05:25:35PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Tue, 21 Nov 2023 17:25:35 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
> On 11/19/23 10:01, Ranjan Maitra via users wrote:
> > I tried:
> >
> > $ gdb python "./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7"
> > (gdb)
>
> $ gdb python
> (gdb) run ./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7
> --

Thanks very much for this for explaining how to run gdb on a python script! On 
Python 3.12 (Fedora 39), I get, at the very end:

 Thread 1 "python" received signal SIGSEGV, Segmentation fault.
 0x779e4b5b in _PyInterpreterState_GET ()
 at 
/usr/src/debug/python3.12-3.12.0-1.fc39.x86_64/Include/internal/pycore_pystate.h:118
 118 return tstate->interp;
 (gdb)

On Python 3.11 (Fedora 38), I get, at the very end:

 [Inferior 1 (process 199650) exited normally]
 (gdb)

Any suggestions as to what is going wrong here?

Many thanks and best wishes,
Ranjan








> ___
> 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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Wed Nov22'23 08:12:58AM, George N. White III wrote:
> From: "George N. White III" 
> Date: Wed, 22 Nov 2023 08:12:58 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: Python code error in F39, but not in F38
>
> On Sun, Nov 19, 2023 at 2:02 PM Ranjan Maitra via users <
> users@lists.fedoraproject.org> wrote:
>
> > On Sun Nov19'23 05:35:19PM, Barry wrote:
> > > From: Barry 
> > > Date: Sun, 19 Nov 2023 17:35:19 +
> > > To: Community support for Fedora users 
> >  >
> > > >
> > > >
> > > > It is possible that there is a bug in the code itself, but nothing
> > above
> > > > points to my created code.
> > > >
> > > > Any suggestions? Or is this a bug?
> > >
> > > Are you using C extensions in your code? If so I would suspect them for
> > corrupting python. I think you can get into gdb inside the core file with
> > coredumpctl debug.
> >
> > The python code calls a shared object library that is written in C. But
> > why does this core dump only happen in F39 (python 3.12) and not with
> > F38 (python 3.11)?
> >
>
> There were some big changes in 3.12 (driven by the need to support Fortran
> on
> Windows and macOS by replacing very old gfortran version with flang-new).
> I havrn't
> had time to look at what is being used in linux, but you could get a quick
> overview from
> ldd.  See: <
> https://discuss.python.org/t/why-scipy-builds-for-python-3-12-on-windows-are-a-minor-miracle-especially-in-conda-forge/38270
> >
>
> There is also new build system, so a lot of work getting everything working
> in 3.12.  Meanwhile
> you can run 3.11 stuff using python environments.
>

Thanks! Interesting, I wonder if that is also what has caused tensorflow to not 
go up to 3.12 for now. From what I read somewhere (I think on an archived 
tensorflow mailing list or something) the linux builds are up, but not the 
MacO$ and Windoze builds. Both of which, if I had my way, should never have 
been allowed even indirectly into any professional environment.

Ranjan
--
___
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: Python code error in F39, but not in F38

[Ranjan Maitra via users]

On Sun Nov19'23 05:35:19PM, Barry wrote:
> From: Barry 
> Date: Sun, 19 Nov 2023 17:35:19 +
> To: Community support for Fedora users 
 >
> >
> >
> > It is possible that there is a bug in the code itself, but nothing above
> > points to my created code.
> >
> > Any suggestions? Or is this a bug?
>
> Are you using C extensions in your code? If so I would suspect them for 
> corrupting python. I think you can get into gdb inside the core file with 
> coredumpctl debug.

The python code calls a shared object library that is written in C. But
why does this core dump only happen in F39 (python 3.12) and not with
F38 (python 3.11)?

> What does “info shared” tell you about what code has been loaded into memory?

This would be under gdb, I presume.


> It is also worth trying to find the type of the object that is being deleted, 
> _PyObject_Free will have pointer to the object.
> Also not sure where siplib.c is from is it python or an extension?

Thanks, I don't know either, but there is no siplib.c anywhere on either
of my two systems.

> I am assuming here that you are familiar with debugging with gdb.

Thanks, I am familiar with using gdb for a C program, never used it with
python code calling a C shared object.

I tried:

$ gdb python "./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7"
GNU gdb (Fedora Linux) 13.2-10.fc39
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from 
/home/localuser/.cache/debuginfod_client/07023eb4f297ae1d4591e--Type  for 
more, q to quit, c to continue without paging--
c808ab20b2788c542be/debuginfo...
./test.py ultadanga.tiff ultadanga-64-rgb.png 1 7: No such file or directory.
(gdb)


Not quite sure how to proceed here.

Many thanks again, and best wishes,
Ranjan

--
___
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

Python code error in F39, but not in F38

[Ranjan Maitra via users]

Hi,

I was running the code here: 
https://github.com/maitra/Visual-Information-Fidelity---Python3

However, the code runs in F38 (python 3.11) without error, but not in F39 
(python 3.12) where it
ends with a segmentation fault (after doing the calculations).

Both, however, give an answer that are not the same after the 14th
decimal place. Not sure if I should be bothered about that.

Looking at valgrind, I can not tell if there is an error in the python call 
itself.  Here is what I get (note that the code calls shared objects created by 
the gcc compiler).

==278781== Invalid read of size 8
==278781==at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
==278781==by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
==278781==by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
==278781==by 0x6526E92E: UnknownInlinedFun (siplib.c:2241)
==278781==by 0x6526E92E: UnknownInlinedFun (objmap.c:69)
==278781==by 0x6526E92E: finalise (siplib.c:2143)
==278781==by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
==278781==by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
==278781==by 0x4B22336: Py_RunMain (main.c:691)
==278781==by 0x4ADD85B: Py_BytesMain (main.c:743)
==278781==by 0x4EE1149: (below main) (libc_start_call_main.h:58)
==278781==  Address 0x10 is not stack'd, malloc'd or (recently) free'd
==278781==
==278781==
==278781== Process terminating with default action of signal 11 (SIGSEGV): 
dumping core
==278781==  Access not within mapped region at address 0x10
==278781==at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
==278781==by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
==278781==by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
==278781==by 0x6526E92E: finalise (siplib.c:2143)
==278781==by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
==278781==by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
==278781==by 0x4B22336: Py_RunMain (main.c:691)
==278781==by 0x4ADD85B: Py_BytesMain (main.c:743)
==278781==by 0x4EE1149: (below main) (libc_start_call_main.h:58)
==278781==  If you believe this happened as a result of a stack
==278781==  overflow in your program's main thread (unlikely but
==278781==  possible), you can try to increase the size of the
==278781==  main thread stack using the --main-stacksize= flag.
==278781==  The main thread stack size used in this run was 8388608.
==278781==
==278781== HEAP SUMMARY:
==278781== in use at exit: 18,046,811 bytes in 92,137 blocks
==278781==   total heap usage: 2,212,074 allocs, 2,119,937 frees, 1,983,813,202 
bytes allocated
==278781==
==278781== LEAK SUMMARY:
==278781==definitely lost: 2,160,027 bytes in 41,915 blocks
==278781==indirectly lost: 112 bytes in 2 blocks
==278781==  possibly lost: 5,021,632 bytes in 34,430 blocks
==278781==still reachable: 10,863,024 bytes in 15,769 blocks
==278781== suppressed: 0 bytes in 0 blocks



It is possible that there is a bug in the code itself, but nothing above
points to my created code.

Any suggestions? Or is this a bug?

Many thanks and best wishes,
Ranjan

--
___
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: recommended practice for python 3.11 on F39

[Ranjan Maitra via users]

My thanks again for this!


On Sat Nov18'23 08:26:10AM, George N. White III wrote:
> From: "George N. White III" 
> Date: Sat, 18 Nov 2023 08:26:10 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: recommended practice for python 3.11 on F39
>
> On Fri, Nov 17, 2023 at 10:29 PM Ranjan Maitra via users <
> users@lists.fedoraproject.org> wrote:
>
> > So, it turns out that there is no tensorflow for Python 3.12, which is
> > what is shipped out with F39.
> >
> > I tried to downgrade my python using
> >
> > sudo dnf downgrade python --releasever=38
> >
> > that downgrades a huge bunch of things, including important components
> > like rpm.
> >
>
> Many system tools use python -- as you have discovered, downgrading it will
> cause problems.
>
> >
> > However, dnf install/update pretty much anything gives a segmentation
> > fault after that.
> >
> > $ sudo dnf update --exclude=python\*
> > Last metadata expiration check: 2:37:29 ago on Fri 17 Nov 2023 05:50:32 PM
> > CST.
> > Segmentation fault
> >
> > Staying within the dnf system, is there a better way to keep the older
> > version of python around?
> >
>
> You broke dnf.  Fix it and you can install the F39 python3.11 package.
> There are ways
> (environments, tweaks to the hashbang line in python scripts).  With F38 I
> used 3rd party
>  python tools that needed python-3.10.   I haven't had time to see what is
> provided with
> F39, but you can look for conda or mamba packages.

I was not aware that it was possibe to install python3.11 using dnf in F39, so 
thanks for this. Wow, amazing! The old tensorflow installation just works out 
of the box. Did not expect that.

Thanks for this!

>
> Anaconda Python is a widely used platform independent system that supports
> use of multiple
> python versions via environments.
>

Thanks also for all the other information, it is very helpful and I will keep 
it with me for later use.

Best wishes,
Ranjan
--
___
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

recommended practice for python 3.11 on F39

[Ranjan Maitra via users]

So, it turns out that there is no tensorflow for Python 3.12, which is
what is shipped out with F39.

I tried to downgrade my python using

sudo dnf downgrade python --releasever=38

that downgrades a huge bunch of things, including important components
like rpm.

However, dnf install/update pretty much anything gives a segmentation
fault after that.

$ sudo dnf update --exclude=python\*
Last metadata expiration check: 2:37:29 ago on Fri 17 Nov 2023 05:50:32 PM CST.
Segmentation fault

Staying within the dnf system, is there a better way to keep the older
version of python around?

Many thanks,
Ranjan
--
___
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: f39 emacs strange behavior?

[Ranjan Maitra via users]

On Thu Nov16'23 08:46:17PM, Ben Hancock wrote:
> From: Ben Hancock 
> Date: Thu, 16 Nov 2023 20:46:17 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: f39 emacs strange behavior?
>
> On 11/12/23 08:12, Ranjan Maitra wrote:
> > Right, now, trying my luck with nvim for writing this email (because
> > mutt for me is linked to an editor, in my case, it was emacs).
>
> FWIW, you may want to try `mg` as a backup editor for Emacs. If you're used
> to Emacs key-bindings, it's sure to be more familiar. When I used mutt more
> regularly I set mg as my fallback for times when I hadn't yet fired up Emacs
> and done `M-x server-start`:
>
>   set editor = 'emacsclient --alternate-editor mg'
>
> Ben

Thanks, Ben! I am more or less finding my way around nvim, but I have
not yet figured out two things yet.

I loved the autoformatting feature of C, etc in emacs. Basically as I
typed, things would get formatted. And I have not really been able to
figure out if that is possible here (automagically, without pressing any
key combination).

The other thing I will look at more carefully this weekend is to figure
out a way to reliably highlight a area with my mouse left button and
then paste it with my second mouse button (the wheel). Inside nvim, it
is largely not reliable (with workarounds in many cases, but with key
combinations) and I can not quite figure out why it is not. In the old
days before DEs, the idea of highlight and paste (rather than use
whatever key combination) is something I really got used to.

Many thanks and best wishes,
Ranjan

--
___
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: emacs is hopeless

[Ranjan Maitra via users]

On Wed Nov15'23 09:58:23AM, Community Support for Fedora Users wrote:
> From: Ranjan Maitra via users 
> Date: Wed, 15 Nov 2023 09:58:23 -0600
> To: Community support for Fedora users 
> Cc: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> On Wed Nov15'23 11:21:51AM, George N. White III wrote:
> > From: "George N. White III" 
> > Date: Wed, 15 Nov 2023 11:21:51 -0400
> > To: Community support for Fedora users 
> > Reply-To: Community support for Fedora users 
> > Subject: Re: emacs is hopeless
> >
> > On Tue, Nov 14, 2023 at 6:12 PM Ranjan Maitra via users <
> > users@lists.fedoraproject.org> wrote:
> >
> > > [...]
> > >
> > Still sad about having to give up on emacs, but, oh, well! ESS is not
> > > really that well-supported (on Fedora, at least anymore).
> > >
> >
> > There has been very little activity in the ESS site.  Unless someone steps
> > forward to maintain
> > it on new linux it may slowly die as people upgrade their systems.
> >
>
> Right, there is still some activity on the github site (five months
> ago), but the RPM no longer builds on Fedora (I tried it a couple of
> days ago with the updated github versio).
>
> I have pretty much given up on emacs now and am working to get nvim to a
> (for me) saner state. It is quite amazing how quickly we adapt to new 
> environments, though falling back to old ways of doing things,  out of 
> unthinking old habit, is why readline is important.
>
> My next stop: try to undo something without exiting insert mode. (Ctrl-/
> in emacs).

I figured this out looking at the remapping for Ctrl-x-Ctrl-s. I came up
with:

inoremap  :u

For good measure, I even mapped out how to get out of the insert mode
directly, without having to launch a few missiles too:

inoremap  :q

These seem to work.

Let us see what else I come up with.

Best wishes,
Ranjan




>
> Best wishes,
> Ranjan
>
>
> >
> > --
> > 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
> > 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
___
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: emacs is hopeless

[Ranjan Maitra via users]

On Wed Nov15'23 11:21:51AM, George N. White III wrote:
> From: "George N. White III" 
> Date: Wed, 15 Nov 2023 11:21:51 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> On Tue, Nov 14, 2023 at 6:12 PM Ranjan Maitra via users <
> users@lists.fedoraproject.org> wrote:
>
> > [...]
> >
> Still sad about having to give up on emacs, but, oh, well! ESS is not
> > really that well-supported (on Fedora, at least anymore).
> >
>
> There has been very little activity in the ESS site.  Unless someone steps
> forward to maintain
> it on new linux it may slowly die as people upgrade their systems.
>

Right, there is still some activity on the github site (five months
ago), but the RPM no longer builds on Fedora (I tried it a couple of
days ago with the updated github versio).

I have pretty much given up on emacs now and am working to get nvim to a
(for me) saner state. It is quite amazing how quickly we adapt to new 
environments, though falling back to old ways of doing things,  out of 
unthinking old habit, is why readline is important.

My next stop: try to undo something without exiting insert mode. (Ctrl-/
in emacs).

Best wishes,
Ranjan


>
> --
> 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
> 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: emacs is hopeless

[Ranjan Maitra via users]

On Tue Nov14'23 06:02:27PM, George N. White III wrote:
> From: "George N. White III" 
> Date: Tue, 14 Nov 2023 18:02:27 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> On Tue, Nov 14, 2023 at 3:26 PM Ranjan Maitra via users <
> users@lists.fedoraproject.org> wrote:
>
> >
> > Indeed, the culprit appears to have been the emacs-ess package, which
> > was creating issues even with it not being called.
> >
> > Unfortunately, for me, emacs-ess was the main selling point of emacs,
> > and with that rendering emacs unusable, it appears that I will have to
> > move on to nvim which has a good R interface.
> >
>
> From https://www.emacswiki.org/emacs/EmacsSpeaksStatistics: Fun Fact:
> Many current RStudio users, (like Jenny Bryan) used to be ESS users!
>
> I'm a member of that ESS to RStudio crowd, but my use case hs changed from
> writing R code to maintenance, and many colleagues working in enterprise
> environments where access to linux is command-line on data center servers,
> but
> they do have R-studio-server and Jupyer that can be used with web browser
> in
> Windows.

Thanks! I do not care for Rstudio. In my experience, it is **slow**, and wastes 
all the time I gain by
using a WM (non-DE).

But I think I found my answer to the nvim keybinding I would like here:
https://superuser.com/questions/88432/save-in-insert-mode-vim

inoremap  :w

That is good.

Still sad about having to give up on emacs, but, oh, well! ESS is not
really that well-supported (on Fedora, at least anymore).

Ranjan
___
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: [Off List] Re: emacs is hopeless

[Ranjan Maitra via users]

On Wed Nov15'23 08:38:07AM, Stephen Morris wrote:
> From: Stephen Morris 
> Date: Wed, 15 Nov 2023 08:38:07 +1100
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: [Off List] Re: emacs is hopeless
>
> On 15/11/23 06:36, Joe Zeff wrote:
> > On 11/14/2023 12:26 PM, Ranjan Maitra via users wrote:
> > > What really irritates me about vi and its friends is that it throws you
> > > out of editing (insert) mode in order to save the file, and needs
> > > another key to come back in.
> >
> > You might want to consider nano; the most common commands are listed at
> > the bottom of the window, including the one needed to get to the rest of
> > them.
> The one issue I've found with nano, which might be my lack of understanding
> of it, is you can't paste anything in that has been copied outside of nano,
> the paste listed at the bottom of the window does nothing in this scenario.
>

Thanks, everyone! I have used nano as part of the pine program in
ancient times (never really realized it was an editor, until my students
started using it) as part of the UW produced ecosystem (I am a UW
product from around that time it was developed there). It can perhaps do
syntax highlighting, but I am also looking for C mode, python mode, TeX mode, 
completions and the like which make
editors such as emacs (or vi) so much more powerful.

I have been trying to overcome my aversion to vi(m) and have been using
nvim now for the past several hours. I have recovered at least a few of my
keybindings (really readline things), and I presume I can figure out a better 
way
of dealing with the fact that we have to constantly move between insert
mode and some other mode just to occassionally save a file (in emacs,
I got used to pressing Ctrl-x-Ctrl-s every few minutes just to save
things while typing).

Thanks again!

Best wishes,
Ranjan
___
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: emacs is hopeless

[Ranjan Maitra via users]

On Mon Nov13'23 11:41:28AM, George N. White III wrote:
> From: "George N. White III" 
> Date: Mon, 13 Nov 2023 11:41:28 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> On Mon, Nov 13, 2023 at 9:04 AM Ranjan Maitra via users <
> users@lists.fedoraproject.org> wrote:
>
> > [...]
> > I also tried emacs-nox and have the same problem. Removing my .emacs did
> > not have any effect.
> >
> I do not mess with my system files so I am a bit confused as to how to
> > track this down. Is there a
> >
> verbose mode which allows me to see what to do?
> >
>
> Try running emacs as newly created user to rule out something in your
> ~/.emacs.d or some
> shell startup script creating variables that confuse emacs. Have you tried
> "emacs -nw" for text mode
> to rule out a GUI issue?
>
> It might help to have a simple example with a description of what happens.
> If emacs is failing due to
> some conflict with libraries you might see an error with journalctl.  Make
> a note of the time the error
> occurs to help identify related errors.
>
>
> >
> > I have emacs-ess also installed (from Fedora 36) that has not been updated
> > and is probably obsolete or retired.
> >
>
> Probably good to remove that old package.  You can reinstall from upstream
> source if Fedora 39 doesn't have a
> package.

Indeed, the culprit appears to have been the emacs-ess package, which
was creating issues even with it not being called.

Unfortunately, for me, emacs-ess was the main selling point of emacs,
and with that rendering emacs unusable, it appears that I will have to
move on to nvim which has a good R interface.

What really irritates me about vi and its friends is that it throws you
out of editing (insert) mode in order to save the file, and needs
another key to come back in.

I don't know if it is possible to remap a key (say C-x-C-s) that would
exit the "insert" mode, save the file, and then come back into the
"insert" mode.

Anyway, this is an off-topic question. At least it appears that I found
the cause of my problems.

Many thanks,
Ranjan
___
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: emacs is hopeless

[Ranjan Maitra via users]

On Mon Nov13'23 07:55:04AM, Neal Becker wrote:
> From: Neal Becker 
> Date: Mon, 13 Nov 2023 07:55:04 -0500
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> On Sun, Nov 12, 2023 at 12:17 PM Tom Horsley  wrote:
>
> > I reported strange things with emacs earlier, but I thought it might be
> > something wrong with my partially configured system.
> >
> > Nope, it is just plain busted. I've added this bug report:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2249379
> >
> > I guess I'll have to try building from the fedora 38 source rpm
> > on fedora 39 and see if I can get a working emacs that way.
> >
>
> It emacs all day every day here, same as the last 30? years.
>
> I'm using [copr:copr.fedorainfracloud.org:bhavin192:emacs-pretest] on 1
> machine, although the stock emacs on another machine is working also.

I also tried emacs-nox and have the same problem. Removing my .emacs did not 
have any effect. I do not mess with my system files so I am a bit confused as 
to how to track this down. Is there a verbose mode which allows me to see what 
to do?

I have emacs-ess also installed (from Fedora 36) that has not been updated and 
is probably obsolete or retired.

Best wishes,
Ranjan


> ___
> 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: emacs is hopeless

[Ranjan Maitra via users]

On Sun Nov12'23 04:12:07PM, George Avrunin wrote:
> From: George Avrunin 
> Date: Sun, 12 Nov 2023 16:12:07 -0500
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> On 11/12/23 13:19, Ranjan Maitra via users wrote:
>
> > Thank you for this: downgrading emacs for me to 28.3 (F38) gets rid of
> > the problem that I was having, and that is, that emacs 29.1 can not load
> > a file for me (without emacs -Q).
> >
> > With emacs -Q in 29.1 (F39), I can load the file all right, but I do not
> > have the correct fonts, and I can not seem to load those.
> >
> > I wonder why emacs users have not reported my issue with 29.1 on the emacs
> > mailing list.
> >
> > Best wishes,
> > Ranjan
> >
>
> As a data point, Emacs 29.1 (from emacs-29.1-2.fc39.x86_64) in Fedora 39
> is working fine for me.  I had to upgrade a couple of the elisp packages
> I use and it seems that the very old auto-insert-tkld package that I've
> used for a long time doesn't work anymore, though I did get some
> semi-informative error messages.  (For the moment, I've just taken the
> auto-insert-tkld stuff out of my .emacs; maybe I'll try to figure that
> out later when I have more time, or set up one of the alternatives.)
> "emacs -q" worked without problems from the beginning.
>
> Since I'm using Wayland, I had to install wl-clipboard and add some code
> in .emacs to get paste with the middle mouse button into emacs to work
> (per the Emacs Wiki: https://www.emacswiki.org/emacs/CopyAndPaste).  But
> everything else I've tried seems to work fine, including AUCTeX, both
> with opening new files and editing existing ones.
>
> I'm using KDE with an NVidia card and the driver from rpmfusion on my
> desktop and KDE with Intel video on a Dell laptop, also in Fedora 39.
> Emacs is ok on both machines.  I haven't tried it in X.

I see, I use the X11 window system (no desktop environment, but openbox window 
manager).

Thanks for your input!

Best wishes,
Ranjan

>
> ___
> 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: emacs is hopeless

[Ranjan Maitra via users]

On Sun Nov12'23 11:22:07AM, Joe Zeff wrote:
> From: Joe Zeff 
> Date: Sun, 12 Nov 2023 11:22:07 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> On 11/12/2023 11:19 AM, Ranjan Maitra via users wrote:
> > I wonder why emacs users have not reported my issue with 29.1 on the emacs
> > mailing list.
>
> Have you reported it?

On that mailing list, yes.

Ranjan
___
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: emacs is hopeless

[Ranjan Maitra via users]

On Sun Nov12'23 07:04:36PM, francis.montag...@inria.fr wrote:
> From: francis.montag...@inria.fr
> Date: Sun, 12 Nov 2023 19:04:36 +0100
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: emacs is hopeless
>
> Hi
>
> On Sun, 12 Nov 2023 12:17:04 -0500 Tom Horsley wrote:
>
> > I reported strange things with emacs earlier, but I thought it might be
> > something wrong with my partially configured system.
>
> > Nope, it is just plain busted. I've added this bug report:
>
> > https://bugzilla.redhat.com/show_bug.cgi?id=2249379
>
> I don't have that problem myself, using also X11.
>
> Do you have it also running "emacs -Q" (I don't) ?
>
> I'm using also (not with -Q of course) a legacy terminus font, declared in
> ~/.Xdefaults as:
>
> *Font:-*-terminus-medium-*-*-*-16-*-*-*-*-*-iso10646-1
> *font:-*-terminus-medium-*-*-*-16-*-*-*-*-*-iso10646-1
>
> Install first the terminus-fonts-legacy-x11 RPM.
>
> > I guess I'll have to try building from the fedora 38 source rpm
> > on fedora 39 and see if I can get a working emacs that way.
>
> You can also try to downgrade with:
>
>   dnf --releasever=38 downgrade emacs
>
> dnf accept this, emacs (28.3) starts properly.

Thank you for this: downgrading emacs for me to 28.3 (F38) gets rid of
the problem that I was having, and that is, that emacs 29.1 can not load
a file for me (without emacs -Q).

With emacs -Q in 29.1 (F39), I can load the file all right, but I do not
have the correct fonts, and I can not seem to load those.

I wonder why emacs users have not reported my issue with 29.1 on the emacs
mailing list.

Best wishes,
Ranjan

___
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: f39 emacs strange behavior?

[Ranjan Maitra via users]

On Sat Nov11'23 06:21:48PM, Tom Horsley wrote:
> From: Tom Horsley 
> Date: Sat, 11 Nov 2023 18:21:48 -0500
> To: Fedora List 
> Reply-To: Community support for Fedora users 
> Subject: f39 emacs strange behavior?
>
> I have by no means finished tweaking my fedora 39 boot partition,
> but the last time I was booted there, emacs was a complete mess.
>
> It seemed to take forever to respond to keystrokes. Scrolling the
> screen would leave random characters in various places which would
> disappear if I moved the cursor over them. Probably other weirdness
> I didn't figure out.
>
> Anyone else seen this?
>
> I've used alternatives to make emacs-lucid the default. I'll see
> if it works better then next time I boot f39...

Did you have any better luck with this. Upgrading to Fedora 39 appears to have 
made my Emacs unusable in that I can no longer open any existing file.

Right, now, trying my luck with nvim for writing this email (because mutt for 
me is linked to an editor, in my case, it was emacs).

Best wishes,
Ranjan


> ___
> 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: F38: systemd-resolved.service oddity

[Ranjan Maitra via users]

On Fri Sep29'23 11:44:08PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Fri, 29 Sep 2023 23:44:08 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/29/23 20:58, Ranjan Maitra wrote:
> > Thanks!
> >
> >
> > > On 9/28/23 19:03, Ranjan Maitra wrote:
> > > > On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> > > > > The problem is that the VPN is setting its options on the global state
> > > > > instead of the tunnel where they should be.  Normally, when the 
> > > > > tunnel goes
> > > > > away, so do the special settings for it, but here they're global, so 
> > > > > they
> > > > > don't.  I use a VPN at work and I have a little script that I run 
> > > > > after
> > > > > connecting that sets the options for me.
> > > >
> > > > Btw, can I know more about this script? Though it would be nice not to 
> > > > have to run anything as it just a week ago.
> > >
> > > I don't know why it would have changed recently and I also don't have
> > > anything on the global setting.
> > >
> > > My script has:
> > > resolvectl dns tun0 
> > > resolvectl default-route tun0 false
> > > resolvectl domain tun0 
> > >
> > > You probably need something more to remove the global settings as well.
> >
> > Is this a bug that should be reported? Against what? The reason I hesitate 
> > is because Cisco SecureClient VPN (a closed source proprietary application) 
> > is involved.
>
> And that's the only thing that could be doing it, so I don't think there's
> much point in filing a bug.  I'm curious how it's doing that though.

As an update, some update to Fedora packages appears to have addressed this 
issue for about a bit more than the past couple of weeks. There has been no 
update to Cisco SecureClient in the meantime, so it appears that the issue must 
have been some update to some Fedora package which seems to have been fixed at 
least for now.

As reported in an earlier separate thread, the glibc issue with updated 
versions continues to not make Cisco SecureClient work at all, though. 
Downdating to glibc-2.37-1 is the only way to get SecureClient to work.

Best wishes,
Ranjan
___
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: LiveUSB doesn't boot

[Ranjan Maitra]

On Sun Oct01'23 01:39:47PM, Joe Zeff wrote:
> From: Joe Zeff 
> Date: Sun, 1 Oct 2023 13:39:47 -0600
> To: Fedora 
> Reply-To: Community support for Fedora users 
> Subject: LiveUSB doesn't boot
>
> Recently, I had trouble creating a LiveUSB and asked for help here.  I was
> given instructions on how to create it using dd, and followed them after
> correcting a slight error in the instructions.  Now, I've finally got my
> laptop back, and tried to use the flash drive.  All that happens is a grub>
> prompt.  I don't know what went wrong, or how to correct it. This is the
> command that I used:
>
> dd if=f38.iso of=/dev/sdX bs=1M
>
> And the correction was using M instead of m.

It is not clear to me if things work.

To use dd, you have to unmount the drive, did you do that?

We need more information on the laptop to help.

Ranjan

> ___
> 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: F38: systemd-resolved.service oddity

[Ranjan Maitra]

On Fri Sep29'23 11:44:08PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Fri, 29 Sep 2023 23:44:08 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/29/23 20:58, Ranjan Maitra wrote:
> > Thanks!
> >
> >
> > > On 9/28/23 19:03, Ranjan Maitra wrote:
> > > > On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> > > > > The problem is that the VPN is setting its options on the global state
> > > > > instead of the tunnel where they should be.  Normally, when the 
> > > > > tunnel goes
> > > > > away, so do the special settings for it, but here they're global, so 
> > > > > they
> > > > > don't.  I use a VPN at work and I have a little script that I run 
> > > > > after
> > > > > connecting that sets the options for me.
> > > >
> > > > Btw, can I know more about this script? Though it would be nice not to 
> > > > have to run anything as it just a week ago.
> > >
> > > I don't know why it would have changed recently and I also don't have
> > > anything on the global setting.
> > >
> > > My script has:
> > > resolvectl dns tun0 
> > > resolvectl default-route tun0 false
> > > resolvectl domain tun0 
> > >
> > > You probably need something more to remove the global settings as well.
> >
> > Is this a bug that should be reported? Against what? The reason I hesitate 
> > is because Cisco SecureClient VPN (a closed source proprietary application) 
> > is involved.
>
> And that's the only thing that could be doing it, so I don't think there's
> much point in filing a bug.  I'm curious how it's doing that though.

Right, I have been busy these past few days, but perhaps I should go and  see 
what got upgraded. Cisco SecureClient has not got upgraded so must be something 
in Fedora.

Best wishes,
Ranjan

> ___
> 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: F38: systemd-resolved.service oddity

[Ranjan Maitra]

Thanks!


> On 9/28/23 19:03, Ranjan Maitra wrote:
> > On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> > > The problem is that the VPN is setting its options on the global state
> > > instead of the tunnel where they should be.  Normally, when the tunnel 
> > > goes
> > > away, so do the special settings for it, but here they're global, so they
> > > don't.  I use a VPN at work and I have a little script that I run after
> > > connecting that sets the options for me.
> >
> > Btw, can I know more about this script? Though it would be nice not to have 
> > to run anything as it just a week ago.
>
> I don't know why it would have changed recently and I also don't have
> anything on the global setting.
>
> My script has:
> resolvectl dns tun0 
> resolvectl default-route tun0 false
> resolvectl domain tun0 
>
> You probably need something more to remove the global settings as well.

Is this a bug that should be reported? Against what? The reason I hesitate is 
because Cisco SecureClient VPN (a closed source proprietary application) is 
involved.

Best wishes,
Ranjan
___
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: F38: systemd-resolved.service oddity

[Ranjan Maitra]

On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Thu, 28 Sep 2023 10:32:55 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/28/23 05:02, Ranjan Maitra wrote:
> >   $ resolvectl dns
> >   Global: [IP addresses associated with my VPN site]   {*}
> >   Link 2 (enp57s0u2u1u1): [IP addresses associated with my ISP] 192.168.1.1 
> > {**}
> >   Link 22 (cscotun0):
> >
> >   $ resolvectl domain
> >   Global: [VPN connection domainname] [ISP]
> >   Link 2 (enp57s0u2u1u1): [ISP]
> >   Link 22 (cscotun0):
> >
> > where [VPN connection] stands for the address that is associated with VPN.
> >
> > After stopping VPN:
> >
> >   $ resolvectl dns
> >   Global: [Same as {*}]
> >   Link 2 (enp57s0u2u1u1): [Same as {**}]
> >
> >   $ resolvectl domain
> >   Global: [VPN connection domainname] [ISP]
> >   Link 2 (enp57s0u2u1u1): [ISP]
> >
> > After $ sudo systemctl restart systemd-resolved.service
> >
> > $ resolvectl dns
> >   Global:
> >   Link 2 (enp57s0u2u1u1): [Same as {**}]
> >
> > $ resolvectl domain
> >   Global:
> >   Link 2 (enp57s0u2u1u1): [ISP]
> >
> > Seems to me there is something "sticky" about the VPN connection?
>
> The problem is that the VPN is setting its options on the global state
> instead of the tunnel where they should be.  Normally, when the tunnel goes
> away, so do the special settings for it, but here they're global, so they
> don't.  I use a VPN at work and I have a little script that I run after
> connecting that sets the options for me.

Btw, can I know more about this script? Though it would be nice not to have to 
run anything as it just a week ago.

Best wishes,
Ranjan


> ___
> 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: F38: systemd-resolved.service oddity

[Ranjan Maitra]

On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Thu, 28 Sep 2023 10:32:55 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/28/23 05:02, Ranjan Maitra wrote:
> >   $ resolvectl dns
> >   Global: [IP addresses associated with my VPN site]   {*}
> >   Link 2 (enp57s0u2u1u1): [IP addresses associated with my ISP] 192.168.1.1 
> > {**}
> >   Link 22 (cscotun0):
> >
> >   $ resolvectl domain
> >   Global: [VPN connection domainname] [ISP]
> >   Link 2 (enp57s0u2u1u1): [ISP]
> >   Link 22 (cscotun0):
> >
> > where [VPN connection] stands for the address that is associated with VPN.
> >
> > After stopping VPN:
> >
> >   $ resolvectl dns
> >   Global: [Same as {*}]
> >   Link 2 (enp57s0u2u1u1): [Same as {**}]
> >
> >   $ resolvectl domain
> >   Global: [VPN connection domainname] [ISP]
> >   Link 2 (enp57s0u2u1u1): [ISP]
> >
> > After $ sudo systemctl restart systemd-resolved.service
> >
> > $ resolvectl dns
> >   Global:
> >   Link 2 (enp57s0u2u1u1): [Same as {**}]
> >
> > $ resolvectl domain
> >   Global:
> >   Link 2 (enp57s0u2u1u1): [ISP]
> >
> > Seems to me there is something "sticky" about the VPN connection?
>
> The problem is that the VPN is setting its options on the global state
> instead of the tunnel where they should be.  Normally, when the tunnel goes
> away, so do the special settings for it, but here they're global, so they
> don't.  I use a VPN at work and I have a little script that I run after
> connecting that sets the options for me.

Thanks, so what changed in the last week? Is it at the VPN end? I don't see an 
update of my client (Cisco SecureClient).

Best wishes,
Ranjan
___
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: F38: systemd-resolved.service oddity

[Ranjan Maitra]

Thank you!

On Wed Sep27'23 03:04:53PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Wed, 27 Sep 2023 15:04:53 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/27/23 09:14, Ranjan Maitra wrote:
> >  From the past week, I have had an issue in that after several hours, some 
> > particular sites become inaccessible to me, and can only be accessed if I 
> > use restart using sudo systemctl restart systemd-resolved.service
> >
> > What particular  issues cause this? Why did it start a week ago, and has 
> > become quite reliable in its annoyance? (I have to say that when I can no 
> > longer access this site, I am no longer on Cisco SecureClient VPN, which is 
> > also one of the sites which can not be accessed with Cisco SecureClient VPN 
> > without restarting systemd-resolved.service, and the site is my worksite 
> > domain).
>
> That is probably relevant.  resolved supports split DNS when using a
> VPN.

I think so too!

> Try the following commands both while the VPN is running and then after you
> stop it:
>
> resolvectl dns
> resolvectl domain

while running:

 $ resolvectl dns
 Global: [IP addresses associated with my VPN site]   {*}
 Link 2 (enp57s0u2u1u1): [IP addresses associated with my ISP] 192.168.1.1 {**}
 Link 22 (cscotun0):



 $ resolvectl domain
 Global: [VPN connection domainname] [ISP]
 Link 2 (enp57s0u2u1u1): [ISP]
 Link 22 (cscotun0):

where [VPN connection] stands for the address that is associated with VPN.

After stopping VPN:

 $ resolvectl dns
 Global: [Same as {*}]
 Link 2 (enp57s0u2u1u1): [Same as {**}]

 $ resolvectl domain
 Global: [VPN connection domainname] [ISP]
 Link 2 (enp57s0u2u1u1): [ISP]

After $ sudo systemctl restart systemd-resolved.service

$ resolvectl dns
 Global:
 Link 2 (enp57s0u2u1u1): [Same as {**}]

$ resolvectl domain
 Global:
 Link 2 (enp57s0u2u1u1): [ISP]

Seems to me there is something "sticky" about the VPN connection?

Many thanks for your suggestions and help!

Best wishes,
Ranjan
___
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: F38: systemd-resolved.service oddity

[Ranjan Maitra]

Thanks very much! An mentioned in the original post, I am on a fully updated 
F38. I update nightly.

$ uname -a Linux 6.4.15-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep  7 
00:25:01 UTC 2023 x86_64 GNU/Linux


Many thanks and best wishes,
Ranjan

On Wed Sep27'23 10:24:00AM, Joe Zeff wrote:
> From: Joe Zeff 
> Date: Wed, 27 Sep 2023 10:24:00 -0600
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 09/27/2023 10:14 AM, Ranjan Maitra wrote:
> >  From the past week, I have had an issue in that after several hours, some 
> > particular sites become inaccessible to me, and can only be accessed if I 
> > use restart using sudo systemctl restart systemd-resolved.service
>
> Before any of us can help you, we need a little more information: what
> version of Fedora are you using and how long since you last updated your
> system?
___
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

F38: systemd-resolved.service oddity

[Ranjan Maitra]

Dear friends,

From the past week, I have had an issue in that after several hours, some 
particular sites become inaccessible to me, and can only be accessed if I use 
restart using sudo systemctl restart systemd-resolved.service

What particular  issues cause this? Why did it start a week ago, and has become 
quite reliable in its annoyance? (I have to say that when I can no longer 
access this site, I am no longer on Cisco SecureClient VPN, which is also one 
of the sites which can not be accessed with Cisco SecureClient VPN without 
restarting systemd-resolved.service, and the site is my worksite domain).

Happy to file bug reports, and to test different things. I am on a fully 
updated F38.

Many thanks and best wishes,
Ranjan
___
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: OT but F38: Cisco SecureClient VPN suddenly stops connecting since this morning

[Ranjan Maitra]

On Fri Sep15'23 04:10:55PM, Ranjan Maitra wrote:
> From: Ranjan Maitra 
> Date: Fri, 15 Sep 2023 16:10:55 -0500
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: OT but F38: Cisco SecureClient VPN suddenly stops connecting
>  since this morning
>
> On Fri Sep15'23 04:03:16PM, Ranjan Maitra wrote:
> > From: Ranjan Maitra 
> > Date: Fri, 15 Sep 2023 16:03:16 -0500
> > To: Community Support for Fedora Users 
> > Reply-To: Community support for Fedora users 
> > Subject: OT but F38: Cisco SecureClient VPN suddenly stops connecting since
> >  this morning
> >
> > Hi,
> >
> > I have a strange problem, after last night's updates on F38. I am not 
> > actually sure that that is the cause, but I can no longer get Cisco's VPN 
> > to work. (I have to use Cisco's SecureClient because of the more "secure" 
> > 2-factor-authentication required to connect: before that, I used 
> > OpenConnect for a long time, and did not have a problem till I was forced 
> > to move to Cisco's version two years ago. I have till date not had any 
> > issue with Cisco either.)
> >
> > But that last statement in parenthesis only holds till last night. From 
> > this morning, I am unable to connect to Cisco's VPN. After logging in, and 
> > going through 2FA, all of which are successful, I get that:
> >
> > "Cisco Secure Client was not able to establish a connection to the 
> > specified secure gateway. Please try connecting again." 
> >
> > which is on top of:
> >
> > "The certificate on the secure gateway is invalid. A VPN connection will 
> > not be established." 
> >
> >
> > Things I have tried:
> >
> > 1) Trying on a different machine, with an up to date, F38, I have the same 
> > issue.
> >
> > 2) Using my wife's F37 machine (possibly not very up to date) and I am able 
> > to connect on VPN using the same account, so the issue seems to be with me 
> > and F38.
> >
> > 3) Back to my F38 machine, I looked at /var/log/report as the connection 
> > was happening, and got the following, and was wondering if it shows 
> > anything that is fixable.
> >
>
> After another reject: this time, the file is probably just over 60.001 KB 
> because of added header, etc information, I put this file at:
>
> https://paste.centos.org/view/6e50432b
>

Downgrading glibc (from 2.37-5 to 2.37-1) gets around the problem (in that I 
can log on). So, is this is a bug or an enhanced feature that Cisco or the 
people who control my certificate have not gotten around to?

Best wishes,
Ranjan
___
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: OT but F38: Cisco SecureClient VPN suddenly stops connecting since this morning

[Ranjan Maitra]

On Fri Sep15'23 05:24:55PM, Tom Horsley wrote:
> From: Tom Horsley 
> Date: Fri, 15 Sep 2023 17:24:55 -0400
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: OT but F38: Cisco SecureClient VPN suddenly stops connecting
>  since this morning
>
> On Fri, 15 Sep 2023 16:10:55 -0500
> Ranjan Maitra wrote:
>
> > > "The certificate on the secure gateway is invalid. A VPN connection will 
> > > not be established." 
>
> That usually means the server at the other end has an expired certificate.
> That seems to happen quite frequently because the previous sysadmin
> didn't set up any kind of reminder that the new admin would need to
> renew the certs when they expire. (Or didn't set up a reminder for himself).


Thanks very much! That is what I was originally thinking, also. But how is it 
that the same account works when I use the less up to date F37 machine (my 
wife's, who is now going to be even less convinced about being up to date)?

Many thanks,
Ranjan
___
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: OT but F38: Cisco SecureClient VPN suddenly stops connecting since this morning

[Ranjan Maitra]

On Fri Sep15'23 04:03:16PM, Ranjan Maitra wrote:
> From: Ranjan Maitra 
> Date: Fri, 15 Sep 2023 16:03:16 -0500
> To: Community Support for Fedora Users 
> Reply-To: Community support for Fedora users 
> Subject: OT but F38: Cisco SecureClient VPN suddenly stops connecting since
>  this morning
>
> Hi,
>
> I have a strange problem, after last night's updates on F38. I am not 
> actually sure that that is the cause, but I can no longer get Cisco's VPN to 
> work. (I have to use Cisco's SecureClient because of the more "secure" 
> 2-factor-authentication required to connect: before that, I used OpenConnect 
> for a long time, and did not have a problem till I was forced to move to 
> Cisco's version two years ago. I have till date not had any issue with Cisco 
> either.)
>
> But that last statement in parenthesis only holds till last night. From this 
> morning, I am unable to connect to Cisco's VPN. After logging in, and going 
> through 2FA, all of which are successful, I get that:
>
> "Cisco Secure Client was not able to establish a connection to the specified 
> secure gateway. Please try connecting again." 
>
> which is on top of:
>
> "The certificate on the secure gateway is invalid. A VPN connection will not 
> be established." 
>
>
> Things I have tried:
>
> 1) Trying on a different machine, with an up to date, F38, I have the same 
> issue.
>
> 2) Using my wife's F37 machine (possibly not very up to date) and I am able 
> to connect on VPN using the same account, so the issue seems to be with me 
> and F38.
>
> 3) Back to my F38 machine, I looked at /var/log/report as the connection was 
> happening, and got the following, and was wondering if it shows anything that 
> is fixable.
>

After another reject: this time, the file is probably just over 60.001 KB 
because of added header, etc information, I put this file at:

https://paste.centos.org/view/6e50432b

Many thanks for any suggestions, and best wishes,

Ranjan
___
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

OT but F38: Cisco SecureClient VPN suddenly stops connecting since this morning

[Ranjan Maitra]

Hi,

I have a strange problem, after last night's updates on F38. I am not actually 
sure that that is the cause, but I can no longer get Cisco's VPN to work. (I 
have to use Cisco's SecureClient because of the more "secure" 
2-factor-authentication required to connect: before that, I used OpenConnect 
for a long time, and did not have a problem till I was forced to move to 
Cisco's version two years ago. I have till date not had any issue with Cisco 
either.)

But that last statement in parenthesis only holds till last night. From this 
morning, I am unable to connect to Cisco's VPN. After logging in, and going 
through 2FA, all of which are successful, I get that:

"Cisco Secure Client was not able to establish a connection to the specified 
secure gateway. Please try connecting again." 

which is on top of:

"The certificate on the secure gateway is invalid. A VPN connection will not be 
established." 


Things I have tried:

1) Trying on a different machine, with an up to date, F38, I have the same 
issue.

2) Using my wife's F37 machine (possibly not very up to date) and I am able to 
connect on VPN using the same account, so the issue seems to be with me and F38.

3) Back to my F38 machine, I looked at /var/log/report as the connection was 
happening, and got the following, and was wondering if it shows anything that 
is fixable.

However turning this file in pegs the message at 62KB (which is over the limit 
of 60KB, that I was not aware of and causes the post to be rejected) so I will 
send that in the next email.

In the meantime, if you have some ideas on what is going on, please let me know.

Many thanks and best wishes,
Ranjan
___
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: xv on F38?

[Ranjan Maitra]

Ah, it is on non-free. Did not realize that.

Thanks!
Ranjan

On Sat Aug26'23 05:24:20PM, Patrick O'Callaghan wrote:
> From: Patrick O'Callaghan 
> Date: Sat, 26 Aug 2023 17:24:20 +0100
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: xv on F38?
>
> On Sat, 2023-08-26 at 11:12 -0500, Ranjan Maitra wrote:
> > Hi,
> >
> > I have not used xv on F38 for a few months, but now noticed that I
> > can not find it in the F38 repos. Is it dropped?
>
> $ dnf info xv
> Name : xv
> Version  : 4.1.1
> Release  : 1.fc38
> Architecture : x86_64
> Size : 607 k
> Source   : xv-4.1.1-1.fc38.src.rpm
> Repository   : rpmfusion-nonfree-updates
> Summary  : Interactive image display program for X
> URL  : https://github.com/jasper-software/xv
> License  : Shareware
> Description  : This is the famous 'xv' by John Bradley. It is shareware, but 
> we ship
>  : it with the permission of the authors. It is a graphics viewer 
> for
>  : many file types, including gif, jpg, tiff, xwd, etc. It also 
> has
>  : manipulation features such as cropping, expanding, etc. 
> Patched to
>  : include flmask, a popular feature in Japan.
>
> poc
> ___
> 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

xv on F38?

[Ranjan Maitra]

Hi,

I have not used xv on F38 for a few months, but now noticed that I can not find 
it in the F38 repos. Is it dropped?

Many thanks,
Ranjan
___
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: Last kernel update leads to emergency mode

[Ranjan Maitra]

On Tue Aug22'23 04:19:23PM, Paul Smith wrote:
> From: Paul Smith 
> Date: Tue, 22 Aug 2023 16:19:23 +0100
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: Last kernel update leads to emergency mode
>
> On Tue, Aug 22, 2023 at 2:26 PM Ranjan Maitra  wrote:
> >
> > > > > Are other also experience that with the new kernel:
> > > > >
> > > > > 6.4.10-200.fc38.x86_64
> > > > >
> > > > > I have already file a bug but no answer:
> > > > >
> > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838
> > > >
> > > > I didn't have any problems, but I updated to 6.4.11 this morning so
> > > > maybe try that.
> > >
> > > Thanks, Patrick: My bad: the problematic kernel is:
> > >
> > > kernel-6.4.11-200.fc38.x86_64
> >
> > Can you boot into the older kernel?
>
> Yes, Ranjan, I can boot into an older kernel. Thanks!
>

When such a thing very rarely has happened to me, it usually means that grub 
did not  finish installing the new kernel update. Try reinstalling perhaps? Or 
rebuild grub?

Ranjan
___
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: Last kernel update leads to emergency mode

[Ranjan Maitra]

On Mon Aug21'23 05:13:34PM, Paul Smith wrote:
> From: Paul Smith 
> Date: Mon, 21 Aug 2023 17:13:34 +0100
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: Last kernel update leads to emergency mode
>
> On Mon, Aug 21, 2023 at 5:10 PM Patrick O'Callaghan
>  wrote:
> >
> > > Are other also experience that with the new kernel:
> > >
> > > 6.4.10-200.fc38.x86_64
> > >
> > > I have already file a bug but no answer:
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838
> >
> > I didn't have any problems, but I updated to 6.4.11 this morning so
> > maybe try that.
>
> Thanks, Patrick: My bad: the problematic kernel is:
>
> kernel-6.4.11-200.fc38.x86_64
>

Can you boot into the older kernel?

Ranjan
___
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: slowness with kernel 6.4.10 and software raid

[Ranjan Maitra]

On Fri Aug18'23 01:21:01PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Fri, 18 Aug 2023 13:21:01 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: slowness with kernel 6.4.10 and software raid
>
> On 8/18/23 13:15, Ranjan Maitra wrote:
> > Thanks, so are there two drives that are bad? Sorry, I am confused. It is 
> > likely no longer in warranty: the one with /home is new (I think) and also 
> > the /mnt/backup (which is a rsync-based backup I do so as to actually be 
> > able to see these files, and also as a more reliable backup that i can 
> > actually see). Outside this, I have a / drive  that is a smaller SSD. I 
> > also used to have that raided, but that other / drive died and I never got 
> > to replacing it.
> >
> > So, my question is that is it only the raid drive /dev/sda that is bad, or 
> > is there something else that you can see based on the report?
>
> The logs only indicate that sda is bad.  There are no errors for sdc.


Thanks very much, Sam!

Best wishes,
Ranjan

> ___
> 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: slowness with kernel 6.4.10 and software raid

[Ranjan Maitra]

Thanks, so are there two drives that are bad? Sorry, I am confused. It is 
likely no longer in warranty: the one with /home is new (I think) and also the 
/mnt/backup (which is a rsync-based backup I do so as to actually be able to 
see these files, and also as a more reliable backup that i can actually see). 
Outside this, I have a / drive  that is a smaller SSD. I also used to have that 
raided, but that other / drive died and I never got to replacing it.

So, my question is that is it only the raid drive /dev/sda that is bad, or is 
there something else that you can see based on the report?

Many thanks, and best wishes,
Ranjan


On Fri Aug18'23 02:58:30PM, Roger Heflin wrote:
> From: Roger Heflin 
> Date: Fri, 18 Aug 2023 14:58:30 -0500
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: slowness with kernel 6.4.10 and software raid
>
> ok.  You have around 4000 sectors that are bad and are reallocated.
>
> You have around 1000 that are offline uncorrectable (reads failed).
>
> And you have a desktop drive that has a bad sector timeout of who
> knows exactly what.   I would guess at least 30 seconds, it could be
> higher, but it must be lower than the scsi timeout fo the device.
>
> Given the power on hours the disk is out of warranty (I think).  If
> the disk was in warranty you could get the disk vendor to replace it.
>
> So whatever that timeout is when you hit a single bad sector the disk
> is going to keep re-reading it for that timeout and then report that
> sector cannot be read and mdraid will then read it from the other
> mirror and re-write it.
>
> This disk could eventually failed to read each sector and mdraid could
> re-write them and that may fix it.  Or it could fix some of them on
> this pass, and some on the next pass, and never fix all of them so sda
> simply sucks.
>
> Best idea would be to buy a new disk, but this time do not buy a
> desktop drive nor buy a SMR drive.There is a webpage someplaec
> that lists which disks are not SMR disks, and other webpages list what
> disks have a settable timeout (WD Red Plus and/or Seagate Ironwolf,
> and likely others).
>
> Likely the disks will be classified as enterprise and/or NAS disks,
> but whatever you look at make sure to check the vendors list to see if
> the disk is SMR or not.  Note WD Red is SMR, WD Red Plus is not SMR.
> And SMR sometimes does not play nice with raid.
>
> On Fri, Aug 18, 2023 at 2:05 PM Ranjan Maitra  wrote:
> >
> > On Fri Aug18'23 01:39:08PM, Roger Heflin wrote:
> > > From: Roger Heflin 
> > > Date: Fri, 18 Aug 2023 13:39:08 -0500
> > > To: Community support for Fedora users 
> > > Reply-To: Community support for Fedora users 
> > > 
> > > Subject: Re: slowness with kernel 6.4.10 and software raid
> > >
> > > The above makes it very clear what is happening.   What kind of disks
> > > are these?  And did you set the scterc timeout?  You can see it via
> > > smartctl -l scterc /dev/sda   and then repeat on the other disk.
> > >
> > > Setting the timeout as low as you can will improve this situation
> > > some, but it appears that sda has a number of bad sectors on it.
> > >
> > > a full output of "smartclt --xall /dev/sda" would be useful also to
> > > see how bad it is.
> > >
> > > Short answer is you probably need a new device for sda.
> > >
> >
> > Thanks!
> >
> > I tried:
> >
> > # smartctl -l scterc /dev/sda
> >  smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.4.10-200.fc38.x86_64] (local 
> > build)
> >  Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
> >
> > SCT Error Recovery Control command not supported
> >
> > # smartctl --xall /dev/sda
> >
> >   smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.4.10-200.fc38.x86_64] 
> > (local build)
> >   Copyright (C) 2002-23, Bruce Allen, Christian Franke, 
> > www.smartmontools.org
> >
> >   === START OF INFORMATION SECTION ===
> >   Model Family: Seagate Barracuda 7200.14 (AF)
> >   Device Model: ST2000DM001-1ER164
> >   Serial Number:Z4Z5F3LE
> >   LU WWN Device Id: 5 000c50 091167f04
> >   Firmware Version: CC27
> >   User Capacity:2,000,398,934,016 bytes [2.00 TB]
> >   Sector Sizes: 512 bytes logical, 4096 bytes physical
> >   Rotation Rate:7200 rpm
> >   Form Factor:  3.5 inches
> >   Device is:In smartctl database 7.3/5528
> >   ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
> >   SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
> &

Re: slowness with kernel 6.4.10 and software raid

[Ranjan Maitra]

ef 00 10 00 02 00 00 00 00 00 00 a0 00 16d+06:35:35.532  SET FEATURES 
[Enable SATA feature]

  Error 378 [17] occurred at disk power-on lifetime: 34042 hours (1418 days + 
10 hours)
When the command that caused the error occurred, the device was active or 
idle.

After command completion occurred, registers were:
ER -- ST COUNT  LBA_48  LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 53 00 00 00 00 a3 12 b8 90 00 00  Error: UNC at LBA = 0xa312b890 = 
2735913104

Commands leading to the command that caused the error were:
CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- --  ---  

60 00 00 00 08 00 00 a3 12 b8 90 40 00 16d+06:35:31.406  READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 12 b8 88 40 00 16d+06:35:31.406  READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 12 b8 80 40 00 16d+06:35:31.405  READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 12 b8 78 40 00 16d+06:35:31.398  READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 12 b8 70 40 00 16d+06:35:31.397  READ FPDMA QUEUED

  Error 377 [16] occurred at disk power-on lifetime: 34042 hours (1418 days + 
10 hours)
When the command that caused the error occurred, the device was active or 
idle.

After command completion occurred, registers were:
ER -- ST COUNT  LBA_48  LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 53 00 00 00 00 a3 12 b8 70 00 00  Error: UNC at LBA = 0xa312b870 = 
2735913072

Commands leading to the command that caused the error were:
CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- --  ---  

60 00 00 00 08 00 00 a3 12 b8 70 40 00 16d+06:35:27.414  READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 12 b8 68 40 00 16d+06:35:27.413  READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 12 b8 60 40 00 16d+06:35:27.402  READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 12 b8 58 40 00 16d+06:35:27.401  READ FPDMA QUEUED
61 00 00 00 08 00 00 a3 12 b8 58 40 00 16d+06:35:27.401  WRITE FPDMA QUEUED

  SMART Extended Self-test Log Version: 1 (1 sectors)
  Num  Test_DescriptionStatus  Remaining  LifeTime(hours)  
LBA_of_first_error
  # 1  Short offline   Completed: read failure   90% 29204 
771754056
  # 2  Short offline   Completed without error   00%19 -
  # 3  Short offline   Completed without error   00% 0 -

  SMART Selective self-test log data structure revision number 1
   SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
  100  Not_testing
  200  Not_testing
  300  Not_testing
  400  Not_testing
  500  Not_testing
  Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
  If Selective self-test is pending on power-up, resume after 0 minute delay.

  SCT Status Version:  3
  SCT Version (vendor specific):   522 (0x020a)
  Device State:Active (0)
  Current Temperature:37 Celsius
  Power Cycle Min/Max Temperature: 37/41 Celsius
  LifetimeMin/Max Temperature: 18/45 Celsius
  Under/Over Temperature Limit Count:   0/0

  SCT Data Table command not supported

  SCT Error Recovery Control command not supported

  Device Statistics (GP/SMART Log 0x04) not supported

  Pending Defects log (GP Log 0x0c) not supported

  SATA Phy Event Counters (GP Log 0x11)
  ID  Size Value  Description
  0x000a  2  102  Device-to-host register FISes sent due to a COMRESET
  0x0001  20  Command failed due to ICRC error
  0x0003  20  R_ERR response for device-to-host data FIS
  0x0004  20  R_ERR response for host-to-device data FIS
  0x0006  20  R_ERR response for device-to-host non-data FIS
  0x0007  20  R_ERR response for host-to-device non-data FIS

Many thanks,
Ranjan


> On Fri, Aug 18, 2023 at 1:30 PM Ranjan Maitra  wrote:
> >
> > Thanks, Roger!
> >
> >
> > On Fri Aug18'23 12:23:23PM, Roger Heflin wrote:
> > > From: Roger Heflin 
> > > Date: Fri, 18 Aug 2023 12:23:23 -0500
> > > To: Community support for Fedora users 
> > > Reply-To: Community support for Fedora users 
> > > 
> > > Subject: Re: slowness with kernel 6.4.10 and software raid
> > >
> > > Is it moving at all or just stopped?  If just stopped it appears that
> > > md126 is using external:/md127 for something and md127 looks wrong
> > > (both disks are spare) but I don't know in this external case what
> > > md127 should look like.
> >
> > It is moving, slowly. It is a 2 TB drive, but this is weird.
> >
> > &g

Re: slowness with kernel 6.4.10 and software raid

[Ranjan Maitra]

vice - MD 
Metadata Monitor on /dev/md127...
  Aug 16 14:21:20 localhost systemd[1]: Started mdmon@md127.service - MD 
Metadata Monitor on /dev/md127.
  Aug 16 14:21:20 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=mdmon@md127 
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? 
res=success'

>
> Maybe also if you have a prior good reboot in messages file include
> that and see what happened differently between the 2.

Yeah, I do not know where to find this. I looked into /var/log/messages, but it 
looks like it starts on August 13, which was a surprise to me, and the last 
non-responsive instance for me was last week (August 10, I think, when I booted 
into the 6.4 kernel). I did reboot in frustration on August 16.

Thanks,
Ranjan


>
> On Fri, Aug 18, 2023 at 7:46 AM Ranjan Maitra  wrote:
> >
> > On Thu Aug17'23 10:37:29PM, Samuel Sieb wrote:
> > > From: Samuel Sieb 
> > > Date: Thu, 17 Aug 2023 22:37:29 -0700
> > > To: users@lists.fedoraproject.org
> > > Reply-To: Community support for Fedora users 
> > > 
> > > Subject: Re: slowness with kernel 6.4.10 and software raid
> > >
> > > On 8/17/23 21:38, Ranjan Maitra wrote:
> > > > $ cat /proc/mdstat
> > > >   Personalities : [raid1]
> > > >   md126 : active raid1 sda[1] sdc[0]
> > > > 1855870976 blocks super external:/md127/0 [2/2] [UU]
> > > > [=>...]  check =  8.8% (165001216/1855870976) 
> > > > finish=45465.2min speed=619K/sec
> > > >
> > > >   md127 : inactive sda[1](S) sdc[0](S)
> > > > 10402 blocks super external:imsm
> > > >
> > > >   unused devices: 
> > > >
> > > > I am not sure what it is doing, and I am a bit concerned that this will 
> > > > go on at this rate for about 20 days. No knowing what will happen after 
> > > > that, and also if this problem will recur with another reboot.
> > >
> > > After a certain amount of time, mdraid will do a verification of the data
> > > where it scans the entire array.  If you reboot, it will continue from 
> > > where
> > > it left off.  But that is *really* slow, so you should find out what's 
> > > going
> > > on there.
> >
> > Yes, I know, just not sure what to do. Thanks very much!
> >
> > Any suggestion is appreciated!
> >
> > Best wishes,
> > Ranjan
> > ___
> > 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
___
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: slowness with kernel 6.4.10 and software raid

[Ranjan Maitra]

On Thu Aug17'23 10:37:29PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Thu, 17 Aug 2023 22:37:29 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: slowness with kernel 6.4.10 and software raid
>
> On 8/17/23 21:38, Ranjan Maitra wrote:
> > $ cat /proc/mdstat
> >   Personalities : [raid1]
> >   md126 : active raid1 sda[1] sdc[0]
> > 1855870976 blocks super external:/md127/0 [2/2] [UU]
> > [=>...]  check =  8.8% (165001216/1855870976) 
> > finish=45465.2min speed=619K/sec
> >
> >   md127 : inactive sda[1](S) sdc[0](S)
> > 10402 blocks super external:imsm
> >
> >   unused devices: 
> >
> > I am not sure what it is doing, and I am a bit concerned that this will go 
> > on at this rate for about 20 days. No knowing what will happen after that, 
> > and also if this problem will recur with another reboot.
>
> After a certain amount of time, mdraid will do a verification of the data
> where it scans the entire array.  If you reboot, it will continue from where
> it left off.  But that is *really* slow, so you should find out what's going
> on there.

Yes, I know, just not sure what to do. Thanks very much!

Any suggestion is appreciated!

Best wishes,
Ranjan
___
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

slowness with kernel 6.4.10 and software raid

[Ranjan Maitra]

Hi,

I am at a bit of a loss. After about two months, I decided to reboot a few days 
ago, and rebooted into 6.4.10  kernel. Everything came up, but the machine is 
very unresponsive, and practically unusable when I am at it. It is better when 
working on it remote, but it is still slower.

I was going to reboot but I came up with the following:

 $ reboot
 Operation inhibited by "Disk Manager" (PID 1044 "udisksd", user root), reason 
is "Unknown (mdraid-check-job)".
 Please retry operation after closing inhibitors and logging out other users.
Alternatively, ignore inhibitors and users with 'systemctl reboot -i'.

This pointed me to the possibility of the issue being raid. So, I looked at

$ cat /proc/mdstat
 Personalities : [raid1]
 md126 : active raid1 sda[1] sdc[0]
   1855870976 blocks super external:/md127/0 [2/2] [UU]
   [=>...]  check =  8.8% (165001216/1855870976) 
finish=45465.2min speed=619K/sec

 md127 : inactive sda[1](S) sdc[0](S)
   10402 blocks super external:imsm

 unused devices: 

I am not sure what it is doing, and I am a bit concerned that this will go on 
at this rate for about 20 days. No knowing what will happen after that, and 
also if this problem will recur with another reboot.

The machine is a 10 core, 20-thread Dell T5810. It is running a fully updated 
Fedora 38 installation.

Any help/suggestions on what to do?

Many thanks and best wishes,
Ranjan
___
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: More hibernation mystery

[Ranjan Maitra]

My apologies for this, but this is how we go about hibernating on a new system 
now? In the past, from F34 or before, which is why I last set up this machine 
and have upgraded it using dnf ever since, it was pretty much automatic. Before 
that, some more work was needed (for a while):


sudo vi /etc/default/grub

add --> resume=UUID="" <-- to the line GRUB_CMDLINE_LINUX=

where the UUID is obtained using blkid.

then

sudo bash -x grub2-mkconfig

# # for efi-based systems: #

sudo bash -x grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

In either case, systemctl hibernate is enough to set it to hibernate.

But all this was not much, compared to what has been described on the thread. 
What changed? I am just trying to understand this in advance, as I was thikning 
of doing a clean install just to get rid of crud that inevitably creeps into my 
system. Having reliable hibernate (and this has been so for me all these years) 
is very important to me.

In the past, I have had a separate physical partition for swap. Nowadays, I 
think that there is something else (dynamic swap) but I am not sure if that 
matters.

Any enlightenment?

Many thanks and best wishes,
Ranjan



On Mon Aug14'23 10:49:28AM, Patrick O'Callaghan wrote:
> From: Patrick O'Callaghan 
> Date: Mon, 14 Aug 2023 10:49:28 +0100
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: More hibernation mystery
>
> On Mon, 2023-08-14 at 08:05 +0200, francis.montag...@inria.fr wrote:
> > On Sun, 13 Aug 2023 22:12:23 +0100 Patrick O'Callaghan wrote:
> >
> > > On Sun, 2023-08-13 at 18:49 +0200,
> > > francis.montag...@inria.fr wrote:
> > > > ExecStart=/bin/bash -c '/usr/sbin/swapon /SWAP/swapfile &&
> > > > /usr/sbin/swapoff /dev/zram0'
> >
> > > I'll do that, but I don't understand why it sometimes works and
> > > sometimes doesn't.
> >
> > The journal when it succeeds shows that /SWAP/swapfile was activated.
> > That may
> > be due to hibernate-resume.service previously failed or was not
> > called.
>
> I don't think so but I'd need to think it through.
>
>
> > In addition swapon fails when the swapfile is already activated. A
> > better
> > hibernate-preparation.service would be:
> >
> >   ExecStart=/bin/bash -c ' \
> >   if ! swapon --show=NAME --noheadings | grep -q /SWAP/swapfile;
> > then \
> >   swapon /SWAP/swapfile || exit; \
> >   fi; \
> >   swapoff /dev/zram0; \
> >   # Ignores the exit code of swapoff.
> >   exit 0; \
> >   '
> >
>
> I'll add that as a defensive measure.
>
>
> Thanks again.
>
> poc
> ___
> 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: youtube-dl error (F37 and F38)

[Ranjan Maitra]

On Thu Jul13'23 09:52:47PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Thu, 13 Jul 2023 21:52:47 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: youtube-dl error (F37 and F38)
>
> On 7/13/23 21:42, Ranjan Maitra wrote:
> > I have been having this error using youtube-dl for a while. Here is what I 
> > get:
> > [...]
> > File 
> > "/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 
> > 1012, in _search_regex
> >   raise RegexNotFoundError('Unable to extract %s' % _name)
> >   youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; 
> > please report this issue on https://yt-dl.org/bug . Make sure you are using 
> > the latest version; see  https://yt-dl.org/update  on how to update. Be 
> > sure to call youtube-dl with the --verbose flag and include its complete 
> > output.
> >
> >
> > Strangely, works fine with mpv, which I understand uses youtube-dl.
>
> Use "yt-dlp" instead, which is what mpv uses now as well.

Thanks very much! Was not aware of this. How do you know so much?:-) yt-dlp 
Works for me.

Thanks again!

Best wishes,
Ranjan
___
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

youtube-dl error (F37 and F38)

[Ranjan Maitra]

Hi,

I have been having this error using youtube-dl for a while. Here is what I get:

  $  youtube-dl --verbose https://www.youtube.com/watch?v=SzH7_gGAM3Y
 [debug] System config: ['--prefer-free-formats']
 [debug] User config: []
 [debug] Custom config: []
 [debug] Command-line args: ['--verbose', 
'https://www.youtube.com/watch?v=SzH7_gGAM3Y']
 [debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
 [debug] youtube-dl version 2021.12.17
 [debug] Python version 3.11.4 (CPython) - 
Linux-6.3.8-200.fc38.x86_64-x86_64-with-glibc2.37
 [debug] exe versions: ffmpeg 6.0, ffprobe 6.0
 [debug] Proxy map: {}
 [youtube] SzH7_gGAM3Y: Downloading webpage
 ERROR: Unable to extract uploader id; please report this issue on 
https://yt-dl.org/bug . Make sure you are using the latest version; see  
https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the 
--verbose flag and include its complete output.
 Traceback (most recent call last):
   File "/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 814, 
in wrapper
 return func(self, *args, **kwargs)
^^^
   File "/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 835, 
in __extract_info
 ie_result = ie.extract(url)
 ^^^
   File "/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", 
line 534, in extract
 ie_result = self._real_extract(url)
 ^^^
   File "/usr/lib/python3.11/site-packages/youtube_dl/extractor/youtube.py", 
line 1794, in _real_extract
 'uploader_id': 

Re: kernel watchdog BUG

[Ranjan Maitra]

On Sun May28'23 12:41:54PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Sun, 28 May 2023 12:41:54 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: kernel watchdog BUG
>
> On 5/28/23 09:15, stan via users wrote:
> > On Sun, 28 May 2023 09:52:04 -0500
> > Ranjan Maitra  wrote:
> > > I rebooted in the good old ways of some other OSs, and the problem
> > > has not reared again for now. I did look at /var/log/messages but
> > > found nothing on kernel lockup. Are these some other log files I
> > > should be looking at.
> >
> > journalctl is the official message repository now.  I like to use
> > journalctl -r
> > because that reverses it, so I am searching from now into the past.
> > You could try a
> > /soft lockup
> > and see if you get any hits.
>
> You'll want to add "-b -1" as well, so you start with the logs from the
> previous boot, not the current one.
>
> "journalctl -b -1 -r"


Thanks! It is possible I do not have this set up because I get:

$ sudo journalctl -b -1 -r /soft lockup
 Specifying boot ID or boot offset has no effect, no persistent journal was 
found.

Best wishes,
Ranjan
___
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: kernel watchdog BUG

[Ranjan Maitra]

On Sat May27'23 07:40:29PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Sat, 27 May 2023 19:40:29 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: kernel watchdog BUG
>
> On 5/27/23 17:48, Ranjan Maitra wrote:
> > Came back to my screen to the following:
> >
> > Message from syslogd@localhost at May 27 19:19:48 ...
> >   kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 134s! [cifsd:21659]
> >
> > What is this issue?
>
> Check the logs, there should be more details.

I rebooted in the good old ways of some other OSs, and the problem has not 
reared again for now. I did look at /var/log/messages but found nothing on 
kernel lockup. Are these some other log files I should be looking at.

Because there is a cifsd tag at the end, I had earlier mounted a drive using 
cifs, but had unmounted it quite some time before this problem showed up. One 
other thing this kernel soft lockup did was to make some commands unresponsive: 
commands such as quitting from zathura, after sending email using mutt, etc. 
That is why I decided to reboot. So far so good. But I would be willing to look 
at logfiles to get an idea.

Thanks again!

Best wishes,
Ranjan



> ___
> 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

kernel watchdog BUG

[Ranjan Maitra]

Came back to my screen to the following:

Message from syslogd@localhost at May 27 19:19:48 ...
 kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 134s! [cifsd:21659]

What is this issue?

I am running Linux 6.2.15-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 
15:56:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Many thanks and best wishes,
Ranjan
___
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: F37: any suggestions on this WebEx error on F37?

[Ranjan Maitra]

On Fri May26'23 08:00:37PM, Ranjan Maitra wrote:
> From: Ranjan Maitra 
> Date: Fri, 26 May 2023 20:00:37 -0500
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: F37: any suggestions on this WebEx error on F37?
>
> On Fri May26'23 06:09:33PM, Thomas Cameron wrote:
> > From: Thomas Cameron 
> > Date: Fri, 26 May 2023 18:09:33 -0500
> > To: users@lists.fedoraproject.org
> > Reply-To: Community support for Fedora users 
> > Subject: Re: F37: any suggestions on this WebEx error on F37?
> >
> > On 5/26/23 13:25, Ranjan Maitra wrote:
> > > Thanks very much! It more or less put me on the right track. After a 
> > > perceived clean exit of WebEx:
> > >
> > > $ ps ux
> > >   localusr  5546 25.8  3.6 6429840 581604 ?  Sl   13:16   0:07 
> > > /opt/Webex/bin/CiscoCollabHost /opt/Webex/lib/ libWebexAppLoader.so /Start
> > >   localusr  5551  0.0  0.3 504684 56320 ?S13:16   0:00 
> > > /opt/Webex/bin/CiscoCollabHostCef --type=zygote --no-zygote-sandbox 
> > > --log-severity=disable --lang=en-US --user-data-dir=/home/localusr/.local/
> > >   localusr  5552  0.0  0.3 504676 56448 ?S13:16   0:00 
> > > /opt/Webex/bin/CiscoCollabHostCef --type=zygote --log-severity=disable 
> > > --lang=en-US --user-data-dir=/home/localusr/.local/share/Webex --log-fi
> > >   localusr  5554  0.0  0.0 504700 14364 ?S13:16   0:00 
> > > /opt/Webex/bin/CiscoCollabHostCef --type=zygote --log-severity=disable 
> > > --lang=en-US --user-data-dir=/home/localusr/.local/share/Webex --log-fi
> > >   localusr  5708  3.9  0.0  0 0 ?Z13:16   0:01 
> > > [CiscoCollabHost] 
> > >   localusr  5740  0.1  0.3 48315076 60060 ?  Sl   13:16   0:00 
> > > /opt/Webex/lib/../bin/CiscoCollabHostCef --type=renderer 
> > > --log-severity=disable --user-data-dir=/home/localusr/.local/share/Webex 
> > > --first-rend
> > >   localusr  5849  0.6  0.0  0 0 ?Z13:16   0:00 
> > > [CiscoCollabHost] 
> > >
> > > So, now when I do a
> > >
> > > $ killall /opt/Webex/bin/CiscoCollabHost
> > >
> > > the problem goes away temporarily, till the next cycle of WebEx being 
> > > shut down.
> > >
> > > Not quite sure why a clean exit keeps these things hanging or what a LT 
> > > fix could be. Any ideas?
> > >
> > > Many thanks and best wishes,
> > > Ranjan
> > That's almost certainly an issue to bring up with WebEx. If there is any way
> > to send feedback or open a ticket with your WebEx account, please do.
>
> Thanks very much! I will see if I can get a way to do so.
>

As a follow-up, last night's updates and a reboot seem to have addressed the 
issue for now. I will report if this problem rears its head again.

Ranjan
___
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: F37: any suggestions on this WebEx error on F37?

[Ranjan Maitra]

On Fri May26'23 06:09:33PM, Thomas Cameron wrote:
> From: Thomas Cameron 
> Date: Fri, 26 May 2023 18:09:33 -0500
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F37: any suggestions on this WebEx error on F37?
>
> On 5/26/23 13:25, Ranjan Maitra wrote:
> > Thanks very much! It more or less put me on the right track. After a 
> > perceived clean exit of WebEx:
> >
> > $ ps ux
> >   localusr  5546 25.8  3.6 6429840 581604 ?  Sl   13:16   0:07 
> > /opt/Webex/bin/CiscoCollabHost /opt/Webex/lib/ libWebexAppLoader.so /Start
> >   localusr  5551  0.0  0.3 504684 56320 ?S13:16   0:00 
> > /opt/Webex/bin/CiscoCollabHostCef --type=zygote --no-zygote-sandbox 
> > --log-severity=disable --lang=en-US --user-data-dir=/home/localusr/.local/
> >   localusr  5552  0.0  0.3 504676 56448 ?S13:16   0:00 
> > /opt/Webex/bin/CiscoCollabHostCef --type=zygote --log-severity=disable 
> > --lang=en-US --user-data-dir=/home/localusr/.local/share/Webex --log-fi
> >   localusr  5554  0.0  0.0 504700 14364 ?S13:16   0:00 
> > /opt/Webex/bin/CiscoCollabHostCef --type=zygote --log-severity=disable 
> > --lang=en-US --user-data-dir=/home/localusr/.local/share/Webex --log-fi
> >   localusr  5708  3.9  0.0  0 0 ?Z13:16   0:01 
> > [CiscoCollabHost] 
> >   localusr  5740  0.1  0.3 48315076 60060 ?  Sl   13:16   0:00 
> > /opt/Webex/lib/../bin/CiscoCollabHostCef --type=renderer 
> > --log-severity=disable --user-data-dir=/home/localusr/.local/share/Webex 
> > --first-rend
> >   localusr  5849  0.6  0.0  0 0 ?Z13:16   0:00 
> > [CiscoCollabHost] 
> >
> > So, now when I do a
> >
> > $ killall /opt/Webex/bin/CiscoCollabHost
> >
> > the problem goes away temporarily, till the next cycle of WebEx being shut 
> > down.
> >
> > Not quite sure why a clean exit keeps these things hanging or what a LT fix 
> > could be. Any ideas?
> >
> > Many thanks and best wishes,
> > Ranjan
> That's almost certainly an issue to bring up with WebEx. If there is any way
> to send feedback or open a ticket with your WebEx account, please do.

Thanks very much! I will see if I can get a way to do so.

>
> I had to stop using the Linux WebEx client because it's so buggy. Instead, I
> use WebEx through Firefox on Linux. I am a technical trainer, and I teach
> using WebEx, so it's a real bummer. WebEx support has been somewhat helpful,
> but they just don't have Linux experts on staff, so they're sort of hobbled.
>
> Try it through your browser. I used to have issues using WebEx via Chrome,
> but it's been a long time since I tried. It might have cleared up with newer
> versions of Chrome. But Firefox has been very solid, and I am on WebEx 9 or
> more hours/day, 3-5 days/week.

I have not had any problems with WebEx on Fedora ever since they released the 
rpm (and I came to know of it, which was a good few months after that). It does 
have fewer features than the Windoze version, I am told, but I have not had a 
problem with it, even now.

The client I have had lots of issues with, with regard to audio, is teams but 
that is another story.

Well, thanks again!

Best wishes,
Ranjan
___
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: F37: any suggestions on this WebEx error on F37?

[Ranjan Maitra]

On Fri May26'23 01:45:49PM, Tom Horsley wrote:
> From: Tom Horsley 
> Date: Fri, 26 May 2023 13:45:49 -0400
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F37: any suggestions on this WebEx error on F37?
>
> On Fri, 26 May 2023 12:39:18 -0500
> Ranjan Maitra wrote:
>
> > Any suggestions?
>
> May or may not help, but I'd tend to use ps to get a list of all
> processes running after reboot, then start webex and do another ps
> of all processes to see how much junk webex starts.
>
> Then after exiting webex, see if any of that junk is still running
> and kill -9 anything it left in the background.

Thanks very much! It more or less put me on the right track. After a perceived 
clean exit of WebEx:

$ ps ux
 localusr  5546 25.8  3.6 6429840 581604 ?  Sl   13:16   0:07 
/opt/Webex/bin/CiscoCollabHost /opt/Webex/lib/ libWebexAppLoader.so /Start
 localusr  5551  0.0  0.3 504684 56320 ?S13:16   0:00 
/opt/Webex/bin/CiscoCollabHostCef --type=zygote --no-zygote-sandbox 
--log-severity=disable --lang=en-US --user-data-dir=/home/localusr/.local/
 localusr  5552  0.0  0.3 504676 56448 ?S13:16   0:00 
/opt/Webex/bin/CiscoCollabHostCef --type=zygote --log-severity=disable 
--lang=en-US --user-data-dir=/home/localusr/.local/share/Webex --log-fi
 localusr  5554  0.0  0.0 504700 14364 ?S13:16   0:00 
/opt/Webex/bin/CiscoCollabHostCef --type=zygote --log-severity=disable 
--lang=en-US --user-data-dir=/home/localusr/.local/share/Webex --log-fi
 localusr  5708  3.9  0.0  0 0 ?Z13:16   0:01 
[CiscoCollabHost] 
 localusr  5740  0.1  0.3 48315076 60060 ?  Sl   13:16   0:00 
/opt/Webex/lib/../bin/CiscoCollabHostCef --type=renderer --log-severity=disable 
--user-data-dir=/home/localusr/.local/share/Webex --first-rend
 localusr  5849  0.6  0.0  0 0 ?Z13:16   0:00 
[CiscoCollabHost] 

So, now when I do a

$ killall /opt/Webex/bin/CiscoCollabHost

the problem goes away temporarily, till the next cycle of WebEx being shut down.

Not quite sure why a clean exit keeps these things hanging or what a LT fix 
could be. Any ideas?

Many thanks and best wishes,
Ranjan
___
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

F37: any suggestions on this WebEx error on F37?

[Ranjan Maitra]

Hi,

I use the WebEx client on F37. I have used it for about a couple of years and 
like it a fair bit.

However, of late, WebEx seems to work fine only for the first time after a 
reboot. After a successful shutdown, it never comes up, and instead, I get:

$ /opt/Webex/bin/CiscoCollabHost
  Wx: X error received: type 0, serial 9, error_code 3, request_code 12, 
minor_code 0
  Wx: X error received: type 0, serial 10, error_code 3, request_code 8, 
minor_code 0

It is unclear to me how to fix or troubleshoot this problem. Both dmesg and 
tail -f /var/log/messages indicate no entries when this call is made.

Any suggestions?

Many thanks and best wishes,
Ranjan
___
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

Emacs error in F38

[Ranjan Maitra]

Hi,

Ever since upgrading to F38, I have been getting emacs crashes (Segmentation 
faults) quite frequently, but not always. Specifically, I get the following 
message on the screen when emacs crashes.

Any ideas as to what the remedy is? The version I have is:

emacs-1:28.2-4.fc38.x86_64

Many thanks and best wishes,
Ranjan

Here is the error I get:

 $ Backtrace:
 emacs(emacs_backtrace+0x5c)[0x5889dc]
 emacs(terminate_due_to_signal+0xa1)[0x46533c]
 emacs[0x465cc6]
 emacs[0x6ae2b4]
 /lib64/libc.so.6(+0x3db70)[0x7f992825fb70]
 /lib64/libcairo.so.2(+0x59c8c)[0x7f9930a01c8c]
 /lib64/libcairo.so.2(+0xa8144)[0x7f9930a50144]
 /lib64/libcairo.so.2(+0x64127)[0x7f9930a0c127]
 /lib64/libcairo.so.2(+0x70099)[0x7f9930a18099]
 /lib64/libcairo.so.2(+0x720e9)[0x7f9930a1a0e9]
 /lib64/libcairo.so.2(+0x2be9a)[0x7f99309d3e9a]
 /lib64/libcairo.so.2(cairo_show_glyphs+0x2e)[0x7f9930a2845e]
 emacs[0x68c1cd]
 emacs[0x539ac2]
 emacs[0x53c0b4]
 emacs[0x4c0f14]
 emacs(gui_write_glyphs+0x9c)[0x4ccc9c]
 emacs[0x4757a6]
 emacs[0x47caac]
 emacs[0x47d824]
 emacs(update_frame+0x1ed)[0x47e4cd]
 emacs[0x4aca1f]
 emacs(message3_nolog+0xf6)[0x4a2a86]
 emacs(message3+0x308)[0x4a2f18]
 emacs(Fmessage+0x46)[0x5fa976]
 
/usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/mule-3352613d-82b9a969.eln(F6c6f61642d776974682d636f64652d636f6e76657273696f6e_load_with_code_conversion_0+0x31b)[0x7f992134051b]
 emacs(Ffuncall+0x221)[0x603971]
 emacs(Fload+0x3f9)[0x6305c9]
 emacs(Ffuncall+0x221)[0x603971]
 emacs[0x609b15]
 emacs(Fmapc+0x55)[0x609db5]
 emacs(eval_sub+0x5c8)[0x602d78]
 emacs[0x63001b]
 emacs(Feval_buffer+0x17a)[0x63143a]
 
/usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/mule-3352613d-82b9a969.eln(F6c6f61642d776974682d636f64652d636f6e76657273696f6e_load_with_code_conversion_0+0x27b)[0x7f992134047b]
 emacs(Ffuncall+0x221)[0x603971]
 emacs(Fload+0x3f9)[0x6305c9]
 emacs(Ffuncall+0x221)[0x603971]
 
/usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/startup-bbc6ea72-9c04c94d.eln(F636f6d6d616e642d6c696e65_command_line_0+0x1436)[0x7f99212d4ca6]
 emacs(Ffuncall+0x221)[0x603971]
 
/usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/startup-bbc6ea72-9c04c94d.eln(F6e6f726d616c2d746f702d6c6576656c_normal_top_level_0+0xf6d)[0x7f99212d138d]
 ..
___
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: Dell XPS 13 recommendations (used/refurbished)

[Ranjan Maitra]

Max,

I have a Dell XPS 13 from 2013 and a Dell XPS 13 from 2018. Both bought new 
then. They work fine, and I have been very pleased with them. (In fact, there 
is a small group of graduate students who bought similar models around that 
time based on my experience.) These machines install my remix of Fedora 
efficiently (which means that they would likely have no problems with the 
Fedora official environments), and are part of my stable of workhorses. I 
largely use the earlier 1980x1080 Dell for teaching and presentation,  in 
connection with HDMI projection, and the newer one is the 3840x2160 resolution 
machine I do all sorts of tasks on, including hour-long computations, and 
typing this email. I have had no problems with wifi/network, however i had to 
change the battery for both of them last year (the older Dell that is not part 
of your consideration, needed an after-market battery because Dell no longer 
made that part).

HTH! As you can see, fairly positive recommendations here, but happy to answer 
questions as needed.

Best wishes,
Ranjan

On Sun May07'23 10:09:58AM, Max Pyziur wrote:
> From: Max Pyziur 
> Date: Sun, 7 May 2023 10:09:58 -0400 (EDT)
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Dell XPS 13 recommendations (used/refurbished)
>
>
> Greetings,
>
> I've been using two Dell XPS L322X of early 2013 vintage acquired used since
> late 2017. They work very well, but I'm considering newer versions of this
> laptop.
>
> Specifically, I've seen some Dell XPS 13 9380s of 2019 vintage.
>
> There is some installation help at this webpage:
> https://raynix.info/archives/4232
>
> With the L322X I was able to do some maintenance on my own, specifically
> replacing the SSD from a 125MB to a 1TB and then installing Fedora via USB.
>
> And also installing a new batter and wifi network cards.
>
> I would hope to do the same with a 9380 (or whatever else might be
> recommended).
>
> Any opinions pro/con?
>
> Much thanks as always.
>
> MP
> p...@brama.com
> ___
> 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: bitmap font error on F38

[Ranjan Maitra]

George,

My thanks to you for your detailed descriptions. Here are some findings:

On Wed Apr26'23 11:25:02AM, George N. White III wrote:
> From: "George N. White III" 
> Date: Wed, 26 Apr 2023 11:25:02 -0300
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: bitmap font error on F38
> 
> On Fri, Apr 21, 2023 at 4:01 PM Ranjan Maitra  wrote:
> 
> > Hi,
> >
> > I am also having the following error with pdflatex upon upgrading to F38
> > from F37.
> >
> >  pathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720
> > eurm10
> >  mktexpk: don't know how to create bitmap font for eurm10.
> >  mktexpk: perhaps eurm10 is missing from the map file.
> >  kpathsea: Appending font creation commands to missfont.log.
> >  (see the transcript file for additional information)
> >  !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 720 not found
> >   ==> Fatal error occurred, no output PDF file produced!
> >
> >
> > How do I get around this issue?
> >
> 
> TeX uses fontmap files that should tell pdflatex to use eurm10 font data,
> which includes .PostScript (.pfb format) files.   Sometimes users run
> things that generate fontmap and format files in their user directory and
> which then hides recent changes to the system files.
> 
> OpenType supports upright variants:
> 
> See:
> https://tex.stackexchange.com/questions/145926/upright-greek-font-fitting-to-computer-modern
>

Thanks for this. There is an example there which essentially rewrites the 
upgreek variants. I think that I can make it work for me, but!

> Your example "works for me" in Debian with their TeX Live packages, and on
> Fedora using CTAN TeX Live 2023.  The eurm10 fonts are present, but I
> didn't have
> upgreek.sty.
> 
> This F38 system has:
> 
> Installed Packages
> Name : texlive-amsfonts
> Epoch: 10
> Version  : svn61937
> Release  : 65.fc38
> Architecture : noarch
> Size : 5.9 M
> Source   : texlive-2022-65.fc38.src.rpm
> Repository   : @System
> From repo: fedora
> Summary  : TeX fonts from the American Mathematical Society
> URL  : http://tug.org/texlive/
> License  : OFL-1.1
> Description  : An extended set of fonts for use in mathematics, including:
>  : extra mathematical symbols; blackboard bold letters
> (uppercase
>  : only); fraktur letters; subscript sizes of bold math italic
> and
>  : bold Greek letters; subscript sizes of large symbols such as
>  : sum and product; added sizes of the Computer Modern small
> caps
>  : font; cyrillic fonts (from the University of Washington);
> Euler
>  : mathematical fonts. All fonts are provided as Adobe Type 1
>  : files, and all except the Euler fonts are provided as
> Metafont
>  : source. The distribution also includes the canonical Type 1
>  : versions of the Computer Modern family of fonts. Plain TeX
> and
>  : LaTeX macros for using the fonts are provided.
> 
> and includes:
> 
> $ find /usr/share/texlive/texmf-dist/fonts -name eurm10\*
> /usr/share/texlive/texmf-dist/fonts/tfm/public/amsfonts/euler/eurm10.tfm
> /usr/share/texlive/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
> /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfb
> /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfm
>

So, I have this package installed/updated, and:

 $ find /usr/share/texlive/texmf-dist/fonts -name eurm10\*
 /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfm
 /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfb
 /usr/share/texlive/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
 /usr/share/texlive/texmf-dist/fonts/tfm/public/amsfonts/euler/eurm10.tfm

> For the .sty file you need to install the Walter Schmidt (was)package:
> texlive-was.

Yes, I have this installed from the Fedora sources.

> 
> TeX Live 2003 from CTAN has:
> 
> $ find /usr/local/texlive/2023/texmf-dist/fonts -name eurm10\*
> /usr/local/texlive/2023/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
> /usr/local/texlive/2023/texmf-dist/fonts/tfm/public/amsfonts/euler/eurm10.tfm
> /usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfb
> /usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfm
> 
> Check that the generated fontmap has eurm10 entries:
> 
> $ grep -F 'eurm10' 
> /usr/share/texlive/texmf-var/fonts/map/pdftex/updmap/pdftex.map
> eurm10 EURM10  eurm9 EURM10  eurmo10 EURM10 

Re: bitmap font error on F38

[Ranjan Maitra]

Thanks very much! And thanks also to Stan.

On Tue Apr25'23 01:57:02PM, Jerry James wrote:
> From: Jerry James 
> Date: Tue, 25 Apr 2023 13:57:02 -0600
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: bitmap font error on F38
> 
> On Tue, Apr 25, 2023 at 12:58 PM Ranjan Maitra  wrote:
> > Thanks very much again!
> >
> > I was explicitly able to update to texlive-was-svn64691-65.fc38.
> >
> > However, my problem with the font error continues on the F38 machine.
> >
> > What does it mean:  !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 
> > 720 not found
> >

...

> That works on my F38 machine.  Does this turn up anything?
> 
> find /usr/share/texlive -name \*.rpmnew

No, I get a blank. Nothing comes back (just the cursor).

> 
> I'm especially interested in /usr/share/texlive/web2c/updmap.cfg.  If
> there's an rpmnew version, you might have to fix that up before your
> example will work.

This file does not exist on my system (both F37 or F38).

Here is what I get when I search for the file:

$ sudo dnf provides */updmap.cfg
 Last metadata expiration check: 1:06:49 ago on Tue 25 Apr 2023 02:04:26 PM CDT.
 texlive-texlive-scripts-10:svn64830-69.fc38.noarch : TeX Live infrastructure
   : programs
 Repo: fedora
 Matched from:
 Filename: /etc/texlive/web2c/updmap.cfg
 Filename: /usr/share/texlive/texmf-config/web2c/updmap.cfg
 Filename: /usr/share/texlive/texmf-dist/web2c/updmap.cfg

 texlive-texlive-scripts-10:svn64830-71.fc38.noarch : TeX Live infrastructure
   : programs
 Repo: @System
 Matched from:
 Filename: /etc/texlive/web2c/updmap.cfg
 Filename: /usr/share/texlive/texmf-config/web2c/updmap.cfg
 Filename: /usr/share/texlive/texmf-dist/web2c/updmap.cfg

 texlive-texlive-scripts-10:svn64830-71.fc38.noarch : TeX Live infrastructure
   : programs
 Repo: updates
 Matched from:
 Filename: /etc/texlive/web2c/updmap.cfg
 Filename: /usr/share/texlive/texmf-config/web2c/updmap.cfg
 Filename: /usr/share/texlive/texmf-dist/web2c/updmap.cfg


But for the epoch numbers, etc that have changed in F38 from F37, the files are 
the same in F37.

But I now do not understand why the file compiles for you on F38, and not for 
me.

Thanks again!

Ranjan

> -- 
> Jerry James
> http://www.jamezone.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
> 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: bitmap font error on F38

[Ranjan Maitra]

Thanks very much again!

I was explicitly able to update to texlive-was-svn64691-65.fc38. 

However, my problem with the font error continues on the F38 machine.

What does it mean:  !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 720 
not found

Where does this come from?

Btw, I created the following LaTeX file font.tex:

%BEGIN FILE

 \documentclass[12pt]{article}
 \usepackage{upgreek}

 \begin{document}

 $\upalpha,\upbeta,\upeta,\upmu,\upsigma$

 \end{document}

%END FILE

 $ pdflatex font
 This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022) (preloaded 
format=pdflatex)
 restricted \write18 enabled.
 entering extended mode
 (./font.tex
 LaTeX2e <2022-06-01> patch level 5
 L3 programming layer <2022-12-17>
 (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
 Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
 (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
 (/usr/share/texlive/texmf-dist/tex/latex/was/upgreek.sty)
 (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def)
 (./font.aux) [1{/usr/share/texlive/texmf-var/fonts/map/pdftex/updmap/pdftex.map
}] (./font.aux)
 kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720 
eurm10
 mktexpk: don't know how to create bitmap font for eurm10.
 mktexpk: perhaps eurm10 is missing from the map file.
 kpathsea: Appending font creation commands to missfont.log.
 )
 !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 720 not found
  ==> Fatal error occurred, no output PDF file produced!

However, this compiles without error, just as it should, on my F37 machine.

Many thanks again, and best wishes,
Ranjan




> > Any more suggestions?
> 
> There was another question about this on the devel list.  As near as I
> can see in koji, there is no texlive-was-9 package.
> https://koji.fedoraproject.org/koji/packageinfo?packageID=5402
> 
> The rpm that contains upgreek.sty seems to be
> Name  texlive-was
> Version   svn64691
> Release   65.fc38
> Epoch 10
> Arch  noarch 
> https://koji.fedoraproject.org/koji/rpminfo?rpmID=33310676
> in F38.  Here is the Provides:
> Provides  
> tex(icomma.sty) = 2022
> tex(upgreek.sty) = 2022
> tex-was = 2022
> texlive-was = 10:svn64691-65.fc38<-  not sure what this is, an
> alternate name?
> 
> There is also, in f37,
> Name  texlive-was
> Version   svn21439.0
> Release   60.fc37
> Epoch 9
> Arch  noarch
> 
> https://koji.fedoraproject.org/koji/rpminfo?rpmID=33634957
> 
> Provides  
> tex(fixmath.sty) = 2021
> tex(gensymb.sty) = 2021
> tex(icomma.sty) = 2021
> tex(upgreek.sty) = 2021
> tex-was = 2021
> texlive-was = 9:svn21439.0-60.fc37<-  not sure what this is, an
> alternate name?
> 
> It looks like the epoch changes, and somehow messes up the update.
> ___
> 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: bitmap font error on F38

[Ranjan Maitra]

On Tue Apr25'23 09:57:58AM, Jerry James wrote:
> From: Jerry James 
> Date: Tue, 25 Apr 2023 09:57:58 -0600
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: bitmap font error on F38
> 
> On Tue, Apr 25, 2023 at 8:34 AM Ranjan Maitra  wrote:
> > Anyone has any suggestions on how to get around this problem? What BZ 
> > report, if any, should I file?
>
> Where did you get texlive-upgreek?  I don't see it in Fedora.

Thanks, it appears that upgreek.sty is in texlive-was-9, but is not on F38. It 
is a F37 package. 

 $ sudo dnf provides */upgreek.sty

 Last metadata expiration check: 2:07:00 ago on Tue 25 Apr 2023 09:00:08 AM CDT.
 texlive-was-9:svn21439.0-59.fc37.noarch : A collection of small packages by
: Walter Schmidt
 Repo: fedora
 Matched from:
 Filename: /usr/share/texlive/texmf-dist/tex/latex/was/upgreek.sty

 texlive-was-9:svn21439.0-60.fc37.noarch : A collection of small packages by
: Walter Schmidt
 Repo: @System
 Matched from:
 Filename: /usr/share/texlive/texmf-dist/tex/latex/was/upgreek.sty

> 
> Do you have the texlive-amsfonts package installed?  That seems to be
> the package that contains eurm10.afm.

Yes, I appear to have. 

 $ sudo dnf install texlive-amsfonts
 Last metadata expiration check: 1:49:57 ago on Tue 25 Apr 2023 09:20:42 AM CDT.
 Package texlive-amsfonts-10:svn61937-65.fc38.noarch is already installed.
 Dependencies resolved.
 Nothing to do.
 Complete!

However, there is a version difference with the one in F37, where upgreek still 
works.

 $ sudo dnf install texlive-amsfonts
 Last metadata expiration check: 2:12:18 ago on Tue 25 Apr 2023 09:00:08 AM CDT.
 Package texlive-amsfonts-9:svn29208.3.04-60.fc37.noarch is already installed.
 Dependencies resolved.
 Nothing to do.
 Complete!

However, both systems happen to have the same file, however, the F38 upgraded 
machine (from F37) gives the error.


 $ ll /usr/share/texlive/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
 -rw-r--r--. 1 root root 6.8K May 12  2012 
/usr/share/texlive/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm


Any more suggestions?

Thanks again for helping with this!

Best wishes,
Ranjan

> -- 
> Jerry James
> http://www.jamezone.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
> 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: bitmap font error on F38

[Ranjan Maitra]

Anyone has any suggestions on how to get around this problem? What BZ report, 
if any, should I file?

Many thanks,
Ranjan

On Fri Apr21'23 03:09:49PM, Ranjan Maitra wrote:
> From: Ranjan Maitra 
> Date: Fri, 21 Apr 2023 15:09:49 -0500
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: bitmap font error on F38
> 
> Hi,
> 
> This error appears to perhaps be coming from including texlive-upgreek (which 
> I am using in my document). Removing this call from the LaTeX document gets 
> around this issue, but of course produces errors of upgreek characters not 
> being found. Something appears to have changed from F37 to F38 with this 
> LaTeX TeXlive package.
> 
> Any suggestions? Happy to provide more information.
> 
> Best wishes,
> Ranjan
> 
> 
> 
> On Fri Apr21'23 02:01:22PM, Ranjan Maitra wrote:
> > From: Ranjan Maitra 
> > Date: Fri, 21 Apr 2023 14:01:22 -0500
> > To: Community Support for Fedora Users 
> > Reply-To: Community support for Fedora users 
> > Subject: bitmap font error on F38
> > 
> > Hi,
> > 
> > I am also having the following error with pdflatex upon upgrading to F38 
> > from F37.
> > 
> >  pathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720 
> > eurm10
> >  mktexpk: don't know how to create bitmap font for eurm10.
> >  mktexpk: perhaps eurm10 is missing from the map file.
> >  kpathsea: Appending font creation commands to missfont.log.
> >  (see the transcript file for additional information)
> >  !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 720 not found
> >   ==> Fatal error occurred, no output PDF file produced!
> > 
> > 
> > How do I get around this issue?
> > 
> > Many thanks and best wishes,
> > Ranjan
> > ___
> > 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
___
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: Fedora 38 Upgrade From Fedora 36

[Ranjan Maitra]

On Sat Apr22'23 11:26:12PM, Jeffrey Walton wrote:
> From: Jeffrey Walton 
> Date: Sat, 22 Apr 2023 23:26:12 -0400
> To: Community support for Fedora users 
> Reply-To: noloa...@gmail.com, Community support for Fedora users
>  
> Subject: Re: Fedora 38 Upgrade From Fedora 36
> 
> On Sat, Apr 22, 2023 at 11:18 PM Ranjan Maitra  wrote:
> > [...]
> > Actually, I went F34 -> F38 last night, without any issue. Just added a 
> > --nogpgcheck.
> >
> > So, I have this circa 2009 Dell Precision T7710 and the HDD died. I put in 
> > an old SSD and brought it back. However, for some reason, it does not boot 
> > off of a live CD that is newer. I had one F34 lying around, and got it 
> > booted off that. Then I  did
> >
> > sudo dnf update --releasever 38
> >
> > and it went through the download and then failed at the key check. So, I 
> > tried by removing the check and it went through.
> >
> > sudo dnf update --releasever 38 --nogpgcheck
> >
> > After installation, it asked to verify the key for F38, and that was 
> > permitted, and it appears to be like another machine that has been able to 
> > follow a more disciplined regimen. I tried this on a whim some time ago 
> > with another old machine (F34 -> F37 in that case), and it worked then too. 
> > I guess this is not recommended, but it worked for me.
> 
> The Fedora signing keys are located at  /etc/pki/rpm-gpg. I wonder if
> you could have copied the missing keys manually, or if the signing
> algorithm was the problem.
> 

Thanks, that is a good point. I could have done that, I guess, but it would 
have been more work. So, I gave the nogpgcheck to update, and then verified 
once the update to the higher release version happened.

I can see why this would not be recommended. I think that my case was safer 
because I used the F34 to install and then immediately moved to upgrade to F38. 
No non-Fedora repos were added before the upgrade.

Many thanks and best wishes,
Ranjan
___
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: Fedora 38 Upgrade From Fedora 36

[Ranjan Maitra]

On Sat Apr22'23 03:59:36PM, Community Support for Fedora Users wrote:
> From: ToddAndMargo via users 
> Date: Sat, 22 Apr 2023 15:59:36 -0700
> To: users@lists.fedoraproject.org
> Cc: ToddAndMargo 
> Reply-To: Community support for Fedora users 
> Subject: Re: Fedora 38 Upgrade From Fedora 36
> 
> On 4/22/23 15:31, Samuel Sieb wrote:
> > On 4/22/23 10:31, Barry wrote:
> > > > On 22 Apr 2023, at 18:11, David Dembrow  wrote:
> > > > 
> > > > Is it safe to upgrade to fedora 38 from fedora 36?  Or in other
> > > > words can a release cycle get skipped?
> > > 
> > > It is not recommended. Safest to go via 37.
> > 
> > That is not correct.  See the link that Jeffrey posted.
> > 
> > "System upgrade is only officially supported and tested over 2 releases
> > at most (e.g. from 36 to 38)."
> > 
> > I have upgraded 2 releases at a time many times with no issues.
> 
> I have got away with it too.  Went two at
> a time from 33 to 37 last year at
> a customer site.
>

Actually, I went F34 -> F38 last night, without any issue. Just added a 
--nogpgcheck.

So, I have this circa 2009 Dell Precision T7710 and the HDD died. I put in an 
old SSD and brought it back. However, for some reason, it does not boot off of 
a live CD that is newer. I had one F34 lying around, and got it booted off 
that. Then I  did

sudo dnf update --releasever 38

and it went through the download and then failed at the key check. So, I tried 
by removing the check and it went through.

sudo dnf update --releasever 38 --nogpgcheck

After installation, it asked to verify the key for F38, and that was permitted, 
and it appears to be like another machine that has been able to follow a more 
disciplined regimen. I tried this on a whim some time ago with another old 
machine (F34 -> F37 in that case), and it worked then too. I guess this is not 
recommended, but it worked for me.

Thanks,
Ranjan
___
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: Surprise! Fedora Linux 38 is here!

[Ranjan Maitra]

On Sat Apr22'23 01:46:56AM, Community Support for Fedora Users wrote:
> From: ToddAndMargo via users 
> Date: Sat, 22 Apr 2023 01:46:56 -0700
> To: Community support for Fedora users 
> Cc: ToddAndMargo 
> Reply-To: Community support for Fedora users 
> Subject: Re: Surprise! Fedora Linux 38 is here!
> 
> On 4/18/23 07:00, Matthew Miller wrote:
> > or, of course, just upgrade your already-installed systems, which
> > shouldn't take much longer than brewing and enjoying a nice cup of
> > coffee. Enjoy!
> 
> 
> Ha!  Are you forgetting this preinstall command?
> 
># dnf --enablerepo=* update --refresh
> 
> That cups of coffee is going to be really strong
> and really cold.

I just tried:

sudo dnf update --releasever 38

and things went through, reasonably well.

Ranjan
___
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: cifs mount error F38 (possible selinux issue).

[Ranjan Maitra]

Barry,

Thanks for this! To answer some of your questions, I do not know what the 
version of Windows is. It is something that is fairly recent, but has not been 
changed for years.

After looking at dmesg (as recommended by the error message), and 
/var/log/messages, I tried to change selinux to permissive on the F38 box, and 
then I was able to mount the share. However, the F37 box mounts the share fine, 
with selinux set at enforcing. So, should a separate context need to be created 
for F38? If so, what, where?

Also, the mount-cifs package version is exactly the same on both F37 and F38 
(both up to date). So, I do not know if mount-cifs is the issue, hence I do not 
know if it is worthwhile trying smbclient for this purpose.

Many thanks again, and best wishes,
Ranjan

On Sat Apr22'23 08:51:20AM, Barry wrote:
> From: Barry 
> Date: Sat, 22 Apr 2023 08:51:20 +0100
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: cifs mount error F38
> 
> 
> 
> > On 21 Apr 2023, at 23:33, Ranjan Maitra  wrote:
> > 
> > Barry,
> > 
> > Thanks!
> > 
> >> On Fri Apr21'23 10:35:32PM, Barry wrote:
> >> From: Barry 
> >> Date: Fri, 21 Apr 2023 22:35:32 +0100
> >> To: Community support for Fedora users 
> >> Reply-To: Community support for Fedora users 
> >> 
> >> Subject: Re: cifs mount error F38
> >> 
> >> 
> >> 
> >>>> On 21 Apr 2023, at 19:34, Ranjan Maitra  wrote:
> >>> 
> >>> I recently upgraded two of my Fedora machines, but when I try to mount a 
> >>> Windows share using mount-cifs, I get the following:
> >>> 
> >>> mount error(126): Required key not available
> >>> 
> >>> The mount.cifs command that is used has the following  
> >>> sec=ntlmssp,rw,nounix,noserverino,file_mode=0777,dir_mode=0777,vers=3.0
> >>> 
> >>> Mounting this same share still works from my F37 machines. Presumably 
> >>> something has changed with F38, and so I am wondering how to mount these 
> >>> shares.
> >> 
> >> What OS and software is serving the shares?
> > 
> > The share is a Windows share. I do not know how to answer the software 
> > question, sorry.
> 
> What is the version of windows?
> 
> > 
> >> Can you use smbclient to access the share?
> > 
> > I do not know about this. the above 
> > sec=ntlmssp,rw,nounix,noserverino,file_mode=0777,dir_mode=0777,vers=3.0 are 
> > needed in mount.cifs for things to work, with mount.cifs.
> > 
> > How would I try using smbclient with something that matches the above 
> > invocations?
> > 
> > Sorry, I am not very familiar with this.
> 
> Try the man page for smbclient, let us know if you can get it working.
> 
> > 
> > Thanks again for your help!
> > 
> > Best wishes,
> > Ranjan
> > ___
> > 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
___
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: cifs mount error F38

[Ranjan Maitra]

Barry,

Thanks!

On Fri Apr21'23 10:35:32PM, Barry wrote:
> From: Barry 
> Date: Fri, 21 Apr 2023 22:35:32 +0100
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: cifs mount error F38
> 
> 
> 
> > On 21 Apr 2023, at 19:34, Ranjan Maitra  wrote:
> > 
> > I recently upgraded two of my Fedora machines, but when I try to mount a 
> > Windows share using mount-cifs, I get the following:
> > 
> > mount error(126): Required key not available
> > 
> > The mount.cifs command that is used has the following  
> > sec=ntlmssp,rw,nounix,noserverino,file_mode=0777,dir_mode=0777,vers=3.0
> > 
> > Mounting this same share still works from my F37 machines. Presumably 
> > something has changed with F38, and so I am wondering how to mount these 
> > shares.
> 
> What OS and software is serving the shares?

The share is a Windows share. I do not know how to answer the software 
question, sorry.

> Can you use smbclient to access the share?

I do not know about this. the above 
sec=ntlmssp,rw,nounix,noserverino,file_mode=0777,dir_mode=0777,vers=3.0 are 
needed in mount.cifs for things to work, with mount.cifs.

How would I try using smbclient with something that matches the above 
invocations?

Sorry, I am not very familiar with this.

Thanks again for your help!

Best wishes,
Ranjan
___
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: bitmap font error on F38

[Ranjan Maitra]

Hi,

This error appears to perhaps be coming from including texlive-upgreek (which I 
am using in my document). Removing this call from the LaTeX document gets 
around this issue, but of course produces errors of upgreek characters not 
being found. Something appears to have changed from F37 to F38 with this LaTeX 
TeXlive package.

Any suggestions? Happy to provide more information.

Best wishes,
Ranjan



On Fri Apr21'23 02:01:22PM, Ranjan Maitra wrote:
> From: Ranjan Maitra 
> Date: Fri, 21 Apr 2023 14:01:22 -0500
> To: Community Support for Fedora Users 
> Reply-To: Community support for Fedora users 
> Subject: bitmap font error on F38
> 
> Hi,
> 
> I am also having the following error with pdflatex upon upgrading to F38 from 
> F37.
> 
>  pathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720 
> eurm10
>  mktexpk: don't know how to create bitmap font for eurm10.
>  mktexpk: perhaps eurm10 is missing from the map file.
>  kpathsea: Appending font creation commands to missfont.log.
>  (see the transcript file for additional information)
>  !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 720 not found
>   ==> Fatal error occurred, no output PDF file produced!
> 
> 
> How do I get around this issue?
> 
> Many thanks and best wishes,
> Ranjan
> ___
> 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

bitmap font error on F38

[Ranjan Maitra]

Hi,

I am also having the following error with pdflatex upon upgrading to F38 from 
F37.

 pathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720 eurm10
 mktexpk: don't know how to create bitmap font for eurm10.
 mktexpk: perhaps eurm10 is missing from the map file.
 kpathsea: Appending font creation commands to missfont.log.
 (see the transcript file for additional information)
 !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 720 not found
  ==> Fatal error occurred, no output PDF file produced!


How do I get around this issue?

Many thanks and best wishes,
Ranjan
___
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

cifs mount error F38

[Ranjan Maitra]

I recently upgraded two of my Fedora machines, but when I try to mount a 
Windows share using mount-cifs, I get the following:

mount error(126): Required key not available

The mount.cifs command that is used has the following  
sec=ntlmssp,rw,nounix,noserverino,file_mode=0777,dir_mode=0777,vers=3.0

Mounting this same share still works from my F37 machines. Presumably something 
has changed with F38, and so I am wondering how to mount these shares.

Many thanks, and best wishes,
Ranjan
___
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: GNOME interface is too bulky

[Ranjan Maitra]

On Mon Apr03'23 09:24:57PM, Tom Horsley wrote:
> From: Tom Horsley 
> Date: Mon, 3 Apr 2023 21:24:57 -0400
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: GNOME interface is too bulky
> 
> On Tue, 04 Apr 2023 10:39:25 +0930
> Tim via users wrote:
> 
> > Icons, icons, icons!  I can't find a damn thing by icons.
> 
> Yes! A stop sign and an envelope are pretty much it for icons that
> make some sense, after those two it is all guesswork (and I wonder how
> the envelope will age with no one sending physical letters
> any longer :-).
> 
> Personally, I use the FVWM window manager and my own custom .fvwmrc
> file which doesn't completely change my interface every six months.

Wow, I used to use twm for a while, pre-Fedora, and then fvwm2, and then went 
to xfce briefly before pekwm and then settling on openbox. I make my own remix, 
and my wife who used to make fun of my desktop environment (shunya/zero) 
eventually adopted it, and does not want to go back. She went kde -> xfce -> 
lxde -> openbox. (She still makes fun of it though.)

There is something to be said for stability and backwards compatibility, which 
seems to be missing from at least a few modern software -- I was long ago given 
to understand that achieving 1.0 in a software version meant that backwards 
compatibility would be maintained in the future, however this does not seem to 
be the case anymore.

Unfortunately, I have read that openbox and other such window managers will 
stop working as wayland progresses without more development. I hope that is too 
long into the future.

Ranjan

___
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: mounting a drive on F37

[Ranjan Maitra]

On Thu Mar30'23 04:23:30PM, Peter Boy wrote:
> From: Peter Boy 
> Date: Thu, 30 Mar 2023 16:23:30 +0200
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: mounting a drive on F37
> 
> 
> 
> > Am 30.03.2023 um 16:02 schrieb Ranjan Maitra :
> > 
> > 
> >> And to make it permanent
> >> 
> >> […]$ sudo vi /etc/fstab
> >> 
> >> and add at the end
> >> either
> >> /dev/sdb1  /mnt   xfs defaults0  0
> >> or
> >> /dev/sdb1  /mnt   ext4 defaults0  0
> >> 
> > 
> > lsblk now yields a UUID, so I guess i could use that for consistency with 
> > the rest, or the actual drive above.
> 
> You can do that, yes. One reason for UUID is, when you do some hardware 
> maintenance and reconnect the drives to different sata ports the naming can 
> change. The previous /dev/sdb may become /dev/sdd etc. Using UUID make you to 
> some degree independent from cabling and ports.
> 
> 
> > But, should I use 0 0 above, or 1 2, given that /home is 1 2. Since  that 
> > is what I will be backing up hourly (after the first run), using changes 
> > per rsync to this drive).
> 
> The first „zero“:
> fs_freq: This field is used by dump(8) to determine which filesystems need to 
> be dumped. Defaults to zero (don’t dump) if not present.
> 
> I suppose, you don’t want it to get dumped, so leave it zero
> 
> The second „zero“:
> fs_passno: This field is used by fsck(8) to determine the order in which 
> filesystem checks are done at boot time. The root filesystem should be 
> specified with a fs_passno of 1. Other filesystems should have a fs_passno of 
> 2. Filesystems within a drive will be checked sequentially, but filesystems 
> on different drives will be checked at the same time to utilize parallelism 
> available in the hardware. Defaults to zero (don’t check the filesystem) if 
> not present.
> 
> Modern journaling filesystems as ext4 or xfs  don’t need a file check at 
> every boot time. So I think it is best to retain the default. 
> 
> 
> 
> Best
> 
>

Thanks, I used it as 0 0 and used the UUID. So after editing the /etc/fstab, I 
have to do, per the file itself:

sudo systemctl daemon-reload

Do I need to do anything else to mount the drive? 

Many thanks,
Ranjan



> 
> 
> --
> Peter Boy
> https://fedoraproject.org/wiki/User:Pboy
> p...@fedoraproject.org
> 
> Timezone: CET (UTC+1) / CEST (UTC+2)
> 
> 
> Fedora Server Edition Working Group member
> Fedora docs team contributor
> Java developer and enthusiast
> 
> 
> ___
> 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: mounting a drive on F37

[Ranjan Maitra]

Thanks very much!

On Thu Mar30'23 03:42:50PM, Peter Boy wrote:
> From: Peter Boy 
> Date: Thu, 30 Mar 2023 15:42:50 +0200

> 
> Then you might have a BIOS Raid, where the BIOS provides some of the code 
> instead of the Linux driver. Before you update to F38 and/or F39, you should 
> study the release notes. Linux support for  BIOS Raid changed, I don’t 
> remember the details out of my head. They will NOT get totally unsupported, 
> but you may have to install different drivers, maybe it’s updated automatic. 
> As I said, I don’t remember the details. 
> 

OK, thanks for this warning, I will remember to make sure.

> >> What says
> >> 
> >> cfdisk /dev/sdb ?
> > 
> > So, I get a new screen come up, and "select label type" from "gpt", "dos", 
> > "sgi" and "sun". I guess this should be "gpt", so I tried that.
> > 
> > The process forward seemed straightforward, and I got a filesystem created 
> > with "Label" gpt, "identifier "some long alphanumeric name" and "Partition 
> > UUID" and of "Partition type: Linux file system", both the last with two 
> > other long alphanumeric names.
> > 
> > I went into "Type" but there is no option for "ext4" ("or xfs", for that 
> > matter) and so left it as "Linux file system" and then "Write" (wrote) to 
> > disk ("yes") and "Quit" to move on.
> > 
> >> 
> >> If you can, create a partition and afterwards a filesystem. Then try e.g.
> >> mount -t xfs|ext4   /dev/sdb1   /mnt 
> > 
> > Here, however, I get:
> > 
> > $ sudo mount -t ext4   /dev/sdb1   /mnt
> > mount: /mnt/backup: wrong fs type, bad option, bad superblock on /dev/sdb1, 
> > missing codepage or helper program, or other error.
> >   dmesg(1) may have more information after failed mount system call.
> 
> 
> Yes, you must create a file system on the newly created partition. Currently 
> xfs is the default, so you have to execute:
> 
> […]$ sudo mkfs.xfs /dev/sdb1
> […]$ sudo mount -t xfs  /dev/sdb1 /mnt  
> 
> or if you want to stay with ext4:
> […]$ sudo mkfs.ext4 /dev/sdb1
> […]$ sudo mount -t ext4  /dev/sdb1  /mnt  
>

Right, got this to work, thanks!

> And to make it permanent
> 
> […]$ sudo vi /etc/fstab
> 
> and add at the end
> either
> /dev/sdb1  /mnt   xfs defaults0  0
> or
> /dev/sdb1  /mnt   ext4 defaults0  0
> 

lsblk now yields a UUID, so I guess i could use that for consistency with the 
rest, or the actual drive above. But, should I use 0 0 above, or 1 2, given 
that /home is 1 2. Since  that is what I will be backing up hourly (after the 
first run), using changes per rsync to this drive).

In the current filesystem set up by anaconda, I have  1 1 for / 0 0 for swap 
and 1 2 for everything else.

> 
> Generally, /mnt is not a good option for a permanent mount. You should create 
> either /srv/backups  (srv for server or services) or at least /mnt/mybackups
> 

I will do that, thank you!

Best wishes,
Ranjan
___
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: mounting a drive on F37

[Ranjan Maitra]

Thanks, very much, to all!

To answer the questions:

> From: Peter Boy 
> Date: Thu, 30 Mar 2023 08:03:25 +0200
>
> > I have three additional drives, two of which are hardware (for historical 
> > reasons) RAIDed, and have /home 
> 
> As it looks, sda and sdc are software raid. If you had a hardware raid, all 
> disks attached to the hardware raid controller show up as one drive.  But 
> doesn’t matter as long as it works.
>

I see, thanks! I assumed HW RAID since it was set up through the BIOS ages ago.

> > But, my problem is that /dev/sdb does not appear to have a UUID number. 
> > Indeed, I get nothing back when I try:
> 
> At first you have to create a partition and a file system on the new drive, 
> which seems to be /dev/sdb. (After that you should see UUIDs).
> 
> What says
> 
> cfdisk /dev/sdb ?

So, I get a new screen come up, and "select label type" from "gpt", "dos", 
"sgi" and "sun". I guess this should be "gpt", so I tried that.

The process forward seemed straightforward, and I got a filesystem created with 
"Label" gpt, "identifier "some long alphanumeric name" and "Partition UUID" and 
of "Partition type: Linux file system", both the last with two other long 
alphanumeric names.

I went into "Type" but there is no option for "ext4" ("or xfs", for that 
matter) and so left it as "Linux file system" and then "Write" (wrote) to disk 
("yes") and "Quit" to move on.

> 
> If you can, create a partition and afterwards a filesystem. Then try e.g.
> mount -t xfs|ext4   /dev/sdb1   /mnt 

Here, however, I get:

$ sudo mount -t ext4   /dev/sdb1   /mnt
 mount: /mnt/backup: wrong fs type, bad option, bad superblock on /dev/sdb1, 
missing codepage or helper program, or other error.
   dmesg(1) may have more information after failed mount system call.

dmesg says lots of selinux-related things, as always, but perhaps the one seems 
more useful:

 [64087.184258] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem

and

$ lsblk -f

now has the additional entry:

 sdb
 └─sdb1

But that is it. Nothing more

I suspect that somewhere above, I should have been able to say that it was an 
ext4, but I can not figure out which of the "TYPE"s would have given me that.

To answer the earlier questions:

> From: Samuel Sieb 
> Date: Wed, 29 Mar 2023 22:07:15 -0700

Now,

$ sudo blkid /dev/sdb1
 /dev/sdb1: PARTUUID="some long alphanumeric number"

(earlier, it gave nothing at all).


$ fdisk -l /dev/sdb

 Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
 Disk model: WDC WD2005FBYZ-0
 Units: sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disklabel type: gpt
 Disk identifier: massive alphanumeric number
 
 Device StartEndSectors  Size Type
 /dev/sdb1   2048 3907028991 3907026944  1.8T Linux filesystem
 

> From: Joe Zeff 
> Date: Thu, 30 Mar 2023 00:06:04 -0600


> So use gparted to partition and format it, and give it a label because
> it's easier to type a label into fstab than a UUID.

So, I have parted, and that is probably good enough (I am currently remote on 
the machine). 

So, I do:


$ sudo parted /dev/sdb

 GNU Parted 3.5
 Using /dev/sdb
 Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted) TYPE-UUID
   align-check TYPE N   check partition N for TYPE(min|opt)
 alignment
   help [COMMAND]   print general help, or help on
 COMMAND
   mklabel,mktable LABEL-TYPE   create a new disklabel (partition
 table)
   mkpart PART-TYPE [FS-TYPE] START END make a partition
   name NUMBER NAME name partition NUMBER as NAME
   print [devices|free|list,all]display the partition table, or
 available devices, or free space, or all found partitions
   quit exit program
   rescue START END rescue a lost partition near START
 and END
   resizepart NUMBER ENDresize partition NUMBER
   rm NUMBERdelete partition NUMBER
   select DEVICEchoose the device to edit
   disk_set FLAG STATE  change the FLAG on selected device
   disk_toggle [FLAG]   toggle the state of FLAG on selected
 device
   set NUMBER FLAG STATEchange the FLAG on partition NUMBER
   toggle [NUMBER [FLAG]]   toggle the state of FLAG on 
partition
 NUMBER
   type NUMBER TYPE-ID or TYPE-UUID type set TYPE-ID or TYPE-UUID of
 partition NUMBER
   unit UNITset the default unit to UNIT
   version  display the version number and  
  copyright information of GNU Parted

I guess I can move mklabel, and then name it (can this be 

mounting a drive on F37

[Ranjan Maitra]

Hi,

I am trying to modify my /etc/fstab to mount a drive (where I want to place a 
backup). From looking at the current setup created by anaconda, it looks like I 
have to setup using UUID or LABEL (however these seem to be blank, see below).

First, my setup.

I have one SSD that has / and all the partitions associated with it.

I have three additional drives, two of which are hardware (for historical 
reasons) RAIDed, and have /home in them, and a third new drive that is  a "free 
agent" (sorry for not knowing the correct term, but I hope that I can convey 
the meaning).

I want this to be mounted at boot as /mnt/whatever (I have verified that this 
mount-point has been created and exists).

So, I look at my /dev/disk/by-disk-seq and see:

~$ ls
 1@  2@  4@  5@  6@

~$ ll *
 lrwxrwxrwx. 1 root root 9 Mar 29 14:01 1 -> ../../sda
 lrwxrwxrwx. 1 root root 9 Mar 29 14:01 2 -> ../../sdb
 lrwxrwxrwx. 1 root root 9 Mar 29 14:01 4 -> ../../sdc
 lrwxrwxrwx. 1 root root 9 Mar 29 14:01 5 -> ../../sr0
 

OK, there is an a, b and c. The d is the first drive that has the /, the sr0 is 
the swap, and the a, b and c are the three drives.

It appears to me that the sda and sdc are the ones raided (they have the same 
UUID and also lsblk indicates so (I have made up the part numbers here, for 
security). I have to say that I expected sda and sdb to be the RAIDed drives, I 
thought that sdc would be the new one that has been put in. But perhaps I am 
wrong in my understanding.


Anyway, 

$ lsblk -f
 NAMEFSTYPE  FSVER  LABEL UUID  FSAVAIL FSUSE% 
MOUNTPOINTS
 sda isw_raid_member 1.3.00 
  
   sda1  ext41.0  x
   md126
  
 md126p1 ext41.0  x 116.3G8% /home
   md127
  
 sdb
  
 sdc isw_raid_member 1.3.00 
  
   sdc1  ext41.0  x
   md126
  
 md126p1 ext41.0  x 116.3G8% /home
   md127
  
 sdd
  
   sdd1  vfatFAT32E56F-E0D8 
  
   sdd2  ext41.0  y 595.9M8% /boot
   sdd3  vfatFAT321616-D18F 933.7M 2% 
/boot/efi
   sdd4  ext41.0  u 43.2G 0% /tmp
   sdd5  ext41.0  v 43.2G 0% 
/usr/local
   sdd6  swap1w[SWAP]
   sdd7  ext41.0  z 76.3G14% /
 sr0
  
 zram0  
  [SWAP]
 

But, my problem is that /dev/sdb does not appear to have a UUID number. Indeed, 
I get nothing back when I try:

$ sudo blkid /dev/sdb1

or even

$ sudo blkid /dev/sdb

So, how do I mount this drive onto my /etc/fstab? Sorry if things are not 
clear, but I am happy to clarify further and provide more information.


Many thanks for your help, and best wishes,
Ranjan
___
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: commands available on bootable iso

[Ranjan Maitra]

On Sun Mar26'23 08:30:51AM, Community Support for Fedora Users wrote:
> From: stan via users 
> Date: Sun, 26 Mar 2023 08:30:51 -0700
> To: users@lists.fedoraproject.org
> Cc: stan 
> Reply-To: Community support for Fedora users 
> Subject: Re: commands available on bootable iso
> 
> On Sat, 25 Mar 2023 22:21:22 -0700
> Geoffrey Leach  wrote:
> 
> > Is it possible to get a list of the commands available on a  Fedora
> > iso  without actually mounting the iso? What I'm looking for is the
> > commands available from the Anaconda menu, not the commands that are
> > installed to the disk. 
> 
> Possible?  Yes.  Easy?  No.
> 
> I think the definitive way would be to download the src.rpm and
> unpack it, and look at the code to see what commands are there.
> 
> https://koji.fedoraproject.org/koji/packageinfo?packageID=2
> 
> You could also ask on the fedora anaconda mailing list.  The developers
> probably have a list of the commands, or know them.
> 
> I haven't seen the interface since they switched from the hub and spoke
> format, but I assume there will be different commands depending on
> where you are in the install process.  So, your question is not well
> difined.  If you are asking the developers, they will probably want to
> know why you are asking, or what you are looking for in order to narrow
> it down.

So, I am not sure what the OP is asking for. But from the kickstart file(s), 
you can get the list of the rpms in an iso from:

https://pagure.io/fedora-kickstarts/tree/f37

Then you can use:

dnf repoquery -l rpm-name

and get the list of the files in each rpm.

This is a large number of rpms, and even larger number of files to go through.

Best wishes,
Ranjan
___
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: Fedora 37: Gnome 43: screensaver: How to lock screen from command line

[Ranjan Maitra]

Hi,

I use slock. It is lightweight, and does not get in the way (as they like to 
say). It is part of the suckless tools (www.suckless.org).

Thanks,
Ranjan

On Sun Mar26'23 03:15:32PM, Wolfgang Pfeiffer wrote:
> From: Wolfgang Pfeiffer 
> Date: Sun, 26 Mar 2023 15:15:32 +0200
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: Fedora 37: Gnome 43: screensaver: How to  lock screen from
>  command line
> 
> On Sat, Mar 25, 2023 at 10:58:28AM +, Patrick O'Callaghan wrote:
> > 
> > I guess what I'm asking is if there's a standard (XDG) way to invoke a
> > screensaver.
> 
> Not sure if this is a "standard (XDG) way", but I'm running i3lock:
> https://i3wm.org/i3lock/
> 
> Simple and efficient.
> https://linuxcommandlibrary.com/man/i3lock
> 
> My environment:
> 
> % env | egrep -i 'n__desktop|session=|ssion_t|xdm'
> DESKTOP_SESSION=i3
> DM_CONTROL=/run/xdmctl
> XDG_SESSION_TYPE=x11
> XDM_MANAGED=method=classic
> 
> % loginctl session-status | grep Servic\[e\]
>Service: kdm; type x11; class user
> 
> HTH,
> Wolfgang
> ___
> 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: OT: is it possible to have one cron job follow GMT/UTC?

[Ranjan Maitra]

On Tue Mar21'23 10:47:47PM, Barry wrote:
> From: Barry 
> Date: Tue, 21 Mar 2023 22:47:47 +
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: OT: is it possible to have one cron job follow GMT/UTC?
> 
> 
> 
> > On 21 Mar 2023, at 08:52, Mike Wright  wrote:
> > 
> > On 3/19/23 21:19, Ranjan Maitra wrote:
> >> Dear friends,
> >> I have a bunch of entries in my crontab, all doing different things at 
> >> different times. These times are picked up by the computer clock.
> >> However, one particular task (downloading weather maps) would benefit if 
> >> it was set to download using a clock that does not spring forward and fall 
> >> back. This is because these maps appear to be released according to 
> >> GMT/UTC and so setting the time according to the local clock does not 
> >> quite work. (I am aware that I could set my cron job to be at a specific 
> >> hour later than the actual during standard time, but I figured that this 
> >> would be a good opportunity to get to know of such a possibility, if such 
> >> exists.)
> >> So, how do I make a single entry that uses GMT or  UTC, in my crontab? 
> >> While also using the local time for the other tasks on crontab?
> > 
> > That sounds ideal for a systemd timer since it has native support
> > for UTC. You'd need a .service to fetch the weather maps and a
> > .timer to trigger the .service.  As far as systemd goes that is
> > pretty basic.

Thanks, so no cron job? And, my apologies, but where can I get an example?

> 
> Yep defaults to UTC but allows you to specify the time zone in the OnCalendar 
> property. This is very useful.
> 
> Barry
> > 
> > Everything else would stay under cron.
> > 
> > Mike Wright

Thanks again!

Ranjan
___
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

OT: is it possible to have one cron job follow GMT/UTC?

[Ranjan Maitra]

Dear friends,

I have a bunch of entries in my crontab, all doing different things at 
different times. These times are picked up by the computer clock.

However, one particular task (downloading weather maps) would benefit if it was 
set to download using a clock that does not spring forward and fall back. This 
is because these maps appear to be released according to GMT/UTC and so setting 
the time according to the local clock does not quite work. (I am aware that I 
could set my cron job to be at a specific hour later than the actual during 
standard time, but I figured that this would be a good opportunity to get to 
know of such a possibility, if such exists.)

So, how do I make a single entry that uses GMT or  UTC, in my crontab? While 
also using the local time for the other tasks on crontab?

Many thanks and best wishes,
Ranjan
___
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: software or hardware raid?

[Ranjan Maitra]

Thanks, Chris!

On Thu Mar02'23 02:49:49PM, Chris Adams wrote:
> From: Chris Adams 
> Date: Thu, 2 Mar 2023 14:49:49 -0600
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: software or hardware raid?
> 
> Once upon a time, Ranjan Maitra  said:
> > Thanks to everybody. I recall discussion from several years ago on the 
> > benefits of software over hardware RAID. I had completely forgotten about 
> > UPS for this new machine. Btw, what happens if power goes out (and I do not 
> > have UPS)?
> 
> Linux software RAID keeps a bitmap of pending writes by default, which
> is an okay (but not perfect) mechanism to recover from unexpected
> shutdown.  There's also an option to keep a write journal instead, but
> unless you put that on a separate fast device (e.g. quality SSD with
> long write lifetime), it'll impact performance significantly.
> 
> There are trade-offs between various types of SW and HW RAID, so really
> the first question would be "what are your requirements and
> expectations".  Are you talking about a high-uptime server, or a desktop
> where you just want to make hardware failure less annoying?  RAID (HW or
> SW) is NOT backups, so you shouldn't depend on it for saving your
> data.

Thanks, this will be a fairly high uptime machine (not allowed to call it a 
server here, because that is central IT's role to have and administer:-), 
running lots of jobs at least a large part of the time, but the  RAID will be 
on the /. It is more to keep the machine going if one of the two / drives fail 
(and till such time as I can get and put in a new one).

For /home (which is where my data reside), I have 2 backups done using rsync 
every hour. I plan to copy the actual /home to the second one, and I was  
thinking that the third one would be incremental backup (kept  for a year, 
since I occasionally realize weeks and months later that I really want a file 
back from long ago) or so. 
> 
> HW RAID has some advantages - quality controllers will have
> battery-backed cache, so things like write journaling don't impact
> performance and recovery from unexpected power failures is basically
> instantaneous.  For high performance requirements, there's less overhead
> with HW RAID (because data only has to transit the bus once, then the
> RAID controller has its own paths to the drives).  But HW RAID typically
> requires odd and/or proprietary software to manage, detect failures,
> etc.  Depending on the RAID level you are using, recovery from a failure
> of the controller itself can be harder too.
> 
> > Btw, I still stick to ext4, largely because of inertia (and because I have 
> > used lvm in the past and hated its naming conventions, I think, but there 
> > were also other limitations that I do not now recall) and have stayed away 
> > from zfs or btrfs or lvm. I am not sure what to do now. Clearly, things 
> > have moved far on.
> 
> I'm generally in the XFS on LVM (on SW mdraid when needed) camp
> myself... LVM adds a significant layer of flexibility and ability, but
> still using more "traditional" filesystems like XFS and ext4.  I had
> poor experiences with ZFS at a former job, and am still a little leery
> of some of the approach BTRFS takes.
> 
> I'm playing with adding the dm-integrity layer for my SW mdraid (so then
> XFS on LVM on mdraid on integrity on drive) setup as an additional check
> against silent drive failures, but again, unless you put that data on a
> separate fast SSD, it slows down performance a lot.

I see, so your recommendation is to go for xfs? 

Many thanks again, and best wishes,
Ranjan
___
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

Fedora 37 installer only sees 1 of 3 4TB drives on NVMe card

[Ranjan Maitra]

Hello,

I have 3 NVMe PCIe M.2 SSD part number CT4000P3PSSD8 on my card. However, the 
Fedora installer only sees one of these three SSDs. I tried looking at them 
using nvme list and only see one (and two separate 256 GB SSDs). I looked into 
the case, and all three 4 TB drives are there, with lights blinking. I am sorry 
not to give more relevant info right now (I do not know what to give), but the 
machine shipped by Dell (the 4 TB drives were purchased separately) is 
Precision 7920 Tower XCTO Base (it came with the 2 256 GB SSDs). 

Many thanks, and best wishes,
Ranjan
___
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: software or hardware raid?

[Ranjan Maitra]

Thanks to everybody. I recall discussion from several years ago on the benefits 
of software over hardware RAID. I had completely forgotten about UPS for this 
new machine. Btw, what happens if power goes out (and I do not have UPS)?

Btw, I still stick to ext4, largely because of inertia (and because I have used 
lvm in the past and hated its naming conventions, I think, but there were also 
other limitations that I do not now recall) and have stayed away from zfs or 
btrfs or lvm. I am not sure what to do now. Clearly, things have moved far on.

Thanks,
Ranjan

On Thu Mar02'23 02:19:25PM, George N. White III wrote:
> From: "George N. White III" 
> Date: Thu, 2 Mar 2023 14:19:25 -0400
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: software or hardware raid?
> 
> On Wed, Mar 1, 2023 at 4:02 PM Ranjan Maitra  wrote:
> 
> > Hi,
> >
> > I would like to RAID two of my disks, and I was wondering if the
> > recommendation is to do software or hardware RAID?
> >
> 
> Software RAID works very well on modern hardware.  You do want to make sure
> a power
> outage can't cause a shutdown before the RAID is safely dismounted.
> Ideally a your site
> has a reliable generator and your server has a UPS that can hold power
> while waiting for
> the generator to come online and also long enough to ensure a clean
> shutdown when the
> generator fails.
> 
>  --
> 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
> 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

software or hardware raid?

[Ranjan Maitra]

Hi,

I would like to RAID two of my disks, and I was wondering if the recommendation 
is to do software or hardware RAID?

Thanks,
Ranjan
___
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: recommended partition for swap with 0.5 TB memory

[Ranjan Maitra]

On Tue Feb28'23 08:09:24PM, Jeffrey Walton wrote:
> From: Jeffrey Walton 
> Date: Tue, 28 Feb 2023 20:09:24 -0500
> To: Community support for Fedora users 
> Reply-To: noloa...@gmail.com, Community support for Fedora users
>  
> Subject: Re: recommended partition for swap with 0.5 TB memory
> 
> On Tue, Feb 28, 2023 at 3:02 PM Ranjan Maitra  wrote:
> > On Tue Feb28'23 01:56:08PM, Richard Shaw wrote:
> > > On Tue, Feb 28, 2023 at 1:43 PM Ranjan Maitra  wrote:
> > >
> > > > I am trying to install Fedora on to a new machine that has 0.5 TB RAM.
> > > > Hard drives are 256 GB for / and friends, and 2 TB for /home partition. 
> > > > In
> > > > the past, it used to be suggested that swap be twice that of RAM: this
> > > > later changed to the same amount, and now it is very unclear (to me)
> > > > because I have not tracked the latest recommendations. Anyway, what 
> > > > would
> > > > you suggest? The machine is a Dell Precision 7920 with 28 cores/56 
> > > > threads.
> > > >
> > >
> > > By 0.5TB you mean 512GB of ram? Assuming you're installing Fedora 36 or 
> > > 37,
> > > I would just leave the defaults alone, which utilizes swap on zram. So
> > > basically it won't use any swap unless needed. You can adjust the amount 
> > > of
> > > memory allowed to be used for swap.
> >
> > Right, thanks. So, I let the installer pick this up. I usually do a custom 
> > partitioning, does that mean that I do not declare anything for swap?
> 
> And set swappiness to something low, like 1. There's almost no reason
> to allow anything to spill into the swap file with 512GB of RAM.

Agreed, but there are 56 threads on this machine. So, if all of them are being 
used, then the amount of memory is not that much on the average, though I hope 
to be fine.

I currently have a 8y-old 10C (20 thread) machine (originally with 32 GB, went 
up to 64 GB). At least for some jobs, I was not able to use all threads because 
of memory requirements. For that machine, I have:

$ swapon NAME   TYPE   SIZE USED PRIO /dev/zram0 partition8G   0B  
100 /dev/sdc6  partition 46.6G   0B   -2

and

$ free
   totalusedfree  shared  buff/cache   available
Mem:65762928 108965661769992   30928 2903280
63914968 Swap:   57215992   057215992

so I guess there is the zram0 there. 

I also don't see much value in having a lot of swap, unless it is some sort of 
very short (to be useful) holding operation (that is how my layman's mind likes 
to think about it).

> 
> In fact, my daily driver has 64GB of RAM, and I set the swap file size
> to 4 GB and set swappiness to 1. The 4 GB swap is there for
> emergencies, but I don't think it's ever been needed.
> 

Thanks again!

Ranjan
___
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: recommended partition for swap with 0.5 TB memory

[Ranjan Maitra]

On Tue Feb28'23 03:23:37PM, Richard Shaw wrote:
> From: Richard Shaw 
> Date: Tue, 28 Feb 2023 15:23:37 -0600
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: recommended partition for swap with 0.5 TB memory
> 
> On Tue, Feb 28, 2023 at 2:48 PM Ranjan Maitra  wrote:
> 
> > On Tue Feb28'23 01:56:08PM, Richard Shaw wrote:
> > > From: Richard Shaw 
> > > Date: Tue, 28 Feb 2023 13:56:08 -0600
> > > To: Community support for Fedora users 
> > > Reply-To: Community support for Fedora users <
> > users@lists.fedoraproject.org>
> > > Subject: Re: recommended partition for swap with 0.5 TB memory
> > >
> > > On Tue, Feb 28, 2023 at 1:43 PM Ranjan Maitra  wrote:
> > >
> > > > Hi,
> > > >
> > > > I am trying to install Fedora on to a new machine that has 0.5 TB RAM.
> > > > Hard drives are 256 GB for / and friends, and 2 TB for /home
> > partition. In
> > > > the past, it used to be suggested that swap be twice that of RAM: this
> > > > later changed to the same amount, and now it is very unclear (to me)
> > > > because I have not tracked the latest recommendations. Anyway, what
> > would
> > > > you suggest? The machine is a Dell Precision 7920 with 28 cores/56
> > threads.
> > > >
> > >
> > > By 0.5TB you mean 512GB of ram? Assuming you're installing Fedora 36 or
> > 37,
> > > I would just leave the defaults alone, which utilizes swap on zram. So
> > > basically it won't use any swap unless needed. You can adjust the amount
> > of
> > > memory allowed to be used for swap.
> > >
> >
> > I decided to let the automatic installer pick up the partition. It
> > correctly sets aside 4 TiB (sorry, it was 4TiB, not 2TiB as mentioned
> > earlier) for /home, and then 1 GiB for /boot, 600 MiB for /boot/efi, 70 GiB
> > for / and leaves aside the rest (as free space). I can adjust the 70 GiB,
> > but do I need to keep aside space for the zram? I am unsure about what to
> > do with so much free space?
> >
> 
> With zram you set a maximum amount of memory which can be used as swap (I
> think the default is 50% but it may have a maximum set). How it works is
> that it compresses the memory, generally giving around 2X compression. The
> CPU cost to compress/decompress is much faster than swapping to disk,
> perhaps not as much with modern NVMe drives, but it does help relieve
> memory pressure without causing unnecessary writes to your expensive SSDs
> :)
>

Thanks! So, at this point, I will simply increase / to cover around 250 GiB: my 
plan is to simply copy the first drive to the second for backups.

Btw, my sysadmin tells me that he bought 3 4 TiB drives and put it on the card. 
But during installation, I see only one 4 TiB drive. Is this possible? (These 
HDDs/SSDs are not RAIDed.)

> I was hoping to find something more Fedora centric, but here's the upstream
> documentation:
> https://github.com/systemd/zram-generator/blob/main/man/zram-generator.conf.md

Thanks for this!

Best wishes,
Ranjan
___
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: recommended partition for swap with 0.5 TB memory

[Ranjan Maitra]

On Tue Feb28'23 01:56:08PM, Richard Shaw wrote:
> From: Richard Shaw 
> Date: Tue, 28 Feb 2023 13:56:08 -0600
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: recommended partition for swap with 0.5 TB memory
> 
> On Tue, Feb 28, 2023 at 1:43 PM Ranjan Maitra  wrote:
> 
> > Hi,
> >
> > I am trying to install Fedora on to a new machine that has 0.5 TB RAM.
> > Hard drives are 256 GB for / and friends, and 2 TB for /home partition. In
> > the past, it used to be suggested that swap be twice that of RAM: this
> > later changed to the same amount, and now it is very unclear (to me)
> > because I have not tracked the latest recommendations. Anyway, what would
> > you suggest? The machine is a Dell Precision 7920 with 28 cores/56 threads.
> >
> 
> By 0.5TB you mean 512GB of ram? Assuming you're installing Fedora 36 or 37,
> I would just leave the defaults alone, which utilizes swap on zram. So
> basically it won't use any swap unless needed. You can adjust the amount of
> memory allowed to be used for swap.
>


I decided to let the automatic installer pick up the partition. It correctly 
sets aside 4 TiB (sorry, it was 4TiB, not 2TiB as mentioned earlier) for /home, 
and then 1 GiB for /boot, 600 MiB for /boot/efi, 70 GiB for / and leaves aside 
the rest (as free space). I can adjust the 70 GiB, but do I need to keep aside 
space for the zram? I am unsure about what to do with so much free space?

Many thanks and best wishes,
Ranjan
___
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