Bug #1354961 “[SRU] Fix for upstream bug #1565 causes segfaults ...” : Bugs : ddd package : Ubuntu

Revision history for this message

themusicgod1 (themusicgod1) wrote on 2014-08-10:

#1

Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (106 bytes, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-10-08:

#2

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ddd (Ubuntu):
status:	New → Confirmed

Revision history for this message

Cees (cakoolen) wrote on 2014-11-13:

#3

Download full text (6.8 KiB)

I am affected to this issue as well. Running a debug version of DDD reveals just a little bit more. I'm under the impression that it is related to keypresses. In Ubuntu 12.04 this was not an issue at all. It looks like it is related to switching to motif in stead of lesstif.

I've built the source package to be able to see more symbols in the trace:
#0 0x00007f2268e127dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6
(gdb) bt
#0 0x00007f2268e127dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#1 0x00007f2268e130d1 in XtWindowOfObject () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#2 0x00007f2269665dd8 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4
#3 0x00007f2268e0c499 in XtDispatchEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#4 0x000000000041e69d in process_next_event () at ddd-3.3.12/./ddd/ddd.C:3247
#5 0x00000000004cd5dd in ddd_main_loop () at ddd/ddd-3.3.12/./ddd/mainloop.C:120
#6 0x000000000040dacf in main (argc=<optimized out>, argv=<optimized out>) at ddd/ddd-3.3.12/./ddd/ddd.C:3175

An inspection of the variables when calling motif reveals only a little:
(gdb) info locals
app_context = <optimized out>
event = {type = 2, xany = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915}, xkey = {type = 2,
    serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, root = 149, subwindow = 0, time = 10274151, x = -425, y = 352,
    x_root = 941, y_root = 376, state = 0, keycode = 64, same_screen = 1}, xbutton = {type = 2, serial = 66981, send_event = 0,
    display = 0x167e930, window = 75497915, root = 149, subwindow = 0, time = 10274151, x = -425, y = 352, x_root = 941, y_root = 376,
    state = 0, button = 64, same_screen = 1}, xmotion = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915,
    root = 149, subwindow = 0, time = 10274151, x = -425, y = 352, x_root = 941, y_root = 376, state = 0, is_hint = 64 '@',
    same_screen = 1}, xcrossing = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, root = 149,
    subwindow = 0, time = 10274151, x = -425, y = 352, x_root = 941, y_root = 376, mode = 0, detail = 64, same_screen = 1, focus = 1,
    state = 0}, xfocus = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, mode = 149, detail = 0},
  xexpose = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, x = 149, y = 0, width = 0, height = 0,
    count = 10274151}, xgraphicsexpose = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, drawable = 75497915, x = 149,
    y = 0, width = 0, height = 0, count = 10274151, major_code = 0, minor_code = -425}, xnoexpose = {type = 2, serial = 66981,
    send_event = 0, display = 0x167e930, drawable = 75497915, major_code = 149, minor_code = 0}, xvisibility = {type = 2, serial = 66981,
    send_event = 0, display = 0x167e930, window = 75497915, state = 149}, xcreatewindow = {type = 2, serial = 66981, send_event = 0,
    display = 0x167e930, parent = 75497915, window = 149, x = 0, y = 0, width = 10274151, height = 0, border_width = -425,
    override_redirec...

I am affected to this issue as well. Running a debug version of DDD reveals just a little bit more. I'm under the impression that it is related to keypresses. In Ubuntu 12.04 this was not an issue at all. It looks like it is related to switching to motif in stead of lesstif.

I've built the source package to be able to see more symbols in the trace:
#0  0x00007f2268e127dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6
(gdb) bt
#0  0x00007f2268e127dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#1  0x00007f2268e130d1 in XtWindowOfObject () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#2  0x00007f2269665dd8 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4
#3  0x00007f2268e0c499 in XtDispatchEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#4  0x000000000041e69d in process_next_event () at ddd-3.3.12/./ddd/ddd.C:3247
#5  0x00000000004cd5dd in ddd_main_loop () at ddd/ddd-3.3.12/./ddd/mainloop.C:120
#6  0x000000000040dacf in main (argc=<optimized out>, argv=<optimized out>) at ddd/ddd-3.3.12/./ddd/ddd.C:3175

An inspection of the variables when calling motif reveals only a little:
(gdb) info locals
app_context = <optimized out>
event = {type = 2, xany = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915}, xkey = {type = 2, 
    serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, root = 149, subwindow = 0, time = 10274151, x = -425, y = 352, 
    x_root = 941, y_root = 376, state = 0, keycode = 64, same_screen = 1}, xbutton = {type = 2, serial = 66981, send_event = 0, 
    display = 0x167e930, window = 75497915, root = 149, subwindow = 0, time = 10274151, x = -425, y = 352, x_root = 941, y_root = 376, 
    state = 0, button = 64, same_screen = 1}, xmotion = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, 
    root = 149, subwindow = 0, time = 10274151, x = -425, y = 352, x_root = 941, y_root = 376, state = 0, is_hint = 64 '@', 
    same_screen = 1}, xcrossing = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, root = 149, 
    subwindow = 0, time = 10274151, x = -425, y = 352, x_root = 941, y_root = 376, mode = 0, detail = 64, same_screen = 1, focus = 1, 
    state = 0}, xfocus = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, mode = 149, detail = 0}, 
  xexpose = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, x = 149, y = 0, width = 0, height = 0, 
    count = 10274151}, xgraphicsexpose = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, drawable = 75497915, x = 149, 
    y = 0, width = 0, height = 0, count = 10274151, major_code = 0, minor_code = -425}, xnoexpose = {type = 2, serial = 66981, 
    send_event = 0, display = 0x167e930, drawable = 75497915, major_code = 149, minor_code = 0}, xvisibility = {type = 2, serial = 66981, 
    send_event = 0, display = 0x167e930, window = 75497915, state = 149}, xcreatewindow = {type = 2, serial = 66981, send_event = 0, 
    display = 0x167e930, parent = 75497915, window = 149, x = 0, y = 0, width = 10274151, height = 0, border_width = -425, 
    override_redirect = 352}, xdestroywindow = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, event = 75497915, 
    window = 149}, xunmap = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, event = 75497915, window = 149, 
    from_configure = 0}, xmap = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, event = 75497915, window = 149, 
    override_redirect = 0}, xmaprequest = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, parent = 75497915, window = 149}, 
  xreparent = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, event = 75497915, window = 149, parent = 0, x = 10274151, 
    y = 0, override_redirect = -425}, xconfigure = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, event = 75497915, 
    window = 149, x = 0, y = 0, width = 10274151, height = 0, border_width = -425, above = 1614907704237, override_redirect = 0}, 
  xgravity = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, event = 75497915, window = 149, x = 0, y = 0}, 
  xresizerequest = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, width = 149, height = 0}, 
  xconfigurerequest = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, parent = 75497915, window = 149, x = 0, y = 0, 
    width = 10274151, height = 0, border_width = -425, above = 1614907704237, detail = 0, value_mask = 4294967297}, xcirculate = {type = 2, 
    serial = 66981, send_event = 0, display = 0x167e930, event = 75497915, window = 149, place = 0}, xcirculaterequest = {type = 2, 
    serial = 66981, send_event = 0, display = 0x167e930, parent = 75497915, window = 149, place = 0}, xproperty = {type = 2, 
    serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, atom = 149, time = 0, state = 10274151}, xselectionclear = {
    type = 2, serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, selection = 149, time = 0}, xselectionrequest = {
    type = 2, serial = 66981, send_event = 0, display = 0x167e930, owner = 75497915, requestor = 149, selection = 0, target = 10274151, 
    property = 1516123455063, time = 1614907704237}, xselection = {type = 2, serial = 66981, send_event = 0, display = 0x167e930, 
    requestor = 75497915, selection = 149, target = 0, property = 10274151, time = 1516123455063}, xcolormap = {type = 2, serial = 66981, 
    send_event = 0, display = 0x167e930, window = 75497915, colormap = 149, c_new = 0, state = 0}, xclient = {type = 2, serial = 66981, 
    send_event = 0, display = 0x167e930, window = 75497915, message_type = 149, format = 0, data = {
      b = "gŜ\000\000\000\000\000W\376\377\377`\001\000\000\255\003\000", s = {-15001, 156, 0, 0, -425, -1, 352, 0, 941, 0}, l = {
        10274151, 1516123455063, 1614907704237, 274877906944, 4294967297}}}, xmapping = {type = 2, serial = 66981, send_event = 0, 
    display = 0x167e930, window = 75497915, request = 149, first_keycode = 0, count = 0}, xerror = {type = 2, display = 0x105a5, 
    resourceid = 0, serial = 23587120, error_code = 187 '\273', request_code = 1 '\001', minor_code = 128 '\200'}, xkeymap = {type = 2, 
    serial = 66981, send_event = 0, display = 0x167e930, window = 75497915, 
    key_vector = "\225", '\000' <repeats 15 times>, "gŜ\000\000\000\000\000W\376\377\377`\001\000"}, xgeneric = {type = 2, serial = 66981, 
    send_event = 0, display = 0x167e930, extension = 75497915, evtype = 0}, xcookie = {type = 2, serial = 66981, send_event = 0, 
    display = 0x167e930, extension = 75497915, evtype = 0, cookie = 149, data = 0x0}, pad = {2, 66981, 0, 23587120, 75497915, 149, 0, 
    10274151, 1516123455063, 1614907704237, 274877906944, 4294967297, 0, 103, 0, 26242144, 26237840, 0, 26239280, 0, 97, 26343152, 
    26280944, 0}}

