After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 332595 - Win32 installation problems without administrator rights.
Win32 installation problems without administrator rights.
Status: RESOLVED FIXED
Product: dia
Classification: Other
Component: install
CVS head
Other Windows
: Normal normal
: ---
Assigned To: Steffen Macke
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-26 06:13 UTC by Steffen Macke
Modified: 2007-08-06 19:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Steffen Macke 2006-02-26 06:13:29 UTC 
I received a bug report that the installer(s) do not
work without admin rights.

The dia installer does not find the GTK+ installation in this case.

I think it should be possible to manually select the GTK+ installation
folder in this case.
Comment 1 Steffen Macke 2006-02-27 11:01:28 UTC 
Additional information regarding the affected system: 

There are keys related to GTK in HKEY_CURRENT_USER/Software/GTK/2.0 : DllPath, Path and Version
Comment 2 Alan Horkan 2006-03-07 10:55:29 UTC 
Can we have the all in one installer back please?  
Maybe bundle the whole lot together, and give the option not to install GTK for those who already have it?  

I'm constantly bitten by this issue because I only use windows when I forced to use it at work or university where it is invariably locked down/crippled.  
Inkscape has been praised in reviews for not forcing user to install both gkt and the application seperately, and conversely it is one of the many little things the GIMP gets derided for.
Comment 3 Alan Horkan 2006-03-07 12:32:36 UTC 
For what it is worth the installer for Workrave http://www.workrave.org/welcome/ provides the option to install GTK or use an existing copy.
Comment 4 Steffen Macke 2007-08-06 19:56:49 UTC 
I assume that this is not an issue any more with 0.96.1-7