Re: F40: strange network issue after upgrade of laptop from F39

2024-05-23 Thread Ranjan Maitra via users
On Thu May23'24 10:16:17PM, Jeffrey Walton wrote:
> From: Jeffrey Walton 
> Date: Thu, 23 May 2024 22:16:17 -0400
> To: Community support for Fedora users 
> Reply-To: noloa...@gmail.com, Community support for Fedora users
>  
> Subject: Re: F40: strange network issue after upgrade of laptop from F39
>
> On Thu, May 23, 2024 at 10:12 PM R. G. Newbury  wrote:
> >
> > On 2024-05-23 19:20, users-requ...@lists.fedoraproject.org wrote:
> > > F40: strange network issue after upgrade of laptop from
> > >   F39
> > > To:users@lists.fedoraproject.org
> > > Message-ID:<088547fa-c5dd-49f3-86a0-a09dba72a...@sieb.net>
> > > Content-Type: text/plain; charset=UTF-8; format=flowed
> > >
> > > On 5/23/24 3:32 PM, Ranjan Maitra via users wrote:
> > >> I have a strange issue after upgrading a laptop (Dell XPS 13, 2013 
> > >> edition). That is that I am connected (whether through WiFi or ethernet 
> > >> cable) to a university network which claims after the upgrade that the 
> > >> laptop is no longer registered. I went through the registration process 
> > >> again through the browser (and was told: why are you registering this 
> > >> machine again, it is registered, simply restart the network/reboot) but 
> > >> the problem does not go away. I upgraded a desktop on the same ethernet 
> > >> switch and this problem did not go show up there (I am using that to 
> > >> write this email).
> > > What are they using to identify the computer?
> > > What is happening with the networking that isn't working?  No DHCP
> > > response, no network traffic, etc.
> >
> > Ignore the browser for the moment. Go into Network Connections and see
> > if your install is cloning a random MAC address. I *suspect* that the
> > registration "feature" may be checking against the MAC address, while
> > the browser passes through the SSID + password only. Just a guess but I
> > have had the same problem with my android cellphone getting a
> > DHCP-served address instead of the expected static IP due to a random
> > MAC address.
>
> Possibly related:
> <https://discussion.fedoraproject.org/t/f40-change-proposal-wifi-mac-randomization-system-wide/99856>

I see, this is possible, but I wonder why the desktops (I upgraded four of them 
so far) that are connected to the ethernet do not have this problem, while the 
laptop does, whether connected with the WiFi or the ethernet.

I will try the suggestion in that link tomorrow and report back.

Thank you again for your suggestion.

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: F40: strange network issue after upgrade of laptop from F39

2024-05-23 Thread Ranjan Maitra via users
Tim,

Thanks!

On Fri May24'24 01:03:08PM, Community Support for Fedora Users wrote:
> From: Tim via users 
> Date: Fri, 24 May 2024 13:03:08 +0930
> To: Community support for Fedora users 
> Cc: Ranjan Maitra , Tim 
> Reply-To: Community support for Fedora users 
> Subject: Re: F40: strange network issue after upgrade of laptop from F39
>
> On Thu, 2024-05-23 at 17:32 -0500, Ranjan Maitra via users wrote:
> > I have a strange issue after upgrading a laptop (Dell XPS 13, 2013
> > edition). That is that I am connected (whether through WiFi or
> > ethernet cable) to a university network which claims after the
> > upgrade that the laptop is no longer registered. I went through the
> > registration process again through the browser (and was told: why are
> > you registering this machine again, it is registered, simply restart
> > the network/reboot) but the problem does not go away. I upgraded a
> > desktop on the same ethernet switch and this problem did not go show
> > up there (I am using that to write this email).
>
> I suppose we need to know what "registration" entails.
>
> For some networks, it's simply going to be the DHCP server assigning
> you an IP to a MAC address it knows about (hardware details about your
> network).  This will get messed up if your hardware supplies random MAC
> addresses each time it makes a connection.

