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

Webcord v4.4.3 crashes on startup #475

Closed
2 of 7 tasks
RiQuY opened this issue Oct 12, 2023 · 7 comments
Closed
2 of 7 tasks

Webcord v4.4.3 crashes on startup #475

RiQuY opened this issue Oct 12, 2023 · 7 comments
Assignees
Labels
info:Wayland Issues specific to Wayland, likely caused by lack of support by Electron / Chromium. status:invalid This doesn't seem right type:bug Something isn't working

Comments

@RiQuY
Copy link

RiQuY commented Oct 12, 2023

Acknowledgements

  • I have checked that there is no other issue describing the same or
    similar problem that I currently have, regardless if it has been
    closed or open.

  • This bug affects Discord website.

  • This issue is confirmed to be reproducible when WebCord is packaged
    on at least all three latest supported Electron major releases.

  • This issue is reproducible in Chrome, Chromium or any
    Chromium-based browser, e.g Brave or Edge (please write in
    Additional Context which browser you have used if it is neither
    Chrome nor unmodified Chromium).

  • There are no fixes done to master which resolves this issue.

  • My issue describes one of the unstable and/or not fully implemented
    features.

  • I have found a workaround to mitigate or temporarily fix this issue
    in affected releases (please write it in Additional context section
    below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

Unknown - The app doesn't start

Application version

v4.4.3

Bug description

Webcord crashes upon opening, it doesn't open any windows, the program shows up in the taskbark and then closes.

Additional context

OS: openSUSE Tumbleweed x86_64
Kernel: 6.5.6-1-default
DE: Plasma 5.27.8
WM: kwin
Wayland

Webcord was installed through flatpak, I tried to search for logs to attach but I haven't found any folder with them.

To at least get some output I tried to start the program through the terminal with the following command and this the output.
flatpak run io.github.spacingbat3.webcord

[10 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[10 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[10 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[15 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[15 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[15 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[20 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[20 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[20 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[25 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[25 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[25 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[30 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[30 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[30 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[35 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[35 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[35 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[40 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[40 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[40 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[45 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[45 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[45 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[52 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[55 zypak-helper] Using spawn strategy test 1 as set by environment
[55:1012/194528.740500:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No existe el fichero o el directorio
xargs: zypak-wrapper: terminado por la señal 11
[3 preload-host-spawn-strategy] Warning: waitpid override ignores groups

The following output is from dmesg command:
dmesg

[   39.852580] show_signal_msg: 50 callbacks suppressed
[   39.852583] webcord[4131]: segfault at 1010101 ip 0000563dceb92ed5 sp 00007ffeec882e10 error 4 in webcord[563dcb393000+79cb000] likely on CPU 1 (core 1, socket 0)
[   39.852595] Code: 0f 86 c1 00 00 00 4c 89 e2 4d 39 ec 72 08 4c 89 e0 31 d2 49 f7 f5 48 8b 01 48 8b 04 d0 48 85 c0 0f 84 97 00 00 00 48 89 5d d0 <48> 8b 18 48 85 db 0f 84 8c 00 00 00 48 89 55 c8 49 8d 45 ff 48 89
[  348.809800] webcord[5684]: segfault at 1010101 ip 000056389a5d1ed5 sp 00007fff527a2140 error 4 in webcord[563896dd2000+79cb000] likely on CPU 5 (core 5, socket 0)
[  348.809818] Code: 0f 86 c1 00 00 00 4c 89 e2 4d 39 ec 72 08 4c 89 e0 31 d2 49 f7 f5 48 8b 01 48 8b 04 d0 48 85 c0 0f 84 97 00 00 00 48 89 5d d0 <48> 8b 18 48 85 db 0f 84 8c 00 00 00 48 89 55 c8 49 8d 45 ff 48 89
[  372.821906] webcord[5901]: segfault at 1010101 ip 0000557504efeed5 sp 00007ffcce2f4bd0 error 4 in webcord[5575016ff000+79cb000] likely on CPU 6 (core 6, socket 0)
[  372.821922] Code: 0f 86 c1 00 00 00 4c 89 e2 4d 39 ec 72 08 4c 89 e0 31 d2 49 f7 f5 48 8b 01 48 8b 04 d0 48 85 c0 0f 84 97 00 00 00 48 89 5d d0 <48> 8b 18 48 85 db 0f 84 8c 00 00 00 48 89 55 c8 49 8d 45 ff 48 89
[  710.777334] BTRFS info (device nvme0n1p3): qgroup scan paused
[ 1163.339669] webcord[11025]: segfault at 1010101 ip 0000558e57acded5 sp 00007fff3c2eb810 error 4 in webcord[558e542ce000+79cb000] likely on CPU 0 (core 0, socket 0)
[ 1163.339684] Code: 0f 86 c1 00 00 00 4c 89 e2 4d 39 ec 72 08 4c 89 e0 31 d2 49 f7 f5 48 8b 01 48 8b 04 d0 48 85 c0 0f 84 97 00 00 00 48 89 5d d0 <48> 8b 18 48 85 db 0f 84 8c 00 00 00 48 89 55 c8 49 8d 45 ff 48 89
@RiQuY RiQuY added the type:bug Something isn't working label Oct 12, 2023
@SpacingBat3
Copy link
Owner

What's with any of official builds (e.g. AppImages)?

I'll probably update Electron soon and release new version (most likely this weekend), so chances are this issue will be resolved/stalled anyway if it won't be confirmed to happen with the newer Electron versions (27.x.y).

@SpacingBat3 SpacingBat3 added the status:need-info Further information is requested label Oct 12, 2023
@RiQuY
Copy link
Author

RiQuY commented Oct 12, 2023

Is not an AppImage I installed it through Flathub https://flathub.org/apps/io.github.spacingbat3.webcord

@SpacingBat3
Copy link
Owner

SpacingBat3 commented Oct 12, 2023

@RiQuY I know, but could you check any different builds, maybe RPMs (if those are native package format for openSUSE) or AppImages? I don't really support Flatpaks right now, this is mostly due to its oddities with sandboxing (in fact, you should get a warning on that when creating a bug report). Also I don't manage Flatpaks, so without giving me the Electron version, I feel like I'm unable to help you.

@RiQuY
Copy link
Author

RiQuY commented Oct 12, 2023

AppImage build starts and let me login succesfully.

When I tried to install the rpm build I get this error in the package manager:

Error: INVALID:webcord-4.4.3-1.x86_64 (file-e308d1de): Error de verificación de firma [6-El fichero no está firmado]
    Header SHA256 digest: OK
    Header SHA1 digest: OK
    Payload SHA256 digest: OK
    MD5 digest: OK
    ¡Cabecera del paquete sin firmar!

@RiQuY
Copy link
Author

RiQuY commented Oct 12, 2023

Weirdly enough, the Flatpak version uses the AppImage internally which can you check here. https://github.com/flathub/io.github.spacingbat3.webcord/blob/master/io.github.spacingbat3.webcord.yml

I can only find the runtime version of the flatpak repo, no mention of the Electron version.

Should I then open an issue in the Flatpak repo?

@SpacingBat3
Copy link
Owner

SpacingBat3 commented Oct 12, 2023

AppImage build starts and let me login succesfully.

When I tried to install the rpm build I get this error in the package manager:

Error: INVALID:webcord-4.4.3-1.x86_64 (file-e308d1de): Error de verificación de firma [6-El fichero no está firmado]
    Header SHA256 digest: OK
    Header SHA1 digest: OK
    Payload SHA256 digest: OK
    MD5 digest: OK
    ¡Cabecera del paquete sin firmar!

@RiQuY TBH I have no clue which distros RPM covers and someone has already suggested some RPMs might not work if these are made for Flapaksedora or Red Hat Linux. Also English logs would be appreciated for the next time (LANG=C).

Should I then open an issue in the Flatpak repo?

@RiQuY I suppose yes, it sounds like this could be an issue associated to Flatpak in some way. Also AppImages are unsandboxed, which could explain this works and Flatpak builds are broken.

Also as it seems official builds work fine, I'll close this issue.

@SpacingBat3 SpacingBat3 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2023
@SpacingBat3 SpacingBat3 added status:invalid This doesn't seem right and removed status:need-info Further information is requested labels Oct 12, 2023
@RiQuY
Copy link
Author

RiQuY commented Oct 12, 2023

@RiQuY TBH I have no clue which distros RPM covers and someone has already suggested some RPMs might not work if these are made for Flapaks or Red Hat Linux. Also English logs would be appreciated for the next time (LANG=C).

OpenSUSE uses RPM packages like Fedora, I suggest taking a look at the error when installing the RPM package because it is an issue with the official build not Flatpak.

As you suggested I'll open an issue in the Flatpak repo for the main issue.

Thanks.

@SpacingBat3 SpacingBat3 added the info:Wayland Issues specific to Wayland, likely caused by lack of support by Electron / Chromium. label Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info:Wayland Issues specific to Wayland, likely caused by lack of support by Electron / Chromium. status:invalid This doesn't seem right type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants