widelands

Windows installer doesn't request elevation

Bug #1640980 reported by Dale McCoy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
widelands
Triaged
Low
Tino
widelands build20-rc1

Bug Description

The Windows installer wants to install in Widelands in Program Files (x86), but doesn't request the elevation necessary in order to do so. Installers that have any intention of putting data in protected parts of the filesystem should request elevation.

Alternatively, Widelands can install choose to itself in AppData/Local by default, in which the elevation is no longer required.

Revision history for this message
GunChleoc (gunchleoc) wrote :

Actually, Widelands will request C:\bin\Widelands rather than Program Files, unless you have an older version already installed in Program Files. We recommend that you uninstall the old version first.

The not requesting elevation is on purpose, so people won't need admin rights to play.

Revision history for this message
Tino (tino79) wrote :

Yes, at the moment the installer does not require elevated privileges because:
- I've not figured out how Innosetup can handle this in a good way (is always or never).
- If installed into C:\Program Files\ with elevated privs, Widelands also does only run with elevated privs.

That is, because it currently writes the log file into the same directory as the binary resides.

We'll figure this out with the next release.

Changed in widelands:
assignee: nobody → Tino (tino79)
importance: Undecided → Low
milestone: none → build20-rc1
status: New → Confirmed
status: Confirmed → Triaged
GunChleoc (gunchleoc)
tags: added: buildsystem windows
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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