[opensuse-factory] Tumbleweed - nano segmentation fault
All, Running nano in TW results is segmentation fault. Anyone else experience this? Do the maintainers of TW monitor this list? Regards. -- Sudhir Anand
On 05/22/2017 03:01 PM, Sudhir Anand wrote:
All,
Running nano in TW results is segmentation fault. Anyone else experience this?
Do the maintainers of TW monitor this list?
Yes they do, and I can confirm the report. When starting nano under gdb, it reports Program received signal SIGSEGV, Segmentation fault. 0x00007ffff775cc72 in _nc_init_acs_sp () from /lib64/libtinfo.so.6 It appears that libtinfo.so.6 has the problem. I did not load the debug symbols, thus I did not get any further info. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, May 22, 2017 4:11:13 PM EDT Larry Finger wrote:
On 05/22/2017 03:01 PM, Sudhir Anand wrote:
All,
Running nano in TW results is segmentation fault. Anyone else experience this?
Do the maintainers of TW monitor this list?
Yes they do, and I can confirm the report. When starting nano under gdb, it reports Program received signal SIGSEGV, Segmentation fault. 0x00007ffff775cc72 in _nc_init_acs_sp () from /lib64/libtinfo.so.6
It appears that libtinfo.so.6 has the problem. I did not load the debug symbols, thus I did not get any further info.
Larry
Guys, I just installed pico and it work great! Cheers!\n\nRoman\n\nIRC: 551368250 \n============== -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 22.05.2017 um 22:11 schrieb Larry Finger
: Yes they do, and I can confirm the report. When starting nano under gdb, it reports Program received signal SIGSEGV, Segmentation fault. 0x00007ffff775cc72 in _nc_init_acs_sp () from /lib64/libtinfo.so.6
It appears that libtinfo.so.6 has the problem. I did not load the debug symbols, thus I did not get any further info.
After zypper up I had the same problem today with ccmake. It went away after another zypper up (with > 400 upgrades?!)-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/22/2017 04:33 PM, Fabian Wein wrote:
Am 22.05.2017 um 22:11 schrieb Larry Finger
: Yes they do, and I can confirm the report. When starting nano under gdb, it reports Program received signal SIGSEGV, Segmentation fault. 0x00007ffff775cc72 in _nc_init_acs_sp () from /lib64/libtinfo.so.6
It appears that libtinfo.so.6 has the problem. I did not load the debug symbols, thus I did not get any further info.
After zypper up I had the same problem today with ccmake. It went away after another zypper up (with > 400 upgrades?!)--
I just did another update a couple of minutes ago. That yielded nano-2.8.2-2.1.x86_64, which runs correctly. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2017-05-22 at 19:23 -0500, Larry Finger wrote:
On 05/22/2017 04:33 PM, Fabian Wein wrote:
Am 22.05.2017 um 22:11 schrieb Larry Finger
: Yes they do, and I can confirm the report. When starting nano under gdb, it reports Program received signal SIGSEGV, Segmentation fault. 0x00007ffff775cc72 in _nc_init_acs_sp () from /lib64/libtinfo.so.6
It appears that libtinfo.so.6 has the problem. I did not load the debug symbols, thus I did not get any further info.
After zypper up I had the same problem today with ccmake. It went away after another zypper up (with > 400 upgrades?!)--
I just did another update a couple of minutes ago. That yielded nano-2.8.2-2.1.x86_64, which runs correctly.
Larry
Confirmed. Nano works. Thanks to all concerned for such a quick response. Regards. -- Sudhir Anand N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Not sure how pertinent, but on occasion it happens to me as well on 42.2 and 42.3. But only when running in a virtualbox VM. Should I file a ticket? -- View this message in context: http://opensuse.14.x6.nabble.com/Tumbleweed-nano-segmentation-fault-tp508714... Sent from the opensuse-factory mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I'm experiencing same issue with htop
2017-05-22 23:01 GMT+03:00 Sudhir Anand
All,
Running nano in TW results is segmentation fault. Anyone else experience this?
Do the maintainers of TW monitor this list?
Regards.
-- Sudhir Anand
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Andrei, It's likely https://bugzilla.opensuse.org/show_bug.cgi?id=1040271 . Feel free to report these issues as a reply to the original update notification. I think it's going to get more traction that way. Libor On Tue 23-05-17 19:04:19, Andrei Dziahel wrote:
I'm experiencing same issue with htop
2017-05-22 23:01 GMT+03:00 Sudhir Anand
: All,
Running nano in TW results is segmentation fault. Anyone else experience this?
Do the maintainers of TW monitor this list?
Regards.
-- Sudhir Anand
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Libor Pechacek SUSE Labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Andrei Dziahel
-
Fabian Wein
-
Larry Finger
-
Libor Pechacek
-
Luigi Baldoni
-
Roman Bysh
-
Sudhir Anand