Urbit: Segfault when opening dojo UI in landscape

Created on 6 Dec 2019 · 10Comments · Source: urbit/urbit

Overview

Process segfaults and crashes after clicking to Dojo app in lanscape UI.

Trace

~hasser-habsyr:dojo> address 0x159 out of loom!
loom: [0x36000000 : 0xb6000000)
Assertion '0' failed in noun/events.c:129

bail: oops
bailing out
Assertion failed: 0 (noun/manage.c: u3m_bail: 667)
                                                  Segmentation fault (core dumped)
hen@hasser-habsyr:~/urbit$ ./urbit hasser-habsyr

Note

Upon reboot, the following was logged. Likely not related, but figured it may be.

---------------- playback starting----------------
pier: replaying events 62650 through 62827
..................................................................................................................................................................................
---------------- playback complete----------------
[%canceling-nonexistant-channel [i=//http-server/0v9.lpsrj/5/4 t=~]]
[%canceling-cancel [i=//http-server/0v9.lpsrj/8/3 t=~]]

Source

hrharder

Most helpful comment

deleted

joemfb on 6 Dec 2019

👍2 ❤1

All 10 comments

This is with https? Likely due to #2032.

philipcmonk on 6 Dec 2019

Apparently a known issue.

hrharder on 6 Dec 2019

Yes -- https, thank you.

hrharder on 6 Dec 2019

umm, you accidently included your +code

botter-nidnul on 6 Dec 2019

😄1

deleted

joemfb on 6 Dec 2019

👍2 ❤1

@botter-nidnul yes, i realized that all too late... (clearly a dumbass in the urbit world still)

thank you for deleting it @joemfb

On another note... after performing a self breach (w/ breach continuity) I'm unable to reconnect tot he network. Any ideas what my next steps should be?

hrharder on 6 Dec 2019

Can you please run +trouble in the dojo and send the results to
[email protected] ?
—
~poldec-tonteg
http://urbit.org

On Fri, Dec 6, 2019 at 10:47 AM Henry Harder notifications@github.com
wrote:

@botter-nidnul https://github.com/botter-nidnul yes, i realized that
all too late... (clearly a dumbass in the urbit world still)

thank you for deleting it @joemfb https://github.com/joemfb

On another note... after performing a self breach (w/ breach continuity)
I'm unable to reconnect tot he network. Any ideas what my next steps should
be?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/urbit/issues/2045?email_source=notifications&email_token=AAMJBY7HRYB3GC6Y2MF5LLTQXKM23A5CNFSM4JWHCNXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGE77GI#issuecomment-562691993,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMJBY24LFJ72672OWB32CLQXKM23ANCNFSM4JWHCNXA
.

vvisigoth on 6 Dec 2019

Thanks @vvisigoth, just sent an email with a gist.

hrharder on 6 Dec 2019

From urbit-help it looks like you're back online. Do you know what you did to make it work?

philipcmonk on 6 Dec 2019

No idea... All I remember doing is 1) restarting urbit 2) deleting pier
and re-running urbit -w [] -k [], 3) running |nuke (sponsor) and |nuke
(sponsor), so one of them likely fixed it.

Sorry I'm not sure which one. My gut is probably the delete pier and
rebuild step, but I'm sure you have a better insight here.

On Fri, Dec 6, 2019 at 11:43 AM Philip Monk notifications@github.com
wrote:

From urbit-help it looks like you're back online. Do you know what you did
to make it work?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/urbit/urbit/issues/2045?email_source=notifications&email_token=ABV4VM3AJRSD5BQJ6OZTWR3QXKTP3A5CNFSM4JWHCNXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGFEYFY#issuecomment-562711575,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABV4VM22R4G54A2GQDP5NNDQXKTP3ANCNFSM4JWHCNXA
.