Hope someone can help!

Alberto Salvia Novella (es20490446e) on 2014-11-29

Changed in ddd (Ubuntu):
importance:	Undecided → High

Revision history for this message

themusicgod1 (themusicgod1) wrote on 2015-02-16:

#4

another layer of stack trace mystery revealed: Xm.c:622

0x00007ffff72427d9 in _XtWindowedAncestor (object=0x3364613466377830) at ../../src/Intrinsic.c:787
(gdb) bt
#0 0x00007ffff72427d9 in _XtWindowedAncestor (object=0x3364613466377830) at ../../src/Intrinsic.c:787
#1 0x00007ffff72430d1 in XtWindowOfObject (object=<optimized out>) at ../../src/Intrinsic.c:700
#2 0x00007ffff7aa3248 in _XmEventDispatcher (event=0x7fffffffe2e0) at Xm.c:622
#3 0x00007ffff723c499 in XtDispatchEvent (event=0x7fffffffe2e0) at ../../src/Event.c:1423
#4 0x00000000004204fd in process_next_event () at ddd.C:3247
#5 0x00000000004e2dcd in ddd_main_loop () at mainloop.C:120
#6 0x000000000040db4f in main (argc=<optimized out>, argv=<optimized out>) at ddd.C:3175

Related: calling XtIsWidget(object) from within ddd, at the point of the crash.... causes a crash in the *current* running instance of ddd(ie not the one being debugged).

