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

[Bug] Vesktop fails to launch #675

Closed
3 tasks done
ISSOtm opened this issue Jun 19, 2024 · 5 comments
Closed
3 tasks done

[Bug] Vesktop fails to launch #675

ISSOtm opened this issue Jun 19, 2024 · 5 comments
Labels
duplicate This issue or pull request already exists

Comments

@ISSOtm
Copy link

ISSOtm commented Jun 19, 2024

Discord Account

No response

Operating System

Arch Linux

Linux Only ~ Desktop Environment

Sway

What happens when the bug or crash occurs?

Launching the application passes the "Loading Vesktop" foxgirl (:3), and then stays on a blank window.

Dev tools' console reports the following:

Uncaught TypeError: Cannot read properties of undefined (reading 'can')
    at Object.isHiddenChannel (index.tsx:485:33)
    at Object.resolveGuildChannels (index.tsx:501:61)
    at q.getChannels (WebpackModule984933:2:2732)
    at q.getFirstChannelOfType (WebpackModule984933:2:2885)
    at q.getFirstChannel (WebpackModule984933:2:3052)
    at q.getDefaultChannel (WebpackModule984933:2:3308)
    at x (25624.cfab532100605014a013.js:1:5951353)
    at j.getChannelId (25624.cfab532100605014a013.js:1:5953262)
    at 306680 (25624.cfab532100605014a013.js:1:5901737)
    at e.<computed> (patchWebpack.ts:197:17)

It's unclear if this is caused by a plugin (of note is a few "patch had no effect" warnings a little above). I'm not sure how to disable them outside of the GUI that is not launching... ><

Edit: I forgot to mention, but the bug did not happen until today. I restarted Vesktop normally after applying the last update a few days ago, so I'm not sure what changed.

What is the expected behaviour?

Vesktop launching as usual.

How do you recreate this bug or crash?

  1. Launch Vesktop
  2. Easy reproducer, for once!

Debug Logs

[97557:0619/193204.982694:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[97557:0619/193204.992890:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[97557:0619/193207.823066:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[97516:0619/193213.054639:ERROR:CONSOLE(1)] "Request Autofill.enable failed. {"code":-32601,"message":"'Autofill.enable' wasn't found"}", source: devtools://devtools/bundled/core/protocol_client/protocol_client.js (1)

I get these from the AppImage, but not the AUR package. The issue reproduces on both, though.

Request Agreement

  • I have searched the existing issues and found no similar issue
  • I am using the latest Vesktop and Vencord versions
  • This issue occurs on an official release (not just the AUR or Nix packages)
@ISSOtm ISSOtm added the bug Something isn't working label Jun 19, 2024
@ISSOtm ISSOtm changed the title [Bug] Vesktop fqils to lqunch [Bug] Vesktop fails to launch Jun 19, 2024
@Vendicated
Copy link
Member

#669

@Vendicated Vendicated closed this as not planned Won't fix, can't repro, duplicate, stale Jun 19, 2024
@Vendicated Vendicated added duplicate This issue or pull request already exists and removed bug Something isn't working labels Jun 19, 2024
@ISSOtm
Copy link
Author

ISSOtm commented Jun 19, 2024

Ah, I didn't check in the closed issues. My bad. Thank you for your time!

@ISSOtm
Copy link
Author

ISSOtm commented Jun 19, 2024

Unfortunately, the fix presented over there (I do not have a tray, so pasting Vencord.Updater.update()) does not fix the issue.

I get a Promise object, and awaiting that just returns true, but restarting Vesktop (again, no tray, so AFAICT no persisting processes) still yields the same. 😅

@ISSOtm
Copy link
Author

ISSOtm commented Jun 19, 2024

I fixed it by running Vesktop.Settings.store.tray = true in the DevTools Console, which immediately enables the tray. Then that can be right-clicked to "Update Vesktop", which did work!

cc @Vendicated if you want to add that to #669's post.

Thank you very much for working on this! ^^

@Wartori54
Copy link

Same happened to me, where Vencord.Update.update() just returned true instantly, but after manually running Vencord.Update.checkForUpdates() and then re-running Vencord.Update.update() it actually updated to latest and fixed itself.

All of this using vesktop-bin from the arch user repositories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants