[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10
I forgot to mention, now I get "Couldn't determine hostname for lock file: File name too long" when I try to run nano as both me AND root. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1509081 Title: nano segfaults as root after upgrade to 15.10 Status in nano 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
I'm getting this too. When I tried to nano my ~/bashrc file (just as me, not as root), the first two times it segfaulted. The third (and any later) times, now it displays "Couldn't determine hostname for lock file: File name too long" for ANY file I try to open or create. Upgraded from Ubuntu 15.04 to 15.10 two days ago. Attached is the crash log that apport created when nano segmentation faulted the first two times. ** Attachment added: "crash log" https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1509081/+attachment/4506693/+files/_bin_nano.1000.crash -- 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 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."
I also get 'File descriptor 50 (/dev/pts/6) leaked on vgs invocation. Parent PID 14069: /usr/sbin/grub-probe ' whenever apt-get updates grub's configuration file... which is several times when you're removing multiple old kernels... I would've thought this would be fixed by now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/591823 Title: "File descriptor \d+ (\S+) leaked on lvs invocation." Status in aptitude: Confirmed Status in lvm2 - Logical Volume Manager: Fix Released Status in lvm2 package in Ubuntu: Opinion Bug description: If you see messages like these: File descriptor 40 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 41 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 42 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 43 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh You can set LVM_SUPPRESS_FD_WARNINGS to suppress these warnings. Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581339 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432986 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138 This is a slightly controversial bug and it's not yet fixed either way (aka fix not to leak file descriptors or stop warning by default) To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/591823/+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
