[Win32] Vista Permissions Issue with Effects

Bug #179683 reported by Martin Andersen
6
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Medium
Simon Dahlbacka
0.46.x
Fix Released
Medium
Unassigned

Bug Description

This may be a duplicate of Bug #176750, but this is more general and relates to the root cause:
Some Effects, such as Perspective, does not work under Windows Vista unless Inkscape is run as Administrator. Perspective (or the Python script rather) is trying to set a Registry value, which it doesn't have permission to.

Revision history for this message
Ryan Lerch (ryanlerch) wrote :

cant confirm this, as i cant get effects working at all on Vista

Changed in inkscape:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
sysFred (sysfred) wrote :

Yes, it is what I experienced to. Effects work in general on windows Vista (rel. 0.45-0.46 eng), except "perspective"

Revision history for this message
Simon Dahlbacka (simon-dahlbacka) wrote :

The issue is that src/RegistryTool.cpp wants to write to HKLM to which normal users doesn't have access, and therefore perspective effect (and everything else that use registrytool) blows up.

Registy tool should probably use HKCU instead or HKLM and it should work even for normal users.

A manual workaround is to use regedit and go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\inkscape.exe
and give full control permissions to Users
(right-click->Permissions->select Users, check Full control checkbox, Ok)

Revision history for this message
Martin Andersen (msandersen) wrote :

As a workaround, since I trust Inkscape, I simply right-clicked the executable and chose "Run As Administrator". That way Perspective etc works, altough I have to click that annoying Allow button every time.
The fix you propose sounds good.

Revision history for this message
Simon Dahlbacka (simon-dahlbacka) wrote :

Trivial patch that replaces HKLM with HKCU.

Revision history for this message
Tom Davidson (tjd-mit) wrote :

If this is tested as fixing the problem, it should be nominated for inclusion in 0.46

Changed in inkscape:
importance: High → Medium
status: Incomplete → Triaged
Revision history for this message
Simon Dahlbacka (simon-dahlbacka) wrote :

I'm running a private build with this patch and it fixes the problem.
 However, I cannot tell if it breaks something else (it shouldn't, but you never know..)

Revision history for this message
Tom Davidson (tjd-mit) wrote :

Assigning to Simon so he can get the bug-killing points when this is added to the tree :)

Changed in inkscape:
assignee: nobody → simon-dahlbacka
milestone: none → 0.46
Revision history for this message
ScislaC (scislac) wrote :

Bryce,

This is a rather trivial patch and didn't break anything on an xp compile for me. Include it?

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks, applied.

Revision history for this message
Bryce Harrington (bryce) wrote :

Dropping the 0.46 milestone on this since it's now included in the release branch.
Can someone please also apply this to the SVN head, so we can close the bug?

Changed in inkscape:
milestone: 0.46 → 0.47
Revision history for this message
Simon Dahlbacka (simon-dahlbacka) wrote :

Per discussions in https://bugs.launchpad.net/bugs/187290 it seems that my patch doesn't work properly on XP.

Revision history for this message
Simon Dahlbacka (simon-dahlbacka) wrote :

2:nd try: This patch does not change away from HKLM as that seems to be documented (but not HKCU), instead it redirects the error messages to stderr. And at least for me python is still found and Perspective is happy.

Tested on Vista x86.

Revision history for this message
Martin Andersen (msandersen) wrote :

So if there are any other errors, the extension dies silently? If there is an error log somewhere, that would be OK. I would prefer not to see any console output; it looks so... Unixy. Ugh.

ScislaC (scislac)
Changed in inkscape:
status: Triaged → Fix Released
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.