mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4124] [bug]: symbol lookup error #1476
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1476
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @ivostoykov on GitHub (Jun 15, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4124
Is there an existing issue for this?
Current behavior
Downloaded the latest version of appimage on Ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
as it failed to start with double click I tried it from the terminal and here is the result:
expected to see the desktop application
Steps to reproduce
chmod +x appimage_file_name./Hoppscotch_linux_x64.AppImageEnvironment
Production
Version
Local
@hakro commented on GitHub (Sep 20, 2024):
I'm getting this same problem trying to run the AppImage on an Ubuntu base distro (TuxedoOS 3)
I used the latest AppImage from the website.
@windigerbus commented on GitHub (Sep 21, 2024):
#3748
@liyasthomas commented on GitHub (Mar 4, 2025):
Thanks for your patience and valuable feedback. We’ve fixed this bug in the latest release.
Download the latest builds and provide your valuable feedback.
Closing this ticket as this bug is now fixed in the recent version. Please feel free to reach out if you have any other concerns.