Issue 3723 - OpenOffice crashes almost immediately running on remote X display
Summary: OpenOffice crashes almost immediately running on remote X display
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 641
Hardware: Other Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christof.pintaske
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-29 17:24 UTC by Unknown
Modified: 2003-03-13 10:14 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-03-29 17:24:34 UTC
Just installed 641D (after deleting 641C) and started 'soffice'.
Pressed cancel at the address database wizard.
Moved the main window, or rather _TRIED_ to move it, which killed the 
application with the following message in the shell:
Xlib: sequence lost (0x12c6b > 0x2c6c) in reply type 0x0!
Aborted

I run an X-terminal on one machine, running the apps on another. All RedHat 
7.2 With the latest patches from red-carpet. Athlon Slot A CPU on the 
terminal and Athlon Thunderbird CPU on the server.
Comment 1 Unknown 2002-03-29 17:28:46 UTC
It's getting worse. Second time around the app died after hitting 
cancel. The third time it survived cancel, but froze when I moved 
the window. Fourth time around I didn't get the address database 
wizard, and tried to type something: crash! Fifth time... Wait a 
minute... There ain't going to be a fifth attempt! :oP

Here is the output in the console:
[philip@mail philip]$ /opt/OpenOffice.org641/soffice 
Xlib: sequence lost (0x12c6b > 0x2c6c) in reply type 0x0!
Aborted
[philip@mail philip]$ 
[philip@mail philip]$ /opt/OpenOffice.org641/soffice 
Aborted
[philip@mail philip]$ /opt/OpenOffice.org641/soffice 
Xlib: unexpected async reply (sequence 0x1ac6)!
[philip@mail philip]$ /opt/OpenOffice.org641/soffice 
Xlib: unexpected async reply (sequence 0x1aad)!
X IO Error
Aborted
Comment 2 stefan.baltzer 2002-04-10 16:09:07 UTC
Changed component to "database access". Reassigned to Marc.
Comment 3 marc.neumann 2002-04-11 13:40:14 UTC
hi,

I can't find any problem. I think it's a more general problem wit you X.

Bye Marc
Comment 4 Unknown 2002-04-11 17:25:02 UTC
Issue is not resolved. It persists. I have no problems but OpenOffice 
with my standard sawfish/rh72. I think OO has a problem with exported 
displays.
Comment 5 marc.neumann 2002-04-12 11:30:05 UTC
Hi Andreas,

this issue has nothing to do with database access. I think it's a more
general issue with displays, can you please have a look in your team.

Bye Marc
Comment 6 atr 2002-04-16 10:07:51 UTC
Hi, i think this is your tutn.
Comment 7 Unknown 2002-05-01 00:36:17 UTC
I am having this problem as well, and it sure looks like a remote
display issue.  When I can boot up a box with a head I'll verify that
it works locally.  I get the following error

Xlib: unexpected async reply (sequence 0x21f8)!

when starting a new install of 641d.  This happens sometimes after I
have had a chance to dismiss the address import stuff, sometimes
before, but always before I have a chance to open a menu.  I'm running
soffice on a Red Hat 6.2 machine with glibc 2.1.3, and going to X
running on a diskless terminal.
Comment 8 Martin Hollmichel 2002-05-05 07:53:29 UTC
4236 may related to this, christof, heiner can you take a look please ?!
Comment 9 thorsten.martens 2002-05-16 10:40:40 UTC
TM: As HR told me, #4236 doesn`t have to do anything with this one.
Comment 10 thorsten.martens 2002-07-31 10:36:50 UTC
TM->CP: Please have a look. Thanks !
Comment 11 christof.pintaske 2002-10-24 14:22:15 UTC
cannot reproduce, This seems to be a specific problem with your
terminal. Can you tell us what kind of window manager you use on your
X terminal ? By any chance can you try a different one ? What does
xdpyinfo report for that display ?
Comment 12 christof.pintaske 2002-11-29 18:00:45 UTC
cannot reproduce
Comment 13 michael.bemmer 2003-03-13 09:39:14 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 14 michael.bemmer 2003-03-13 10:14:55 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.