[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#309432: marked as done (openoffice.org: hangs at start with Xlib error)

Your message dated Tue, 7 Jun 2005 17:25:04 +0100
with message-id <200506071725.05983.halls@debian.org>
and subject line Bug#309432: Can't reproduce anymore
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)

Received: (at submit) by bugs.debian.org; 17 May 2005 07:47:27 +0000
>From bilm@oce.nl Tue May 17 00:47:27 2005
Return-path: <bilm@oce.nl>
Received: from mail-res.bigfish.com (mail64-res-R.bigfish.com) [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DXwnX-0001DW-00; Tue, 17 May 2005 00:47:27 -0700
Received: from mail64-res.bigfish.com (localhost.localdomain [])
	by mail64-res-R.bigfish.com (Postfix) with ESMTP id D418684300
	for <submit@bugs.debian.org>; Tue, 17 May 2005 07:46:56 +0000 (UTC)
X-BigFish: VPC
Received: by mail64-res (MessageSwitch) id 1116316016801040_12994; Tue, 17 May 2005 07:46:56 +0000 (UCT)
Received: from smtp01.oce.nl (smtp01.oce.nl [])
	by mail64-res.bigfish.com (Postfix) with ESMTP id 848FE842DE
	for <submit@bugs.debian.org>; Tue, 17 May 2005 07:46:56 +0000 (UTC)
Received: from smtp05.oce.nl (smtp05.oce.nl [])
	by smtp01.oce.nl (8.12.8p1/8.12.8) with ESMTP id j4H7ktxC021622
	for <submit@bugs.debian.org>; Tue, 17 May 2005 09:46:55 +0200 (MEST)
Received: from smtp-venlo.oce.nl (localhost [])
	by smtp05.oce.nl (8.12.8p1/8.12.8) with ESMTP id j4H7ksg7019401
	for <submit@bugs.debian.org>; Tue, 17 May 2005 09:46:55 +0200 (MEST)
Received: from smtp03.oce.nl (smtp03.oce.nl [])
	by smtp-venlo.oce.nl (8.12.8p1/8.12.8) with ESMTP id j4H7kqCa001134
	for <submit@bugs.debian.org>; Tue, 17 May 2005 09:46:53 +0200 (MEST)
Received: from pc2-bilm.oce.nl (localhost [])
	by smtp03.oce.nl (8.12.8p1/8.12.8) with SMTP id j4H7kqGd001647
	for <submit@bugs.debian.org>; Tue, 17 May 2005 09:46:52 +0200 (MEST)
Message-Id: <200505170746.j4H7kqGd001647@smtp03.oce.nl>
Received: by pc2-bilm.oce.nl (sSMTP sendmail emulation); Tue, 17 May 2005 09:46:45 +0200
From: "Manuel Bilderbeek" <bilm@oce.nl>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: openoffice.org: hangs at start with Xlib error
X-Mailer: reportbug 3.8
Date: Tue, 17 May 2005 09:46:45 +0200
X-Filter-Version: 1.12a-oce (smtp-venlo)
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.3 required=4.0 tests=BAYES_00,HAS_PACKAGE,
	MSGID_FROM_MTA_HEADER autolearn=no 

Package: openoffice.org
Version: 1.1.3-9
Severity: normal

Since a short while, I can't start OO.o anymore:

$ oowriter
Xlib: sequence lost (0x10000 > 0xe) in reply type 0x0!

it hangs after this and I need to press CTRL-C to get back to my prompt.

The same happens with the other OO.o applications.

This makes the whole package unusable for me, so I think the Severity
should be set to higher than normal. (It was downgraded because I don't
know what violation of the DPM it is, exactly...)

Note that I'm using the Matrox binary display driver version 1.4.1,
which may (or may not) be related to this issue.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages openoffice.org depends on:
ii  dictionaries-common [openoffi 0.25.9     Common utilities for spelling dict
ii  openoffice.org-bin            1.1.3-9    OpenOffice.org office suite binary
ii  openoffice.org-debian-files   1.1.3-8+1  Debian specific parts of OpenOffic
ii  openoffice.org-l10n-en [openo 1.1.3-9    English (US) language package for 
ii  ttf-opensymbol                1.1.3-9    The OpenSymbol TrueType font
ii  xml-core                      0.09       XML infrastructure and XML catalog

-- no debconf information

Received: (at 309432-close) by bugs.debian.org; 7 Jun 2005 16:25:10 +0000
>From halls@debian.org Tue Jun 07 09:25:10 2005
Return-path: <halls@debian.org>
Received: from moutng.kundenserver.de [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1Dfgt3-0006nh-00; Tue, 07 Jun 2005 09:25:09 -0700
Received: from i-83-67-59-194.freedom2surf.net [] (helo=feathers.thehalls.de)
	by mrelayeu.kundenserver.de with ESMTP (Nemesis),
	id 0ML25U-1Dfgt21y2E-0000b9; Tue, 07 Jun 2005 18:25:08 +0200
Received: by feathers.thehalls.de (Postfix, from userid 1050)
	id BE5DA8008; Tue,  7 Jun 2005 17:25:07 +0100 (BST)
From: Chris Halls <halls@debian.org>
To: Manuel Bilderbeek <bilm@oce.nl>, 309432-close@bugs.debian.org
Subject: Re: Bug#309432: Can't reproduce anymore
Date: Tue, 7 Jun 2005 17:25:04 +0100
User-Agent: KMail/1.8.1
References: <429C350E.5040904@oce.nl>
In-Reply-To: <429C350E.5040904@oce.nl>
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200506071725.05983.halls@debian.org>
X-Provags-ID: kundenserver.de abuse@kundenserver.de login:b46e2b357ea7d4f6cadf4c99fb902606
Delivered-To: 309432-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

On Tuesday 31 May 2005 10:57, Manuel Bilderbeek wrote:
> I just rebooted after the new X and kernel packages got in, and now I
> can't reproduce this problem anymore.

Thanks, I'll close the report then.

> About reportbug, maybe I should report a bug to reportbug, because
> there's no way of reporting important bugs anymore if you don't know the
> exact violation of the DPM...? Or is this related to the freeze?

I tried reporting an important bug in reportbug and did not get any question 
about violations.  Perhaps you mean serious/grave/critical bugs?  Those are 
managed/upgraded by the maintainer so it is fine to report as severity 
important and suggest a higher severity in the report body.

Thanks for your report

Reply to: