Download it now!
Bug 50676 - soffice.bin crashed after entering chars using ibus-chewing
Summary: soffice.bin crashed after entering chars using ibus-chewing
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: Other Linux (All)
: medium major
Assignee: Björn Michaelsen
URL:
Whiteboard: target:3.5.5
Keywords:
Depends on:
Blocks: mab3.5
  Show dependency treegraph
 
Reported: 2012-06-04 05:08 UTC by Björn Michaelsen
Modified: 2012-06-04 11:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Michaelsen 2012-06-04 05:08:40 UTC
Upstreamed from https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915173:
When using ibus-chewing to input some Chinese characters in bufferred area such as "一二三四五六七八九十一二三四五六七八九十" (one two three four five six seven eight nine ten one two three four five six seven eight nine ten in English), libreoffice writer crashed.

Not reproducible in Xubuntu:
lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.5.0-1ubuntu4
  Candidate: 1:3.5.0-1ubuntu4
  Version table:
 *** 1:3.5.0-1ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

ibus-chewing
ibus-chewing:
  Installed: 1.3.10+clean-1
  Candidate: 1.3.10+clean-1
  Version table:
 *** 1.3.10+clean-1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.4.4-0ubuntu2
ProcVersionSignature: User Name 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Thu Jan 12 14:58:04 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120111)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=7
ProcEnviron:
 LANGUAGE=zh_TW:
 PATH=(custom, no user)
 LANG=zh_TW.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2f5f5d3d99: testb $0x1,0x8(%r12,%r15,1)
 PC (0x7f2f5f5d3d99) ok
 source "$0x1" ok
 destination "0x8(%r12,%r15,1)" (0x7f2f0315c8c0) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
Title: soffice.bin crashed with SIGSEGV in malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Comment 1 Björn Michaelsen 2012-06-04 05:11:51 UTC
Fixed on master with f9a4af41ca574760dbd22c8207661fabb6823e3b and 7e3ebe35a6a1a69b3a36f7eb41e1ec5c5905f714.

@Coalan: Any objection for me to backport the fix to -3-5?
Comment 2 Björn Michaelsen 2012-06-04 05:38:45 UTC
got an ack by thorsten, backporting
Comment 3 Not Assigned 2012-06-04 09:50:52 UTC
Caolan McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-3-5":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=10a390d4676cb678c58b2d6f1db9db8a76041996&g=libreoffice-3-5

fdo#50676: Related: rhbz#799628 crash with chewing-IM with g3g


It will be available in LibreOffice 3.5.5.
Comment 4 Not Assigned 2012-06-04 09:51:16 UTC
Caolan McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-3-5":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=5ae8cb8fc0d7ae3c85ccf23ffb8e2a890728cb72&g=libreoffice-3-5

fdo#50676: silence SolarMutex not locked spew


It will be available in LibreOffice 3.5.5.
Comment 5 Björn Michaelsen 2012-06-04 11:22:18 UTC
resolving again after backport