** Changed in: kernel-sru-workflow/promote-to-proposed
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/1741610
Title:
linux-lts-trusty: 3.13.0-139.188~precise1 -pro
*** This bug is a duplicate of bug 1741914 ***
https://bugs.launchpad.net/bugs/1741914
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1741914, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1741914 ***
https://bugs.launchpad.net/bugs/1741914
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1741914, so it is being marked as such. Please look
linux (4.13.0-25.29) artful; urgency=low
* linux: 4.13.0-25.29 -proposed tracker (LP: #1741955)
* CVE-2017-5754
- Revert "UBUNTU: [Config] updateconfigs to enable PTI"
- [Config] Enable PTI with UNWINDER_FRAME_POINTER
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017
Public bug reported:
OS: Ubuntu 14.04
Kernel: 3.13.0-137-generic #186-Ubuntu SMP Mon Dec 4 19:09:19 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
motherboard: X9DR3-F with two E2630-v2 CPUs
Graphics card: Nvidia 950 GeForce
Monitors: two 4K monitors being driven on the Displayport ports. Seiki Pro an
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/1742333
Title:
Can't reboot, shutdown, or suspend with 4.4
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow se
This is a big problem. I am using https://github.com/NetSys/bess. BESS
relies on gRPC. gRPC fails to compile under gcc 5 due to the to_string
not declared error. gRPC does compile under gcc 6 or 7 but it breaks
BESS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Actually we don't need to ignore it. We can release the fixes for the
regression. The fixes are:
1. libinput:
https://lists.freedesktop.org/archives/wayland-devel/2018-January/036475.html
(not landed yet)
2. kernel: https://bugs.freedesktop.org/show_bug.cgi?id=104533 (not tested yet)
James will
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain statu
Thank you @jsalisbury. Sorry for my misunderstanding with the status
label.
I will keep an eye out for when the update arrives and I will just avoid
rebooting the server until then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Your log shows an 11 second delay each time this happens:
Nov 06 13:57:46 hostname gnome-session-binary[3428]: WARNING: Could not get
session path for session. Check that logind is properly installed and
pam_systemd is getting used at login.
Nov 06 13:57:57 hostname unity-settings-[3399]: failed
Public bug reported:
Jan 9 20:06:30 arjun kernel: [94151.650813] [ cut here
]
Jan 9 20:06:30 arjun kernel: [94151.650820] WARNING: CPU: 13 PID: 0 at
/build/linux-hwe-edge-Ybwf2T/linux-hwe-edge-4.13.0/net/ipv4/tcp_input.c:2826
tcp_fastretrans_alert+0x83e/0x9c0
Jan 9 20
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716432
Title:
With dash to dock enabled, title in window is
Thank you for the explanation, Bryce and Mattia! But until 2020, this
should be solved, as far as I understand, regardless of this? We've only
got 2 hackfests until then... time flies.
I found that these depend on python scripts, but there may be more, hope
others will fill in the blanks (I've als
** Changed in: libinput (Ubuntu)
Status: Incomplete => New
** Also affects: libinput via
https://bugs.freedesktop.org/show_bug.cgi?id=98689
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
*** This bug is a duplicate of bug 1742278 ***
https://bugs.launchpad.net/bugs/1742278
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1742278, so is being marked as such.
Great. But just a warning; 17.04 reaches end of life this month:
https://wiki.ubuntu.com/Releases
So you will need to upgrade again soon. If you're using gnome-shell then
we recommend 17.10 right now. And before May 2018 we will have 18.04
ready too.
** Changed in: gnome-shell (Ubuntu)
Sta
*** This bug is a duplicate of bug 1180649 ***
https://bugs.launchpad.net/bugs/1180649
It's still here:
Setting up linux-headers-generic (4.4.0.108.113) ...
Setting up linux-generic (4.4.0.108.113) ...
Setting up linux-signed-image-4.4.0-108-generic (4.4.0-108.131) ...
warning: file-aligned s
*** This bug is a duplicate of bug 1726156 ***
https://bugs.launchpad.net/bugs/1726156
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.26.2-0ubuntu2, the problem page
*** This bug is a duplicate of bug 1726156 ***
https://bugs.launchpad.net/bugs/1726156
** This bug has been marked a duplicate of bug 1726156
gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (priv->label_box == NULL)")
Yes, sorry about that. I experience the same on my development machine.
I have no idea why that's happening.
Suggestion: Remove the two empty files *.upload and *.uploaded and then
in a terminal re-upload the existing crash file:
ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
That will
** Package changed: kernel-package (Ubuntu) => linux-hwe-edge (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742341
Title:
WARNING: CPU: 13 PID: 0 at /build/linux-hwe-edge-Ybwf2T/linux-hwe-
** Also affects: ubuntu-themes
Importance: Undecided
Status: New
** Changed in: ubuntu-themes
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/1742269
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-themes (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/1742269
Title
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409
** This bug is no longer a duplicate of private bug 1742278
** This bug has been marked a duplicate of bug 1505409
gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
_XEventsQueued()
On Tue, Jan 09, 2018 at 08:41:09AM -, Talat Batheesh wrote:
> Reading the report, there are a lot FALSE positives. For example, all
> resp.* warnings are false. resp is initialize to be zero.
Hello Talat, at least in the version I'm reviewing, this does not appear
to be the case.
Consider pr
This issue is also being tracked in:
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc
** Description changed:
+ https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc
+
+ ---
+
gnome-shell-portal-helper crashed with SIGABRT
ProblemType: Crash
** Changed in: caribou
Importance: Medium => Unknown
** Changed in: caribou
Status: Confirmed => Unknown
** Changed in: caribou
Remote watch: GNOME Bug Tracker #777468 => GNOME Bug Tracker #604585
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
Did you change between Intel and Nvidia before this issue happens?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742112
Title:
NVIDIA graphics card failed to initialized
To manage notifications a
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
cannot upload as you suggest:
mfg@bix:~$ apport-cli -u 1741946 -c /home/mfg/tmp/wifi.apport
Usage: apport-cli [options] [symptom|pid|package|program path|.apport/.crash
file]
apport-cli: error: -u/--update-bug option cannot be used together with
options for a new report
however, I attach the pr
One thing we'd need to consider is that some more or less basic Inkscape
functionality currently relies on Python extensions, e.g.
- Several templates
- Help links
although I already wondered if this was even really necessary -
I assume there are better solutions available to open a link from
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
The verification of the Stable Release Update for nplan 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 encounter a re
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
The verification of the Stable Release Update for nplan 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 encounter a re
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
The verification of the Stable Release Update for nplan 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 encounter a re
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
The verification of the Stable Release Update for nplan 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 encounter a re
This bug was fixed in the package nplan - 0.32~17.04.1
---
nplan (0.32~17.04.1) zesty; urgency=medium
* Backport 0.32 to 17.04. (LP: #1713142)
nplan (0.32) bionic; urgency=medium
* src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affe
This bug was fixed in the package nplan - 0.32~16.04.3
---
nplan (0.32~16.04.3) xenial; urgency=medium
* tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.
nplan (0.32~16.04.2) xenial; urgency=medium
* tests/integration.py: Fix test_routes_v6 that I
The verification of the Stable Release Update for nplan 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 encounter a re
Is this still an issue being looked into? It's suddenly started
presenting itself to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616497
Title:
uwsgi-plugin-python3 failed to install
To manag
** Changed in: kernel-sru-workflow/prepare-package-lbm
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/1741612
Title:
linux: 3.2.0-132.178 -proposed tracker
** Changed in: caribou
Status: Unknown => In Progress
** Changed in: caribou
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741843
Title:
caribou (gnome-shel
Also, can you post a digital image or screen shot of the panic?
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
You r
*** This bug is a duplicate of bug 1742330 ***
https://bugs.launchpad.net/bugs/1742330
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** This bug has been marked a duplicate of bug 1742330
Can't reboot, shutdown or suspend with 4.4.0-108
--
You received this bug notificat
I have the same issue on a Dell XPS-13-9343, with exactly the same
Broadcom chip. Just like the OP, it does not work on 4.13.0-24 - it
can't seem to find the Wifi. But works just fine on 4.13.0-22.
This is from my kernel on 4.13.0-22.
description: Wireless interface
Can you see if this bug happens with the following kernel:
http://kernel.ubuntu.com/~jsalisbury/lp1741934/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Are you able to install any test kernels on the system to perform some
debugging?
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Tags added: kernel-da-key
** Tags removed: kernel-da-key
** Tags added: kerne
Not sure if this is related. Caught this before I upgraded. System is
now freezing and I can't use an old kernel as I get the following:
NVRM: API mismatch: the client has the version 384.111, but
NVRM: this kernel module has the version 384.90. Please
NVRM: make sure that this kernel module and
Can you see if this bug happens with the following kernel:
http://kernel.ubuntu.com/~jsalisbury/lp1741934/
Also, can you post a digital image or screen shot of the panic?
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Tags added: kernel-key
** Also affects: linux (Ubuntu
** Changed in: linux (Ubuntu)
Importance: High => Critical
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742330
Title:
Can't
Can you see if this bug happens with the following kernel:
http://kernel.ubuntu.com/~jsalisbury/lp1741934/
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738259
Title:
need to ensure microcode updates are available to all bare-metal
installs of Ubuntu
To manage notificatio
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sr
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => Fix Released
** 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.
h
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sr
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => Fix Released
** 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.
h
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => Fix Released
** 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.
h
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: curtin (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/1569567
Title:
Run
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (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/1569567
Title:
Runn
Can't get a good screen shot of it. Machine is frozen and the resolution is
3200x1800. Tried taking a picture, but not readable.
Getting ready to try the kernel you provided. Then I will type in some of
the panic info.
On Tue, Jan 9, 2018 at 10:12 PM, Joseph Salisbury <
joseph.salisb...@canonical.
So is there any progress on this? I can't use gnome-shell because of it,
even with 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/1714886
Title:
gnome-shell crashed with SIGSEGV in
me
The kernel that you provided has solved the problem. Now able to reboot,
shutdown and suspend.
On Tue, Jan 9, 2018 at 10:25 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> ** Changed in: linux (Ubuntu)
> Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
>
> ** Changed i
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Marcelo Cerri (mhcerri) => Leann Ogasawara (leannogasawara)
** Changed in: kernel-sru-workflow/promote-to-proposed
Statu
Public bug reported:
still trying
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Tue
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Marcelo Cerri (mhcerri) => Brad Figg (brad-figg)
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Pr
Achim Behrens,
Is the kernel that fails really 104? Or is that your backup that you
just booted into to report the problem?
The one that fails for me is the new one, 108. It just "panics" nearly
instantaneously.
** Attachment added: "Screenshot of "panic" showing the callstack"
https://bugs.
I'm really not sure we're linking to the right upstream bugs still, or
that we've captured all the right error reports from errors.ubuntu.com.
Possibly this is related and is in progress:
https://bugzilla.gnome.org/show_bug.cgi?id=72
As for Ubuntu crash reports, the only link we have suggests
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742252
Title:
linux: 4.4.0-109.132 -proposed tracker
To manage notifications a
Thanks for providing the stack trace, Lars.
This shows the illegal instruction is happening in Skia, specifically
SkJumper's implementation of _sk_xor__vfp4. To run with Skia disabled,
edit your user profile at ~/.mozilla/firefox/*.default/prefs.js and add
the following line:
user_pref("gfx.conte
No, it's new machine and fresh installation.
It seems a acpi bug in kernel. I use the 'acpi_osi=Linux' as kernel parameter,
also work.
But if I remove the acpi_osi parameter, the nvidia driver can't be initilaized.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the inst
I just upgraded to kernel 4.4 108, and got a similar kernel panic. Is
there a regression to this fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709126
Title:
kernel BUG at [tty_ldisc_reinit] mm
[Expired for openjdk-8 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: openjdk-8 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
901 - 1000 of 1070 matches
Mail list logo
