Skip to content
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

Can't launch uTox (0.16.1-1) after update #1016

Closed
Snake883 opened this issue Aug 26, 2017 · 5 comments
Closed

Can't launch uTox (0.16.1-1) after update #1016

Snake883 opened this issue Aug 26, 2017 · 5 comments

Comments

@Snake883
Copy link

Updated to a nightly build, and can no long launch uTox.
No errors.
Nothing in Task Manager.
Maybe something to do with "AddressSanitizer" (guessing)?

utox (0.16.1-1) over (0.16.0-1)
ubuntu 17.04

@GrayHatter
Copy link
Member

utox -vvvvvv in a terminal

@Snake883
Copy link
Author

Snake883 commented Aug 27, 2017

$ utox -vvvvvv
XLIB MAIN: Setting theme to: 5
uToxAv: Toxav thread init
GTK: Failed loading: libgtk-3.so. Falling back to libgtk-3.so.0
GTK: have GTK
==14715==AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_interceptors.cc:364 "((__interception::real___cxa_throw)) != (0)" (0x0, 0x0)
#0 0x7f09c7acc80a (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xd080a)
#1 0x7f09c7ad31d3 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xd71d3)
#2 0x7f09c7a2d93c in __interceptor___cxa_throw (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x3193c)
#3 0x7f09bb2d17a5 (/usr/lib/x86_64-linux-gnu/libmirclient.so.9+0x757a5)
#4 0x7f09bb2d48fe (/usr/lib/x86_64-linux-gnu/libmirclient.so.9+0x788fe)
#5 0x7f09bb292a6f (/usr/lib/x86_64-linux-gnu/libmirclient.so.9+0x36a6f)
#6 0x7f09bb29cb08 in mir::client::DefaultConnectionConfiguration::the_rpc_channel() (/usr/lib/x86_64-linux-gnu/libmirclient.so.9+0x40b08)
#7 0x7f09bb28d1a8 in mir_connect (/usr/lib/x86_64-linux-gnu/libmirclient.so.9+0x311a8)
#8 0x7f09bb28e4da in mir_connect_sync (/usr/lib/x86_64-linux-gnu/libmirclient.so.9+0x324da)
#9 0x7f09bec2dff6 (/usr/lib/x86_64-linux-gnu/libgdk-3.so.0+0xa4ff6)
#10 0x7f09bebc3234 in gdk_display_manager_open_display (/usr/lib/x86_64-linux-gnu/libgdk-3.so.0+0x3a234)
#11 0x7f09bf0c2e19 in gtk_init_check (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x22de19)
#12 0x7f09bf0c2e48 in gtk_init (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x22de48)
#13 0x5569fff97098 in ugtk_load (/usr/bin/utox+0xd1098)
#14 0x5569fff313d7 in main (/usr/bin/utox+0x6b3d7)
#15 0x7f09c76553f0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x203f0)
#16 0x5569fff32669 in _start (/usr/bin/utox+0x6c669)

@redmanmale
Copy link
Contributor

Same error log in #940.

@Snake883
Copy link
Author

Is there something easy I can do to help?

@redmanmale
Copy link
Contributor

Let's say there's Ubuntu 18.04 LTS and uTox 0.17.0
They are working together just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants