Marking the evince tasks as Fix Released since they both have the dbus
abstraction.
** Changed in: evince (Ubuntu Lucid)
Status: Triaged => Fix Released
** Changed in: evince (Ubuntu Maverick)
Status: Triaged => Fix Released
--
apparmor blocks evince from /usr/bin/dbus-launch
http
Based on Nikolus feedback, I am going to mark the AppArmor Lucid task as "Won't
Fix" for now (since evince is starting and running ok, but is otherwise just
noisy). If required, this can be reevaluated going forward. Upstream AppArmor
and Maverick will use the following in the new dbus-session a
This bug also affects me, and I tried the workaround. This is the
output:
k...@kai-laptop:~$ sudo evince
** (evince:6037): WARNING **: Failed to create dbus proxy for
org.gnome.SettingsDaemon: Could not get owner of name
'org.gnome.SettingsDaemon': no such name
** (evince:6037): WARNING **: Erro
the recent update of evince_2.30.1-0ubuntu1 to evince_2.30.1-0ubuntu2
solved the problem for me.
--
apparmor blocks evince from /usr/bin/dbus-launch
https://bugs.launchpad.net/bugs/566207
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ev
The AppArmor part has been committed to trunk and will be in maverick
when it hits.
** Also affects: apparmor (Ubuntu Maverick)
Importance: Medium
Assignee: Jamie Strandboge (jdstrand)
Status: Triaged
** Also affects: evince (Ubuntu Maverick)
Importance: Medium
Assignee: Ja
** Changed in: apparmor (Ubuntu Maverick)
Status: Triaged => Fix Committed
--
apparmor blocks evince from /usr/bin/dbus-launch
https://bugs.launchpad.net/bugs/566207
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in ubuntu.
I just log into the machine with ssh X11 forwarding enabled (the machine
is headless) and type "evince" in the console:
$ evince
** (evince:702): WARNING **: Error connecting to D-Bus: /bin/dbus-launch
terminated abnormally without any error message
** (evince:702): WARNING **: Service registra
The correct fix for this is to add a dbus-session abstraction to
apparmor and have evince use it. Will discuss with ubuntu-release if
this is acceptable for before release.
** Changed in: evince (Ubuntu)
Status: New => Triaged
** Changed in: evince (Ubuntu)
Importance: Undecided => High
Nikolaus, to workaround this issue, please add the following to
/etc/apparmor.d/abstractions/evince:
/usr/bin/dbus-launch Uxr,
Then perform:
$ sudo apparmor_parser -r -W -T /etc/apparmor.d/usr.bin.evince
--
apparmor blocks evince from /usr/bin/dbus-launch
https://bugs.launchpad.net/bugs/56620
The workaround seems to work, thanks. Now the only remaining error
message is
$ evince
** (evince:2175): WARNING **: Failed to create dbus proxy for
org.gnome.SettingsDaemon: Could not get owner of name
'org.gnome.SettingsDaemon': no such name
--
apparmor blocks evince from /usr/bin/dbus-launch
The remaining error is not an apparmor issue and should probably be
addressed in a separate bug.
--
apparmor blocks evince from /usr/bin/dbus-launch
https://bugs.launchpad.net/bugs/566207
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ev
This will be fixed in a an SRU.
** Changed in: evince (Ubuntu Lucid)
Milestone: None => lucid-updates
** Changed in: apparmor (Ubuntu Lucid)
Milestone: None => lucid-updates
--
apparmor blocks evince from /usr/bin/dbus-launch
https://bugs.launchpad.net/bugs/566207
You received this bug
Nikolaus, the problem you are seeing is that the dbus session bus is not
started, which is why evince won't start. The AppArmor issue will be
fixed in SRU, but to access evince using a remote display even after
this is fixed, you will need to start a session dbus (this is something
that gnome-sessi
No, that's a misunderstanding. Evince has been starting (and running)
fine all the time. It just produced a lot of error messages in the
kernel log and on the console.
--
apparmor blocks evince from /usr/bin/dbus-launch
https://bugs.launchpad.net/bugs/566207
You received this bug notification bec
** Changed in: apparmor (Ubuntu Lucid)
Importance: High => Medium
** Changed in: evince (Ubuntu Lucid)
Importance: High => Medium
--
apparmor blocks evince from /usr/bin/dbus-launch
https://bugs.launchpad.net/bugs/566207
You received this bug notification because you are a member of Ubuntu
It seems this has been yet again broken in Oneiric.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/566207
Title:
apparmor blocks evince from /usr/bin/dbus-launch
To manage notifica
I just opened #904001. Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/566207
Title:
apparmor blocks evince from /usr/bin/dbus-launch
To manage notifications a
Accepted apparmor into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Lucid affected, and added dbus-session abstraction, but nothing uses
this abstraction in Lucid. /etc/apparmor.d/abstractions/dbus is
unchanged on uupgrade and therefore no regression.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification bec
I was unclear in my last comment. Lucid is affected by this bug, but the
fix is not in the SRU for 2.5.1-0ubuntu0.10.04.1. I verified that
/etc/apparmor.d/abstractions/dbus is unchanged on upgrade and therefore
there are no regressions.
--
You received this bug notification because you are a memb
This bug was fixed in the package apparmor - 2.5.1-0ubuntu0.10.04.1
---
apparmor (2.5.1-0ubuntu0.10.04.1) lucid-proposed; urgency=low
* Backport 2.5.1-0ubuntu0.10.10.1 from maverick for userspace tools to work
with newer kernels (LP: #660077)
NOTE: user-tmp now uses 'owner'
This bug was fixed in the package apparmor - 2.5.1~pre1393-0ubuntu1
---
apparmor (2.5.1~pre1393-0ubuntu1) maverick; urgency=low
* Update to upstream bzr revision 1393 from lp:apparmor/2.5.
* add dbus-session abstraction (LP: #566207)
* require owner in user-tmp abstraction (
Hi Ben, if you feel this has regressed, please open a new bug and
reference it here. Add the tag 'regression-release' so that we can
prioritize it properly, and reference this bug in the report. Remember
to come back here and comment so that we can find the new bug and make
sure it gets triaged qui
23 matches
Mail list logo
