Bug 541

Summary:

Xorg Xprt may crash with "Freeing resource id=40200000 which isn't there"

Product:

xprint

Reporter:

Roland Mainz <roland.mainz>

Component:

Server: Other

Assignee:

Roland Mainz <roland.mainz>

Status:

RESOLVED FIXED

QA Contact:

Severity:

enhancement

Priority:

high

CC:

alan.coopersmith, jay.hobson

Version:

unspecified

Hardware:

All

OS:

All

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Patch for 2004-04-22-XORG-CURRENT	none
Patch for 2004-04-25-trunk	none

Description Roland Mainz 2004-04-23 16:49:37 UTC

The Xorg version of Xprt can "crash" with the following message when a client
exists unexpectedly (e.g. client crash may take Xprt with it):
-- snip --
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from
list!
AUDIT: Fri Apr 23 08:44:30 2004: 11056 Xprt: client 1 connected from local host
AUDIT: Fri Apr 23 08:45:34 2004: 11056 Xprt: client 1 disconnected

Fatal server error:
Freeing resource id=40200000 which isn't there
-- snip --

Comment 1 Roland Mainz 2004-04-25 05:01:14 UTC

Created attachment 234 [details] [review]
Patch for 2004-04-22-XORG-CURRENT

The patch makes the issue non-fatal... just a warning will be printed.
I am not sure whether this is really correct... but it worked for the last two
years in the xprint.mozdev.org CVS without problems...

Comment 2 Roland Mainz 2004-04-26 08:40:42 UTC

Created attachment 240 [details] [review]
Patch for 2004-04-25-trunk

Comment 3 Roland Mainz 2004-04-26 08:42:50 UTC

Patch checked-in...

Checking in xc/ChangeLog;
/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.4; previous revision: 1.3
done
Checking in xc/programs/Xserver/dix/resource.c;
/cvs/xorg/xc/programs/Xserver/dix/resource.c,v  <--  resource.c
new revision: 1.3; previous revision: 1.2
done
Mailing the commit message to xorg-commit@pdx.freedesktop.org...

... marking bug as FIXED.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.