Azureus always crashes on launch

It does exactly the smae thing here : the Azureus splash shows up, the window shows up and then after approximately 2 seconds...it crashes.

Here is what I get when trying to run Azureus :
"iks@iks:~$ azureus
changeLocale: *Default Language* != English (United States). Searching without country..
changeLocale: Searching for language English in *any* country..
changeLocale: no message properties for Locale 'English (United States)' (en_US), using 'English (default)'
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (53484152454432554E54494D450E43505001A3), pid=5806, tid=3084568256
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_10-b03 mixed mode, sharing)
# An error report file with more information is saved as hs_err_pid5806.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)"

I joined the log located in "~/.azureus/".

I've the same problem here at my Edgy *with all updates*. I attach a file to someone provide a fix for it.

The bug 57875 seems to be "a collection of bugs". An effort should be
made to distinguish them instead of just marking all the bugs with
similar effect as duplicates.

For instance my debdiff above solves the startup issue on both my
desktop and my laptop that are running feisty, but at friend of mine
who also has startup problems reported that his azureus still crashed
after installing my patched azureus package.

Well, sometimes this happens: that all bugs get put in one bug report.
This usually happens when a program refuses to start at all.

Somebody has some patch (that doesn't reach the repositories), so some people continue and then they go try to fix the next thing.

I agree, the idea would be that:
 a) a non launching package never reaches the repository
 b) a patch to fix _launching_ gets put in the repo's immidiately (it can't create any regression .. for anybody)
 c) the bug is closed
 d) new bugs get posted on launchpad
 e) the bugs are linked to upstream bug tracker

But what is going on here is:
  a) a completely not launching package reaches repositories
  b) patches are ignored
  c) the bug remains open
  d) those who apply the patch manually add all bugs to the already open bug report
  e) the bugs are not linked upstream
  f) everybody gives up, and downloads azureus from upstream, which _just_ works. (its been packaged as a non-working version some time since dapper, all the time with upstream's version just working)

What would be the reason it fails so miserably?
  a) there are too few motu's
  b) they have too many packages to track
  c) they don't care about pirating kids
  d) the rules about applying patches to the universe are too strict
  e) the rules about getting packages into the universe are too loose or badly enforced
  f) we don't tell the MOTU's that we love them enough (?)

PS. There are much better alternatives for azureus at the moment: Deluge 0.5, Transmission, K-Torrent. You should get deluge and transmission from http://getdeb.net (the versions in the repo's are very broken .. but not for the same reasons azureus is broken though: in this case the older upstream versions are just broken)

I think the problem is that there are packages in Ubuntu universe that
don't have MOTU maintainers who are responsible for them. If the MOTU
developers are not willing to assert that a package fulfills certain
quality requirements, it should be removed from the repositories. And
that immediately!

There are obviously too many packages to handle for the too few MOTUs.

I know that this isn't the place for this discussion, sorry.

Adding that I also know this is not really the place, but that there are simpler ways out of this mess: it's pretty obvious to me that changing bug names to be more specific would be an excellent starting point. People are voting for/duping bugs based on simple symptom rather than cause (i.e. THE BUG). Encourage people with separate symptoms to file separate bugs. BTW, as far as I know Azureus has never been non-launching (in a fresh configuration - it is quite clear in some cases what (part of) the cause is, and it's not something that could be detected before going in to the repository).

The problem of vagueness seems to me to have confused things somewhat for these bugs just recently. This bug seems pretty clearly to be a dup of bug 68020 (possibly providing useful extra information), yet it was marked as not so. It has also been marked a dup of bug 57875, which it is NOT. Bug 57875 seems to have become confused with bug 68020 as well. I'm not going to change anything yet, as Ulf has been quite active on these - you see to have provided a fix for the issue with the splash problem on bug 57875, and then a contradictory stack dump that suggests it is another bug (namely, bug 68020 - notification window crash). Even worse, other users have added a second cause, seemingly amd64 related, to bug 57875.

To summarise:

This bug should be marked duplicate of bug 68020 unless the original poster can confirm it is not (possibly adding a comment that it may be a compile issue to that bug)
This bug should be marked NOT a duplicate of bug 57875.
The title of bug 57875 should be changed to something like "Azureus crashes drawing splash screen image at startup"
Title of bug 68020 should be changed likewise to reference the notification window.
Investigate all the dups of bug 57875 to see what's really going on.
Check to make sure the amd64 issue has been filed elsewhere.

If I don't hear objections, I'll do it myself.

OK, I agree. After reading the other bug reports in 57875 more closely
I also came to the conclusion that I was having some other problem
than the one originally reported in 57875. If you believe that my
problem (and patch) correspond to 68020, then that is probably
correct, and it should be posted there. It started the first time, but
then suddenly it began to fail at startup. I haven't traced the "real"
cause of the problem, I just removed patches one by one till azureus
started again.

So yes, can you please fix this mess per your suggestions? :)

Thanks!

ons 2007-04-25 klockan 15:17 +0000 skrev Sam Brightman:
> If I don't hear objections, I'll do it myself.

No objections, but just a simple note: as issues get fixed (and the
program starts to actually launch properly) it's going to get much less
complex. Right now we're just adding issues without going anywhere.

My understanding is that your patch fixes the problem described in bug 57875, but your stack trace matches bug 68020. I will go ahead and correct the descriptions/duplicates to clarify the separate bugs, but could you confirm exactly which problem(s) you are experiences, as I do not experience bug 57875 myself:

Problem (crash?) on startup displaying splash screen, possibly stuck "Loading images"?
Crash after startup but only shortly after - you see the main Azureus window but only briefly (due to notification window trying to slide up, attempt workarounds as per bug 68020)?

Also, your patch is supposed to fix which? Or both? Or one and now you have the other problem?