遇到一些问题 got some problems
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@parcel/watcher/build/Release/watcher. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@parcel/watcher/build/Release/watcher. node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/policy-watcher/build/Release/vscode-policy-watcher. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/policy-watcher/build/Release/vscode-policy-watcher. node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/spdlog/build/Release/spdlog. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/spdlog/build/Release/spdlog. node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/sqlite3/build/Release/vscode-sqlite3. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/sqlite3/build/Release/vscode-sqlite3. node: Unknown debugging section .debug_gnu_pubtypes
objcopy: ./opt/visual-studio-code/resources/app/node_modules.asar. unpacked/@vscode/vsce-sign/bin/vsce-sign: debuglink section already exists
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/kerberos. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/kerberos. node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/obj.target/kerberos. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/obj.target/kerberos. node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping. node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty. node: Unknown debugging section .debug_gnu_pubtypes
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/vsda/build/Release/vsda. node: Unknown debugging section .debug_gnu_pubnames
debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/vsda/build/Release/vsda. node: Unknown debugging section .debug_gnu_pubtypes
vscode和linuxqq一起安装的时候会安装失败，冲突貌似在各自的debug程序上 When vscode and linuxqq are installed together, the installation fails, and the conflict seems to be on their respective debug programs
错误：无法提交处理 (有冲突的文件)
/usr/lib/debug/.build-id/b1/ace29c2ed9438afddbed0feb85e62b70014f5f 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
/usr/lib/debug/.build-id/b1/ace29c2ed9438afddbed0feb85e62b70014f5f.debug 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
/usr/lib/debug/.build-id/f8/92293f507294f22c5d8b7eda75c8b7bd530932 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
/usr/lib/debug/.build-id/f8/92293f507294f22c5d8b7eda75c8b7bd530932.debug 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
发生错误，没有软件包被更新。
-> 安装时出错: [/home/stone/.cache/yay/visual-studio-code-bin/visual-studio-code-bin-1.88.0-1-x86_64.pkg.tar.zst /home/stone/.cache/yay/visual-studio-code-bin/visual-studio-code-bin-debug-1.88.0-1-x86_64.pkg.tar.zst /home/stone/.cache/yay/linuxqq/linuxqq-2:3.2.7_240403-1-x86_64.pkg.tar.zst /home/stone/.cache/yay/linuxqq/linuxqq-debug-2:3.2.7_240403-1-x86_64.pkg.tar.zst] - exit status 1
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2020-02-06 21:33 (UTC) by dcelasun)
FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)
This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the license difference and branding, there are some proprietary features not available in the open source version.
Please check this page before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on Github is NOT a release! If you can see the new version on the updates page but the AUR package is still not updated, flag it and give it time. It's usually done within a day or two.
Sometimes AUR helpers do weird things. Download the tarball and install it manually with
makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.xdg-openuses vscode, not my file manager! How do I fix this?Install shared-mime-info-gnome. Also see this reddit thread.
Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap to make sure it's really not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.
The problem might be a packaging issue (wrong paths, dependencies, icons), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on Github.
No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.