Sure seems like the crash is actually happening at _XtCheckSubclassFlag() from XtIsWidget(object) where it's checking object->core.widget_class->core_class, which is not defined.

(gdb) print object->core
$2 = {self = 0x0, widget_class = 0x37, parent = 0x5900d0 <HandleTipEvent(Widget, XtPointer, XEvent*, Boolean*)>, xrm_name = 0, being_destroyed = 0 '\000', destroy_callbacks = 0xf259, constraints = 0x51, x = 6, y = 0, width = 36, height = 0, border_width = 23328, managed = -13 '\363', sensitive = 0 '\000', ancestor_sensitive = 0 '\000', event_table = 0x656372756f73, tm = {translations = 0x3766666666373030, proc_table = 0x6920396437323432, current_state = 0x6e695774585f206e, lastEventTime = 7164735956647898980}, accelerators = 0x6f2820726f747365, border_pixel = 8660489653526555234, border_pixmap = 81, popup_list = 0x240000000c, num_popups = 15948656, name = 0x6d6f635f63657865 <error: Cannot access memory at address 0x6d6f635f63657865>, screen = 0x63006300646e616d, colormap = 1876372909337502510, window = 8372021752999980826, depth = 1970103656, background_pixel = 3414964798904951919, background_pixmap = 3328491577862678892, visible = 81 'Q', mapped_when_managed = 0 '\000'}

another layer of stack trace mystery revealed:  Xm.c:622

0x00007ffff72427d9 in _XtWindowedAncestor (object=0x3364613466377830) at ../../src/Intrinsic.c:787
(gdb) bt
#0  0x00007ffff72427d9 in _XtWindowedAncestor (object=0x3364613466377830) at ../../src/Intrinsic.c:787
#1  0x00007ffff72430d1 in XtWindowOfObject (object=<optimized out>) at ../../src/Intrinsic.c:700
#2  0x00007ffff7aa3248 in _XmEventDispatcher (event=0x7fffffffe2e0) at Xm.c:622
#3  0x00007ffff723c499 in XtDispatchEvent (event=0x7fffffffe2e0) at ../../src/Event.c:1423
#4  0x00000000004204fd in process_next_event () at ddd.C:3247
#5  0x00000000004e2dcd in ddd_main_loop () at mainloop.C:120
#6  0x000000000040db4f in main (argc=<optimized out>, argv=<optimized out>) at ddd.C:3175

Related: calling XtIsWidget(object) from within ddd, at the point of the crash.... causes a crash in the *current* running instance of ddd(ie not the one being debugged).

Sure seems like the crash is actually happening at _XtCheckSubclassFlag() from XtIsWidget(object) where it's checking object->core.widget_class->core_class, which is not defined.
 
(gdb) print object->core
$2 = {self = 0x0, widget_class = 0x37, parent = 0x5900d0 <HandleTipEvent(Widget, XtPointer, XEvent*, Boolean*)>, xrm_name = 0, being_destroyed = 0 '\000', destroy_callbacks = 0xf259, constraints = 0x51, x = 6, y = 0, width = 36, height = 0, border_width = 23328, managed = -13 '\363', sensitive = 0 '\000', ancestor_sensitive = 0 '\000', event_table = 0x656372756f73, tm = {translations = 0x3766666666373030, proc_table = 0x6920396437323432, current_state = 0x6e695774585f206e, lastEventTime = 7164735956647898980}, accelerators = 0x6f2820726f747365, border_pixel = 8660489653526555234, border_pixmap = 81, popup_list = 0x240000000c, num_popups = 15948656, name = 0x6d6f635f63657865 <error: Cannot access memory at address 0x6d6f635f63657865>, screen = 0x63006300646e616d, colormap = 1876372909337502510, window = 8372021752999980826, depth = 1970103656, background_pixel = 3414964798904951919, background_pixmap = 3328491577862678892, visible = 81 'Q', mapped_when_managed = 0 '\000'}

Revision history for this message

themusicgod1 (themusicgod1) wrote on 2015-02-22:

#5

Download full text (7.8 KiB)

I've seen this happen when you *paste* something copied from within ddd into another window of another application (ie chromium), and "Ctrl" seems to be capable of triggering it.

an example event which kills XtDispatchEvent() has type 2 just as the example given above does.
(gdb) print *event
$3 = {type = 2, xany = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078}, xkey = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, state = 0, keycode = 37, same_screen = 1}, xbutton = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, state = 0, button = 37, same_screen = 1}, xmotion = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, state = 0, is_hint = 37 '%', same_screen = 1}, xcrossing = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, mode = 0, detail = 37, same_screen = 1, focus = 1, state = 256}, xfocus = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, mode = 205, detail = 0}, xexpose = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, x = 205, y = 0, width = 0, height = 0, count = 909015716}, xgraphicsexpose = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, drawable = 62915078, x = 205, y = 0, width = 0, height = 0, count = 909015716, major_code = 0, minor_code = 259}, xnoexpose = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, drawable = 62915078, major_code = 205, minor_code = 0}, xvisibility = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, state = 205}, xcreatewindow = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, parent = 62915078, window = 205, x = 0, y = 0, width = 909015716, height = 0, border_width = 259, override_redirect = 451}, xdestroywindow = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205}, xunmap = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, from_configure = 0}, xmap = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, override_redirect = 0}, xmaprequest = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, parent = 62915078, window = 205}, xreparent = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, parent = 0, x = 909015716, y = 0, override_redirect = 259}, xconfigure = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, x = 0, y = 0, width = 909015716, height = 0, border_width = 259, above = 3770981287427, override_redirect = 0}, xgravity = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window ...

