For your reference: Bug #1890905
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
Status in ibus:
Fix
Agreed. I'll be referencing this issue there. And I'll have a look into
the journal, thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system
I agree that a new bug should be filed. When doing so, please attach any
relevant policy violations from journalctl to the bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
@Rüdiger: Quite some water has passed under the bridge since the
submission of this bug. It mostly came to be about the method for
achieving a distinguishable abstract path for IBus, and is now closed.
I would suggest that you file a new bug about the issue you now
encounter. It sounds like an
We are talking about recent Ubuntu focal, thst is: Ubuntu 20.04.1. This
is deemed safe for LTS upgrade! It is not! It will make petfectly
working installs of 18.04 LTS unusable without any warning.
--
You received this bug notification because you are a member of Desktop
Packages, which is
This will affect many installs, notably in professional multi user
environments. It is absurd assuming that $XDG_CACHE_HOME is unset (any
installation with a few hundred users will have homes on a network share
and consequently caches moved elsewhere).
--
You received this bug notification
Test case: chromium snap with $XDG_CACHE_HOME set.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
Status in
Our $XDG_CACHE_HOME points to /var/cache/usercache//
I tried adding /var/cache/usercache/ to @{HOMEDIRS} in apparmor, but it did not
work. How do I tell my snaps that user caches are in /var/cache/usercache/ ??
--
You received this bug notification because you are a member of Desktop
Packages,
This is *not* fixed. I still see this issue in a recent install of Ubuntu
20.04, where $XDG_CACHE_HOME is set.
We have home dirs mounted via network, so user caches were moved to local
storage to sanitize network load. The right and perfectly valid way of doing so
is setting $XDG_CACHE_HOME.
** Changed in: ibus (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus,
@Jamie: The code, which changes the abstract socket path from
'unix:tmpdir=/tmp/ibus' to 'unix:tmpdir=$XDG_CACHE_HOME/ibus', was
uploaded to focal via ibus 1.5.21-5ubuntu1 (unix-socket-path.patch).
Mentioned it on bug #1856738 too.
Closing the ibus (ubuntu) task on this bug.
--
You received
@Gunnar - I am preparing the focal upload now, though there is a parser
bug (bug 1856738) which means I cannot use @{HOME} in the rule and
instead hardcode /home/*/. This will cover all typical situations (ie,
not the atypical /root/.cache/ibus...) except when the user updates
@Tyler, @Jamie: When reviewing the proposal in comment #37, Sebastien
pointed at a possible need to also change
/etc/apparmor.d/abstractions/ibus. Can you please consider that?
Also, in Ubuntu 17.10 - 19.04 the im-config change of the abstract
socket path has not been effective in Ubuntu, since
Reopening the ibus (ubuntu) task.
Background:
The change in ibus 1.5.19-1ubuntu3, which set the abstract socket path to
'unix:tmpdir=/tmp/ibus', was upstreamed and is now included in the 1.5.21
source. However, the path proved to not work well on BSD systems:
** Changed in: ibus
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
This bug was fixed in the package ibus - 1.5.19-1ubuntu3
---
ibus (1.5.19-1ubuntu3) eoan; urgency=medium
* ubuntu-use-distinguishable-abstract-address.patch:
Change the default address of ibus daemon to 'unix:tmpdir=/tmp/ibus'
so it has a mediatable abstract socket path
** Changed in: ibus
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
Status in
** Bug watch added: github.com/ibus/ibus/issues #2095
https://github.com/ibus/ibus/issues/2095
** Also affects: ibus via
https://github.com/ibus/ibus/issues/2095
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
IBus is not always launched via im-config when GNOME is involved. In
Ubuntu 19.10 im-config will be disabled by default in Wayland sessions.
So to achieve a consistent address of ibus daemon, it's better to change
the default in ibus itself. Attached please find a debdiff with a
proposed fix.
This bug was fixed in the package im-config - 0.29-1ubuntu12.2
---
im-config (0.29-1ubuntu12.2) xenial-proposed; urgency=medium
* debian/patches/use-distinguishable-abstract-address.patch: adjust
ibus-daemon args to include "--address 'unix:tmpdir=/tmp/ibus'" so it has
a
This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5
---
apparmor (2.10.95-0ubuntu2.5) xenial; urgency=medium
* debian/lib/apparmor/functions, debian/apparmor.init,
debian/apparmor.service, debian/apparmor.upstart,
debian/lib/apparmor/profile-load: Adjust the
I've completed the AppArmor test plan:
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
I've also manually verified the AppArmor portion of this SRU.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member
Just for clarity, I did both the main test case and the extended test
case for im-config. I also noticed that when installing im-config, it
correctly required the updated apparmor.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
FYI, im-config is verification-done. I didn't do full SRU testing for
AppArmor. Tyler, when you are done with the SRU testing, feel free to
mark this as verification-done.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in
Hello Sebastien, or anyone else affected,
Accepted im-config into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/im-
config/0.29-1ubuntu12.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Description changed:
= SRU im-config =
[Impact]
ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has
AppArmor mediation, ibus-daemon does not so it is important that its abstract
socket not
im-config 0.29-1ubuntu12.2 is uploaded to xenial-proposed and ensures
the newer apparmor is installed. Please see the updated description for
im-config in Test Case and Regression Potential for details.
** Description changed:
IMPORTANT: SRU Team, see comment #25 for why this bug is
** Description changed:
IMPORTANT: SRU Team, see comment #25 for why this bug is temporarily
marked verification-failed
= SRU im-config =
[Impact]
ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is
indistinguishable from dbus-daemon abstract sockets. While
Swapping verification-failed for verification-needed now that bug
1579135 has been fixed for ~1 week.
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in
I'm temporarily marking this SRU bug as verification-failed so that it
doesn't get let through until kernel bug 1579135 is fixed. Without the
kernel bug fix for bug 1579135, this SRU has the potential for oopsing
the kernel of some users. Lets sit on this SRU until the Xenial kernel
currently in
Hello Sebastien, or anyone else affected,
Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package apparmor - 2.10.95-4ubuntu4
---
apparmor (2.10.95-4ubuntu4) yakkety; urgency=medium
* debian/patches/allow-access-to-ibus-socket.patch: Adjust the ibus
abstraction to allow access to the abstract UNIX domain socket location
used in Ubuntu.
** Branch linked: lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus,
** Description changed:
= SRU im-config =
[Impact]
ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has
AppArmor mediation, ibus-daemon does not so it is important that its abstract
socket not
This bug was fixed in the package snapd - 2.11+16.10
---
snapd (2.11+16.10) yakkety; urgency=medium
* New upstream release: LP: #1605303
- increase version number to reflect the nature of the update
better
- store, daemon, client, cmd/snap, docs/rest.md: adieu search
** Summary changed:
- Snap blocks access to system input methods (ibus, fctix, ...)
+ Snap blocks access to system input methods (ibus, fcitx, ...)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
36 matches
Mail list logo
