[Bug 1676218] Re: [FFe] Sync Mosh 1.3.0 instead of release candidate
** Description changed: Zesty currently has Mosh 1.3.0~rc2-1 (release candidate 2), synced from Debian sid. Mosh upstream released the final version 1.3.0 yesterday, March 25. It is now in Debian sid and built successfully on all Debian architectures. Could you please sync the final 1.3.0 release from Debian? Debdiff attached. There are no changes in the upstream ChangeLog. There are almost no changes to the Mosh source code, other than (1) updating the version number to 1.3.0, and (2) working around a regression in OpenBSD's "pledge". This latter code is guarded by a HAVE_PLEDGE macro and does not affect builds on Linux. The other changes relate to improving the test suite for locale-related code when running in an sbuild chroot (e.g., on the Debian buildds). - We (upstream and Debian maintainer) would be grateful if the Ubuntu LTS - could include the final release of Mosh 1.3.0, instead of the release - candidate. It would reduce our support burden and increase uniformity - across platforms. Thank you for your consideration. + We (upstream and Debian maintainer) would be grateful if the Ubuntu + 17.04 release could include the final release of Mosh 1.3.0, instead of + the release candidate. It would reduce our support burden and increase + uniformity across platforms. Thank you for your consideration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676218 Title: [FFe] Sync Mosh 1.3.0 instead of release candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1676218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676218] [NEW] [FFe] Sync Mosh 1.3.0 instead of release candidate
Public bug reported: Zesty currently has Mosh 1.3.0~rc2-1 (release candidate 2), synced from Debian sid. Mosh upstream released the final version 1.3.0 yesterday, March 25. It is now in Debian sid and built successfully on all Debian architectures. Could you please sync the final 1.3.0 release from Debian? Debdiff attached. There are no changes in the upstream ChangeLog. There are almost no changes to the Mosh source code, other than (1) updating the version number to 1.3.0, and (2) working around a regression in OpenBSD's "pledge". This latter code is guarded by a HAVE_PLEDGE macro and does not affect builds on Linux. The other changes relate to improving the test suite for locale-related code when running in an sbuild chroot (e.g., on the Debian buildds). We (upstream and Debian maintainer) would be grateful if the Ubuntu LTS could include the final release of Mosh 1.3.0, instead of the release candidate. It would reduce our support burden and increase uniformity across platforms. Thank you for your consideration. ** Affects: mosh (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff from 1.3.0~rc2-1 to 1.3.0-1" https://bugs.launchpad.net/bugs/1676218/+attachment/4846408/+files/diff_from_1.3.0~rc2_to_1.3.0-1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676218 Title: [FFe] Sync Mosh 1.3.0 instead of release candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1676218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482501] Re: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server
The mosh-clients and mosh-servers in Ubuntu 12.04 and 14.04 are compatible (in both directions). However, you need a UTF-8 locale to run Mosh. Before Mosh version 1.2, this was the user's (or SSH's) responsibility. Debian, Ubuntu, and Mac OS X have shipped with SendEnv LANG LC_* in its ssh_config for some time, but not forever. Apparently you don't have this in your SSH config. Because not everybody was sending these environment variables, in 2012, Mosh version 1.2 started transferring these variables itself. We also improved the diagnostic message considerably. Your options to fix this problem are basically: (1) Add the SendEnv line (that you have already discovered) to /etc/ssh/ssh_config. I believe this would have been the default if you had installed Ubuntu 12.04 fresh. (2) Upgrade to Mosh 1.2.4 (released in 2013) by using the ubuntu- backports repository. (3) Upgrade to the most recent version of Mosh using the ppa:keithw/mosh repository. ** Changed in: mosh (Ubuntu) Status: New = Fix Released ** Changed in: mosh (Ubuntu) Assignee: (unassigned) = Keith Winstein (keithw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482501 Title: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1482501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337935] Re: mosh package does not support tab-completion of host aliases
** Changed in: mosh (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337935 Title: mosh package does not support tab-completion of host aliases To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1337935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337935] Re: mosh package does not support tab-completion of host aliases
Fixed in Mosh 1.2.5. ** Also affects: mosh Importance: Undecided Status: New ** Changed in: mosh Assignee: (unassigned) = Keith Winstein (keithw) ** Changed in: mosh Importance: Undecided = Low ** Changed in: mosh Status: New = Fix Released ** Changed in: mosh (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337935 Title: mosh package does not support tab-completion of host aliases To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1337935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
This does seem to be a systemd problem that is affecting a lot of different applications -- basically any application that would like a SIGTERM on reboot/shutdown so that it can save or clean up resources gracefully. See https://bugzilla.redhat.com/show_bug.cgi?id=1141137 (upstream systemd issue) https://bugzilla.redhat.com/show_bug.cgi?id=1170765 (systemd issue affecting bash's attempt to save history) https://github.com/cockpit-project/cockpit/issues/1155 (systemd issue affecting cockpit) http://lists.freedesktop.org/archives/systemd- devel/2014-October/024452.html (discussion) My suggestion would be that you open a new bug report against systemd in Ubuntu 15.04 and mention that it is affecting bash and mosh (and probably every other application that would like to clean up gracefully on shutdown or reboot). ** Bug watch added: Red Hat Bugzilla #1141137 https://bugzilla.redhat.com/show_bug.cgi?id=1141137 ** Bug watch added: Red Hat Bugzilla #1170765 https://bugzilla.redhat.com/show_bug.cgi?id=1170765 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448259] Re: Systemd has wrong kill mode on shutdown
This does seem to be a systemd bug that is affecting several applications -- basically any application that would like a SIGTERM on reboot/shutdown so that it can save or clean up resources gracefully. Please see https://bugzilla.redhat.com/show_bug.cgi?id=1141137 (upstream systemd bug) https://bugzilla.redhat.com/show_bug.cgi?id=1170765 (bug affects bash's attempt to save history) https://github.com/cockpit-project/cockpit/issues/1155 (bug affects cockpit) http://lists.freedesktop.org/archives/systemd- devel/2014-October/024452.html (discussion) ** Bug watch added: Red Hat Bugzilla #1141137 https://bugzilla.redhat.com/show_bug.cgi?id=1141137 ** Bug watch added: Red Hat Bugzilla #1170765 https://bugzilla.redhat.com/show_bug.cgi?id=1170765 ** Also affects: systemd via https://bugzilla.redhat.com/show_bug.cgi?id=1141137 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd has wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
Hello, I think this is working as intended. When you kill -9, that is sending the SIGKILL signal -- you are asking the program to shut down *uncleanly* and immediately. The mosh-client dies immediately, and it doesn't have a chance to let the server know that it won't be coming back. The server has no way to distinguish this from a case where the client simply lost its network connection (but might regain it later). Please use a nicer signal to kill the mosh-client. (E.g. the default for kill, or just exit from within the client.) Then it will have a chance to shut down the connection cleanly. (You might still have the problem if you exit the client while it doesn't have a network connection -- then it again doesn't have a chance to let the server know that it's quitting. But that is a different problem that is hard to escape given mosh's design of everlasting, roamable connections.) ** Changed in: mosh (Ubuntu) Assignee: (unassigned) = Keith Winstein (keithw) ** Also affects: mosh Importance: Undecided Status: New ** Changed in: mosh Assignee: (unassigned) = Keith Winstein (keithw) ** Changed in: mosh (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
Do you see different behavior on Ubuntu 14.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
Can you be a lot more explicit? To make sure I understand you correctly, you are saying that: (1) With a client running Ubuntu 15.04, shutting down the system does not cleanly close your Mosh connections (it leaves a mosh-server running), but rebooting the system *does* cleanly close your Mosh connections. (2) With a client running Ubuntu 14.10 but nothing else changed, BOTH shutting down AND rebooting the client cleanly close your Mosh connections. Is this correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
I'm trying to help you out here, but you are making things more confusing than necessary. If you can document clearly that Ubuntu 15.04 behaves differently from 14.10 in the shutdown sequence (e.g., perhaps Ubuntu 14.10's shutdown sequence sent a SIGTERM *before* cutting off the network, and Ubuntu 15.04 cuts off the network first), you might be able to get the systemd people interested again. But you have to document it very clearly and change only one thing at a time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337935] Re: mosh package does no register bash completion like ssh
The mosh package installs an `/etc/bash_completion.d/mosh` file, and supports tab-completion of hosts defined in ~/.ssh/config. We will support host aliases in the next release; please see https://github.com/keithw/mosh/pull/518 ** Changed in: mosh (Ubuntu) Status: New = Incomplete ** Changed in: mosh (Ubuntu) Assignee: (unassigned) = Keith Winstein (keithw) ** Changed in: mosh (Ubuntu) Status: Incomplete = In Progress ** Summary changed: - mosh package does no register bash completion like ssh + mosh package does not support tab-completion of host aliases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337935 Title: mosh package does not support tab-completion of host aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1337935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198808] [NEW] apt-get(8) man page doesn't mention apt-mark or history.log
Public bug reported: It would be nice if the apt-get(8) man page mentioned the apt-mark tool, e.g. in the SEE ALSO section. The man page could also mention that the APT database keeps track of manually installed packages. (It mentions automatically installed packages in the discussion of autoremove.) It would also be nice if it discussed the log in /var/log/apt/history.log, e.g. in the FILES section. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: apt 0.9.7.7ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Mon Jul 8 02:24:07 2013 InstallationDate: Installed on 2013-05-10 (58 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198808 Title: apt-get(8) man page doesn't mention apt-mark or history.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1198808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1185863] Re: mosh-client crashed with SIGABRT in __assert_fail_base()
Thanks for this detailed backtrace. This is upstream bug #168/#207, which can be triggered when the user resizes the window while disconnected. (https://github.com/keithw/mosh/issues/168 , https://github.com/keithw/mosh/issues/207) The fix was shipped in mosh 1.2. ** Changed in: mosh (Ubuntu) Status: New = Fix Released ** Changed in: mosh (Ubuntu) Assignee: (unassigned) = Keith Winstein (keithw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1185863 Title: mosh-client crashed with SIGABRT in __assert_fail_base() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1185863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1029030] Re: function keys are not working on byobu-tmux under mosh connection
We believe this issue was fixed in mosh 1.2 (https://github.com/keithw/mosh/issues/161), which will be included in the next Ubuntu release. It is also available in the PPA (ppa:keithw/mosh). ** Changed in: mosh (Ubuntu) Status: Confirmed = Fix Released ** Changed in: mosh (Ubuntu) Assignee: (unassigned) = Keith Winstein (keithw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1029030 Title: function keys are not working on byobu-tmux under mosh connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1029030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016297] [NEW] Sync mosh 1.2.2-1 (universe) from Debian unstable (main)
Public bug reported: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 affects ubuntu/mosh status new importance wishlist subscribe ubuntu-sponsors done Please sync mosh 1.2.2-1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: The Ubuntu delta contains ufw integration (LP#985981, debbugs #674127) that was accepted by Debian and upstream in version 1.2.1-1. The current quantal package (1.2.1-1ubuntu1) has two copies of the ufw integration. Changelog entries since current quantal version 1.2.1-1ubuntu1: mosh (1.2.2-1) unstable; urgency=low * Version 1.2.2 released. * Remove warning on out-of-order/duplicated datagrams * Add experimental prediction mode -- Keith Winstein kei...@mit.edu Tue, 12 Jun 2012 14:52:17 -0400 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJP46r6AAoJECC3KDr+JUxpNlIP/R/Qw6neDhS2H/OZsHsknch9 gFLIidTzZfXodtqWmyjeYra22pxni/M2UYteH53grHqSqWYpnJqvIDhHlyBhcF5y XoxixvvdJI66JAjjCNhP826KQdAIN06VgLIr13ZSQ4fYKQLe2GxWcpiVELlnQIUS 5YNK2JPwqaMPWIFPRkNYgjAz8oXW4O7EK7sZKzr6mHZDCnH+vE4Te14APQRiY5CY P/dNo2j8vswTOFo4bnf3hNufNYxizd+umPFh6jTgWx+T6Urczh3FEoXreSbhLBE6 FGfoaMGW8RlWXe/NDalH8Hskri+W89EA8LOYXQkL5m0qoJqBWYT4DkifFQwD+k4N qgs0azj/BsxuFzUhbqVjMtWdhwagx32MSpTr15E+j7qdm2KJPsLt9Z4qgjFujqBk kZLYPgRjIXUat564NJr7HnMeZCI6epatm6Ps7UFqri6Y1dQ9ch32sE4oPMfz6G7K BFpR8Bqk4+BwDTYMUDuoEUXjmOTxmBtdzQKLOKIGhpWfdAG3GThDzUt/KzLOXnY9 0MQ8sS4VW4VsbxKZRp1B7+Hy5L8YqQFJos31CNIyHnvxWReNSDuGo+cg8d+r6zyv 6oXgJlCv4uLtMJV/sfT5Xkaq6AnGlYJbGbpZEtI1qx+8Ki+GBfWIbpht7Cp4vOam CfwyIaL/dGxxCwLdSmmn =CT5N -END PGP SIGNATURE- ** Affects: mosh (Ubuntu) Importance: Wishlist Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016297 Title: Sync mosh 1.2.2-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1016297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004164] Re: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** Changed in: mosh (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004164 Title: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1004164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010047] Re: mosh uses a lot of CPU when not connected
Thanks for this report. This is fixed in version 1.2.1 (available in PPA, add-apt-repository ppa:keithw/mosh). ** Changed in: mosh (Ubuntu) Status: New = Fix Released ** Changed in: mosh (Ubuntu) Assignee: (unassigned) = Keith Winstein (keithw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010047 Title: mosh uses a lot of CPU when not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1010047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010047] Re: mosh uses a lot of CPU when not connected
(Fix Committed might be more accurate, but it looks like I cannot change this back.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010047 Title: mosh uses a lot of CPU when not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1010047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004164] Re: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
Thanks for this report. It is checking the type, and throwing an exception -- this is not a crash or undesired behavior. (The mosh-server is only supposed to spit out numeric port numbers, so running the client with something else is considered evil input.) We will make the error message clearer, but this situation generally indicates a programming error or attack. The intended way for end users to run mosh is with the mosh command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004164 Title: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1004164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004164] Re: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** Changed in: mosh Importance: Undecided = Low ** Changed in: mosh Status: New = Fix Committed ** Changed in: mosh Assignee: (unassigned) = Keith Winstein (keithw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004164 Title: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1004164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004164] Re: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** Changed in: mosh (Ubuntu) Status: New = Fix Committed ** Changed in: mosh (Ubuntu) Assignee: (unassigned) = Keith Winstein (keithw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004164 Title: mosh-client crashes with alphabetic port number crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1004164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936729] [NEW] libprotobuf-dev should include libprotobuf-lite.so symlink
Public bug reported: Later versions of libprotobuf-dev (10.10 onward) seem to include the libprotobuf-lite.so symlink to the actual libprotobuf-lite.so libraries (.5 or .7) provided by libprotobuf5/libprotobuf-lite7. But the version for Ubuntu 10.04 LTS (Lucid) is missing the libprotobuf- lite.so symlink, even though it installs a .pc so that pkg-config --libs protobuf-lite reports -lprotobuf-lite. This causes programs using libprotobuf-lite not to compile, even when they use the options supplied by pkg-config. libprotobuf-dev should either (a) include the symlink, or (b) if it's not appropriate to link against libprotobuf-lite5, remove the pkg-config entry. ** Affects: protobuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936729 Title: libprotobuf-dev should include libprotobuf-lite.so symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/936729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705291] [NEW] Misplaced Unicode combining characters
*** This bug is a duplicate of bug 299158 *** https://bugs.launchpad.net/bugs/299158 Public bug reported: Binary package hint: ttf-dejavu DejaVu Sans Mono Book produces bizarre behavior with some combining characters. See http://web.mit.edu/keithw/www/badcombine3.html In gedit or gnome-terminal with DejaVu Sans Mono, the first circumflex is correctly positioned over the second x in the row. But in the second line, the circumflex is improperly one character to the right of where it should be. In the third line, the second o should have a circumflex, a minus sign below, and a slash through it. The first two combining characters are rendered correctly, but as for the slash, instead of striking the second o it either gets its own space (in gedit) or strikes the next letter (in gnome-terminal). In the fourth line, the second - should have all three combining characters. Instead the three diacritics either each get their own space (in gedit) or are applied to later characters in the same line (in gnome-terminal). Similar bugs affect most monospace fonts (see, e.g., https://bugs.launchpad.net/ubuntu/+source/ttf-liberation/+bug/299158), with different wrinkles in each case. I also see buggy behavior with Andale Mono, Courier New provided by the ttf-mscorefonts-installer, package, etc., so there may be a more general bug with TrueType rendering. This is on Ubuntu 10.10, ttf-dejavu 2.31-1. ** Affects: ttf-dejavu (Ubuntu) Importance: Undecided Status: Confirmed ** This bug has been marked a duplicate of bug 299158 Liberation Mono, Droid Sans Mono: Combining diacritics out of place * You can subscribe to bug 299158 by following this link: https://bugs.launchpad.net/ubuntu/+source/ttf-liberation/+bug/299158/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705291 Title: Misplaced Unicode combining characters -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299158] Re: Liberation Mono, Droid Sans Mono: Combining diacritics out of place
This bug also affects Courier New and Andale Mono provided by the ttf- mscorefonts-installer package, and DejaVu Mono has other buggy behavior (see http://web.mit.edu/keithw/www/badcombine3.html), so there may be a more general problem with TrueType rendering of Unicode combining characters. ** Also affects: ttf-dejavu (Ubuntu) Importance: Undecided Status: New ** Also affects: msttcorefonts (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: Liberation Mono, Droid Sans Mono: Combining diacritics out of place -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