I've seen this happen when you *paste* something copied from within ddd into another window of another application (ie chromium), and "Ctrl" seems to be capable of triggering it.

an example event which kills XtDispatchEvent() has type 2 just as the example given above does.
(gdb) print *event
$3 = {type = 2, xany = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078}, xkey = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, state = 0, keycode = 37, same_screen = 1}, xbutton = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, state = 0, button = 37, same_screen = 1}, xmotion = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, state = 0, is_hint = 37 '%', same_screen = 1}, xcrossing = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, root = 205, subwindow = 0, time = 909015716, x = 259, y = 451, x_root = 1539, y_root = 878, mode = 0, detail = 37, same_screen = 1, focus = 1, state = 256}, xfocus = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, mode = 205, detail = 0}, xexpose = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, x = 205, y = 0, width = 0, height = 0, count = 909015716}, xgraphicsexpose = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, drawable = 62915078, x = 205, y = 0, width = 0, height = 0, count = 909015716, major_code = 0, minor_code = 259}, xnoexpose = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, drawable = 62915078, major_code = 205, minor_code = 0}, xvisibility = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, state = 205}, xcreatewindow = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, parent = 62915078, window = 205, x = 0, y = 0, width = 909015716, height = 0, border_width = 259, override_redirect = 451}, xdestroywindow = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205}, xunmap = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, from_configure = 0}, xmap = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, override_redirect = 0}, xmaprequest = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, parent = 62915078, window = 205}, xreparent = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, parent = 0, x = 909015716, y = 0, override_redirect = 259}, xconfigure = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, x = 0, y = 0, width = 909015716, height = 0, border_width = 259, above = 3770981287427, override_redirect = 0}, xgravity = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, x = 0, y = 0}, xresizerequest = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, width = 205, height = 0}, xconfigurerequest = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, parent = 62915078, window = 205, x = 0, y = 0, width = 909015716, height = 0, border_width = 259, above = 3770981287427, detail = 0, value_mask = 4294967297}, xcirculate = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, event = 62915078, window = 205, place = 0}, xcirculaterequest = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, parent = 62915078, window = 205, place = 0}, xproperty = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, atom = 205, time = 0, state = 909015716}, xselectionclear = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, selection = 205, time = 0}, xselectionrequest = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, owner = 62915078, requestor = 205, selection = 0, target = 909015716, property = 1937030250755, time = 3770981287427}, xselection = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, requestor = 62915078, selection = 205, target = 0, property = 909015716, time = 1937030250755}, xcolormap = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, colormap = 205, new = 0, state = 0}, xclient = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, message_type = 205, format = 0, data = {b = "\244z.6\000\000\000\000\003\001\000\000\303\001\000\000\003\006\000", s = {31396, 13870, 0, 0, 259, 0, 451, 0, 1539, 0}, l = {909015716, 1937030250755, 3770981287427, 158913789952, 4294967297}}}, xmapping = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, request = 205, first_keycode = 0, count = 0}, xerror = {type = 2, display = 0xcec4, resourceid = 0, serial = 9429264, error_code = 6 '\006', request_code = 2 '\002', minor_code = 192 '\300'}, xkeymap = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, window = 62915078, key_vector = "\315", '\000' <repeats 15 times>, "\244z.6\000\000\000\000\003\001\000\000\303\001\000"}, xgeneric = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, extension = 62915078, evtype = 0}, xcookie = {type = 2, serial = 52932, send_event = 0, display = 0x8fe110, extension = 62915078, evtype = 0, cookie = 205, data = 0x0}, pad = {2, 52932, 0, 9429264, 62915078, 205, 0, 909015716, 1937030250755, 3770981287427, 158913789952, 4294967297, 256, 12182128, 6214617, 0, 12657184, 96, 64, 12658544, 6231967, 0, 12330256, 12140944}}
(gdb)

grabw_top->w->core.depth is 0 in *dispatch(), but i've seen it 1 also

an attempt is made to create a new XtWindow based on

(gdb) print grabw_top
$4 = (GrabData *) 0xbc5a90
(gdb) graph display *grabw_top
(gdb) print grabw_top->w
$5 = (Widget) 0xca9760
(gdb) print *(grabw_top->w)
$6 = {core = {self = 0xcb5920, widget_class = 0x7ffff6275938 <main_arena+472>, parent = 0x20740000001a0064, xrm_name = 1965059956, being_destroyed = 115 's', destroy_callbacks = 0x616e206570797420, constraints = 0x6e61000000000000, x = 18064, y = 169, width = 0, height = 0, border_width = 31, managed = 0 '\000', sensitive = 0 '\000', ancestor_sensitive = 2 '\002', event_table = 0x62640000001a0064, tm = {translations = 0x222029, proc_table = 0xca9860, current_state = 0x0, lastEventTime = 11095824}, accelerators = 0x3600020000001f, border_pixel = 1704036, border_pixmap = 0, popup_list = 0x0, num_popups = 0, name = 0x0, screen = 0x30, colormap = 0, window = 13277200, depth = 0, background_pixel = 5831856, background_pixmap = 0, visible = -63 '\301', mapped_when_managed = 0 '\000'}}

