from:"Benno Schulenberg"

** Changed in: nano (Ubuntu)
   Status: Incomplete => Fix Committed

-- 
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/1539627

Title:
  Buffer underflow in nano 2.4.2-1ubuntu0.1  causes  SIGSEGV

Status in nano package in Ubuntu:
  Fix Committed

Bug description:
  nusch@XPS13:~$ touch .the_test.swp
  nusch@XPS13:~$ nano  the_test
  core dumped
  LANG env is ="pl_PL.UTF" without it it doen't Segfault so error is connected 
with unicode handling.

  Compiling nano from source(apt-get source - so the same version)
  doesn't geneate nano binary which beheaves same way.

  The difference is in libncurses>w< library:
  nusch@XPS13:~$ ldd /bin/nano
   linux-vdso.so.1 =>  (0x7ffe5cb0)
   libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fdec11c5000) << with w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fdec0f9c000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdec0bd1000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdec09cd000)
   /lib64/ld-linux-x86-64.so.2 (0x55cc1e5d6000)
  nusch@XPS13:~$ ldd /bin/nano_from_src
   linux-vdso.so.1 =>  (0x7ffd22d48000)
   libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 
(0x7f75dc891000) << without w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f75dc668000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f75dc29d000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f75dc099000)
   /lib64/ld-linux-x86-64.so.2 (0x55f9b15ce000)

  Backtrace of segfault:
  Program received signal SIGSEGV, Segmentation fault.
  0x00404047 in ?? 
()
  (gdb) bt
  #0  0x00404047 in ?? ()
  #1  0x775d1a40 in __libc_start_main (main=0x403770, argc=2, 
argv=0x7fffe2a8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe298) at libc-start.c:289
  #2  0x00404329 in ?? ()

  Disassembly of that part of code:
    40401d:   0f 84 3c 01 00 00   je 40415f 
<__sprintf_chk@plt+0x9ff>
    404023:   83 7c 24 10 00  cmpDWORD PTR [rsp+0x10],0x0
    404028:   75 0a   jne404034 
<__sprintf_chk@plt+0x8d4>
    40402a:   81 25 1c e8 22 00 ffandDWORD PTR 
[rip+0x22e81c],0xbfff# 632850 
    404031:   bf ff ff
    404034:   48 8b 05 dd e7 22 00movrax,QWORD PTR [rip+0x22e7dd]   
 # 632818 
    40403b:   48 8b 80 90 00 00 00movrax,QWORD PTR [rax+0x90]
    404042:   48 85 c0test   rax,rax
    404045:   74 0b   je 404052 
<__sprintf_chk@plt+0x8f2>
    404047:   83 78 38 00 cmpDWORD PTR [rax+0x38],0x0
    40404b:   7e 05   jle404052 
<__sprintf_chk@plt+0x8f2>
    40404d:   e8 3e fc 00 00  call   413c90 
<__sprintf_chk@plt+0x10530>
    404052:   48 8b 7c 24 20  movrdi,QWORD PTR [rsp+0x20]
    404057:   48 85 fftest   rdi,rdi
    40405a:   0f 8e b5 00 00 00   jle404115 
