desktop-packages team mailing list archive

[Sebastien Bacher <seb128@xxxxxxxxxx>]

Could you get a backtrace of the issue using gdb?

** No longer affects: unity

** Package changed: unity (Ubuntu) => motif (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1472826

Title:
  Motif library v4.0.4 causes segfault in legacy app

Status in motif package in Ubuntu:
  New

Bug description:
  Our group develops an X application that uses the Motif Library (package libxm4 v2.3.4-5). It appears that in the latest version of libXm.4.0.4 on Trusty (14.04), on certain types of X events, it causes a segfault. I've isolated this to a particular version of the library and OS rev. Our application works fine for OS older than 14.04, ie 12.04 etc. I also confirmed the version issue by copying libXm.4.0.3 from a 12.04 machine onto a 14.04 machine and it allows the program to work normally. I basically copied libXm.4.0.3 from a 12.04 machine to the 14.04 machine and created a symlink to it:
  ln -s /usr/lib/x86_64-linux-gnu/libXm.4.0.3  /usr/lib/x86_64-linux-gnu/libXm.4.0.4

  So, whatever has changed between 4.0.3 and 4.0.4 has broken some API
  calls. It's hard for us to debug this from the application side b/c it
  generates a segfault, which causes the application to crash.

  Example of what causes the crash. When our application generates a
  child window which has text field widgets like a text field or
  textarea, typing into the field causes this crash.

  Any ideas on why the new version would cause these crashes? Looking at the release notes (/usr/share/doc/libmotif-dev/RELNOTES.gz), I see there were a number of bug fixes. Is it possible one of these fixes caused another bug?
  Thanks in advance.

  Quang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/motif/+bug/1472826/+subscriptions