Public bug reported:
After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
longer connect to network. I tried downgrading snapd from edge, still no
connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also
add apparmor in case this is an apparmor issue as well.
Just moving to the correct package since the signed kernel is merely
derived.
** Package changed: linux-signed-lowlatency-hwe-6.2 (Ubuntu) => linux-
lowlatency-hwe-6.2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thank you for reporting this and helping make Ubuntu better. Could you
please boot into a Ubuntu kernel (not third party kernel) and execute
the following command only once, as it will automatically gather
debugging information, in a terminal:
apport-collect 2011385
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We need some more information from you before we can
start working on this bug.
Please include the information requested from the "Reporting Sound Bugs"
section of https://wiki.ubuntu.com/DebuggingSoundProblems as
Targeted to jammy since at least one of the duplicates is specifically
talking about 22.04.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-hwe-6.2
This bug report was filed against the Linux kernel but seems to have
been intended for the flatpak package touchegg. Please contact the
developer of touchegg for support. Contact information for the developer
seems to be at https://github.com/JoseExposito/touchegg.
** Changed in: linux (Ubuntu)
Working with Pirouette on IRC, we determined this may be related to
https://bugzilla.kernel.org/show_bug.cgi?id=201957#c94 in which the
solution, sadly, was to add amdgpu.mcbp=0 to the kernel boot parameters.
Per that bug report, it does appear as though this might be the result
of a regression in
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
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/2039744
Title:
"Wi-Fi and Bluetooth drop or become unstable after
** Package changed: linux-signed-hwe-6.2 (Ubuntu) => linux-hwe-6.2
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039747
Title:
snd_intel_dsp_driver_probe page fault
** Summary changed:
- While running Updates in Discover on Ubuntu Studio 22.04, an error occures
about overwiting acpidbg file
+ Error while updating linux-intel-iotg-tools-common
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux-hwe-5.19
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2018197
Title:
Ubuntu 22.04 crash when plays game
** Package changed: linux-meta-hwe-5.19 (Ubuntu) => linux-hwe-5.19
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2018200
Title:
Dell XPS 15 9520 kernel
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but
** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux-hwe-5.19
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2016202
Title:
bluetooth doesnt work properly,
--
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/2016185
Title:
Kernel panic at initial boot of April 13 daily 23.04 image on
VirtualBox VM
Status in linux package in Ubuntu:
> Sometimes, when the system is rendered unresponsive as a result of any
of the above, the power led is sending the message of "processor
failure" (2 x amber blinks followed by 1 x white blink).
Based on this, your CPU is failing. Unfortunately, this is not something
software (Ubuntu) related,
** Package changed: linux-signed-hwe-5.4 (Ubuntu) => linux-hwe-5.4
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/2000491
Title:
Dell Latitude 7390 running Ubuntu
** Package changed: linux (Ubuntu) => cheese (Ubuntu)
** Changed in: cheese (Ubuntu)
Status: Incomplete => 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/1983181
Title:
RE: Comment #5
That would be getting off-topic, and support questions are no place for
a bug tracker. You're better off looking for support. In your case,
looking for support would be a matter of checking
https://lubuntu.me/links/ for ways to get help.
--
You received this bug notification
** Package changed: linux-signed-hwe-5.15 (Ubuntu) => linux-hwe-5.15
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981930
Title:
Touchpad is not detected, on Windows
** Package changed: linux (Ubuntu) => joystick (Ubuntu)
** Changed in: joystick (Ubuntu)
Status: Confirmed => 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/1973216
Title:
** Package changed: ubuntu => linux (Ubuntu)
** Package changed: linux (Ubuntu) => unattended-upgrades (Ubuntu)
--
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/1973237
Title:
WiFi
** Package changed: ubuntu => linux (Ubuntu)
--
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/1973203
Title:
Kubuntu does not shut down properly
Status in linux package in Ubuntu:
** Package changed: ubuntu => linux-hwe (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1973086
Title:
System won't go into suspend normally with kernel above 5.13.0-35
** Package changed: ubuntu => linux (Ubuntu)
--
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/1971573
Title:
After upgrade from 20.04 to 22.04 & reboor hangs
Status in linux package in
** Package changed: kubuntu-meta (Ubuntu) => linux (Ubuntu)
--
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/1971117
Title:
2nd display crashed
Status in linux package in Ubuntu:
New
** Package changed: ubuntu => linux (Ubuntu)
--
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/1970125
Title:
suspend drains battery
Status in linux package in Ubuntu:
Incomplete
Bug
** Package changed: ubuntu => linux (Ubuntu)
--
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/1970065
Title:
System not going to be completly powered off
Status in linux package in
** Package changed: ubuntu => linux-hwe-5.13 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1968938
Title:
Integrated webcam no longer working after latest system
** Also affects: partman-swapfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
** Changed in: partman-swapfile (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but
Allan, bsdz: thanks for the workaround(s). However, workarounds don't
get to the heart of fixing the problem, which is what bug reports are
intended to do. Rest assured, the people that need to fix this are
working on it, hence the triage and assignment, and I would expect this
to be fixed very
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
** Package changed: linux-signed-hwe-5.13 (Ubuntu) => linux-hwe-5.13
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1962373
Title:
Cannot resume from suspend
Status
Tested with 1020 kernel in focal-updates, still no-good.
Tested with 1021 kernel in focal-proposed, seems to be OK.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1956393
Title:
@xnox:
Upon investigation, and per our conversation on IRC, I did some
experimenting with the prebuilt modules. Unfortunately, these use
llvmpipe and don't interface well with nvidia-settings.
Using ubuntu-drivers to install the drivers used *the exact same
mechanism* as installing
** Description changed:
- On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013
- kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure
- why this has happened, but this is likely an API change.
+ On many CLEVO chassis computers with the recent update to the
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: linux-oem-5.14 (Ubuntu)
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
Public bug reported:
On Kubuntu Focus computers with the recent update to the OEM 5.14.0-1013
kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure
why this has happened, but this is likely an API change.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it. We understand the
difficulties you are facing, but it is better to raise problems you are
having in the
** Changed in: ubuntu
Status: New => Invalid
** Package changed: ubuntu => linux (Ubuntu)
--
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/1949258
Title:
First installation of
We're using whatever nvidia-driver-470 pulls in.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1947043
Title:
nvidia drivers do not update initramfs properly
Status
Public bug reported:
When Nvidia drivers are installing, they are only rebuilding the
initramfs for the currently running kernel and/or the newest kernel when
installed. Unfortunately, that means that if one has two kernel flavors
installed (such as -generic and -lowlatency) this means that the
Thank you for reporting this bug to Ubuntu.
Ubuntu Studio 18.04 (bionic) reached end-of-life on January 26, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
Enabled proposed for this file, does exactly what is described and
allows for CUDA library installation on Hirsute, Groovy, and Focal.
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done
Verified fixes work in Groovy as well using the above method.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Verified fixes work in Hirsute as well using above method.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Summary changed:
- Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
+ Please SRU nvidia-modprobe 465.24
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
** Changed in: nvidia-settings (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: nvidia-settings (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received
Installed and ran on systems containing issue. Kernel seemed to work
flawlessly. We are going to roll with this kernel and resume sales of
our systems.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a
** Changed in: nvidia-settings (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: nvidia-settings (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because
** Changed in: nvidia-modprobe (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: nvidia-modprobe (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: nvidia-modprobe (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and
This bug was fixed in the package nvidia-modprobe - 465.24.02-1
---
nvidia-modprobe (465.24.02-1) experimental; urgency=medium
* New upstream release. (Closes: #987744)
-- Luca Boccassi Thu, 29 Apr 2021 11:48:45 +0100
** Description changed:
[Impact]
Users of the
** Changed in: nvidia-modprobe (Ubuntu Impish)
Status: Fix Released => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe and
Public bug reported:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
** Summary changed:
- [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer,
+ [SRU] Patch for flicker and glitching on common LCD display panels, intel
framebuffer
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Added linux-hwe-5.8 because that's really where the issues against Focal
appear. I now understand why Timo marked as "Won't fix" since that's for
the 5.4 kernel in Focal.
** Also affects: linux-hwe-5.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Timo, can we get an explanation for the "Won't Fix" status as it relates
to Focal? This directly affects our business as we only use LTS,
therefore Focal in this case.
** Changed in: linux (Ubuntu Focal)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are
** Description changed:
Filing this with my Kubuntu Focus (kfocus.org) OEM hat on:
[Impact]
We are having screen flickering and glitching issues with some of our
hardware upon wake from suspend. We have worked with our ODM to figure
out a fix for this. They had reported there were
** Patch removed: "Intel-developed patch to fix framebuffer flicker/glitching"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491120/+files/drm-intel.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Sadly, we can't wait that long, Kai-Heng. This is a patch that is
critical to our operation and is causing money to be lost daily on
machines we can't sell. There are other OEMs that are affected by this
as well.
The aforementioned patch is headed to kernel 5.13, due out in June. If
this weren't
Hi Kai-Heng,
We built a combined patch (attached) from that commit and our initial
patch and tested, and it seems to work even better. We tested on only
one system, but we intend to test on all the glitchy systems to ensure
it is stable.
That said, the commit you pointed out seems to work well
Public bug reported:
Filing this with my Kubuntu Focus (kfocus.org) OEM hat on:
[Impact]
We are having screen flickering and glitching issues with some of our
hardware upon wake from suspend. We have worked with our ODM to figure
out a fix for this. They had reported there were no issues when
Meant to say groovy in #15 (oops)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1915003
Title:
SRU: Always update the initramfs when changing power profile
Status in NVIDIA
Verified on a Kubuntu Focus M1 running focal:
erich@erich-KFocus:~$ apt-cache policy nvidia-settings
nvidia-settings:
Installed: 460.39-0ubuntu0.20.10.1
Candidate: 460.39-0ubuntu0.20.10.1
Version table:
*** 460.39-0ubuntu0.20.10.1 100
100 /var/lib/dpkg/status
Works exactly as
Verified on a Kubuntu Focus M1 running focal:
erich@erich-KFocus:~$ apt-cache policy nvidia-settings
nvidia-settings:
Installed: 460.39-0ubuntu0.20.04.1
Candidate: 460.39-0ubuntu0.20.04.1
Version table:
*** 460.39-0ubuntu0.20.04.1 100
100 /var/lib/dpkg/status
Works exactly as
> Why is it not possible to report a bug directly to the "Ubuntu Kernel
Team"?
Because this way (reporting it against the package) DOES report it to
the correct team. Ubuntu does stuff automatically so you don't have to.
:)
--
You received this bug notification because you are a member of
As this issue is not specific to Ubuntu Studio, and since this has *not*
been verified by anybody but the bug reporter, I removed Ubuntu Studio
Developers from this bug and changed it to "New".
The lowlatency kernel has many, many more use cases than audio, hence it
is no longer developed or
Bugs in Ubuntu are never filed against the distribution as a whole, but
rather, individual components/packages. Removed affecting Ubuntu.
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1880325
When reporting bugs in the future please use apport by using 'ubuntu-
Respin already in progress. New spin has the fix.
** Project changed: ubuntustudio => syslinux (Ubuntu)
** Changed in: syslinux (Ubuntu)
Status: New => Fix Released
** Package changed: syslinux (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification because you are a
** Changed in: ubuntustudio-meta (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1826844
Title:
Found out the problem. It was indeed a firmware update with my BIOS
which disabled a power-on-demand item in the ACPI. Closing this.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
I did a kernel bisection back to 5.0 (in disco) and the problem still
persisted. It could be a firmware problem with my machine, but I'm
uncertain.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It did definitely work in 19.04, but cannot find a CPU governor on 19.10
or Focal.
--
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/1856440
Title:
cpufreq: no or unknown cpufreq driver
Public bug reported:
Not sure where this goes, but no cpufreq driver is available in 19.10 or
20.04 on AMD CPUs. I'm not sure why this is happening, but no cpufreq
driver gets loaded.
Output of cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to
*** This bug is a duplicate of bug 1787857 ***
https://bugs.launchpad.net/bugs/1787857
Please report that in the bug this is a duplicate of, and also mark it
as affecting you. (Bug 1787857).
--
You received this bug notification because you are a member of Kernel
Packages, which is
*** This bug is a duplicate of bug 1787857 ***
https://bugs.launchpad.net/bugs/1787857
In the future, please report bugs against the package using "ubuntu-bug
{packagename}" in the command line. Filing bugs against Ubuntu Studio as
a whole is invalid.
** Also affects: linux (Ubuntu)
Subscribing kernel team.
Also, posting the difference between the kernel configurations for
reference so that you can see exactly why I believe it's a hardware
issue. This issue you're reporting has been reported very few times,
which is why I believe there is hardware commonality and might be
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1787857
Title:
USB mouse cursor lags after random time of correct
In that case I'm keeping this as incomplete, especially since OP
(ronso0) has failed to verify with suggestions given by kaihengfeng. I
feel like there is some hardware commonality here, and would like to see
some hardware specifics as previously requested to better triage this
bug.
--
You
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: rtirq (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Lassi, thanks for the comment. If that's the case, I'm going to go ahead
and mark this bug as "Invalid" for rtirq and "Fix Released" for linux,
but I'd love to see more comments first to confirm this.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: ubuntustudio
Status: Incomplete => Confirmed
** No longer affects: ubuntustudio
--
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/1787857
Title:
USB mouse cursor
** No longer affects: ubuntustudio-meta (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1826844
Title:
nvidia-drivers-* are not on the ISO
Status in
** Changed in: ubuntustudio-meta (Ubuntu Eoan)
Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1826
** Changed in: ubuntustudio-meta (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1826844
Title:
** Changed in: ubuntustudio-meta (Ubuntu Eoan)
Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)
** Changed in: ubuntustudio-meta (Ubuntu Eoan)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Added ubuntustudio-meta to get this into our live session.
** Also affects: ubuntustudio-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
I wouldn't worry about that. If it's in disco-proposed, it'll likely
land before the first RC spins even happen. The release team is
considering this a serious bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@robstrube It is currently in disco-proposed as well. :)
--
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/1821820
Title:
Cannot boot or install - have to use nomodeset
Status in linux
Workaround found at
https://wiki.archlinux.org/index.php/Intel_graphics#Xorg_configuration
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Also experiencing same problem on a Dell Inspiron 3168. Seems as though
what should be handled by iio-sensor-proxy is not being handled for the
input part of the touchscreen.
** Also affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iio-sensor-proxy
Also subscribing rtirq since this may be related.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: rtirq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Still need to know hardware specifics. I, for one, have AMD Graphics
which exhibits this behavior without some AMD-specific kernel parameters
in the command line in grub. Either way, subscribing the kernel package
to this as well.
** Also affects: linux (Ubuntu)
Importance: Undecided
Public bug reported:
Booting various kernels including the mainline 3.12 kernel, HP Mini 1000
does not resume from suspend. Problem seems to have begun following
update to 13.10, including kernels 3.9, 3.10, 3.11.
Ran steps on DebuggingKernelSuspend wiki page at
apport information
** Tags added: apport-collected saucy
** Description changed:
Booting various kernels including the mainline 3.12 kernel, HP Mini 1000
does not resume from suspend. Problem seems to have begun following
update to 13.10, including kernels 3.9, 3.10, 3.11.
Ran steps
98 matches
Mail list logo
