*** This bug is a duplicate of bug 1856738 ***
https://bugs.launchpad.net/bugs/1856738
@Reinhard, you are now hitting bug #1856738 which prevents @{HOME} from
being used in the peer_addr for an abstract socket. For now, I suggest
updating /etc/apparmor.d/abstractions/ibus to have:
unix (con
FYI, there is a pending update that will go out either tomorrow or early
next week. Please base your next upload on this update.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
*** This bug is a duplicate of bug 1872564 ***
https://bugs.launchpad.net/bugs/1872564
This is a dupe of
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564 which,
AIUI, the server team will be performing an SRU for.
** This bug has been marked a duplicate of bug 1872564
/proc/
** Changed in: pulseaudio (Ubuntu Groovy)
Importance: High => Medium
** Changed in: pulseaudio (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: pulseaudio (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: pulseaudio (Ubuntu Bionic)
Importance: Undecided => Med
FYI, the upload to focal-proposed was superseded by
https://usn.ubuntu.com/4355-1/. Please rebase your changes on that and
reupload.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/187
FYI, the upload to bionic-proposed was superseded by
https://usn.ubuntu.com/4355-1/. Please rebase your changes on that and
reupload.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/18
I'll apply the focal patch to what is in groovy-proposed.
** Changed in: pulseaudio (Ubuntu Groovy)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: pulseaudio (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification becaus
Uploaded
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu5 to
groovy based on 1:13.99.1-1ubuntu4 from groovy-proposed.
** Changed in: pulseaudio (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Rather than superseding 1:13.99.1-1ubuntu4 in groovy-proposed, I instead
based the changes in 1:13.99.1-1ubuntu5 on top of 1:13.99.1-1ubuntu4 to
address the CVE that was fixed in https://usn.ubuntu.com/4355-1/.
** Also affects: pulseaudio (Ubuntu Groovy)
Importance: High
Assignee: Kai-Heng
I suggest following/participating in the discussion in the forum topic
for snapd/ecosystem updates and use this bug to track chromium-browser's
use of those updates.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubun
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1071392
Title:
Firefox 16.0.2 stable update
Status in “firefox” pa
Encrypted home is typically setup as ~/.Private, not ~/Private and the
policy already allows:
owner @{HOME}/.Private/** mrixwlk,
owner @{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,
The home interface should already allow ~/Private. What is the denial
you see in the logs?
--
You received this
Ok, that is a read on /home/ubuntu/.Private/. Is the encrypted home
mounted at the time of the denial?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1848919
Title:
[snap] Pe
Ok, I'll fix this in the next batch of policy updates for snapd.
** Changed in: snapd (Ubuntu)
Importance: Undecided => Low
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
** Changed in: evince (Ubuntu)
Status: Confirmed => Triaged
** Changed in: evince (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
I've added it to my trello card for 2.43 policy updates.
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1851211
Tit
Note, these accesses were added in
22d37f834b6f4605faa3887bae3cf4d0e1673278
** Changed in: gnome-system-monitor (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubu
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1848919
Title:
[snap] Permission denied on Private encrypted folder
Status
Nov 11 09:47:56 kernel: audit: type=1400
audit(1573487276.018:797080): apparmor="DENIED" operation="open"
profile="snap.gnome-system-monitor.gnome-system-monitor"
name="/run/systemd/sessions/c1" pi d=8733 comm="gnome-system-mo"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
I'm able to repr
Clement, your issue is different than Charles'. More information is
required from you to triage your issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1778332
Title:
** Changed in: snapd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1851211
Title:
[snap] SoloKeys not supported by u2f-devices
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
Installing 1:11.1-1ubuntu7.5 from bionic-proposed, the test plan and
James' addition for mediation is preserved across snapd restart all
works as expected. Marking as verification done.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug n
Installing 1:8.0-0ubuntu3.11 from xenial-proposed, the test plan and
James' addition for mediation is preserved across snapd restart all
works as expected. Marking as verification done.
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if
https://github.com/snapcore/snapd/pull/7779
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => In Progress
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd
Assignee: (unassigned) => Jamie S
https://github.com/snapcore/snapd/pull/7779
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
** Changed in: snapd
Importance: Undecided => Low
** Changed in: snapd
As
OTOH, I think it makes sense to allow for the ability to share
~/.pki/nssdb (and yes, a personal-files addition along with a snap
change (perhaps just a symlink from $SNAP_USER_DATA/.pki/nssdb to
~/.pki/nssdb would be enough rather than patching?).
For read access, I have no problem with using per
$ aa-decode
2F686F6D652F7361726E6F6C642F736E61702F6368726F6D69756D2F313032362F2E636F6E6669672F6368726F6D69756D2F44656661756C742F53796E6320446174612F53796E63446174612E73716C697465332D6A6F75726E616C
Decoded: /home/sarnold/snap/chromium/1026/.config/chromium/Default/Sync
Data/SyncData.sqlite3-journa
Seth, I suspect if you stop the snap and restart it, these errors will
go away.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1864127
Title:
apparmor denies ~/snap/chromium/
pparmor (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: apparmor (Ubuntu Focal)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bu
hanged in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1848919
Title:
[snap] Permissi
** Changed in: snapd
Status: In Progress => Fix Released
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/b
All that said, Daniel and Jean-Baptiste, I installed 20.04 in a vm and
tried to reproduce this and could not. The apparmor change was about
correctness of the unit so I performed the upload, but I also hoped that
it would address the issue you are seeing.
I'm not certain it will. On one boot, prio
Daniel responded on irc and said after several reboots with the new
apparmor, everything was fine on every boot (though his critical-chain
has var.lib.mount listed).
My attached systemd-analyze plot svg shows that apparmor.service is
indeed starting after var.lib.mount on the VM where the critical
Daniel, this is a different cause but same result:
zfs-load-module.service (2ms)
zfs-import-cache.service (8ms)
zfs-import.target
...
var-lib.mount (69ms)
...
snap-multipass-1869.mount (1.358s)
...
apparmor.service (279ms)
...
In this case, apparmor correctly waited for var.lib.mount, but multipa
Adding a snapd Ubuntu task, marking as In Progress and assigning to mvo
since he is preparing a 20.04 upload.
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu Focal)
Assignee: (unassigned) => Michael Vogt (mvo)
** Changed in: snapd (Ub
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
I confirmed that https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html shows no autopkgtest regression for
xenial.
I also ran through the TEST CASE for this bug and xenial passed. Marking
verification-done-xenial
** Tags removed: verification-failed-xenial
**
I confirmed that https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html shows no autopkgtest regression for
bionic.
I also ran through the TEST CASE for this bug and bionic passed. Marking
verification-done-bionic.
** Tags removed: verification-failed verific
FYI, in recent PR discussions[1] we've acknowledged that we should make
it easier to allow different URL schemes into snapd and I laid out some
criteria/process ideas on how to make this happen, and I applied that
criteria to the zoommtg PR and it was merged quickly. I discussed with
Samuele that w
@Christina - I suggest filing a new bug with more specifics. That said,
I suspect you have a .dpkg-dist file in /etc/apparmor.d or
/etc/apparmor.d/abstractions that has changes that need to be merged
into your evince profile.
--
You received this bug notification because you are a member of Deskt
Ubuntu 14.04 LTS is now out of standard support and evince is not
included in ESM.
** Changed in: evince (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bu
** Tags removed: apparmor
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1826415
Title:
Videos do not play in presentation mode
Status in Evince:
New
Status in evince package in Ubu
You can 'sudo snap connect chromium:mount-observe' for /etc/fstab.
/run/mount/utab is more complicated and you can read about it here:
https://forum.snapcraft.io/t/namespace-awareness-of-run-mount-utab-and-
libmount/5987
For the /run/udev/data accesses, can you paste the output of:
$ cat /run/ude
(nemo:31811): CinnamonDesktop-WARNING **: 01:08:30.200: Error creating
thumbnail for smb://akem-
hp.local/comics_bds_mangas/Scrooge/Uncle%20Scrooge%20(001-100)%20GetComics.INFO/029%20Uncle%20Scrooge.cbr:
Unrecognized image file format
This suggests that the problem is not due to the apparmor profi
** Description changed:
+
+ # Original summary: pulseaudio built with --enable-snappy but 'Enable
+ Snappy support: no'
+
+ # Original description
+
From https://launchpadlibrarian.net/377100864/buildlog_ubuntu-cosmic-
amd64.pulseaudio_1%3A12.0-1ubuntu1_BUILDING.txt.gz:
...
dh_auto_c
** Attachment added: "test-snapd-audio-record_1_amd64.snap"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5292539/+files/test-snapd-audio-record_1_amd64.snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Attaching test-snapd-pulseaudio and test-snapd-audio-record snaps.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1781428
Title:
please enable snap mediation support
Status in pul
** Description changed:
+ [Impact]
+ Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
** Changed in: pulseaudio (Ubuntu Xenial)
Status: In Progress => Triaged
** Changed in: pulseaudio (Ubuntu Bionic)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https:/
Thank you for using Ubuntu and reporting a bug.
Are you using wayland or Xorg for your desktop session? What password
manager are you using?
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, w
** Changed in: snapd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1851211
Title:
[snap] SoloKeys not supported by u2f-devices int
Note, there is a spread test in snapd that checks for if the mediation
patches are dropped (or added). While it is fine for
https://launchpad.net/bugs/1856054 to be fast tracked, this pulseaudio
bug should not be marked as Fix Released before the end of year break
unless you coordinate with the sna
@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
/etc/apparmor.d/tunab
** Package changed: apparmor (Ubuntu) => firefox (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1482852
Title:
apparmor profile usr.bin.firefox missing abstractions/ubuntu-he
** Changed in: apparmor
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1848919
Title:
[snap] Permission denied on Private encrypted fold
libreoffice ships this profile, so the bug should be tracked there.
** Package changed: apparmor (Ubuntu) => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1849
For the next libreoffice upload, the non-/home read-only accesses all
look fine to add to the libreoffice profile.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1849680
Title:
au
)
Status: New => In Progress
** Changed in: im-config (Ubuntu Yakkety)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.ne
** Changed in: im-config (Ubuntu Yakkety)
Status: In Progress => Fix Committed
** Changed in: im-config (Ubuntu Xenial)
Status: New => In Progress
** Changed in: im-config (Ubuntu Xenial)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: im-confi
** Changed in: im-config (Ubuntu Xenial)
Status: In Progress => Triaged
--
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 metho
** Description changed:
- Currently snaps can't access ibus/fcitx from the system, do we need a
- interface for input methods there?
+ = 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
** 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 be
** Changed in: snapd (Ubuntu Yakkety)
Status: Incomplete => Confirmed
--
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
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu Xenial)
Status: New => Triaged
** Changed in: apparmor (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Xenial)
Importance: Undecided => Medi
Tyler said that he would update the apparmor ibus abstraction for this
change, which will be required to not break ibus in evince and
webbrowser-app. As such, I'm going to mark this as 'verification-failed'
then adjust im-config to Breaks with apparmor less than the version
Tyler is uploading.
**
Thanks for working on this! Per the snappy team, this will also need a
SRU for xenial.
** Also affects: pulseaudio (Ubuntu Yakkety)
Importance: High
Assignee: Luke Yelavich (themuso)
Status: Fix Released
** Also affects: pulseaudio (Ubuntu Xenial)
Importance: Undecided
St
Adding xenial task and marking triaged since a fix is available in
yakkety. Who will be providing this update?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057
Title:
Deny au
** Changed in: pulseaudio (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057
Title:
Deny audio recording for all snap applications
FYI, fcitx uses dbus-daemon (as opposed to ibus-daemon, which does not)
and so apparmor dbus mediation can be used with 'dbus bus=fcitx,'. As
such, im-config does not need an update for fcitx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Based on comment #15 I removed im-config 0.29-1ubuntu12.1 from xenial-
proposed so it doesn't accidentally get promoted.
--
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:
Ok, I looked at this quite a bit today. I'll summarize some stuff that
was already said to justify the path forward.
1. bug #1509829 reports that the lightdm guest session fails to start fcitx and
mozc input methods
2. the fix as implemented was to create apparmor abstractions for fcitx and
mozc
Marking the bug as Triaged since comment #8 describes how to fix the
bug.
** Changed in: lightdm (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/15
What 'click review code' are you referring to? If
https://code.launchpad.net/~store-reviewers/click-reviewers-tools/trunk
it can absolutely review snaps-- it reviews clicks, 15.04 snaps and
series 16 (all snaps) just fine and is what the store uses today to
review all store apps.
--
You received
@Simon, thanks, I'll work on sponsoring this.
@Zygmunt, I'm not sure this is the patch to upstream-- it is the phase 1
approach and the phase 2 approach is pulseaudion/trust-store/snappy
interfaces which we will be discussing this week.
--
You received this bug notification because you are a mem
** Changed in: pulseaudio (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057
Title:
Deny audio recording for all snap appl
@Simon, couple of small things:
* you should use 8.0-0ubuntu3.1 as the version instead of 8.0-0ubuntu4
* the changelog has a date of 'Tue, 17 May 2016 17:59:58 +0200' which is quite
old, yet the diff was only recently uploaded. You can use 'dch -r' to update
the date
More importantly:
* the pat
** Changed in: pulseaudio (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: pulseaudio (Ubuntu Xenial)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu
The functionality does not work as expected and I am able to record when
running parecord under an apparmor profile that starts with 'snap.' (see
attached).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bug
I should mention that when testing this installed test packages then
logged out of my session, killed my user's pulseaudio then logged back
in. I suppose I could have also done 'killall pulseaudio' and have it
restart automatically instead.
--
You received this bug notification because you are a
The functionality does not work as expected and I am able to record when
running parecord under an apparmor profile that starts with 'snap.' (see
attached).
** Attachment added: "1583057-test.sh"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4696048/+files/15830
** Description changed:
- Until we have a proper trust-store implementation with snappy and on the
- desktop/ubuntu core we want pulseaudio to simply deny any audio
- recording request coming from an app shipped as part of a snap.
+ [Impact]
+ Currently snaps on Ubuntu Classic may declare in thei
@Simon, finally, in reading the patch this will affect both strict and
devmode and so the patch should "if startswith 'snap.' and process is in
enforce mode ; then block recording".
This will be needed for the phase 2 implementation as well, so it is not
wasted effort. I've asked the apparmor devs
@Simon, per the SRU process, I've done the paperwork to pursue the SRU
but leaving this as 'In Progress' due to my comments. Please attach an
updated debdiff and I'll review and adjust the bug as appropriate.
--
You received this bug notification because you are a member of Desktop
Packages, whic
** Description changed:
- [Impact]
+ [Impact]
Currently snaps on Ubuntu Classic may declare in their snap.yaml that they
want access to pulseaudio. When installed, snapd will auto-connect the
pulseaudio interface giving the snap access to the pulseaudio server for
playback and recording. Bec
@Simon, thanks for the updates. It looks I did not have the module-
snappy-policy module loaded and appreciate the update to default.pa and
the updated patch that addresses the other issues.
The only remaining issue is making sure that recording continues to work
in devmode. I think you will want
Could this be related to https://bugs.launchpad.net/bugs/1604872 ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1603904
Title:
X apps that use dbus (GTK, Firefox) either don't s
Note I was seeing this in zesty for a while (then didn't):
https://bugzilla.gnome.org/show_bug.cgi?id=772476
** Bug watch added: GNOME Bug Tracker #772476
https://bugzilla.gnome.org/show_bug.cgi?id=772476
--
You received this bug notification because you are a member of Desktop
Packages, whic
I still have console-setup 1.166ubuntu4 so decided to poke at this more.
I can confirm that 'sudo udevadm trigger' causes the ctrl+c to logout of
Wayland. It does not cause a logout of gnome-shell under X. I then found
that 'udevadm trigger --subsystem-nomatch=tty' does not cause the issue
under wa
Closing the snappy task-- while we might want to adjust its use of
udevadm trigger, it is clear that running this command should not break
the wayland desktop, just like it doesn't under X.
** Changed in: snappy
Status: New => Opinion
** Changed in: snappy
Status: Opinion => Won't F
I just now upgraded to 1.166ubuntu5 and no longer see the issue. To
ogra's point, I use encrypted lvm and was able to enter a password and
have everything work like normal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ub
@Mathieu, while I understand the wayland gnome-shell desktop session is
not supported on zesty or xenial, I wonder if this should be SRU'd to
those releases?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://b
The forum thread is enough IMO for this improvement (as opposed to bug
fix) and it is in trello.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through
Public bug reported:
After upgrading from zesty to artful, media keys don't work right and
the terminal is very slow to launch. Eg:
ctrl+alt+t
wait 20 seconds
terminal pops up
I see this in the logs:
Jul 24 11:08:37 iolanthe /usr/lib/gdm3/gdm-wayland-session[12104]: Failed to
activate service '
This seems to be related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1456134
Which describes how on reboot, things work ok, but on logout/login they
do not.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubu
Note that I still see this even when the terminal comes up fast:
Jul 24 11:12:48 iolanthe org.gnome.SettingsDaemon.MediaKeys.desktop[6820]:
Warning: DESKTOP_STARTUP_ID not set and no fallback available.
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Summary changed:
- org.gnome.SettingsDaemon.MediaKeys.desktop: Warning: DESKTOP_STARTUP_ID not
set and no fallback available.
+ /usr/lib/gdm3/gdm-wayland-session[12104]: Failed to activate service
'org.gnome.keyring': timed out
--
You received this bug notification because you are a member
** Changed in: pulseaudio (Ubuntu Xenial)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583057
Title:
Deny audio recording for all snap ap
901 - 1000 of 1289 matches
Mail list logo