and store it in xany.window, but before it can get there, an attempt to create a _XtWindowedAncestor fails:

and the name is the same as the parent, or 0x0

(gdb) print *obj
$1 = {core = {self = 0xcb5920, widget_class = 0x7ffff6275938 <main_arena+472>, parent = 0x20740000001a0064, xrm_name = 1965059956, being_destroyed = 115 's', destroy_callbacks = 0x616e206570797420, constraints = 0x6e61000000000000, x = 18064, y = 169, width = 0, height = 0, border_width = 31, managed = 0 '\000', sensitive = 0 '\000', ancestor_sensitive = 2 '\002', event_table = 0x62640000001a0064, tm = {translations = 0x222029, proc_table = 0xca9860, current_state = 0x0, lastEventTime = 11095824}, accelerators = 0x3600020000001f, border_pixel = 1704036, border_pixmap = 0, popup_list = 0x0, num_popups = 0, name = 0x0, screen = 0x30, colormap = 0, window = 13277200, depth = 0, background_pixel = 5831856, background_pixmap = 0, visible = -63 '\301', mapped_when_managed = 0 '\000'}}

either way: grabw_top is an internal variable to motif, ddd doesn't seem to touch it much except through motif

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-16:

#6

> I've seen this happen when you *paste* something copied from within ddd into
> another window of another application (ie chromium), and "Ctrl" seems to be
> capable of triggering it.

I am able to reproduce this crash by doing the following:
start ddd from within gdb: 'gdb ddd'
Open Program (a simple C program, compiled with debugging info '-g')
create a breakpoint at the start of the program
click Run
click Next several times
select some text from the Source Window
press Ctrl+Ins to copy
paste into another application
repeat last three steps until segfault occurs

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-03-16:

#7

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in motif (Ubuntu):
status:	New → Confirmed

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-16:

#8

Please try the version of motif in my PPA:
https://launchpad.net/~ginggs/+archive/ubuntu/testing
I have reverted the updated fix for upstream issue #1565 introduced in 2.3.4-5 in Trusty.

More information about the #1565 fix in LP: #1255473.

Revision history for this message

Cees (cakoolen) wrote on 2015-03-17: Re: [Bug 1354961] Re: segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6

#9

Can you build that motif version for Trusty as well? I'm fixed at LTS
releases.

On Mon, Mar 16, 2015 at 8:36 PM, Graham Inggs <email address hidden> wrote:

> Please try the version of motif in my PPA:
> https://launchpad.net/~ginggs/+archive/ubuntu/testing
> I have reverted the updated fix for upstream issue #1565 introduced in
> 2.3.4-5 in Trusty.
>
> More information about the #1565 fix in LP: #1255473.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1354961
>
> Title:
> segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>
> Status in ddd package in Ubuntu:
> Confirmed
> Status in motif package in Ubuntu:
> Confirmed
>
> Bug description:
> Trying to step/next through code in a ddd window, ddd segfaults with
> stack trace:
>
> #0 0x00007ffff725a7dd in _XtWindowedAncestor () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
> #1 0x00007ffff725b0d1 in XtWindowOfObject () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
> #2 0x00007ffff7aafdd8 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4
> #3 0x00007ffff7254499 in XtDispatchEvent () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
> #4 0x000000000041e63f in ?? ()
> #5 0x00000000004cd6dd in ?? ()
> #6 0x000000000040da6f in ?? ()
> #7 0x00007ffff5eeeec5 in __libc_start_main (main=0x40da50, argc=1,
> argv=0x7fffffffe5c8, init=<optimized out>, fini=<optimized out>,
> rtld_fini=<optimized out>, stack_end=0x7fffffffe5b8) at libc-start.c:287
> #8 0x0000000000413d95 in ?? ()
>
> It's segfaulted twice in 15 minutes so it can't be that unlikely.
>
> (Disclaimer: I do have an outdated acer BIOS, if that's an issue
> here)
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.10
> Package: ddd 1:3.3.12-5
> ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
> Uname: Linux 3.16.0-6-generic x86_64
> ApportVersion: 2.14.5-0ubuntu4
> Architecture: amd64
> CurrentDesktop: GNOME
> Date: Sun Aug 10 19:13:34 2014
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2014-07-09 (32 days ago)
> InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64
> (20140708)
> SourcePackage: ddd
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ddd/+bug/1354961/+subscriptions
>

Can you build that motif version for Trusty as well? I'm fixed at LTS
releases.

On Mon, Mar 16, 2015 at 8:36 PM, Graham Inggs <graham@nerve.org.za> wrote:

