GNU nano - Bugs: bug #63732, segfault while processing terminfo...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63732: segfault while processing terminfo data
Submitter: | JH <ifiht> | ||
Submitted: | Mon 30 Jan 2023 05:08:35 PM UTC | ||
Severity: | 3 - Normal | Status: | Invalid |
Assigned to: | None | Open/Closed: | Closed |
Mon 06 Feb 2023 08:35:58 AM UTC, comment #5: |
Benno Schulenberg <bens> |
Sun 05 Feb 2023 06:08:03 PM UTC, comment #4: Quick update:
|
JH <ifiht> |
Sun 05 Feb 2023 05:34:54 PM UTC, comment #3: Hey thanks for the help & sorry for the delay, here's the details:
|
JH <ifiht> |
Sun 05 Feb 2023 09:07:58 AM UTC, comment #2: Ping? |
Benno Schulenberg <bens> |
Tue 31 Jan 2023 10:43:17 AM UTC, comment #1: First: what version of nano? Self-compiled? What platform (BSD, Linux)? What basic distro?
|
Benno Schulenberg <bens> |
Mon 30 Jan 2023 05:08:35 PM UTC, original submission:
Running a pretty unique AI/ML setup, but it looks like something in my conda environment is messing up nano - it segfaults even after I've disabled my custom settings, trying to edit a new test file. Here's the strace output:
|
JH <ifiht> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-02-06 | bens | Status | Need Info | Invalid | |
Open/Closed | Open | Closed | |||
2023-02-05 | bens | Summary | Segfault with xterm ENV VARS? | segfault while processing terminfo data | |
2023-01-31 | bens | Status | None | Need Info |
Powered by Savane 3.13-d3ae.
Corresponding source code
Thanks for confirming that it is a linkage problem on your
particular system, and that there's nothing wrong with nano
(when it finds the libraries that it is supposed to find).
If you need LD_LIBRARY_PATH to be set for other things on
your system to work properly, you can try changing the order
of its colon-separated paths, shuffling them until everything
works. If you can't get that to work, you could alias nano
to 'LD_LIBRARY_PATH="" nano', or something similar.
Since it's not a bug in nano, closing.