I use the in-kernel NFS root support and $HOME is just another directory
inside of that. My fstab does not have an entry for / or /home. I'm not
sure about autofs, but / never gets unmounted or remounted (Lazily or
otherwise) as far as I know...
--
apparmor not properly handling file deletion on
I use the in-kernel NFS root support and $HOME is just another directory
inside of that. My fstab does not have an entry for / or /home. I'm not
sure about autofs, but / never gets unmounted or remounted (Lazily or
otherwise) as far as I know...
--
evince fails to open all PDF - grey screen
https
Also, accessing PDFs on NFS works fine, so it is not a networking issue.
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Do you use autofs or otherwise have the nfs unmounting/remounting or
lazy unmounting?
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Twigathy, as a work around unitl this is fixed, you can do:
sudo aa-complain /etc/apparmor.d/usr.bin.evince
This will allow evince to work, but log policy violations.
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because y
Ok, I'll look into this more. FTR, the unencoded paths are:
Processing:
2F746D702F6F726269742D74776967617468792F6C696E632D6434632D302D33383265306665303636396664202864656C6574656429
Aug 24 15:53:48 corona kernel: [ 486.011858] type=1503
audit(1251125628.417:12): operation="mknod" info="Failed nam
Yes, ~ is on NFS (Along with the rest of root...)
twiga...@corona:~$ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.evince
Removal succeeded for "/usr/bin/evince".
Removal succeeded for "/usr/bin/evince-previewer".
Removal succeeded for "/usr/bin/evince-thumbnailer".
^ After doing this, I can op
I cannot reproduce this. Are you using and encrypted $HOME or an NFS mounted
$HOME? Does the problem go away if you do:
$ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.evince
** Changed in: evince (Ubuntu)
Status: New => Incomplete
--
evince fails to open all PDF - grey screen
https:/
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Attachment added: "KernLog.txt"
http://launchpadlibrarian.net/30818646/KernLog.txt
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
** Attachment added: "RelatedPackageVersions.txt"
http://launchpadlibrarian.net/30818647/RelatedPackageVersions.txt
** Changed in: evince (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/4
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30818645/Dependencies.txt
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm not sure this is not still an AppArmor issue. Please run:
apport-collect -p evince 415632
** Changed in: evince (Ubuntu)
Status: Invalid => Incomplete
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you ar
Still getting this problem. I removed .recently-used.xbel and that
didn't help either. Created a new user and they can use evince just
fine So some conf file somewhere has got borked. What should I
remove to stop this happening and make evince work again?
twiga...@corona:~$ evince zigbee.pdf
Not fixed for me -- see comments
** Changed in: evince (Ubuntu)
Status: Fix Released => Incomplete
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: evince (Ubuntu)
Status: Incomplete => Fix Committed
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
This bug was fixed in the package evince - 2.27.90-0ubuntu6
---
evince (2.27.90-0ubuntu6) karmic; urgency=low
* debian/apparmor-profile.abstraction: include abstractions/user-tmp
(LP: #415632)
* debian/apparmor-profile*:
- add support for DVI
- add support for EPS
Well, I just wrote it this morning. See http://bazaar.launchpad.net
/~ubuntu-core-dev/apparmor/profiles-devel/annotate/head%3A/bin/aa-
decode. I may try to get that into apparmor proper.
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug not
Excellent - cheers :)
I'll have to remember that aa-decode tool. Could come in handy some
time...
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
$ cat /tmp/415632 | aa-decode
Processing:
2F746D702F6F726269742D74776967617468792F6C696E632D6630362D302D32343134643233643135633963202864656C6574656429
Aug 19 14:14:51 corona kernel: [ 748.256584] type=1503
audit(1250687691.088:12): operation="mknod" info="Failed name lookup - deleted
entry" err
Sure - pasted below [apparently only two...]
Aug 19 14:14:51 corona kernel: [ 748.256584] type=1503
audit(1250687691.088:12): operation="mknod" info="Failed name lookup - deleted
entry" error=-2 pid=3846 parent=3621 profile="/usr/bin/evince"
requested_mask="w::" denied_mask="w::" fsuid=1000 ou
Thanks. This decodes to:
/home/twigathy/.recently-used.xbel.DEUIYU (deleted)
Can you attach your entire /var/log/kern.log right after you try to open
a PDF to make sure we can address all of the paths?
--
evince fails to open all PDF - grey screen
https://bugs.launchpad.net/bugs/415632
You recei
Good intelligent guesswork! My kern.log has a lot of these in:
Aug 18 23:56:11 corona kernel: [14335.422844] type=1503
audit(1250636171.706:27): operation="mknod" info="Failed name lookup -
deleted entry" error=-2 pid=7731 parent=4075 profile="/usr/bin/evince"
requested_mask="w::" denied_mask="w::
Thank you for using Ubuntu and taking the time to report a bug. Can you
attach your /var/log/kern.log right after you try to open a PDF? It is
possible that the new apparmor profile is causing you trouble.
** Changed in: evince (Ubuntu)
Status: New => Incomplete
** Changed in: evince (Ubun
24 matches
Mail list logo
