*** This bug is a duplicate of bug 1701135 ***
https://bugs.launchpad.net/bugs/1701135
Public bug reported:
issues started from failed install of google-earth-
stable_current_amd64.deb
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-83-generic 4.4.0-83.106
ProcVer
Update to my previous comment - I've extensively tested different
configurations (mostly kernel parameters) on my Legion 5 15ach6. I did
manage to get the brightness to change when using just the dedicated GPU
(selected as such within the BIOS,) using the parameter
nvidia.NVreg_RegistryDwords=Enab
** Also affects: linux (Arch Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1944094
Title:
Can't adjust screen backlight on Legion Slim
Hey, look what I found!
https://gitlab.freedesktop.org/drm/amd/-/issues/1671 there is also
https://gitlab.freedesktop.org/drm/amd/-/issues/1438 which is the bug
report for the previous legion laptops, that one seems to center around
the 4000 series APUs, whereas this time it's centered around the 5
This seems to also effect the Legion 5 15ach6 (AMD) There are two
versions of the legion 5, the 2020 version and the 2021 version. It
seems that this issue is fixed on the 2020 version by adding the kernel
parameter amdgpu.backlight=0 but I can confirm that this does not fix
the issue on the 2021 v
Public bug reported:
I see something similar (but different) to bug 1766076 on a Dell 5530:
- Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from
other bugs that make this dock unusable)
- BIOS 1.6.0
- TB16 dock with a single monitor on the display port, providing power, usi
** Attachment added: "lspci output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+attachment/5250165/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
Dock is unusable with current Ubuntu kernel (screen locks up) as per
https://bugs.launchpad.net/dell-sputnik/+bug/1752165
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
another datapoint: kernel 5.0.4 from UKUU doesn't show the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752165
Title:
TB16 dock freezes X on hotplug when used with external dis
I tried the latest kernel on 18.10 but still see the issue: 4.18.0-17.
Dell Precision 5530, Intel+NVIDIA graphics with Intel graphics selected.
I'm also using the workaround from
https://bugs.freedesktop.org/show_bug.cgi?id=109675, which prevents the
screen from "shuffling" back and forth after pl
all.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC4: shaun 2837 F pulseaudio
+ /dev/snd/controlC3: shaun 2837 F pulseaudio
+ /dev/snd/controlC1: shaun 283
MMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Ins
CCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease:
D
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Ins
D
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Ins
D
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Ins
CCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease:
CCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease:
ERPID ACCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRe
PID ACCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease:
CCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease:
D
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Ins
CCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease:
to see the disconnect under heavy load, such as webcam/headset getting
disconnected during a conference call.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC4: shaun 283
D
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Ins
CCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F pulseaudio
/dev/snd/controlC0: shaun 2837 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease:
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC4: shaun 2837 F pulseaudio
/dev/snd/controlC3: shaun 2837 F pulseaudio
/dev/snd/controlC1: shaun 2837 F
ely
to see the disconnect under heavy load, such as webcam/headset getting
disconnected during a conference call.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC4: shaun 283
-generic 5.4.0.33.38
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: shaun 2
Still seems to be an issue; I tried 4.18.16 on 18.10 and it didn't help
(nor did the most recent 4.19 kernel in UKUU).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752165
Title:
TB16
Following kernel seems to fix the issue (running on 18.10 with kernel
installed by UKUU):
4.20.0-042000-generic #201812232030 SMP Mon Dec 24 01:32:58 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
I still see one or two of these errors when hotplugging but the others
are gone and the external screen wor
PID ACCESS COMMAND
/dev/snd/controlC1: shaun 2662 F pulseaudio
/dev/snd/controlC0: shaun 2662 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 10:51:25 2020
InstallationDate: Installed on 2018-12-11 (641 days ago)
InstallationMedia
PID ACCESS COMMAND
/dev/snd/controlC1: shaun 2662 F.... pulseaudio
/dev/snd/controlC0: shaun 2662 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 10:51:25 2020
InstallationDate: Installed on 2018-12-11 (641 days ago)
In
Package: linux-image-5.4.0-45-generic 5.4.0-45.49
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMA
5.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: shaun 2662 F pulseaudio
/dev/snd/co
Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: shaun 2662 F pulseaudio
/dev/snd/controlC0: shaun
ACCESS COMMAND
/dev/snd/controlC1: shaun 2662 F pulseaudio
/dev/snd/controlC0: shaun 2662 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 10:51:25 2020
InstallationDate: Installed on 2018-12-11 (641 days ago)
Installation
Found the source of the v4l warnings; I was experimenting with
v4lloopback to use a camera as webcam. Disabled that and it's gone
away.
Unfortunately, /var/crash is empty and I didn't see any report from the
right time in the errors webpage.
After applying the change to add "Crash" to the crashd
Confirmed that 4.15.0-041500-lowlatency fixes the problem on an XPS 13
9360.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745282
Title:
Freezes XPS 13
Status in linux package in Ubun
-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1194 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 16 11:18:12 2017
InstallationDate:
itecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1194 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 16 11:18:12 2017
InstallationDate: Installed on 2017-12-14 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aard
9.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: shaun 1194 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 16 11:18:12 2017
Inst
u 17.10
Package: linux-image-4.13.0-19-generic 4.13.0-19.22
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/cont
Public bug reported:
Wifi worked fine for a while then stopped working. dmesg log has a
correlated firmware crash for the Wifi adapter's driver.
Disabling and reenabling Wifi in the network manager widget seemed to
make it work for a while again.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Pac
Here's the dmesg crash report:
[ 3683.563419] wlp58s0: AP 00:07:26:aa:e0:45 changed bandwidth, new config is
2472 MHz, width 2 (2462/0 MHz)
[ 3708.293559] ath10k_pci :3a:00.0: failed to stop wmi scan: -11
[ 3708.293565] ath10k_pci :3a:00.0: failed to stop scan: -11
[ 3708.293568] ath10k_p
Looks similar to Bug #1627474, not sure if trace is identical though
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1654754
Title:
Wifi stopped working; ath10k_pci firmware cras
/dev/snd/controlC0: shaun 2212 F pulseaudio
CurrentDesktop: Unity
Date: Sat Nov 19 10:39:23 2016
HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f
InstallationDate: Installed on 2012-09-26 (1515 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal"
-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1646 F pulseaudio
CurrentDesktop: Unity
Date: S
-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1646 F pulseaudio
CurrentDesktop: Unity
Date: Sat May 2 13:26:14 2015
HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-88
.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1646 F pulseaudio
CurrentDesktop: Unity
Date: Sat May 2 13:26:14 2015
HibernationDevice: RESUME=UUID=e
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 2212 F pulseaudio
CurrentDesktop: Unity
Date: Sat Nov 19 10:39:23 2016
HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d
e: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 2212 F pulseaudio
CurrentDesktop: Unity
Date: Sat Nov 19 10:39:23 2016
HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f
InstallationDate: Installed on 2012-09-26 (1515
I am seeing this as well in a Hyper-V 2012R2 environment, but with more
reasonable boot times.
$ systemd-analyze
Startup finished in 14.479s (kernel) + 3.101s (userspace) = 17.580s
$ cat /proc/version
Linux version 4.4.0-36-generic (buildd@lcy01-01) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ub
Christopher M . Penalver; Apologies for posting technical inaccuracies
to an unrelated bug report. Have unmarked as affected here and will
follow your advice. My troubles now seem (to me)to be vendor/firmware
related and will subscribe you to another bug report.
--
You received this bug notific
On different hardware GA A75 UD4H this is a very similar issue
regarding using EFI to install Ubuntu. Have tried from 11.04 and up to
13.04 all with same result ie does not run installer in EFI mode,
noefi does not work for me but running installer using BIOS/legacy mode
does work then installing
Ubuntu flavours <=12.04.1 may cause trouble regarding making a 16bit; or
wanting to use a 16bit ESP whereas firmwares are looking for 32bit ESP= no
worky!? The workaround is to allow installer to run as it wants to but be sure
to copy ESP save in another location then delete 16bit ESP and remake
*** This bug is a duplicate of bug 1213119 ***
https://bugs.launchpad.net/bugs/1213119
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213172
x-image-3.5.0-21-generic 3.5.0-21.32
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1915 F pulseaudi
ric x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1915 F pulseaudio
Date: Sat Dec 29 11:54:48 2012
HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f
InstallationDate: Install
9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1915 F pulseaudio
Date: Sat Dec 29 11:54:48 2012
HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f
InstallationDate: Installed on 2012-09-26 (94 days ago)
In
This error is reproducable on my hardware >=12.04.2 with EFI mode on.
Am posting this from 13.04 amd 64 desktop live session because of this
error and others possibly associated with it. Using ga a75 ud4h mobo
with latest firmware which uses EFI 1.1 rev 2 specification firmware.
rEFInd sees this
This affects precise,quantal , and raring. Have not tried saucy yet.
Is there a way to confirm the first stage installer are capable of running on
an EFI system that is not secure boot capable? Is shim required on non
SecureBoot system?
I suspect if shim/ first stage installer are not able to
Taking Secure Boot out of equation indicates this is almost certainly a
grub 2 deficiency or bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1072378
Title:
[Asus Eee PC 1015BXO] Ubunt
Public bug reported:
will use url to add linux as affects to this bug report
https://bugs.launchpad.net/ubiquity/+bug/1213119
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.29
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19
Uploaded this report with intaention of adding as affected to
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1213119
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1213172
Title:
"
This affects raring
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1025467
Title:
sysrq is now completely disabled, it would be nice to maintain the
ability to reboot etc
Status in “l
Booting Ubuntu Desktop amd64 liveDVD (3.8.0-19-generic) in BIOS mode
searching "computer" using file manager to find sysreq settings is now
found in /etc/systl.d and named 10-magic-sysrq.conf. Looking in my
Ubuntu partitionb which was last bootable using 3.8.0.28 kernel; also
confirms sysrq as b
If sysrq is disabled by default and users are saying it works for them
(Ask Ubuntu) ie http://askubuntu.com/questions/53263/shut-down-computer-
from-keyboard/53266#53266 Perhaps this is evidence of why full
disablement of sysrq is applied by default? ie If user did not set sysrq
on; Who did?
--
Sorry wrong link- intended to post http://askubuntu.com/questions/11002
/alt-sysrq-reisub-doesnt-reboot-my-laptop
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1025467
Title:
sysrq is n
Apologies once again. Now understand S U B are only sysrq commands
allowed by default by the use of bitmask 176 which for it is easy to
change or adapt relevant settings to any other commands as needed or
desired. This for me is applicable to 12.10 and 13.04 desktop amd64.
Suprisingly very little i
*** This bug is a duplicate of bug 1213119 ***
https://bugs.launchpad.net/bugs/1213119
Sorry for not replying quicker. Just acknowleging last comment and
would like to confirm this possible bug i am trying to describe is at
install time. Also this is duplicate due to me trying to add report
I've flashed the BIOS update via FreeDOS live cd and I'm currently on
version A10, release date 08/28/2013. At first, it did not look as if it
had done anything to fix the problem. Brightness control was still not
working.
However, I noticed a recent comment
(https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
I've seen this problem in both kernels 3.8.0.30-generic and
3.8.0.31-generic. It seems to be working without any problems in
3.8.0.29-generic.
Current version of intel packages:
xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1
libdrm-intel1: 2.4.43-0ubuntu1.1
** Affects: linux
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+attachment/3847174/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+attachment/3847173/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/123
apport information
** Attachment added: "HookError_cloud_archive.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847214/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847213/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847216/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1232459
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847211/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847226/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847218/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847224/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1232459
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847215/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/12
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847212/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1232459
Ti
apport information
** Tags added: apport-collected
** Description changed:
I've seen this problem in both kernels 3.8.0.30-generic and
3.8.0.31-generic. It seems to be working without any problems in
3.8.0.29-generic.
Current version of intel packages:
xserver-xorg-video-intel: 2:2.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847220/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847219/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847223/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1232459
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847221/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847222/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847217/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1232459
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1232459/+attachment/3847225/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1232
I've double-checked, and I'm running this XPS via UEFI boot. Most of my
searching for any resolution has mentioned additions/removals from
GRUB_CMDLINE_LINUX_DEFAULT, but nothing has helped there (currently only
arguments passed are "quiet splash")
--
You received this bug notification because yo
I attempted the upstream 3.8.13.10 kernel, but was unable to boot. I've
tagged this bug indicating that.
** Tags added: kernel-unable-to-test-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I can no longer replicate this using the 3.2.0-54 kernel. I'm going to
assume one of the intermediate versions fixed the issue.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
Scale testing our product, which uses the BIRD BGP daemon, on Google's
GCE cloud, we see frequent (40% of hosts) Kernel Oopses and reboots on
kernel 3.19.0-25-generic #26~14.04.1-Ubuntu with BIRD running. This is
the standard GCE-provided Ubuntu image.
If we replace the imag
I added ppa:canonical-kernel-team/ppa2 but still get the same error in
the log file. This is after apt upgrade and booting into the newer
kernel image. Should it have worked or am I missing a step to test?
...
Loading new amdgpu-5.16.9.22.20-1438747~22.04 DKMS files...
Building for 5.15.0-56-gen
ok, I see. I"ll try to figure out how to report the same issue for the
AMD release.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1996740
Title:
5.15.0-53-generic no longer boots
Stat
98 matches
Mail list logo