question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Segmentation fault just after startup

See original GitHub issue

Issue Report Checklist

  • Searched the issues page for similar reports
  • Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
  • Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
  • [n/a] Could not reproduce inside jupyter qtconsole (if console-related)
  • Tried basic troubleshooting (if a bug/error)
    • Restarted Spyder
    • Reset preferences with spyder --reset
    • Reinstalled the latest version of Anaconda
    • [n/a] Tried the other applicable steps from the Troubleshooting Guide
  • Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

Spyder starts, the IDE shows briefly, then Spyder segv’s and closes 3-5 seconds later, before the kernel finishes starting. No information is reported at the console other than:

Segmentation fault (core dumped)

I can run qtconsole from the command line (i.e., jupyter qtconsole), and it starts normally.

spyder --reset runs (including the splash screen) and terminates normally.

Versions

  • Spyder version: 4.1.2
  • Python version: 3.7.7
  • Qt version: 5.6.0
  • PyQt version: 5.6.3
  • Operating System name/version: Ubuntu 16.04

Qt and PyQt were rolled back to 5.6.* in this case from the current 5.9 versions because of the “Could not initialize GLX” error. I don’t think this is related to the present issue, since the IDE shows for a few seconds before the segv in this case.

Let me know what else I can provide to help debug! Thanks.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:14 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
CAM-Gerlachcommented, May 9, 2020

Glad to hear! Users like you are the reason we do what we do!

1reaction
agentmorriscommented, May 9, 2020

NP, I consider this fixed for me; Spyder 4 works everywhere except for one archaic machine where Spyder 3 works fine. I call that a win! Thanks for your quick responses…

I do all my dev in Spyder and have since I picked up Python, I’m a super-fan!

Thanks.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Identify what's causing segmentation faults (segfaults)
A segmentation fault (aka segfault) is a common condition that causes programs to crash; they are often associated with a file named core...
Read more >
during startup program exited normally. segmentation fault
I am able to run my C++ program on my local ubuntu vm. But when I try to compile it and run in...
Read more >
Segmentation fault immediately on startup (musl-libc) - GitLab
"Segmentation Fault". Expected result: program to open and start functioning. Actual result: splash screen shows and then the program crashes ...
Read more >
Building with jemalloc causes segmentation fault on startup
Starting inkscape without parameters segfaults on startup without ever showing a gui. Running "inkscape somefile.gif" shows the small window ...
Read more >
Debugging Segmentation Faults and Pointer Problems
"Segmentation Fault (core dumped)" is a pretty vague error message, and it's even worse when strange bugs start appearing that don't cause segmentation ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found