blender doesn't start with the settings from official portable version (20.04)

Bug #1883318 reported by Dima
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
blender (Ubuntu)
New
Undecided
Unassigned

Bug Description

I used official portable version on Lubuntu 18.04 and I have the settings file that still works with official portable version (2.82a). For some reason it doesn't work with blender from ubuntu 20.04 repos.

I tried to delete files and directories one by one and the problem is in my userpref.blend. For some reason it works with official portable version but doesn't work with blender shipped with Ubuntu. I could to delete the config directory, but it would take some time to recreate all my customs.

I get this messages when I try to start blender:

$ blender
Read prefs: /home/user/.config/blender/2.82/config/userpref.blend
blender(BLI_system_backtrace+0x37) [0x5573be937897]
blender(BLI_exists+0x73) [0x5573be932d43]
blender(BLI_is_dir+0xd) [0x5573be93300d]
blender(+0x13f3912) [0x5573bc24a912]
blender(wm_homefile_read+0x54a) [0x5573bc4336aa]
blender(WM_init+0x163) [0x5573bc437e53]
blender(main+0x2e1) [0x5573bc1f7401]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f61e3fea0b3]
blender(_start+0x2e) [0x5573bc2458ae]
BLI_assert failed: /build/blender-RL3axj/blender-2.82.a+dfsg/source/blender/blenlib/intern/storage.c:240, BLI_exists(), at '!BLI_path_is_rel(name)'
Aborted (core dumped)

I will attach my userpref.blend to next message.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: blender 2.82.a+dfsg-1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXDE
Date: Fri Jun 12 22:25:22 2020
EcryptfsInUse: Yes
SourcePackage: blender
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Dima (dima2017) wrote :
Revision history for this message
Dima (dima2017) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.