> Please try the version of motif in my PPA:
> https://launchpad.net/~ginggs/+archive/ubuntu/testing
> I have reverted the updated fix for upstream issue #1565 introduced in
> 2.3.4-5 in Trusty.
>
> More information about the #1565 fix in LP: #1255473.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1354961
>
> Title:
>   segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from
>   /usr/lib/x86_64-linux-gnu/libXt.so.6
>
> Status in ddd package in Ubuntu:
>   Confirmed
> Status in motif package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Trying to step/next through code in a ddd window, ddd segfaults with
>   stack trace:
>
>   #0  0x00007ffff725a7dd in _XtWindowedAncestor () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>   #1  0x00007ffff725b0d1 in XtWindowOfObject () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>   #2  0x00007ffff7aafdd8 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4
>   #3  0x00007ffff7254499 in XtDispatchEvent () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>   #4  0x000000000041e63f in ?? ()
>   #5  0x00000000004cd6dd in ?? ()
>   #6  0x000000000040da6f in ?? ()
>   #7  0x00007ffff5eeeec5 in __libc_start_main (main=0x40da50, argc=1,
> argv=0x7fffffffe5c8, init=<optimized out>, fini=<optimized out>,
> rtld_fini=<optimized out>, stack_end=0x7fffffffe5b8) at libc-start.c:287
>   #8  0x0000000000413d95 in ?? ()
>
>   It's segfaulted twice in 15 minutes so it can't be that unlikely.
>
>   (Disclaimer: I do  have an outdated acer BIOS, if that's an issue
>   here)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.10
>   Package: ddd 1:3.3.12-5
>   ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
>   Uname: Linux 3.16.0-6-generic x86_64
>   ApportVersion: 2.14.5-0ubuntu4
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Sun Aug 10 19:13:34 2014
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2014-07-09 (32 days ago)
>   InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64
> (20140708)
>   SourcePackage: ddd
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ddd/+bug/1354961/+subscriptions
>

Revision history for this message

Cees (cakoolen) wrote on 2015-03-17: Re: segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6

#10

Thanks for the patch!

Can you build that motif version for Trusty as well? I'm fixed at LTS releases. And I would like to verify if that would be a solution to our case.

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-17:

#11

@cakoolen:
motif - 2.3.4-8~ppa3~ubuntu14.04.1~ppa2 for Trusty is now in that PPA

Revision history for this message

themusicgod1 (themusicgod1) wrote on 2015-03-17:

#12

Initial testing so far so good.

Alberto Salvia Novella (es20490446e) on 2015-03-17

Changed in motif (Ubuntu):
importance:	Undecided → High

Revision history for this message

Cees (cakoolen) wrote on 2015-03-18:

#13

No segfault here yet. Looks promising. I'm gonna ask some colleagues to test it as well.

Revision history for this message

themusicgod1 (themusicgod1) wrote on 2015-03-23:

#14

Looks like the patch works to me, ddd sure does seem a little more stable now.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-03-23:

#15

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xpdf (Ubuntu):
status:	New → Confirmed

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-23:

#16

xpdf is also affected, and is easier to crash, see LP: #1372649

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-23:

#17

@cakoolen and themusicgod1:
Thanks for your feedback. Can you confirm whether you are now affected by LP: #1255473 ?

Revision history for this message

Cees (cakoolen) wrote on 2015-03-23:

#18

While using DDD, I can open the menu with <alt>-f. I can use the arrow keys <left> and <right> to switch menu's from [file] to [edit] to [view] and back. I cannot use the arrow keys <up> and <down> to select a menu item or use <enter> or an other key to select the highlighted menu entry.

Using a system without the reverted libmotif, the <up> and <down> keys work find as is the <enter> to select the highlighted menu item.

To me it looks like now I'm affected by LP: #1255473 .

Alberto Salvia Novella (es20490446e) on 2015-03-23

Changed in xpdf (Ubuntu):
importance:	Undecided → High

Revision history for this message

themusicgod1 (themusicgod1) wrote on 2015-03-24:

#19

I can't use up/down either (though I didn't realize you could do that, guess it makes sense)

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-24:

#20

screenshot of bug #1565 and expected behaviour Edit (18.2 KiB, image/png)

I have another version of Motif in a different PPA for testing:
https://launchpad.net/~ginggs/+archive/ubuntu/motif1565

This version completely reverts upstream's fix for #1565 and should behave as in Motif 2.3.3.
Bugs LP: #1354961 and LP: #1255473 should be fixed and upstream bug #1565 should be present:
"The active window changes to inactive when the drop down list is clicked."

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-24:

#21

Interesting bit of code in xpdf/XPDFViewer.cc (around lines 1058 and 2113):

  // this is magic (taken from DDD) - weird things happen if this
  // call isn't made (this is done in two different places, in hopes
  // of squashing this stupid bug)
  XtUngrabButton(core->getDrawAreaWidget(), AnyButton, AnyModifier);

Revision history for this message

Cees (cakoolen) wrote on 2015-03-24: Re: [Bug 1354961] Re: segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6

#22

What do you want me to test? If I have the same results as in bug #1565? Or
if the segfaults are still there?

On Tue, Mar 24, 2015 at 2:40 PM, Graham Inggs <email address hidden> wrote:

