Arch Linux

chibo

Member

Registered: 2018-04-27

Posts: 87

Programs are crashing because of relying on the 'makepkg' path

I have a few examples

First is a Blender addon error, I already talk with addon dev, so he says on his machine all works just fine

location: /usr/share/blender/2.79/scripts/modules/bpy/ops.py:197
Error: Traceback (most recent call last):
  File "/usr/share/blender/2.79/scripts/addons/io_scene_obj/__init__.py", line 312, in execute
    return export_obj.save(context, **keywords)
  File "/usr/share/blender/2.79/scripts/addons/io_scene_obj/export_obj.py", line 856, in save
    EXPORT_PATH_MODE=path_mode,
  File "/usr/share/blender/2.79/scripts/addons/io_scene_obj/export_obj.py", line 798, in _write
    progress,
  File "/usr/share/blender/2.79/scripts/addons/io_scene_obj/export_obj.py", line 333, in write_file
    with open(filepath, "w", encoding="utf8", newline="\n") as f:
FileNotFoundError: [Errno 2] No such file or directory: ''

location: /usr/share/blender/2.79/scripts/modules/bpy/ops.py:197

ERROR (wm.operator): /home/chibo/HGST/.cache/makepkg/blender-git/src/blender/source/blender/windowmanager/intern/wm_event_system.c:1182 wm_operator_invoke: invalid operator call 'SCREEN_OT_redo_last'

https://i.imgur.com/FEvd2K3.png

Next is Unreal Engine 4 with -vulkan flag, I have installed vulkan-icd-loader and vulkan-radeon, for my HD 7950, but it works only with -opnegl4 flag

LoginId:0002c54308d646b3a65e587463f1ee0e
EpicAccountId:

Fatal error: [File:/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanUtil.cpp] [Line: 669] VulkanRHI::vkEnumeratePhysicalDevices(Instance, &GpuCount, nullptr) failed, VkResult=-3 at /home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanRHI.cpp:453 with error VK_ERROR_INITIALIZATION_FAILED 0x00007f3a3b311a57 libUE4Editor-VulkanRHI.so!VulkanRHI::VerifyVulkanResult(VkResult, char const*, char const*, unsigned int) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanUtil.cpp:668] 0x00007f3a3b2cf931 libUE4Editor-VulkanRHI.so!FVulkanDynamicRHI::SelectAndInitDevice() [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanRHI.cpp:453] 0x00007f3a3b2cd5f0 libUE4Editor-VulkanRHI.so!FVulkanDynamicRHI::InitInstance() [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanRHI.cpp:614] 0x00007f3a3b2cd1fa libUE4Editor-VulkanRHI.so!FVulkanDynamicRHI::Init() [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanRHI.cpp:185] 0x00007f3a576c687a libUE4Editor-RHI.so!RHIInit(bool) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/RHI/Private/DynamicRHI.cpp:201] 0x000000000022e7d9 UE4Editor!FEngineLoop::PreInit(char16_t const*) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Launch/Private/LaunchEngineLoop.cpp:1903] 0x0000000000240288 UE4Editor!GuardedMain(char16_t const*) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Launch/Private/Launch.cpp:135] 0x00007f3a5309b1d5 libUE4Editor-UnixCommonStartup.so!CommonUnixMain(int, char**, int (*)(char16_t const*)) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Unix/UnixCommonStartup/Private/UnixCommonStartup.cpp:245] 0x00007f3a52d5c223 libc.so.6!__libc_start_main(+0xf2) 0x000000000022b02e UE4Editor!_start(+0x2d)

libUE4Editor-Core.so!FGenericPlatformMisc::RaiseException(unsigned int) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Core/Private/GenericPlatform/GenericPlatformMisc.cpp:404]
libUE4Editor-Core.so!FUnixErrorOutputDevice::Serialize(char16_t const*, ELogVerbosity::Type, FName const&) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Core/Private/Unix/UnixErrorOutputDevice.cpp:56]
libUE4Editor-Core.so!FOutputDevice::LogfImpl(char16_t const*, ...) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Core/Private/Misc/OutputDevice.cpp:71]
libUE4Editor-Core.so!FDebug::AssertFailed(char const*, char const*, int, char16_t const*, ...) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Core/Private/Misc/AssertionMacros.cpp:417]
libUE4Editor-VulkanRHI.so!VulkanRHI::VerifyVulkanResult(VkResult, char const*, char const*, unsigned int) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanUtil.cpp:668]
libUE4Editor-VulkanRHI.so!FVulkanDynamicRHI::SelectAndInitDevice() [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanRHI.cpp:453]
libUE4Editor-VulkanRHI.so!FVulkanDynamicRHI::InitInstance() [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanRHI.cpp:614]
libUE4Editor-VulkanRHI.so!FVulkanDynamicRHI::Init() [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/VulkanRHI/Private/VulkanRHI.cpp:185]
libUE4Editor-RHI.so!RHIInit(bool) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/RHI/Private/DynamicRHI.cpp:201]
UE4Editor!FEngineLoop::PreInit(char16_t const*) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Launch/Private/LaunchEngineLoop.cpp:1903]
UE4Editor!GuardedMain(char16_t const*) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Launch/Private/Launch.cpp:135]
libUE4Editor-UnixCommonStartup.so!CommonUnixMain(int, char**, int (*)(char16_t const*)) [/home/chibo/HGST/.cache/makepkg/unreal-engine/src/UnrealEngine/Engine/Source/Runtime/Unix/UnixCommonStartup/Private/UnixCommonStartup.cpp:245]
libc.so.6!__libc_start_main(+0xf2)
UE4Editor!_start(+0x2d)

