** Package changed: libreoffice (Unity Linux) => 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/1854183
Title:
when compiz have enabled gtk-window-decorator
I'm using 18.04.1, together with gnome flashback (3.28.0-1ubuntu1.3).
For me, night mode only works with one screen, which is the primary
screen. In my case, this is an external screen.
With all 3 screens attached however, night mode however does not work with my
two other monitors:
- one
For some PDFs I can type something in the search field. Seems to be
related to the PDF (if it contains text or not).
--
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/1588197
Title:
Right after upgrading from 16.04 to 18.04, I can't type in evince's
search field any more. Proposed packages where never installed on that
system.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
I still get this message, using FF 62.0, ubuntu 18.04.
--
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/1735529
Title:
Firefox incorrectly blacklists system for WebGL
Status in
@gf I'm still on 16.04 and plan to upgrade this year.
I think this issue should still be about upgrading from 14.04 to 16.04
because 14.04 still is supported and people still upgrade from 14.04 to
16.04 until EOL.
--
You received this bug notification because you are a member of Desktop
@gf I have not upgraded from 14.04.x to 16.04 for a long time. I'm not
sure if this has been fixed in the mean time. I'd rather have a look at
#1592917, and according to #1592917, no fix has been released yet which
would address this issue. When in doubt, I'd rather guess it is not
fixed, but only
I just reproduced the freeze again after switching off wireless devices
with a physical switch in my laptop. After reenabling wireless devices,
videos froze again. Worked around it by changing bluetooth profiles
(away from A2DP and back again).
So this issue is still not fixed.
--
You received
I think that one of the recent updates fixed it (and it also survives
S2RAM):
libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
For me, it's
sudo ls -lah /var/crash/
[sudo] Passwort für thomas:
insgesamt 189M
drwxrwsrwt 1 root whoopsie 682 Jun 9 07:52 .
drwxr-xr-x 1 root root 130 Jul 26 2015 ..
-rwxrwxrwx 1 root whoopsie0 Jun 8 17:19 .lock
-rw-r- 1 thomas whoopsie 155M Jun 6 12:04
I've just seen this error in up-to-date ubuntu 16.04, HES Kernel 4.8.
** Changed in: xorg (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
As bluetooth headsets tend to deal with audio, I assume that the cause
of this issue is somewhere between pulseaudio and bluetooth.
Pulseaudio also deals with bluetooth directly, like in issue #508522. As
long as it is unclear where this issue really comes from, I'll add
pulseaudio package to
@vanvugt Given that this issue is for pulseaudio and deals with
bluetooth, a backport fixing this issue eventually also fixes #1589008.
In case it does, #1589008 eventually is a duplicate, or vice-versa.
In respect to #1589008: I'm really frightened that one day I still
switch bluetooth profiles
Off-topic in terms of this issue:
@b2109455 I have two Arctic P311 (one is ~3 years old and one is ~5
years old). For both, the quality of the microphone is not sufficient to
talk with somebody. I can only use A2DP with it, which is perfectly fine
for me (most of the time).
Can you practically
@anoda I wrote back via #1656065.
--
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/1659988
Title:
Firefox apparmor profile: /usr/bin/python3: error while loading shared
libraries:
Could you add the http link you have visited when FF crashed? Maybe
someone can reproduce it.
Does your FF also crash with apparmor profile disabled?
My experience is that FF tolerates a lot of these apparmor-blocked
actions which are reported in syslog. These logged errors are not
necessarily
unattended upgrades did an upgrade this morning:
libgdm1
That could be the reason for this issue. Eventually, a restart of the
display manager would have avoided this issue after the update.
I'll track this issue for some time and see if it reappears after a
reboot and in regular execution
Attached is an excerpt of my syslog which should contain the relevant
period of time.
** Attachment added: "syslog_excerpt.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1691289/+attachment/4877834/+files/syslog_excerpt.txt
--
You received this bug notification because
Public bug reported:
My gnome desktop session just segfaulted or somehow crashed. Before the
crash, the desktop session was running for hours, it even survived
several s2ram's during the past days.
I did not have these issues for a long time.
My syslog shows up a lot of errors around the crash,
** Also affects: shutter
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #819149
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819149
** Also affects: shutter (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819149
Importance: Unknown
[Typo fixed]: I don't get why especially a major browser can't have its
apparmor profile enabled by default. I get that there is a reason for
that, however.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
@anoda Btw: Apparmor log messages sometimes occur for special tasks.
Like playing a youtube video, opening a file on disk, etc. Maybe that
explains that you see some of these log entries very seldom.
--
You received this bug notification because you are a member of Desktop
Packages, which is
@anoda Yes, on every release of Firefox it is possible that it uses
something which is new to the apparmor profile. However, Firefox somehow
heals itself in most cases.
I don't get why especially a major browser can't have its apparmor
profile enabled by itself. I get that there is a reason for
I'm getting this error for 16.04, since upgrading to latest HWE Kernel
4.8.0-39. Note that I also updated the Xorg packages to
xserver-xorg-*-hwe-16.04.
On top of that, I can also confirm that I get the error message
"Invalid core dump: BFD: Warning: /tmp/apport_core_aiu21o8t
is truncated:
I still get syslog entries
Feb 18 20:16:52 lat61 gnome-session[3090]: ** (gnome-flashback:3185): WARNING
**: Could not assign CRTC to outputs, ignoring configuration
Feb 18 20:16:52 lat61 gnome-session[3090]: ** (gnome-flashback:3185): WARNING
**: Could not make default configuration for
** Summary changed:
- Gnome Flashback: Could not assign CRTC to outputs, ignoring configuration
+ HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in
The path was wrong in #6 (I forgot the /.config/
Copying
/home//.config/monitors.xml
to
/var/lib/lightdm/.config/monitors.xml
fixes this issue for me (see image attached).
Btw.: After upgrade to new HWE/Xorg I had to resize my monitors to get
rid of similar situations for the gnome session
@mitya57 @muktupavels thanks for reporting back.
Directory /var/lib/lightdm was empty in my case:
/var/lib/lightdm# ls -lh #as root user
insgesamt 0
Copying
/home//.config/monitors.xml
to
/var/lib/lightdm/monitors.xml
does not fix this issue.
--
You received this bug notification because
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-flashback (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Here's the full version of VERSION 9
** Attachment added: "usr.bin.firefox_patched"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988/+attachment/4821323/+files/usr.bin.firefox_patched
--
You received this bug notification because you are a member of Desktop
Packages, which is
Found another entry in syslog (when starting FF):
Feb 18 06:45:15 lat61 kernel: [ 1123.988918] audit: type=1400
audit(1487396715.969:78): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}//lsb_release"
name="/usr/bin/python3.5" pid=4722 comm="lsb_release"
I'm using up-to-date ubuntu 16.04
I've seen this issue for the first time, after upgrading to 4.8 HWE
kernel, including xorg-xserver hwe. Kernel is 4.8.0-36-generic
Syslog says:
Feb 18 05:03:35 lat61 gnome-session[2876]: (nautilus:3580): Gtk-CRITICAL **:
gtk_icon_theme_get_for_screen:
@anoda Got it. Maybe someone else who also uses 12.04 does the porting.
For instance, I don't feel responsible for that (I'm not the package
maintainer...).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
And here's the full version with patch VERSION 8 applied. (see
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988/comments/21
how to use it).
** Attachment added: "usr.bin.firefox_patched"
@anoda Yes, only the black/white tab issue got fixed with the update
which officially got released.
Here's a new patch against the official NEW apparmor profile taken from
ubuntu 16.04.
Patch VERSION 8 (please name the version when you reference it
somewhere).
** Patch added:
@anoda Today, the maintainers announced a bugfix release which at least
is supposed to fix the "black/white tab issue":
https://bugs.launchpad.net/bugs/1659922
They backported it for a release for 12.04, too.
I'm not sure if they applied all the rules FF actually requires, or just
a subset of
@wfhammond
12.04:
My usr.bin.firefox_patched originates from FF package which is shipped
with ubuntu 16.04. It is very likely that the apparmor profile shipped
with ubuntu 12.04 is different from that version. As a result, the patch
seems not to be applicable.
Still good to know for other
Patched it in VERSION 7 of my patch, available at
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988/comments/30
--
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/1553763
full profile in VERSION 7
** Attachment added: "usr.bin.firefox_patched"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988/+attachment/4811650/+files/usr.bin.firefox_patched
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Patch VERSION 7
Also covers bug #1553763 (org.gtk.vfs.Metadata was still missing).
** Patch added: "usr.bin.firefox.patch"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988/+attachment/4811649/+files/usr.bin.firefox.patch
--
You received this bug notification because you are
Not a duplicate of bug #1659988 (which is about python 3.5 support).
** This bug is no longer a duplicate of bug 1659988
Firefox apparmor profile: /usr/bin/python3: error while loading shared
libraries: cannot apply additional memory protection after relocation:
Permission denied
--
You
I had the /dev/shm/org.chromium.XX issues with
- Flash plugin DISABLED
- Java plugin DISABLED
Maybe playing a HTML5 youtube video exposes it.
I'm on ubuntu 16.04 (up-to-date), FF 51.0.1, with apparmor profile
activated.
@fevrier Have you tried my patch (version 6) (taken from
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
@es20490446e By its nature (bug description), this is not a duplicate of
bug #1659988 (which is about pyhton3 support). Just that bug #1659988
contains a patch for a number of apparmor related issues.
This
*** This bug is a duplicate of bug 1659988 ***
https://bugs.launchpad.net/bugs/1659988
@blantonradford Thanks for reporting back.
That can easily happen: As documented in my previous comments, I had
black/white tabs already with FF 50. Most users won't have noticed that
because the extension
@sdeziel feel free to to take rules from bug #1659988 patch version 6.
Some are still missing, e.g. python 3.5 support.
--
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/1659922
Title:
@blantonradford Thanks for reporting back.
Please report back in bug #1643200, which is the right place for
black/white tabs.
I assume that your old version of Session Manager was incompatible to
E10S, which is why firefox did not enable it, which is why it worked.
If Session Manager 0.8.1.13
@sziraki.tamas I experienced myself that reading from / writing to files
does not always work, depending on the chosen path. Is that your
problem?
To some extent, I think this is intentional: If firefox could read/write
to any path/file you have permissions as a user, that would render most
of
@kamp000x If you have the same problem with the apparmor profile
disabled, then your problem is not related to apparmor. Then you have a
different problem. Maybe your drivers are not compatible.
>From my side, I can say that, if the issue is related to apparmor, the
E10S issues disappear as soon
Ugly as it is, but mozilla could also maintain profiles for different
feature sets, or distros, respectively.
But there's more: Different versions of FF with different requirements.
The only right place to keep track of that is in the source repo of FF.
Even if Mozilla does not maintain it distro
@sdeziel In the long run, I think that mozilla should provide such a
profile, now that FF's dependencies can change at any time, whereas
distros must roll it out quickly because of security fixes.
Why should all the distros do that independently? There's a lot of
redundancy which could be
*** This bug is a duplicate of bug 1553758 ***
https://bugs.launchpad.net/bugs/1553758
Right. Did not reread the issue number. Sorry for that.
** This bug has been marked a duplicate of bug 1553758
usr.bin.firefox apparmor profile blocks access to meminfo
--
You received this bug
@sdeziel Exactly. To be honest, I have seen your ticket and effort you
did. But I could not figure out what your version of the profile
intended to fix, because that is not documented anywhere.
That could also be the reason why nobody merged it within more than a
year. There's nobody to blaim for
** This bug is no longer a duplicate of bug 1553758
usr.bin.firefox apparmor profile blocks access to meminfo
--
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/1660268
Title:
** This bug is no longer a duplicate of bug 1533232
missing many apparmor rules on Xenial
--
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/1553712
Title:
usr.bin.firefox apparmor
** This bug is no longer a duplicate of bug 1659922
Firefox 51.0.1 does not display pages/shows blank pages.
--
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/1659988
Title:
Firefox
Given that bug #1660268 is very unspecific and does not allow tracking
specific rules, I think that this issue is not a duplicate of bug
#1660268.
** This bug is no longer a duplicate of bug 1533232
missing many apparmor rules on Xenial
--
You received this bug notification because you are a
@sdeziel That was intentional: How should someone keep track of what
your profile fixes if there's no ticket for each rule?
How should a maintainer decide if that should be merged?
Please don't duplicate specific tickets to an unspecific ticket. That
just confuses - at least me.
--
You
@sdeziel Is this somehow related to the E10S issues? Have you been faced
with these issues and do you claim that your apparmor profile fixes
them?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
What happens if you do a
cd /etc/apparmor.d/disable
ln -s ./../usr.bin.firefox
ln -s ./../usr.bin.firefox_patched
?
This is just to test if your problem is at least _related_ to apparmor.
Should be undone after the test as it disables the apparmor profile for
firefox (temporarily weakens
@asgard2 ...followed by a
service apparmor reload
--
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/1659922
Title:
Firefox 51.0.1 does not display pages/shows blank pages.
Status in
@asgard2 Which version of the patch are you using? Which version of
ubuntu are you using? The patch is against 16.04, whereas it's unknown
what it does to 12.04/14.04.
Please try again with "VERSION 6" of the patched full version, as shown
in
I get this message in a row with cups messages:
Jan 31 07:35:09 lat61 systemd[1]: Stopping Make remote CUPS printers available
locally...
Jan 31 07:35:09 lat61 systemd[1]: Stopped Make remote CUPS printers available
locally.
Jan 31 07:35:09 lat61 systemd[1]: Stopping CUPS Scheduler...
Jan 31
Im on xenial 16.04, Kernel 4.4.0-59-generic. Still get this message.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1442050
Title:
(colord:832): Cd-WARNING **: failed to get session
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
@roberto-colnaghi Thanks for reporting back.
I thought you were affected by the black/white tabs, too. If not,
Firefox should be usable at least (and indeed not be broken).
Which problem exactly did the
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
@roberto-colnaghi Indeed, python 3.5 dependency is not the cause for
white/black tabs. But the patch fixes that, too. It fixes every apparmor
blocking I'm aware of in terms of firefox.
--
You received
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
@roberto-colnaghi Not exactly. The patch is against the apparmor profile
of FF only.
Attached, I send the full version of a patched apparmor profile (patched
with VERSION 6)
You can even leave the
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
@roberto-colnaghi Please try out VERSION 6 of the patch. I think it
fixes the [GFX1] issues, too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
@roberto-colnaghi I had similar issues as well. These have all gone in
my case after applying my patch.
I'll post a comment in bug #1643200, eventually some of the affected
users can test it.
--
You
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
@roberto-colnaghi Ah, my error. Thought this was a new issue.
It even gets better: The person who posted these
[GFX1]: Failed 2 buffer db=0 dw=0 for 0, 0, 1920, 876
errors was me.
And from my side, I
Testing so far happened with FF 51.0.1, ubuntu 16.04.
--
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/1660298
Title:
Firefox misses interface org.gtk.vfs.Enumerator
Status in firefox
I can reproduce this issue with and without FF-extension "ubuntu
modifications" enabled.
--
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/1660298
Title:
Firefox misses interface
I've uploaded a patch named VERSION 6 at
https://bugs.launchpad.net/bugs/1659988 which all changes I suggested in
this ticket so far.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
Patch VERSION 6.
Supposed to fix issues
- 1660287 apparmor blocking VFS related operations
- 1660314 apparmor blocking recently added files
regression potential: FF now exposes some other issues like:
ca.desrt.dconf.Writer also needs receive:
Jan 30 13:32:08 lat61 dbus[3005]: apparmor="DENIED"
operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" name=":1.578" mask="receive" pid=3201 label="unconfined"
peer_pid=7811
I just DID reproduce this issue with FF's apparmor profile disabled.
That said, this issue seems to not be related to apparmor profiles.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Also catched a "receive", which is part of VERSION 6 of the patch.
Jan 30 12:45:21 lat61 dbus[3005]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gtk/vfs/mounttracker"
interface="org.gtk.vfs.MountTracker" member="Mounted" name=":1.8"
mask="receive" pid=836
There's more:
dbus (send)
bus=session
interface=org.gnome.GConf.Database,
dbus (send)
bus=session
interface=org.gtk.Private.RemoteVolumeMonitor,
dbus (send)
bus=session
interface=org.freedesktop.DBus,
dbus (receive, send)
bus=session
I CAN'T reproduce this issue EVERY time I click on the upload button.
Just every 2-3 times I click it.
--
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/1660298
Title:
Firefox misses
Public bug reported:
To reproduce this issue with ubuntu 16.04, you must first unblock
org.gtk.vfs.Daemon/Mount via FF's apparmor profile.
When I click the file upload button at https://uploadfiles.io/
then syslog reports:
Jan 30 12:16:19 lat61 org.gtk.vfs.Daemon[3005]: ** (process:3444):
When I disable FF's apparmor profile, nothing is logged to syslog.
That said, it's unclear to me if this is apparmor profile related or
not.
In any case this is not related to the apparmor PACKAGE.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Please also note that I'm in apparmor's reporting mode (which logs an
entry every time apparmor blockes something and which I tested for also
complaining).
The syslog entries mentioned above are thrown WITHOUT entries telling me
that apparmor blocked something. Basically that means that apparmor
For changes I made to FF's apparmor profile to reproduce this issue, see
https://bugs.launchpad.net/bugs/1660287
--
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/1660298
Title:
Firefox
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
Patch VERSION 5.
Here's a new version of the patch which also fixes:
- 1660287 Apparmor blocking FF to access org.gtk.vfs.Daemon and Mount
** Patch added: "usr.bin.firefox.patch"
This issue can be mitigated by adding the following lines to FF's
apparmor profile:
dbus (send)
bus=session
interface=org.gtk.vfs.Daemon,
dbus (send)
bus=session
interface=org.gtk.vfs.Mount,
I've uploaded a patch named VERSION 5 at
Public bug reported:
Taken from syslog:
Jan 30 11:12:29 lat61 dbus[3005]: apparmor="DENIED"
operation="dbus_method_call" bus="session" path="/org/gtk/vfs/Daemon"
interface="org.gtk.vfs.Daemon" member="GetConnection" mask="send" name=":1.77"
pid=18514
@mailing-m1
I uploaded a patch named "VERSION 4" at
https://bugs.launchpad.net/bugs/1659988 which integrates your suggestion
for 14.04. Would you like to retry?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
*** This bug is a duplicate of bug 1659922 ***
https://bugs.launchpad.net/bugs/1659922
Patch VERSION 4.
Here's a new version of the patch which also fixes:
- 1660272 Apparmor blocking Freedesktop interfaces on video playback
- 1660268 Apparmor blocking access to
All 4 apparmor blockings can be mitigated by adding 4 rules to the
apparmor profile:
dbus (send)
bus=session
interface=org.freedesktop.ScreenSaver,
dbus (send)
bus=session
interface=org.gnome.SessionManager,
dbus (send)
bus=system
There's more:
Jan 30 10:25:47 lat61 dbus[3005]: apparmor="DENIED"
operation="dbus_method_call" bus="session" path="/ScreenSaver"
interface="org.freedesktop.ScreenSaver" member="Inhibit" mask="send"
name="org.freedesktop.ScreenSaver" pid=12831
label="/usr/lib/firefox/firefox{,*[^s][^h]}"
Public bug reported:
taken from syslog:
Jan 30 10:25:47 lat61 dbus[3005]: apparmor="DENIED"
operation="dbus_method_call" bus="session" path="/ScreenSaver"
interface="org.freedesktop.ScreenSaver" member="Inhibit" mask="send"
name="org.freedesktop.ScreenSaver" pid=12831
Public bug reported:
Taken from syslog:
Jan 30 10:13:46 lat61 kernel: [212284.232797] audit: type=1400
audit(1485767626.654:46432): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/sys/devices/system/node/node0/meminfo" pid=10696 comm="firefox"
@christoph-thomas I did not propose to disable the apparmor profile. I
just disabled it to demonstrate that the issue is fully related to the
apparmor profile provided by ubuntu and not related to FF upstream.
Later on, I uploaded a patch which fixes the profile itself. With the
patch applied to
@dupondje Not exactly: In my case FF was broken directly after the
update to 51.0.1, without any further change, including configuration
and extensions/plugins.
And yes, by its nature, it's a regression. Not in FF upstream, but in
the ubuntu package (apparmor profile).
The problem itself could
@chrisccoulson I can confirm that the problem can be reproduced with all
FF extensions/plugins disabled.
Since FF 51.0.1, enabling or disabling the extension "ubuntu
modifications" does not fix this issue any more (to my knowledge, that
was the case up until FF 49 and 50).
--
You received this
Google translate translates comment 19 to "Thomas Mayer (thomas303),
after adding the owner /dev/shm/org.chromium.* rw in the patch and
Apparmor profile for Firefox Firefox earned. Thank you. But this is a
crutch, an update on the issue as there was no and no. Employees of
Canonical - Student
@wfhammond My patch is tested by myself against 16.04 only. It's not
tested against 12.04 or 14.04. I'm not sure how that works out, would be
great if you can test it against 12.04, too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@wfhammond It is not necessary to build FF to test my patch from
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988
The patch patches a config file only (an apparmor profile, to be
precise). Can be done in a text editor, too. With the patch applied, FF
51.0.1 should work again.
--
Google translate translates comment #15 to "Thomas Mayer (thomas303),
check yourself, assholes, we need to was a patch that fixes the problem.
Students, blah! Unprofessional!"
Not the feedback I wish to hear for voluntary work.
Не обратной связи я хотел бы услышать о доброволь
A patch which might fix this issue, too, is available at 1659988.
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988
Everyone affected, please give it a try and report back.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
A patch which is known to fix this issue, is available at 1659988.
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988
Everyone affected, please give it a try (take the latest version of the
patch!) and report back.
@Maintainers: This issue duplicates
1 - 100 of 183 matches
Mail list logo
