Bug 275661 - gdmlogin segfault for XDMCP on x86_64
Summary: gdmlogin segfault for XDMCP on x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 246399
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 7
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-04 00:11 UTC by Scott Hunziker
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-05 14:37:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Scott Hunziker 2007-09-04 00:11:27 UTC
Description of problem:
Can't log in to new F7 installation via XDMCP.  Message in /var/log/messages:

      kernel: gdmlogin[3099]: segfault at 00000000000000001c rip
00002aaab617a318 rsp 00007ffffff649410 error 4

I added debugging to log -- this happens right after

      gdm[2501]: Handling user message: 'GET_CONFIG daemon/AddGTkModules hostname:0'
      gdm[2501]: Handling user message: 'CLOSE'

Version-Release number of selected component (if applicable):
gdm-2.18.4-2.fc7.src.rpm

How reproducible:
always happens from Exceed on Windows 

Steps to Reproduce:
1.  Set Exceed for XDMCP Query of F7 machine
2.  Launch it -- silently quits with no connection
3.  See segfault message in F7 log file
  
Actual results:
no connection

Expected results:
Trying to replace an old i386 machine.  It runs FC3 with gdm-2.6.0.5-6 and works
fine with Exceed.

Additional info:
Same results, even if I set remote logins disabled.

Comment 1 Ray Strode [halfline] 2007-09-04 14:12:24 UTC
Hi, this may be a duplicate of bug 246399.  Does the work around mentioned in
the second comment of that bug report work around the problem for you? 

Comment 2 Ray Strode [halfline] 2007-09-05 14:37:07 UTC

*** This bug has been marked as a duplicate of 246399 ***


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