** Description changed: - TEST CASE: - IMPORTANT NOTE: below will modify currently running locale/keyboard be prepared to restore it, e.g. by enabling keyboard indicator to change keyboard back to normal. + [ Description ] + + Memory corruption when rendering Myanmar text leeds to a crash + + [ Test case ] + + IMPORTANT NOTE: below will modify currently running locale/keyboard be + prepared to restore it, e.g. by enabling keyboard indicator to change + keyboard back to normal. 1. Install ubiquity on a desktop or boot from an ISO - $ sudo apt-get install ubiquity-frontend-gtk + $ sudo apt-get install ubiquity-frontend-gtk 2. If you run on a desktop start ubiquity with: - $ ubiquity --greeter + $ ubiquity --greeter 3. Scroll to the bottom of the language list, click on 5th or 4th from the bottom ACTUAL RESULT python3 segmentation fault: *** Error in `/usr/bin/python3': malloc(): memory corruption: 0x0000000003b33d80 *** Segmentation fault (core dumped) EXPECTED RESULT No crash + [ QA ] - == Original Report == + Check that the test case doesn't crash after applying the SRU + + [ Original Report ] I was testing a daily imagine of Ubuntu Gnome 14.04 (Live Image test), and was just checking out the languages on the initial boot up. When i was trying to click on the 4th language from the bottom ubiquitity crashed to give me this error. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ubiquity 2.17.10 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 Date: Mon Apr 7 00:06:38 2014 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InterpreterPath: /usr/bin/python3.4 LiveMediaBuild: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3d8a71dd71 <_int_malloc+689>: mov %r14,0x10(%r9) PC (0x7f3d8a71dd71) ok source "%r14" ok destination "0x10(%r9)" (0x180000001210) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: ubiquity StacktraceTop: _int_malloc (av=0x7f3d8aa5c760 <main_arena>, bytes=1824) at malloc.c:3489 __GI___libc_malloc (bytes=1824) at malloc.c:2891 ?? () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 gr_make_font_with_ops () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 gr_make_font_with_advance_fn () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 Title: ubiquity crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UpstartUbiquity: debconf: DbDriver "templatedb": /var/cache/debconf/templates.dat is locked by another process: Resource temporarily unavailable UserGroups:
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1303516 Title: ubiquity crashed with SIGSEGV in _int_malloc() Status in HarfBuzz: Confirmed Status in “graphite2” package in Ubuntu: Invalid Status in “harfbuzz” package in Ubuntu: Triaged Status in “graphite2” source package in Trusty: Invalid Status in “harfbuzz” source package in Trusty: In Progress Bug description: [ Description ] Memory corruption when rendering Myanmar text leeds to a crash [ Test case ] IMPORTANT NOTE: below will modify currently running locale/keyboard be prepared to restore it, e.g. by enabling keyboard indicator to change keyboard back to normal. 1. Install ubiquity on a desktop or boot from an ISO $ sudo apt-get install ubiquity-frontend-gtk 2. If you run on a desktop start ubiquity with: $ ubiquity --greeter 3. Scroll to the bottom of the language list, click on 5th or 4th from the bottom ACTUAL RESULT python3 segmentation fault: *** Error in `/usr/bin/python3': malloc(): memory corruption: 0x0000000003b33d80 *** Segmentation fault (core dumped) EXPECTED RESULT No crash [ QA ] Check that the test case doesn't crash after applying the SRU [ Original Report ] I was testing a daily imagine of Ubuntu Gnome 14.04 (Live Image test), and was just checking out the languages on the initial boot up. When i was trying to click on the 4th language from the bottom ubiquitity crashed to give me this error. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ubiquity 2.17.10 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 Date: Mon Apr 7 00:06:38 2014 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InterpreterPath: /usr/bin/python3.4 LiveMediaBuild: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3d8a71dd71 <_int_malloc+689>: mov %r14,0x10(%r9) PC (0x7f3d8a71dd71) ok source "%r14" ok destination "0x10(%r9)" (0x180000001210) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: ubiquity StacktraceTop: _int_malloc (av=0x7f3d8aa5c760 <main_arena>, bytes=1824) at malloc.c:3489 __GI___libc_malloc (bytes=1824) at malloc.c:2891 ?? () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 gr_make_font_with_ops () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 gr_make_font_with_advance_fn () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 Title: ubiquity crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UpstartUbiquity: debconf: DbDriver "templatedb": /var/cache/debconf/templates.dat is locked by another process: Resource temporarily unavailable UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/harfbuzz/+bug/1303516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
