[Bug 584797] Re: vim loses left/right cursor keys in insert mode when editing SQL
I can't reproduce this bug. Can you try with "vim -u NONE foo.sql" to make sure it's not one of your settings in your ~/.vimrc which is causing the problem? -- vim loses left/right cursor keys in insert mode when editing SQL https://bugs.launchpad.net/bugs/584797 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83142] Re: crash on XSetIMValues() call when using xim and esperanto locale
Bryce Harrington wrote: > Can you try with the latest development release of Ubuntu? I'll install the latest Ubuntu shortly after it's released. I'll then check whether bug is still present. But in the mean time, if someone has already installed Ubuntu-10.04 beta, can try post the content of the 2 files? - /usr/share/X11/locale/compose.dir - /usr/share/X11/locale/locale.dir I'm curious about what they contain for the eo.UTF-8 locale. Or if you prefer, the output of this command would help: $ grep eo /usr/share/X11/locale/{locale,compose}.dir -- crash on XSetIMValues() call when using xim and esperanto locale https://bugs.launchpad.net/bugs/83142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291373] Re: vim: hang after ^Z / fg
** Changed in: vim (Ubuntu) Status: Confirmed => Fix Released -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510362] Re: SIGSEGV in setup_context for vim -g in karmic
I can't reproduce this bug. Vim or gVim (built with Python) do not crash for me when putting vimchat.vim in my ~/.vim/plugin directory. However: - I have not spent time figuring out how this plugin works. Perhaps you have some settings in your ~/.vimrc which trigger the bug. If you don't mind, can you send your ~/.vimrc file? - when starting Vim (built with Python interpreter) with valgrind memory checker, I see some accesses to freed memory (see http://dominique.pelle.free.fr/valgrind-errors-vim7.2.351-python2.6.4.txt) even without the plugin. I don't know yet whether this bug in the Python lib or in Vim. See this thread in vim_dev mailing list: http://groups.google.com/group/vim_dev/browse_thread/thread/11ed0e435190ccb -- SIGSEGV in setup_context for vim -g in karmic https://bugs.launchpad.net/bugs/510362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515211] Re: "POD ERRORS" when doing "man gcc"
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38584146/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/38584147/XsessionErrors.txt -- "POD ERRORS" when doing "man gcc" https://bugs.launchpad.net/bugs/515211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515211] [NEW] "POD ERRORS" when doing "man gcc"
Public bug reported: When doing "man gcc", at the very bottom of the man page, I see this: = POD ERRORS Hey! The above document had some coding errors, which are explained below: Around line 8761: You can't have =items (as at line 8774) unless the first thing after the =over is an =item = I'm using Ubuntu-9.10 (Karmic). ProblemType: Bug Architecture: i386 Date: Sun Jan 31 18:52:16 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: gcc 4:4.4.1-1ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: gcc-defaults Uname: Linux 2.6.31-17-generic i686 ** Affects: gcc-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- "POD ERRORS" when doing "man gcc" https://bugs.launchpad.net/bugs/515211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127399] Re: bogus background command often causes shell to exit
I can still reproduce this bug with Ubuntu-9.10 Karmic (tested in a xterm). It happens rarely but I managed to reproduce it at least twice. I happens more often if I run it strace. I ran... $ strace -s 3000 -f -o /tmp/trace-xterm xterm And in the xterm, I ran the non existing command: $ foobar& xterm exited immediately! (but it does not happen all the time when I try again). In the log file /tmp/trace-xterm, I see something interesting shortly before it exits: 334 write(2, "Sorry, command-not-found has crashed! Please file a bug report at:", 66) = -1 EIO (Input/output error) I attach the full /tmp/trace-xterm log file. ** Attachment added: "trace-xterm" http://launchpadlibrarian.net/38446086/trace-xterm -- bogus background command often causes shell to exit https://bugs.launchpad.net/bugs/127399 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 511885] Re: spatialite crashes when exiting
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38327485/Dependencies.txt ** Description changed: - spatialite program on Ubuntu-9.10 (Karmic) crashes when existing with + spatialite program on Ubuntu-9.10 (Karmic) crashes when exiting with double free message. Steps to reproduce: 1/ install spatialite with: $ sudo apt-get install spatialite-bin 2/ run "spatialite" from shell, and issue the ".quit" command as follows. - Oberver the crash when issuing the ".quit" command: + Oberve the crash when issuing the ".quit" command: $ spatialite SpatiaLite version ..: 2.3.0 Supported Extensions: - - 'VirtualShape'[direct Shapefile access] - - 'VirtualText [direct CSV/TXT access] - - 'VirtualNetwork [Dijkstra shortest path] - - 'RTree' [Spatial Index - R*Tree] - - 'MbrCache'[Spatial Index - MBR cache] - - 'VirtualFDO' [FDO-OGR interoperability] - - 'SpatiaLite' [Spatial SQL - OGC] + - 'VirtualShape' [direct Shapefile access] + - 'VirtualText [direct CSV/TXT access] + - 'VirtualNetwork[Dijkstra shortest path] + - 'RTree'[Spatial Index - R*Tree] + - 'MbrCache' [Spatial Index - MBR cache] + - 'VirtualFDO' [FDO-OGR interoperability] + - 'SpatiaLite' [Spatial SQL - OGC] PROJ.4 version ..: Rel. 4.7.1, 23 September 2009 GEOS version : 3.1.1-CAPI-1.6.0 SQLite version ..: 3.6.16 Enter ".help" for instructions spatialite> .quit *** glibc detected *** spatialite: double free or corruption (fasttop): 0x09024ec0 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0x238ff1] /lib/tls/i686/cmov/libc.so.6[0x23a6f2] /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x23d7cd] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xf8b6f1] /usr/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1d)[0xf6935d] /usr/lib/libstdc++.so.6(_ZNSsD1Ev+0x4c)[0xf6ad6c] /lib/tls/i686/cmov/libc.so.6(__cxa_finalize+0xb8)[0x1fd428] /usr/lib/libgeos-3.1.1.so[0xa9d504] /usr/lib/libgeos-3.1.1.so[0xb46430] /lib/ld-linux.so.2[0x379f46] /lib/tls/i686/cmov/libc.so.6[0x1fd05f] /lib/tls/i686/cmov/libc.so.6[0x1fd0cf] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xee)[0x1e4b5e] spatialite[0x8049eb1] === Memory map: 0011-00143000 r-xp 08:01 15717 /usr/lib/libproj.so.0.6.6 00143000-00144000 r--p 00032000 08:01 15717 /usr/lib/libproj.so.0.6.6 00144000-00146000 rw-p 00033000 08:01 15717 /usr/lib/libproj.so.0.6.6 00146000-0014f000 r-xp 08:01 211401 /lib/tls/i686/cmov/libnss_nis-2.10.1.so 0014f000-0015 r--p 8000 08:01 211401 /lib/tls/i686/cmov/libnss_nis-2.10.1.so 0015-00151000 rw-p 9000 08:01 211401 /lib/tls/i686/cmov/libnss_nis-2.10.1.so 00196000-001ca000 r-xp 08:01 591/lib/libncurses.so.5.7 001ca000-001cb000 ---p 00034000 08:01 591/lib/libncurses.so.5.7 001cb000-001cd000 r--p 00034000 08:01 591/lib/libncurses.so.5.7 001cd000-001ce000 rw-p 00036000 08:01 591/lib/libncurses.so.5.7 001ce000-0030c000 r-xp 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so 0030c000-0030d000 ---p 0013e000 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so 0030d000-0030f000 r--p 0013e000 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so 0030f000-0031 rw-p 0014 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so - 0031-00313000 rw-p 00:00 0 + 0031-00313000 rw-p 00:00 0 0036c000-00387000 r-xp 08:01 1055 /lib/ld-2.10.1.so 00387000-00388000 r--p 0001a000 08:01 1055 /lib/ld-2.10.1.so 00388000-00389000 rw-p 0001b000 08:01 1055 /lib/ld-2.10.1.so 004b9000-005f2000 r-xp 08:01 8923 /usr/lib/libgeos-3.1.0.so 005f2000-005f6000 r--p 00138000 08:01 8923 /usr/lib/libgeos-3.1.0.so 005f6000-005f7000 rw-p 0013c000 08:01 8923 /usr/lib/libgeos-3.1.0.so 0065d000-006aa000 r-xp 08:01 8924 /usr/lib/libspatialite.so.2.0.3 006aa000-006ab000 r--p 0004c000 08:01 8924 /usr/lib/libspatialite.so.2.0.3 006ab000-006ac000 rw-p 0004d000 08:01 8924 /usr/lib/libspatialite.so.2.0.3 00763000-00776000 r-xp 08:01 15699 /usr/lib/libgeos_c.so.1.6.0 00776000-00777000 r--p 00012000 08:01 15699 /usr/lib/libgeos_c.so.1.6.0 00777000-00778000 rw-p 00013000 08:01 15699 /usr/lib/libgeos_c.so.1.6.0 0086-008e6000 r-xp 08:01 3872 /usr/lib/libsqlite3.so.0.8.6 008e6000-008e7000 r--p 00086000 08:01 3872 /usr/lib/libsqlite3.so.0.8.6 008e7000-008e8000 rw-p 00087000 08:01 3872 /usr/lib/libsqlite3.so.0.8.6 008f1000-0090d000 r-xp 08:01 8738 /lib/libgcc_s.so.1 0090d000-0090e000 r--p 0001b000 08:01 8738 /lib/libgcc_s.so.1 0090e000-0090f000 rw-p 0001c000 08:01 8738 /lib/libg
[Bug 511885] [NEW] spatialite crashes when exiting
Public bug reported: spatialite program on Ubuntu-9.10 (Karmic) crashes when exiting with double free message. Steps to reproduce: 1/ install spatialite with: $ sudo apt-get install spatialite-bin 2/ run "spatialite" from shell, and issue the ".quit" command as follows. Oberve the crash when issuing the ".quit" command: $ spatialite SpatiaLite version ..: 2.3.0Supported Extensions: - 'VirtualShape' [direct Shapefile access] - 'VirtualText [direct CSV/TXT access] - 'VirtualNetwork [Dijkstra shortest path] - 'RTree' [Spatial Index - R*Tree] - 'MbrCache' [Spatial Index - MBR cache] - 'VirtualFDO' [FDO-OGR interoperability] - 'SpatiaLite' [Spatial SQL - OGC] PROJ.4 version ..: Rel. 4.7.1, 23 September 2009 GEOS version : 3.1.1-CAPI-1.6.0 SQLite version ..: 3.6.16 Enter ".help" for instructions spatialite> .quit *** glibc detected *** spatialite: double free or corruption (fasttop): 0x09024ec0 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0x238ff1] /lib/tls/i686/cmov/libc.so.6[0x23a6f2] /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x23d7cd] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xf8b6f1] /usr/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1d)[0xf6935d] /usr/lib/libstdc++.so.6(_ZNSsD1Ev+0x4c)[0xf6ad6c] /lib/tls/i686/cmov/libc.so.6(__cxa_finalize+0xb8)[0x1fd428] /usr/lib/libgeos-3.1.1.so[0xa9d504] /usr/lib/libgeos-3.1.1.so[0xb46430] /lib/ld-linux.so.2[0x379f46] /lib/tls/i686/cmov/libc.so.6[0x1fd05f] /lib/tls/i686/cmov/libc.so.6[0x1fd0cf] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xee)[0x1e4b5e] spatialite[0x8049eb1] === Memory map: 0011-00143000 r-xp 08:01 15717 /usr/lib/libproj.so.0.6.6 00143000-00144000 r--p 00032000 08:01 15717 /usr/lib/libproj.so.0.6.6 00144000-00146000 rw-p 00033000 08:01 15717 /usr/lib/libproj.so.0.6.6 00146000-0014f000 r-xp 08:01 211401 /lib/tls/i686/cmov/libnss_nis-2.10.1.so 0014f000-0015 r--p 8000 08:01 211401 /lib/tls/i686/cmov/libnss_nis-2.10.1.so 0015-00151000 rw-p 9000 08:01 211401 /lib/tls/i686/cmov/libnss_nis-2.10.1.so 00196000-001ca000 r-xp 08:01 591/lib/libncurses.so.5.7 001ca000-001cb000 ---p 00034000 08:01 591/lib/libncurses.so.5.7 001cb000-001cd000 r--p 00034000 08:01 591/lib/libncurses.so.5.7 001cd000-001ce000 rw-p 00036000 08:01 591/lib/libncurses.so.5.7 001ce000-0030c000 r-xp 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so 0030c000-0030d000 ---p 0013e000 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so 0030d000-0030f000 r--p 0013e000 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so 0030f000-0031 rw-p 0014 08:01 211381 /lib/tls/i686/cmov/libc-2.10.1.so 0031-00313000 rw-p 00:00 0 0036c000-00387000 r-xp 08:01 1055 /lib/ld-2.10.1.so 00387000-00388000 r--p 0001a000 08:01 1055 /lib/ld-2.10.1.so 00388000-00389000 rw-p 0001b000 08:01 1055 /lib/ld-2.10.1.so 004b9000-005f2000 r-xp 08:01 8923 /usr/lib/libgeos-3.1.0.so 005f2000-005f6000 r--p 00138000 08:01 8923 /usr/lib/libgeos-3.1.0.so 005f6000-005f7000 rw-p 0013c000 08:01 8923 /usr/lib/libgeos-3.1.0.so 0065d000-006aa000 r-xp 08:01 8924 /usr/lib/libspatialite.so.2.0.3 006aa000-006ab000 r--p 0004c000 08:01 8924 /usr/lib/libspatialite.so.2.0.3 006ab000-006ac000 rw-p 0004d000 08:01 8924 /usr/lib/libspatialite.so.2.0.3 00763000-00776000 r-xp 08:01 15699 /usr/lib/libgeos_c.so.1.6.0 00776000-00777000 r--p 00012000 08:01 15699 /usr/lib/libgeos_c.so.1.6.0 00777000-00778000 rw-p 00013000 08:01 15699 /usr/lib/libgeos_c.so.1.6.0 0086-008e6000 r-xp 08:01 3872 /usr/lib/libsqlite3.so.0.8.6 008e6000-008e7000 r--p 00086000 08:01 3872 /usr/lib/libsqlite3.so.0.8.6 008e7000-008e8000 rw-p 00087000 08:01 3872 /usr/lib/libsqlite3.so.0.8.6 008f1000-0090d000 r-xp 08:01 8738 /lib/libgcc_s.so.1 0090d000-0090e000 r--p 0001b000 08:01 8738 /lib/libgcc_s.so.1 0090e000-0090f000 rw-p 0001c000 08:01 8738 /lib/libgcc_s.so.1 009ba000-009bc000 r-xp 08:01 211384 /lib/tls/i686/cmov/libdl-2.10.1.so 009bc000-009bd000 r--p 1000 08:01 211384 /lib/tls/i686/cmov/libdl-2.10.1.so 009bd000-009be000 rw-p 2000 08:01 211384 /lib/tls/i686/cmov/libdl-2.10.1.so 00a43000-00a44000 r-xp 00:00 0 [vdso] 00a44000-00b7e000 r-xp 08:01 15698 /usr/lib/libgeos-3.1.1.so 00b7e000-00b82000 r--p 00139000 08:01 15698 /usr/lib/libgeos-3.1.1.so 00b82000-00b83000 rw-p 0013d000 08:01 15698 /usr/lib/libgeos-3.1.1.so 00be2000-00be8000 r-xp 08:01 211397 /lib/tls/i686/cmov/libnss_compat-2.10.1.so 00be8000-00be9000 r--p 5000 08:01 211397 /lib/tls/i686/cmov/libnss_compat-2.10.1.so 00be9000-00bea000 rw-p 6000 08:01 211397 /lib/tls/i686/cmov/libnss_compat-2.10.1.so 00c31000-0
[Bug 498303] Re: Vim syntax highlighting doesn't have "Breaks"
The latest version upstream (as of today) of file runtime/syntax/depcontrol.vim which I downloaded with... rsync -avzcP --delete --exclude="dos" --exclude="spell" ftp.nluug.nl::Vim/runtime/ . ... does does not contain the Breaks keyword indeed. Looking at http://www.sfr-fresh.com/linux/misc/dpkg_1.15.5.3.tar.gz:a/dpkg-1.15.5.3/man/deb-control.5 I see that the "Tag" keyword may also be missing. File runtime/syntax/depcontrol.vim contains the email of its maintainer at the top (I'm not going to repeat the email here). -> Can you email your patch to its maintainer? It's best to CC the vim_use mailing list too: http://groups.google.com/group/vim_use I see that the last update in the official file is "2009 July 14" so this file is actively maintained. -- Vim syntax highlighting doesn't have "Breaks" https://bugs.launchpad.net/bugs/498303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497923] Re: typo in "man ld"
I precise that I'm using Ubuntu-9.10 (Karmic Koala) -- typo in "man ld" https://bugs.launchpad.net/bugs/497923 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497923] [NEW] typo in "man ld"
Public bug reported: When doing "man ld", I see a typo: the word "explicitely" should be spelled "explicitly". It's in the last paragraph of the the description of the option --no-gc- sections. ** Affects: ubuntu Importance: Undecided Status: New -- typo in "man ld" https://bugs.launchpad.net/bugs/497923 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83142] Re: crash on XSetIMValues() call when using xim and esperanto locale
Esperanto locale is no longer eo_XX.UTF-8 but is eo.UTF-8. So we need to update the following 2 files accordingly: /usr/share/X11/locale/locale.dir /usr/share/X11/locale/compose.dir See attached patch for Ubuntu-9.10 Karmic Koala ** Attachment added: "fix for eo.UTF-8 locale in Ubuntu-9.10" http://launchpadlibrarian.net/36227721/fix-eo-locale.patch -- crash on XSetIMValues() call when using xim and esperanto locale https://bugs.launchpad.net/bugs/83142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83142] Re: crash on XSetIMValues() call when using xim and esperanto locale
The bug is still present in Ubuntu-9.10 Karmic Koala. The patch I submited in previous comment needs to be changed because Esperanto locale is no longer eo_XX.UTF-8 but it is now eo.UTF-8. So in files /usr/share/X11/locale/compose.dir and /usr/share/X11/locale/locale.dir, we need to substitute eo_XX.UTF-8 into eo.UTF-8. In other words, in file /usr/share/X11/locale/locale.dir, lines... en_US.UTF-8/XLC_LOCALE eo.UTF-8 ... en_US.UTF-8/XLC_LOCALE: eo.UTF-8 ... need to be changed into: en_US.UTF-8/XLC_LOCALE eo.UTF-8 ... en_US.UTF-8/XLC_LOCALE: eo.UTF-8 And in file /usr/share/X11/locale/compose.dir, lines... en_US.UTF-8/Compose eo_XX.UTF-8 ... en_US.UTF-8/Compose:eo_XX.UTF-8 ... need to be changed into: en_US.UTF-8/Compose eo.UTF-8 ... en_US.UTF-8/Compose:eo.UTF-8 After doing that, everything works fine in Ubuntu-9.10 (so it's easy to fix): - compose key then works - launching xterm no longer complains unsupported locale - and Vim no longer crash -- crash on XSetIMValues() call when using xim and esperanto locale https://bugs.launchpad.net/bugs/83142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381668] Re: xfig produces illegal PNG file when exporting as PNG
This bug is still present in Ubuntu-9.10 (Karmic Koala) -- xfig produces illegal PNG file when exporting as PNG https://bugs.launchpad.net/bugs/381668 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312563] Re: xvidcap: xtoffmpeg.c guess_input_pix_fmt(): image depth 32 not supported ... aborting
I can still reproduce this bug in Ubuntu-9.10 (Karmic Koala) -- xvidcap: xtoffmpeg.c guess_input_pix_fmt(): image depth 32 not supported ... aborting https://bugs.launchpad.net/bugs/312563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339569] Re: ftp command crashes when typing: !cd /tmp
I can't reproduce the bug anymore in Ubuntu-9.10 (Karmic Koala) so it appears to have been fixed. -- ftp command crashes when typing: !cd /tmp https://bugs.launchpad.net/bugs/339569 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318812] Re: *** buffer overflow detected ***: xfig terminated
I can't reproduce this bug anymore in Ubuntu-9.10 (Karmic Koala) so it appears to have been fixed. $ xfig -v Xfig 3.2 patchlevel 5a (Protocol 3.2) -- *** buffer overflow detected ***: xfig terminated https://bugs.launchpad.net/bugs/318812 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 202435] Re: typos in man page of "xdvi"
These typos are still present man page of xdvi in Ubuntu-9.10 (Karmic Koala) -- typos in man page of "xdvi" https://bugs.launchpad.net/bugs/202435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129106] Re: [gutsy] Vim crash when gnome terminal tab is detached
As indicated in previous comment, this bug has been fixed in Vim-7.1.166. This fix has been included in Ubuntu for a while now (I don't know from which release). Ubuntu-9.10 uses Vim-7.2.245 so at least Ubuntu-9.10 is fixed. -- [gutsy] Vim crash when gnome terminal tab is detached https://bugs.launchpad.net/bugs/129106 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320388] Re: accentuated characters wrongly displayed (encoding problem) in title bar
I'm still seeing this issue in Ubuntu-9.10 (Karmic Koala) when using xterm. But there is no bug when using gnome-terminal. -- accentuated characters wrongly displayed (encoding problem) in title bar https://bugs.launchpad.net/bugs/320388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71322] Re: reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale
I'm still seeing this issue in Ubuntu-9.10 (Karmic Koala). Very easy to reproduce: ~$ LC_ALL=en_GB.UTF-8 aspell list < /dev/null Segmentation fault -- reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale https://bugs.launchpad.net/bugs/71322 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133323] Re: [upstream] English spelling checker of openoffice incorrectly accepts word "informations"
This minor bug is still in Ubuntu-9.10 (Karmic Koala) which has OpenOffice-3.1.1 -- [upstream] English spelling checker of openoffice incorrectly accepts word "informations" https://bugs.launchpad.net/bugs/133323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291373] Re: vim: hang after ^Z / fg
Bug was fixed in Vim-7.2.130. I have just installed Ubuntu-9.10 Karmic Koala, and I see that it comes with Vim-7.2.245. So bug can be marked as fixed at least in Ubuntu >= 9.10 (Karmic Koala) -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403417] [NEW] assert failure in multitail program when file arguments do not exist
Public bug reported: Binary package hint: multitail "multitail" program asserts when passing non existing file names. Bug is easily 100% reproducible on Ubuntu Steps to reproduce: 1/ install "multitail" (in case it's not already installed) $ sudo apt-get install multitail 2/ run "multitail" on non existing file names and observe the assert failure $ multitail non-existing-file-1 non-existing-file-2 --*- multitail 5.2.2 (C) 2003-2007 by folk...@vanheusden.com -*-- A problem occured at line 1010 in function do_commandline (from file cmdline.c): Error opening file non-existing-file-1. errno variable (if applicable): 2 which means No such file or directory Binary build at May 22 2008 11:05:50 multitail: utils.c:197: stop_process: Assertion `pid > 1' failed. Aborted Expected behavior: it should report an error rather than an assert failure. Oh, and while we're at it, notice also the typo in the error message: "A problem occured at line 1010..." (*occured* is misspelled -> occurred) ** Affects: multitail (Ubuntu) Importance: Undecided Status: New -- assert failure in multitail program when file arguments do not exist https://bugs.launchpad.net/bugs/403417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403417] Re: assert failure in multitail program when file arguments do not exist
I precise that I am using Ubuntu-9.04 (Jaunty) with all updates as of today (2009/07/23). -- assert failure in multitail program when file arguments do not exist https://bugs.launchpad.net/bugs/403417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390603] Re: segv inside _XReply / get_x11_windis / mch_settitle / win_close
Is this crash reproducible? If so can you give the step by step instructions to reproduce it? -- segv inside _XReply / get_x11_windis / mch_settitle / win_close https://bugs.launchpad.net/bugs/390603 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 202435] Re: typos in man page of "xdvi"
> Have you got a URL for the upstream bug report? google search gives this: http://www.tug.org/pipermail/tex-live/2009-January/019666.html -- typos in man page of "xdvi" https://bugs.launchpad.net/bugs/202435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314023] Re: Gnuplot svg output is broken
I tried this... $ cat test-case.gnuplot set terminal svg plot sin(x) title 'utf-8 test ĉĝĥĵŝŭ (Esperanto diacritics)' $ gnuplot test-case.gnuplot > test.svg $ head -1 foo.svg ... and looking at test.svg with inkscape for example, I can see proper accentuated characters (good) However, I can't see the sin(x) function!? (which is a bug in the svg terminal of gnuplot it seems) I also tried with the "png" terminal instead of "svg" and then utf-8 does not work. I see garbage. I need to to set latin1 title to see them properly. In gnuplot, when doing "help encoding", I see: gnuplot> help encoding The `set encoding` command selects a character encoding. Syntax: set encoding {} show encoding Valid values are default - tells a terminal to use its default encoding iso_8859_1 - the most common Western European font used by many Unix workstations and by MS-Windows. This encoding is known in the PostScript world as 'ISO-Latin1'. iso_8859_2 - used in Central and Eastern Europe iso_8859_15 - a variant of iso_8859_1 that includes the Euro symbol koi8r - popular Unix cyrillic encoding koi8u - ukrainian Unix cyrillic encoding cp437 - codepage for MS-DOS cp850 - codepage for OS/2, Western Europe cp852 - codepage for OS/2, Central and Eastern Europe cp1250 - codepage for MS Windows, Central and Eastern Europe Generally you must set the encoding before setting the terminal type. Note that encoding is not supported by all terminal drivers and that the device must be able to produce the desired non-standard characters. Press return for more: The PostScript, X11 and wxt terminals support all encodings. OS/2 Presentation Manager switches automatically to codepage 912 for `iso_8859_2`. Hmmm, it seems that gnuplot is not yet aware of Unicode, or at least it's not described in "help encoding". Trying "set encoding utf-8" gives an error: gnuplot> set encoding utf-8 ^ expecting one of 'default', 'iso_8859_1', 'iso_8859_2', 'iso_8859_15', 'cp437', 'cp850', 'cp852', 'koi8r' or 'koi8u' Shouldn't gnuplot look at the current locale anyway to decide what default encoding to use? -- Gnuplot svg output is broken https://bugs.launchpad.net/bugs/314023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314023] Re: Gnuplot svg output is broken
I read in the gnuplot FAQ (http://www.gnuplot.info/faq/faq.html): = 4.11 How do I include accented characters To obtain accented characters like ü or n in your labels you should use 8bit character codes together with the appropriate encoding option. See the following example: gnuplot> set encoding iso_8859_1 gnuplot> set title "M\374nchner Bierverbrauch \374ber die Jahre" gnuplot> plot "bier.dat" u 1:2 Consequently, you can type labels in Czech, French, Hungarian, Russian... by means of an appropriate set encoding. However, you cannot mix two encodings in one file (e.g. accents for west and east latin encodings). A more general solution is to use UTF-8 encoded fonts, and type the UTF-8 characters directly into gnuplot. This works for many terminal types but not, unfortunately, PostScript. Update: The CVS version of gnuplot contains more complete support for UTF-8, including PostScript. = -- Gnuplot svg output is broken https://bugs.launchpad.net/bugs/314023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381668] Re: xfig produces illegal PNG file when exporting as PNG
pngcheck tool also complains about the PNG file produced by xfig (so it's not only optipng): $ pngcheck foo.png foo.png additional data after IEND chunk -- xfig produces illegal PNG file when exporting as PNG https://bugs.launchpad.net/bugs/381668 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381668] [NEW] xfig produces illegal PNG file when exporting as PNG
Public bug reported: Binary package hint: xfig Summary: Exporting a figure as PNG with xfig produces illegal PNG file. Steps to reproduce: 1/ start 'xfig foo.fig' from command line: $ xfig foo.fig 2/ draw something (it does not matter what you draw) 3/ Export as PNG with: File -> Export In the export dialog box, select "Language: PNG (Portable Network Graphic)" and click "Export" button 4/ observe that xfig has produce file "foo.png" (so far so good) 5/ Now run "optipng" tool from command line with: $ optipng foo.png 6/ Observe the following error: $ optipng foo.png OptiPNG 0.6.2.1: Advanced PNG optimizer. Copyright (C) 2001-2009 Cosmin Truta. ** Processing: foo.png Warning: Extraneous data found after IEND 39x39 pixels, 3x8 bits/pixel, RGB Reducing image to 1 bit/pixel, 2 colors in palette Recoverable errors found in input. Rerun OptiPNG with the -fix option. Error: Previous error(s) not fixed ** Status report 1 file(s) have been processed. 1 error(s) have been encountered. -> the PNG file is illegal. It can be corrected though with "optipng -fix foo.png". I'm using xfig as shipped with Ubuntu 9.04 (Jaunty) $ xfig -v Xfig 3.2 patchlevel 5 (Protocol 3.2) ** Affects: xfig (Ubuntu) Importance: Undecided Status: New -- xfig produces illegal PNG file when exporting as PNG https://bugs.launchpad.net/bugs/381668 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318812] Re: *** buffer overflow detected ***: xfig terminated
This bug still happens with latest release Ubuntu-9.04 (as well as 8.10). Very easy to reproduce as explain in previous comment. -- *** buffer overflow detected ***: xfig terminated https://bugs.launchpad.net/bugs/318812 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318812] Re: *** buffer overflow detected ***: xfig terminated
I also observe this bug with Ubuntu-8.10. It's very easy to reproduce. 1/ start xfig without argument: $ xfig 2/ Click in the canvas to give it focus then press z (lower case) several times until xfig crashes. On my machine it always crashes after pressing z 9 times. Observe the following error: $ xfig *** buffer overflow detected ***: xfig terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7e936d8] /lib/tls/i686/cmov/libc.so.6[0xb7e91800] /lib/tls/i686/cmov/libc.so.6[0xb7e90ef8] /lib/tls/i686/cmov/libc.so.6(_IO_default_xsputn+0xc8)[0xb7e06a78] /lib/tls/i686/cmov/libc.so.6(_IO_vfprintf+0x371b)[0xb7ddc0db] /lib/tls/i686/cmov/libc.so.6(__vsprintf_chk+0xa4)[0xb7e90fa4] /lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xb7e90eed] xfig[0x80f76cd] xfig[0x80f81ab] xfig[0x80dc585] xfig[0x80dd061] /usr/lib/libXt.so.6[0xb7d8c4c1] /usr/lib/libXt.so.6[0xb7d8c89b] /usr/lib/libXt.so.6(_XtTranslateEvent+0x5e8)[0xb7d8ce98] /usr/lib/libXt.so.6(XtDispatchEventToWidget+0x4c2)[0xb7d63672] /usr/lib/libXt.so.6[0xb7d63e8a] /usr/lib/libXt.so.6(XtDispatchEvent+0xc7)[0xb7d62cf7] xfig[0x808916d] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7daf685] xfig[0x804dd91] === Memory map: 08048000-08142000 r-xp 08:04 2184158/usr/bin/xfig 08142000-08143000 r--p 000fa000 08:04 2184158/usr/bin/xfig 08143000-0816 rw-p 000fb000 08:04 2184158/usr/bin/xfig 0816-0820 rw-p 0816 00:00 0 08a07000-08a8c000 rw-p 08a07000 00:00 0 [heap] b7c99000-b7ca6000 r-xp 08:04 1894074/lib/libgcc_s.so.1 b7ca6000-b7ca7000 r--p c000 08:04 1894074/lib/libgcc_s.so.1 b7ca7000-b7ca8000 rw-p d000 08:04 1894074/lib/libgcc_s.so.1 b7ca8000-b7cac000 r-xp 08:04 2180417/usr/lib/libXfixes.so.3.1.0 b7cac000-b7cad000 rw-p 3000 08:04 2180417/usr/lib/libXfixes.so.3.1.0 b7cad000-b7cb5000 r-xp 08:04 2181518/usr/lib/libXrender.so.1.3.0 b7cb5000-b7cb6000 r--p 7000 08:04 2181518/usr/lib/libXrender.so.1.3.0 b7cb6000-b7cb7000 rw-p 8000 08:04 2181518/usr/lib/libXrender.so.1.3.0 b7cb7000-b7cbf000 r-xp 08:04 2180407/usr/lib/libXcursor.so.1.0.2 b7cbf000-b7cc rw-p 7000 08:04 2180407/usr/lib/libXcursor.so.1.0.2 b7cc-b7cc2000 rw-p b7cc 00:00 0 b7cc2000-b7cc6000 r-xp 08:04 2181398/usr/lib/libXdmcp.so.6.0.0 b7cc6000-b7cc7000 rw-p 3000 08:04 2181398/usr/lib/libXdmcp.so.6.0.0 b7cc7000-b7cc9000 r-xp 08:04 2180573/usr/lib/libXau.so.6.0.0 b7cc9000-b7cca000 rw-p 1000 08:04 2180573/usr/lib/libXau.so.6.0.0 b7cca000-b7ccc000 r-xp 08:04 1909306/lib/tls/i686/cmov/libdl-2.8.90 .so b7ccc000-b7ccd000 r--p 1000 08:04 1909306/lib/tls/i686/cmov/libdl-2.8.90 .so b7ccd000-b7cce000 rw-p 2000 08:04 1909306/lib/tls/i686/cmov/libdl-2.8.90 .so b7cce000-b7ce5000 r-xp 08:04 2181505/usr/lib/libxcb.so.1.0.0 b7ce5000-b7ce6000 r--p 00016000 08:04 2181505/usr/lib/libxcb.so.1.0.0 b7ce6000-b7ce7000 rw-p 00017000 08:04 2181505/usr/lib/libxcb.so.1.0.0 b7ce7000-b7ce8000 r-xp 08:04 2181509/usr/lib/libxcb-xlib.so.0.0.0 b7ce8000-b7ce9000 r--p 08:04 2181509/usr/lib/libxcb-xlib.so.0.0.0 b7ce9000-b7cea000 rw-p 1000 08:04 2181509/usr/lib/libxcb-xlib.so.0.0.0 b7cea000-b7ceb000 rw-p b7cea000 00:00 0 b7ceb000-b7d0 r-xp 08:04 2180364/usr/lib/libICE.so.6.3.0 b7d0-b7d01000 rw-p 00014000 08:04 2180364/usr/lib/libICE.so.6.3.0 b7d01000-b7d03000 rw-p b7d01000 00:00 0 b7d03000-b7d0a000 r-xp 08:04 2179449/usr/lib/libSM.so.6.0.0 b7d0a000-b7d0b000 r--p 6000 08:04 2179449/usr/lib/libSM.so.6.0.0 b7d0b000-b7d0c000 rw-p 7000 08:04 2179449/usr/lib/libSM.so.6.0.0 b7d0c000-b7d21000 r-xp 08:04 2180427/usr/lib/libXmu.so.6.2.0 b7d21000-b7d22000 rw-p 00015000 08:04 2180427/usr/lib/libXmu.so.6.2.0 b7d22000-b7d2f000 r-xp 08:04 2180024/usr/lib/libXext.so.6.4.0 b7d2f000-b7d31000 rw-p c000 08:04 2180024/usr/lib/libXext.so.6.4.0 b7d31000-b7d45000 r-xp 08:04 2179310/usr/lib/libz.so.1.2.3.3 b7d45000-b7d47000 rw-p 00013000 08:04 2179310/usr/lib/libz.so.1.2.3.3 b7d47000-b7d48000 rw-p b7d47000 00:00 0 b7d48000-b7d95000 r-xp 08:04 2180441/usr/lib/libXt.so.6.0.0 b7d95000-b7d99000 rw-p 0004c000 08:04 2180441/usr/lib/libXt.so.6.0.0 b7d990Aborted (core dumped) Since I see "fortify" in the stack, it might either be: - a bug in xfig caught with fortify option of gcc (since Ubuntu compiles by default with -D_FORTIFY_SOURCE=2 I think). - or xfig is fine bug -D_FORTIFY_SOURCE=2 detects a spirious issue (which is possible). In that case, recompiling xfig with -D_FORTIFY_SOURCE=1 should be OK. In "man gcc", you can see the following: NOTE: In Ubuntu 8.10 and later versions, -D_FORTIFY_SOURCE=2 is set by default, and is activated when -O is set to 2 or higher. This
[Bug 304680] Re: Esperanto locale broken
It looks like Debian fixed this very recently (among other things). Hurray. See comments from Wed, 08 Apr 2009 there: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479058 I quote: > > * 003_recognize_glibc_2.3.2_locale_names.diff: don't comment out the eo_XX > entries from compose.dir and locale.dir (closes: #479058). Thanks, Luiz > Portella! ** Bug watch added: Debian Bug tracker #479058 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479058 -- Esperanto locale broken https://bugs.launchpad.net/bugs/304680 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 316973] Re: ftp crashes after some shell commands
*** This bug is a duplicate of bug 339569 *** https://bugs.launchpad.net/bugs/339569 ** This bug has been marked a duplicate of bug 339569 ftp command crashes when typing: !cd /tmp -- ftp crashes after some shell commands https://bugs.launchpad.net/bugs/316973 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339569] Re: ftp command crashes when typing: !cd /tmp
I deleted the bogus patch, correct patch is now attached. -- ftp command crashes when typing: !cd /tmp https://bugs.launchpad.net/bugs/339569 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339569] Re: ftp command crashes when typing: !cd /tmp
Sorry for the confusion :-( I attached the wrong patch in my previous comment (something totally unrelated!). I don't know how to delete my previous attachment. But I attache hereby the patch that I was meant to attach earlier. ** Attachment added: "patch to fix crash + memory leaks" http://launchpadlibrarian.net/24205259/fix-ftp-crash-and-leaks.patch ** Attachment removed: "patch to fix crash + memory leaks" http://launchpadlibrarian.net/24205202/fix-uninitialized-return- value-eval.c.patch -- ftp command crashes when typing: !cd /tmp https://bugs.launchpad.net/bugs/339569 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339569] Re: ftp command crashes when typing: !cd /tmp
I see the following error with valgrind when doing "!cd /tmp" in ftp. ==11101== Invalid write of size 4 ==11101==at 0x80549E5: makeargv (main.c:506) ==11101==by 0x80550EB: main (main.c:413) ==11101== Address 0x42251f0 is 0 bytes after a block of size 8 alloc'd ==11101==at 0x402603E: malloc (vg_replace_malloc.c:207) ==11101==by 0x80547D9: makeargv (main.c:495) ==11101==by 0x80550EB: main (main.c:413) ==11101== Warning: silly arg (0) to malloc() Code in main.c is: 494 /* allocate memory for $count-sized array of chars */ !!495 rargv = (char **) malloc( count * strlen(line)); 496 if (rargv == NULL) 497 fatal("Out of memory"); 498 499 INTOFF; 500 argbuf = obstack_alloc(&mainobstack, strlen(line) + 1); 501 INTON; 502 argp = rargv; 503 stringbase = line; /* scan from first of buffer */ 504 argbase = argbuf; /* store from first of buffer */ 505 slrflag = 0; !!506 while ((*argp++ = slurpstring())!=NULL) 507 rargc++; This code is quite a mess. The way rargv is allocated is completely wrong for several reasons. It should: - allocate count pointers (so multiply count by sizeof(char *) when doing malloc(...) and not by multiply count the non-sensical strlen(line)!? - Also it should increase count by 2 when command contains an exclation mark - it should add 1 to count for the final NULL pointer in argp - it should add an extra 1 to count since some commands such as "ls" or "put" may append an extra argument to argp! Attached patch fixes it. Attached patch also fixes some memory leak which you can reproduce by typing illegal or ambiguous commands. This for example was leaking: ftp> a ?Ambiguous command Every ambiguous commands (among other things) was leaking memory. -- Dominique ** Attachment added: "patch to fix crash + memory leaks" http://launchpadlibrarian.net/24205202/fix-uninitialized-return-value-eval.c.patch -- ftp command crashes when typing: !cd /tmp https://bugs.launchpad.net/bugs/339569 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339569] [NEW] ftp command crashes when typing: !cd /tmp
Public bug reported: I observe a reproducable crash (seg fault) when typing the command "!cd /tmp" in ftp. I'm using Ubuntu-8.10 $ ftp ftpperso.free.fr Connected to ftpperso.free.fr. 220 Serveur de mise a jour des pages perso de Free.fr version [May 5 2008 15:14:30] Name (ftpperso.free.fr:pel): dominique.pelle 331 Password required for dominique.pelle. Password: 230 User dominique.pelle logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to I ftp> !cd /tmp Segmentation fault (core dumped) Sometimes, doing the same thing crashes but prints more information: $ ftp ftpperso.free.fr Connected to ftpperso.free.fr. 220 Serveur de mise a jour des pages perso de Free.fr version [May 5 2008 15:14:30] Name (ftpperso.free.fr:pel): dominique.pelle 331 Password required for dominique.pelle. Password: 230 User dominique.pelle logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> !cd /tmp *** glibc detected *** ftp: corrupted double-linked list: 0x09674848 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0xb7d84f7f] /lib/tls/i686/cmov/libc.so.6[0xb7d86a8d] /lib/tls/i686/cmov/libc.so.6(__libc_malloc+0x95)[0xb7d888c5] /lib/tls/i686/cmov/libc.so.6(_obstack_begin+0x5e)[0xb7d8b61e] ftp[0x8054fb1] ftp[0x8055858] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7d2b685] ftp[0x8049c71] === Memory map: 08048000-08059000 r-xp 08:04 2180499/usr/bin/netkit-ftp 08059000-0805b000 rw-p 0001 08:04 2180499/usr/bin/netkit-ftp 0805b000-08069000 rw-p 0805b000 00:00 0 09664000-09685000 rw-p 09664000 00:00 0 [heap] b7b0-b7b21000 rw-p b7b0 00:00 0 b7b21000-b7c0 ---p b7b21000 00:00 0 b7c5d000-b7c6a000 r-xp 08:04 1894074/lib/libgcc_s.so.1 b7c6a000-b7c6b000 r--p c000 08:04 1894074/lib/libgcc_s.so.1 b7c6b000-b7c6c000 rw-p d000 08:04 1894074/lib/libgcc_s.so.1 b7c83000-b7cba000 r--p 08:04 2376727 /usr/lib/locale/eo_XX.utf8/LC_CTYPE b7cba000-b7cca000 r-xp 08:04 1909319 /lib/tls/i686/cmov/libresolv-2.8.90.so b7cca000-b7ccb000 r--p f000 08:04 1909319 /lib/tls/i686/cmov/libresolv-2.8.90.so b7ccb000-b7ccc000 rw-p 0001 08:04 1909319 /lib/tls/i686/cmov/libresolv-2.8.90.so b7ccc000-b7cce000 rw-p b7ccc000 00:00 0 b7cce000-b7cd2000 r-xp 08:04 1909311 /lib/tls/i686/cmov/libnss_dns-2.8.90.so b7cd2000-b7cd3000 r--p 3000 08:04 1909311 /lib/tls/i686/cmov/libnss_dns-2.8.90.so b7cd3000-b7cd4000 rw-p 4000 08:04 1909311 /lib/tls/i686/cmov/libnss_dns-2.8.90.so b7cd4000-b7cd6000 r-xp 08:04 1892447/lib/libnss_mdns4_minimal.so.2 b7cd6000-b7cd7000 rw-p 1000 08:04 1892447/lib/libnss_mdns4_minimal.so.2 b7cd7000-b7ce r-xp 08:04 1909314 /lib/tls/i686/cmov/libnss_nis-2.8.90.so b7ce-b7ce1000 r--p 8000 08:04 1909314 /lib/tls/i686/cmov/libnss_nis-2.8.90.so b7ce1000-b7ce2000 rw-p 9000 08:04 1909314 /lib/tls/i686/cmov/libnss_nis-2.8.90.so b7ce2000-b7cf7000 r-xp 08:04 1909309 /lib/tls/i686/cmov/libnsl-2.8.90.so b7cf7000-b7cf8000 r--p 00014000 08:04 1909309 /lib/tls/i686/cmov/libnsl-2.8.90.so b7cf8000-b7cf9000 rw-p 00015000 08:04 1909309 /lib/tls/i686/cmov/libnsl-2.8.90.so b7cf9000-b7cfb000 rw-p b7cf9000 00:00 0 b7cfb000-b7d02000 r-xp 08:04 1909310 /lib/tls/i686/cmov/libnss_compat-2.8.90.so b7d02000-b7d03000 r--p 6000 08:04 1909310 /lib/tls/i686/cmov/libnss_compat-2.8.90.so b7d03000-b7d04000 rw-p 7000 08:04 1909310 /lib/tls/i686/cmov/libnss_compat-2.8.90.so b7d04000-b7d0e000 r-xp 08:04 1909312 /lib/tls/i686/cmov/libnss_files-2.8.90.so b7d0e000-b7d0f000 r--p 9000 08:04 1909312 /lib/tls/i686/cmov/libnss_files-2.8.90.so b7d0f000-b7d1 rw-p a000 08:04 1909312 /lib/tls/i686/cmov/libnss_files-2.8.90.so b7d1-b7d11000 rw-p b7d1 00:00 0 b7d11000-b7d13000 r-xp 08:04 1909306 /lib/tls/i686/cmov/libdl-2.8.90.so b7d13000-b7d14000 r--p 1000 08:04 1909306 /lib/tls/i686/cmov/libdl-2.8.90.so b7d14000-b7d15000 rw-p 2000 08:04 1909306 /lib/tls/i686/cmov/libdl-2.8.90.so b7d15000-b7e6d000 r-xp 08:04 1909303 /lib/tls/i686/cmov/libc-2.8.90.so b7e6d000-b7e6f000 r--p 00158000 08:04 1909303 /lib/tls/i686/cmov/libc-2.8.90.so b7e6f000-b7e7 rw-p 0015a000 08:04 1909303 /lib/tls/i686/cmov/libc-2.8.90.so b7e7-b7e74000 rw-p b7e7 00:00 0 b7e74000-b7ea1000 r-xp 08:04 1892432/lib/libncurses.so.5.6 b7ea1000-b7ea4000 rw-p 0002c000 08:04 1892432/lib/libncurses.so.5.6 b7ea4000-b7ed r-xp 08:04 1892472/lib/libreadline.so.5.2 b7ed-b7ed4000 rw-p 0002c000 08:04 1892472/lib/libreadline.so.5.2 b7ed4000-b7ed5000 rw-p b7ed4000 00:00 0 b7ee1000-b7ee8000 r--s 08:04 2187878 /usr/lib/gconv/gconv-modules.cache b7ee8000-b7eee000 rw-p b7ee8000 00:00 0 b7eee000-b7f08000 r-xp 08:04 1892468/lib/ld-2.8.90.so
[Bug 291373] Re: vim: hang after ^Z / fg
This bug has now been fixed upstream in Vim-7.2.130. You can find the patch here: ftp://ftp.vim.org/pub/vim/patches/7.2/7.2.130 See also the summary of all pages available for Vim-7.2 available at: ftp://ftp.vim.org/pub/vim/patches/7.2/README No idea when this version will make it into Ubuntu packages. -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291373] Re: vim: hang after ^Z / fg
This is the message in vim_dev where I posted the patch: http://groups.google.com/group/vim_dev/tree/browse_frm/month/2009-2/2a9cb76087f154a2?rnum=361&start=250&_done=%2Fgroup%2Fvim_dev%2Fbrowse_frm%2Fmonth%2F2009-2%3Fstart%3D250%26sa%3DN%26#doc_b5e783c7690e9614 ** Attachment added: "fixed race condition in suspend resume with CTRL-Z fg" http://launchpadlibrarian.net/22983879/fix-race-condition-suspend-os_unix.c.patch -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291373] Re: vim: hang after ^Z / fg
It's probably also a good idea to make the variable "sigcont_received" volatile since it is changed in a signal handler. I will send the patch to the vim_dev mailing list. -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291373] Re: vim: hang after ^Z / fg
Put previous patch as attachment (since putting it in previous comment removed spaces) ** Attachment added: "patch to fix hang when doing fg after CTRL-Z" http://launchpadlibrarian.net/22976362/fix-race-suspend-os_unix.c.patch -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291373] Re: vim: hang after ^Z / fg
Thanks for the stack traces. That looks very useful. I've been able to reproduce this bug only twice so far. It's very rare on my machine but it did happen. >From your stack trace, I suppose that we can't assume that kill(0, SIGTSTP); is handled immediately (i.e. it's asynchronous) even though signal is sent to ouselves. So if the signal is handled after if (!sigcont_received) but before pause(); then we call pause() and we then wait for a signal that will never come anymore (which would hangs vim until we press CTRL-C. If so, we should not call pause() here. Yielding the CPU (sleep(0)) should be enough to have the signal handled when process is rescheduled since we sent it to ourselves. Can anybody confirm that the following patch fixes to bug? It works for me but since bug was very hard to reproduce on my machine it would be interesting to get feedback for other people, especially on Solaris since old code had a comment for Solaris. Index: os_unix.c === RCS file: /cvsroot/vim/vim7/src/os_unix.c,v retrieving revision 1.90 diff -c -r1.90 os_unix.c *** os_unix.c 22 Feb 2009 01:52:46 - 1.90 --- os_unix.c 22 Feb 2009 14:05:50 - *** *** 1122,1133 sigcont_received = FALSE; # endif kill(0, SIGTSTP); /* send ourselves a STOP signal */ ! # ifdef _REENTRANT ! /* When we didn't suspend immediately in the kill(), do it now. Happens ! * on multi-threaded Solaris. */ ! if (!sigcont_received) ! pause(); ! # endif # ifdef FEAT_TITLE /* --- 1122,1144 sigcont_received = FALSE; # endif kill(0, SIGTSTP); /* send ourselves a STOP signal */ ! /* ! * Wait for the STOP signal to be handled. It generally happens ! * immediately since signal is sent to ourselves, but somehow not ! * all the time. Do not call pause() because there would be race ! * condition which would hang Vim if signal happened in between the ! * test of sigcont_received and the call to pause(). If signal is ! * not yet received, call sleep(0) to just yield CPU. Signal should ! * then be received. If still not received, sleep 1, 2, 3 ms. ! * Don't bother waiting further if signal is not received after ! * 1+2+3+4 ms. ! */ ! { ! long wait; ! for (wait = 0; !sigcont_received && wait <= 3L; wait++) ! /* Loop is not entered most of the time */ ! mch_delay(wait, FALSE); ! } # ifdef FEAT_TITLE /* -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320958] Re: xterm renders some unicode characters incorrectly when using colors (or bold?)
> Can you test against Jaunty and see if the problem still exists? I have not installed Jaunty yet. So I can verify whether bug is still there. Hopefully someone else can verify it? If not, I will verify it when I upgrade to Jaunty after it's officially released. -- xterm renders some unicode characters incorrectly when using colors (or bold?) https://bugs.launchpad.net/bugs/320958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133323] Re: [Upstream] [hardy] English spelling checker of openoffice incorrectly accepts word "informations"
This bug is still in Ubuntu-8.10 (intrepid) which is using OpenOffice-2.4.1. -- [Upstream] [hardy] English spelling checker of openoffice incorrectly accepts word "informations" https://bugs.launchpad.net/bugs/133323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247161] Re: 'xterm -sb' seg faults
I don't observe this bug with Ubuntu-8.10 (intrepid) -- 'xterm -sb' seg faults https://bugs.launchpad.net/bugs/247161 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320388] Re: accentuated characters wrongly displayed (encoding problem) in title bar
I also observe this bug in Ubuntu-8.10 (intrepid). Very easy to reproduce. I'm using locale en_US.UTF-8. -- accentuated characters wrongly displayed (encoding problem) in title bar https://bugs.launchpad.net/bugs/320388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320958] Re: xterm renders some unicode characters incorrectly when using colors (or bold?)
** Description changed: Binary package hint: xterm Summary: xterm does not render some Unicode characters correctly when using colors (or maybe bold?) Bug only happens in xterm, other terminals (such as gnome-terminal) do not have this bug. Steps to reproduce: 1/ Open an xterm 2/ in xterm, create 4 files as follows: $ touch fooẹbar fooẹbar.jpg fooŭbar fooŭbar.jpg (you may want to copy paste above command if you don't know how to type those characters) ẹ is Unicode char 0x1EB9 ŭ is Unicode char 0x16d 3/ do a ls with colors: $ ls --color foo* fooẹbar fooẹbar.jpg fooŭbar fooŭbar.jpg 4/ Observe that the filename fooẹbar.jpg (second one) is not rendered properly whereas other filenames are somehow rendered correctly. I see a square instead of character ẹ when rendered in color (or bold?) whereas it's rendered correctly when not rendered in color (or bold?). I've put a screenshot of what I see at: http://dominique.pelle.free.fr/pic/bug-unicode-color-xterm.png Doing \ls (so that there is no color) in instead of ls --color shows the filename correctly. Interestingly, if I press CTRL + right click on the mouse in xterm to bring the xterm popup menu "VT Fonts", and if if I select the font size "Huge", then xterm renders character correctly. I'm using Ubuntu-8.10 Intrepid, xterm -v gives 'XTerm(235)'. + + I tried with TERM env variable set to xterm or to xterm-color + and bug happens in both cases. My locale is set to en_US.UTF-8. -- xterm renders some unicode characters incorrectly when using colors (or bold?) https://bugs.launchpad.net/bugs/320958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 320958] [NEW] xterm renders some unicode characters incorrectly when using colors (or bold?)
Public bug reported: Binary package hint: xterm Summary: xterm does not render some Unicode characters correctly when using colors (or maybe bold?) Bug only happens in xterm, other terminals (such as gnome-terminal) do not have this bug. Steps to reproduce: 1/ Open an xterm 2/ in xterm, create 4 files as follows: $ touch fooẹbar fooẹbar.jpg fooŭbar fooŭbar.jpg (you may want to copy paste above command if you don't know how to type those characters) ẹ is Unicode char 0x1EB9 ŭ is Unicode char 0x16d 3/ do a ls with colors: $ ls --color foo* fooẹbar fooẹbar.jpg fooŭbar fooŭbar.jpg 4/ Observe that the filename fooẹbar.jpg (second one) is not rendered properly whereas other filenames are somehow rendered correctly. I see a square instead of character ẹ when rendered in color (or bold?) whereas it's rendered correctly when not rendered in color (or bold?). I've put a screenshot of what I see at: http://dominique.pelle.free.fr/pic/bug-unicode-color-xterm.png Doing \ls (so that there is no color) in instead of ls --color shows the filename correctly. Interestingly, if I press CTRL + right click on the mouse in xterm to bring the xterm popup menu "VT Fonts", and if if I select the font size "Huge", then xterm renders character correctly. I'm using Ubuntu-8.10 Intrepid, xterm -v gives 'XTerm(235)'. ** Affects: xterm (Ubuntu) Importance: Undecided Status: New ** Summary changed: - xterm render some unicode characters incorrectly when using colors + xterm renders some unicode characters incorrectly when using colors (or bold?) -- xterm renders some unicode characters incorrectly when using colors (or bold?) https://bugs.launchpad.net/bugs/320958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304680] Re: Esperanto locale broken
Attached output of 'lspci -vvnn' as requested (though I think it's not relevant). ** Attachment added: "output of lspci -vvnn as requested." http://launchpadlibrarian.net/21298502/lspci-vvnn.txt -- Esperanto locale broken https://bugs.launchpad.net/bugs/304680 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183760] Re: Changing font size in a maximized window doesn't recalculate usable area
This bug is upstream but it's a valid bug. I really don't understand why it gets marked as INVALID because someone asked whether it happened in 9.04 (which has not even been officially released yet since its only Jan 2009). The bug still happens in the latest release Ubuntu-8.10 (Intrepid). -- Changing font size in a maximized window doesn't recalculate usable area https://bugs.launchpad.net/bugs/183760 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315740] Re: Breton keyboard layout C'HWERTY not supported
The link below details all the files that I modified to get my C'HWERTY keyboard to work on Ubuntu-8.10. It provides full files as well as patches: http://dominiko.livejournal.com/20206.html Some of the files are already being integrated in the official Xorg. See: https://bugs.freedesktop.org/show_bug.cgi?id=19506 http://lists.freedesktop.org/archives/xorg/2009-January/042335.html -- Breton keyboard layout C'HWERTY not supported https://bugs.launchpad.net/bugs/315740 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315740] Re: Breton keyboard layout C'HWERTY not supported
Ah never mind, after spending a few hours, I found how to configure xkb on Ubuntu to define my own keyboard. I will attach the modified files here when I'm happy enough with it, so hopefully the C'HWERTY keyboard can be integrated into the next versions of Ubuntu. -- Breton keyboard layout C'HWERTY not supported https://bugs.launchpad.net/bugs/315740 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315740] [NEW] Breton keyboard layout C'HWERTY not supported
Public bug reported: Ubuntu has configuration for several keyboard layouts, but my C'HWERTY keyboard (that's the Breton keyboard if you need to know) is not supported. Support for C'HWERTY keyboard layout would be welcome. Doing a Google search, a found a xmodmap file for C'HWERTY keyboard, but it does not work well: some keys work in terminal but not all of them (arrow keys are broken, C'H key does not work, page up broken, etc...). And in gnome applications it does not work at all. I think xmodmap is deprecated anyway (probably why it did not work in GNOME applications). But then I'm still confused how I can configure my keyboard on Ubuntu. I've put a picture of the keyboard in wikimedia commons: - http://upload.wikimedia.org/wikipedia/commons/9/9e/Bretona-klavaro.jpg Some more info about the keyboard C'HWERTY layout: - http://www.drouizig.org/Saozneg/Keyboard/keyboard-index.html xmodmap file for C'HWERTY (but broken for me at least on Ubuntu): - http://www.drouizig.org/Saozneg/Keyboard/keyboard-Linuxsupport.html I'm using Ubuntu-8.10 (Intrepid). ** Affects: ubuntu Importance: Undecided Status: New -- Breton keyboard layout C'HWERTY not supported https://bugs.launchpad.net/bugs/315740 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312563] [NEW] xvidcap: xtoffmpeg.c guess_input_pix_fmt(): image depth 32 not supported ... aborting
Public bug reported: Binary package hint: xvidcap I'm trying to use xvidcap tool but it crashes all the time with the following error: xtoffmpeg.c guess_input_pix_fmt(): image depth 32 not supported ... aborting Steps to reproduce: 1/ start xvidcap from shell: xvidcap The GUI pops up. 2/ Click on the button "Select Rectangular Area to Capture" button (that's the second button from the right) 3/ Click on a terminal window to capture its content with xvidcap 4/ observe the error message: xtoffmpeg.c guess_input_pix_fmt(): image depth 32 not supported ... aborting ... and xvidcap exits immediately. This is with Intrepid (Ubuntu 8.10, latest updates) ** Affects: xvidcap (Ubuntu) Importance: Undecided Status: New -- xvidcap: xtoffmpeg.c guess_input_pix_fmt(): image depth 32 not supported ... aborting https://bugs.launchpad.net/bugs/312563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296216] Re: After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly
Chauncellor write: > I backed those two files up and replaced them with your edits, rebooted > for good measure, but nothing was changed. Was there something else I > was supposed to do? You seem like you have it pinpointed, so I probably > didn't do something right. I assume you're referring to my comment regarding bug #304680 where I patched /usr/share/X11/locale/locale.dir and /usr/share/X11/locale/compose.dir. This is most likely *not* to be root cause of the problem of other people than me, since it's only relevant if you're using the eo_XX.UTF-8 locale. IWhich is why you don't observe any improvement after applying the patch. Which locale are you using? You can find out by entering the 'locale' command from shell. On my machine (where compose key now works after tweaking /usr/share/X11/locale/{locale,compose}.dir: $ locale LANG=eo_XX.UTF-8 LC_CTYPE="eo_XX.UTF-8" LC_NUMERIC="eo_XX.UTF-8" LC_TIME="eo_XX.UTF-8" LC_COLLATE="eo_XX.UTF-8" LC_MONETARY="eo_XX.UTF-8" LC_MESSAGES="eo_XX.UTF-8" LC_PAPER="eo_XX.UTF-8" LC_NAME="eo_XX.UTF-8" LC_ADDRESS="eo_XX.UTF-8" LC_TELEPHONE="eo_XX.UTF-8" LC_MEASUREMENT="eo_XX.UTF-8" LC_IDENTIFICATION="eo_XX.UTF-8" LC_ALL= -- After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly https://bugs.launchpad.net/bugs/296216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296216] Re: After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly
In earlier comments, I mentioned that I was affected by this bug. It turned out that it was because of a specific reason, most certainly different than other submitters. I opened a separate issue (bug #304680) and submitted a patch. In a nutshell, compose key did not work for me (among other things) because locale is broken when using eo_XX.UTF-8 (Esperanto locale). After fixing my locale, my compose key is now working fine in Intrepid (Ubuntu-8.10). -- After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly https://bugs.launchpad.net/bugs/296216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304680] Re: Esperanto locale broken
** Tags added: esperanto locale -- Esperanto locale broken https://bugs.launchpad.net/bugs/304680 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304680] Re: Esperanto locale broken
** Attachment added: "patch for file /usr/share/X11/locale/compose.dir" http://launchpadlibrarian.net/20173746/compose.dir.patch -- Esperanto locale broken https://bugs.launchpad.net/bugs/304680 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304680] Re: Esperanto locale broken
** Attachment added: "patch for file /usr/share/X11/locale/locale.dir" http://launchpadlibrarian.net/20173742/locale.dir.patch -- Esperanto locale broken https://bugs.launchpad.net/bugs/304680 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304680] [NEW] Esperanto locale broken
Public bug reported: Binary package hint: libx11-data The Esperanto locale is broken in Ubuntu Ubuntu-8.10 Intrepid. It was already broken in previous releases, I can't remember when the regression was introduced, but at least Ubuntu-8.04.1 was also affected. I initially reported this as comment in bug #83142, but in hindsight, it might be a different issue so I open this new bug. When setting my locale to eo_XX.UTF-8, I noticed several bugs, at least those 3 problems: * the compose key does not work at all. * vim-7.1.314 from Ubuntu-8.10 crashed (segfault) when using X clipboard with visual selection. This bug is discussed in more details in vim mailing list, see: http://groups.google.com/group/vim_dev/browse_thread/thread/55612319d5c737ca * gnome-terminal worked but xterm defaulted to "C" locale. These 3 bugs only happen because eo_XX.UTF-8 locale in Ubuntu is broken. Changing locale to en_US.UTF-8 or fr_FR.UTF-8 for example makes everything work. It is easy to fix: I see that the Esperanto settings in files /usr/share/X11/locale/locale.dir and /usr/share/X11/locale/compose.dir are commented out (!?) Uncommenting them resolves all 3 problems. -> Please uncomment those lines. I've been using it with the fix without problems. Ubuntu works fine with the eo_XX.UTF-8 uncommented out and it fixes the 3 issues I described. I think the only reasons those line were commented out is because someone did check for non existing country codes and stumbled upon XX. But this change was incorrect, since it breaks havoc the Esperanto locale, and it was probably not well reviewed, since the comment even included a typo (*Esperato* instead of Esperanto) The country code XX should be OK, see: http://unicode.org/reports/tr35/tr35-6.html ... and search for territory_code, twice, and you will see that XX is a code allowed for private use, which is the case, since Esperanto is a language that doesn't necessary belong to a specific territory. To quote the page: "The private use codes from XA..XZ will never be used by CLDR, and are thus safe for use for other purposes by applications using CLDR data." I see that Debian Lenny/sid also has the same bug. But unlike Ubuntu or Debian, I see that in the file /usr/share/X11/locale/locale.dir on OpenSUSE-11.0 is fine: the Esperanto locale settings are *not* commented out. Attached is the patched /usr/share/X11/locale/locale.dir and /usr/share/X11/locale/compose.dir files. Please notice: * esperanto setting uncommented * some colon characters removed The offending package should be libx11-data: $ dpkg --search /usr/share/X11/locale/locale.dir libx11-data: /usr/share/X11/locale/locale.dir ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- Esperanto locale broken https://bugs.launchpad.net/bugs/304680 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71322] Re: reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale
This is still reproducible in Ubuntu-8.10 Intrepid Ibex. $ LC_ALL=en_GB.UTF-8 aspell list < /dev/null Segmentation fault (core dumped) -- reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale https://bugs.launchpad.net/bugs/71322 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83142] Re: crash on XSetIMValues() call when using xim and esperanto locale
patch of /usr/share/locale/compose.dir, see above comment. Can this fix be included in the next release of Ubuntu? ** Attachment added: "patch of /usr/share/locale/compose.dir" http://launchpadlibrarian.net/19795792/compose.dir.patch -- crash on XSetIMValues() call when using xim and esperanto locale https://bugs.launchpad.net/bugs/83142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83142] Re: crash on XSetIMValues() call when using xim and esperanto locale
I have have installed Ubuntu-8.10 Intrepid (upgrade from 8.04.1) and I noticed several bugs: * the compose key did not work at all * vim-7.1.314 from Ubuntu-8.10 crashed when using X clipboard with visual selection. This bug is discussed in more details in vim mailing list, see: http://groups.google.com/group/vim_dev/browse_thread/thread/55612319d5c737ca * gnome-terminal worked bug xterm defaulted to "C" locale. These 3 bugs only happened because eo_XX.UTF-8 locale in Ubuntu is broken, and it is easy to fix. I saw that the Esperanto settings in files /usr/share/X11/locale/locale.dir and /usr/share/X11/locale/compose.dir are commented out. Uncommenting them resolved all 3 problems. Please uncomment those lines. I've been using it with the fix without problems. Ubuntu works fine with the eo_XX.UTF-8 uncommented out and it fixes the 3 issues I described. I think the only reasons those line were commented out is because someone did check for non existing country codes and stumbled upon XX. But this should be OK as pointed out by previous comments. This incorrect change was probably not well reviewed, since the comment even included a typo (*Esperato* instead of Esperanto) I also saw the file /usr/share/X11/locale/locale.dir on OpenSUSE-11.0 and the Esperanto locale settings were not commented there. Attached is the patch /usr/share/X11/locale/locale.dir file. Please notice: * esperanto setting uncommented * some colon characters removed ** Attachment added: "patch /usr/share/X11/locale/locale.dir" http://launchpadlibrarian.net/19795749/locale.dir.patch -- crash on XSetIMValues() call when using xim and esperanto locale https://bugs.launchpad.net/bugs/83142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231512] Re: xterm does not handle bold characters properly (regression in Hardy)
> [...] We were wondering is this still an issue for you? I have installed Ubuntu-8.10, and this issue is fixed in xterm. Bug can be marked as resolved. -- xterm does not handle bold characters properly (regression in Hardy) https://bugs.launchpad.net/bugs/231512 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296216] Re: After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/19654070/xorg.conf -- After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly https://bugs.launchpad.net/bugs/296216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296216] Re: After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly
** Attachment added: "/var/log/Xorg.0.log" http://launchpadlibrarian.net/19654062/Xorg.0.log -- After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly https://bugs.launchpad.net/bugs/296216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296216] Re: After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly
Same issue here. I attach `lspc --vvnn` output + /var/log/Xorg.0.log + /etc/X11/xorg.conf. ** Attachment added: "lspc-vvnn.txt" http://launchpadlibrarian.net/19654026/lspc-vvnn.txt -- After Upgrade from Hardy to Intrepid Compose Key No longer Functions Correctly https://bugs.launchpad.net/bugs/296216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290506] Re: cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards
Using Ubuntu-8.04.1, my webcam is working with skype. ekiga or aMSN, but it's not working with cheese. I have HPdv9000 laptop with a Ricoh builtin webcam: $ lsusb Bus 005 Device 003: ID 05ca:1810 Ricoh Co., Ltd Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 003 Device 001: ID : Bus 002 Device 003: ID 04f3:0210 Elan Microelectronics Corp. Bus 002 Device 001: ID : Bus 001 Device 001: ID : -- cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards https://bugs.launchpad.net/bugs/290506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183760] Re: Changing font size in a maximized window doesn't recalculate usable area
I can reproduce this bug with Ubuntu-8.04 using Vim-7.1.138 which comes with Hardy. I can also still reproduce it if I compile the latest Vim-7.2.26. -- Changing font size in a maximized window doesn't recalculate usable area https://bugs.launchpad.net/bugs/183760 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152915] Re: fonts displayed wrong in gvim
Is this bug still happening? I tried to reproduce it with Ubuntu-8.04 but I could not: vim worked fine for me when using locale zh_CN.UTF-8 in Ubuntu-8.04. -- fonts displayed wrong in gvim https://bugs.launchpad.net/bugs/152915 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133265] Re: crash on switching tab (I think)
Which version of Ubuntu is this? It's yet another case of double free in vim, this is probably a dupe of Bug #219546 and Bug #215374. This is probably the patch that fixes it (from Oct 30, 2007, a year ago): 7.1.147 (after 7.1.127) freeing memory twice completing user name -- crash on switching tab (I think) https://bugs.launchpad.net/bugs/133265 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195264] Re: vim.gnome crashed with SIGSEGV in free()
Vim-7.1.138 in Ubuntu-8.04 has a known severe bug which causes it to segfault (double free). It happens at least when doing completion on user names. It's fixed upstream on Oct 30 2007 (more than 1 year ago) in this patch: 7.1.147 (after 7.1.127) freeing memory twice completing user name I assume you stumbled upon this bug. This bug is probably a duplicate with several other Vim bugs such as Bug #215374 and Bug #219546 (possibly others). My advice is to compile vim yourself. Latest version of vim is 7.2.26 and it fixes the double free bug and many other bugs. You can see all the bugs fixed since 7.1.138 there: ftp://ftp.vim.org/pub/vim/patches/7.1/README ftp://ftp.vim.org/pub/vim/patches/7.2/README Any chance to get a newer vim in Ubuntu-8.04? -- vim.gnome crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/195264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270386] Re: Vim pegs the CPU when typing ( open paren
The following patch could from Jan 6 2008 could also be relevant: Patch 7.1.211 Problem:The matchparen plugin may take an unexpected amount of time, so that it looks like Vim hangs. Solution: Add a timeout to searchpair(), searchpairpos(), search() and searchpos(). Use half a second timeout in the plugin. Files: runtime/doc/eval.txt, runtime/plugin/matchparen.vim, src/edit.c, src/eval.c, src/ex_cmds2.c, src/ex_docmd.c, src/normal.c, src/proto/eval.pro, src/proto/ex_cmds2.pro, src/proto/search.pro, src/search.c -- Vim pegs the CPU when typing ( open paren https://bugs.launchpad.net/bugs/270386 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270386] Re: Vim pegs the CPU when typing ( open paren
I could not reproduce it somehow, but the bug description sounds an awful lot like the following bug which was fixed in vim-7.1.227 on Jan 13 2008: Patch 7.1.227 Problem:Hang in syntax HL when moving over a ")". (Dominique Pelle) Solution: Avoid storing a syntax state in the wrong position in the list of remembered states. Files: src/syntax.c -- Vim pegs the CPU when typing ( open paren https://bugs.launchpad.net/bugs/270386 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291373] Re: vim: hang after ^Z / fg
I can't reproduce this bug. Could it be caused by some settings in your ~/.vimrc or some plugin that you installed? Can you try first to run vim with: "vim -u NONE" to avoid loading ~/.vimrc and plugins. If it then works, you can try commenting things in your ~/.vimrc or move out your ~/.vim directory until you find what setting or plugin is triggering the bug. -- vim: hang after ^Z / fg https://bugs.launchpad.net/bugs/291373 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235883] Re: gnome-terminal is handling wierdly french ipa nasal wowels signs
I've noticed that too quite a wile ago. Gnome terminal (and terminator) don't handle properly composing Unicode characters. The first character in the attached file "french ipa signs" is composed of: <ɛ> Hex 025b + < ̃> Hex 0303 (utf-8 sequence: c9 9b + cc 83) (you can check that by the ga or g8 command in vim) 0x303 is a composing character so normally it should be displayed on top of the previous character. But gnome terminal does not do it properly. gvim does display it properly. -- gnome-terminal is handling wierdly french ipa nasal wowels signs https://bugs.launchpad.net/bugs/235883 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240693] Re: vim-gnome is very slow to load
I suspect your DISPLAY env variable is incorrecty set, or set to a remote machine which is somehow slow to access. Using vim -X would ignore DISPLAY so should be fast. This is probably not a bug in Vim. -- vim-gnome is very slow to load https://bugs.launchpad.net/bugs/240693 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239948] [NEW] typo in default user's ~/.bashrc file
Public bug reported: When creating a user, Ubuntu creates a default ~/.bashrc file. I see a typo in the comment in this file: *sucessive* -> successive Also, why HISTCONTROL variable is set twice in ~/.bashrc? One should be commented or removed. # don't put duplicate lines in the history. See bash(1) for more options export HISTCONTROL=ignoredups # ... and ignore same sucessive entries. export HISTCONTROL=ignoreboth ** Affects: ubuntu Importance: Undecided Status: New -- typo in default user's ~/.bashrc file https://bugs.launchpad.net/bugs/239948 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232264] Re: vim (and gvim) crash frequently
This bug has already been fixed upstream in patch 7.1.147 of Vim (on Oct 30, 2007, yes, that's quite a while ago): 7.1.147 (after 7.1.127) freeing memory twice completing user name ... but Vim in Ubuntu-8.04 is still using Vim-7.1.138. This bug is also most certainly a dupe of bug #219546. My advice is to compile latest Vim (7.1.298) from www.vim.org until the fix is put into Hardy. Can we backport a more recent version Vim? Crashes in the text editor are not good. -- vim (and gvim) crash frequently https://bugs.launchpad.net/bugs/232264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231512] [NEW] xterm does not handle bold characters properly (regression in Hardy)
Public bug reported: Binary package hint: xterm I'm using xterm with Ubuntu-8.04 (Hardy) and notice something wrong with the way xterm handles bold characters. xterm displays bold characters fine in vim, until I press page-up (causing a visualbell) and then bold character no longer appear in bold. I need to reset xterm or start another one to see bold characters again. I don't think this is a vim bug because it only happens in xterm. gnome-terminal is fine. Steps to reproduce: 1) Open a _new_ xterm window (don't do it in an already existing window!) and enter the following command: $ vim -c ':so http://dominique.pelle.free.fr/.vimrc | help' This should display the vim help page as in: http://dominique.pelle.free.fr/xterm-bug-1.png Notice at the bottom how "WHAT" "PREPEND" and "EXAMPLE" are show in bold grey characters (as expected). 2) Now press . It should trigger the visual bell (which makes the screen flicker). Notice that the characters that were in bold (WHAT, PREPEND, EXAMPLE) are no longer in bold (bug!). This is what I see after pressing : http://dominique.pelle.free.fr/xterm-bug-2.png (notice the slight difference with previous screenshot, no bold characters in screenshot 2) Even quiting vim and reopening it won't restore bold characters. To get characters in bold again, I need to open a new xterm. I have another machine with Ubuntu-7.04 and I don't observe that there, so it's a regression. Although I no longer have a machine with Ubuntu-7.10 (Gutsy), I don't think it was in Gutsy either so it's a regression which started to appear in Ubuntu-8.04 (Hardy). ** Affects: xterm (Ubuntu) Importance: Undecided Status: New -- xterm does not handle bold characters properly (regression in Hardy) https://bugs.launchpad.net/bugs/231512 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226342] Re: pulseaudio module-alsa-sink.c Error...
Same bug on my HP dv9000 Pavilion laptop. After using the laptop for a few minutes, I notice that sound stops working. From then on, I can't start applications from GNOME menu (gnome-terminal hangs from example). I see those errors in logs: [EMAIL PROTECTED]:~$ tail -f /var/log/messages May 11 09:57:25 pel-laptop kernel: [ 51.276557] NET: Registered protocol family 10 May 11 09:57:25 pel-laptop kernel: [ 51.276806] lo: Disabled Privacy Extensions May 11 09:57:39 pel-laptop pulseaudio[5937]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz. May 11 09:57:39 pel-laptop pulseaudio[5937]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz. May 11 09:57:39 pel-laptop pulseaudio[5937]: alsa-util.c: Cannot find fallback mixer control "Mic". May 11 10:17:11 pel-laptop -- MARK -- May 11 10:26:14 pel-laptop pulseaudio[5937]: sink-input.c: Failed to create sink input: too many inputs per sink. May 11 10:34:20 pel-laptop pulseaudio[5937]: sink-input.c: Failed to create sink input: too many inputs per sink. May 11 10:37:08 pel-laptop kernel: [ 1778.924660] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_i> May 11 10:37:08 pel-laptop pulseaudio[5937]: sink-input.c: Failed to create sink input: too many inputs per sink. Here is my sound card: $ lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) -- pulseaudio module-alsa-sink.c Error... https://bugs.launchpad.net/bugs/226342 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43484] Re: poor disk performance during heavy io
Journaling file systems (such as ext3) are slow at fsync. See what Linus writes in this thread about this particular problem (http://kerneltrap.org/node/14148) === BEGIN QUOTE === > hm, it turns out that it's due to vim doing an occasional fsync not only > on writeout, but during normal use too. "set nofsync" in the .vimrc > solves this problem. Yes, that's independent. The fact is, ext3 *sucks* at fsync. I hate hate hate it. It's totally unusable, imnsho. The whole point of fsync() is that it should sync only that one file, and avoid syncing all the other stuff that is going on, and ext3 violates that, because it ends up having to sync the whole log, or something like that. So even if vim really wants to sync a small file, you end up waiting for megabytes of data being written out. I detest logging filesystems. === [ END QUOTE ] === -- poor disk performance during heavy io https://bugs.launchpad.net/bugs/43484 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222739] Re: xterm segfaults after a while.
Package for this bug was incorrect. I replaced firefox-3 with xterm. ** Changed in: xterm (Ubuntu) Sourcepackagename: firefox-3.0 => xterm -- xterm segfaults after a while. https://bugs.launchpad.net/bugs/222739 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116753] Re: "locale not supported by Xlib" message when starting xterm (my locale is eo_XX.UTF-8)
I no longer observe this bug in hardy. I suggest to close this issue. -- "locale not supported by Xlib" message when starting xterm (my locale is eo_XX.UTF-8) https://bugs.launchpad.net/bugs/116753 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127399] Re: bogus background command often causes shell to exit
I still observe this bug after upgrade to Hardy. -- bogus background command often causes shell to exit https://bugs.launchpad.net/bugs/127399 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 197076] Re: "man gvcolor" shows error message
This no longer happens in Hardy (8.04). I'd suggest to close the bug. -- "man gvcolor" shows error message https://bugs.launchpad.net/bugs/197076 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 215374] Re: Vim crash when trying to expand a path
Yes, I can reproduce that too. This bug has already been fixed in latest vim from CVS (in patch 7.1.147 which was released on Tue, Oct 30, 2007). But Ubuntu Hardy is using an older version: vim-7.1.138 (which was released on Oct 9, 2007). Here is the patch description which fixes it: 7.1.147 (after 7.1.127) freeing memory twice completing user name Can we backport a more recent vim? It would fix several issues. The latest vim from CVS is vim-7.1.293 (apr-9) which I've been using and testing since it was released looks very stable. Updating would fix not only this issue but other opened vim issues which I have investigated such as at least: - bug #215374 (this bug) (fixed in vim-7.1.147) - bug #129106 vim crashes when gnome-terminal tab is detached (fixed in vim-7.1.166) - bug #68960 fix hangs when editing a specific file (fixed in vim 7.1.227) - bug #219546 vim crashes when pressing tab and using rails.vim (no longer happens in latest vim-7.1.293, not sure which patch fixes it, possibly also 7.1.147) -- Vim crash when trying to expand a path https://bugs.launchpad.net/bugs/215374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222901] Re: 5 tab limit in Firefox 3 b5
I can't reproduce that bug with Hardy. I opened 7 tabs successfully without problem (pressing CTRL-T). Firefox correctly goes the the address I type in the location bar. -- 5 tab limit in Firefox 3 b5 https://bugs.launchpad.net/bugs/222901 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156913] Re: Installing the Esperanto language pack does not offer Esperanto in choices
Finally, after trying several experimentations, I got my locale in Esperanto with Hardy. I had forgotten to do: "sudo mv /usr/share/i18n/locales/eo into /usr/share/i18n/locales/eo_XX" After that, "sudo dpkg-reconfigure locales" created the esperanto locale. So there is a workaround but hopefully bug can be fixed soon. -- Installing the Esperanto language pack does not offer Esperanto in choices https://bugs.launchpad.net/bugs/156913 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156913] Re: Installing the Esperanto language pack does not offer Esperanto in choices
I read the previous comments from Bertilo and Joop, but none of this works for me. When I do "sudo apt-get install language-pack-eo", it does not create any Esperanto locale. $ sudo apt-get install language-pack-eo ... $ locale -a C en_AU.utf8 en_BW.utf8 en_CA.utf8 en_DK.utf8 en_GB.utf8 en_HK.utf8 en_IE.utf8 en_IN en_NZ.utf8 en_PH.utf8 en_SG.utf8 en_US.utf8 en_ZA.utf8 en_ZW.utf8 POSIX No Esperanto locale, I'd expect to find eo_XX.utf8 there. My file my "/var/lib/locales/supported.d/local" only contains: en_US.UTF-8 UTF-8 Reconfiguring my locale, does not rebuild Esperanto locale: $ sudo dpkg-reconfigure locales Generating locales... en_AU.UTF-8... done en_BW.UTF-8... done en_CA.UTF-8... done en_DK.UTF-8... done en_GB.UTF-8... done en_HK.UTF-8... done en_IE.UTF-8... done en_IN.UTF-8... done en_NZ.UTF-8... done en_PH.UTF-8... done en_SG.UTF-8... done en_US.UTF-8... done en_ZA.UTF-8... done en_ZW.UTF-8... done When I installed Hardy (from scratch, not upgraded), I installed it in English (then later tried to add the Esperanto locale) Perhaps Bertilo and Joop installed it in Esperanto? I also tried tweaking /usr/share/X11/locale/{compose,locale}.dir as described by Joop but without any effect. What is also odd is that it behaves differently for different people. For example, I did not have that bug with Gutsy but reading above comments, several people had this bug with Gutsy. When I installed Gutsy, it was a dist-upgrade from Feisty. Now with Hardy, I did an install from scratch and I do get the bug. A bit disheartening, knowing that when I reported this bug initially in Ubuntu-5.04 (#23435) 3 years ago, it was then fixed but then reappears. -- Installing the Esperanto language pack does not offer Esperanto in choices https://bugs.launchpad.net/bugs/156913 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219546] Re: vim crashed using rails.vim on Hardy
Thanks for the step by step description. Following the explanations from "matrixise" I could also reproduce the bug when doing ":REcontroller te" which segfaults (press tab twice): [EMAIL PROTECTED]:~/test_crash$ /usr/bin/vim Vim: Caught deadly signal SEGV This is happening with vim-full from Hardy: [EMAIL PROTECTED]:~/test_crash$ /usr/bin/vim --version VIM - Vi IMproved 7.1 (2007 May 12, compiled Jan 31 2008 12:00:11) Included patches: 1-138 Now, running with valgrind, I can see several errors but the last one must be the one which causes the crash: ==10292== Invalid free() / delete / delete[] ==10292==at 0x402265C: free (vg_replace_malloc.c:323) ==10292==by 0x80CD2FA: ExpandOne (in /usr/bin/vim.gnome) ==10292==by 0x80CF245: (within /usr/bin/vim.gnome) ==10292==by 0x80D0EF3: getcmdline (in /usr/bin/vim.gnome) ==10292==by 0x80C5AF3: do_cmdline (in /usr/bin/vim.gnome) ==10292==by 0x81305FE: (within /usr/bin/vim.gnome) ==10292==by 0x8132FAB: normal_cmd (in /usr/bin/vim.gnome) ==10292==by 0x80F736F: main_loop (in /usr/bin/vim.gnome) ==10292==by 0x80FA972: main (in /usr/bin/vim.gnome) ==10292== Address 0x67f57b8 is 0 bytes inside a block of size 3 free'd ==10292==at 0x402265C: free (vg_replace_malloc.c:323) ==10292==by 0x80CD320: ExpandOne (in /usr/bin/vim.gnome) ==10292==by 0x809744F: (within /usr/bin/vim.gnome) ==10292==by 0x809D4D0: (within /usr/bin/vim.gnome) ==10292==by 0x80A07F7: (within /usr/bin/vim.gnome) ==10292==by 0x80A1D83: (within /usr/bin/vim.gnome) ==10292==by 0x80A254C: (within /usr/bin/vim.gnome) ==10292==by 0x809EF81: (within /usr/bin/vim.gnome) ==10292==by 0x809F207: (within /usr/bin/vim.gnome) ==10292==by 0x809FA3B: (within /usr/bin/vim.gnome) ==10292==by 0x809FB5B: (within /usr/bin/vim.gnome) ==10292==by 0x80A10CD: (within /usr/bin/vim.gnome) Unfortunately, /usr/bin/vim is not built with symbols, but the message shows that there is an invalid free() in the ExpandOne() function of Vim. If I download the latest vim (vim-7.1.293) source code (see http://www.vim.org/download.php), and compiled it myself: cd vim7 ./configure --with-features=huge make make install Then it works fine and valgrind does not complain either. So this bug must have already been already fixed in latest vim. Note the Hardy is using vim-7.1.138 and latest vim from CVS is vim-7.1.293. It would be a good idea to do an Ubuntut package with a more recent vim, many bugs have been fixed. Here are all the missing patches in vim as shipped with Ubuntu: 1557 7.1.139 fold truncated when ending Insert mode with CTRL-C 1664 7.1.140 v:count can't be used in an expression mapping 2806 7.1.141 GTK: can't use negative offset with -geom argument 2161 7.1.142 ":redir @A>" doesn't work 1723 7.1.143 uninitialized memory read when diffing three files 1250 7.1.144 after ":diffup" cursor can be in the wrong position 6160 7.1.145 stay in Insert completion mode depending on the char typed 2838 7.1.146 VMS: writing fails for rare record organisation 2079 7.1.147 (after 7.1.127) freeing memory twice completing user name 2557 7.1.148 QNX and some other systems require testing for sys/types.h 4823 7.1.149 completion menu messed up when using the scroll bar 1759 7.1.150 Visual mode "p" doesn't work when 'clipboard' has "unnamed" 2108 7.1.151 lalloc(0) error for line completion with 'ic' and 'inf' set 3183 7.1.152 display problem when 'hls' and 'cursorcolumn' are set 4610 7.1.153 compiler warnings on SGI 1547 7.1.154 (after 7.1.152) compiler warning for signed/unsigned compare 1594 7.1.155 crash when 'undolevels' is 0 and repeating "udd" 4174 7.1.156 overlapping arguments for strcpy() during cmdline completion 1541 7.1.157 :" in Ex mode at end of file results in an error message 4629 7.1.158 (extra) Win32: with utf-8 and cp1250 Alt-y is the wrong char 1646 7.1.159 overlapping arguments for a strcpy() 1661 7.1.160 getting/losing focus may cause hit-enter prompt to be redrawn 4347 7.1.161 compilation errors with tiny features and EXITFREE 4691 7.1.162 crash when using a modifier before "while" or "for" 2367 7.1.163 warning for the unknown option 'bufsecret' 1576 7.1.164 reading past end of regexp pattern 5538 7.1.165 crash related to getting X window ID 2134 7.1.166 memory leak when using "gp" in Visual mode 2528 7.1.167 xxd crashes when using "xxd -b -c 110" 2989 7.1.168 (extra) Win32 GUI: when no focus click doesn't position cursor 1926 7.1.169 using uninitialized memory when system() fails 1722 7.1.170 overlapping arguments to strcpy() 2324 7.1.171 reading one byte before allocated memory. 1536 7.1.172 if 'buftype' is "acwrite" Vim still does overwrite check 1928 7.1.173 accessing freed memory when using "\%^" pattern 2197 7.1.174 writing NUL past end of a buffer 4722 7.1.175 doesn'
[Bug 219546] Re: vim crashed using rails.vim on Hardy
Can someone give the exact steps to reproduce the bug? -- vim crashed using rails.vim on Hardy https://bugs.launchpad.net/bugs/219546 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156913] Re: Installing the Esperanto language pack does not offer Esperanto in choices
I just install Hardy and stumbled upon this bug. I just remember that a long time ago, I reported a similar bug (see bug #23435) in Hoary Hedgehog (yes, that's old!) and it was fixed back then. But somehow this bug now reappears. -- Installing the Esperanto language pack does not offer Esperanto in choices https://bugs.launchpad.net/bugs/156913 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 201324] Re: Can't select Esperanto as main language
*** This bug is a duplicate of bug 156913 *** https://bugs.launchpad.net/bugs/156913 ** This bug has been marked a duplicate of bug 156913 Installing the Esperanto language pack does not offer Esperanto in choices -- Can't select Esperanto as main language https://bugs.launchpad.net/bugs/201324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157265] Re: [gutsy] proprietary driver for NVIDIA accelerated graphics not working (regression from Feisty)
I upgraded to Ubuntu-8.04 (Hardy Heron) and everything now works fine. I'd suggest to close the issue. -- [gutsy] proprietary driver for NVIDIA accelerated graphics not working (regression from Feisty) https://bugs.launchpad.net/bugs/157265 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71322] Re: reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale
I just installed Ubuntu-8.04 (Hardy Heron), and aspell still crashes with: $ export LC_ALL=en_GB.UTF-8 ; echo -n | aspell list Segmentation fault -- reproducible seg fault in 'aspell' when using 'eo_XX.UTF-8' locale https://bugs.launchpad.net/bugs/71322 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 202435] [NEW] typos in man page of "xdvi"
Public bug reported: In man page of xdvi (man xdvi), I see the following typos: - unneccessary -> unnecessary (this is in description of -paper option) - used for the the magnifier -> the the is doubled (this is in description of the -rulecolor option) - encosed -> enclosed (this is in the description of the -sourceposition option) - occurences -> occurrences (this is the description of the -sourceposition option) - currenlty -> currently (this is in the description of the "Space key" keystroke) - numbers correspond the the actual page -> the the is doubled (this is in description of the g keystroke) - turing on -> turning on (this is near end of "STRING SEARCH" section) - segmeted -> segmented (this is in "PRINT DIALOG" section) - continously -> continuously (this is in description of "Ruler Mode") Also, in "man xdvi", I notice that the "-browser" option says "the following default value is used: netscape -raise [...]". Hmmm, netscape is obsolete now. Ubuntu uses Firefox. ** Affects: ubuntu Importance: Undecided Status: New -- typos in man page of "xdvi" https://bugs.launchpad.net/bugs/202435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs