Skip to content

Fix for biglybt not launching after update to version 4.0.0.0 #14

@AzaleeBleue

Description

@AzaleeBleue

Hi,

It's not an issue with this repo, but it can be useful to keep this small doc until a fixed biglybt release is available.

BiglyBT 4.0.0.0 has a bug where it may not launch when not using a clean profile.
It was my case when updating in my container, not sure if it's impacting everyone with an existing profile.

As said here: BiglySoftware/BiglyBT#3654 (comment), it's fixed in BiglyBT v4.0.0.1-beta02.

Here is how to replace the 4.0.0.0 jar with the fixed one in a running container.
You need to have an access to the shell in the container (through running a terminal in vnc, or docker container exec).

  1. Kill currently running biglybt process
    Change the process id in the kill command with the one given by running the first command.
$ ps -ef | grep bigly | grep java
root      4325  4202 99 15:26 ?        00:00:36 java -Xmx256m -cp ./BiglyBT.jar:./commons-cli.jar:swt/J17/swt-x86_64.jar -Djava.library.path=/opt/biglybt -Dazureus.install.path=/opt/biglybt -Dazureus.script=/opt/biglybt/biglybt -Dazureus.script.version=12 -Xmx2g --add-opens java.base/java.net=ALL-UNNAMED com.biglybt.ui.Main

$ kill -9 4325
  1. Download BiglyBT v4.0.0.1-beta02
    URL is from the biglybt issue linked previously.
$ cd ~

$ wget https://biglybt-files.s3.us-east-1.amazonaws.com/core/BiglyBT4001-B02-signed.jar

$ cp BiglyBT4001-B02-signed.jar /opt/biglybt/BiglyBT.jar
  1. Start biglybt
    From vnc because I don't know how to launch it from a docker container exec shell and having biglybt interface visible through vnc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions