azureus (and others) cannot start main window on amd64

[HPO]

reproduce:
- install latest azureus (2.5.0) and sun jvm (1.5.0.10).
- WORKS with vnc4server- 4.1.1+xorg1.0.2-0ubuntu1.6.06
- does NOT WORK with 4.1.1+xorg1.0.2-0ubuntu1.6.10

X Windows error: request_code 146, minor code 2

[Kees Cook (kees)]

Thanks for your report. If you downgrade vnc4 using:

  apt-get install vnc4=4.1.1+xorg1.0.2-0ubuntu1

Does this bug go away?

(I'm assuming you tried azureus on both a Dapper and Edgy machine?)

[Kees Cook (kees)]

This is a duplicate of #78282?

[HPO (hpo)]

It works fine after re-downgrading to 4.1.1+xorg1.0.2-0ubuntu1.6.06. Different versions of jre, however, don't solve the problem in .10 .

It is NOT a duplicate of 78282. e.g. xterm starts, wm2 starts (custom xstartup).
After launching azureus (sync or not), the splash window appears; I even imagine a "flash" of the main window - then the whole thing aborts with above-mentioned X Window Error in SWT.

I cannot say if it's x64-specific as I only have x64 machines here, unfortunately.

[Kees Cook (kees)]

Confirming. I see the same behavior. (And downgrading fixes the problem.)

[William Grant (wgrant)]

That X error code is the same as the one experienced in #78282. An xterm will start fine in my situation as well, but gnome-terminal, metacity, other complexish stuff dies with the above error. I think they're dupes.

[HPO (hpo)]

If so, they may be duplicates. From the thread on #78282, the description sounded wholly different (scripts not being executable etc.).

For complexish stuff: I don't run metacity/gnome, but it seems all my "bigger" java programs, esp. those using SWT, crash.

[William Grant (wgrant)]

The script not being executable is unrelated to the actual bug.

[Ian Justman (ianj)]

I have a case where the exact opposite is true, per bug 68020. In my case, it DOES work under Xorg but DOES -NOT- work under VNC4Server and it's i386 rather than AMD64/EM64T. And I'm running Feisty on all my production Ubuntu machines.

My normal complement I run as a "desktop" on that machine (which is headless) is as follows:

--VNC4Server
--IceWM (I do not need GNOME, KDE or any heavy GUE, though TWM's entirely too lightweight for my purposes); this is my fileserver, not my desktop
--Azureus (I have 2.5.0.0 from Universe for testing purposes; I prefer to use the official version for my actual torrenting)

Works under Xorg just fine but dies after presenting splash screen or a few screens during its first run in VNC4Server. And it doesn't matter whether Azureus and VNC4Server is on the same machine or are on two separate machines. The outcome is always the same.

I have a similar report on bug #78282 and the solution one user suggested was using TightVNCServer in the meantime. That advice actually worked. I now have Azureus running stably on TightVNC. I would like to at least have VNC4Server as a possible choice.

Hope this report helps.

--Ian.

[Ian Justman (ianj)]

Another note I forgot to make. Per 68020's advice, I tried the JRE 5 package and I had the exact same problem under VNC4Server as I had under JRE6, and likewise, the exact same success I had, only substitute VNC4Server with Xorg, and now, TightVNCserver.

--Ian.

[Saivann Carignan (oxmosys)]

This sounds a lot like bug 57875.

Can you install the latest azureus version 2.5.0.4-1ubuntu3~gutsy1 from Linux Ubuntu Gutsy backports and confirm if you still have this issue?

And outside of azureus, did you experience that bug with another software?

Thanks for your contribution with this bug report.

[Saivann Carignan (oxmosys)]

Can someone still reproduce that issue with latest azureus?

[HPO (hpo)]

Given up-to-date gutsy and the newest azureus (official distribution): No, the issue has gone.

Thanks a lot!

[Saivann Carignan (oxmosys)]

Thank you very much for your confirmation, I'm glad to ear that it's fixed here :)