Closed Bug 60281 Opened 25 years ago Closed 22 years ago

[greeamozilla-installer: Xlib: unexpected async reply (sequence 0x1ee5)!

Categories

(SeaMonkey :: Installer, defect, P3)

Product:
SeaMonkey
Component:
Installer
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
Future

People

(Reporter: greearb, Assigned: slogan)

Details

[greear@grok mozilla-installer]$ ./mozilla-installer Xlib: unexpected async reply (sequence 0x1ee5)! Installer is busted it seems. Gets started downloading (though never shows progress bars, and doesn't update 1/6 package info..it seems to download a few packages before blowing up with the above error.) This is from the 'latest nightly build', as of Wed 15, 2000 Keep up the good work, Ben
sending this over to Samir.
Assignee: ssu → sgehani
QA Contact: gemal → gbush
Linux distribution vendor?
Per Ben Greear: Redhat 6.2, but with a fairly recent version of GNOME installed. It was very re-producible.
GNOME version?
I am seeing this with builds for 11/27 and 11/28 also
Marking NEW as per comments.
Status: UNCONFIRMED → NEW
Ever confirmed: true
installation is a problem when doing from remote login. I can successfully install on the machine itself
Grace, When did this first start? (We have not changed the Linux installer code since N6 RTM. Have you changed the way you remote display?)
This started 11/27....I have the trunk builds from 11/14 that installed as usual- up through 11/21 I have not changed anything - on purpose that is I have access to machine in lab for CD testing and tried the 11/27 and on builds there and they install successfully (and run from my remote machine once installed)
I always used the installer builds, last one that worked for me was a 2-5 build. Now, with a build from the 2001-02-06-21-Mtrunk directory, I get this error. As far as I can remember, I did not change my configuration.
Nothing changed on our end with the installer code base either. Does the 02-05 build still work for you? (Trying to determine if anything may have changed on your end in the last two days.)
No problem installing todays build (2001020808 linux).
is this related to bug 76224? tinus: what steps did you take to attempt to reproduce this issue? Would someone please follow the bug reporting guidelines and provide steps to reproduce? Thanks.
As this happened three months ago, I do not remember exactly what happened. The steps to reproduce were like this: - Try to install mozilla using the installer build - See it fail with the 'unexpected async reply' message. As simple as that. I did not do anything strange, there are little choices to make in the installer, it just didn't work. The bug I reported was probably fixed, as I haven't had any problems since. I am not sure if it was the same problem as what this bug is about, but since it looked quite similar to what I had been experiencing, I appended my report to this bug instead of filing another duplicate. It might have been better to describe exactly what I did and what happened, but that's hard to do when there is so little to describe. I apologize if I confused you. I think the other people who have reported that they have reproduced the bug should be contacted to retry with a recent build. I expect there will be little problems, as otherwise this would probably have been a MOSTFREQ bug.
I just had this problem. Red Hat 7.0 beta (wolverine) with glibc-2.2.2-9.i386. mozilla-installer apparently downloads all the packages, but then dies with this error: Xlib: unexpected async reply (sequence 0x29d3)! Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown).
Syd, Can you take a look at this? Looks very similar to bug 69734. Thanks.
Over to Syd for installer bug triage
Assignee: sgehani → syd
Target Milestone: --- → M1
Target Milestone: M1 → Future
@Reporter Does this bug exists in newer builds? If not, then please close the bug as WorksForMe else let us know.
As far as I know, this is fixed. I have done several installs lately with no problem on RedHat 9 + updates.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.