That's with LXD 2.12? Martin, can you try LXD 2.17 iirc quite some
things have changed from 2.12 on, including btrfs detection and querying
at start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17177
Thanks for the suggestion. However, we very deliberately don't do it
the way you suggest, because it would mean the boot loader would too
easily be broken by perfectly legitimate internal rearrangements
performed by the file system. For example, a file system might quite
reasonably move the physi
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1717856
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-precise
** Tags removed: block-proposed
--
You received this bug notification because you
3.2.0-131.177 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html
Issue to note in amd64:
None
Issue to note in i386:
ubuntu_qrt_kernel_security - test_021_aslr_dapper_libs failed, issue seen
before in 3.2.0, bug 1717856
** Changed in: kernel-sru-workflow/re
Kernel 4.13.2 working fine for 2 days...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550779
Title:
[i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
To manage notifications about this bug
The system is up to date. Unfortunately the problem persist.
I'm Sorry, I have added old syslog file in previous post. Please find attached
syslog from today morning, logs starting on the time of crash.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/
4.13.2 kernel working fine for 2 days with Ubuntu Gnome 17.04, I have an
old IronLake i5 intel.
** Tags added: kernel-fixed-upstream-4.12.3 kernel-fixed-upstream-4.13.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Tags added: wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710373
Title:
Desktop shortcut missing for Vino GUI in Ubuntu 17.10
To manage notifications about this bug go to:
https://bugs.
I think this has been fixed by this commit here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d139e9a6cf01b8c31f59
... so closing this ticket now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716614
Title:
linux-lts-xenial: 4.4.0-96.119~14.04.1 -propo
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716608
Title:
linux-hwe: 4.10.0-35.39~16.04.1 -proposed tra
Aha!
Yes you were probably experiencing bug 1714330 in the old log of comment
#6 but not any more.
In your new log of comment #8 you are now experiencing a new assertion:
Sep 18 07:25:39 internet-ws org.gnome.Shell.desktop[1891]:
mutter:ERROR:backends/meta-monitor-
manager.c:2274:meta_monitor_ma
Hi William,
Do you mind trying out the suggested workaround in comment #8. If I
don't hear back from you in 4 weeks I will close the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697132
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1717865/+attachment/4952004/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717865
Public bug reported:
Just opened http://gnomepomodoro.org/ app. CPU spiked (judging by my
laptop's fans) and I got a partial UI freeze for about a second or so
followed by a dock redraw.
Multiple app open/close sequences do not seem to trigger that but I had
this a couple of times already. Not su
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1717865/+attachment/4952007/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717865
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1717865/+attachment/4952006/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1717865/+attachment/4952005/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17178
** Changed in: linux-aws (Ubuntu Trusty)
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/1716616
Title:
linux-aws: 4.4.0-1002.2 -proposed tracker
To manage notificatio
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716628
Title:
linux-lts-vivid: -proposed tracker
To manage notifications about this bug go to:
http
hmm, no such file ~/.config/monitors.xml in my home directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
man
The final refactoring is now merged and available in the master branch:
24f8cdc572 seccomp: add resourcecontrol argument to command line
995a226f88 seccomp: add spawn argument to command line
73a1e64725 seccomp: add elevateprivileges argument to command line
2b716fa6d6 seccomp: add obsolete argumen
*** This bug is a duplicate of bug 1462647 ***
https://bugs.launchpad.net/bugs/1462647
Don't bother with NaCL, it is deprecated and will be removed from
chrome/chromium in Q1 2018. Use WASM (that is already supported by
chromium-browser)
--
You received this bug notification because you are
** Description changed:
GNOME 3.26 is now released and feature a dynamic transparency.
It means that when no window is next to the top panel, a small gradient
is present. As soon as any window touches it, the top panel become
opaques.
This doesn't play visually well with our ubuntu
** Changed in: cinder (Ubuntu)
Importance: Undecided => High
** Changed in: cinder (Ubuntu)
Status: Confirmed => Triaged
** Changed in: cinder (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (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/1716957
Title:
Go
4.4.0-96.119 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html
Issue to note in amd64:
monotonic_time - gtod failed
ubuntu_kvm_unit_tests - pku, svm, hyperv_clock failed (smap failed on onza)
ubuntu_lxc - Failed to start networking in ubuntu-cloud container
Patch: https://review.openstack.org/#/c/501829/
** Also affects: horizon
Importance: Undecided
Status: New
** No longer affects: horizon
** Also affects: charm-openstack-dashboard
Importance: Undecided
Status: New
** Changed in: charm-openstack-dashboard
Status: New =
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Changed in: cloud-archive/pike
Status: New => Triaged
** Changed in: cloud-archive/pike
Importance: Undecided => High
** Change
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716610
Title:
linux-raspi2: 4.10.0-1018.21 -proposed tracke
** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684789
Title:
trunc-file.sh.btrfs from ubuntu_ecryptfs-test-suite failed on X-hwe
To m
** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684788
Title:
extend-file-random.sh.btrfs from ubuntu_ecryptfs-test-suite failed on
X
I first thought bisecting would be broken (showed all bad and back to the first
commit), but unless there are other things influencing it 1.3.1 from git does
not show this behavior.
Maybe we have a broken delta on top that fixes something else but exhibits this
behavior.
--
You received this b
I mean "~" is your home directory, ".config" is a directory and
"monitors.xml" is the file. :)
Regardless, your original description suggests the invalid config occurs
dynamically. Not necessarily on disk.
** Bug watch added: GNOME Bug Tracker #787637
https://bugzilla.gnome.org/show_bug.cgi?id
Found it. Gnome Developers are already aware of the crash:
https://bugzilla.gnome.org/show_bug.cgi?id=787637
If you would like to contribute to a speedy resolution then please
comment on that page.
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
--
You received this bug notifica
kusader1:2.4.0~beta3
I have the same bug on both of my machines
Ubuntu Mate 16.04 (64 bit)
Debian Jessie with MATE (64 bit)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609456
Title:
Crash after
Overriding, only one outstanding and that is a customer requested arch
specific change.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Overriding 2 outstanding verifications:
1. Address sanitizer regression (selected revert is part of upstream stable
anyway)
2. oops on s390x: changes requested and backported by maintainers. previously
tested in test kernel
** Changed in: kernel-sru-workflow/verification-testing
Status: C
An SRU *to backport a new version* may not be acceptable if it risks
breaking existing users. I hope the rationale for this policy is
obvious. Unfortunately it's not possible to make a definitive statement
unless someone does a technical assessment (which any suitably well-
versed developer can do)
> Is there a reason that the specific bug causing problems in Xenial
cannot just be fixed on its own? That would probably be the easiest to
drive unless there's some technical reason this is difficult.
Looking at the upstream report, it seems that the problem has been
analysed and a simple SRU to
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717616
Title:
linux-azure: 4.11.0-1010.10 -proposed
Even on a fresh Xenial container with Xenial level libvirt the issue is not
reproducible.
So it seems that was an issue local to my initial test system (a xenial lxd
container onas well but on a test system driven by jenkins).
The retest was a simple:
1. xenial container
2. uvtool 3 guests
3. ki
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-zesty
** Tags removed: block-proposed
--
You received this bug notification because you a
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
I'm seeing the same bug, same gnome-online-accounts version but on
17.04. First time running Online Accounts I was presented with a
Microsoft option. I signed in (and I also have a non-standard Live
account meaning it's not outlook.com or hotmail.com), seemed successful,
I turned off e-mail but lef
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-zesty
** Tags removed: block-proposed
--
You received this bug notification because you a
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1684789
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1684788
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Additionally, the problem does not seem to appear when the cronjob
actually runs. The PKG should trigger a crond reload after installation!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393175
Title:
4.0.2-8 apparently builds on s390x
** Changed in: givaro (Ubuntu)
Status: New => 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/1715352
Title:
FTBFS on s390x test suite backtrace
Am 15.09.2017 um 18:08 schrieb Nicolás Abel Carbone:
> Is there a missing piece in the bug
It's a missing piece.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714330
Title:
gnome-shell crashed wit
If the current user is admin, the dialog shall prompt for his password directly.
A list of admin users makes sense only if the current user is not admin.
In Ubuntu 16.04, after adding second administrative user there is a
drop-down but password entry is disabled before selecting the other
admin an
This bug was fixed in the package linux-raspi2 - 4.10.0-1018.21
---
linux-raspi2 (4.10.0-1018.21) zesty; urgency=low
* linux-raspi2: 4.10.0-1018.21 -proposed tracker (LP: #1716610)
[ Ubuntu: 4.10.0-35.39 ]
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
*** This bug is a duplicate of bug 1716606 ***
https://bugs.launchpad.net/bugs/1716606
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-session (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/1715365
Title
*** This bug is a duplicate of bug 1716610 ***
https://bugs.launchpad.net/bugs/1716610
This bug was fixed in the package linux-raspi2 - 4.10.0-1018.21
---
linux-raspi2 (4.10.0-1018.21) zesty; urgency=low
* linux-raspi2: 4.10.0-1018.21 -proposed tracker (LP: #1716610)
[ Ubunt
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
With some recent update to 17.10, this issue seems to be fixed, at least
on my machine. Creating Screenshots with gnome-screenshot works as
expected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170978
Thank you for volunteering! Please see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. If you need any
help, please ask in #ubuntu-devel on IRC (Freenode) if you are able.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
There's also bug 1458323, that I suspect is not properly fixed without
moving to a later version, and updating pjsip, or a config hack to
disable the offending module (which is the officially supported core SIP
module).
--
You received this bug notification because you are a member of Ubuntu
Bugs
This is fixed by the proposed pull request:
https://github.com/snapcore/snapd/pull/3931
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Also affects: snappy
Importance: Undecided
Status: New
** Changed in: snappy
Status: New => Confirmed
** Changed in: snappy
Public bug reported:
This issue can be reproduced on 4.12 and 4.13 kernel.
And it's only happening on node lodygin (AMD speedway).
== sysdig smoke test to trace dd, cat, read and writes ==
Limiting raw capture file to 16384 blocks
Try 1 of 10
Raw capture file is 0 Mbytes
Converted event
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717878
Title:
gdm3 crashed with SIGTRAP in get_fallback_session_name from
get_default_session_name
*** This bug is a duplicate of bug 1717878 ***
https://bugs.launchpad.net/bugs/1717878
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gdm3. This problem was most recently seen with package version
3.25.90.1-0ubuntu4, the problem page at
I think this looks like the same as:
https://errors.ubuntu.com/problem/b8e7721d0034b2c4a5ddafcac2e1cc55703f9dbd
** Summary changed:
- gdm3 crashed with signal 5
+ gdm3 crashed with SIGTRAP in get_fallback_session_name from
get_default_session_name from get_session_name from get_session_filename
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (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/1717878
Title:
gdm3
*** This bug is a duplicate of bug 1717878 ***
https://bugs.launchpad.net/bugs/1717878
** This bug has been marked a duplicate of bug 1717878
gdm3 crashed with signal 5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Affected on ThinkPad X240 after upgrade from 17.04 when booting in an
environment with no known wifi networks. If a known wifi network is
available (and set accessible to all users) the boot time is more
reasonable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: ubuntu-power-systems
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/1709352
Title:
Avoid spurious PMU interrupts after idle
To manage noti
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18
06:52 EDT---
** Attachment added: "Fix race on mm->context.flush_mm"
https://bugs.launchpad.net/bugs/1708399/+attachment/4952057/+files/0003-s390-mm-fix-race-on-mm-context.flush_mm.patch
--
You received thi
1 - 100 of 856 matches
Mail list logo
