[Touch-packages] [Bug 1667929] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 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/1667929 Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in nano package in Ubuntu: Incomplete Bug description: it crashed during software update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nano 2.5.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Feb 25 14:28:00 2017 DpkgHistoryLog: Start-Date: 2017-02-25 14:01:31 Commandline: aptdaemon role='role-commit-packages' sender=':1.34' Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 (4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68) DuplicateSignature: package:nano:2.5.3-2ubuntu2 Setting up nano (2.5.3-2ubuntu2) ... update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid status dpkg: error processing package nano (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: nano Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1667929/+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 1698673] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить
** 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/1698673 Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить Status in nano package in Ubuntu: Incomplete Bug description: 1) Ubuntu 16.04 LTS 2) Nano 2.5.3-2ubuntu2 3) Nothing 4) Start system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nano 2.5.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 16 23:46:17 2017 ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его следует переустановить InstallationDate: Installed on 2017-06-16 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: nano Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1698673/+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 1785475] Re: with LANG=C, fragments of lines get superimposed/intertwined when paging up and down
** 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/1785475 Title: with LANG=C, fragments of lines get superimposed/intertwined when paging up and down Status in nano package in Ubuntu: Incomplete Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1998592] Re: in specific situations, nano can eat characters
(I've updated the description because Launchpad shrinks double blanks into a single blank, breaking the original recipe. The original report is in https://savannah.gnu.org/bugs/?63407.) -- 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/1998592 Title: in specific situations, nano can eat characters Status in nano package in Ubuntu: New Bug description: Reproduction recipe: printf "two words\n second line\n" >words nano --ignore --auto --break +,2 words Then press Enter. See how "t" from the first word has *disappeared*. This is wrong. And what is worse: M-U does not bring the eaten letter back. Attached patch has been applied upstream to fix the issue. Please consider applying it to nano-6.2 in Jammy (22.04), and maybe also to nano-4.8 in Focal (20.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1998592/+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 1998592] [NEW] in specific situations, nano can eat characters
Public bug reported: Reproduction recipe: printf "two words\n second line\n" >words nano --ignore --auto --break +,2 words Then press Enter. See how "t" from the first word has *disappeared*. This is wrong. And what is worse: M-U does not bring the eaten letter back. Attached patch has been applied upstream to fix the issue. Please consider applying it to nano-6.2 in Jammy (22.04), and maybe also to nano-4.8 in Focal (20.04). ** Affects: nano (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream ** Attachment added: "prevent from eating non-blanks" https://bugs.launchpad.net/bugs/1998592/+attachment/5633931/+files/0001-text-upon-Enter-eat-only-lefthand-blanks-not-any-oth.patch ** Description changed: Reproduction recipe: - printf "two words\n second line\n" >words + printf "two words\n second line\n" >words - src/nano --ignore --auto --break +,3 words + nano --ignore --auto --break +,3 words Then press Enter. See how "tw" from the first word has *disappeared*. This is wrong. And what is worse: M-U does not bring the eaten letters back. Attached patch has been applied upstream to fix the issue. Please consider applying it to nano-6.2 in Jammy (22.04), and maybe also to nano-4.8 in Focal (20.04). ** Description changed: Reproduction recipe: - printf "two words\n second line\n" >words + printf "two words\n second line\n" >words - nano --ignore --auto --break +,3 words + nano --ignore --auto --break +,2 words - Then press Enter. See how "tw" from the first word has *disappeared*. - This is wrong. And what is worse: M-U does not bring the eaten letters + Then press Enter. See how "t" from the first word has *disappeared*. This is wrong. And what is worse: M-U does not bring the eaten letter back. Attached patch has been applied upstream to fix the issue. Please consider applying it to nano-6.2 in Jammy (22.04), and maybe also to nano-4.8 in Focal (20.04). ** Description changed: Reproduction recipe: printf "two words\n second line\n" >words nano --ignore --auto --break +,2 words - Then press Enter. See how "t" from the first word has *disappeared*. This is wrong. And what is worse: M-U does not bring the eaten letter + Then press Enter. See how "t" from the first word has *disappeared*. + This is wrong. And what is worse: M-U does not bring the eaten letter back. Attached patch has been applied upstream to fix the issue. Please consider applying it to nano-6.2 in Jammy (22.04), and maybe also to nano-4.8 in Focal (20.04). ** Bug watch added: GNU Savannah Bug Tracker #63407 http://savannah.gnu.org/bugs/?63407 -- 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/1998592 Title: in specific situations, nano can eat characters Status in nano package in Ubuntu: New Bug description: Reproduction recipe: printf "two words\n second line\n" >words nano --ignore --auto --break +,2 words Then press Enter. See how "t" from the first word has *disappeared*. This is wrong. And what is worse: M-U does not bring the eaten letter back. Attached patch has been applied upstream to fix the issue. Please consider applying it to nano-6.2 in Jammy (22.04), and maybe also to nano-4.8 in Focal (20.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1998592/+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)
Thomas? Nano does not add a BOM to any file. If you want to know whether any file contains a BOM, you can start nano with the +1 cursor- positioning directive (like so: nano +1 thefilename) and then type . If the upper right corner then says "Modified", an invisible character (most likely a BOM) was deleted before the first visible one. If so, type ^S and ^X and you're done. If "Modified" does not appear, there is no BOM, and you can simply type ^X to exit. To summarize: to make sure a file does not contain a Byte Order Mark, run 'nano +1' followed by the filename, and type: ^S ^X. -- 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 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
Thanks for the feedback. It's good to know that it works. (And sorry about having had to replace \r with CR_CODE in the patch -- I hadn't checked whether it applied cleanly to 4.8.) When going to make a sync exception, then better wait for 4.9.2 which will come out in two days: it fixes a crash that was introduced in 4.9. (Lots of things are happening under the hood; sometimes a mistake is made.) -- 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/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] Status in nano package in Ubuntu: New Bug description: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi-line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+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 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
Please try the attached patch. Then please report back whether it fixes the issue for you. ** Patch added: "upstream patch to accept LF in a bracketed paste" https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+attachment/5346923/+files/0001-input-accommodate-silly-emulators-that-have-LF-inste.patch ** Tags added: patch patch-accepted-upstream ** Tags added: focal -- 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/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] Status in nano package in Ubuntu: New Bug description: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi-line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+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 1866820] [NEW] crash in nano-4.8 when typing ^6 ^J [patch]
Public bug reported: Nanos since version 4.0 contain a silly oversight: when the user tries to justify an empty region (with ^6 ^J, or similar), nano crashes. Attached upstream patch fixes the problem. Please apply to Focal before it is released. ** Affects: nano (Ubuntu) Importance: Undecided Status: New ** Tags: focal patch patch-accepted-upstream ** Patch added: "upstream patch to avoid a crash upon ^6 ^J" https://bugs.launchpad.net/bugs/1866820/+attachment/5335248/+files/0001-justify-do-not-crash-when-the-user-attempts-to-justi.patch ** 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/1866820 Title: crash in nano-4.8 when typing ^6 ^J [patch] Status in nano package in Ubuntu: New Bug description: Nanos since version 4.0 contain a silly oversight: when the user tries to justify an empty region (with ^6 ^J, or similar), nano crashes. Attached upstream patch fixes the problem. Please apply to Focal before it is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1866820/+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 1858293] Re: Missing repeated characters
Thanks for confirming that the problem was caused by using an older Putty. ** Summary changed: - Missing repeated characters + Missing repeated characters when using old Putty [resolved] ** 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/1858293 Title: Missing repeated characters when using old Putty [resolved] Status in nano package in Ubuntu: Invalid Bug description: Nano 2.9.3 Ubuntu 18.04.3 LTS - Linux 4.14.157-171 armv7l ARMv7 Processor rev 3 (v7l) Ubuntu 18.04.3 LTS - Linux 4.9.196-63 aarch64 Amlogic S922X rev a (4 A73 + 2 A53) This issue is repeatable on more than 6 each different machines of the above configurations. I am using ssh via Putty to log in via terminal screen. I am using nano defaults. I have not changed anything nor do I open with any arguments. I use nano and it's not associated with any extension. It behaves the same for all files, even no extension files. Nano is not changing the file, it's just not displaying correctly. The characters are there and they save properly, they're just not visible on the terminal screen. Using WinSCP presents no issues as I am using my local Windows text editor. If I use vi to view the file there are no problems. If I use cat to view the file there are no problems. If I use tail to view the file there are no problems I do not experience this issue on: Nano 2.5.3 Ubuntu 16.04.6 LTS - Linux 4.14.5-92 armv7l ARMv7 Processor rev 3 (v7l) If I take any file that has repeat characters such as: - ||| Nano 2.9.3 will not display all of the continuous repeat characters in the row. For example: Copy and paste is displayed as: # <-- But end of line is correct If I copy that line from the file in nano editor and paste it into another non nano editor I get: # as the paste result This is the same for all different repeated characters. If I keyboard type ## nano will display it until nano is closed and then the same file is reopened. Then it's same as above, one # but end of line is correct. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ into nano results in displayed: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ while nano is still open. Close the file and view in cat, vi or tail and it is show properly.. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ using vi editor then save file and open file in nano results in: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1858293/+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 1858293] Re: Missing repeated characters
> write(1, "+-\33[7b+\33[25G", 12) = 12 This tells your terminal to draw a "+", followed by a "-" which should then be repeated seven more times (\33[7b), followed by a "+". So, nano (by way of ncurses) gives your terminal a correct sequence of codes to draw the stuff that should be drawn. But apparently your terminal (Putty) does not understand the \33[nb code and ignores it, resulting in a garbled display. Please see https://stackoverflow.com/questions/46507473/ncurses-in- urxvt-does-not-print-repeating-characters. And https://invisible- island.net/ncurses/ncurses.faq.html#xterm_generic (the paragraphs after the table). The problem is in Putty: it says it is an xterm (or xterm-compatible), but it isn't. Solution: set your TERM to what it should be: putty. Look in /usr/share/terminfo/p/ for other possibilities. -- 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/1858293 Title: Missing repeated characters Status in nano package in Ubuntu: New Bug description: Nano 2.9.3 Ubuntu 18.04.3 LTS - Linux 4.14.157-171 armv7l ARMv7 Processor rev 3 (v7l) Ubuntu 18.04.3 LTS - Linux 4.9.196-63 aarch64 Amlogic S922X rev a (4 A73 + 2 A53) This issue is repeatable on more than 6 each different machines of the above configurations. I am using ssh via Putty to log in via terminal screen. I am using nano defaults. I have not changed anything nor do I open with any arguments. I use nano and it's not associated with any extension. It behaves the same for all files, even no extension files. Nano is not changing the file, it's just not displaying correctly. The characters are there and they save properly, they're just not visible on the terminal screen. Using WinSCP presents no issues as I am using my local Windows text editor. If I use vi to view the file there are no problems. If I use cat to view the file there are no problems. If I use tail to view the file there are no problems I do not experience this issue on: Nano 2.5.3 Ubuntu 16.04.6 LTS - Linux 4.14.5-92 armv7l ARMv7 Processor rev 3 (v7l) If I take any file that has repeat characters such as: - ||| Nano 2.9.3 will not display all of the continuous repeat characters in the row. For example: Copy and paste is displayed as: # <-- But end of line is correct If I copy that line from the file in nano editor and paste it into another non nano editor I get: # as the paste result This is the same for all different repeated characters. If I keyboard type ## nano will display it until nano is closed and then the same file is reopened. Then it's same as above, one # but end of line is correct. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ into nano results in displayed: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ while nano is still open. Close the file and view in cat, vi or tail and it is show properly.. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ using vi editor then save file and open file in nano results in: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1858293/+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/ListHe
[Touch-packages] [Bug 1853825] Re: ^W ^G ^X fails to redisplay the text being edited
Any chance that this patch can get released into Eoan? It is an upstream 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/1853825 Title: ^W ^G ^X fails to redisplay the text being edited Status in nano package in Ubuntu: New Bug description: There is a silly display bug in nano-4.3 (https://savannah.gnu.org/bugs/?57295): when opening some file (for example, 'nano README') and typing the sequence Ctrl+W Ctrl+G Ctrl+X, the Search help text stays on the screen whereas the text of the README file should be redisplayed. Attached upstream patch fixes this. Please apply to Eoan. (It could be applied to Focal too, but nano-4.6 will be out within a week, so it's probably not worth the effort.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1853825/+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 ***
As the patch for bug #1641592 has been released to Xenial, it means that this bug has been fixed too. ** Changed in: nano (Ubuntu) Status: Confirmed => 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/1572807 Title: /bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR *** Status in nano package in Ubuntu: Fix Released 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 1858293] Re: Missing repeated characters
Thanks for reporting. Please answer the following questions. 1) From what kind of machine are you putty'ing into your Ubuntu 18.04 machines? 2) When putty'ed in, what is the output of 'env | grep TERM'? 3) When putty'ed in, please run 'strace -ewrite -s2000 /bin/nano --ignore 2>TRAIL', paste your seven-line example into nano, then press ^X N, and attach the resultant TRAIL file here. 4) When ssh'ing in from a regular GNU/Linux machine (from an xterm or from a Linux console) to your Ubuntu 18.04 machines, do you observe the same problem? 5) If you build the latest nano-4.7 on one of your 18.04 machines, does the problem still occur when putty'ing in and running nano-4.7? 6) When you putty into an Ubuntu 19.10 machine (if you can find one), does the problem occur there too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1858293 Title: Missing repeated characters Status in nano package in Ubuntu: New Bug description: Nano 2.9.3 Ubuntu 18.04.3 LTS - Linux 4.14.157-171 armv7l ARMv7 Processor rev 3 (v7l) Ubuntu 18.04.3 LTS - Linux 4.9.196-63 aarch64 Amlogic S922X rev a (4 A73 + 2 A53) This issue is repeatable on more than 6 each different machines of the above configurations. I am using ssh via Putty to log in via terminal screen. I am using nano defaults. I have not changed anything nor do I open with any arguments. I use nano and it's not associated with any extension. It behaves the same for all files, even no extension files. Nano is not changing the file, it's just not displaying correctly. The characters are there and they save properly, they're just not visible on the terminal screen. Using WinSCP presents no issues as I am using my local Windows text editor. If I use vi to view the file there are no problems. If I use cat to view the file there are no problems. If I use tail to view the file there are no problems I do not experience this issue on: Nano 2.5.3 Ubuntu 16.04.6 LTS - Linux 4.14.5-92 armv7l ARMv7 Processor rev 3 (v7l) If I take any file that has repeat characters such as: - ||| Nano 2.9.3 will not display all of the continuous repeat characters in the row. For example: Copy and paste is displayed as: # <-- But end of line is correct If I copy that line from the file in nano editor and paste it into another non nano editor I get: # as the paste result This is the same for all different repeated characters. If I keyboard type ## nano will display it until nano is closed and then the same file is reopened. Then it's same as above, one # but end of line is correct. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ into nano results in displayed: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ while nano is still open. Close the file and view in cat, vi or tail and it is show properly.. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ using vi editor then save file and open file in nano results in: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1858293/+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 1853825] [NEW] ^W ^G ^X fails to redisplay the text being edited
Public bug reported: There is a silly display bug in nano-4.3 (https://savannah.gnu.org/bugs/?57295): when opening some file (for example, 'nano README') and typing the sequence Ctrl+W Ctrl+G Ctrl+X, the Search help text stays on the screen whereas the text of the README file should be redisplayed. Attached upstream patch fixes this. Please apply to Eoan. (It could be applied to Focal too, but nano-4.6 will be out within a week, so it's probably not worth the effort.) ** Affects: nano (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Patch added: "fix display bug after invoking ^G help" https://bugs.launchpad.net/bugs/1853825/+attachment/5307655/+files/0001-display-do-refresh-the-edit-window-when-exiting-from.patch ** Tags added: eoan -- 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/1853825 Title: ^W ^G ^X fails to redisplay the text being edited Status in nano package in Ubuntu: New Bug description: There is a silly display bug in nano-4.3 (https://savannah.gnu.org/bugs/?57295): when opening some file (for example, 'nano README') and typing the sequence Ctrl+W Ctrl+G Ctrl+X, the Search help text stays on the screen whereas the text of the README file should be redisplayed. Attached upstream patch fixes this. Please apply to Eoan. (It could be applied to Focal too, but nano-4.6 will be out within a week, so it's probably not worth the effort.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1853825/+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 1785475] Re: with LANG=C, fragments of lines get superimposed/intertwined when paging up and down
I've given you my IP address, but am unable to ssh into your server. -- 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/1785475 Title: with LANG=C, fragments of lines get superimposed/intertwined when paging up and down Status in nano package in Ubuntu: New Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: with LANG=C, fragments of lines get superimposed/intertwined when paging up and down
** Summary changed: - Scrolling in files gives display isues + with LANG=C, fragments of lines get superimposed/intertwined when paging up and down -- 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/1785475 Title: with LANG=C, fragments of lines get superimposed/intertwined when paging up and down Status in nano package in Ubuntu: New Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: Scrolling in files gives display isues
Hmmm... When the line containing "Minimum" and the second "vpn" line should 'overlap' when doing a single PageDown, then your terminal must have 61 rows (when using --ignorercfiles). But... when I alternately do a PageDown and a PageUp, and look how exactly those two lines would interweave, then I can never see "vpn IN NSnimum ( ns2urs)", as you have posted, no matter what tabsize I use. With --tabsize=4, it would display "NSinimumns2__4_hours)" (where an underscore stands for a space), and with --tabsize=5 it would display "NSimum_(__ns2hours)" -- *if* tabs wouldn't be cleared properly. So... how you can ever see "vpn IN NSnimum ( ns2urs)" without the "nimum" jumping left or right is a mystery to me. Can you give me an account on one of your servers, complete with the "faulty" environment that triggers the effect, so that I can see it for myself? A ssh key is attached. ** Attachment added: "Benno's ssh public key" https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1785475/+attachment/5174358/+files/bennos-ssh.pub -- 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/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: New Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: Scrolling in files gives display isues
The bug *seemingly* affects three people: the reporter (you), one person who was clearly a fake, and one other person "confirmed" it by clicking that he/she is affected too. But an anonymous person whom I can't ask questions doesn't count as confirmation for me. And most likely that anonymous person is a sockpuppet too, because confirming a report so soon after it was filed... As I said: run 'stty size' on your terminal, and paste the output. When setting LANG=C, I still cannot reproduce the effect that you see. What did you change LANG into to "fix" the problem? So... in fact there is no problem? It was just an anomaly in your setup, as I suspected? You saw the effect on new installs of Ubuntu 18.04 server. Can you make a fresh install (on a random, free partition) and take note of the choices that you make? So that I stand a chance of reproducing your environment. -- 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/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: New Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: Scrolling in files gives display isues
Thanks for the files you sent via private email. However, I am unable to reproduce the effect that you see. Also, this report has *not* been confirmed. You are the only person who is seeing this effect -- or have only one machine that displays this behavior. I am suspecting an anomaly in your setup, which (when you move to another page) makes ncurses think that there are already spaces on the rows that it should draw and therefore does not bother to draw them. What is the output of 'stty size'? Do you use 'stty' to change the number of columns or rows from what they actually are? Further, do you see the effect also when you use 'nano --ignore' instead of plain 'nano'? And what when you run 'LANGUAGE=en nano --ignore'? The machine that you see the effect on, is it a server? Did you see this effect since 18.04 was installed, or did it develop later? How come that the locale of that machine is set to all "C"? Because as far as I know, most distros default to a Unicode locale nowadays. ** Changed in: nano (Ubuntu) Status: Confirmed => 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/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: New Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: Scrolling in files gives display isues
Dang. How hard is it to answer *all* questions? Provide the full output of 'locale' on the affected machine. ** Changed in: nano (Ubuntu) Status: Confirmed => 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/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: Incomplete Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: Scrolling in files gives display isues
By the way: please delete your sockpuppet bastiaan82. -- 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/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: Incomplete Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: Scrolling in files gives display isues
Please answer also the other questions: which terminal, and the full output of 'locale'. Further, did you fiddle with your system? Have you symlinked some libraries? Also, are you able to build nano from source? If so, please try building the latest 2.9.8, and see how it fares. -- 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/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: Confirmed Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1785475] Re: Scrolling in files gives display isues
On which terminal emulator are you seeing this effect? What is the output of the 'locale' command? Can you attach the DNS zone file you were looking at? Can you search your system for a file that contains the word fragments "every", "fresh", "urs", "xpire" and "nimum"? Because it seems the zone file gets interleaved with another. -- 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/1785475 Title: Scrolling in files gives display isues Status in nano package in Ubuntu: Confirmed Bug description: By scrolling down a file the layout is screwd up. example i scrole in zone file of dns server i get this : dhcpIN NS ns1 dhcpIN NS ns2 dhcp IN NS every cns3 dhcp IN NSfresh (ns4urs) vpn IN NSxpirens1 vpn IN NSnimum (ns2urs) vpn IN NS ns3 vpn me servers IN NS ns4 But i realy looks like this : dhcpIN NS ns1 dhcpIN NS ns2 dhcpIN NS ns3 dhcpIN NS ns4 vpn IN NS ns1 vpn IN NS ns2 vpn IN NS ns3 vpn IN NS ns4 When i edit and save everyting is stored correctly but on display it's wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nano 2.9.3-2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 5 15:54:27 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash 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/1785475/+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 1753724] Re: nano fails to redo a file insertion
** Tags added: artful bionic -- 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/1753724 Title: nano fails to redo a file insertion Status in nano package in Ubuntu: New Bug description: In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to redo a file insertion can fail with the message: "[ Gone undo line -- please report a bug ]". To reproduce, run 'nano --ignore' and type: Ctrl+R /etc/issue Alt+U Alt+E Attached upstream patch fixes the issue. References: https://savannah.gnu.org/bugs/?53272 http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1753724/+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 1753724] [NEW] nano fails to redo a file insertion
Public bug reported: In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to redo a file insertion can fail with the message: "[ Gone undo line -- please report a bug ]". To reproduce, run 'nano --ignore' and type: Ctrl+R /etc/issue Alt+U Alt+E Attached upstream patch fixes the issue. References: https://savannah.gnu.org/bugs/?53272 http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html ** Affects: nano (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-undo-when-redoing-don-t-try-to-find-a-line-number-th.patch" https://bugs.launchpad.net/bugs/1753724/+attachment/5070577/+files/0001-undo-when-redoing-don-t-try-to-find-a-line-number-th.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/1753724 Title: nano fails to redo a file insertion Status in nano package in Ubuntu: New Bug description: In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to redo a file insertion can fail with the message: "[ Gone undo line -- please report a bug ]". To reproduce, run 'nano --ignore' and type: Ctrl+R /etc/issue Alt+U Alt+E Attached upstream patch fixes the issue. References: https://savannah.gnu.org/bugs/?53272 http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1753724/+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 1710511] Re: nano crashed with SIGSEGV in get_sysdep_segment_value()
The crash was in libc (while looking up the translation of a string), not in nano itself. Could it be that you updated libc shortly before the crash? As this crash happened in an alpha release, and if you cannot reproduce it any more in 17.10 proper, I think this bug can be closed. -- 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/1710511 Title: nano crashed with SIGSEGV in get_sysdep_segment_value() Status in nano package in Ubuntu: New Bug description: When update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nano 2.8.6-2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 20:22:31 2017 ExecutablePath: /bin/nano InstallationDate: Installed on 2017-08-09 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170806) ProcCmdline: nano /etc/defaults/grub SegvAnalysis: Segfault happened at: 0x7fdda72da0f5 <_nl_find_msg+725>: mov (%r12),%rdi PC (0x7fdda72da0f5) ok source "(%r12)" (0x30b03019) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nano StacktraceTop: get_sysdep_segment_value (name=0x7fdda7cd3364 ) at loadmsgcat.c:727 _nl_load_domain (domain_file=0x55d7c83aafc0, domainbinding=domainbinding@entry=0x0) at loadmsgcat.c:1002 _nl_find_domain (dirname=dirname@entry=0x7fdda743ca40 <_nl_default_dirname> "/usr/share/locale", locale=locale@entry=0x7ffcc307a400 "pt", domainname=domainname@entry=0x7ffcc307a420 "LC_MESSAGES/libc.mo", domainbinding=domainbinding@entry=0x0) at finddomain.c:173 __dcigettext (domainname=0x7fdda7435a40 <_libc_intl_domainname> "libc", msgid1=0x7fdda7435dfd "No such file or directory", msgid2=msgid2@entry=0x0, plural=plural@entry=0, n=n@entry=0, category=category@entry=5) at dcigettext.c:722 __GI___dcgettext (domainname=, msgid=, category=category@entry=5) at dcgettext.c:47 Title: nano crashed with SIGSEGV in get_sysdep_segment_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1710511/+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 1667929] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Jerome, for some reason I didn't see the message that said you posted the file. The file you posted looks entirely corrupt, being full of binary stuff. If you have also Pico itself installed (beside nano), the content of that file should look something like this: auto /usr/bin/pico pico.1.gz /usr/share/man/man1/pico.1.gz /bin/nano 10 /usr/share/man/man1/nano.1.gz Nine lines, of which two blank. If you haven't already done so, I suggest you simply delete the corrupted file, and then try installing nano again. Let us know how it went. -- 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/1667929 Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in nano package in Ubuntu: New Bug description: it crashed during software update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nano 2.5.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Feb 25 14:28:00 2017 DpkgHistoryLog: Start-Date: 2017-02-25 14:01:31 Commandline: aptdaemon role='role-commit-packages' sender=':1.34' Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 (4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68) DuplicateSignature: package:nano:2.5.3-2ubuntu2 Setting up nano (2.5.3-2ubuntu2) ... update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid status dpkg: error processing package nano (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: nano Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1667929/+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 1698673] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить
Denis, Could you give a rough translation of "пакет абсолютно неработоспособен; перед настройкой его следует переустановить"? Because I have no idea what it says there. Did you try installing the package again? Did it succeed the second time? -- 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/1698673 Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить Status in nano package in Ubuntu: New Bug description: 1) Ubuntu 16.04 LTS 2) Nano 2.5.3-2ubuntu2 3) Nothing 4) Start system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nano 2.5.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 16 23:46:17 2017 ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его следует переустановить InstallationDate: Installed on 2017-06-16 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: nano Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1698673/+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 1667929] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Please attach the file /var/lib/dpkg/alternatives/pico . -- 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/1667929 Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in nano package in Ubuntu: New Bug description: it crashed during software update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nano 2.5.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Feb 25 14:28:00 2017 DpkgHistoryLog: Start-Date: 2017-02-25 14:01:31 Commandline: aptdaemon role='role-commit-packages' sender=':1.34' Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 (4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68) DuplicateSignature: package:nano:2.5.3-2ubuntu2 Setting up nano (2.5.3-2ubuntu2) ... update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid status dpkg: error processing package nano (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: nano Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1667929/+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 1650056] Re: /bin/nano:*** Error in `nano': munmap_chunk(): invalid pointer: ADDR ***
Thanks. Problem is the same as with bug #1641592: a long path that makes the prompt exceed 128 characters. So the patch attached to bug #1641592 should fix this crash too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1650056 Title: /bin/nano:*** Error in `nano': munmap_chunk(): invalid pointer: 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 package version 2.5.3-2, the problem page at https://errors.ubuntu.com/problem/295eb585019cebe203e4b05aec3f4a4fb98932b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1650056/+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 1650056] Re: /bin/nano:*** Error in `nano': munmap_chunk(): invalid pointer: ADDR ***
Brian? Can you show me the backtrace for this one too, please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1650056 Title: /bin/nano:*** Error in `nano': munmap_chunk(): invalid pointer: 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 package version 2.5.3-2, the problem page at https://errors.ubuntu.com/problem/295eb585019cebe203e4b05aec3f4a4fb98932b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1650056/+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 ***
(Oh! For some reason I am not getting all of the bug mail from Launchpad. At least: I missed notifications about this bug.) Hm... It seems that free() on Ubuntu checks that nothing was written outside of the allocated space? Does malloc() put a "canary" at the tail? Anyway, I am pretty sure that the patch attached to bug #1641592 will fix this crash. It is same patch as the second one attached to https://lists.gnu.org/archive/html/nano-devel/2016-04/msg00075.html, which was applied upstream nearly a year ago. -- 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: Confirmed 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 1650056] Re: /bin/nano:*** Error in `nano': munmap_chunk(): invalid pointer: ADDR ***
Why not apply the patch that I referred to in bug #1595607? It will solve the crashes. Why do you have this crash reporting system when you don't do anything with the reports? -- 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/1650056 Title: /bin/nano:*** Error in `nano': munmap_chunk(): invalid pointer: 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 package version 2.5.3-2, the problem page at https://errors.ubuntu.com/problem/295eb585019cebe203e4b05aec3f4a4fb98932b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1650056/+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 1641592] Re: nano 2.5.3-2 on Xenial crashes with long paths on lockfiles
This is a duplicate of upstream bug https://savannah.gnu.org/bugs/?47511 . The problem was fixed in git, commit fb9585e. See attached patch. The fix is in version 2.6.0 and higher. Thanks for reporting. ** Bug watch added: GNU Savannah Bug Tracker #47511 http://savannah.gnu.org/bugs/?47511 ** Patch added: "fixes the crash when finding lockfiles for long names" https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1641592/+attachment/4777372/+files/allocate-enough-space.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/1641592 Title: nano 2.5.3-2 on Xenial crashes with long paths on lockfiles Status in nano package in Ubuntu: New Bug description: # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt-cache policy nano nano: Installed: 2.5.3-2 Candidate: 2.5.3-2 Reproducer: 1. # nano -G 999 2. 3. # nano -G 999 4. 5. Quick dissection: Looking at function do_lockfile in files.c, it seems that promptstr is statically allocated to 128 characters. Now with a sufficiently long filename, the following sprintf() call will overflow the allocated promptstr buffer and corrupt memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1641592/+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 1637950] [NEW] nano HEAD is stuck in the year 2006
Public bug reported: On https://launchpad.net/nano/head both the timeline and the Downloads say that the last release of nano is 1.9.99pre3 from October 2006. But the last release is 2.7.1 from a few days ago. Please adjust things so that the timeline and the Downloads show also the most recent versions. ** 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/1637950 Title: nano HEAD is stuck in the year 2006 Status in nano package in Ubuntu: New Bug description: On https://launchpad.net/nano/head both the timeline and the Downloads say that the last release of nano is 1.9.99pre3 from October 2006. But the last release is 2.7.1 from a few days ago. Please adjust things so that the timeline and the Downloads show also the most recent versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1637950/+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
The problem has finally been fixed in nano-2.7.0. Thanks for reporting, and for your patience. ** Changed in: nano (Ubuntu) Status: Confirmed => 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
** 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 ***
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 ***
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
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
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
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
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
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
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
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
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
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
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
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
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
> 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
** 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
> 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
** 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
> 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 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
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 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
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
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
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
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
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
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
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 1300565] Re: please syntax highlight debdiff files
So if one saves the result of a debdiff as a 'name.diff' file, then opening it with nano should colour most things already in an appropriate and expected way, no? Or are there things missing that really should be coloured too? Could someone attach a sample 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/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
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 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 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 and , 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 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 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 1299829] Re: keyboard for Bambara not usable : name in evdev.xml points to Malayalam.
Hello Jean-Jacques, Ehm... how to say this... The filename 'ml' for Bambara layouts is correct. The filenames in the symbols/ directory follow country codes, not language codes. See for example the files for Kenia and Tanzania (symbols/ke and symbols/tz) which both contains layouts for Swahili (swa). There is no sw of swa file, so there should be no bm file either. You should rename your bm file to ml again. It will then still not work, because somewhere hidden there is a mistaken redirect from ml to in(mal), but that has been fixed in xkeyboard-config and should be fixed in the next release of Ubuntu. However, in comment #10 you say that the current Bambara layouts are old and need to be fixed. Could you please file a new bug upstream and post your up-to-date ml file (renamed from bm) here: https://bugs.freedesktop.org/enter_bug.cgi?product=xkeyboard-config Just that layouts file, no need for evdev.xml or anything else. The bare file, not zipped or compressed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1299829 Title: keyboard for Bambara not usable : name in evdev.xml points to Malayalam. Status in central project for keyboard configuration: Confirmed Status in “xkeyboard-config” package in Ubuntu: New Bug description: I am dong research in africa, languages, I have little knowledge about Linux/Ubuntu. I have been implementing bambara keyboards for Windows and Mac OSX (with Ukelele). A year ago I noticed that I could not use the keyboard for Bambara, apparently it was giving access to a strange asian language. Since then, my Ubuntu computer is updated regularly, it now runs Ubuntu 13.10 I spent a lot of time yesterday, I share what I found : 1) the in rules/edvdev.xml for this keyboard is "ml" this code is actually the one for a language called Malayalam, spoken in Kerala, south of India. Nothing to do with West Africa, and it's this language alphabet which is displayed when a user selects the Bambara keyword. I changed it to "bm", which is the ISO 639-1 code. (I changed also the ! layout section in evdev.lst) 2) the "ml" file in symbols is actually for Bambara! Some of the keys defined are obsolete, it does not align with the keys used by other SIL.org keyboard, but it is for bambara. I copied this file into a file called "bm" and renamed "ml" as "ml-old" I updated the bm file to align it to the SIL standards. This fixed it... only partially : the Malayalam keyboard does not display any longer when I select Bambara. I does now display the bambara keyboard. But : it still displays the one defined in the old "ml" file, not the one I corrected in the "bm" file!!! I messed up, restarted several times, to no avail : still the old obsolete keyboard. The only thing that works is that I can now use the keyboard variant which is defined in my "bm" as "French (Mali, alternative)" with my new keys definitions. When I add the basic "Bambara" keyboard, it displays the old layout. In the drop down list of keyboard at the top right of the screen, it is there... but greyed out. "French (Mali, alternative)" is OK for my personal use, but my objective is to make it available generally as "Bambara". Please help. Of cours I'm OK to supply the "bm" file Jean-Jacques, Paris To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1299829/+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
