Resubmit to apport as
https://code.launchpad.net/~vicamo/ubuntu/+source/apport/+git/apport/+merge/382559
instead per comment #11.
** Merge proposal linked:
https://code.launchpad.net/~vicamo/ubuntu/+source/apport/+git/apport/+merge/382559
** Changed in: linux-firmware (Ubuntu Bionic)
S
24.38% in Ubuntu 20.04
--
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/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing g
The actual proportions of Ubuntu users with Nvidia are:
21.94% in Ubuntu 18.04
24.10% in Ubuntu 19.10
And even fewer will be using automatic login.
So to say that most users have Nvidia is false. And to imply that even
most Nvidia users can't login is false.
--
You received this bug notificati
@Daniel Van Vugt. I appreciate your feedback, and I do very much
appreciate it, However I think it is worth a try. I think it is more of
Nvidia screwing with us rather than we creating problems for ourselves,
It is like a chicken and and egg situation, You enable nvidia-
drm.modeset=1 and then you
Same here for a while now, really annoying
$ inxi -SCGxxxz
System:Host: Slenvy Kernel: 5.3.0-46-generic x86_64 bits: 64 gcc: 7.5.0
Desktop: Gnome 3.28.4 (Gtk 3.22.30-1ubuntu4) info: gnome-shell dm:
gdm3 Distro: Ubuntu 18.04.4 LTS
CPU: Quad core Intel Core i7-8550U (-MT-MCP-)
added to git
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux-oem-5.6 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
[Expired for linux (Ubuntu Eoan) because there has been no activity for
60 days.]
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
[Expired for linux (Ubuntu Focal) because there has been no activity for
60 days.]
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
** Tags added: hwe-bluetooth
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1873718
Title:
CSR8510 based BTA-402 Bluetooth device cannot be started
Status in bluez package in Ubuntu:
Sounds like this might be a kernel bug, or a hardware problem. I am
skeptical of CSR Bluetooth dongles since they seem to be consistently
unreliable, at least on Linux.
Please try a newer (or older) kernel version and tell us if that makes
any difference:
https://kernel.ubuntu.com/~kernel-ppa/m
Now we are getting somewhere.
X windows system implicated. Though the 2d video shows how fast the
shortcut boot is, I thought I should get a firm number so I did the
shortcut boot and logged in to get output of 'systemd-analyze critical-
chain' and I got the following very interesting responses, s
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873720
Title:
Failed to boot after upgrade d
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described ear
Public bug reported:
In the GUI, I can go to the Bluetooth settings and it shows BT to be
off. I turn on the little switch at the top but nothing else changes. If
I navigate away from this page and then back, the switch is off again.
If I try to reset the device on the command line I get:
seb@er
Public bug reported:
When I upgraded my system to 20.04, the boot sequence hung.
When I changed my GRUB to include nomodeset, things booted up fine, but
not much functionality for my display.
I finally added modeprobe.blacklist=nouveau in order to get the machine
to boot and get more display fun
@vicamo, did this failure (comment#23) only happen this v5 patch? We did
successfully aplly the earlier (v3?) patch, right?
--
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/1868936
Title:
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873714
Title:
Computer freeze on application
** Tags added: oem-priority originate-from-1873553 somerville
--
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/1873441
Title:
modinfo: ERROR: could not get modinfo from 'da903x': No such f
Public bug reported:
Experience behaviour: The system freezes for about 10 seconds often when
- I change applications
- I open applications
- switch tabs in firefox
- open new web pages
- draw in GIMP with pen tablet
Average occurance:
- every 1 - 4 minutes // usual PC usage
- every 30 seconds /
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described ear
A stray click sent my previous message before I had finished editing it,
and I see no way to edit my post. I will post fully complete/edited
version momentarily. I hope an admin will delete this message and my
prior message to avoid cruft in this thread.
--
You received this bug notification beca
And yes nvidia-drm.modeset=1 will give you back the missing boot
animation, but that discussion should stay in bug 1868240.
--
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/b
Note that we don't recommend use of nvidia-drm.modeset=1 for most users
because it still results in some bugs:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset
And I'm not sure that's even a complete list. So you should be aware of
what you're getting into.
--
You received
I'm trying to break this down further:
This block is the set of keys which I've included the byte output for in
a reply further back, repeated for clarity. This block is currently not
interpreted by the kernel as anything I guess due to the vendor specific
page:
0x06, 0x31, 0xFF, // Usage Page (V
The USB descriptor for the affected device:
0x06, 0x31, 0xFF, // Usage Page (Vendor Defined 0xFF31)
0x09, 0x76,// Usage (0x76)
0xA1, 0x01,// Collection (Application)
0x85, 0x5A,// Report ID (90)
0x19, 0x00,// Usage Minimum (0x00)
0x2A, 0xFF, 0x00, // Usage M
Removing packages from focal:
linux-meta-oem-5.4 5.4.0.1002.4 in focal
Comment: superseded by linux-meta-oem-5.6; LP: #1872635
1 package successfully removed.
** Changed in: linux-meta-oem-5.4 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you
Removing packages from focal:
linux-oem-5.4 5.4.0-1002.4 in focal
linux-buildinfo-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64
linux-headers-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64
linux-image-unsigned-5.4.0-1002-oem 5.4.0-1002.4 in focal amd
Removing packages from focal:
linux-restricted-modules-oem-5.4 5.4.0-1002.4 in focal
linux-modules-nvidia-390-5.4.0-1002-oem 5.4.0-1002.4 in focal
amd64
linux-modules-nvidia-390-oem-20.04 5.4.0-1002.4 in focal amd64
linux-modules-nvidia-440-5
Removing packages from focal:
linux-signed-oem-5.4 5.4.0-1002.4 in focal
linux-image-5.4.0-1002-oem 5.4.0-1002.4 in focal amd64
Comment: superseded by linux-oem-5.6; LP: #1872635
1 package successfully removed.
** Changed in: linux-signed-oem-5.4 (Ubuntu)
Status: Ne
I noticed that after boot with badly initialized GPU idle power
consumption is 2-2.5 higher than after normal boots.
But this can be fixed by putting laptop to suspend and waking it.
Therefore I've extended my workaround from #3 to this:
[Service]
Type=oneshot
ExecCondition=/bin/sh -c "journalct
@Rajat Pandita: awesome, thanks for sharing!
I came here to report that I too was experiencing this bug: GTX 1060,
up-to-date Focal Fossa beta, NVidia 440 driver series, 5.4.0-24 kernel.
Couldn't log in.
Removing `splash` from grub's kernel parameters solved the issue, but
adding `nvidia-drm.mode
This bug was fixed in the package linux - 5.4.0-25.29
---
linux (5.4.0-25.29) focal; urgency=medium
* focal/linux: 5.4.0-25.29 -proposed tracker (LP: #1873459)
* [TGL] VMD support in TGL (LP: #1855954)
- PCI: vmd: Add bus 224-255 restriction decode
- PCI: vmd: Add device
This bug was fixed in the package linux - 5.4.0-25.29
---
linux (5.4.0-25.29) focal; urgency=medium
* focal/linux: 5.4.0-25.29 -proposed tracker (LP: #1873459)
* [TGL] VMD support in TGL (LP: #1855954)
- PCI: vmd: Add bus 224-255 restriction decode
- PCI: vmd: Add device
I did a bisect for this bug, now it is weekend and I was able to do
tests on this computer. The bisect result is:
51d69817519f5f00041a1a039277f0367d76c82c is the first new commit
commit 51d69817519f5f00041a1a039277f0367d76c82c
Merge: 0174cb6ce944 f3efc406d67e
Author: Linus Torvalds
Date: Wed Ja
I’ve had the same problem during installation Ubuntu 20.04 Beta and last
daily release.
I’m not sure if it’s necessary but my PC spec is Intel i9
9900k/RTX2080Ti.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
After doing some research I'm quite sure that this bug was introduced by [1] in
the 5.4.29 mainline kernel and the 5.4.0-22.26 ubuntu kernel.
The bug was already fixed by [2] in the 5.4.32 mainline kernel. At least that's
the case on my machine [3] and Heiner Kallweit also pointed in this directi
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873684
Title:
bug #1320282
Status in linux
Public bug reported:
Computer restarts when i tell it shutdown. Does not happen when shutdown
from grub menu.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-96-generic 4.15.0-96.97
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873677
Title:
Lenovo Ideapad S145 - Touchpad
*** This bug is a duplicate of bug 1871182 ***
https://bugs.launchpad.net/bugs/1871182
Should be fixed by:
net: phy: realtek: fix handling of RTL8105e-integrated PHY
** This bug has been marked a duplicate of bug 1871182
[RTL810xE] No ethernet connection
--
You received this bug notifica
Public bug reported:
Touchpad not working and does not show in /proc/bus/input/devices
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-24-generic 5.4.0-24.28
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11
Did a Fresh Install today, and Selected the option to automatically install
proprietary drivers, Something changed and my Installation Failed, I got a
message saying that there was already a bug for that, I followed along and
updated my situation in that bug report, because why not, It is just a
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873673/+attachment/5356793/+files/syslog.xz
--
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/1873673
T
Public bug reported:
Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs 3.0
- one with an external HD connected, and one USB-C)
I noted that the mouse and keyboard using one Logitech Unifying receiver
(connected through USB on the Laptop, not dock) started to jump over the
screen
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873673
Title:
Kernel Error IRQ
Status in li
** Attachment added: "lsusb --tree -vv"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873673/+attachment/5356792/+files/lsusb-tree-vv.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: oem-priority
Importance: Undecided => Critical
--
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/1855954
Title:
[TGL] VMD support in TGL
Status in HWE Next:
New
Status
usbcore.quirks=056a:5146:m also failed for me (with 19.10 and focal); I
read on the Arch wiki that disabling Thunderbolt in the bios (under
Security -> IO ports) might work and tried it, and it worked!
I imagine this breaks Thunderbolt, but have no way to test.
--
You received this bug notificat
*** This bug is a duplicate of bug 1871182 ***
https://bugs.launchpad.net/bugs/1871182
So now I build a kernel based on 5.4.0-24-generic with [1] on top of it
and it indeed fixed the problem for me.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.32&id=3fcd
No amelioration with Ubuntu 20.04 beta.
--
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/1850439
Title:
No sound on ASUS UX534FT
Status in linux package in Ubuntu:
Confirmed
Bug descri
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 1873644
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Another important note: this module is included to initramfs so this
"fix" fixes nothing, in fact breaks stuff
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Still present in the nvidia-graphics-drivers-440 package, sigh.
To reproduce, it's still as simple as "Start playing a video with VLC in
user #1, switch to user #2 for a couple of seconds, switch back to user
#2 to see a black screen in VLC and hundreds of megabytes of error
messages in the logs".
Public bug reported:
No network connection since 5.4.0-24 kernel update, `dmesg` output
contains the following unusual line:
[2.450854] r8169 :01:00.0: realtek.ko not loaded, maybe it needs
to be added to initramfs?
Important note: this module is available and listed in the `lsmod`
outpu
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 1873644
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
bluetooth cannot connect
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-174-generic 4.4.0-174.204
ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211
Uname: Linux 4.4.0-174-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Cu
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873641
Title:
pulseaudio says: ALSA woke us
Um, that should say I got a "single" report like this in syslog so far.
--
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/1873641
Title:
pulseaudio says: ALSA woke us up to write new data t
Public bug reported:
Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to the
device, but there was actually nothing to write.
Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA
driver 'snd_hda_intel'. Please report this issue to the ALSA developers
https://patchwork.freedesktop.org/series/75941/ was merged as
https://cgit.freedesktop.org/drm/drm-
tip/commit/?id=0f8925090ac7ad451ed9e803662ebe3214dc8072
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
65 matches
Mail list logo
