Public bug reported:
grub-installer-dbgsym
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => aldric (arauk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327133
Title:
grub-install defaults to partition on whole d
Hello!
Same with jdk11 and maven 3.6.3.
➜ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
➜ mvn --version
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 11.0.7, vendor: Ubuntu,
Public bug reported:
Since Firefox was updated to version 58.0.1+build1-0ubuntu0.16.04.1
(xenial-updates), I noticed a consistent high CPU usage while Firefox
was running under plasma (both by firefox and plasmashell processes).
After a little inquiry, I tend to believe this is due to a global
Sorry, I was not available for the bisection work.
However, it seems that the problem is gone with 4.15.0-59.
This is probably explained by this changelog line:
>> - xhci: Don't let USB3 ports stuck in polling state prevent suspend
Thanks for all (I'll let you know if anything changes again.
Public bug reported:
Since the upgrade to 4.15.0-56-generic (Ubuntu 18.04), my computer fails to
suspend.
Suspend still works fine if I boot with previous kernel (4.15.0-55-generic).
Looking at the changelog, I suspect the following change to be the cause of
this regression:
>> - usb: xhci:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1838514/+attachment/5280149/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1838514/+attachment/5280148/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838514
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1838514/+attachment/5280150/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838514
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1838514/+attachment/5280152/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838514
Title:
ersion: 2.20.9-0ubuntu7.7
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: aldric16562 F pulseaudio
+ /dev/snd/controlC0: aldric16562 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: KDE neon 18.04
+ HibernationDevice: RESUM
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1838514/+attachment/5280153/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838514
Remark: all this apport data was obtained running kernel
4.15.0-55-generic. Please tell me if you need more data, in particular
running kernel 4.15.0-56-generic instead.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1838514/+attachment/5280151/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838514
Title:
I have a very similar issue with a WD19TB under Ubuntu 20.04 (Dell
Latitude 5410) and desperately browsing the net, looking for solutions.
Everything works fine until I resume from suspend. Then all USB devices
connected to the dock start having failures (like missing key presses
for the
#106 The described symptoms are so specific that it would be a really
surprising coincidence if my issue had a different cause with so
identical symptoms.
Are you sure this is really about the dock?
What if it was actually about the thunderbolt controller on the motherboard
instead?
I assume
#107 (sorry, my previous message was meant as an answer to #107 too!)
Incidentally, linux-oem-5.10 does not fix this my issue (with a WB19TB
dock).
Does this kernel work well with the TB16?
What are the relevant logs I should join to my bug report to linux-
oem-5.10? Is dmesg output enough?
--
17 matches
Mail list logo