I suspect it is this above, since this is a one-time deal, only when a computer 
is set up for the first time (but done through the browser that one time). 
After that, it never asks for registration again unless the computer in 
question has not connected for months (in which case it has to be validated).

> For some networks, you login via a browser, and it does some kind of
> token exchange with their network that authorises you and they remember
> some network details about you.  Again it could be the MAC or they may
> simply associate the token with your current IP address.  This could
> get upset by things like your web browser not storing cookies, script
> blocking, or something stuck in its cache.  Going through web browser
> settings might be a good thing (checking what's allowed) and perhaps
> clearing your cache (you can do that without losing stored passwords,
> etc).  The cache just stores what you can see as web pages, so you can
> go back and forth through a site without redownloading each page.
>

I don't know if this matters but I do not need to keep the browser on after 
that first-time registration. Also, I never store my cache so once the browser 
is shut down, the cache is deleted.

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: F40: strange network issue after upgrade of laptop from F39

2024-05-23 Thread Ranjan Maitra via users
Thanks, Sam!

On Thu May23'24 03:42:32PM, Samuel Sieb wrote:
> From: Samuel Sieb 
> Date: Thu, 23 May 2024 15:42:32 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: F40: strange network issue after upgrade of laptop from F39
>
> On 5/23/24 3:32 PM, Ranjan Maitra via users wrote:
> > I have a strange issue after upgrading a laptop (Dell XPS 13, 2013 
> > edition). That is that I am connected (whether through WiFi or ethernet 
> > cable) to a university network which claims after the upgrade that the 
> > laptop is no longer registered. I went through the registration process 
> > again through the browser (and was told: why are you registering this 
> > machine again, it is registered, simply restart the network/reboot) but the 
> > problem does not go away. I upgraded a desktop on the same ethernet switch 
> > and this problem did not go show up there (I am using that to write this 
> > email).
>
> What are they using to identify the computer?

I don't know the answer to this question. But in general, this setup is, I 
think, fairly common in universities. Every machine is given an IP address (I 
think) if and only if it is registered (either as a guest, or as an 
employee/student).

> What is happening with the networking that isn't working?  No DHCP response,
> no network traffic, etc.

I am able to connect to WiFi (or ethernet). I get "Open Network Login page" and 
am then taken to the page which is what is used to register the machine. I 
register (or try to) as above, but this problem does not go away upon 
restarting the network (or rebooting the computer).

Sorry I am not sure I am answering the question here. Please let me know what I 
can do to find the answers to your questions.

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
--
___
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: F40: strange network issue after upgrade of laptop from F39

2024-05-23 Thread Ranjan Maitra via users

Thanks, Jeff!

On Thu May23'24 08:13:00PM, Jeffrey Walton wrote:
> From: Jeffrey Walton 
> Date: Thu, 23 May 2024 20:13:00 -0400
> To: Community support for Fedora users 
> CC: Ranjan Maitra 
> Reply-To: noloa...@gmail.com, Community support for Fedora users
>  
> Subject: Re: F40: strange network issue after upgrade of laptop from F39
>
> On Thu, May 23, 2024 at 6:33 PM Ranjan Maitra via users
>  wrote:
> > [...]
> >  I am connected (whether through WiFi or ethernet cable) to a university 
> > network which claims after the upgrade that the laptop is no longer 
> > registered. I went through the registration process again through the 
> > browser (and was told: why are you registering this machine again, it is 
> > registered, simply restart the network/reboot) but the problem does not go 
> > away. I upgraded a desktop on the same ethernet switch and this problem did 
> > not go show up there (I am using that to write this email).
> >
> > I should mention that the network on this upgraded laptop works fine when I 
> > take the laptop home and connect.
> >
> > So what could be the problem? I have not had such an issue with 
> > installations and upgrades for 40.5 versions of Fedora (the 0.5 is for RH9 
> > that I think I used mid-2003 to late 2003 before Fedora Core 1). How do I 
> > troubleshoot this?
>
> Does the University use a Captive Portal?

My apologies, but what is a captive portal. Btw, I can not stress this enough, 
but this was not a problem before the upgrade: indeed, the upgrade itself 
happened on that same network (on WiFi).

Many thanks again, and best wishes,
Ranjan

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


F40: strange network issue after upgrade of laptop from F39

2024-05-23 Thread Ranjan Maitra via users
Hi,

I have a strange issue after upgrading a laptop (Dell XPS 13, 2013 edition). 
That is that I am connected (whether through WiFi or ethernet cable) to a 
university network which claims after the upgrade that the laptop is no longer 
registered. I went through the registration process again through the browser 
(and was told: why are you registering this machine again, it is registered, 
simply restart the network/reboot) but the problem does not go away. I upgraded 
a desktop on the same ethernet switch and this problem did not go show up there 
(I am using that to write this email).

I should mention that the network on this upgraded laptop works fine when I 
take the laptop home and connect.

So what could be the problem? I have not had such an issue with installations 
and upgrades for 40.5 versions of Fedora (the 0.5 is for RH9 that I think I 
used mid-2003 to late 2003 before Fedora Core 1). How do I troubleshoot this?

Many thanks in advance 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


(Solved!) Re: Any idea how to solve: upgrade to F40 results in Cisco VPN not finding required libraries

2024-05-17 Thread Ranjan Maitra via users
On Sat May18'24 12:10:31AM, Community Support for Fedora Users wrote:
> From: Ranjan Maitra via users 
> Date: Sat, 18 May 2024 00:10:31 -0500
> To: Community Support for Fedora Users 
> Cc: Ranjan Maitra 
> Reply-To: Community support for Fedora users 
> Subject: Any idea how to solve: upgrade to F40 results in Cisco VPN not
>  finding required libraries
>
> I have Cisco VPN version cisco-secure-client-linux64-5.0.05040 which is what 
> is the current version released by our workplace.
>
> The complete upgrade to Fedora 40 from Fedora 39 appears to have resulted in:
>
>  You are missing the required libraries for the authentication method you 
> requested.
>
> whenever I try to use the VPN and basically I can not connect.
>
> Any suggestions as to how to get around this problem?

It appears that

sudo dnf install webkit2gtk4.0

gets around this problem for now.

Best,
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/f
--
___
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


Any idea how to solve: upgrade to F40 results in Cisco VPN not finding required libraries

2024-05-17 Thread Ranjan Maitra via users
I have Cisco VPN version cisco-secure-client-linux64-5.0.05040 which is what is 
the current version released by our workplace.

The complete upgrade to Fedora 40 from Fedora 39 appears to have resulted in:

 You are missing the required libraries for the authentication method you 
requested.

whenever I try to use the VPN and basically I can not connect.

Any suggestions as to how to get around this problem?

Many thanks in advance!

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 ... even after version 40

2024-04-22 Thread 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

2024-04-22 Thread 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)

2024-02-08 Thread 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)

2024-02-08 Thread 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)

2024-02-08 Thread 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)

2024-02-08 Thread 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

2023-12-20 Thread 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

2023-12-20 Thread 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

2023-12-03 Thread 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

2023-12-03 Thread 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

2023-12-03 Thread 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

2023-12-02 Thread 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

2023-11-30 Thread 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?

2023-11-27 Thread 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

2023-11-23 Thread 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

2023-11-23 Thread 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

2023-11-23 Thread 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

2023-11-22 Thread 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

2023-11-22 Thread 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

2023-11-22 Thread 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

2023-11-22 Thread 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

2023-11-19 Thread 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

2023-11-19 Thread 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

2023-11-18 Thread 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

2023-11-17 Thread 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?

2023-11-17 Thread 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

2023-11-15 Thread 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

2023-11-15 Thread 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

2023-11-14 Thread 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

2023-11-14 Thread 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

2023-11-14 Thread 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

2023-11-13 Thread 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

2023-11-12 Thread 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

2023-11-12 Thread 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

2023-11-12 Thread 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?

2023-11-12 Thread 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

2023-10-21 Thread 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