For the record:
mosh | 1.1-1~lucid1 | lucid-backports/universe | source, amd64, i386,
ia64, powerpc, sparc
mosh | 1.1-1~oneiric1 | oneiric-backports/universe | source, amd64, i386,
powerpc
mosh | 1.1.3-1 | precise/universe | source, amd64, armel, armhf, i386,
powerpc
mosh | 1.2.2-1~ubuntu12.04.1 | precise-backports/universe | source,
amd64, armel, armhf, i386, powerpc
mosh | 1.2.2-1 | quantal/universe | source, amd64, armel, armhf, i386,
powerpc
mosh | 1.2.4a-1 | raring/universe | source, amd64, armhf, i386, powerpc
mosh | 1.2.4a-1 | saucy/universe | source, amd64, armhf, i386, powerpc
So there is a backported mosh for Precise (version
1.2.2-1~ubuntu12.04.1) that should not have this bug anymore.
--
You received this bug notification because you are a member of Ubuntu
Bug Control, which is subscribed to the bug report.
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
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-bugcontrol
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol
More help : https://help.launchpad.net/ListHelp
