LBRYCommunity/lbry-desktop

Fork 0

LBRY will not open on Mac OS. #219

New issue

Closed

opened 2017-06-09 21:30:58 +02:00 by rcanolty · 19 comments

rcanolty commented

2017-06-09 21:30:58 +02:00

(Migrated from github.com)

The Issue

LBRY will not open on Mac OS.

Steps to reproduce

Got email from LBRY at 14:51 EST, clicked on MAC OS button to download latest app.
Opened .dmg and dragged LBRY to Applications folder.
Message says "The daemon has unexpectedly shutdown. Goodbye."

Expected behaviour

should open

Actual behaviour

does not open

System Configuration

Version 0.11.9 (0.11.9.1072)

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

## The Issue LBRY will not open on Mac OS. ### Steps to reproduce 1. Got email from LBRY at 14:51 EST, clicked on MAC OS button to download latest app. 2. Opened .dmg and dragged LBRY to Applications folder. 3. Message says "The daemon has unexpectedly shutdown. Goodbye." ### Expected behaviour should open ### Actual behaviour does not open ## System Configuration  Version 0.11.9 (0.11.9.1072)  - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else  ## Screenshots

kauffj commented

2017-06-09 23:37:21 +02:00

(Migrated from github.com)

Can you:

Make sure no lbry processes are running
Run the application
Email ~/lbrynet/lbrynet.log to jeremy@lbry.io

Thanks!

Can you: 1. Make sure no lbry processes are running 1. Run the application 1. Email `~/lbrynet/lbrynet.log` to jeremy@lbry.io Thanks!

kauffj commented

2017-06-09 23:37:30 +02:00

(Migrated from github.com)

And sorry it didn't work! :(

tzarebczan commented

2017-06-14 03:28:03 +02:00

(Migrated from github.com)

@jackrobison - same issue as the guy on slack recently? db migration?

@rcanolty did you have lbry installed previously?

@jackrobison - same issue as the guy on slack recently? db migration? @rcanolty did you have lbry installed previously?

rcanolty commented

2017-06-14 16:28:01 +02:00

(Migrated from github.com)

i had lbry installed previously, when I put app in Applications folder, was asked if I wanted to replace old version, i said yes. i do not recall using lbry before, however (i may have just installed without opening).

Just downloaded and installed LBRY 0.12.0, same problem.

kauffj commented

2017-06-14 17:36:52 +02:00

(Migrated from github.com)

@rcanolty I definitely want to get to the bottom of this, can you send me the lbrynet.log file I mentioned via email to jeremy@lbry.io? It will be in a hidden .lbrynet folder in your home directory.

@rcanolty I definitely want to get to the bottom of this, can you send me the `lbrynet.log` file I mentioned via email to jeremy@lbry.io? It will be in a hidden `.lbrynet` folder in your home directory.

rcanolty commented

2017-06-14 17:42:06 +02:00

(Migrated from github.com)

I don't see this file. Terminal command "ls -a" shows me a hidden file .lbryum, but no .lbrynet.

jackrobison commented

2017-06-14 17:46:59 +02:00

(Migrated from github.com)

on os x the lbrynet data folder is ~/Library/Application Support/LBRY @kauffj

https://lbry.io/faq/lbry-directories

on os x the lbrynet data folder is `~/Library/Application Support/LBRY` @kauffj https://lbry.io/faq/lbry-directories

rcanolty commented

2017-06-14 18:01:15 +02:00

(Migrated from github.com)

Ah, got it. log file attached as text.
lbrynet.txt

