Comment 6 for bug 447292

Revision history for this message
DaTa (danielt) wrote : Re: [Bug 447292] Re: permission denied on various files while starting evince

On Mon, Oct 12, 2009 at 02:57:51PM -0000, Jamie Strandboge wrote:
> DaTa, your setup is non-standard and as such you will need to adjust
> /etc/apparmor.d/tunables/home from:
> @{HOMEDIRS}=/home/
>
> to:
> @{HOMEDIRS}=/home/ /export/home
>
> However, evince still won't run correctly due to #415632. A fix is
> pending for that issue and should be available in the next karmic
> kernel.

Thank you for the information.

> I highly suggest rather than removing all of AppArmor, that you simply
> disable the problematic profile. See
> https://wiki.ubuntu.com/DebuggingApparmor for details. There are many
> profiles enabled in the default install which greatly improves the
> security of your machine, and disabling all of AppArmor is not
> recommended.

You sit in front of

  [1]> strace -e mkdir evince
  mkdir("/home/danielt/.gnome2/evince", 0700) = -1 EACCES (Permission denied)

  (evince:8463): EvinceDocument-WARNING **: Failed to create directory /home/danielt/.gnome2/evince: Permission denied
  [0]> strace -e mkdir perl -le 'mkdir "/home/danielt/.gnome2/evince",0700 or die($!)'
  mkdir("/home/danielt/.gnome2/evince", 0700) = 0

and think: "What the fu^W^Wheck is going on?"

I've checked for SELinux (Where I've had a similar problem), but until a
few hours ago, I've never ever heard about AppArmor.

Maybe I'll give it a try sometime, but not know. (I'm angry about
AppArmor at the moment :)

Regards,
-DaTa