touch-packages team mailing list archive

[Benno Schulenberg <benno@xxxxxxxxxxx>]

> It worked before on 15.04 (and before), but broke upgrading to
15.10...

Well, on 15.04 (nano-2.2.6), nano didn't have any file locking.

> env | grep MALLOC returns nothing

Good.

> nano --ignore works fine...

It should, because it ignores the 'set locking' that uou have in your
.nanorc. As a temporary measure you can comment out that setting.

> My computer is a vm from Bytemark over on their bigv platform

Well, when it's a virtual machine, then it's not really a computer.  :)
And yes, then it's likely that it gets its hostname over the network.
But it doesn't matter.  If you can compile from source, please try the
attached patch.

** Patch added: "trims an overlong hostname instead of complaining"
   https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1509081/+attachment/4513012/+files/trim-long-hostname.patch

-- 
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:
  Confirmed

Bug description:
  Description:	Ubuntu 15.10
  Release:	15.10

  nano:
    Installed: 2.4.2-1
    Candidate: 2.4.2-1
    Version table:
   *** 2.4.2-1 0
          500 http://mirror.bytemark.co.uk/ubuntu/ wily/main amd64 Packages
          100 /var/lib/dpkg/status

  
  After upgrading Ubuntu 15.04 to 15.10, when I run nano as root on a file it just segfaults. I'm not having this problem on other 15.04->15.10 upgrades

  strace is https://p.defau.lt/?q7xGwt3HoqB74xTawUUHDA
  catchsegv is https://p.defau.lt/?0SPQY_bDj6F6j1ZKeToQoA

  
  Under gdb with nano-dbgsym installed, it gives

  #0  main (argc=2, argv=0x7fffffffe688) at ../../src/nano.c:2768

  
  If I run it as sudo nano filename.txt, it gives an error as below rather than segfaulting

  [ Couldn't determine hostname for lock file: File name too long ]


  Both my user and root have the same locale settings. I've tried
  regenerating the locales

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1509081/+subscriptions