desktop-packages team mailing list archive

[Rolf Leggewie <258089@xxxxxxxxxxxxxxxxxx>]

Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as "Won't Fix".

** Changed in: xterm (Ubuntu Hardy)
       Status: New => Won't Fix

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

Title:
  xterm segfaults when run via panel launcher

Status in “xterm” package in Ubuntu:
  Fix Released
Status in “xterm” source package in Hardy:
  Won't Fix

Bug description:
  Binary package hint: xterm

  Package: xterm-229-1ubuntu1
  Description:	Ubuntu 8.04.1
  Release:	8.04

  When started from a panel launcher, xterm segfaults shortly after
  startup at least 50% of the time.  When run from the command line, it
  always seems to work.  The launcher was created with  Add to
  Panel/Custom Application Launcher/Command=xterm.  Additional arguments
  to xterm do not seem to affect whether or not it crashes.

  I'm running Hardy i386 on a Core2Duo.  I also experienced similar
  failure to launch from xterm on Gutsy, on this same PC and on another
  PC.

  This appears in /var/log/syslog each time:

  Aug 15 13:36:12 loki kernel: [66796.742525] xterm[18595]: segfault at
  00044c10 eip 08077dbd esp bf9b4dc0 error 4

  (esp varies but the other addresses are always the same).

  No core dump is produced (ulimit -c is unlimited and a simple test app
  which does "*(int*)0=0" does produce a core file), nor is there a
  crash log in /var/crash (apport is enabled).

  Changing the launcher command to run strace produced the attached log.

  Downloading the source package & rebuilding with debugging enabled
  gave me a core dump.  The crash is at line 1684 of util.c in
  handle_translated_exposure():

      (gdb) where
      #0  0x08082722 in handle_translated_exposure (xw=0x80c7478, rect_x=0, rect_y=0, rect_width=499, 
          rect_height=316) at ../util.c:1684
      #1  0x08082346 in HandleExposure (xw=0x80c7478, event=0xbfe29838) at ../util.c:1598
      #2  0x0805aac4 in VTExpose (w=0x80c7478, event=0xbfe29838, region=0x0) at ../charproc.c:4803
      #3  0x08073a36 in Redraw () at ../misc.c:1119
      #4  0x0807da6e in ScrollBarOn (xw=0x80c7478, init=0, doalloc=1) at ../scrollbar.c:488
      #5  0x0805db1f in VTRealize (w=0x80c7478, valuemask=0xbfe299d8, values=0xbfe2998c)
          at ../charproc.c:6250
      #6  0xb7e5db71 in ?? () from /usr/lib/libXt.so.6
      #7  0xb7e5dcfa in ?? () from /usr/lib/libXt.so.6
      #8  0xb7e5df9e in XtRealizeWidget () from /usr/lib/libXt.so.6
      #9  0x0805af82 in VTInit () at ../charproc.c:4976
      #10 0x0806cc2d in spawnXTerm (xw=0x80c7478) at ../main.c:3245
      #11 0x0806be0e in main (argc=0, argv=0xbfe2a918) at ../main.c:2289

  Line 1684 is:

      leftcol = x0 / CurFontWidth(screen, screen->cur_row);

  screen is a valid pointer and much of what it points to looks
  sensible, but screen->visbuf (used by CurFontWidth) does not point to
  a readable memory location:

      (gdb) x/32x screen->visbuf
      0x44c00:	Cannot access memory at address 0x44c00

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