Hi,
I have a doubt about what the title says; it consists on using Inkscape under Linux, particularly in my case, under Ubuntu.
I mean: when Inkscape is opened with normal user privileges, the icons on the left of the text that is in the menu bar don't appear; i just can see an icon that means "unknown issue" or something like that.
But when I open Inkscape as an administrator i can see those icons normally.
I also observe that the .svg files that I create when I'm using Inkscape as root can't be modified unless I modify the acces permission to them.
The case is that I would like to see those icons on normal mode; is there any way to get it??
thanks in advance.
In spanish we say something like this: "The value of only one image is bigger than thousand words"; so here are the images of what I'm trying to explain:
The first image is how I see the menu as admin:
This one is when I open Inkscape on a normal way:
Differences between using Inkscape as admin or as a normal u
Re: Differences between using Inkscape as admin or as a norm
Oh, that is very interesting! It might be a bug. I'm not familiar with Linux/Ubuntu, only with Windows. And with Windows Vista/7, we have options to "Run as Admin", but I haven't found that necessary to use Inkscape.
Also with Windows, when we install some programs, we are given an option to install for all users. Honestly, I don't remember from whenever I last installed Inkscape, whether that option was available. If it's available in your os when you install, that would probably solve the problem. But I have no idea about Linux/Ubuntu.
I'll do some searching at Launchpad (Inkscape bug tracker) to see if it's been reported. Probably it already has been, and if so, a solution may be given there. I'll let you know what I find (Of course you're welcome to search yourself https://launchpad.net/inkscape)
Edit
Ah-HA! https://bugs.launchpad.net/inkscape/+bug/775702 You're welcome to read through (long read) and add any comments, if you have relevant info that has not already been reported.
It looks like rather a complex bug with several related bugs. I have not read more than the original report, and the user/admin issue wasn't mentioned. So be sure and read all the way through them all. If no one else has reported that the problem can be solved by running as admin, that would certainly be helpful for them. Or if it has been reported (maybe in one of the related bugs) maybe someone has a solution for non-admin use.
Also with Windows, when we install some programs, we are given an option to install for all users. Honestly, I don't remember from whenever I last installed Inkscape, whether that option was available. If it's available in your os when you install, that would probably solve the problem. But I have no idea about Linux/Ubuntu.
I'll do some searching at Launchpad (Inkscape bug tracker) to see if it's been reported. Probably it already has been, and if so, a solution may be given there. I'll let you know what I find (Of course you're welcome to search yourself https://launchpad.net/inkscape)
Edit
Ah-HA! https://bugs.launchpad.net/inkscape/+bug/775702 You're welcome to read through (long read) and add any comments, if you have relevant info that has not already been reported.
It looks like rather a complex bug with several related bugs. I have not read more than the original report, and the user/admin issue wasn't mentioned. So be sure and read all the way through them all. If no one else has reported that the problem can be solved by running as admin, that would certainly be helpful for them. Or if it has been reported (maybe in one of the related bugs) maybe someone has a solution for non-admin use.
Basics - Help menu > Tutorials
Manual - Inkscape: Guide to a Vector Drawing Program
Inkscape Community - Inkscape FAQ - Gallery
Inkscape for Cutting Design
Manual - Inkscape: Guide to a Vector Drawing Program
Inkscape Community - Inkscape FAQ - Gallery
Inkscape for Cutting Design
Re: Differences between using Inkscape as admin or as a norm
I think that your default.xml file in /user/share/inscape/keys is scrambled.
Replace it with a copy of inkscape.xml which contains the defaults.
Read the start of this file which explains all.
Replace it with a copy of inkscape.xml which contains the defaults.
Read the start of this file which explains all.
Re: Differences between using Inkscape as admin or as a norm
Thanks brynn and rich2005 for your quick responses; both are very usefull and fistable I'm gonna try replacing the default.xml file.
I'll keep you in contact
I'll keep you in contact
Re: Differences between using Inkscape as admin or as a norm
i think that was meant to be "first of all" instead of "fistable".
u crazy spanish paela
make sure to install for all users under linux. otherwise a non-root user can't access some of the files that make inkscape, or you end up trying to access root owned preferences and cache files.
u crazy spanish paela
make sure to install for all users under linux. otherwise a non-root user can't access some of the files that make inkscape, or you end up trying to access root owned preferences and cache files.
Re: Differences between using Inkscape as admin or as a norm
Never come across installing an application 'for all users' in linux only windows. You can change file permissions to 'other' and change the owner though.
Ubuntu uses the 'sudo' system, so when you install an application you temporarily have admin privileges for installing system files but after that you run it as a user and any files created are 'owned' by that user. Naturally if you 'sudo inkscape' then you are running it as 'root' and the files are owned by root.
I duplicated the menu difference by disabling the default.xml file, thats why I think that is the problem.
Ubuntu uses the 'sudo' system, so when you install an application you temporarily have admin privileges for installing system files but after that you run it as a user and any files created are 'owned' by that user. Naturally if you 'sudo inkscape' then you are running it as 'root' and the files are owned by root.
I duplicated the menu difference by disabling the default.xml file, thats why I think that is the problem.