-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beagle crashes on startup #133
Comments
I've reviewed the crash log and it looks like it may be caused by an issue with a MUC bookmark or handling of a bookmark in Beagle IM (synchronization). To confirm that, and as a workaround, I would suggest disabling any network connection, starting BeagleIM, and in Would you be able to review your bookmarks and check if there is any MUC room bookmark with autojoin enabled and with a room jid without localpart? (no room name/just domain name?) |
You nailed it, I had a bogus bookmark entry indeed (no @). It was caused by the component I develop and I definitely need to investigate how it happened. Removing the bogus bookmark from Conversations fixed the issue. I guess it would be nice if such entries didn't prevent Beagle from starting. |
Not sure when this happens, but apparently it can? References: tigase/beagle-im#133
Yes, the cause of the issue will be fixed in the future version of Beagle IM. I just wanted to give you a way to possibly fix it for now and to confirm if that was the actual cause of the issue. |
Discovered via tigase/beagle-im#133 Fixes: https://todo.sr.ht/~nicoco/slidge/157
Since a few days, I cannot useBeagleIM on my M1 macbook pro anymore.
The crash report is too long for a github comment, but you can read it on paste.sr.ht
The text was updated successfully, but these errors were encountered: