As mentioned above, this turns out to have been a Chrome/Chromium bug
exposed by the new kernel. It has been fixed in Chrome 123, which is now
the stable release. This issue can be closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Mainline kernel 6.6.1 also exhibits this regression.
--
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/2043299
Title:
Linux 6.5 breaks Novation Components web MIDI application
Status in li
And here's the syslog for the last 6.4 kernel, from the moment the
device is plugged in to the moment the app states the connection is
good. Other than some slight timing changes and the absence of the
"falling back to MIDI 1.0" message, not much has changed.
** Attachment added: "syslog-6.4.16-06
Yes it's a regression. Here's the syslog using the current kernel from
the moment the device is plugged in to the moment the app gives up on
communication.
** Attachment added: "syslog-6.5.0-10"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+attachment/5718992/+files/syslog-6.5.
Public bug reported:
Ubuntu version: 23.10
Kernel version: 6.5.0-10
Steps to recreate:
1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
2. Navigate to https://components.novationmusic.com/
3. Connect a Novation Circuit Tracks via USB
Expected behaviour (demonstrated by l
I have the same problem. The Release Notes for 21.2 has a section titled
"Solving freezes during the boot sequence" that sounds similar this problem.
Even though I have an AMD video board instead of NVIDIA, I tried the listed
fixes to no avail. I gave up and went back to vmlinuz-5.15.0-84-generi
ia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: edward 2854 F wireplumber
/dev/snd/seq:edward 2850 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Aug 14 15:05:10 2023
Er
@kmhallen0. I discovered that reinstalling driver 525.85.12 worked as
well. I think that the real problem is that Ubuntu Software Updater did
not install the NVIDIA drivers correctly. I have not tried the
5.19.0-32 kernel. Thanks for responding.
--
You received this bug notification because yo
I ran "apport-collect 2009226" while booted to 5.19.0-32, not while
booted to 5.19.0-35 because X/Wayland doesn't start in 5.19.0-35. If
apport-collect will run in a terminal window then I can boot to
5.19.0-35 and run apport-collect if needed/helpful.
--
You received this bug notification becau
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651503/+files/WifiSyslog.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/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651502/+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/2009226
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651504/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651499/+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/2009226/+attachment/5651501/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651498/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651497/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651500/+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: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651496/+files/PaInfo.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/2009226
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651495/+files/Lsusb-v.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/2009
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651494/+files/Lsusb-t.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/2009
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651493/+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/2009226
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651491/+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/2009226
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651492/+files/Lspci-vt.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/20
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2009226/+attachment/5651490/+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 jammy wayland-session
** Description changed:
- I updated software this morning and on reboot ubuntu kernel 5.19.0-35
- gives black screen. It appears to be an issue with graphics as I can
- access a console and login. I am able boot and run no
** Description changed:
- I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
- It appears to be an issue with graphics as I can access a console and
- login. I am able boot with 5.19.0-32-generic. I am using nvidia
- drivers.
+ I updated software this morning and on reboot ubun
I am not running in problematic update but I have attached sudo lspci
-vnvn > lspci-vnvn.log
** Attachment added: "output of sudo lspci -vnvn > lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+attachment/5651446/+files/lspci-vnvn.log
--
You received this bug not
Public bug reported:
I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
It appears to be an issue with graphics as I can access a console and
login. I am able boot with 5.19.0-32-generic. I am using nvidia
drivers.
** Affects: linux (Ubuntu)
Importance: Undecided
May have been solved by:
sudo pip uninstall distro-info
sudo apt install --reinstall python3-distro-info
ref: https://askubuntu.com/questions/1137645/python-error-when-
upgrading-from-18-10-to-19-04
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
I made the terminal window several screens' tall, to see the following
(before the screen gets blanked by the install process - why would it do
that?):
Reading cache
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://securi
Public bug reported:
$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,265 kB]
Public bug reported:
Tired X.org, Other Nvidia Drivers, swapping and changing cables,
lowering refresh rates, swapping over the HDMI to other monitor
(ThinkVision can not remeber) now the second monitor has the exact
same problem and the first one via DP is perfect (not a problem of the
monit
@andch
You're a genius. Turns out I just needed to reset the BIOS to default
settings!
Thanks a ton!
--
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/1955383
Title:
Support Inte
@kchsieh
No, the webcam light doesn't turn on even on webcamtest. I don't think I
have tried the oem image from Dell's website. Do you think you could
attach a link to it? I can't seem to find it. I ran $ journalctl -k -b
and the results of this are attached in "results.txt". I also ran $ cat
/sys
@kchsieh
Hi, so I tried following the wiki for 20.04, but that didn't work, so I
just ended up upgrading to 22.04 and tried what comment #79 mentioned
but I'm still getting a black screen. I ran $ dpkg-query -W again and
here are the results:
accountsservice 22.07.5-2ubuntu1.3
acl 2.3.1-1
acp
@kchsieh
I tried doing what you said by enabling the oem meta then upgrading the
distro, but I'm still getting a black screen with the webcam. I also ran
$ dpkg-query -W and here are the results:
accountsservice 0.6.55-0ubuntu12~20.04.5
acl 2.2.53-6
acpi-support0.143
acpid 1:2.0.32-1ubu
I just got a new XPS 13 plus 9320 and it came with Windows 11. I
replaced it with Ubuntu 22.04, but the Webcam wasn't working so I
replaced that with Ubuntu 20.04, but the webcam still doesn't seem to be
working. I tried:
$ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
$ sudo apt inst
** Project changed: maas-deployer => maas
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1911360
Title:
Nvidia-Graphics-Drivers-460 Causes System To Not Boot
Statu
I am seeing the same problem on a Dell Precision 7750.
Ubuntu 20.04LTS
kernel: 5.11.0-27-generic #29~20.04.1-Ubuntu SMP
graphics: VGA compatible controller: NVIDIA Corporation TU106GLM [Quadro RTX
3000 Mobile / Max-Q] (rev a1)
plus Intel i915
processor: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Chris,
With the following packages installed and the workaround removed the
issue no longer occurs for me when enabling Automatic Login via
Settings. I have tested rebooting and starting from off several times
and it worked as expected each time. Previously the issue occurred on
every boot.
gdm
I had difficulties installing Kernel 5.8-rc3. But I tested 5.8.1:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/
Lenovo Ideapad L340-17API (81LY000KGE): No black screen in 6 attempts.
The notebook also booted much faster. Before, there had always been a
kind of "pause", during which it ma
... further to # 30: it would have been nice, but actually the Lenovo
Ideapad L340-17API (81LY000KGE) still occasionally gets a "black
screen". Weird: after numerous positive attempts (something like 10),
the odd boot goes to black screen. Then a "series" of black screens
seems to start.
--
You r
I have experienced the problem with the black screen in battery mode in
all my (fairly new) AMD notebooks (bought this year; all AMD Ryzen 5
3500U), running Kubuntu 20.04. As of today the status is as follows:
- Lenovo Ideapad L340-17API (81LY000KGE) (possibly identical to the one
in #21). Kernel
So I don't know if this will help or not, but I have troubleshot my P50
turns off on resume from sleep issue. I have Ubuntu on a 2 TB Samsung
970 EVO NVME SSD (with 2B2QEXM7 firmware). If I remove the password
(User and Master) from this disk resume from sleep works. I have 2
other Samsung SSDs
So my fix worked for a couple of days, then stopped working. I think
there was a kernal upgrade a couple of days ago (on Ubuntu 20.04, now
running 5.4.0-37-generic), and I am now shutting down on resume. Sleeps
normally, LED blinking, displays off, no heat produced. When I open the
lid the LED i
Add me to the list of those having this issue, but also have a partial
fix. I am running a Thinkpad P50 with Nvidia display adapter. 18.04
was great, never any issues with suspend or resume. I upgraded to 20.04
a couple of weeks ago and immediately began encountering the reboot on
resume issue.
Regenerating initramfs as suggested by Dan resolved this issue for me.
I did not attempt to change compression or change any settings in the
BIOS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
I upgraded to 5.5-rc6 and this appeared to fix things. I did not need
to update the firmware.
--
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/1858231
Title:
QCA6174 Wifi adapter not func
Sorry, wasn't getting launchpad emails.
I'll try with the latest kernel and firmware shortly.
--
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/1858231
Title:
QCA6174 Wifi adapter not func
** Attachment added: "lspci"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+attachment/5317468/+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/185823
Public bug reported:
The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from
the live cd and an install. It is functional in a 18.04 install.
At boot, the kernel log contains the following messages in 19.10:
[ 15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity
For reference, this is the extensive upstream kernel discussion
https://bugzilla.kernel.org/show_bug.cgi?id=201685
The filesystem corruption issue is real, not theoretical, and
was the extensive discussion of problems experienced during the early days of
4.19:
** Bug watch added: Linux Kernel
This data corruption issue was written about extensively here
https://lwn.net/Articles/774440/
as part of the early 4.19 days when a number of folks were seeing ext4
filesystem corruption as a consequence of the blk-mq bug.
--
You received this bug notification because you are a member of Kerne
No applicable logs
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (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/
This bug is easily reproduced and will not leave any meaningful log
entries.
--
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/1808251
Title:
systemctl disable fails to clean up override
S
Public bug reported:
I am using Ubuntu 16.04.4 LTS and package version
systemd:
Installed: 229-4ubuntu21.10
Candidate: 229-4ubuntu21.10
Version table:
*** 229-4ubuntu21.10 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://security.u
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Edward Haigh (funcylambda)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1585364
Title:
CVE-2014-8
** Changed in: linux (Ubuntu Xenial)
Assignee: Edward Haigh (funcylambda) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1585364
Title:
CVE-2014-8
HI guys,
Im trying to use my second Monitor with this videocard, i do not know if
i have the same issue but my HDMI monitor just would not work. it worked
before the update and only with kernels until 4.13... i don't know if i
have to put some info here or somewhere else.
thanks.
--
You receive
I am on Linux version 4.15.0-33-generic (buildd@lcy01-amd64-024) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #36-Ubuntu SMP and the bluetooth
is not working.
Please help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
i have the same exact problem
lsusb | grep -i blue
Bus 003 Device 002: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth
4.0
uname -a
Linux ednote 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available.
Thanks Dann. Scott is testing this and has found an additional issue,
but we're not sure yet whether it's directly related or independent.
He'll file a more detailed report or open another Launchpad as
appropriate.
--
You received this bug notification because you are a member of Kernel
Packages,
Thank you. We will be testing this new kernel at Packet and will report
results.
--
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/1736593
Title:
ThunderX: TX failure unless checksum offloa
What I did to get it working for now is creating a modified ISO with
kernel version v4.11.12 that has support for this RAID controller. Works
fine, so hope this patch is applied to the default kernel that is
shipped with Ubuntu soon.
--
You received this bug notification because you are a member
Hi
I have a new Dell PowerEdge R640 server a PERC H740P RAID Controller.
I tried to install the latest 16.04 LTS Ubuntu on it, but during
installation it failed to detect any disks. After pulling my hair out
while diagnosing this issue for hours I finally found this thread.
Can anyone confirm th
@Marc,
thanks a lot mate! you are saving the day of all of us. Hope u are not
from the NSA heheheh. thanks a lot mate!
--
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/1671360
Title:
Syst
Hi guys,
i think we should do something about this gigabyte-situation, kinda of
writing then a bunch of letters from all of us, there is also a bunch of
ppl on reddit having this same problem, and still, gigabyte is not
giving a breath to address this situation... do we really have to accept
this
Just attempting to install package results in:
root@edwardnewman-MacBookPro:~# dpkg -i
/var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb
(Reading database ... 194747 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.10.0-20_4.10.0-20.22_all.deb
@jsalisbury
Ran steps with same result
root@edwardnewman-MacBookPro:~# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
linux-headers-4.10.0-20
Public bug reported:
Trying to upgrade Linux
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-headers-4.10.0-20 (not installed)
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDev
i tried the wrong kernel, now i am using that 4.10.3 (ryzen) kernel, it
works fine
--
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/1671360
Title:
System doesn't boot properly on Gigabyte
i dont understand why i the Joseph's kernel wont let me type (kernel is on, but
aint gonna work) anything :( it looks like the solution for me for, at least
temporal... :(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Marc,
yep i got that.. i desinstalled it so that it would work better.
im running 16.04, i dont know actually what to do, cuz i fond now way to
boot using the keyboard with that kernel, and also both monitors (i
might solve that with the graphic card, but i need to use the keyboard
for that.)
i need to find* sorry, i am writing from my Android device.
--
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/1671360
Title:
System doesn't boot properly on Gigabyte AM4 motherboards (AMD R
i treid to boot with Joseph's kernel and the machine booted, but there
is no way for me to use my keyboard :S
--
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/1671360
Title:
System doesn't
Hi again guys,
ive tried Joseph's kernel but this is what i got...
linux-headers-4.10.0-19-generic (4.10.0-19.21~lp1671360) wird eingerichtet ...
Examining /etc/kernel/header_postinst.d.
Thanks Milosz!
actually i couldnt start the pc like that, im still using the kernel
4.7.8, the good thing is that all cores wore good, like i said... the
problem is that the Network cards are totally crazy and the soundcard
just does not work anylonger since a couple of weeks.
--
You received th
i forgot to mention that i use the f4 version of the bios
--
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/1671360
Title:
System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryz
hi guys,
maybe my information helps a bit (at least a hope)
my PC is a 1700x with the gaming aorus 5 from gigabyte (GA-AX370-Gaming K5),
got 32 GB RAM but i dont think that it has much to do with all the problems
metioned above.
i got all those errors, and i can only use my computer with my n
SERPID ACCESS COMMAND
- /dev/snd/controlC0: Edward-admin 1721 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: Edward-admin 1721 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jan 3 13:37:32 2017
GvfsMonitorLog: Monitoring events. Press Ctrl+C to q
x 4.4.0-57-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: Edward-admin 1721 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jan 3 13:37:32 2017
GvfsMonitorLog: Monitoring events. Press
35
Uname: Linux 4.4.0-57-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: Edward-admin 1721 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jan 3 13:37:32 2017
GvfsMonitorLog: Monitor
stroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78
ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
Uname: Linux 4.4.0-57-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
inux 4.4.0-57-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: Edward-admin 1721 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jan 3 13:37:32 2017
GvfsMonitorLog: Monitoring events. Pr
/controlC0: Edward-admin 1721 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jan 3 13:37:32 2017
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28
HotplugNewDevices:
HotplugNewMounts:
InstallationDate
md64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: Edward-admin 1721 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jan 3 13:37:32 2017
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=cd636119-7499-4207-
ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
Uname: Linux 4.4.0-57-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: Edward-admin 1721 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jan 3 13:37:32 2017
I was able to replicate this failure on an ARMv8 (aarch64) xenial
system, using the supplied instructions for QEMU and getting the
modprobe error.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
** Bug watch added: Linux Kernel Bug Tracker #65201
http://bugzilla.kernel.org/show_bug.cgi?id=65201
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=65201
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of K
Yes, I'm relatively sure.
--
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/1461738
Title:
iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after
500ms
Status in linux pa
Public bug reported:
I have Ubuntu Precise guests running in kvm to which I attach volumes
immediately after boot. Sometimes I notice that the devices do not show
up in the guest e.g. they are not visible in /proc/partitions and dmesg
boot log shows no sign of then being noticed. Qemu itself shows
** Description changed:
I have Ubuntu Precise guests running in kvm to which I attach volumes
immediately after boot. Sometimes I notice that the devices do not show
up in the guest e.g. they are not visible in /proc/partitions and dmesg
boot log shows no sign of then being noticed. Qemu i
Utopic. Looking at leftover kernels on my system, probably 3.16.0-36?
--
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/1461738
Title:
iwl3945 on X61T crashes with Error sending C_POWER_TBL
This problem did occur in a release prior to vivid.
It's hard for me to report exactly when the problem started occurring,
because most of the time I use ethernet, and there seem to be some
wireless networks which are more likely to tickle the problem than
others.
--
You received this bug notifi
Tested on upstream kernel, bug exists, marking confirmed as per
instructions.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.1rc6
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kerne
I regretfully report that I can reproduce the error, with the same error
in dmesg.
ezyang@sabre:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for ezyang:
7SET39WW (1.25 )
03/22/2011
Here's just the starting bit of dmesg from the re-reprod.
[ 3190.3120
OK, I've updated my BIOS and I will see if the problem happens again. If
not I'll close this 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/1461738
Title:
iwl3945 on X61T crashes wi
Oh, I also have another X61 which I could dust off and use to test for
the bug, if that would be helpful.
--
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/1461738
Title:
iwl3945 on X61T cr
Public bug reported:
After using wireless for some period of time, it stops working. dmesg
report is attached. Rebooting the machine makes the wireless driver work
again (for a little bit anyway). I haven't checked if it's related to
suspend/resume, but I use this a lot. I can try bisecting for a
Per Linda Knippers (HP) :
Why are you blacklisting the watchdog timers? It seems like if corosync wants
to use them, which is why it would open /dev/watchdog, then there's either a
corosync bug or there's something in the configuration that isn't right. Is
anyone looking into that?
For cluste
1 - 100 of 156 matches
Mail list logo
