Recently inkscape has taken a very long time to launch if it is started by a regular user (~25 seconds compared with < 10). Reproducible: Always Steps to Reproduce: 1. Attempt to start media-gfx/inkscape-0.46-r2 using a ~AMD64 system as a regular user. Expected Results: Inkscape should (and used to) have similar times for both regular users and root. Using an ~AMD64 system. In order to 'solve' the problem I have emerge -e world. GTK theme is the same for both root and normal user, preferences (~/.inkscape) have been deleted to ensure that they are not the problem. Attached are strace -tt logs of normal and root users starting inkscape. Exact cause is unknow.
Created attachment 153845 [details] Normal user
Created attachment 153847 [details] As root.
Created attachment 153849 [details] emerge --info
This is not reproducible on my systems. Maybe you'll have more luck when you report this upstream. - Is this a regression compared to inkscape-0.45? - Could you paste your emerge -pv inkscape output here?
because inkscape doesn't use python.eclass to byte-compile and optimize the plugins into .pyc and .pyo and as non-root you won't have write permission to the plugins directory. solution, restore functionality -> convert to python.eclass, python_mod_optimize, python_mod_cleanup.. /usr/share is wrong place for python since it's getting byte-compiled, should convince upstream to change it to libdir. patch welcome.
*** Bug 270670 has been marked as a duplicate of this bug. ***
This is fixed long time ago: *inkscape-0.48.4-r1 (01 May 2013) 01 May 2013; Julian Ospald <hasufell@gentoo.org> +inkscape-0.48.4-r1.ebuild, +files/inkscape-0.48.4-automake-1.3.patch, +files/inkscape-0.48.4-epython.patch: convert to python-single-r1 wrt #467234 and fix build with automake-1.13 wrt #467228
Thank you for pointing there, Nikoli.
