Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#72637 - [bitwarden] v1.29.1 does not start
Attached to Project:
Community Packages
Opened by zeroconf (zeroconf) - Thursday, 04 November 2021, 19:37 GMT
Last edited by Alexander Epaneshnikov (alex19EP) - Friday, 05 November 2021, 13:38 GMT
Opened by zeroconf (zeroconf) - Thursday, 04 November 2021, 19:37 GMT
Last edited by Alexander Epaneshnikov (alex19EP) - Friday, 05 November 2021, 13:38 GMT
|
DetailsDescription:
Bitwarden v1.29.1 does not start. Additional info: * package version(s): 1.29.1-1 * config and/or log files etc. * link to upstream bug report, if any Error messages: ps aux|grep -i bitward user 33773 2.3 0.2 21653236 131568 ? Sl 21:13 0:00 /usr/lib/electron14/electron /usr/lib/bitwarden/app.asar user 33807 0.5 0.1 17364704 77632 ? Sl 21:13 0:00 /usr/lib/electron14/electron --type=gpu-process --field-trial-handle=8668675506232649735,3094726596050778986,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --user-data-dir=/home/user/.config/Bitwarden --gpu-preferences=UAAAAAAAAAAgAAAQAAAAAAAAAAAAAAAAAABgAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAAAAAAAAAGAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAACAAAAAAAAAA= --shared-files user 33817 0.2 0.1 17316212 86724 ? Sl 21:13 0:00 /usr/lib/electron14/electron --type=utility --utility-sub-type=network.mojom.NetworkService --field-trial-handle=8668675506232649735,3094726596050778986,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=et --service-sandbox-type=none --user-data-dir=/home/user/.config/Bitwarden --shared-files=v8_context_snapshot_data:100 Steps to reproduce: Try to run Bitwarden either directly GUIor from CLi - not possible. |
This task depends upon
Closed by Alexander Epaneshnikov (alex19EP)
Friday, 05 November 2021, 13:38 GMT
Reason for closing: None
Additional comments about closing: resolved
Friday, 05 November 2021, 13:38 GMT
Reason for closing: None
Additional comments about closing: resolved
(node:36497) DeprecationWarning: file property is deprecated and will be removed in v5.
(Use `electron --trace-deprecation ...` to show where the warning was created)
(node:36497) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15. See https://github.com/electron/electron/issues/28511 for more information.
(node:36497) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'setContextMenu')
at tray_main_TrayMain.updateContextMenu (/usr/lib/bitwarden/app.asar/main.js:2084:23)
at messaging_main_MessagingMain.updateTrayMenu (/usr/lib/bitwarden/app.asar/main.js:1515:28)
at messaging_main_MessagingMain.onMessage (/usr/lib/bitwarden/app.asar/main.js:1453:22)
at messaging_main_MessagingMain.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:1444:154)
at Generator.next (<anonymous>)
at /usr/lib/bitwarden/app.asar/main.js:1422:71
at new Promise (<anonymous>)
at messaging_main_awaiter (/usr/lib/bitwarden/app.asar/main.js:1418:12)
at IpcMainImpl.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:1444:82)
at IpcMainImpl.emit (events.js:376:20)
(node:36497) 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:36497) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:36497) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'setContextMenu')
at tray_main_TrayMain.updateContextMenu (/usr/lib/bitwarden/app.asar/main.js:2084:23)
at messaging_main_MessagingMain.updateTrayMenu (/usr/lib/bitwarden/app.asar/main.js:1515:28)
at messaging_main_MessagingMain.onMessage (/usr/lib/bitwarden/app.asar/main.js:1453:22)
at messaging_main_MessagingMain.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:1444:154)
at Generator.next (<anonymous>)
at /usr/lib/bitwarden/app.asar/main.js:1422:71
at new Promise (<anonymous>)
at messaging_main_awaiter (/usr/lib/bitwarden/app.asar/main.js:1418:12)
at IpcMainImpl.<anonymous> (/usr/lib/bitwarden/app.asar/main.js:1444:82)
at IpcMainImpl.emit (events.js:376:20)
(node:36497) 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)
15:01:26.452 › search indexing: 38.1378491ms
I am too. but unfortunately I cannot influence this in any way.
> when running bitwarden-desktop from CLI, the output contains some irritating messages
these messages are in the official bitworden builds as well.