> Interesting bit of code in xpdf/XPDFViewer.cc (around lines 1058 and
> 2113):
>
> // this is magic (taken from DDD) - weird things happen if this
> // call isn't made (this is done in two different places, in hopes
> // of squashing this stupid bug)
> XtUngrabButton(core->getDrawAreaWidget(), AnyButton, AnyModifier);
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1354961
>
> Title:
> segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>
> Status in ddd package in Ubuntu:
> Confirmed
> Status in motif package in Ubuntu:
> Confirmed
> Status in xpdf package in Ubuntu:
> Confirmed
>
> Bug description:
> Trying to step/next through code in a ddd window, ddd segfaults with
> stack trace:
>
> #0 0x00007ffff725a7dd in _XtWindowedAncestor () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
> #1 0x00007ffff725b0d1 in XtWindowOfObject () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
> #2 0x00007ffff7aafdd8 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4
> #3 0x00007ffff7254499 in XtDispatchEvent () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
> #4 0x000000000041e63f in ?? ()
> #5 0x00000000004cd6dd in ?? ()
> #6 0x000000000040da6f in ?? ()
> #7 0x00007ffff5eeeec5 in __libc_start_main (main=0x40da50, argc=1,
> argv=0x7fffffffe5c8, init=<optimized out>, fini=<optimized out>,
> rtld_fini=<optimized out>, stack_end=0x7fffffffe5b8) at libc-start.c:287
> #8 0x0000000000413d95 in ?? ()
>
> It's segfaulted twice in 15 minutes so it can't be that unlikely.
>
> (Disclaimer: I do have an outdated acer BIOS, if that's an issue
> here)
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.10
> Package: ddd 1:3.3.12-5
> ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
> Uname: Linux 3.16.0-6-generic x86_64
> ApportVersion: 2.14.5-0ubuntu4
> Architecture: amd64
> CurrentDesktop: GNOME
> Date: Sun Aug 10 19:13:34 2014
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2014-07-09 (32 days ago)
> InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64
> (20140708)
> SourcePackage: ddd
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ddd/+bug/1354961/+subscriptions
>

What do you want me to test? If I have the same results as in bug #1565? Or
if the segfaults are still there?

On Tue, Mar 24, 2015 at 2:40 PM, Graham Inggs <graham@nerve.org.za> wrote:

> Interesting bit of code in xpdf/XPDFViewer.cc (around lines 1058 and
> 2113):
>
>   // this is magic (taken from DDD) - weird things happen if this
>   // call isn't made (this is done in two different places, in hopes
>   // of squashing this stupid bug)
>   XtUngrabButton(core->getDrawAreaWidget(), AnyButton, AnyModifier);
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1354961
>
> Title:
>   segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from
>   /usr/lib/x86_64-linux-gnu/libXt.so.6
>
> Status in ddd package in Ubuntu:
>   Confirmed
> Status in motif package in Ubuntu:
>   Confirmed
> Status in xpdf package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Trying to step/next through code in a ddd window, ddd segfaults with
>   stack trace:
>
>   #0  0x00007ffff725a7dd in _XtWindowedAncestor () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>   #1  0x00007ffff725b0d1 in XtWindowOfObject () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>   #2  0x00007ffff7aafdd8 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4
>   #3  0x00007ffff7254499 in XtDispatchEvent () from
> /usr/lib/x86_64-linux-gnu/libXt.so.6
>   #4  0x000000000041e63f in ?? ()
>   #5  0x00000000004cd6dd in ?? ()
>   #6  0x000000000040da6f in ?? ()
>   #7  0x00007ffff5eeeec5 in __libc_start_main (main=0x40da50, argc=1,
> argv=0x7fffffffe5c8, init=<optimized out>, fini=<optimized out>,
> rtld_fini=<optimized out>, stack_end=0x7fffffffe5b8) at libc-start.c:287
>   #8  0x0000000000413d95 in ?? ()
>
>   It's segfaulted twice in 15 minutes so it can't be that unlikely.
>
>   (Disclaimer: I do  have an outdated acer BIOS, if that's an issue
>   here)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.10
>   Package: ddd 1:3.3.12-5
>   ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
>   Uname: Linux 3.16.0-6-generic x86_64
>   ApportVersion: 2.14.5-0ubuntu4
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Sun Aug 10 19:13:34 2014
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2014-07-09 (32 days ago)
>   InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64
> (20140708)
>   SourcePackage: ddd
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ddd/+bug/1354961/+subscriptions
>

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-03-24: Re: segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from /usr/lib/x86_64-linux-gnu/libXt.so.6

#23

@cakoolen: Sorry for not making that clear. I'd like you to check whether LP: #1354961 and LP: #1255473 are both fixed, i.e. you don't get a segfault and that keyboard navigation of menus still works correctly.

In my opinion, upstream bug #1565 is purely cosmetic, so I am considering reverting the fix for it if it means LP: #1354961 and LP: #1255473 are both fixed.

Revision history for this message

Cees (cakoolen) wrote on 2015-03-24:

#24

Installed the motif version from https://launchpad.net/~ginggs/+archive/ubuntu/motif1565 on my machine.

I didn't notice any stability issues (no segfaults up to now). Keyboard navigation of menus work fine now. I did not notice the upstream bug #1565. Tested it with the large drop-down box under the menu panel. When clicking it to drop down, the active window remains the same and when selecting an itom from the drop-down box, the main window remains active as well.

Bug Watch Updater (bug-watch-updater) on 2015-04-06

Changed in motif (Debian):
status:	Unknown → New

Bug Watch Updater (bug-watch-updater) on 2015-04-13

Changed in motif (Debian):
status:	New → Fix Committed

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-04-14:

#25

This is being fixed in motif 2.3.4-6.1 for Jessie.
I'm going to upload the same fix for Vivid (as motif 2.3.4-7ubuntu1) and then backport to Utopic and Trusty.
After Jessie is released, the fix will be included in motif 2.3.4-8 and uploaded to unstable.

Graham Inggs (ginggs) on 2015-04-15

Changed in motif (Ubuntu):
status:	Confirmed → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-04-15:

#26

This bug was fixed in the package motif - 2.3.4-7ubuntu1

---------------
motif (2.3.4-7ubuntu1) vivid; urgency=medium