https://i.imgur.com/KLVB6tA.png

Last edited by chibo (2018-11-10 17:37:13)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,769

Re: Programs are crashing because of relying on the 'makepkg' path

Please do not post large pictures.  And, in the case of the first photo, do not send pictures of text.  Post the text.
https://wiki.archlinux.org/index.php/Co … s_and_code
EdIt:  I took the liberty of converting your img tag to code tags.

Last edited by ewaller (2018-11-10 15:53:22)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,517

Website

Re: Programs are crashing because of relying on the 'makepkg' path

How did you install these packages?  Were these PKGBUILDs that you wrote or modified yourself?

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

chibo

Member

Registered: 2018-04-27

Posts: 87

Re: Programs are crashing because of relying on the 'makepkg' path

ewaller
np

How did you install these packages?  Were these PKGBUILDs that you wrote or modified yourself?

yay -S blender-git unreal-engine
(Epic Games love Linux, you hear it?)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,540

Re: Programs are crashing because of relying on the 'makepkg' path

The first one doesn't seem to have anything to do with the path, that's just there as debugging info.

The second one, too much is cut off. Post text as text, not pictures.

chibo

Member

Registered: 2018-04-27

Posts: 87

Re: Programs are crashing because of relying on the 'makepkg' path

Scimmia
Done

Could you tell me whose fault it is?

loqs

Member

Registered: 2014-03-06

Posts: 17,310

Re: Programs are crashing because of relying on the 'makepkg' path

Could you tell me whose fault it is?

Whose fault what is?  Does the source code use the __FILE__ macro?

chibo

Member

Registered: 2018-04-27

Posts: 87

Re: Programs are crashing because of relying on the 'makepkg' path

Whose fault what is?

 
To make my software useless, obviously ~_~

Does the source code use the __FILE__ macro?

I guess so https://i.imgur.com/MqEjRlB.png

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,769

Re: Programs are crashing because of relying on the 'makepkg' path

It would appear that your pwd is that directory, and that is why it is why the program is looking in that directory.   cd to ~ and run it again and see if the reported directory changes.
There is a problem, but the "'makepkg' path" might be a red herring.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

HalosGhost

Forum Moderator

From: Twin Cities, MN

Registered: 2012-06-22

Posts: 2,092

Website

Re: Programs are crashing because of relying on the 'makepkg' path

I guess so https://i.imgur.com/MqEjRlB.png

Post text as text, not pictures.

chibo, Please go reread the full Code of Conduct before posting again.

All the best,

-HG

---

Code of Conduct

chibo

Member

Registered: 2018-04-27

Posts: 87

Re: Programs are crashing because of relying on the 'makepkg' path

It would appear that your pwd is that directory, and that is why it is why the program is looking in that directory.   cd to ~ and run it again and see if the reported directory changes.
There is a problem, but the "'makepkg' path" might be a red herring.

oh, it's going too complicated for me, this scripts executed inside Blender, so can't imagine how to cd inside of it

anyway I wondering how blender knows this path!? as well as eu4

HalosGhost
maan, I heard you, but in this case image provides a lot more information than text, I don't want to blowing up forum with a tons of listings, and list of opened files

Last edited by chibo (2018-11-10 18:41:13)

loqs

Member

Registered: 2014-03-06

Posts: 17,310

Re: Programs are crashing because of relying on the 'makepkg' path

https://git.blender.org/gitweb/gitweb.c … em.c#l1182
https://git.blender.org/gitweb/gitweb.c … log.h#l167
The binary is just being built with the locations of the the sources at build time.  As scimmia and ewaller have pointed out already these strings are in no way related to the issue you are reporting.
Edit:
Looks to the blender plugin https://github.com/sobotka/blender-addo … bj.py#L330

Last edited by loqs (2018-11-10 18:58:18)

chibo

Member

Registered: 2018-04-27

Posts: 87

Re: Programs are crashing because of relying on the 'makepkg' path

ok, got it, so ue4 vulkan issue is also unrelated to the path?

I just thinking so it tried to open some stuff, but cant'f find it by wrong path

chibo

Member

Registered: 2018-04-27

Posts: 87

Re: Programs are crashing because of relying on the 'makepkg' path

Looks to the blender plugin

it's working on other machine, that the main reason why I start worrying about myself

Last edited by chibo (2018-11-10 19:13:32)

loqs

Member

Registered: 2014-03-06

Posts: 17,310

Re: Programs are crashing because of relying on the 'makepkg' path

Was the other system using blender built from the same git commit using the same build environment?

chibo

Member

Registered: 2018-04-27

Posts: 87

Re: Programs are crashing because of relying on the 'makepkg' path

Was the other system using blender built from the same git commit using the same build environment?

nope