Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #225836 > unrolled thread

Python 3 Segmentation Fault

Back to article view | Back to linux.debian.user

Contents

  Python 3 Segmentation Fault "J.Arun Mani" <J.ArunMani@protonmail.com> - 2020-08-04 17:10 +0200
    Re: Python 3 Segmentation Fault Kushal Kumaran <kushal@locationd.net> - 2020-08-04 18:10 +0200
    Re: Python 3 Segmentation Fault Cindy Sue Causey <butterflybytes@gmail.com> - 2020-08-04 18:20 +0200
      a little bit off-topic (Was: Re: Python 3 Segmentation Fault) soyeomul@doraji.xyz (황병희) - 2020-08-09 04:50 +0200
    Re: [Python-Help] Python 3 Segmentation Fault "J.Arun Mani" <J.ArunMani@protonmail.com> - 2020-08-05 20:00 +0200
    Re: Python 3 Segmentation Fault soyeomul@doraji.xyz (황병희) - 2020-08-09 04:30 +0200

#225836 — Python 3 Segmentation Fault

[Multipart message — attachments visible in raw view] — view raw

Hello.
I'm using Debian Testing (upgraded from Debian 10). Today I started Python 3, but it was not able to interpret any commands from stdin and resulted in Segmentation Fault. Luckily modules (python3 -m <module>) and files (python3 <file>) works fine though.

Observed:
$ python3
Python 3.8.3rc1 (default, Apr 30 2020, 07:33:30)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> print
<No output, nothing>
<Press any key>
Segmentation fault

Screen capture that could help : https://www.dropbox.com/s/9w941t93ymem1x1/python3_issue-2020-08-04_19.38.28.mp4?dl=0

Some additional info:
1. I tried running a file that takes input from user (using input function), it also didn't work. So I think something regarding standard input has broken.
2. Python 2 also has the exact, same issue. So both Pythons face the problem !

I have IPython installed, which works fine without any issue.
The very recent installations I made :
Installed Emacs (~ 2 days ago)
Installed and removed Neovim (~ 1 day ago)

I tried reinstalling Python by : sudo apt reinstall python3
But it didn't fix the issue.

Though I hardly use live session of Python 3 (I use IPython for live sessions), having a broken Python 3 scares me. Any help regarding the issue is greatly appreciated. :)

Thanks
J Arun Mani

[toc] | [next] | [standalone]

#225842

"J.Arun Mani" <J.ArunMani@protonmail.com> writes:

> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started
> Python 3, but it was not able to interpret any commands from stdin and
> resulted in Segmentation Fault. Luckily modules (python3 -m <module>)
> and files (python3 <file>) works fine though.
>
> Observed:
> $ python3
> Python 3.8.3rc1 (default, Apr 30 2020, 07:33:30)

Where did you get this from?
https://tracker.debian.org/pkg/python3-defaults says testing has version
3.8.2-3.

The output of the command "apt policy python3" and looking at your
sources.list and /etc/apt/sources.list.d/* will help.

> [GCC 9.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
>>>> print
> <No output, nothing>
> <Press any key>
> Segmentation fault
>
> Screen capture that could help :
> https://www.dropbox.com/s/9w941t93ymem1x1/python3_issue-2020-08-04_19.38.28.mp4?dl=0
>
> Some additional info:
> 1. I tried running a file that takes input from user (using input
> function), it also didn't work. So I think something regarding
> standard input has broken.
> 2. Python 2 also has the exact, same issue. So both Pythons face the problem !
>
> I have IPython installed, which works fine without any issue.
> The very recent installations I made :
> Installed Emacs (~ 2 days ago)
> Installed and removed Neovim (~ 1 day ago)
>
> I tried reinstalling Python by : sudo apt reinstall python3
> But it didn't fix the issue.
>
> Though I hardly use live session of Python 3 (I use IPython for live
> sessions), having a broken Python 3 scares me. Any help regarding the
> issue is greatly appreciated. :)
>
> Thanks
> J Arun Mani

[toc] | [prev] | [next] | [standalone]

#225843

On 8/4/20, J.Arun Mani <J.ArunMani@protonmail.com> wrote:
> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started Python
> 3, but it was not able to interpret any commands from stdin and resulted in
> Segmentation Fault. Luckily modules (python3 -m <module>) and files (python3
> <file>) works fine though.
>
> Observed:
> $ python3
> Python 3.8.3rc1 (default, Apr 30 2020, 07:33:30)
> [GCC 9.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
>>>> print
> <No output, nothing>
> <Press any key>
> Segmentation fault


Hi... A C(omputer)C(opy) was sent to that help@python address for
informational purposes. If it bounces, that's cool, but I'll be
checking that out, too. Appreciate the lead there. :)

So.... I get this while attempting your path above:

++++ BEGIN TEST +++
$ python3
Python 3.8.5 (default, Jul 20 2020, 18:32:44)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> print
<built-in function print>
++++ END TEST ++++

Mine's Python 3.8.5 on Bullseye.. I STARTED TO ASK: Did you run
something similar to "apt-get update" before reinstalling?

But in addition to that: Did you also try
installing/reinstalling/upgrading Python3.8? It took a few seconds of
nosing around to figure out that's where *my* "Python 3.8.5" came from
(and NOT from e.g. Python3 nor Python):

++++ BEGIN APT-CACHE POLICY ++++
$ apt-cache policy python3.8
python3.8:
  Installed: 3.8.5-1
  Candidate: 3.8.5-1
  Version table:
 *** 3.8.5-1 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
++++ END APT-CACHE POLICY ++++

N.B. as an aside: There's a Debian-Python list out there:

https://lists.debian.org/debian-python/

Debian-Python's description is:

"Discussion of issues related to Python on Debian systems with a
stress on packaging standards. Therefore relevant for maintainers of
Python related packages."

It's for Developer types who are either creating or maintaining
Debian's Python-based packages. They're VERY helpful when inquiries
contain all the pertinent details necessary to work through issues.

Cindy :)

PS #ThankYou! You just helped me a little, too. I'm messing around
with something that's having GTK issues... and there is... a list for
that, too! Score!

https://lists.debian.org/completeindex.html

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed.. && yet another shiny new deboostrap... *

[toc] | [prev] | [next] | [standalone]

#226031 — a little bit off-topic (Was: Re: Python 3 Segmentation Fault)

Cindy Sue Causey <butterflybytes@gmail.com> writes:

> Mine's Python 3.8.5 on Bullseye..

Howdy, Cindy^^^
*Because* i like very so much Bullseye^^^ 

Sincerely, Byung-Hee from South Korea

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//

[toc] | [prev] | [next] | [standalone]

#225906 — Re: [Python-Help] Python 3 Segmentation Fault

Hello all.

I found a crazy fix to this issue. Running Python in Isolation mode raises no problem ! That is, you need to run Python like this:
 $ python3 -I

So having the isolation mode fix the issue, what next step shall I take to make the fix permanent (I mean tweak or look at which modules, binaries etc.) ?

Thanks
J Arun Mani

[toc] | [prev] | [next] | [standalone]

#226030

Dear Arun,

"J.Arun Mani" <J.ArunMani@protonmail.com> writes:

> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started Python 3, but it was not able to interpret any
> commands from stdin and resulted in Segmentation Fault. Luckily
> modules (python3 -m <module>) and files ...

Just i guess because you are in Debian *Testing*. Many people say Testing
is always dangerous. So you would be try to Debian stable or Ubuntu LTS?

Sincerely, Byung-Hee (my python3 is 3.6.9 in Ubuntu 18.04 LTS)

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web