[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-12-10 Thread reedy
Unpacking nano (2.4.2-1ubuntu0.1) over (2.4.2-1) ... Re-enabled locking and now nano doesn't segfault (in default config) on the target machine Tag updated :) Thankyou! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-12-07 Thread reedy
Any chance we could get it backported to 15.10 too please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1509081 Title: nano segfaults as root after upgrade to 15.10

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-05 Thread reedy
The patch works! Got a little confused by caching of the paths, which was returning /usr/local/bin/nano, but without the qualified path, it was using /bin/nano. Easily fixed What happens next? I noticed your thread over at https://lists.gnu.org/archive/html/nano-devel/2015-11/msg0.html - I

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-05 Thread reedy
Post sent to nano-devel too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1509081 Title: nano segfaults as root after upgrade to 15.10 Status in nano package in Ubuntu:

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-05 Thread reedy
Yup, 15.10 seems to. I have never edited the /etc/nanorc file, so I guess it was just updated to the default package maintainers version as per the usual. So the grep gives the obvious output: reedy@ko-kra:~$ grep locking /etc/nanorc set locking reedy@ko-kra:~$ Yeah, I ended up applying

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-04 Thread reedy
Yay, rabbit holes... Checked out from svn, extra packages installed, run autogen, then ./configure is giving ./configure: line 8316: syntax error near unexpected token `NCURSESW,' ./configure: line 8316: ` PKG_CHECK_MODULES(NCURSESW, ncursesw,' root@ko-kra:~/nano# dpkg -l | grep ncurses ii

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-04 Thread reedy
Neither root, nor my user have a .nanorc file, but it is in the /etc/nanorc file Thought I'd just use `apt-get source nano` on wily, but seems that's a few revisions behind the svn repo, as free_and_fail doesn't seem to be defined (else something else is out of date/out of sync) .deps/files.Tpo

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-04 Thread reedy
How does the long path tool help? It worked before on 15.04 (and before), but broke upgrading to 15.10... It shouldn't segfault! env | grep MALLOC returns nothing nano --ignore works fine... `strace -o nano.txt nano --ignore` is http://p.defau.lt/?ggvjOCTok9EfbnKi_XNNBA My computer is a vm

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-04 Thread reedy
`strace -o nano2.txt nano --ignore --locking filename.txt` is http://p.defau.lt/?T04ctRlETH_GkL6kEuqSLA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1509081 Title: nano

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

2015-11-04 Thread reedy
But yeah, nano --ignore works via sudo or as root -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1509081 Title: nano segfaults as root after upgrade to 15.10 Status in nano