search

voltapp / volt

300 KB desktop client for Slack, Skype, Twitter, Telegram, and more
608 stars 8 forks source link

Volt not starting on Archlinux #147

Open hideraimu opened 5 years ago

hideraimu commented 5 years ago

When I execute volt in the terminal it outputs: volt: /build/glfw/sec/glfw-3.2.1/src/window.c:774: glfwSetWindowUserPointer: Assertion window !=NULL' failed.

Aborted (core dumped)

Executing the downloaded volt executable in my file manager also doesn't do anything.

hideraimu commented 5 years ago

EDIT: After some research it seems that this happens because the application requires OpenGL 3.2.1 but my machine has version 2.1. Is there a workaround to this or can the developer downgrade the OpenGL requirement?

sispus commented 5 years ago

+1 Manjaro xfce, chose to install either glfw-x11 or glfw-wayland, errors occurred when try to start volt from terminal. for x11: volt: /build/glfw/src/glfw-3.2.1/src/window.c:774: glfwSetWindowUserPointer: Assertionwindow != NULL' failed. ` for wayland, error message is similar.

Manually installing either glfw-x11-git or glfw-wayland-git, and start, it gives: exiting from os.exit(): Failed to initialize glad OpenGL context

badosu commented 5 years ago

Same thing here, however no output is sent, it initializes a window then simply segfaults.

Manjaro-i3, glfw-x11-3.2.1, OpenGL version string: 4.6.0 NVIDIA 418.43

albakham commented 5 years ago

Same problem on Archlinux with glfw-x11 package :

Volt starts and crashes in one second, the output is only :

exiting from os.exit():

KlausEverWalkingDev commented 5 years ago

Same error appearing on Manjaro KDE 18.0.4 64-bit. Probably the same bug that's mentioned and fixed here.

cutzenfriend commented 5 years ago

Same issue here! Arch (Manjaro 18.x KDE). glfw-x11 package : Volt starts and crashes in one second, the output is only: exiting from os.exit():

sispus commented 5 years ago

For volt 0.80.4 and glfw 3.3 it still gives the same output.

hideraimu commented 5 years ago

Same error appearing on Manjaro KDE 18.0.4 64-bit. Probably the same bug that's mentioned and fixed here.

But that 'bug' was from more than a year ago and it's claimed to be fixed. I and I assume other posters here too have latest versions which still have this problem.

@medvednikov Any update on this thread's issue?

andrelaszlo commented 5 years ago

After installing glfw-x11 on arch, I also have a window initializing for a second and then a segfault. I do get the output (once):

initial setup...
done!

strace (end):

rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb4ce03bd00}, NULL, 8) = 0
rt_sigaction(SIGPIPE, NULL, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb4ce03bd00}, 8) = 0
rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb4ce03bd00}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb4ce03bd00}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb4ce03bd00}, NULL, 8) = 0
openat(AT_FDCWD, "/home/andre/.voltapp/chats", O_RDONLY) = -1 ENOENT (No such file or directory)
clone(child_stack=0x7fb4c5501fb0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x7fb4c55029d0, tls=0x7fb4c5502700, child_tidptr=0x7fb4c55029d0) = 27378
access("/home/andre/.voltapp/chats", F_OK) = -1 ENOENT (No such file or directory)
recvmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\34\0\244\0\7\0\200\2\275\1\0\0\305\3\352\34\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 296
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
memfd_create("xshmfence", MFD_CLOEXEC|MFD_ALLOW_SEALING) = 10
ftruncate(10, 4)                        = 0
mmap(NULL, 4, PROT_READ|PROT_WRITE, MAP_SHARED, 10, 0) = 0x7fb4c4d01000
futex(0x7fb4cde60aa0, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x7fb4cde60aa0, FUTEX_WAKE_PRIVATE, 1) = ?
+++ killed by SIGSEGV (core dumped) +++

gdb:

Thread 7 "volt" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe9eae700 (LWP 26925)]
0x000000000043da8a in os.read_file ()

I saw that it was missing the .voltapp/chats directory, but creating it didn't help.

yshym commented 4 years ago

5.3.6-arch same issue exiting from os.exit():

Mayurifag commented 4 years ago

same with exiting from os.exit():

gigch commented 3 years ago

Manjaro 20.2:

initial setup...
done!
exiting from os.exit():