Describe the bug
MediaElch crashes upon searching for movie details
To Reproduce
Steps to reproduce the behavior:
Nov 25 13:31:53 mycomputer kernel: MediaElch[1121587]: segfault at 129 ip 00007f22bd28fd57 sp 00007ffefd871e90 error 4 in libQt5Widgets.so.5.15.1[7f22bd259000+3b0000]
Nov 25 13:31:53 mycomputer kernel: audit: type=1701 audit(1606307513.678:818): auid=2107 uid=2107 gid=2020 ses=1 pid=1121587 comm="MediaElch" exe="/usr/bin/MediaElch" sig=11 res=1
Nov 25 13:31:54 mycomputer systemd[1905]: app-gnome-MediaElch-1121587.scope: Succeeded.
Nov 25 13:31:54 mycomputer systemd-coredump[1123372]: Process 1121587 (MediaElch) of user 2107 dumped core.
#16 0x000055f84f6d2dc2 main (MediaElch + 0xa7dc2)
#18 0x000055f84f6d3c2e n/a (MediaElch + 0xa8c2e)
Expected behavior
No Crash
MediaElch Version:
Operating System:
Additional context
This is a fresh install of Manjaro/Arch.
Looks like this issue is similar to #1050 - could be duplicate.
Thanks for reporting. Yes, there are multiple duplicates of this issue. I'm setting up a VM with Manjaro to test this our right now. :-)
Can't reproduce it yet in a virtual machine with Manjaro KDE desktop. Which desktop environment are you using? :-)
And how many CPUs/Cores does your machine have?
I was able to reproduce this on Manjaro with XFCE :tada: :disappointed:
Hello
Thank you for the follow up. My DE is Gnome.
My CPU is a single Intel 8700k, it has 6 cores, 12 threads.
**gnome-shell --version**
GNOME Shell 3.38.1
**uname -a**
Linux server 5.9.11-3-MANJARO #1 SMP PREEMPT Sat Nov 28 09:08:57 UTC 2020 x86_64 GNU/Linux
**cat /proc/cpuinfo**
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
stepping : 10
microcode : 0xde
cpu MHz : 1114.608
cache size : 12288 KB
Hi,
I just wanted to inform you that I was able to reproduce this issue on Manjaro XFCE and that the bug will be fixed by #1078.
Turns out that this bug only happened with Kvantum installed which is why I wasn't able to reproduce this bug (I used Manjaro KDE for testing before...).
Regards,
Andre
If this issue wasn't fixed for you, please let me know.