Bug 235751 - Splash screen stays open
Splash screen stays open
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: azureus (Show other bugs)
6
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Anthony Green
Fedora Extras Quality Assurance
:
: 236191 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-09 18:35 EDT by Peter faric
Modified: 2008-01-15 18:04 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-12-03 12:07:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter faric 2007-04-09 18:35:35 EDT
Description of problem:
After starting Azureus (2.5.0.4) with the "show splash screen" set to ON the
splash screen stays open indefinitely at the "Opening views" stage even though
the program's main screen is up and running. 

Version-Release number of selected component (if applicable):
2.5.0.4

How reproducible:
Always

Steps to Reproduce:
1. yum update azureus
2. azureus
3.
  
Actual results:
Splash screen stays open indefinitely.

Expected results:
Splash screen closes after main screen shows up.

Additional info:
Comment 1 David Juran 2007-04-17 02:13:11 EDT
*** Bug 236191 has been marked as a duplicate of this bug. ***
Comment 2 Paul Jenner 2007-04-29 09:59:07 EDT
Following exception is logged to console:

DEBUG::Sun Apr 29 13:48:45 GMT
2007::com.aelitis.azureus.core.impl.AzureusCoreImpl$8::runSupport::-1:
  java.lang.NullPointerException
   at org.gudy.azureus2.ui.swt.updater2.SWTUpdateChecker.initialize(Azureus2.jar.so)
   at org.gudy.azureus2.ui.swt.mainwindow.Initializer$4.started(Azureus2.jar.so)
   at com.aelitis.azureus.core.impl.AzureusCoreImpl$8.runSupport(Azureus2.jar.so)
   at org.gudy.azureus2.core3.util.AEThread.run(Azureus2.jar.so)
Comment 3 Paul Jenner 2007-04-29 10:02:22 EDT
Running with another VM (JamVM) to get line numbers:

DEBUG::Sun Apr 29 15:01:05 British Summer Time
2007::com.aelitis.azureus.core.impl.AzureusCoreImpl$8::runSupport::512:
  java.lang.NullPointerException
   at
org.gudy.azureus2.ui.swt.updater2.SWTUpdateChecker.initialize(SWTUpdateChecker.java:67)
   at
org.gudy.azureus2.ui.swt.mainwindow.Initializer$4.started(Initializer.java:258)
   at
com.aelitis.azureus.core.impl.AzureusCoreImpl$8.runSupport(AzureusCoreImpl.java:508)
   at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69)
Comment 4 Paul Jenner 2007-05-11 15:15:28 EDT
Reproduced using OpenJDK so this is an Azureus (package) issue and not VM issue.
Comment 5 Anthony Green 2007-05-11 15:40:42 EDT
Upstream says this is a bug in SWT, and they've fixed it in the SWT they bundle
with Azureus.  We use the Eclipse SWT, so we don't have the patch.  I don't know
what the fix is yet.
Comment 6 Jonathan Steffan 2007-06-02 01:15:31 EDT
I'll confirm this.
Comment 7 drago01 2007-06-02 01:28:00 EDT
(In reply to comment #5)
> Upstream says this is a bug in SWT, and they've fixed it in the SWT they bundle
> with Azureus.  We use the Eclipse SWT, so we don't have the patch.  I don't know
> what the fix is yet.

what about ccing the eclipse maintainer(s) ?
Comment 8 Chris Spencer 2007-06-17 00:32:03 EDT
I've confirmed this problem exists for F7 as well, using either GCJ or Sun Java.
Comment 9 Julian Sikorski 2007-09-13 17:16:50 EDT
IcedTea does not help either.
Comment 10 Julian Sikorski 2007-09-13 17:28:36 EDT
CCing the eclipse maintainer.
Comment 11 Andrew Overholt 2007-09-13 17:36:35 EDT
Can we get the actual SWT patch?  How about an eclipse.org bug #?
Comment 12 Lillian Angel 2007-12-03 12:07:40 EST
Updated to azureus-3.0.3.4-1.fc9. 
Should be available tomorrow in rawhide.
Comment 13 Fedora Update System 2008-01-15 18:04:39 EST
azureus-3.0.3.4-2.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.