* Disable buggy fix for upstream bug #1565 causing
ddd and xpdf to be unusable (LP: #1354961).
-- Graham Inggs <email address hidden> Tue, 14 Apr 2015 17:26:18 +0200

Changed in motif (Ubuntu):
status:	Fix Committed → Fix Released

Bug Watch Updater (bug-watch-updater) on 2015-04-15

Changed in motif (Debian):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-09-24:

#27

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ddd (Ubuntu Trusty):
status:	New → Confirmed
Changed in ddd (Ubuntu Utopic):
status:	New → Confirmed
Changed in motif (Ubuntu Trusty):
status:	New → Confirmed
Changed in motif (Ubuntu Utopic):
status:	New → Confirmed
Changed in xpdf (Ubuntu Trusty):
status:	New → Confirmed
Changed in xpdf (Ubuntu Utopic):
status:	New → Confirmed

Graham Inggs (ginggs) on 2015-09-24

Changed in ddd (Ubuntu):
status:	Confirmed → Invalid
Changed in ddd (Ubuntu Trusty):
status:	Confirmed → Invalid
Changed in ddd (Ubuntu Utopic):
status:	Confirmed → Invalid
Changed in xpdf (Ubuntu):
status:	Confirmed → Invalid
Changed in xpdf (Ubuntu Trusty):
status:	Confirmed → Invalid
Changed in xpdf (Ubuntu Utopic):
status:	Confirmed → Invalid
Changed in motif (Ubuntu Utopic):
status:	Confirmed → Invalid
Changed in motif (Ubuntu Trusty):
assignee:	nobody → Graham Inggs (ginggs)
status:	Confirmed → In Progress

Graham Inggs (ginggs) on 2015-09-24

summary:

- segfault in 0x00007ffff725a7dd in _XtWindowedAncestor () from
- /usr/lib/x86_64-linux-gnu/libXt.so.6
+ [SRU] Fix for upstream bug #1565 causes segfaults in ddd and xpdf

Graham Inggs (ginggs) on 2015-09-24

description:

updated

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-09-25:

#33

motif-sru-lp1354961.debdiff Edit (3.2 KiB, text/plain)

Revision history for this message

Chris J Arges (arges) wrote on 2015-09-30: Please test proposed package

#34

Hello themusicgod1, or anyone else affected,

Accepted motif into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/motif/2.3.4-5ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in motif (Ubuntu Trusty):
status:	In Progress → Fix Committed
tags:	added: verification-needed

Revision history for this message

Cees (cakoolen) wrote on 2015-10-01:

#35

Hi,

Did some testing using ddd and to me it looks like this fixes the problem. Up til now, I was still using the PPA version from Graham so I had to downgrade to this version. Clicked arround in DDD, used my keyboard and it looks fine.

Revision history for this message

Cees (cakoolen) wrote on 2015-10-01:

#36

Sorry, Forgot to mention the version I tested: 2.3.4-5ubuntu0.1

Cees (cakoolen) on 2015-10-01

tags:

added: verification-done-trusty

Graham Inggs (ginggs) on 2015-10-01

tags:

added: verification-done
removed: utopic verification-needed

Revision history for this message

Quang Ong (quang777) wrote on 2015-10-01:

#37

What version are we supposed to see for the proposed repo? I initially tried the PPA that Graham posted with was version 2.3.4-8~ppa4~ubuntu14.04.1~ppa1, but I don't see that version on the trusty-proposed repo after following the instructions on how to configure to use the -proposal repos.

Q

Revision history for this message

Graham Inggs (ginggs) wrote on 2015-10-01:

#38

@quang777:
> What version are we supposed to see for the proposed repo?

2.3.4-5ubuntu0.1

https://launchpad.net/ubuntu/+source/motif/2.3.4-5ubuntu0.1

Revision history for this message

Brian Murray (brian-murray) wrote on 2015-10-08: Update Released

#39

The verification of the Stable Release Update for motif has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-10-08:

#40

This bug was fixed in the package motif - 2.3.4-5ubuntu0.1

---------------
motif (2.3.4-5ubuntu0.1) trusty; urgency=medium

  * Stable Release Update (LP: #1354961):
    + Disable fix for upstream bug #1565 which caused segfaults in
      ddd and xpdf (Closes: #781995).
    + Remove XmForceGrabKeyboard@Base from d/libxm4.symbols
      which was introduced by upstream's updated fix applied in
      motif 2.3.4-5 (Closes: #782678).

-- Graham Inggs <email address hidden> Fri, 25 Sep 2015 10:48:10 +0200

Changed in motif (Ubuntu Trusty):
status:	Fix Committed → Fix Released

Ubuntu
ddd package

[SRU] Fix for upstream bug #1565 causes segfaults in ddd and xpdf

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

	Status	Importance	Assigned to
ddd (Ubuntu)	Invalid	High	Unassigned
Trusty	Invalid	Undecided	Unassigned
Utopic	Invalid	Undecided	Unassigned
motif (Debian)	Fix Released	Unknown	debbugs #781995
motif (Ubuntu)	Fix Released	High	Unassigned
Trusty	Fix Released	Undecided	Graham Inggs
Utopic	Invalid	Undecided	Unassigned
xpdf (Ubuntu)	Invalid	High	Unassigned
Trusty	Invalid	Undecided	Unassigned
Utopic	Invalid	Undecided	Unassigned

Ubuntuddd package

[SRU] Fix for upstream bug #1565 causes segfaults in ddd and xpdf

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntu
ddd package