--appimage-extract-and-run: mkdir_p error: Permission denied on FreeBSD · AppImage/AppImageKit#1073

(1 comment) (0 reactions) (0 assignees)C (8,239 stars) (547 forks)batch import

buggood first issuehelp-wanted

説明

Trying to --appimage-extract-and-run a x86_64 Linux AppImage on FreeBSD 12.1-RELEASE-p8 with the Linux compatibility layer:

user@FreeBSD$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract-and-run
mkdir_p error: Permission denied
Failed to extract AppImage

but

user@FreeBSD$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract

user@FreeBSD$ truss /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract-and-run 2>&1 | grep tmp
linux_access("/tmp/appimage_extracted_11b387e8ae9d3b2f6c030e4cfa7e8cc2/",F_OK) ERR#-2 'No such file or directory'
linux_mkdir("/tmp",493)                          ERR#-13 'Permission denied'

Doing manually:

user@FreeBSD$ mkdir -p /tmp/appimage_extracted_11b387e8ae9d3b2f6c030e4cfa7e8cc2/

works though, so why are we failing then?

コントリビューターガイド

技術スタック: cshell
領域: desktoptooling
Issue 種別: bug
難度: 3
推定時間: half day
活動状況: stale
明確さ: mostly clear
前提条件: basic C knowledgeLinux compatibility layer on FreeBSD
初心者向け度: 30
調査方針: The issue is that mkdir p fails with permission denied on /tmp when running appimage extract and run, but manual mkdir works. Look at the source code for mkdir p in AppImageKit (likely in src/), especially how it constructs the path. Compare with the truss output showing linux mkdir failing; the issue might be related to the Linux compatibility layer's handling of permissions on /tmp. Check if the AppImage runtime is attempting to create the /tmp directory itself instead of just the subdirectory, or if there's a difference in how the mkdir system call is invoked.