Bug #7552 “xterm: Segmentation fault on start” : Bugs : libx11 package : Ubuntu

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-22:

#1

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 20:42:01 +0300
From: Anton <email address hidden>
To: <email address hidden>
Subject: xterm: Segmentation fault on start

Package: xterm

xterm crashes on start in XtToolkitThreadInitialize () from
/usr/X11R6/lib/libXt.so.6

I am using debian sarge installed from debian-installer-rc1

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-22:

#2

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 16:13:38 -0400
From: Thomas Dickey <email address hidden>
To: <email address hidden>
Subject: Re: Bug#266684: xterm: Segmentation fault on start

--9jxsPFA5p3P2qPhR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 18, 2004 at 08:20:07PM +0200, Anton wrote:
> Package: xterm
>=20
> xterm crashes on start in XtToolkitThreadInitialize () from=20
> /usr/X11R6/lib/libXt.so.6
>=20
> I am using debian sarge installed from debian-installer-rc1

It is likely (given recent reports) that the problem lies in the X librarie=
s.
A walkback would be useful for collating the various reports.

--=20
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

--9jxsPFA5p3P2qPhR
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (SunOS)
Comment: For info see http://www.gnupg.org

iD8DBQFBI7gmtIqByHxlDocRAu0JAKCaulHQE3Odxp91aUv2HquNwIO4VACdG6qQ
voJPvtwc5w2ohyvSfhF0SqA=
=YSIr
-----END PGP SIGNATURE-----

--9jxsPFA5p3P2qPhR--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-22:

#3

Download full text (5.5 KiB)

Message-ID: <email address hidden>
Date: Sat, 21 Aug 2004 21:02:55 -0500
From: Branden Robinson <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: Bug#266684: xterm: Segmentation fault on start

--F4Dl6XKrV7PH8SJF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

reassign 266684 libx11-6
severity 266684 serious
merge 250655 266684
thanks

On Wed, Aug 18, 2004 at 08:42:01PM +0300, Anton wrote:
> Package: xterm
>=20
> xterm crashes on start in XtToolkitThreadInitialize () from=20
> /usr/X11R6/lib/libXt.so.6
>=20
> I am using debian sarge installed from debian-installer-rc1

This was already filed as #250655. If it had not already been filed,
however, your report would not have included enough information for us to
handle it well.

[The following is a form letter.]

Hello,

You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.

While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name. A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports. This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report. This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers. The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports. (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System. (If you already do use
"reportbug", please see below.)

One way to install reportbug is with "apt-get"; for
example:

# apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise. If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.

$ reportbug --mo...

Message-ID: <20040822020255.GG14820@redwald.deadbeast.net>
Date: Sat, 21 Aug 2004 21:02:55 -0500
From: Branden Robinson <branden@debian.org>
To: 266684-submitter@bugs.debian.org, control@bugs.debian.org
Subject: Re: Bug#266684: xterm: Segmentation fault on start

--F4Dl6XKrV7PH8SJF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

reassign 266684 libx11-6
severity 266684 serious
merge 250655 266684
thanks

On Wed, Aug 18, 2004 at 08:42:01PM +0300, Anton wrote:
> Package: xterm
>=20
> xterm crashes on start in XtToolkitThreadInitialize () from=20
> /usr/X11R6/lib/libXt.so.6
>=20
> I am using debian sarge installed from debian-installer-rc1

This was already filed as #250655.  If it had not already been filed,
however, your report would not have included enough information for us to
handle it well.

[The following is a form letter.]

Hello,

You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.

While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports.  This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report.  This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers.  The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports.  (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System.  (If you already do use
"reportbug", please see below.)

One way to install reportbug is with "apt-get"; for
example:

# apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise.  If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.

$ reportbug --mode=3Dnovice
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.

$ reportbug
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

The reportbug command is extensively documented in its usage message and
manual page.  Commands to view these pieces of documentation are:

$ reportbug --help | more
  $ man reportbug

(The output of the above commands has been omitted from this message.)

If you do use reportbug, but are so daunted by the large number of bugs
already filed against a package that you feel you cannot search for a
duplicate, please note that reportbug has a (f)ilter feature that enables
you to use a keyword search to limit the number of bugs reported.  (If
you're feeling ambitious, the filter feature also accepts a regular
expression.)  For example, if you'd like to report a SEGV (segfault), you
might filter based on the term "SEGV".  If you're having trouble upgrading
a package, you might filter based on "upgrad" (to catch both "upgrade" and
"upgrading").  Some package maintainers retitle bugs to contain keywords so
as to facilitate better filtering and convey more useful information, since
a bug report with a title of "broken" or the like is not very useful to
anyone.

We appreciate you taking the time to help package maintainers serve you
better by reducing the amount of time they need to spend coping with
duplicate bug reports.

Thanks for using the Debian system!

--=20
G. Branden Robinson                |         "Religion is nonsense."
Debian GNU/Linux                   |         "It's also a gold mine --
branden@debian.org                 |         if you know where to dig."
http://people.debian.org/~branden/ |         -- _Shine_

--F4Dl6XKrV7PH8SJF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iEYEARECAAYFAkEn/s8ACgkQ6kxmHytGonwkUwCeKjiB8BU3xWkABxHcm75vrivU
NusAnRcLhy7UwLxM7UrWLMO8b12lNWQW
=qmAO
-----END PGP SIGNATURE-----

--F4Dl6XKrV7PH8SJF--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-22:

#4

Marking as duplicate based on debbugs merge (250655,266684)

This bug has been marked as a duplicate of bug 7170.

Bug Watch Updater (bug-watch-updater) on 2006-09-27

Changed in libx11:
status:	Unknown → Fix Released

Affects		Status	Importance	Assigned to	Milestone
	libx11 (Debian)	Fix Released	Unknown	debbugs #266684
	libx11 (Ubuntu)	Invalid	High	Unassigned

Ubuntu
libx11 package

xterm: Segmentation fault on start

Bug Description

Other bug subscribers

Remote bug watches

Ubuntulibx11 package

xterm: Segmentation fault on start

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
libx11 package