Ah, the TP has moved since then. New link is:
http://translationproject.org/POT-files/bash-3.2.pot
--
bash-3.2 shipped with wrong pot file: help texts do not get translated
https://bugs.launchpad.net/bugs/104261
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Permissions here are crw-rw, and the card is accessible without a
problem by normal users. You may be missing this section in your
/etc/X11/xorg.conf:
Section "DRI"
Mode0666
EndSection
Alternatively, make sure that you are member of the video group:
check the output of the 'group
The upgrade of kde-guidance-powermanager from 0.8.0-0ubuntu3 to
0.8.0-0ubuntu4 has given me this problem: the battery shows as full and
as connected to mains -- while really it is unconnected and a few
minutes earlier it was at about 70%.
--
powermanager icon sometimes shows fully charged when no
Okay, 0.8.0-0ubuntu5 has fixed this again. Thanks.
--
powermanager icon sometimes shows fully charged when not
https://bugs.launchpad.net/bugs/64978
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kde-guidance in ubuntu.
--
kubuntu-bugs m
*** This bug is a duplicate of bug 43154 ***
https://bugs.launchpad.net/bugs/43154
Hi narr,
If you are willing and able to compile things from source, then join
#unichrome on irc.freenode.net and present your problem there.
--
Freezes with VIA KM400/VT8378 (regression)
https://bugs.launchpa
Pascal's Celeron M 420 cpu does not support frequency scaling (see
http://en.wikipedia.org/wiki/Intel_Core#Derivatives), so it should not
show the Frequency bar at all, in my opinion. Attached patch achieves
that for me on the same cpu.
For Nabla a workaround could maybe be found in automatically
Any more information you can give, tomasz? Is your problem like Nabla's
or like Pascal's? Or other still?
--
Doesn't detect CPU frequency
https://bugs.launchpad.net/bugs/89750
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
Public bug reported:
Binary package hint: bash
As noted by the bash maintainer in a message to bug-bash
(http://article.gmane.org/gmane.comp.shells.bash.bugs/9578/match=inadvertently)
bash-3.2 shipped with an old and wrong pot file. The main difference with the
correct pot file is that all the
Public bug reported:
Binary package hint: kde-guidance-powermanager
The update to kde-guidance-powermanager-0.8.0 removed the battery icon
from the system tray (after a restart). Running guidance-power-manager
on the command line produces this:
$ guidance-power-manager
[EMAIL PROTECTED]:~$ Trac
(The indentation patch changes nothing, except two line numbers in the
trace back.) The exception-catching patch 'solves' the problem and
brings back the battery in the system tray. Thanks.
--
kde-guidance-powermanager-0.8.0 fails with AttributeError: 'NoneType' object
has no attribute 'setChe
(The indentation patch changes nothing, except two line numbers in the
trace back.) The exception-catching patch 'solves' the problem and
brings back the battery in the system tray. Thanks.
--
kde-guidance-powermanager-0.8.0 fails with AttributeError: 'NoneType' object
has no attribute 'setChe
This bug was fixed upstream (for the latin layout only) :
http://cgit.freedesktop.org/xkeyboard-config/commit/?id=71001bc8956e382496f1572ce3f8efa270adc2b1
It seems to have been imported into Launchpad already:
http://bazaar.launchpad.net/~alexeyten/xkeyboard-config/master/revision/1169
The genera
Public bug reported:
When I tried to suspend my system today for the second time, 'systemctl
suspend' was hanging -- having no effect. (Yesterday I had a full
system freeze, which took two reboots to recover from. Such a freeze
never happened before, so I immediately suspected kernel
4.15.0-151-
** Summary changed:
- BUG: unable to handle kernel paging request after 'systemctl suspend'
+ kernel 4.15.0-151 tends to freeze after having been suspended
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This morning I still booted into 4.15.0-151 (to give it one more
chance), then put the system into suspension after half an hour or so,
and when I tried to wake it up a little later, the screen stayed blank
-- no response to any keystroke, not to Ctrl+Alt+F1/F2/F3 either:
frozen. Rebooting into 4.
A very similr issue was reported in bug #1938430: a kernel oops or a
complete freeze upon resuming from suspension.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938275
Title:
UI becomes completely
It seems likely that this is a duplicate of bug #1938013: kernel
4.15.0-151 is freezing various CPUs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938275
Title:
UI becomes completely unresponsive
*** This bug is a duplicate of bug 1938013 ***
https://bugs.launchpad.net/bugs/1938013
It seems that this is a duplicate of bug #1938013.
** This bug has been marked a duplicate of bug 1938013
4.15.0-151 is freezing various CPUs
--
You received this bug notification because you are a mem
Your report is rather confusing: it seem to be several sentences, all
run together, without any punctuation. And I fail to understand what it
has to with nano. The Gnome shell and dash have nothing to do with
nano. Please clarify what your problem is. What do you expect to
happen when you click
*** This bug is a duplicate of bug 1895782 ***
https://bugs.launchpad.net/bugs/1895782
** This bug has been marked a duplicate of bug 1895782
Screen brightness adjustment doesn't work on Lenovo Thinkpad T14 AMD gen1
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Cannot modify screen brightness
+ Cannot modify screen brightness on HP Spectre x360
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860497
Title:
Cannot modify screen brightne
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
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 back
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
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
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 recei
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
Same error (grub-install failing) when trying to install Ubuntu Mate
onto bare metal. I have no ESP (and have no room to make one), but saw
no warning about a missing ESP.
What's worse: the installation failed to boot: it hung while trying to
mount something. Rebooting into another distro and ex
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
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)
So, in fact this bug has been fixed by the fix for
https://bugzilla.mozilla.org/show_bug.cgi?id=1192655 -- pressing Alt
plus a letter when in fullscreen mode no longer opens hidden menus, and
thus pressing F11 to get out of fullscreen mode will always work.
The desire of the other bug report
(http
Indeed, grub.cfg gets larger and larger with _every_ run of the script
(all my systems are localized to Dutch, which uses "op" not "on").
Yesterday, booting on my old laptop had become so slow, that I finally
looked into it. It resulted that grub.cfg had grown to *seventeen
thousand* lines, with h
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785475
Title:
with LANG=C, fragments of lines get superimposed/intertwined when
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
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
By the way: please delete your sockpuppet bastiaan82.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785475
Title:
Scrolling in files gives display isues
To manage notifications about this bug go t
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
Bugs, which is subscribed to Ubuntu.
https:/
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 s
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 per
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17854
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 th
** Tags added: artful bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753724
Title:
nano fails to redo a file insertion
To manage notifications about this bug go to:
https://bugs.launchpad.ne
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
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:
*
Oh, forgot to say: it also has more complete translations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554660
Title:
request for import-freeze exception for nano-2.5.3-2
To manage notifications
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
Bugs, which is subscribed to Ubuntu.
https://b
Please attach the file /var/lib/dpkg/alternatives/pico .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667929
Title:
package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess
installed po
Should be fixed by now. Please reopen if this still doesn't work right.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/28907
Title:
Dapper 3: Shift cancels CapLock not OK
To manage notifica
Are you using Neo 2 as a secondary layout? If so, then this is a
duplicate of bug #879838 .
(By the way, neo-layout.org is not the upstream for keyboard layouts,
xkeyboard-config is.
http://www.freedesktop.org/wiki/Software/XKeyboardConfig/Development/ )
--
You received this bug notification b
Closing; this bug was fixed long ago. This also fixed bug #8585.
It does not depend on bug #19004 which is about having options per layout --
although a fix for that bug would make this fix more useful for some people.
--
You received this bug notification because you are a member of Ubuntu
Bugs
(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 t
Brian? Can you show me the backtrace for this one too, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650056
Title:
/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
Bugs, which is subscribed to Ubuntu.
https://bugs.
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
** Changed in: nano (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522598
Title:
nano crashes when resizing terminal
To manage notifications about
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 goe
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/con
** Changed in: nano (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320461
Title:
keybindings do not work when opening multiple files
To manage
** Changed in: nano (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539627
Title:
Buffer underflow in nano 2.4.2-1ubuntu0.1 causes SIGSEGV
To ma
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
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
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 cha
** Changed in: nano (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569964
Title:
Malformed characters on the console with LANG=de_DE.UTF-8 are shown
To mana
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. O
Ping? Bartłomiej?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539627
Title:
Buffer underflow in nano 2.4.2-1ubuntu0.1 causes SIGSEGV
To manage notifications about this bug go to:
https://bugs
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/bugre
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
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
Bugs, which is subsc
For me the workaround in comment #19 worked: removing the file gnome-
wm.desktop from the folder .local/share/applications in my home
directory. Thanks for posting, André.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
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 s
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 t
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, a
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
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 notifi
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
Bugs, which is subscribed to Ubuntu.
https:/
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/481363
Title:
Python syntax formatting incorrectly hig
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300565
Title:
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 notific
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 colo
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300565
Title:
please syntax highlight debdiff files
To manage notifications
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.
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
Closing; the requested change has been made in git. (The attached patch
is obviously wrong, as it does not match the text of the original request
in Launchpad.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471459
Title:
First run of nano creates a directory in $HOME, if run as sudo
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471459
Title:
First run
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
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509081
Title:
nano segfaults as root aft
> 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
> ./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 l
> 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
** 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
Bugs, which is subscribed to Ubuntu.
h
> 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
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509081
Title:
nano segfaults as root after upgrade to 15.10
To manage notifications about this bug go to:
https
> 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/+fil
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539627
Title:
Buffer underflow in nano 2.4
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320461
Title:
keybindings do not work when opening mu
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522598
Title:
nano crashes when resizing terminal
To
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
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 =>
1 - 100 of 119 matches
Mail list logo
