** Package changed: libreoffice (Unity Linux) => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854183
Title:
when compiz have enabled gtk-window-decorator libreoffice-calc
For older kernels, there are no such warnings:
update-initramfs: Generating /boot/initrd.img-5.3.0-62-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
cryptsetup: WARNING: could not determine root device from /etc/fstab
update-initramfs: Generating
uname -a
Linux lat61 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
sudo apt-get upgrade
reports:
update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
For the record in terms of Google's Chrome browser: Google announced
that they plan to block http downloads when the user comes from a https
page.
Source: https://www.xda-developers.com/google-chrome-block-insecure-
downloads-https-pages/
--
You received this bug notification because you are a
Mate-applets merged https://github.com/mate-desktop/mate-
applets/pull/409 to work around the libgtop issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835332
Title:
Add support for NVMe
A quick fix could be to document at
https://help.ubuntu.com/community/ReportingBugs that the error reporting
must be switch on first.
On top of that, ubuntu-bug could output a warning message that the error
reporting must be switched on first (and how/where this can be done).
--
You received
A patch was provided at https://github.com/mate-desktop/mate-
applets/issues/290
** Bug watch added: gitlab.gnome.org/GNOME/libgtop/issues #43
https://gitlab.gnome.org/GNOME/libgtop/issues/43
** Also affects: libgtop via
https://gitlab.gnome.org/GNOME/libgtop/issues/43
Importance:
Public bug reported:
The system load monitor applet 3.28.0 does not show disk I/O when NVMe
disks are used (white box in the screen shot). This is because NVMe
devices are named e.g. /dev/nvme0n1 instead of e.g. /dev/sda1.
This is a tracking bug. To be fixed via
gnome-applets:
For this to work, I had to enable the error reporting switch in system
settings/privacy protection.
With error reporting enabled, the browser window opened.
This is not a bug, but I'm not very happy with the behaviour:
- Having error reporting switched off, I should be able to enforce it via
Documentation says (after having pressed the "send" button):
"Apport will then upload the problem information to Launchpad, and a new
browser window will then open to inform you that the bug report is being
processed."
https://help.ubuntu.com/community/ReportingBugs
--
You received this bug
I'm using ubuntu 18.04 with all updates installed.
When I type
ubuntu-bug gnome-applets
then it does not open the browser window when I click on the "send"
button.
When i type
xdg-open http://bugs.launchpad.net
then the corresponding page opens perfectly fine in Firefox 67.0.4.
This is
@mpt There's also non-public mirrors in the field which have never been
on the list of mirrors. And never will be.
For public mirrors on the list, how would Canonical know about a
compromised mirror _before_ a victim downloads from it?
I'm still very happy with having https'ed mirrors, because
@seth-arnold
There we go and let an imaginary grandma (she's a non-DD) verify an
ubuntu ISO image via gpg. Of course, she will know by herself which DSA
key IDs are trusted and not just extract the (MITM-compromised) IDs from
the (MITM-compromised) SHA256SUMS.gpg as described in
I'd like to sum it up like this: Users should _download_ from a mirror
but they should neither _trust_ the download of the mirror nor the
checksums a mirror provides.
It's even the other way round: Having mirrors in the game makes it _even
more_ important that checksums are provided by Canonical
Here's a perfect illustration how NOT to protect against MITM:
http://www.system-rescue-cd.org/Download/
Assumed, the attacker _can_ attack via MITM, then
1. the attacker can let the download link point somewhere else (e.g. to a
compromised download).
2. the attacker can _also_ show a checksum
In respect to the above discussion TJ posted:
Please be aware that https-securing mirrors does in fact not necessarily
increase the trustworthyness of the download. Reason:
An attacker could compromise a mirror's downloads (e.g. via stolen
credentials or via MITM while the mirror downloads via
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
In 18.04.1 Server, I was able to freshly install with two luks encrypted
devices which I already added during the partitioning step.
Later on, I changed the generated /dev/mapper/... names in /etc/crypttab
and /etc/fstab and continued with a
dmsetup rename OLD_NAME1 NEW_NAME1 #avoids errors in
I've just seen this infinite loop in 16.04 with kernel 4.15.
For me, this was just a leftover because I was transitioning from
software raid to btrfs raid. Therefore, I had commented out the old
software raid definition in /etc/mdadm/mdadm.conf. Which in turn brought
me to the loop problem.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588197
Title:
Can't type anything
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588197
I've hit this issue right after upgrading from 16.04 to 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
I still get this message, using FF 62.0, ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735529
Title:
Firefox incorrectly blacklists system for WebGL
To manage notifications about
I've just seen this issue after upgrading from 16.04 to 18.04. Burning
DVDs worked but burning CDs didn't.
I worked around it via https://askubuntu.com/questions/1032903/problem-
with-k3b-in-18-04-releases-cdrecord-has-no-permission-to-open-the-
devi/1034927 with a
sudo chmod 4711
@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 Ubuntu
Bugs,
@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
Newly released 2.1.4 does the trick. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784168
Title:
gscan2pdf 2.1.3 not sends E-Mail (regression)
To manage notifications about this bug go
Public bug reported:
I just upgraded gscan2pdf 1.3.9 to the ppa version 2.1.3, still using
ubuntu 16.04.
After the upgrade, sending pdf via email no longer works whereas it
worked before with 1.3.9 (regression). As a mail program, I'm using
thunderbird as before.
Attached is the dialog box:
Public bug reported:
A while ago, I reported a regression because G4 compression did not work
any more in recent versions of ubuntu:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/482673 .
My bug report led to the disablement of G4 compression. This somehow
restores user satisfaction,
That was due to a running docker instance which was using port 3306 so
that restarting the mysql server failed.
After stopping the docker instance I could just run apt-get upgrade and
the update completed as usual.
This is not a bug. Close this issue.
** Changed in: mysql-5.7 (Ubuntu)
That was due to a running docker instance which was using port 3306 so
that restarting the mysql server failed.
After stopping the docker instance I could just run apt-get upgrade and
the update completed as usual.
This is not a bug. Close this issue.
** Changed in: mysql-5.7 (Ubuntu)
Public bug reported:
auto generated bug report
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.22-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Public bug reported:
auto generated bug report
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server 5.7.22-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture:
@sabdfl In 2018, I would not download ubuntu in Turkey and Egypt.
https://www.bleepingcomputer.com/news/security/turkish-isp-swapped-
downloads-of-popular-software-with-spyware-infected-apps/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@seth-arnold.
https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-
ubuntu?backURL=%2F#1
takes me to
http://releases.ubuntu.com/16.04/
How stupid is that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701572
Title:
[regression] bluetooth headset not connecting after regular update
To
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
Looks as if one of these updates improved it for S2RAM, but not for
hardware switch (I mean a real physical switch in my laptop for all
wireless hardware)
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
I worked around it.
I had to remove --purge
bluetooth bluez blueman bluetooth pulseaudio pulseaudio-module-bluetooth
Then I removed all pairing information with devices, both in
~/.config/pulse and /var/lib/bluetooth
Then rebooted
Then paired my A2DP device again, this time with blueman.
Then
When I try to connect the headset (which still seems to pair), I see the
little lock next to the bluetooth device for ~0.5 seconds. Then the lock
disappears.
Syslog reports:
Jun 30 16:00:40 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for
00:1A:7D:70:08:7E: Protocol not available
Jun
Public bug reported:
Hi, my bluetooth headset Arctic P311 was connecting until I installed
these updates:
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
I get the same error with ubuntu 16.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584512
Title:
gnome-flashback crashed with SIGSEGV
To manage notifications about this bug go to:
I'm getting this on up-to-date ubuntu 16.04.2 with latest HES kernel
4.8.0-56. My system has become instable with gnome-flashback breaking
over and over.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've seen this again now:
- Shutter is loaded as a tray icon:
https://storage4.static.itmages.com/i/17/0612/h_1497254345_7516840_9007c67980.png
- Go into s2ram mode with a pm-suspend
- after resume, ubuntu asks if the shutter crash should be reported AND the
gnome session got reset, with all
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515972
Title:
Public bug reported:
An error
"shutter crashed with SIGSEGV in raise()"
happens to me from time to time, especially after suspend to ram.
Now that I have shutter configured to be loaded as a tray icon, this
error distroys my current user session. Every desktop application is
inaccessible after
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659988
Title:
Firefox apparmor profile: /usr/bin/python3: error while loading shared
libraries: cannot apply
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
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,
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
@petrosyan I'm still on fully up-to-date 16.04, Kernel 4.8 via HES
packages.
I've just seen this again in syslog:
gnome-session[3496]: I/O warning : failed to load external entity
"/home/userX/.compiz/session/106261e716d9321ea114949725822646160034960003"
This time, my whole gnome session
*** This bug is a duplicate of bug 1540399 ***
https://bugs.launchpad.net/bugs/1540399
My problem fully relates to
https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1469840
No need to track this here any more.
** No longer affects: shutter (Debian)
--
You received this bug
The patch of comment 2 seems not to be applied to the ubuntu 16.04
package.
By applying it to /usr/bin/shutter, sending E-Mails from shutter now
works for me.
I attached the patch I used therefore (which does the same as the patch
from comment 2, just for ubuntu 16.04).
** Patch added:
*** This bug is a duplicate of bug 1540399 ***
https://bugs.launchpad.net/bugs/1540399
Debian fixed this via https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=819149:
Date: Tue, 06 Dec 2016 21:53:19 +0800
Source: shutter
Binary: shutter
Architecture: source
Version: 0.93.1-1.1
Distribution:
** 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
*** This bug is a duplicate of bug 1540399 ***
https://bugs.launchpad.net/bugs/1540399
I get this error on fully patched 16.04, when trying to e-mail shutter
screen shots:
Fehler beim Ausführen von 'xdg-email'
Which translates to:
Error when executing 'xdg-email'
--
You received this bug
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@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
@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 Ubuntu
Bugs, which is
I've just seen this with 16.04, together with latest HES 4.8 kernel:
uname -a
Linux server 4.8.0-51-generic #54~16.04.1-Ubuntu SMP Wed Apr 26 16:00:28 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
That happened during a btrfs-scrub:
May 7 02:11:52 server kernel: [17884.471597] []
Public bug reported:
Syslog logs systemd trying to restart logind every few seconds:
May 7 00:51:29 server systemd[1]: Starting Login Service...
May 7 00:51:54 server systemd[1]: systemd-logind.service: Main process exited,
code=exited, status=1/FAILURE
May 7 00:51:54 server systemd[1]:
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 removed debian's package and installed ubuntu's fixed version of ttf-
mscorefonts-installer (3.4+nmu1ubuntu2). Works great now. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607535
Title:
Public bug reported:
After a reboot, syslog reports:
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
As it turned out, the leftern part of the right screen is already part
of the right screen (not a overstretched part of the left screen.
To illustrate it, I marked it red on a photo (attached).
Still: 80% of the second screen remain black, as long as the login
process is not finished.
**
Public bug reported:
I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.
On dual screen setup, during system login, the first screen stretches
over a part of the second screen (about 25% of it), whereas the rest of
the second screen is black. Like this:
#
That got scrambled. Should be:
_
#--#_#<<|...#
#-Login#_#<<|.Black.#
#--#_#<<|...#
_
Again, The part marked with "<<" is the rightest part of the background
image of the first screen.
--
You received this bug
I've seen this in 16.04 today (kernel 4.8):
Feb 18 06:27:03 lat61 gnome-session[3242]: compiz (core) - Info: Starting
plugin: session
Feb 18 06:27:03 lat61 gnome-session[3242]: I/O warning : failed to load
external entity
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 Ubuntu
Bugs, 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:
Tracked it further down (ubuntu 16.04).
On a fresh boot
- bluetooth device connects, with sound enabled (I configured bluetooth to
default to bluetooth sound device on connect)
- video playback does not stop
- Sound is played perfectly fine.
After a suspend to ram and suspend
- bluetooth
@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 Ubuntu
Bugs, which is subscribed to 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
I can confirm this bug for up-to-date xenial (16.04). Note that this is
a regression for me, which happened within xenial's updates (it was
working a few weeks ago with xenial).
ehler beim Starten der Domain: Kann keine Daten empfangen: Die
Verbindung wurde vom Kommunikationspartner zurückgesetzt
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553763
Title:
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 Ubuntu
Bugs, which is subscribed to
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659922
Title:
Firefox 51.0.1
@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
1 - 100 of 452 matches
Mail list logo