http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2389
Guy Harris <guy@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Guy Harris <guy@xxxxxxxxxxxx> 2008-03-26 23:40:01 GMT ---
X11server-480100~2 isn't a build number from OS X, so you presumably installed
that from http://trac.macosforge.org/projects/xquartz.
According to that page:
Official OS-X Updates and Xquartz
Apple included some of the work done in this project in their 10.5.2 update
and will likely include further changes in possible future updates of 10.5.x.
It is suggested that you install the latest XQuartz release after updating to
10.5.2 (and any future 10.5.x or security updates).
10.5.2's version of X11 is somewhere between the 2.1.1 and 2.1.2 packages
released through this site. The launchd mechanism to start X11 in 10.5.2 is
unique to Apple's 10.5.2 and never appeared in a release from this site in its
current form (though it was essentially integrated into xinit for 2.1.2).
The 2008-002 Security Update version of X11 is the same as 10.5.2 with some
security fixes applied.
Installing versions prior to X11 2.1.2 onto OS-X 10.5.2 may work but is not
supported.
and the corresponding bugs for this crash in the Apple bug database say it's
fixed in 10.5.2, so you need to get the version of X11 from 10.5.2, or a later
version, installed.
In any case, a crash in the X11 server is *NOT* a Wireshark bug, it's an
Xquartz bug, and should be filed against Xquartz. (It is *NEVER* a bug in an X
application if it makes the X server crash, just as it's *NEVER* a bug in an
application if, for example, it causes a kernel crash or causes a crash in a
daemon to which the application talks - the {kernel,daemon} should be robust in
the face of stuff it gets passed.)
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
