diamondburned / gtkcord3

A Gtk3 Discord client in Golang
GNU General Public License v3.0
628 stars 28 forks source link

ArchLinux support? #87

Closed NTBBloodbath closed 4 years ago

NTBBloodbath commented 4 years ago

I have installed in ArchLinux (using the grkcord3-git AUR package) and it was installed without troubles but when I tried to launch I got this error (I already have all the dependencies installed). It's due to compatibility or another thing?

Thanks in advance!

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x642e6716a4]

goroutine 1 [running]:
github.com/diamondburned/gtkcord3/gtkcord/gtkutils/gdbus.(*Connection).SignalSubscribe(0x0, 0x0, 0x0, 0x642e7b4404, 0x1d, 0x0, 0x0, 0x642e7b4d49, 0x1e, 0x0, ...)
    github.com/diamondburned/gtkcord3/gtkcord/gtkutils/gdbus/gdbus.go:185 +0xec
github.com/diamondburned/gtkcord3/gtkcord/gtkutils/gdbus.NewNotifier(0x0, 0x0)
    github.com/diamondburned/gtkcord3/gtkcord/gtkutils/gdbus/notify.go:28 +0xec
github.com/diamondburned/gtkcord3/gtkcord.(*Application).Activate(0x4000492000)
    github.com/diamondburned/gtkcord3/gtkcord/gtkcord.go:128 +0x40
main.main.func1()
    github.com/diamondburned/gtkcord3/main.go:112 +0x2c
reflect.Value.call(0x642ea81660, 0x4000468180, 0x13, 0x642e75b9c7, 0x4, 0x642faf9dd8, 0x0, 0x0, 0x400081f9b8, 0x642dd9e7ec, ...)
    reflect/value.go:460 +0x658
reflect.Value.Call(0x642ea81660, 0x4000468180, 0x13, 0x642faf9dd8, 0x0, 0x0, 0x7d1cab6f21, 0xffffffffffffffff, 0x400081fa20)
    reflect/value.go:321 +0x84
github.com/gotk3/gotk3/glib.goMarshal(0x646637af40, 0x0, 0x4000000001, 0x7ff12e1fb0, 0x7ff12e1f78, 0x0)
    github.com/gotk3/gotk3@v0.4.1-0.20200610045216-1bfadb2ac3e6/glib/glib.go:255 +0x5f0
github.com/gotk3/gotk3/glib._cgoexpwrap_3a432a83c3cf_goMarshal(0x646637af40, 0x0, 0x7d00000001, 0x7ff12e1fb0, 0x7ff12e1f78, 0x0)
    _cgo_gotypes.go:5500 +0x50
github.com/gotk3/gotk3/glib._Cfunc_g_application_run(0x64663780f0, 0x6400000001, 0x6466376c70, 0x0)
    _cgo_gotypes.go:1425 +0x44
github.com/gotk3/gotk3/glib.(*Application).Run.func4(0x400068d950, 0x4000110190, 0x1, 0x1, 0x6466376c70, 0x6466376c70)
    github.com/gotk3/gotk3@v0.4.1-0.20200610045216-1bfadb2ac3e6/glib/application.go:185 +0x7c
github.com/gotk3/gotk3/glib.(*Application).Run(0x400068d950, 0x4000110190, 0x1, 0x1, 0x0)
    github.com/gotk3/gotk3@v0.4.1-0.20200610045216-1bfadb2ac3e6/glib/application.go:185 +0x11c
main.main()
    github.com/diamondburned/gtkcord3/main.go:140 +0x208

goroutine 5 [chan receive, locked to thread]:
github.com/diamondburned/gtkcord3/gtkcord/semaphore.init.0.func1()
    github.com/diamondburned/gtkcord3/gtkcord/semaphore/semaphore.go:33 +0x68
created by github.com/diamondburned/gtkcord3/gtkcord/semaphore.init.0
    github.com/diamondburned/gtkcord3/gtkcord/semaphore/semaphore.go:30 +0x30

goroutine 13 [chan receive]:
github.com/diamondburned/gtkcord3/gtkcord/components/message/completer.init.0.func1()
    github.com/diamondburned/gtkcord3/gtkcord/components/message/completer/completer.go:26 +0x58
created by github.com/diamondburned/gtkcord3/gtkcord/components/message/completer.init.0
    github.com/diamondburned/gtkcord3/gtkcord/components/message/completer/completer.go:25 +0x68

goroutine 66 [trace reader (blocked)]:
runtime.goparkunlock(...)
    runtime/proc.go:310
runtime.ReadTrace(0x400011c310, 0x400011ad30, 0x10)
    runtime/trace.go:395 +0x3f4
runtime/trace.Start.func1(0x642ec99500, 0x400011c310)
    runtime/trace/trace.go:129 +0x44
created by runtime/trace.Start
    runtime/trace/trace.go:127 +0xd4

goroutine 67 [chan receive]:
main.main.func3()
    github.com/diamondburned/gtkcord3/main.go:135 +0x68
created by main.main
    github.com/diamondburned/gtkcord3/main.go:134 +0x1dc
daniel071 commented 4 years ago

I'm unable to reproduce this issue. I installed the gtkcord3-git package and it worked fine for me. Have you tried to re-build it? Are you using any AUR helper?

Titaniumtown commented 4 years ago

Can't reproduce this issue either. Works fine for me.

Titaniumtown commented 4 years ago

This issue should prob be closed.