OK,
I have now tested this new apt (1.4.1) against the old version (1.4).
My setup is using solely systemd (with no upstart nor cgmanager installed).
I have fast SSD's, so my normal booting time is about 4 seconds.
Now after upgrading to apt 1.4.1 the booting time to GDM increased with about 5
** Also affects: sosreport (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: sosreport (Ubuntu Zesty)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Zesty)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Trusty)
Assignee:
This bug was fixed in the package nagios-plugins-contrib -
16.20151226ubuntu0.16.04.1
---
nagios-plugins-contrib (16.20151226ubuntu0.16.04.1) xenial; urgency=medium
* pmp-check-unix-memory: Consider MemAvailable if available in
/proc/meminfo. (LP: #1610878)
-- Christian Biamont
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
** Tags removed: trusty ubiquity-2.17.1
** Tags added: artful ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261175
Title:
[wishlist] F2FS missing in Ubiquity "Use as" partition option
To
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
** Changed in: ubuntuone-client
Assignee: (unassigned) => roopa (roopat85)
** Changed in: ubuntuone-client (Ubuntu)
Assignee: (unassigned) => roopa (roopat85)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
So, I think the issue occurs because of the pte_lockptr lock being used
on a PMD and is incontention with the lock on the same PMD. There are
several possible points where this can happen, for example, pages being
migrated on NUMA systems (unlikely in most of these bug reports) or even
mremap()
On 2017-03-22 04:02 PM, Eduardo Otubo wrote:
> On Wed, Mar 22, 2017 at 07=28=12PM -, Simon Déziel wrote:
>> On 2017-03-22 03:08 PM, Eduardo Otubo wrote:
>>> These patches are intended to 2.9, but will be able to be backported.
>>> What's the urgency of this issue? Do you need a hotfix for it
Can you give us exact commands to reproduce it? The example in the
original post looks like you're running cargo, not rustc directly. Does
it still occur if you move ~/.cargo away somewhere else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Okay, if you are typing on the laptop but
/proc/acpi/button/lid/LID/state is closed, then it's a kernel bug,
systemd can't do much here...
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hey!
What a wonderful news from our best friend I've just read, you may
read it yourself here http://inmovivienda.co/everything.php?6667
Best wishes, onecatharsis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2735
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677239
Title:
It happens when compiling this project:
https://github.com/plietar/librespot
I tried with .cargo purged and such.
Also have tried with full updated dependencies. Always the same problem since
the new rustc.
The command that is executed by cargo is:
`rustc --crate-name serde_derive
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680421
Title:
Computer suspends/sleeps before login
To
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606959
Title:
DPI setting is not correctly calculated on Ubuntu
Is this also occurring with Unity too then? What about GNOME Shell? I
get it in the Snap (and the original report was me seeing it on GNOME
Flashback on 16.10) but I haven't seen it in the Deb on Unity or GNOME
Shell yet.
--
You received this bug notification because you are a member of Ubuntu
Recently I can definitely reproduce the issue anytime.
It's extremely annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage
Another test "Openssl speed"
[Without patch]
$ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 2217067
** Tags removed: kernel-adt-failure-lts-trusty
** Tags added: kernel-adt-failure-lts-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672397
Title:
bcmwl 6.30.223.248+bdcom-0ubuntu0.2 ADT test
Public bug reported:
wifi problems, also ethernet not working but a loto of people seem to have the
same issue :)
thanks a bunch!
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
** Tags removed: kernel-adt-failure-lts-trusty
** Tags added: kernel-adt-failure-lts-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672399
Title:
blktap-dkms 2.0.93-0.3ubuntu6~14.04.1 ADT
** Tags removed: kernel-adt-failure-lts-trusty
** Tags added: kernel-adt-failure-lts-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672402
Title:
flashcache 3.1.1+git20131019-1 ADT test
Hello Victor, or anyone else affected,
Accepted sssd into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sssd/1.13.4-3ubuntu0.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
thanks for the work, as said on IRC I would vote for starting the cycle
with easy merges and syncs and wait for the initial archive sync to go
through britney before adding more transitions but if somebody is
wanting to go ahead and is ready to deal with the extra work it might
create I'm not
Marc Singer, could you please tell me which kernel version this is? And you say
it's the official ubuntu repos, not the custom kernel ppa?
I've managed to compile and install 4.11-rc5 without too many issues, but an
official fix would be wonderful.
--
You received this bug notification
For joseph's kernel: Install it, then proprietary drivers. It works a
charm! New kernel also now supports my Gigabyte gc-wb867d-i wifi!
Thank you so much! Sorry folks for so the number of comments in a row,
if there were an edit button I'd be using it. :-)
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2735
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672955
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Hello Guys
Seems AMD_PINCTRL has been excluded from official sources; I've built 2
new kernel versions today and both of them had AMD_PINCTRL disabled,
even though I applied all the patches from kernel.ubuntu.org.
Could someone please check if the newest stuff works without compiling a
custom
The pdf displays fine in 16.04 so considering it fixed in the current
series
** Changed in: evince (Ubuntu)
Importance: Undecided => High
** Changed in: evince (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The verification of the Stable Release Update for appstream has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Bug watch added: GNOME Bug Tracker #701537
https://bugzilla.gnome.org/show_bug.cgi?id=701537
** Changed in: evince
Importance: Medium => Unknown
** Changed in: evince
Status: Invalid => Unknown
** Changed in: evince
Remote watch: GNOME Bug Tracker #772597 => GNOME Bug Tracker
not sure what you describe but that doesn't seem a problem in the evince
pdf viewer
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
** Changed in: evince (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
thank you for your bug report, what database are you speaking about?
evince is a pdf viewer
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
** Changed in: evince (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package python-os-brick - 1.2.0-2ubuntu0.3
---
python-os-brick (1.2.0-2ubuntu0.3) xenial; urgency=medium
* d/p/Stop-calling-multipath-r-when-attaching-detaching-iS.patch: Backport
Backport fix for stopping calling 'multipath -r' (LP: #1623700)
--
The verification of the Stable Release Update for python-os-brick has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Hello gravy45, or anyone else affected,
Accepted caja into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/caja/1.18.1-0ubuntu2
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 ido - 13.10.0+14.04.20170403-0ubuntu1
---
ido (13.10.0+14.04.20170403-0ubuntu1) trusty; urgency=medium
* IdoCalendarMenuItem: disconnect from parent signals on item
destruction (LP: #1506427)
-- Marco Trevisan (Treviño) Mon,
I had the same issue with different packages (namely texlive-related
packages) during a distribution update from 16.10 to 17.04, resulting in
an incomplete upgrade. After a couple hours of trying to fix the issues,
I finally suspected Sophos, and disabling/enabling on-access scanning
worked around
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
*** This bug is a duplicate of bug 887821 ***
https://bugs.launchpad.net/bugs/887821
Still present in Ubuntu 16.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010132
Title:
Show copy
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be
meaningful.
Please do not hesitate to report crashes occurring with recent releases of
chromium-browser, they will hopefully be investigated and acted upon in a more
timely manner.
** Changed in: chromium-browser
Still affected by this bug in 15.04
The media keys work fine as far as I can see, however the following keys
produce no keycode (checked with xinput), meaning that can't be used at
all.
No keycode:
Reset zoom
Zoom in
Zoom out
Word key
Excel key
Launch A
Launch B
Launch C
Launch D
Messenger
--
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
simple-scan. This problem was most recently seen with package version
3.24.0-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/3034378cc25bf3741cd155478aa661746da8a3df
contains
I'm not familiar with systemd-resolved but it seems that you are not
using it as otherwise you'd have 127.0.0.53 in /etc/resolv.conf?
If you could run a packet capture while you do DNS lookups when
connected to the VPN that would be useful. You could capture with:
sudo tcpdump -w /tmp/dns.pcap
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Hi,
I have just installed again Ubuntu 17.04. The process gone util the end without
error and asked me to reboot.
After reboot only Windows 10 boot, no mark of Ubuntu.
I don't understand
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> ... any other help pointer (man page, comment in config, ...) that
would help?
No need for man page, as --with-nvme-devicescan also results in a brief
change to smartd.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I built a test kernel with these four patches. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1685792/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685792
Title:
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685931
Title:
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Zesty)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu Zesty)
**
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661245
Title:
chromium-browser 55 version on Zesty : FTBFS
To
I have worked around this in my Xenial dropbear/initrd environment by
replacing the package /usr/share/initramfs-tools/scripts/init-
bottom/dropbear with:
##
#!/bin/sh
#From /usr/share/initramfs-tools/scripts/init-bottom/dropbear
PREREQ=""
prereqs() {
video=SVIDEO-1:d fixed my laptop. Well found!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637347
Title:
Xubuntu 16.10: drm errors causing slow boot
To manage notifications about this bug go to:
@TJ
Please could you explain what you tested and what the results were?
Please also confirm the package version of the package you tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655752
** Also affects: synaptic (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630283
Title:
LightDM fails to start on Upstart based systems
To
According to the upstream chromium bug, this was an issue in Modernizr.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393902
Title:
GOOG search credit flag isn't always in search
We're seeing errors very similar to this on 2 16.04 VMs, both attached
to different SANs. Sadly one is the live data and the other the backup,
so...
kern.log snippet:
Apr 25 14:54:52 oaebackup1 kernel: [11778105.146482] EXT4-fs (sda1): previous
I/O error to superblock detected
Apr 25 14:54:52
*** This bug is a duplicate of bug 1447715 ***
https://bugs.launchpad.net/bugs/1447715
This was fixed via update to isc-dhcp in bug 1633479. Please see that
bug for the specific isc-dhcp version number needed to fix the bug.
** This bug has been marked a duplicate of bug 1447715
dhclient
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374222
Title:
path for policy files changed
To manage
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755036
Title:
chrome plugin crashes when calling javascript function
To
I have tested Caja 1.18.1-0ubuntu2 from proposed on a clean, updated,
Ubuntu MATE 17.04 VM and confirm this issue is resolved.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
301 - 400 of 803 matches
Mail list logo