<__sprintf_chk@plt+0x9b5>
    404060:   48 8b 74 24 28  movrsi,QWORD PTR [rsp+0x28]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 29 15:13:25 2016
  InstallationDate: Installed on 2015-05-08 (266 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nano
  UpgradeStatus: Upgraded to wily on 2015-11-15 (74 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1320461] Re: keybindings do not work when opening multiple files

** Changed in: nano (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
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/1320461

Title:
  keybindings do not work when opening multiple files

Status in nano package in Ubuntu:
  Fix Released

Bug description:
  I think I have found a bug. At least weird behaviour.

  I set my ~/.nanorc to "unbind ^J  main" because I
  find it very annoying when it mangles my text when I
  accidentally press Ctrl+Enter.  

  
  This setup works well for me when I use nano to open  
  
  one file, i.e. "nano foo.tex". However, when I open two files,
  i.e. "nano foo.tex bar.tex", it works for the first file only.
  That is, when I quit the first instance with Ctrl+X and when nano 
  
  has loaded the second file, my nanorc does not seem to be 
  
  respected anymore. I can press Ctrl+Enter and it mangles my text.
  I hope you find this useful and are able to reproduce this issue. 
  

  
  nano --version
  
   GNU nano version 2.2.6 (compiled 14:12:08, Oct  1 2012)  
  
   (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
  
   2008, 2009 Free Software Foundation, Inc.
  
   E-mail: n...@nano-editor.org   Web: http://www.nano-editor.org/  
  
   Compiled options: --disable-wrapping-as-root --enable-color --enable-extra 
--en
  able-multibuffer --enable-nanorc --enable-utf8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nano 2.2.6-1ubuntu1
  Uname: Linux 3.14.0-031400rc4-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat May 17 12:21:54 2014
  InstallationDate: Installed on 2014-01-22 (114 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MarkForUpload: True
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.nanorc: [modified]
  mtime.conffile..etc.nanorc: 2014-02-26T11:29:03.194042

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1569964] Re: On the console block characters are shown instead of pretty quotes

See https://bugs.launchpad.net/ubuntu/+source/console-
setup/+bug/657551/comments/23 .

The recipe more explicitly:

sudo cp /usr/share/consolefonts/Uni2-Fixed16.psf.gz /etc/console-setup/
sudo gunzip etc/console-setup/Uni2-Fixed16.psf.gz
sudo sed -i 's:^CODESET=.*:CODESET="Uni2":' /etc/default/console-setup

And this comment gives, I think, a hint at the proper solution:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/609775/comments/4
 --
that is: the installer should figure out which consolefont to install.

-- 
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/1569964

Title:
  On the console block characters are shown instead of pretty quotes

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04 dev with nano 2.5.3-2 and on going to the
  console and setting LANG to de_DE.UTF-8 I'm noticing that changing an
  existing file with nano and aborting the changes with CTRL + X does
  show before and after the word "Nein" a black square instead of the
  characters „ and “ as they are shown on a terminal.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1522598] Re: nano crashes when resizing terminal

In fact, it isn't fixed.  It just happened that on my two machines I use
VTE-based terminals, and somehow they don't allow the window to be made
smaller than four columns.  But xterm allows reducing the window to just
one column -- and with anything less than four columns, nano goes down.

Nano goes down deliberately when the window gets narrower than four
columns, but... I don't think it should do that.  No other console
editor does that.  Vim and joe and Emacs all stay alive even in a one-
column terminal.  So I think nano should do the same.  Emacs stops
outputting anything to the screen when the terminal is narrower than six
columns (probably because by then things are entirely unreadable).  Nano
could do something similar, also because it is an easy fix: simply skip
all display activity when COLS < 4.

-- 
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/1522598

Title:
  nano crashes when resizing terminal

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  See video here: https://vid.me/5ksi

  Whenever I resize the terminal that nano is running in to a very small
  size, it will crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nano 2.2.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-37.42~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  3 22:57:39 2015
  InstallationDate: Installed on 2015-11-09 (24 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1522598] Re: nano crashes when resizing terminal

** Changed in: nano (Ubuntu)
   Status: Fix Committed => Confirmed

-- 
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/1522598

Title:
  nano crashes when resizing terminal

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  See video here: https://vid.me/5ksi

  Whenever I resize the terminal that nano is running in to a very small
  size, it will crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nano 2.2.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-37.42~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  3 22:57:39 2015
  InstallationDate: Installed on 2015-11-09 (24 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1595607] Re: /bin/nano:* Error in `nano': free(): invalid next size (normal): ADDR *

2016-06-25 Thread Benno Schulenberg

I am quite willing to work on this issue, but... don't make me jump
through hoops just to see the crash report.  (Take an example from
Fedora, where such reports are freely accessible (for example,
https://retrace.fedoraproject.org/faf/reports/1181921/).  I don't need
heaps of information -- a backtrace is normally enough.)

Anyway, I'm guessing your users are hitting a bug that is fixed by the
first patch attached to this message: https://lists.gnu.org/archive/html
/nano-devel/2016-04/msg00075.html.  That patch (and the other three)
were already applied to nano in Debian.

-- 
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/1595607

Title:
  /bin/nano:*** Error in `nano': free(): invalid next size (normal):
  ADDR ***

Status in nano package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/d609e39daa79867af99f7c1c75f3db7b998971d9
  contains more details.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1572807] Re: /bin/nano:* Error in `nano': double free or corruption (!prev): ADDR *

2016-04-22 Thread Benno Schulenberg

I am logged in on Launchpad, why must I log in again (on Ubuntu One) to
access the above information?  I do not want to log in again, nor create
another account.  Just give me the info about the problem.

-- 
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/1572807

Title:
  /bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR
  ***

Status in nano package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/7dd7f74a72fca06513544d8af66b623efa15b26c
  contains more details.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1569964] Re: Malformed characters on the console with LANG=de_DE.UTF-8 are shown

2016-04-18 Thread Benno Schulenberg

I think this bug should instead be filed against the console, against
the font it uses, not against each individual package that uses pretty
quotes.  Really, a modern font should be able to render “” and ‘’ and «»
correctly, also on the console (VT).

** Summary changed:

- Malformed characters on the console with LANG=de_DE.UTF-8 are shown
+ On the console block characters are shown instead of pretty quotes

-- 
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/1569964

Title:
  On the console block characters are shown instead of pretty quotes

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04 dev with nano 2.5.3-2 and on going to the
  console and setting LANG to de_DE.UTF-8 I'm noticing that changing an
  existing file with nano and aborting the changes with CTRL + X does
  show before and after the word "Nein" a black square instead of the
  characters „ and “ as they are shown on a terminal.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539627] Re: Buffer underflow in nano 2.4.2-1ubuntu0.1 causes SIGSEGV

2016-04-16 Thread Benno Schulenberg

Thanks for confirming.  Strangely, I was now able to reproduce the crash
with your recipe on nano-2.4.2.

I think it has been fixed since then by commit 8a06dfa on August 2 last year, 
which was a fix for a Debian bug [1],
which went into 2.4.3 and later.

[1]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787914

** Bug watch added: Debian Bug tracker #787914
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787914

-- 
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/1539627

Title:
  Buffer underflow in nano 2.4.2-1ubuntu0.1  causes  SIGSEGV

Status in nano package in Ubuntu:
  Incomplete

Bug description:
  nusch@XPS13:~$ touch .the_test.swp
  nusch@XPS13:~$ nano  the_test
  core dumped
  LANG env is ="pl_PL.UTF" without it it doen't Segfault so error is connected 
with unicode handling.

  Compiling nano from source(apt-get source - so the same version)
  doesn't geneate nano binary which beheaves same way.

  The difference is in libncurses>w< library:
  nusch@XPS13:~$ ldd /bin/nano
   linux-vdso.so.1 =>  (0x7ffe5cb0)
   libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fdec11c5000) << with w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fdec0f9c000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdec0bd1000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdec09cd000)
   /lib64/ld-linux-x86-64.so.2 (0x55cc1e5d6000)
  nusch@XPS13:~$ ldd /bin/nano_from_src
   linux-vdso.so.1 =>  (0x7ffd22d48000)
   libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 
(0x7f75dc891000) << without w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f75dc668000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f75dc29d000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f75dc099000)
   /lib64/ld-linux-x86-64.so.2 (0x55f9b15ce000)

  Backtrace of segfault:
  Program received signal SIGSEGV, Segmentation fault.
  0x00404047 in ?? 
()
  (gdb) bt
  #0  0x00404047 in ?? ()
  #1  0x775d1a40 in __libc_start_main (main=0x403770, argc=2, 
argv=0x7fffe2a8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe298) at libc-start.c:289
  #2  0x00404329 in ?? ()

  Disassembly of that part of code:
    40401d:   0f 84 3c 01 00 00   je 40415f 
<__sprintf_chk@plt+0x9ff>
    404023:   83 7c 24 10 00  cmpDWORD PTR [rsp+0x10],0x0
    404028:   75 0a   jne404034 
<__sprintf_chk@plt+0x8d4>
    40402a:   81 25 1c e8 22 00 ffandDWORD PTR 
[rip+0x22e81c],0xbfff# 632850 
    404031:   bf ff ff
    404034:   48 8b 05 dd e7 22 00movrax,QWORD PTR [rip+0x22e7dd]   
 # 632818 
    40403b:   48 8b 80 90 00 00 00movrax,QWORD PTR [rax+0x90]
    404042:   48 85 c0test   rax,rax
    404045:   74 0b   je 404052 
<__sprintf_chk@plt+0x8f2>
    404047:   83 78 38 00 cmpDWORD PTR [rax+0x38],0x0
    40404b:   7e 05   jle404052 
<__sprintf_chk@plt+0x8f2>
    40404d:   e8 3e fc 00 00  call   413c90 
<__sprintf_chk@plt+0x10530>
    404052:   48 8b 7c 24 20  movrdi,QWORD PTR [rsp+0x20]
    404057:   48 85 fftest   rdi,rdi
    40405a:   0f 8e b5 00 00 00   jle404115 
<__sprintf_chk@plt+0x9b5>
    404060:   48 8b 74 24 28  movrsi,QWORD PTR [rsp+0x28]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 29 15:13:25 2016
  InstallationDate: Installed on 2015-05-08 (266 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nano
  UpgradeStatus: Upgraded to wily on 2015-11-15 (74 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539627] Re: Buffer underflow in nano 2.4.2-1ubuntu0.1 causes SIGSEGV

Ping?  Bartłomiej?

-- 
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/1539627

Title:
  Buffer underflow in nano 2.4.2-1ubuntu0.1  causes  SIGSEGV

Status in nano package in Ubuntu:
  Incomplete

Bug description:
  nusch@XPS13:~$ touch .the_test.swp
  nusch@XPS13:~$ nano  the_test
  core dumped
  LANG env is ="pl_PL.UTF" without it it doen't Segfault so error is connected 
with unicode handling.

  Compiling nano from source(apt-get source - so the same version)
  doesn't geneate nano binary which beheaves same way.

  The difference is in libncurses>w< library:
  nusch@XPS13:~$ ldd /bin/nano
   linux-vdso.so.1 =>  (0x7ffe5cb0)
   libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fdec11c5000) << with w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fdec0f9c000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdec0bd1000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdec09cd000)
   /lib64/ld-linux-x86-64.so.2 (0x55cc1e5d6000)
  nusch@XPS13:~$ ldd /bin/nano_from_src
   linux-vdso.so.1 =>  (0x7ffd22d48000)
   libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 
(0x7f75dc891000) << without w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f75dc668000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f75dc29d000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f75dc099000)
   /lib64/ld-linux-x86-64.so.2 (0x55f9b15ce000)

  Backtrace of segfault:
  Program received signal SIGSEGV, Segmentation fault.
  0x00404047 in ?? 
()
  (gdb) bt
  #0  0x00404047 in ?? ()
  #1  0x775d1a40 in __libc_start_main (main=0x403770, argc=2, 
argv=0x7fffe2a8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe298) at libc-start.c:289
  #2  0x00404329 in ?? ()

  Disassembly of that part of code:
    40401d:   0f 84 3c 01 00 00   je 40415f 
<__sprintf_chk@plt+0x9ff>
    404023:   83 7c 24 10 00  cmpDWORD PTR [rsp+0x10],0x0
    404028:   75 0a   jne404034 
<__sprintf_chk@plt+0x8d4>
    40402a:   81 25 1c e8 22 00 ffandDWORD PTR 
[rip+0x22e81c],0xbfff# 632850 
    404031:   bf ff ff
    404034:   48 8b 05 dd e7 22 00movrax,QWORD PTR [rip+0x22e7dd]   
 # 632818 
    40403b:   48 8b 80 90 00 00 00movrax,QWORD PTR [rax+0x90]
    404042:   48 85 c0test   rax,rax
    404045:   74 0b   je 404052 
<__sprintf_chk@plt+0x8f2>
    404047:   83 78 38 00 cmpDWORD PTR [rax+0x38],0x0
    40404b:   7e 05   jle404052 
<__sprintf_chk@plt+0x8f2>
    40404d:   e8 3e fc 00 00  call   413c90 
<__sprintf_chk@plt+0x10530>
    404052:   48 8b 7c 24 20  movrdi,QWORD PTR [rsp+0x20]
    404057:   48 85 fftest   rdi,rdi
    40405a:   0f 8e b5 00 00 00   jle404115 
<__sprintf_chk@plt+0x9b5>
    404060:   48 8b 74 24 28  movrsi,QWORD PTR [rsp+0x28]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 29 15:13:25 2016
  InstallationDate: Installed on 2015-05-08 (266 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nano
  UpgradeStatus: Upgraded to wily on 2015-11-15 (74 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1569964] Re: Malformed characters on the console with LANG=de_DE.UTF-8 are shown

Confirmed on an up-to-date Manjaro install, so it is not just an Ubuntu
thing.  And it's not just nano either, because when I do (in a Dutch
locale) for example 'stty cols' (without giving a number), I get an
error message that has those two block characters around cols.  (On a
console, that is.  On a terminal emulator it works fine.)

On a console, the accented letters of French, German, and Spanish seem
okay.  But when I specify Croat as the language...  Try running
'LANGUAGE=hr nano', and then type ^G.  You'll see twenty, thirty, forty
of these block characters.  Apparently the console font leaves something
to be desired.

-- 
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/1569964

Title:
  Malformed characters on the console with LANG=de_DE.UTF-8 are shown

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04 dev with nano 2.5.3-2 and on going to the
  console and setting LANG to de_DE.UTF-8 I'm noticing that changing an
  existing file with nano and aborting the changes with CTRL + X does
  show before and after the word "Nein" a black square instead of the
  characters „ and “ as they are shown on a terminal.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1569964] Re: Malformed characters on the console with LANG=de_DE.UTF-8 are shown

** Changed in: nano (Ubuntu)
   Status: New => Confirmed

-- 
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/1569964

Title:
  Malformed characters on the console with LANG=de_DE.UTF-8 are shown

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04 dev with nano 2.5.3-2 and on going to the
  console and setting LANG to de_DE.UTF-8 I'm noticing that changing an
  existing file with nano and aborting the changes with CTRL + X does
  show before and after the word "Nein" a black square instead of the
  characters „ and “ as they are shown on a terminal.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1569964] Re: Malformed characters on the console with LANG=de_DE.UTF-8 are shown

Hm.  Did earlier version of nano (for example, 2.2.6 on Lucid) not show
these black squares around Nein?  Because those pretty double quotes
have been there in the German translation of nano since at least 2009.
If not, did you maybe change the font that is used on the console?  Or
maybe Ubuntu changed the default font there?

-- 
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/1569964

Title:
  Malformed characters on the console with LANG=de_DE.UTF-8 are shown

Status in nano package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04 dev with nano 2.5.3-2 and on going to the
  console and setting LANG to de_DE.UTF-8 I'm noticing that changing an
  existing file with nano and aborting the changes with CTRL + X does
  show before and after the word "Nein" a black square instead of the
  characters „ and “ as they are shown on a terminal.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1554660] Re: request for import-freeze exception for nano-2.5.3-2

2016-03-08 Thread Benno Schulenberg

Oh, forgot to say: it also has more complete translations.

-- 
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/1554660

Title:
  request for import-freeze exception for nano-2.5.3-2

Status in nano package in Ubuntu:
  New

Bug description:
  Nano-2.5.2 has an annoying bug: the cursor is visible in the help
  screens (^G) and in the file browser (^R ^T).  Nano-2.5.3 fixes that.
  2.5.3 also fixes two segfaults that can occur in rare situations
  (editing very large files, and certain errors in the nanorc file).  It
  fixes a few other small bugs too which would be nice /not/ to have in
  an LTS release.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1554660] Re: request for import-freeze exception for nano-2.5.3-2

2016-03-08 Thread Benno Schulenberg

Fixes slowness in the file browser in big directories:
* src/browser.c (do_browser, browser_refresh): Rebuild the file list
only when necessary, not for each and every cursor movement. This
fixes Savannah bug #47133.

Fixes segfault when editing very large files:
* src/files.c (save_poshistory): Allocate enough space for printing
out the line and column numbers. This fixes Savannah bug #47135.

Hides the cursor in the help screens and file browser:
* src/*.c: Switch the cursor on and off at the appropriate moments,
so that it no longer shows in the help screen nor in the file list.
This fixes Savannah bug #47126.

Fixes a segfault when the header command is quoteless:
* src/rcfile.c (parse_header_exp): Don't continue when something is
wrong -- skip the rest of the line. This fixes Savannah bug #47289.

The last fix is not in 2.5.3 itself, but it /is/ in 2.5.3-2 in Debian
Testing. So please sync with that for Xenial.

** Patch added: "diff of the changelog between 2.5.2 and 2.5.3"

https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1554660/+attachment/4593019/+files/changelog.diff

--
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/1554660

Title:
request for import-freeze exception for nano-2.5.3-2

Status in nano package in Ubuntu:
New

Bug description:
Nano-2.5.2 has an annoying bug: the cursor is visible in the help
screens (^G) and in the file browser (^R ^T). Nano-2.5.3 fixes that.
2.5.3 also fixes two segfaults that can occur in rare situations
(editing very large files, and certain errors in the nanorc file). It
fixes a few other small bugs too which would be nice /not/ to have in
an LTS release.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1554660] [NEW] request for import-freeze exception for nano-2.5.3-2

2016-03-08 Thread Benno Schulenberg

Public bug reported:

Nano-2.5.2 has an annoying bug: the cursor is visible in the help
screens (^G) and in the file browser (^R ^T).  Nano-2.5.3 fixes that.
2.5.3 also fixes two segfaults that can occur in rare situations
(editing very large files, and certain errors in the nanorc file).  It
fixes a few other small bugs too which would be nice /not/ to have in an
LTS release.

** Affects: nano (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1554660

Title:
  request for import-freeze exception for nano-2.5.3-2

Status in nano package in Ubuntu:
  New

Bug description:
  Nano-2.5.2 has an annoying bug: the cursor is visible in the help
  screens (^G) and in the file browser (^R ^T).  Nano-2.5.3 fixes that.
  2.5.3 also fixes two segfaults that can occur in rare situations
  (editing very large files, and certain errors in the nanorc file).  It
  fixes a few other small bugs too which would be nice /not/ to have in
  an LTS release.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539627] Re: Buffer underflow in nano 2.4.2-1ubuntu0.1 causes SIGSEGV

I don't use Ubuntu's package; I only run nano built from source.
This is what 'ldd /usr/local/bin/nano' says here:

linux-gate.so.1 =>  (0x00d0b000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0x005dc000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x0011)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0x0029a000)
/lib/ld-linux.so.2 (0x00d89000)

So, it also uses wide curses (w = wide).

Do you still have the old nano, the one that segfaults?
If yes, could you then provide the output of 'locale',
and of 'touch .XXX.swp && nano --ignore --locking XXX'.

-- 
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/1539627

Title:
  Buffer underflow in nano 2.4.2-1ubuntu0.1  causes  SIGSEGV

Status in nano package in Ubuntu:
  Incomplete

Bug description:
  nusch@XPS13:~$ touch .the_test.swp
  nusch@XPS13:~$ nano  the_test
  core dumped
  LANG env is ="pl_PL.UTF" without it it doen't Segfault so error is connected 
with unicode handling.

  Compiling nano from source(apt-get source - so the same version)
  doesn't geneate nano binary which beheaves same way.

  The difference is in libncurses>w< library:
  nusch@XPS13:~$ ldd /bin/nano
   linux-vdso.so.1 =>  (0x7ffe5cb0)
   libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fdec11c5000) << with w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fdec0f9c000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdec0bd1000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdec09cd000)
   /lib64/ld-linux-x86-64.so.2 (0x55cc1e5d6000)
  nusch@XPS13:~$ ldd /bin/nano_from_src
   linux-vdso.so.1 =>  (0x7ffd22d48000)
   libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 
(0x7f75dc891000) << without w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f75dc668000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f75dc29d000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f75dc099000)
   /lib64/ld-linux-x86-64.so.2 (0x55f9b15ce000)

  Backtrace of segfault:
  Program received signal SIGSEGV, Segmentation fault.
  0x00404047 in ?? 
()
  (gdb) bt
  #0  0x00404047 in ?? ()
  #1  0x775d1a40 in __libc_start_main (main=0x403770, argc=2, 
argv=0x7fffe2a8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe298) at libc-start.c:289
  #2  0x00404329 in ?? ()

  Disassembly of that part of code:
    40401d:   0f 84 3c 01 00 00   je 40415f 
<__sprintf_chk@plt+0x9ff>
    404023:   83 7c 24 10 00  cmpDWORD PTR [rsp+0x10],0x0
    404028:   75 0a   jne404034 
<__sprintf_chk@plt+0x8d4>
    40402a:   81 25 1c e8 22 00 ffandDWORD PTR 
[rip+0x22e81c],0xbfff# 632850 
    404031:   bf ff ff
    404034:   48 8b 05 dd e7 22 00movrax,QWORD PTR [rip+0x22e7dd]   
 # 632818 
    40403b:   48 8b 80 90 00 00 00movrax,QWORD PTR [rax+0x90]
    404042:   48 85 c0test   rax,rax
    404045:   74 0b   je 404052 
<__sprintf_chk@plt+0x8f2>
    404047:   83 78 38 00 cmpDWORD PTR [rax+0x38],0x0
    40404b:   7e 05   jle404052 
<__sprintf_chk@plt+0x8f2>
    40404d:   e8 3e fc 00 00  call   413c90 
<__sprintf_chk@plt+0x10530>
    404052:   48 8b 7c 24 20  movrdi,QWORD PTR [rsp+0x20]
    404057:   48 85 fftest   rdi,rdi
    40405a:   0f 8e b5 00 00 00   jle404115 
<__sprintf_chk@plt+0x9b5>
    404060:   48 8b 74 24 28  movrsi,QWORD PTR [rsp+0x28]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 29 15:13:25 2016
  InstallationDate: Installed on 2015-05-08 (266 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nano
  UpgradeStatus: Upgraded to wily on 2015-11-15 (74 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1320461] Re: keybindings do not work when opening multiple files

It is fixed in Wily and Xenial.

** Changed in: nano (Ubuntu)
   Status: New => Fix Committed

-- 
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/1320461

Title:
  keybindings do not work when opening multiple files

Status in nano package in Ubuntu:
  Fix Committed

Bug description:
  I think I have found a bug. At least weird behaviour.

  I set my ~/.nanorc to "unbind ^J  main" because I
  find it very annoying when it mangles my text when I
  accidentally press Ctrl+Enter.  

  
  This setup works well for me when I use nano to open  
  
  one file, i.e. "nano foo.tex". However, when I open two files,
  i.e. "nano foo.tex bar.tex", it works for the first file only.
  That is, when I quit the first instance with Ctrl+X and when nano 
  
  has loaded the second file, my nanorc does not seem to be 
  
  respected anymore. I can press Ctrl+Enter and it mangles my text.
  I hope you find this useful and are able to reproduce this issue. 
  

  
  nano --version
  
   GNU nano version 2.2.6 (compiled 14:12:08, Oct  1 2012)  
  
   (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
  
   2008, 2009 Free Software Foundation, Inc.
  
   E-mail: n...@nano-editor.org   Web: http://www.nano-editor.org/  
  
   Compiled options: --disable-wrapping-as-root --enable-color --enable-extra 
--en
  able-multibuffer --enable-nanorc --enable-utf8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nano 2.2.6-1ubuntu1
  Uname: Linux 3.14.0-031400rc4-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat May 17 12:21:54 2014
  InstallationDate: Installed on 2014-01-22 (114 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MarkForUpload: True
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.nanorc: [modified]
  mtime.conffile..etc.nanorc: 2014-02-26T11:29:03.194042

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1522598] Re: nano crashes when resizing terminal

It is fixed in Wily and Xenial.

** Changed in: nano (Ubuntu)
   Status: New => Fix Committed

-- 
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/1522598

Title:
  nano crashes when resizing terminal

Status in nano package in Ubuntu:
  Fix Committed

Bug description:
  See video here: https://vid.me/5ksi

  Whenever I resize the terminal that nano is running in to a very small
  size, it will crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nano 2.2.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-37.42~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  3 22:57:39 2015
  InstallationDate: Installed on 2015-11-09 (24 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539627] Re: Buffer underflow in nano 2.4.2-1ubuntu0.1 causes SIGSEGV

Waiting for the info requested in comment #2.

** Changed in: nano (Ubuntu)
   Status: New => Incomplete

-- 
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/1539627

Title:
  Buffer underflow in nano 2.4.2-1ubuntu0.1  causes  SIGSEGV

Status in nano package in Ubuntu:
  Incomplete

Bug description:
  nusch@XPS13:~$ touch .the_test.swp
  nusch@XPS13:~$ nano  the_test
  core dumped
  LANG env is ="pl_PL.UTF" without it it doen't Segfault so error is connected 
with unicode handling.

  Compiling nano from source(apt-get source - so the same version)
  doesn't geneate nano binary which beheaves same way.

  The difference is in libncurses>w< library:
  nusch@XPS13:~$ ldd /bin/nano
   linux-vdso.so.1 =>  (0x7ffe5cb0)
   libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fdec11c5000) << with w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fdec0f9c000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdec0bd1000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdec09cd000)
   /lib64/ld-linux-x86-64.so.2 (0x55cc1e5d6000)
  nusch@XPS13:~$ ldd /bin/nano_from_src
   linux-vdso.so.1 =>  (0x7ffd22d48000)
   libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 
(0x7f75dc891000) << without w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f75dc668000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f75dc29d000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f75dc099000)
   /lib64/ld-linux-x86-64.so.2 (0x55f9b15ce000)

  Backtrace of segfault:
  Program received signal SIGSEGV, Segmentation fault.
  0x00404047 in ?? 
()
  (gdb) bt
  #0  0x00404047 in ?? ()
  #1  0x775d1a40 in __libc_start_main (main=0x403770, argc=2, 
argv=0x7fffe2a8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe298) at libc-start.c:289
  #2  0x00404329 in ?? ()

  Disassembly of that part of code:
    40401d:   0f 84 3c 01 00 00   je 40415f 
<__sprintf_chk@plt+0x9ff>
    404023:   83 7c 24 10 00  cmpDWORD PTR [rsp+0x10],0x0
    404028:   75 0a   jne404034 
<__sprintf_chk@plt+0x8d4>
    40402a:   81 25 1c e8 22 00 ffandDWORD PTR 
[rip+0x22e81c],0xbfff# 632850 
    404031:   bf ff ff
    404034:   48 8b 05 dd e7 22 00movrax,QWORD PTR [rip+0x22e7dd]   
 # 632818 
    40403b:   48 8b 80 90 00 00 00movrax,QWORD PTR [rax+0x90]
    404042:   48 85 c0test   rax,rax
    404045:   74 0b   je 404052 
<__sprintf_chk@plt+0x8f2>
    404047:   83 78 38 00 cmpDWORD PTR [rax+0x38],0x0
    40404b:   7e 05   jle404052 
<__sprintf_chk@plt+0x8f2>
    40404d:   e8 3e fc 00 00  call   413c90 
<__sprintf_chk@plt+0x10530>
    404052:   48 8b 7c 24 20  movrdi,QWORD PTR [rsp+0x20]
    404057:   48 85 fftest   rdi,rdi
    40405a:   0f 8e b5 00 00 00   jle404115 
<__sprintf_chk@plt+0x9b5>
    404060:   48 8b 74 24 28  movrsi,QWORD PTR [rsp+0x28]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 29 15:13:25 2016
  InstallationDate: Installed on 2015-05-08 (266 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nano
  UpgradeStatus: Upgraded to wily on 2015-11-15 (74 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1535478] Re: Nano search History destroyed

2016-02-06 Thread Benno Schulenberg

Okay.   So most likely the history file becoming inaccessible was not
caused by a bug or misfeature in nano, but by the same cause that made
your Ubuntu install stop working.  Closing this as invalid as there is
no way to verify anything any more.

** Changed in: nano (Ubuntu)
   Status: New => Invalid

-- 
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/1535478

Title:
  Nano search History destroyed

Status in nano package in Ubuntu:
  Invalid

Bug description:
  nano gives result:
  Error reading /home/sand/.nano/search_history: Permission denied
  Press Enter to continue

  sudo nano gives result:
  Error reading /home/sand/.nano/search_history: Permission denied
  Press Enter to continue

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nano 2.4.2-1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 18:21:07 2016
  InstallationDate: Installed on 2015-11-23 (56 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nano
  UpgradeStatus: Upgraded to xenial on 2015-11-25 (54 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539627] Re: Buffer underflow in nano 2.4.2-1ubuntu0.1 causes SIGSEGV

2016-01-29 Thread Benno Schulenberg

When I follow your recipe (touch .the_test.swp; nano the_test), I don't
get a segfault but just  an error message on the status bar:

  [ Error reading lock file ./.the_test.swp: Not enough data read ]

Please try the command 'nano --ignore --locking the_test' instead (to
test only the locking mechanism and exclude any other settings).  And
please paste the output of the command 'locale' -- because pl_PL.UTF
does not look like the name of a locale to me.

-- 
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/1539627

Title:
  Buffer underflow in nano 2.4.2-1ubuntu0.1  causes  SIGSEGV

Status in nano package in Ubuntu:
  New

Bug description:
  nusch@XPS13:~$ touch .the_test.swp
  nusch@XPS13:~$ nano  the_test
  core dumped
  LANG env is ="pl_PL.UTF" without it it doen't Segfault so error is connected 
with unicode handling.

  Compiling nano from source(apt-get source - so the same version)
  doesn't geneate nano binary which beheaves same way.

  The difference is in libncurses>w< library:
  nusch@XPS13:~$ ldd /bin/nano
   linux-vdso.so.1 =>  (0x7ffe5cb0)
   libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fdec11c5000) << with w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fdec0f9c000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdec0bd1000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdec09cd000)
   /lib64/ld-linux-x86-64.so.2 (0x55cc1e5d6000)
  nusch@XPS13:~$ ldd /bin/nano_from_src
   linux-vdso.so.1 =>  (0x7ffd22d48000)
   libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 
(0x7f75dc891000) << without w
   libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f75dc668000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f75dc29d000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f75dc099000)
   /lib64/ld-linux-x86-64.so.2 (0x55f9b15ce000)

  Backtrace of segfault:
  Program received signal SIGSEGV, Segmentation fault.
  0x00404047 in ?? 
()
  (gdb) bt
  #0  0x00404047 in ?? ()
  #1  0x775d1a40 in __libc_start_main (main=0x403770, argc=2, 
argv=0x7fffe2a8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe298) at libc-start.c:289
  #2  0x00404329 in ?? ()

  Disassembly of that part of code:
    40401d:   0f 84 3c 01 00 00   je 40415f 
<__sprintf_chk@plt+0x9ff>
    404023:   83 7c 24 10 00  cmpDWORD PTR [rsp+0x10],0x0
    404028:   75 0a   jne404034 
<__sprintf_chk@plt+0x8d4>
    40402a:   81 25 1c e8 22 00 ffandDWORD PTR 
[rip+0x22e81c],0xbfff# 632850 
    404031:   bf ff ff
    404034:   48 8b 05 dd e7 22 00movrax,QWORD PTR [rip+0x22e7dd]   
 # 632818 
    40403b:   48 8b 80 90 00 00 00movrax,QWORD PTR [rax+0x90]
    404042:   48 85 c0test   rax,rax
    404045:   74 0b   je 404052 
<__sprintf_chk@plt+0x8f2>
    404047:   83 78 38 00 cmpDWORD PTR [rax+0x38],0x0
    40404b:   7e 05   jle404052 
<__sprintf_chk@plt+0x8f2>
    40404d:   e8 3e fc 00 00  call   413c90 
<__sprintf_chk@plt+0x10530>
    404052:   48 8b 7c 24 20  movrdi,QWORD PTR [rsp+0x20]
    404057:   48 85 fftest   rdi,rdi
    40405a:   0f 8e b5 00 00 00   jle404115 
<__sprintf_chk@plt+0x9b5>
    404060:   48 8b 74 24 28  movrsi,QWORD PTR [rsp+0x28]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 29 15:13:25 2016
  InstallationDate: Installed on 2015-05-08 (266 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nano
  UpgradeStatus: Upgraded to wily on 2015-11-15 (74 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1522598] Re: nano crashes when resizing terminal

2016-01-22 Thread Benno Schulenberg

Thanks for the report.  This bug has been fixed in nano-2.3.3 and newer.

-- 
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/1522598

Title:
  nano crashes when resizing terminal

Status in nano package in Ubuntu:
  New

Bug description:
  See video here: https://vid.me/5ksi

  Whenever I resize the terminal that nano is running in to a very small
  size, it will crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nano 2.2.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-37.42~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  3 22:57:39 2015
  InstallationDate: Installed on 2015-11-09 (24 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned

2016-01-22 Thread Benno Schulenberg

This has been addressed in nano's SVN, r5580.  In version 2.5.2 and
higher, nano will ignore $HOME when it is effectively running as root,
and will therefore not create or change anything in the home directory
of the user that invokes nano through a plain sudo.

(It also means that it will not use the normal user's .nanorc, but only
the global /etc/nanorc plus the .nanorc file in /root.  Which is kind of
nice, because you can then give a root-privileged nano another
appearance from that of a normal user, by using for example 'set
titlecolor brightwhite,red'.)

-- 
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/1471459

Title:
  First run of nano  creates a  directory in $HOME, if run as sudo will
  be root owned

Status in One Hundred Papercuts:
  Confirmed
Status in nano package in Ubuntu:
  Confirmed

Bug description:
  If nano is started for the first with sudo then a root owned directory named 
.nano is created in the user's $HOME directory.
  If 1st. started as a user then the user owns .nano & ownership will not be 
altered by subsequent use of sudo nano.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.1-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Sat Jul  4 20:06:16 2015
  InstallationDate: Installed on 2015-02-25 (128 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1535478] Re: Nano search History destroyed

2016-01-19 Thread Benno Schulenberg

Sorry, for the first one I meant:

ls -ld /home/sand/.nano

-- 
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/1535478

Title:
  Nano search History destroyed

Status in nano package in Ubuntu:
  New

Bug description:
  nano gives result:
  Error reading /home/sand/.nano/search_history: Permission denied
  Press Enter to continue

  sudo nano gives result:
  Error reading /home/sand/.nano/search_history: Permission denied
  Press Enter to continue

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nano 2.4.2-1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 18:21:07 2016
  InstallationDate: Installed on 2015-11-23 (56 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nano
  UpgradeStatus: Upgraded to xenial on 2015-11-25 (54 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1535478] Re: Nano search History destroyed

2016-01-19 Thread Benno Schulenberg

Could you post the results of these two commands:

ls -l /home/sand/.nano
ls -l /home/sand/.nano/search_history

-- 
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/1535478

Title:
  Nano search History destroyed

Status in nano package in Ubuntu:
  New

Bug description:
  nano gives result:
  Error reading /home/sand/.nano/search_history: Permission denied
  Press Enter to continue

  sudo nano gives result:
  Error reading /home/sand/.nano/search_history: Permission denied
  Press Enter to continue

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nano 2.4.2-1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 18:21:07 2016
  InstallationDate: Installed on 2015-11-23 (56 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nano
  UpgradeStatus: Upgraded to xenial on 2015-11-25 (54 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned

2015-11-17 Thread Benno Schulenberg

Anyone, what does 'grep -e storylog -e poslog /etc/nanorc' on Wily say?

-- 
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/1471459

Title:
  First run of nano  creates a  directory in $HOME, if run as sudo will
  be root owned

Status in One Hundred Papercuts:
  Confirmed
Status in nano package in Ubuntu:
  Confirmed

Bug description:
  If nano is started for the first with sudo then a root owned directory named 
.nano is created in the user's $HOME directory.
  If 1st. started as a user then the user owns .nano & ownership will not be 
altered by subsequent use of sudo nano.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.1-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Sat Jul  4 20:06:16 2015
  InstallationDate: Installed on 2015-02-25 (128 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2015-11-08 Thread Benno Schulenberg

> I've got the same error.

Then please click at the top of this page that you are affected too.

> Could you please provide patch's URL

You can find the patch somewhere on the right.  But this is the direct
URL:

https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1509081/+attachment/4513318/+files
/trim-an-overlong-hostname.patch

> and how-to install ?

No.  You will have to google how to get the source, apply the patch,
compile, and install.  Or wait for Ubuntu to apply the patch and push it
out.  Or change your hostname to something shorter.  Or comment out the
"set locking" in your /etc/nanorc file.

-- 
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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2015-11-06 Thread Benno Schulenberg

** Tags added: patch-accepted-upstream

-- 
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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

** Patch removed: "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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

> but it is in the /etc/nanorc file

Ubuntu sets 'locking' by default?  What's the output of 'grep locking
/etc/nanorc'?

> files.c: In function ‘write_lockfile’:
> files.c:149:6: error: label ‘free_and_fail’ used but not defined
>   goto free_and_fail;

Ah.  But then applying the patch should have failed.  Did you edit the
file by hand?

Nevermind.  See the updated patch for version 2.4.2.  (Yes, sorry, SVN
is far ahead of 2.4.2 -- there should have been a 2.4.3 two months ago.)


** Patch added: "trims an overlong hostname instead of complaining"
   
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1509081/+attachment/4513318/+files/trim-an-overlong-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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

> ./configure: line 8316: syntax error near unexpected token `NCURSESW,'
> ./configure: line 8316: ` PKG_CHECK_MODULES(NCURSESW, ncursesw,'

Oh dear, autoconf stuff.  Could you post your ./configure to nano-devel
-- this error not directly related to this bug, so let's take it
elsewhere.  On that list (https://lists.gnu.org/mailman/listinfo/nano-
devel) there will be people who understand autoconf.

-- 
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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

> The patch works!

Thanks for testing.  The patch will go into SVN soon, it will be in
2.4.3.  But this newer version will not make it into Wily, so some
Ubuntu maintainer will have to apply the attached patch to 2.4.2 and
release an updated ubuntu version of nano-2.4.2.

-- 
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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

Can you attach a strace of a run of 'nano --ignore' (without a
filename)?  Is your computer part of some network, does it need to ask
the network about its hostname?  What is the output of 'env | grep
MALLOC'?

-- 
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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

Sorry, that was a silly request.  What is needed of course is a strace
of: 'nano --ignore --locking filename'.

-- 
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=0x7fffe688) 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

> 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=0x7fffe688) 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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned

Paul, when you temporarily move ~/.nano and ~/.nanorc to different
names, does a run of 'sudo nano' then create a new ~/.nano?

-- 
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/1471459

Title:
  First run of nano  creates a  directory in $HOME, if run as sudo will
  be root owned

Status in One Hundred Papercuts:
  Confirmed
Status in nano package in Ubuntu:
  Confirmed

Bug description:
  If nano is started for the first with sudo then a root owned directory named 
.nano is created in the user's $HOME directory.
  If 1st. started as a user then the user owns .nano & ownership will not be 
altered by subsequent use of sudo nano.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.1-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Sat Jul  4 20:06:16 2015
  InstallationDate: Installed on 2015-02-25 (128 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned

2015-07-12 Thread Benno Schulenberg

It turns out that Ubuntu carries a patch for sudo that Debian doesn't: see 
keep_home_by_default.patch [1].
See also the changelog [2], somewhere in item 72.  So I think one should ask 
the Ubuntu maintainer of sudo what the motivation for this patch is.  And if 
there is no strong reason for it, ask him to drop it.  That would solve this 
issue.

[1] 
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/sudo/wily-proposed/files/head:/debian/patches/
[2] https://code.launchpad.net/~ubuntu-branches/ubuntu/wily/sudo/wily

-- 
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/1471459

Title:
  First run of nano  creates a  directory in $HOME, if run as sudo will
  be root owned

Status in One Hundred Papercuts:
  Confirmed
Status in nano package in Ubuntu:
  Confirmed

Bug description:
  If nano is started for the first with sudo then a root owned directory named 
.nano is created in the user's $HOME directory.
  If 1st. started as a user then the user owns .nano  ownership will not be 
altered by subsequent use of sudo nano.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.1-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Sat Jul  4 20:06:16 2015
  InstallationDate: Installed on 2015-02-25 (128 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned

2015-07-10 Thread Benno Schulenberg

For those affected by the bug, could you please paste the output of
'sudo sudo -V | head -1', and of 'sudo sudo -V | grep -e ve: -e HOME',
and of 'sudo grep -v ^# /etc/sudoers'?  Because if all things are at
their defaults, the sudo of Wily shouldn't be preserving HOME but should
be setting it to the home directory of root instead.

-- 
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/1471459

Title:
  First run of nano  creates a  directory in $HOME, if run as sudo will
  be root owned

Status in One Hundred Papercuts:
  Confirmed
Status in nano package in Ubuntu:
  Confirmed

Bug description:
  If nano is started for the first with sudo then a root owned directory named 
.nano is created in the user's $HOME directory.
  If 1st. started as a user then the user owns .nano  ownership will not be 
altered by subsequent use of sudo nano.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.1-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Sat Jul  4 20:06:16 2015
  InstallationDate: Installed on 2015-02-25 (128 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned

2015-07-08 Thread Benno Schulenberg

Current nano (2.4.2) will only check for the existence of $HOME/.nano/
(and create it when it doesn't exist) when 'set historylog' or 'set
poslog' are set in the $HOME/.nanorc file (or when the -H or -P options
are used on the command line).  But... when nano is used for the very
first time (with sudo), how come there is already a .nanorc file?  Does
Ubuntu give you a default one?  Or do they tell you to create a .nanorc
before starting to use nano?

Maybe Ubuntu could consider adding an empty .nano dir to the skeleton
dir for each new user?

-- 
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/1471459

Title:
  First run of nano  creates a  directory in $HOME, if run as sudo will
  be root owned

Status in One Hundred Papercuts:
  Confirmed
Status in nano package in Ubuntu:
  Confirmed

Bug description:
  If nano is started for the first with sudo then a root owned directory named 
.nano is created in the user's $HOME directory.
  If 1st. started as a user then the user owns .nano  ownership will not be 
altered by subsequent use of sudo nano.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nano 2.4.1-1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Sat Jul  4 20:06:16 2015
  InstallationDate: Installed on 2015-02-25 (128 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1361131] Re: constantly flashing bright green while typing

2015-03-30 Thread Benno Schulenberg

Nano colours the things on the screen using just the regular expressions
specified in the relevant syntax file.  There is no way that these
regexes can take the position of the cursor into account.  (Well, not
without a major and ugly patch, and that for just one special case.)
So... unless you are willing to write the 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/1361131

Title:
  constantly flashing bright green while typing

Status in nano package in Ubuntu:
  New

Bug description:
  While editing a shell script (.sh file) nano colours trailing spaces
  bright green.

  It also considers spaces that have just been typed to be trailing
  spaces.

  This results in constant flashing bright green while typing, which is
  both distracting and annoying.

  It's at its most ridiculous when typing comments (for which trailing
  whitespace is obviously completely irrelevant), but is also irritating
  any time you happen to look at what you're typing. Which for me is, as
  it happens, all the time.

  Ideal solution: only display trailing whitespace if the user is not,
  you know, still typing on that line, with the cursor right there.

  Easy solution: just shut up about the damn spaces already.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1361131] Re: constantly flashing bright green while typing

2015-03-28 Thread Benno Schulenberg

Code is inspected far more often than it is written, and when inspecting
code, some people do want to be alerted to trailing whitespace.  So
that's why it is in several of the *.nanorc files.  However, those files
in /usr/share/nano are just examples -- they are meant to be customized
by the user.  Most distributions, however, include and activate them by
default.

By the way, it is not necessary to edit the files in /usr/share/nano;
you can instead redefine any syntax in your ~/.nanorc: just put in
'syntax sh \.sh$' and follow it by the color commands that you do
want.

(In newer nanos (2.4.0 and higher) there is no need to completely
redefine a syntax; you can just add or override things with
'extendsyntax'.  In your case you would put 'extendsyntax sh color
black, [[:space:]]+$' to get rid of the trailing-whitespace
colouring.)

If, when reading code, you do want trailing whitespace to be
highlighted, you can just toggle syntax colouring off with Alt+Y while
you are typing the code, and toggle it back on when you are done
writing.

Okay, all that is selfhelp.  But if you think that for most people the
colouring of trailing whitespace should never be the default, you could
report a bug to nano itself (https://savannah.gnu.org/bugs/?group=nano)
or send an email to its development list
(https://lists.gnu.org/mailman/listinfo/nano-devel).

-- 
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/1361131

Title:
  constantly flashing bright green while typing

Status in nano package in Ubuntu:
  New

Bug description:
  While editing a shell script (.sh file) nano colours trailing spaces
  bright green.

  It also considers spaces that have just been typed to be trailing
  spaces.

  This results in constant flashing bright green while typing, which is
  both distracting and annoying.

  It's at its most ridiculous when typing comments (for which trailing
  whitespace is obviously completely irrelevant), but is also irritating
  any time you happen to look at what you're typing. Which for me is, as
  it happens, all the time.

  Ideal solution: only display trailing whitespace if the user is not,
  you know, still typing on that line, with the cursor right there.

  Easy solution: just shut up about the damn spaces already.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300565] Re: please syntax highlight debdiff files

2015-03-27 Thread Benno Schulenberg

Okay, fixed in SVN.  It will work out of the box in nano 2.4.1 and
higher.

-- 
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/1300565

Title:
  please syntax highlight debdiff files

Status in nano package in Ubuntu:
  New

Bug description:
  nano source highlights diff and patch files.  It would be nice if it
  did the same with debdiff files.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300565] Re: please syntax highlight debdiff files

2015-03-26 Thread Benno Schulenberg

In reply to comment #4: If in /usr/share/nano/patch.nanorc you change
the line that says syntax patch \.(patch|diff)$ to syntax patch
\.(patch|diff|debdiff)$ -- that is, you add a |debdiff (without the
quotes) -- and save the file (use sudo to edit it), do your debdiff
files then get coloured the way you want?

-- 
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/1300565

Title:
  please syntax highlight debdiff files

Status in nano package in Ubuntu:
  New

Bug description:
  nano source highlights diff and patch files.  It would be nice if it
  did the same with debdiff files.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1320461] Re: keybindings do not work when opening multiple files

I can confirm this issue (the forgetting of an unbind) in version 2.2.6.
It is no longer present in 2.4.0, which was recently released.  It is,
however, not an easy patch to backport.  So with a little patience...
you will be freed from this annoyance in a next version of Ubuntu.

-- 
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/1320461

Title:
  keybindings do not work when opening multiple files

Status in nano package in Ubuntu:
  New

Bug description:
  I think I have found a bug. At least weird behaviour.

  I set my ~/.nanorc to unbind ^J  main because I
  find it very annoying when it mangles my text when I
  accidentally press Ctrl+Enter.  

  
  This setup works well for me when I use nano to open  
  
  one file, i.e. nano foo.tex. However, when I open two files,
  i.e. nano foo.tex bar.tex, it works for the first file only.
  That is, when I quit the first instance with Ctrl+X and when nano 
  
  has loaded the second file, my nanorc does not seem to be 
  
  respected anymore. I can press Ctrl+Enter and it mangles my text.
  I hope you find this useful and are able to reproduce this issue. 
  

  
  nano --version
  
   GNU nano version 2.2.6 (compiled 14:12:08, Oct  1 2012)  
  
   (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
  
   2008, 2009 Free Software Foundation, Inc.
  
   E-mail: n...@nano-editor.org   Web: http://www.nano-editor.org/  
  
   Compiled options: --disable-wrapping-as-root --enable-color --enable-extra 
--en
  able-multibuffer --enable-nanorc --enable-utf8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nano 2.2.6-1ubuntu1
  Uname: Linux 3.14.0-031400rc4-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat May 17 12:21:54 2014
  InstallationDate: Installed on 2014-01-22 (114 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MarkForUpload: True
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.nanorc: [modified]
  mtime.conffile..etc.nanorc: 2014-02-26T11:29:03.194042

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1361131] Re: constantly flashing bright green while typing

If the trailing-whitespace highlighting annoys you, you can edit
/usr/share/nano/sh.nanorc and remove or comment out the line that says:
color ,green [[:space:]]+$.  Problem solved.  (You will then probably
want to do the same for the other *.nanorc files there.)

-- 
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/1361131

Title:
  constantly flashing bright green while typing

Status in nano package in Ubuntu:
  New

Bug description:
  While editing a shell script (.sh file) nano colours trailing spaces
  bright green.

  It also considers spaces that have just been typed to be trailing
  spaces.

  This results in constant flashing bright green while typing, which is
  both distracting and annoying.

  It's at its most ridiculous when typing comments (for which trailing
  whitespace is obviously completely irrelevant), but is also irritating
  any time you happen to look at what you're typing. Which for me is, as
  it happens, all the time.

  Ideal solution: only display trailing whitespace if the user is not,
  you know, still typing on that line, with the cursor right there.

  Easy solution: just shut up about the damn spaces already.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300565] Re: please syntax highlight debdiff files

What's a debdiff file?  Can you add an example?

And would you want it to be coloured in the same manner as normal diff
and patch files?

-- 
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/1300565

Title:
  please syntax highlight debdiff files

Status in nano package in Ubuntu:
  New

Bug description:
  nano source highlights diff and patch files.  It would be nice if it
  did the same with debdiff files.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1045062] Re: No option to save without BOM (Byte Order Mark)

But nano can, just like those other editors, remove the invisible BOM:
when on the first line of the file, press Home and Delete, and save,
and the BOM is gone.  Does this not work for you?

-- 
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/1045062

Title:
  No option to save without BOM (Byte Order Mark)

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  This may be a wishlist type bug.

  Currently, Nano in precise saves with BOM (Byte Order Mark) by
  default.  There is no way within nano to save without BOM, which
  requires me to download remote server documents to this system and
  then update and reupload the documents after using gedit, kate, or
  some other editor.

  This sometimes screws up remote PHP programs and scripts, which means
  it may be prudent to give the option to decide whether to save with or
  without the Byte Order Mark.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nano 2.2.6-1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Sun Sep  2 14:36:54 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 481363] Re: Python syntax formatting incorrectly highlights syntax within quote blocks

This little problem has been solved in nano's SVN.  It should appear in
a future version (2.4.1).

-- 
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/481363

Title:
  Python syntax formatting incorrectly highlights syntax within quote
  blocks

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nano

  when viewing a python file from within nano, all characters after a
  pound sign are still colored as a comment when the line is within a
  quote block.  Everything within a quote block should be colored as a
  string.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300565] Re: please syntax highlight debdiff files