Bug 459434 - (_UsUrPeR_) LTSP ldm core dump
LTSP ldm core dump
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: ldm (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-18 16:19 EDT by Joel Sass
Modified: 2009-01-29 16:38 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-29 16:38:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joel Sass 2008-08-18 16:19:38 EDT
Description of problem:
Fedora 9 server running LTSP 5 with. Getting ldm segfaults. Problem reported in #ltsp on irc.freenode.net

The error is only generated with the following client:

AOpen PT75 (SIS 6326 Chipset).

The error is as follows:

xauth: Creating new authority file /var/run/ldm-xauth-oQR0egdsB
/usr/share/ltsp/screen.d/ldm: line 105: 1370 Segmentation fault
ldm vt${TTY} ${DISP} ${XARGS}

The core has been dumped and sent out.



Version-Release number of selected component (if applicable):
ldm-2.0.11-1.fc9.i386

How reproducible:
As the sun rises and sets

Steps to Reproduce:
1.Install LTSP5 in Fedora 9
2.run the following RPM: http://togami.com/~k12linux-temporary/fedora/9/i386/ltspfs-server-5.1.19-1.fc9.i386.rpm
3.use the etherboot-tagged image that is generated after re-building an i386 ltsp image
  
Actual results:
core dump

Expected results:
Clean booting client without a core dump

Additional info:
Comment 1 Warren Togami 2008-08-18 18:54:55 EDT
#0  __libc_free (mem=0xb7ef2000) at malloc.c:3599
#1  0x002c1a64 in _IO_free_backup_area (fp=0x89017a8) at genops.c:214
#2  0x002bf8b8 in _IO_new_file_overflow (f=0x89017a8, ch=-1) at fileops.c:853
#3  0x002be994 in _IO_new_file_xsputn (f=0x89017a8, data=0x804b95d, n=27) at fileops.c:1348
#4  0x00293d0f in _IO_vfprintf_internal (s=0x89017a8, format=0x804b95d "Process returned no status\n", ap=0xbfbfa9ec "��\004\b\n") at vfprintf.c:1315
#5  0x0034bbb7 in ___fprintf_chk (fp=0x89017a8, flag=1, format=0x804b95d "Process returned no status\n") at fprintf_chk.c:37
#6  0x0804940d in ldm_wait (pid=1383) at /usr/include/bits/stdio2.h:98
#7  0x080494ea in die (msg=0x804b7f4 "ERROR: get_userid from greeter failed") at ldm.c:73
#8  0x0804a45b in main (argc=Cannot access memory at address 0xb7ef2000
) at ldm.c:461

ldm-2.0.11-1.fc9.i386
Comment 2 Warren Togami 2009-01-29 16:38:12 EST
This was fixed with the ldm and X race condition fix.

Note You need to log in before you can comment on or make changes to this bug.