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
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.
*** 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.
--- 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
** Changed in: kernel-package (Ubuntu Zesty)
Status: New => Invalid
** 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.
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,
** 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
** 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
** Changed in: gnome-terminal
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/328444
Title:
gnome-terminal shortcuts: Alt+Shift+1 shows as Alt+! etc.
To manage
Unable to show full message.
You can view it by clicking here
Mon, 18 Sep 2017 03:22:58 -0800
Yahoo error code: 56win
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/116300
Title:
eclipse crashes
Public bug reported:
Description:Ubuntu 16.04.2 LTS
Release:16.04
Seems very similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687512
Running on google compute engine as kubernetes node.
[516083.665420] BUG: unable to handle kernel NULL pointer dereference at
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
Didn't see test results coming in after several attempts, might be some issue
to the test infrastructure.
I will just let it through and work with Brad to resolve this.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in:
@bdmurray, I'd like you to reconsider the notfixing tag, it's a real
issue for QA because qxl is the only driver that works with wayland. The
system falls back to X with the standard vga driver and does not boot
after installation with cirrus.
--
You received this bug notification because you
** Changed in: freeplane (Debian)
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/172
Title:
Missing Avalon NoClassDefFoundError:
Did you ever manage to install the HP Designjet T520 on Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636142
Title:
toolbox.py assert failure: *** buffer overflow detected ***:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
Didn't see test results coming in after several attempts, might be some issue
to the test infrastructure.
I will just let it through and work with Brad to resolve this.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in:
** 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
Didn't see test results coming in after several attempts, might be some issue
to the test infrastructure.
I will just let it through and work with Brad to resolve this.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in:
There are already (upstream) binaries available for zesty and earlier;
see http://www.4pane.co.uk/Download.htm . Is that sufficient, or are
there reasons for using a PPA too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Intention: Dual boot Windows 10 and Ubuntu
Partition Layout:
1. LVM of 250 GiB on mount point / with ext4,
2. LVM SWAP of 12 GiB,
3. Primary ext4 partition on mount point /boot of 48 GiB
4. Set mount point of /boot/efi on existing Windows 10 boot partition marked
Note I was seeing this in zesty for a while (then didn't):
https://bugzilla.gnome.org/show_bug.cgi?id=772476
** Bug watch added: GNOME Bug Tracker #772476
https://bugzilla.gnome.org/show_bug.cgi?id=772476
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tested with Colin's patch on two amd64 systems with Artful kernel. They
both passed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
** 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.
** 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
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.
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.
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
*** This bug is a duplicate of bug 1716622 ***
https://bugs.launchpad.net/bugs/1716622
This bug was fixed in the package linux-kvm - 4.4.0-1007.12
---
linux-kvm (4.4.0-1007.12) xenial; urgency=low
* linux-kvm: 4.4.0-1007.12 -proposed tracker (LP: #1716622)
[ Ubuntu:
*** This bug is a duplicate of bug 1716621 ***
https://bugs.launchpad.net/bugs/1716621
This bug was fixed in the package linux-gke - 4.4.0-1031.31
---
linux-gke (4.4.0-1031.31) xenial; urgency=low
* linux-gke: 4.4.0-1031.31 -proposed tracker (LP: #1716621)
[ Ubuntu:
*** This bug is a duplicate of bug 1716613 ***
https://bugs.launchpad.net/bugs/1716613
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing:
*** This bug is a duplicate of bug 1716619 ***
https://bugs.launchpad.net/bugs/1716619
This bug was fixed in the package linux-snapdragon - 4.4.0-1076.81
---
linux-snapdragon (4.4.0-1076.81) xenial; urgency=low
* linux-snapdragon: 4.4.0-1076.81 -proposed tracker (LP: #1716619)
*** This bug is a duplicate of bug 1716618 ***
https://bugs.launchpad.net/bugs/1716618
This bug was fixed in the package linux-raspi2 - 4.4.0-1074.82
---
linux-raspi2 (4.4.0-1074.82) xenial; urgency=low
* linux-raspi2: 4.4.0-1074.82 -proposed tracker (LP: #1716618)
[
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux-hwe - 4.10.0-35.39~16.04.1
---
linux-hwe (4.10.0-35.39~16.04.1) xenial; urgency=low
* linux-hwe: 4.10.0-35.39~16.04.1 -proposed tracker (LP: #1716608)
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing:
This bug was fixed in the package linux-hwe - 4.10.0-35.39~16.04.1
---
linux-hwe (4.10.0-35.39~16.04.1) xenial; urgency=low
* linux-hwe: 4.10.0-35.39~16.04.1 -proposed tracker (LP: #1716608)
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
This bug was fixed in the package linux-gcp - 4.10.0-1006.6
---
linux-gcp (4.10.0-1006.6) xenial; urgency=low
* linux-gcp: 4.10.0-1006.6 -proposed tracker (LP: #1716609)
[ Ubuntu: 4.10.0-35.39 ]
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
** 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
Commenting out the entire code block that does wayland logic in bin
/desktop-launch works around the problem. I think I will release a
manually modified snap for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18
06:51 EDT---
** Attachment added: "Fix race local TLB flushing vs. context switch"
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux-gke - 4.4.0-1031.31
---
linux-gke (4.4.0-1031.31) xenial; urgency=low
* linux-gke: 4.4.0-1031.31 -proposed tracker (LP: #1716621)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
--- Comment From vipar...@in.ibm.com 2017-09-18 07:01 EDT---
(In reply to comment #8)
> I failed to reproduce this in our lab, I was able to upgrade 16.04.3 to
> 17.04 (16.10 is no longer supported). I am closing this bug as invalid,
> please re-open if you are able to reproduce this on
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
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
> 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
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
** 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 was fixed in the package linux-kvm - 4.4.0-1007.12
---
linux-kvm (4.4.0-1007.12) xenial; urgency=low
* linux-kvm: 4.4.0-1007.12 -proposed tracker (LP: #1716622)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not
** 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 was fixed in the package linux-gke - 4.4.0-1031.31
---
linux-gke (4.4.0-1031.31) xenial; urgency=low
* linux-gke: 4.4.0-1031.31 -proposed tracker (LP: #1716621)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not
** 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)
--
You received this bug notification because you are
This bug was fixed in the package linux-raspi2 - 4.4.0-1074.82
---
linux-raspi2 (4.4.0-1074.82) xenial; urgency=low
* linux-raspi2: 4.4.0-1074.82 -proposed tracker (LP: #1716618)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic
** 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 was fixed in the package linux-snapdragon - 4.4.0-1076.81
---
linux-snapdragon (4.4.0-1076.81) xenial; urgency=low
* linux-snapdragon: 4.4.0-1076.81 -proposed tracker (LP: #1716619)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
*
** 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-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
** 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-security
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you
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.
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
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.
** 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:
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
*** 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)
[
Thank you, yes It seems that the bug report you found on Gnome Bugzilla
is reporting the same type of crash.
--
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
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 1717884
and then change the status of the bug to 'Confirmed'.
If, due to the
Yo!
My dear friend I've got such a good news for you, just take a look at
http://www.phoenixicetheatre.org/sites/default/files/css/liberal.php?UE81MTg0N0BidWdzLmxhdW5jaHBhZC5uZXQ-
Paolo Grifa
From: 51847 [mailto:51...@bugs.launchpad.net]
Sent: Monday, September 18, 2017 4:48 AM
To:
Looks like the timeout for the capture occurs before sysdig manages to
start. Need to add a polling delay that checks if sysdig is up and ready
before we kick off the capture timeout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1716622 ***
https://bugs.launchpad.net/bugs/1716622
This bug was fixed in the package linux-kvm - 4.4.0-1007.12
---
linux-kvm (4.4.0-1007.12) xenial; urgency=low
* linux-kvm: 4.4.0-1007.12 -proposed tracker (LP: #1716622)
[ Ubuntu:
*** This bug is a duplicate of bug 1716613 ***
https://bugs.launchpad.net/bugs/1716613
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing:
1 - 100 of 873 matches
Mail list logo
