Comment # 4 on bug 1169468 from Tom de Vries

>  	/usr/bin/gdb
>  		Error processing line 1 of
> /usr/lib/python3.6/site-packages/Paste-3.0.4-py2.7-nspkg.pth:
> 

This looks suspicious.

You're using leap 15.1.  The python-Paste version that goes with that is 2.0.3.

The version shown here is 3.0.4.

That's not the one tumbleweed currently uses, that's 3.4.0. And looking at
tumbleweed history, I don't find any package to use 3.0.4 (version jump went
from 2.0.3 to 3.0.5).

So, what is the provenance of that package?

Furthermore, it seems curious that a python2.7 package landed in the python 3.6
site-package directory. Looking at the tumbleweed package:
...
$ rpm -qlp ~/Downloads/python2-Paste-3.4.0-1.1.noarch.rpm \
    | grep Paste-3.4.0-py2.7-nspkg.pth
/usr/lib/python2.7/site-packages/Paste-3.4.0-py2.7-nspkg.pth
...
things land in the correct directory.

So, is there an actual file
/usr/lib/python3.6/site-packages/Paste-3.0.4-py2.7-nspkg.pth on your system?
How did it get there?

---

I think we need to establish whether there's a gdb problem, or whether your
system python is broken.

I locally (on my openSUSE Leap 15.1 system) created a file:
...
$ cat /usr/lib/python3.6/site-packages/Paste-3.4.0-py2.7-nspkg.pth
import sys, types, os;raise NameError('HiThere')
...

and with system gdb, I see:
...
$ gdb -q
Error processing line 1 of
/usr/lib/python3.6/site-packages/Paste-3.4.0-py2.7-nspkg.pth:

  Traceback (most recent call last):
    File "/usr/lib64/python3.6/site.py", line 168, in addpackage
      exec(line)
    File "<string>", line 1, in <module>
  NameError: HiThere

Remainder of file ignored
(gdb) 
...
and with system python, I see that same:
...
$ /usr/bin/python3.6
Error processing line 1 of
/usr/lib/python3.6/site-packages/Paste-3.4.0-py2.7-nspkg.pth:

  Traceback (most recent call last):
    File "/usr/lib64/python3.6/site.py", line 168, in addpackage
      exec(line)
    File "<string>", line 1, in <module>
  NameError: HiThere

Remainder of file ignored
Python 3.6.10 (default, Jan 16 2020, 09:12:04) [GCC] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 
...

So, to me it looks like you have a broken system python. I cannot comment on
the root cause, but it seems increasingly likely that there is no gdb issue
here.