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

yarn start not works on Windows #1463

Closed
fidoman opened this issue Jan 28, 2024 · 2 comments · Fixed by #1466
Closed

yarn start not works on Windows #1463

fidoman opened this issue Jan 28, 2024 · 2 comments · Fixed by #1466
Assignees
Labels

Comments

@fidoman
Copy link

fidoman commented Jan 28, 2024

Steps to reproduce

git clone https://github.com/element-hq/element-desktop
yarn install
yarn run fetch --noverify --cfgdir ""
yarn start

Outcome

What did you expect?

element runs

What happened instead?

Process runs but no any UI

yarn run v1.22.21
warning ....\package.json: No license field
$ yarn run build:ts && yarn run build:res && electron .
warning ....\package.json: No license field
$ tsc
warning ....\package.json: No license field
$ ts-node scripts/copy-res.ts

C:\Users\Administrator\AppData\Roaming\Element exists: yes
C:\Users\Administrator\AppData\Roaming\Riot exists: no
No update_base_url is defined: auto update is disabled
(node:1556) UnhandledPromiseRejectionWarning: Error: Invalid GUID format
at Object.create (C:\Users\Administrator\Documents\element-desktop\lib\tray.js:83:16)
at C:\Users\Administrator\Documents\element-desktop\lib\electron-main.js:483:14
at Generator.next ()
at fulfilled (C:\Users\Administrator\Documents\element-desktop\lib\electron-main.js:46:58)
(Use electron --trace-warnings ... to show where the warning was created)
(node:1556) 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: 1)
(node:1556) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'setAppLocale')
at IpcMainImpl. (C:\Users\Administrator\Documents\element-desktop\lib\ipc.js:101:40)
at Generator.next ()
at C:\Users\Administrator\Documents\element-desktop\lib\ipc.js:23:71
at new Promise ()
at __awaiter (C:\Users\Administrator\Documents\element-desktop\lib\ipc.js:19:12)
at IpcMainImpl. (C:\Users\Administrator\Documents\element-desktop\lib\ipc.js:79:12)
at IpcMainImpl.emit (node:events:517:28)
at IpcMainImpl.emit (node:domain:489:12)
at WebContents. (node:electron/js2c/browser_init:2:77364)
at WebContents.emit (node:events:517:28)
(node:1556) 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)

Operating system

Windows 2016

Application version

1.11.55

How did you install the app?

git clone from repo

Homeserver

No response

Will you send logs?

Yes

@fidoman
Copy link
Author

fidoman commented Jan 28, 2024

Last version that I could run is 1.11.36

@t3chguy
Copy link
Member

t3chguy commented Jan 29, 2024

Your repro steps are invalid

git clone [element-hq/element-desktop](https://github.com/element-hq/element-desktop)
yarn install
yarn run fetch --noverify --cfgdir ""
yarn start

image

You do not cd element-desktop so all later commands are invalid, ignoring that your run fetch command is also invalid, as running without a config will end up erroring unless you have a local config created which your repro steps do not claim you do - https://github.com/element-hq/element-desktop#user-specified-configjson


Last version that I could run is 1.11.36

Seems like your problem is caused by #1059

@t3chguy t3chguy self-assigned this Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants