SpacingBat3 / WebCord

A Discord and SpaceBar :electron:-based client implemented without Discord API.
MIT License
1.89k stars 94 forks source link

Webcord won't start. Floss manager not present, cannot set Floss enable/disable. #366

Closed IgnIVertiKalCaD closed 1 year ago

IgnIVertiKalCaD commented 1 year ago

Aknowledgements

Operating System / Platform

🐧️ Linux Fedora 37

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

last

Application version

v4.1.1, development build

Bug description

out/devel/WebCord-linux-x64/webcord --verbose [OPTIMIZE] Applying flag: --enable-features=WebRTCPipeWireCapturer... [FEATURE] Disabling 'MediaSessionService'... [FEATURE] Disabling 'HardwareMediaKeyHandling'... [OPTIMIZE] Applying flag: --use-gl=egl... [OPTIMIZE] Applying flag: --enable-features=WebRTCPipeWireCapturer,VaapiVideoDecoder,VaapiVideoEncoder... [OPTIMIZE] Applying flag: --disable-features=UseChromeOSDirectVideoDecoder... Switching to the existing window... [L10N] Computing strings for locale list: en-US, en_US, en, US, EN-US, en-us [L10N] Computing strings for locale list: en-US, en_US, en, US, EN-US, en-us [L10N] Computing strings for locale list: en-US, en_US, en, US, EN-US, en-us [19001:0116/031613.977394:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.

Additional context

Wayland GPU - AMD RX 6700XT. OpenCL, OpenGL - open driver all The error appeared after restarting the computer. Normal discord works. WebCord dev/build - dont works

IgnIVertiKalCaD commented 1 year ago

rm -rf ~/.config/WebCord

This is fix

IgnIVertiKalCaD commented 1 year ago

problem returned after reboot

xharris commented 1 year ago

For me, the issue was an empty ~/.config/WebCord/windowState when the file is decoded here: https://github.com/SpacingBat3/WebCord/blob/9d291fe04aeb081cf617f1aea6c72f94b7fe7ae9/sources/code/main/modules/config.ts#L163 On my machine, I changed it to

    if (!decodedData.trim().length)
      return {}
    return JSON.parse(decodedData);

in /usr/lib/webcord/app/code/main/modules/config.js as a temporary fix.

7oxicshadow commented 1 year ago

I can confirm @xharris results.

The config.js does not exist on my machine but simply deleting the corrupted windowState file gets Webcord running again.

I suspect this is caused by the application not closing down properly when you shutdown the machine (as it goes to tray). In an attempt to prove this I disabled the following configuration option

"Hide Window to tray with close button"

Now after each restart Webcord seems to be reliable again (at least for me)