https://bugs.kde.org/show_bug.cgi?id=503204
Bug ID: 503204
Summary: Krita Next nightly Appimage cannot start, memory
allocation failed and bad address
Classification: Applications
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: * Unknown
Assignee: krita-bugs-n...@kde.org
Reporter: tysont...@gmail.com
Target Milestone: ---
Since Apr 17, 2025, Krita Next nightly appimages cannot start anymore. Older
ones still works.
Environment:
Operating System: Manjaro Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.0-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 46.9 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: GPD
Product Name: G1619-04
System Version: Ver.1.0
Run them in console returns the following message:
./krita-5.3.0-prealpha-036380b067-x86_64.AppImage
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
Can't open squashfs image: Bad address
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
execv error: No such file or directory
--
You are receiving this mail because:
You are watching all bug changes.
