github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-05 19:18:16 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Vikunja Desktop Debian Package 0.24.6 Crashes #2062

New Issue
Closed
opened 2026-03-22 13:54:00 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-22 13:54:00 -05:00
Owner
Copy Link

Originally created by @nosbig on GitHub (Jan 10, 2025).

Description

I am self-hosting 0.24.6 on a public VPS and upgraded the package to 0.24.6. After doing so, the startup of the Desktop app crashes with an error about missing the body-parser module.

A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module 'body-parser'
Require stack:

  • /opt/Vikunja Desktop/resources/app.asar/node_modules/express/lib/express.js
  • /opt/Vikunja Desktop/resources/app.asar/node_modules/express/index.js
  • /opt/Vikunja Desktop/resources/app.asar/main.js
  • at Module._resolveFilename (node:internal/modules/cjs/loader:1055:15)
    at s._resolveFilename (node:electron/js2c/browser_init:2:115690)
    at Module._load (node:internal/modules/cjs/loader:908:27)
    at c._load (node:electron/js2c/node_init:2:13672)
    at Module.require (node:internal/modules/cjs/loader:1122:19)
    at require (node:internal/modules/helpers:130:18)
    at Object. (/opt/Vikunja Desktop/resources/app.asar/node_modules/express/lib/express.js:15:18)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1311:10)
    at Module.load (node:internal/modules/cjs/loader:1098:32)

If I downgrade to the 0.24.4 package and allow the internal update process pull the 0.24.6 code from my server, the Desktop package works flawlessly and retains the 0.24.6 update locally. However, upgrading to the 0.24.6 Debian package consistently throws that error for me on Debian 12 Stable.

Vikunja Version

0.24.6

Browser and version

Desktop Package - Deb

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @nosbig on GitHub (Jan 10, 2025). ### Description I am self-hosting 0.24.6 on a public VPS and upgraded the package to 0.24.6. After doing so, the startup of the Desktop app crashes with an error about missing the body-parser module. --- A JavaScript error occurred in the main process Uncaught Exception: Error: Cannot find module 'body-parser' Require stack: - /opt/Vikunja Desktop/resources/app.asar/node_modules/express/lib/express.js - /opt/Vikunja Desktop/resources/app.asar/node_modules/express/index.js - /opt/Vikunja Desktop/resources/app.asar/main.js - at Module._resolveFilename (node:internal/modules/cjs/loader:1055:15) at s._resolveFilename (node:electron/js2c/browser_init:2:115690) at Module._load (node:internal/modules/cjs/loader:908:27) at c._load (node:electron/js2c/node_init:2:13672) at Module.require (node:internal/modules/cjs/loader:1122:19) at require (node:internal/modules/helpers:130:18) at Object.<anonymous> (/opt/Vikunja Desktop/resources/app.asar/node_modules/express/lib/express.js:15:18) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Module._extensions..js (node:internal/modules/cjs/loader:1311:10) at Module.load (node:internal/modules/cjs/loader:1098:32) --- If I downgrade to the 0.24.4 package and allow the internal update process pull the 0.24.6 code from my server, the Desktop package works flawlessly and retains the 0.24.6 update locally. However, upgrading to the 0.24.6 Debian package consistently throws that error for me on Debian 12 Stable. ### Vikunja Version 0.24.6 ### Browser and version Desktop Package - Deb ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:54:02 -05:00
Author
Owner
Copy Link

@nosbig commented on GitHub (Jan 10, 2025):

This appears to be a duplicate of #387. Closing.

@nosbig commented on GitHub (Jan 10, 2025): This appears to be a duplicate of #387. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2062
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?