[Bug] App just not opening

[mazeymoos0022]

Discord Account

mazeymoos0022

Operating System

Windows 11

Linux Only ~ Desktop Environment

No response

Package Type

Setup EXE (Installer)

What happens when the bug or crash occurs?

Title explains it all, I click the app, not opening. Just get this white box. Using version 1.5.4 (latest). Tried reinstalling and also restarting my machine... Still no luck. Been working fine on v1.5.3

What is the expected behaviour?

Vesktop/Discord should open

How do you recreate this bug or crash?

1. Open the app... That's all I did...

Debug Logs

Replace this text with your crash-log. Do not remove the backticks

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)

[x8c8r]

Seconded

[Vendicated]

please provide logs

[x8c8r]

please provide logs

are you gonna tell us where to find them? i cant find any info on where they are stored and for obvious reasons i cant check the console.

[kamild1996]

I just had this issue after restarting my PC from a crash. The only logs I could find were in %appdata%/vesktop/sessionData/Session Storage. The 000003.log file contained this:

namespace-�©&f ��           

And the LOG file contained this:

2024/12/31-11:28:57.897 2134 Reusing MANIFEST C:\Users\Kamil\AppData\Roaming\vesktop\sessionData\Session Storage/MANIFEST-000001

That's it. I renamed the "vesktop" folder to "_vesktop", relaunched Vesktop, reconfigured it and it works fine now. But it would be nice to know if there's a better way to deal with this.

[mazeymoos0022]

please provide logs

Just adding my file from C:\Users\MIKI\AppData\Roaming\vesktop\sessionData\Session Storage (Windows 11)
000004.log

For other logs, can you please verify the location of where these are stored? I can find them, I just need to know where they are saved to. Also to add I have Vencord on the canary branch of Discord if this is somehow interfearing. (extra info, might not be needed but may be useful, idk)

[Vendicated]

you get logs by running vesktop from the command like

[x8c8r]

you get logs by running vesktop from the command like

here is my log

Failed to parse Vesktop state.json: SyntaxError: Unexpected token '', ""... is not valid JSON
    at JSON.parse (<anonymous>)
    at Vr (VCDMain:1:2605)
    at VCDMain:1:3398
    at VCDMain:1:225
    at VCDMain:1:4559
    at VCDMain:1:225
    at Object.<anonymous> (VCDMain:87:331)
    at Module._compile (node:internal/modules/cjs/loader:1484:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1564:10)
    at Module.load (node:internal/modules/cjs/loader:1295:32)
Checking for update
Update for version 1.5.4 is not available (latest version: 1.5.4, downgrade is disallowed).
checkForUpdatesAndNotify called, downloadPromise is null

[Vendicated]

delete state.json from your vesktop folder (in %APPDATA%, ~/.config or Application Support)

[x8c8r]

delete state.json from your vesktop folder (in %APPDATA%, ~/.config or Application Support)

the error is gone, but the app is still just a white square. left it open for like 30 min nothing happened. the log just talks about the update, same thing as last time.

[Covkie]

Can someone who is experiencing this try to build and run with either frame: true removed or add transparent: false

Vesktop/src/main/firstLaunch.ts

Lines 29 to 36 in 6c4ecc0

	const win = new BrowserWindow({
	...SplashProps,
	frame: true,
	autoHideMenuBar: true,
	height: 470,
	width: 550,
	icon: ICON_PATH
	});

[ViliusP]

I am using cosmic-os (wayland). I tried either to remove frame: true or to add transparent: false, but it doesn't change situation. After playing for about an hour, I managed to make it render.

After running pnpm start, I got:

APPIMAGE env is not defined, current application is not an AppImage
checkForUpdatesAndNotify called, downloadPromise is null
(node:61852) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/home/viliusp/.config/vesktop/settings/quickCss.css'
    at async open (node:internal/fs/promises:639:25)
(Use `electron --trace-warnings ...` to show where the warning was created)
(node:61852) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

{
  discordBranch: 'stable',
  richPresence: 'on',
  importSettings: 'on',
  minimizeToTray: 'on'
}
Failed to import settings: Error: ENOENT: no such file or directory, scandir '/home/viliusp/.config/Vencord/settings'
    at readdirSync (node:fs:1506:26)
    at t.readdirSync (node:electron/js2c/node_init:2:13703)
    at WebContents.<anonymous> (VCDMain:87:4114)
    at WebContents.emit (node:events:518:28) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'scandir',
  path: '/home/viliusp/.config/Vencord/settings'
}
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started

When I tried running with various combinations of the following:

• Deleting frame: true;
• Adding transparent: false;
• Running with --ozone-platform-hint=auto --ozone-platform=x11;
• Running with --ozone-platform-hint=auto --ozone-platform=wayland --enable-features=WaylandWindowDecorations;

After several attempts of various combintations, I managed to make the login screen appear, but I couldn't consistently reproduce the result.

After some difficulties and monkey testing, I managed to consistently reproduce it:

• Delete the configuration files: rm -rf ~/.config/vesktop/ ;
• Run with pnpm start --ozone-platform-hint=auto --ozone-platform=x11;
• Wait until it loads (for me, this takes about 30–60 seconds);
• A white window should appear.
• Press and hold ctrl, (mandatory) wait for few seconds and press R.
• If last step did nothing, repeat it for some times.
• Every other start, should start vesktop correctly, without this white screen.

To try replicate it again, delete configs again rm -rf ~/.config/vesktop/

This also somehow managed to fix my flatkpak version of Vesktop. So It is probably linked with settings/configurations or electron itself. Also I think, if the login screen isn't rendered, on the next open Vesktop downloads files again (because it loads for some time).

TL:DR If you have the same problem, Press and hold ctrl, wait for few seconds and press R. Repeat till it shows something. Also, before you can delete config folder.

[Covkie]

What is cosmic-os? The cosmic DE by system76? If so that DE is still highly in alpha and is likely the cause of YOUR specific issue.
Everyone else in here is a windows user and I can replicate this in both 10 & 11 vms just fine. The fix I mentioned earlier consistently fixed the white screen issue so I'm just waiting for someone on baremetal windows to replicate.

[x8c8r]

Can someone who is experiencing this try to build and run with either frame: true removed or add transparent: false

Vesktop/src/main/firstLaunch.ts

Lines 29 to 36 in 6c4ecc0

	const win = new BrowserWindow({
	...SplashProps,
	frame: true,
	autoHideMenuBar: true,
	height: 470,
	width: 550,
	icon: ICON_PATH
	});

worked for me

[TuxBalazs]

Clicking on the reset Vencord option in the tray menu, than selecting canary in the installer fixed the issue for me.