Issue started reoccurring with upgrade to 5.8.0.44, only after a screen
lock, and ALT-F2 + 'r' fixes the problem until the next screen lock.
--
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/1
This bug reoccurred just now for the first time since I installed the
patched kernel.
Am currently on
```
Linux floombort 5.8.0-34-generic #37-Ubuntu SMP Thu Dec 10 18:01:14 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
```
And Alt+F2 then 'r' fixed it again.
--
You received this bug notification b
No re-occurrences of the issue since installing the new kernel on 12-02.
--
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/1896091
Title:
[i915] Noise-like lines of graphics corruption when
I have installed "5.8.0-32-generic #34-Ubuntu" and will report if I
experience the issue again. It sometimes takes a couple of days to
manifest.
--
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
Public bug reported:
Trackpad and keyboard don't work past the GNU boot menu, including they
do not work in recovery mode.
Have tried updating all drivers and reinstalling drivers. Have tried
repairing OS.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-26-generic 5.8.0-2
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
I am experiencing this issue as well, but don't know how to extract the
19.10 default.pa from the .deb package. Can someone who has successfully
applied this solution please post which lines they changed/add
This fix has been reverted in qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 to align
with Zesty. qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 has now been released to
ocata-updates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
qemu (1:2.8+dfsg-3ubuntu2.9~cloud1) xenial-ocata; urgency=medium
* reverted "Backport support for GICv3/vITS save/restore (LP 1710019)."
as there was an arm regressions found in zesty-proposed (cancelled before
SRU release).
--
You received this bug notification because you are a membe
** Changed in: cloud-archive/ocata
Status: Fix Released => Triaged
--
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/1710019
Title:
support GICv3 ITS save/restore & migration
Status
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.8~cloud0
---
qemu (1:2.8+dfsg-3ubuntu2.8~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.8+dfsg-3ubuntu2.8) zesty; urgency=medium
.
* Backport support for GICv3/vITS sa
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we c
Hello dann, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo add-apt-rep
I do not see the same behaviour as Johann:
cschuhen@loriel:/tmp$ for i in 1 2 3 4; do curl -s
http://de.releases.ubuntu.com/zesty/ubuntu-17.04-server-amd64.img -o $i.iso;
md5sum $i.iso; done
4672ce371fb3c1170a9e71bc4b2810b9 1.iso
4672ce371fb3c1170a9e71bc4b2810
The issue appears solve for me with 4.10.0-33 on zesty. I assume that an
open invitation for anybody to change the tag to verified.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages,
I just accidentally clicked on "Fix Releeased" thinking it would provide
more info rather than change the status ;/
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
As at March 18th 2016, confirming that following the guide at the top of
the page as well as the Backports method as described at Comment #90
fixed the problem and wifi now works on my Acer Aspire V17. Have
attached relevant output from lspci and modinfo confirming h/w
configuration for those inte
Chris, I have the email ready to send but I can't seem to figure out
where to find the email addresses for Johannes Berg and Kalle Valo.
Could you advise where I could find those?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Ooh ok I got it, sorry its been a long day.
The build number is LRX22C.N915VVRU2BOJ7
--
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/1538673
Title:
Atheros Qualcomm Killer N1525 Wire
Oh so then its just 5.0.1, I just bundled that with the OS, my bad.
--
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/1538673
Title:
Atheros Qualcomm Killer N1525 Wireless-AC Cannot Connect
I'm sorry that part slipped my mind?
Samsung
Galaxy Note Edge
Android 5.0.1
And I'm not sure what you mean by firmware, if you mean kernel its 3.10.40
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I think you meant laptop not phone,
MSI
GS60-2QE
Ubuntu Gnome 15.10
BIOS E16H5IMS.10H
--
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/1538673
Title:
Atheros Qualcomm Killer N1525 Wireles
** 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/1538673
Title:
Atheros Qualcomm Killer N1525 Wireless-AC Cannot Connec
The log in the attachment is not what I had in the description
originally, you can see this by viewing the original description, but if
its not helping anyone anyway I will just remove it.
The bug was not fixed upstream, will add tags
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
u
Also the log that is linked in the original post now is neither from my
laptop nor a laptop with this wifi card. I'm not sure if that was
intentional or not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Thank you for finding that, a few days ago that page was empty.
1)
E16H5IMS.10H
07/28/2015
2) There was no improvement, the firmware still crashes attempting to
connect to a wireless ac network.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug noti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557796/+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/15
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557798/+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/1538673
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557805/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557804/+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/1538673
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557799/+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/1538673
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557802/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557801/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557803/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557800/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557797/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557795/+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
** Tags added: apport-collected wily
** Description changed:
Ubuntu Gnome 15.10
I do not know what package this error is a part of or if it is even part
of a package as I am not familiar enough with linux. I know it is the
ath10k_pci module.
Expected: The wifi
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1538673/+attachment/4557794/+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/1538673
Ti
Public bug reported:
Ubuntu Gnome 15.10
I do not know what package this error is a part of or if it is even part
of a package as I am not familiar enough with linux. I know it is the
ath10k_pci module.
Expected: The wifi would connect to the access point.
Actual: Firmware crashes twice then Ne
** Description changed:
When attempting to connect with the Microsoft Bluetooth Mobile Keyboard
- 6000 keyboard a pin should be generated but it isn't, and the bluetooth
+ 5000 keyboard a pin should be generated but it isn't, and the bluetooth
pairing fails.
/var/log/syslog shows:
- Age
Public bug reported:
When attempting to connect with the Microsoft Bluetooth Mobile Keyboard
6000 keyboard a pin should be generated but it isn't, and the bluetooth
pairing fails.
/var/log/syslog shows:
Agent replied with an error: org.bluez.Error.Rejected, Rejected bluetoothd
generated PIN co
The fix in the first post for 15.10 does not seem to work, I can see the
networks but not connect. Eventually I'm not even able to see the
available networks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Public bug reported:
It appears that the upgrade will refuse to continue.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: crash (not installed)
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd6
ard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: corey 2385 F pulseaudio
/dev/snd/controlC0: corey 2385
reeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: corey 2385 F pulseaudio
/dev/snd/controlC0: corey 2385 F pulseaudio
en hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: corey 2385 F pul
ze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC
nfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/c
ze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
ze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/c
ze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
ze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
nfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
undock they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/c
ck they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
ze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
they unfreeze. If I
dock when hdmi is not connected to the dock, the mouse and keyboard
don't freeze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/con
eze.
Ubuntu release: 14.04 Trusty Tahr (development branch)
+ ---
+ ApportVersion: 2.13.2-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: corey 2385 F pulseaudio
+ /dev/snd/controlC0: corey 2385 F pulseaudio
+ Curre
** 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/1275794
Title:
Lenovo T440s freezes when connected to docking station
Status in “linux” packa
64 matches
Mail list logo