Ah, got it. log file attached as text. [lbrynet.txt](https://github.com/lbryio/lbry-app/files/1075212/lbrynet.txt)

kauffj commented

2017-06-14 19:00:46 +02:00

(Migrated from github.com)

Looks like the issue is a failure for the claim_ids table to be created. We'll get this fixed.

Appreciate your help on this @rcanolty, if you send me or post a wallet address, happy to send you a tip.

(And if you can't get a wallet address until we fix this, you'll get a notification when this is closed.)

Looks like the issue is a failure for the `claim_ids` table to be created. We'll get this fixed. Appreciate your help on this @rcanolty, if you send me or post a wallet address, happy to send you a tip. (And if you can't get a wallet address until we fix this, you'll get a notification when this is closed.)

jackrobison commented

2017-06-14 19:07:41 +02:00

(Migrated from github.com)

to manually bypass this, delete blockchainname.db and db_revision in the lbrynet data folder

to manually bypass this, delete `blockchainname.db` and `db_revision` in the lbrynet data folder

jackrobison commented

2017-06-14 19:08:29 +02:00

(Migrated from github.com)

@rcanolty what was the very first version you installed, or around when did you initially install it?

rcanolty commented

2017-06-14 19:23:01 +02:00

(Migrated from github.com)

Not sure of first version number, but first email from LBRY was 2016 may 08.
Glad to help, I'd like to see this project succeed.

Not sure of first version number, but first email from LBRY was 2016 may 08. Glad to help, I'd like to see this project succeed.

kauffj commented

2017-06-16 01:30:14 +02:00

(Migrated from github.com)

While definitely a bug, this only affects a small number of old installs and may never get fixed.

Please contact help@lbry.io and reference this GitHub issue if you'd like assistance from our team in migrating and getting it running again.

While definitely a bug, this only affects a small number of old installs and may never get fixed. Please contact help@lbry.io and reference this GitHub issue if you'd like assistance from our team in migrating and getting it running again.

kauffj commented

2017-06-16 01:30:29 +02:00

(Migrated from github.com)

And sorry!

rcanolty commented

2017-12-04 00:24:22 +01:00

(Migrated from github.com)

If the LBRY tip offer still stands, here is my address: bVxY4EtVtakjxhJqjVLX
632RsaQVci7nLs

Looks like the project is doing well! Just joined the discord group.

Best,
Ryan

On Wed, Jun 14, 2017 at 1:00 PM, Jeremy Kauffman notifications@github.com
wrote:

Looks like the issue is a failure for the claim_ids table to be
corrected. We'll get this fixed.

Appreciate your help on this @rcanolty https://github.com/rcanolty, if
you send me or post a wallet address, happy to send you a tip.

(And if you can't get a wallet address until we fix this, you'll get a
notification when this is closed.)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/219#issuecomment-308494677,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMmFDrwm81wNUAL8HvbXdsdDzjzALBFqks5sEBHAgaJpZM4N1v2y
.

If the LBRY tip offer still stands, here is my address: bVxY4EtVtakjxhJqjVLX 632RsaQVci7nLs Looks like the project is doing well! Just joined the discord group. Best, Ryan On Wed, Jun 14, 2017 at 1:00 PM, Jeremy Kauffman <notifications@github.com> wrote: > Looks like the issue is a failure for the claim_ids table to be > corrected. We'll get this fixed. > > Appreciate your help on this @rcanolty <https://github.com/rcanolty>, if > you send me or post a wallet address, happy to send you a tip. > > (And if you can't get a wallet address until we fix this, you'll get a > notification when this is closed.) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-app/issues/219#issuecomment-308494677>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AMmFDrwm81wNUAL8HvbXdsdDzjzALBFqks5sEBHAgaJpZM4N1v2y> > . >

kauffj commented

2017-12-04 15:21:26 +01:00

(Migrated from github.com)

@rcanolty sent

rcanolty commented

2017-12-04 16:10:10 +01:00

(Migrated from github.com)

ah, sorry, I went with rtc as my channel name, so @rtc? i also just learned
about discord tipbot, if that is easier.

On Mon, Dec 4, 2017 at 9:21 AM, Jeremy Kauffman notifications@github.com
wrote:

@rcanolty https://github.com/rcanolty sent

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/219#issuecomment-348975430,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMmFDkVcC0r_xBPFbX2XEqXtM_bptlw3ks5s8__ogaJpZM4N1v2y
.

ah, sorry, I went with rtc as my channel name, so @rtc? i also just learned about discord tipbot, if that is easier. On Mon, Dec 4, 2017 at 9:21 AM, Jeremy Kauffman <notifications@github.com> wrote: > @rcanolty <https://github.com/rcanolty> sent > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-app/issues/219#issuecomment-348975430>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AMmFDkVcC0r_xBPFbX2XEqXtM_bptlw3ks5s8__ogaJpZM4N1v2y> > . >

tzarebczan commented

2017-12-04 16:11:11 +01:00

(Migrated from github.com)

Ah, welcome to our Discord... We had some interactions yesterday :)

rcanolty commented

2017-12-04 16:12:46 +01:00

(Migrated from github.com)

ah, just looked and it is there, so no worries. keep it up guys, this is
the project that got me into blockchain (better than cryptokitties.co !)

On Mon, Dec 4, 2017 at 10:11 AM, Thomas Zarebczan notifications@github.com
wrote:

Ah, welcome to our Discord... We had some interactions yesterday :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/219#issuecomment-348990439,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMmFDic_LdOp7rVL32VF5bhN1JU-bJWPks5s9AuSgaJpZM4N1v2y
.

ah, just looked and it is there, so no worries. keep it up guys, this is the project that got me into blockchain (better than cryptokitties.co !) On Mon, Dec 4, 2017 at 10:11 AM, Thomas Zarebczan <notifications@github.com> wrote: > Ah, welcome to our Discord... We had some interactions yesterday :) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-app/issues/219#issuecomment-348990439>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AMmFDic_LdOp7rVL32VF5bhN1JU-bJWPks5s9AuSgaJpZM4N1v2y> > . >