Your message dated Thu, 17 Jan 2008 03:47:03 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#461155: flightgear: dependency version missing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: flightgear
Version: 1.0.0-1
Severity: minor
flightgear 1.0.0 shows a dependency on libgl1-mesa-glx (without a version
requirement).
Package with Etch release was 6.5.1-0.6; and identical 6.5.1-06 for
libgl1-mesa-dri.
This config terminates with Segmentation Fault, with a 3Dfx graphics board (tdfx
support compiled into kernel) and all dependencies satisfied to make aptitude
happy.
Multiple lines of form: "libGL warning: ..driver claims to not support visual
0xNN"
(various NN values) are emitted to console, flightgear proceeds through
initialization
up to (apparently) the first image display then SegFaults.
Solution:
Upgraded libgl1-mesa-glx (and *-dri) to version 7.0.2-3 and flightgear starts
properly
with no libGL warning messages. Therefore, I suggest setting a minimum version
requirement for the libgl1-mesa-glx dependency.
-- System Information:
Debian Release: 4.0
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_US
Versions of packages flightgear depends on:
ii fgfs-base 1.0.0-1 Flight Gear Flight Simulator -- ba
ii freeglut3 2.2.0-8 OpenGL Utility Toolkit
ii libalut0 1.1.0-1 OpenAL Utility Toolkit
ii libc6 2.7-5 GNU C Library: Shared libraries
ii libgcc1 1:4.2.2-4 GCC support library
ii libgl1-mesa-glx [libgl1 7.0.2-3 A free implementation of the OpenG
ii libglu1-mesa [libglu1] 6.5.1-0.6 The OpenGL utility library (GLU)
ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library
ii libjpeg62 6b-13 The Independent JPEG Group's JPEG
ii libopenal0a 1:0.0.8-4 OpenAL is a portable library for 3
ii libsm6 1:1.0.1-3 X11 Session Management library
ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
ii libxi6 1:1.0.1-4 X11 Input extension library
ii libxmu6 1:1.0.2-2 X11 miscellaneous utility library
ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii plib1.8.4c2 1.8.4-8 Portability Libraries: Run-time pa
ii simgear0 1.0.0-1 Simulator Construction Gear -- sha
ii zlib1g 1:1.2.3.3.dfsg-8 compression library - runtime
flightgear recommends no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Eugene Stemple skrev:
Package: flightgear
Version: 1.0.0-1
Severity: minor
flightgear 1.0.0 shows a dependency on libgl1-mesa-glx (without a version
requirement).
Package with Etch release was 6.5.1-0.6; and identical 6.5.1-06 for
libgl1-mesa-dri.
This config terminates with Segmentation Fault, with a 3Dfx graphics board (tdfx
support compiled into kernel) and all dependencies satisfied to make aptitude
happy.
Multiple lines of form: "libGL warning: ..driver claims to not support visual
0xNN"
(various NN values) are emitted to console, flightgear proceeds through
initialization
up to (apparently) the first image display then SegFaults.
Solution:
Upgraded libgl1-mesa-glx (and *-dri) to version 7.0.2-3 and flightgear starts
properly
with no libGL warning messages. Therefore, I suggest setting a minimum version
requirement for the libgl1-mesa-glx dependency.
I don't think this is flightgear's responsibility. FlightGear (or any
other OpenGL game) doesn't and shouldn't depend on a particular version
of OpenGL, as long as it's properly configured. If your version doesn't
work, that's a bug or misconfiguration in your OpenGL drivers, not in
flightgear; glxinfo and glxgears (from mesa-utils) would certainly show
the same symptoms. If there's any versions involved, presumably it would
rather be your kernel (and its DRI modules) or your X server requiring a
particular libgl1-mesa-dri version. It may also be hardware-specific;
perhaps ATI users wouldn't have to upgrade their DRI.
The application doesn't care, as long as it's configured right;
FlightGear would run fine on woody (if backported there), with whatever
hardware woody supported, for example. All it takes is that glxinfo and
glxgears works, as a baseline.
--- End Message ---
