Before the update i had to run bluez-simple-agent to get bluetooth
working. Now it just does not find the device. I tested bluetooth with a
usb bluetooth dongle, and bluetooth transfers work, given that bluez-
simple-agent command is running. I can even discover the native
bluetooth adapter
After the latest update, bluetooth is working without a problem. No
workaround is required. However, bluetooth breaks after suspend resume.
Following is a hcidump of a suspend resume action.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
After the latest update, bluetooth is working without a problem. No
workaround is required. However, bluetooth breaks after suspend resume.
Following is a hcidump of a suspend resume action.
** Attachment added: hci.log
Hey guys, i'm on gigabyte u2442n and stopped using ubuntu a couple of
month ago because of this bug (mainly use touchpad b/c travelling). Do I
understand correctly that kubuntu 14.04 and newer or 3.16 seem to have a
fix for this issue? Would love to switch again.
--
You received this bug
I also have the same problem on Ubuntu 18.04.2.
The login screen starts normally, but right after typing my password and
pressing enter the screen is black.
The problem started after an NVIDIA driver update with "apt upgrade". I was
using the nvidia driver form the CUDA Repository.
I tried
This bug seems to affect me with a Dell XPS 16 2024. I get the following
dmesg output if it is of any use:
[2.844944] intel-ipu6 :00:05.0: enabling device ( -> 0002)
[2.845217] intel-ipu6 :00:05.0: Device 0x7d19 (rev: 0x4)
[2.845232] intel-ipu6 :00:05.0: physical base
** Package changed: alsa-driver (Ubuntu) => firmware-sof (Ubuntu)
** Changed in: firmware-sof (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
The IPU6 webcam still does not work on my Dell XPS 16 (9640). I've
tested it with Ubuntu 24.04 daily builds including with the 6.9-rc1
kernel. What information would you need to check the problem?
--
You received this bug notification because you are a member of Kernel
Packages, which is
/controlC0: moritz 2278 F kmix
moritz 2284 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf462 irq 22'
Mixer name : 'Realtek ALC888'
Components : 'HDA
Can also confirm the bug. There seems to be a workaround:
Brightness controls do work in terminal mode (Ctrl+Alt+F1) and the change is
kept when in GUI mode (Ctrl+Alt+F7).
For me, when I use the brightness controls in Gnome, I can see and move the
(ThinkPad-) control slide but changes are not
I think I have the same problem with a Thinkpad T450s.
Kernel 3.16.0-34 boots fine.
Trying to boot 3.16.0-36 instead shows the same behaviour as reported in
bug description.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Same problem on Thinkpad T450s (Broadwell chip) and Trusty.
3.16.0-34 works fine, 3.16.0-36 just shows black screen with backlight
lit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
To confirm Stoepsel: 3.16.0-37 doesn't boot on my Thinkpad T450s either.
--
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/1450156
Title:
kernel 3.16.0-36 won't boot on Lenovo Thinkpad X1
Thanks for the hint, Timo!
3.16.0-37.51 also doesn't boot on my T450s.
Boot process gets stuck displaying:
Loading Linux 3.16.0-37-generic
Loading initial ramdisk
I installed the .deb from the link you provided, Timo, and aptitude
tells me the -51 version is installed:
$ sudo aptitude show
I have to correct my last comment:
3.16.0-37.51 does boot.
I had to install the linux-image-extra package, too, which I didn't in
the first try.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If someone could point me to a doc on how to install 3.16.0-37.51 in
Trusty, I would be happy to test it.
I enabled the proposed repository and tried sudo apt-get install linux-
image-3.16.0-37-generic/trusty-proposed but it tells me I already have
the newest version, which is
The one in the public Trusty repositories (3.16.0-37.49~14.04.1.)
doesn't work on my T450s.
I don't know how to install 3.16.0-37.51. I have the proposed repository
enabled and tried sudo apt-get install linux-image-3.16.0-37-generic
/trusty-proposed but it tells me I already have the newest
Could we please fast-track this solution? My laptop is crashing every
other hour because of it :/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1451789
Title:
bcmwl causes system
Public bug reported:
The trusty kernel can crash if the OOM killer kills processes which have
reached a memory limit imposed by cgroups. More details can be found in
this blog post:
https://community.nitrous.io/posts/stability-and-a-linux-oom-killer-bug
The upstream patch series which
This looks good to me: We have been running the test kernel on nine
production servers for more than a week now and the systems are stable
(while previous we'd seen three kernel hands over the course of 48
hours).
--
You received this bug notification because you are a member of Kernel
Packages,
I've installed the 3.13.0-92.139 kernel from trusty-proposed on eight
production systems. I'll let you know by Monday.
--
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/1592429
Title:
I am having this problem (only dummy output) on ubuntu 19.10 with linux kernel
5.3.0.45.38. After booting I can make the output show up and work by running
pulseaudio -k && sudo alsa force-reload
Maybe that workaround helps other people suffering from this problem until a
fix is available.
--
I have had this on 19.10 (see https://bugs.launchpad.net/ubuntu/+source
/linux-oem-osp1/+bug/1864061/comments/42) and on 20.04.
Adding "options snd-hda-intel dmic_detect=0" to the end of
/etc/modprobe.d/alsa-base.conf has apparently fixed the issue on 20.04
(microphone is still working).
I
Seeing 'timidity' in the data collected by apport I have just
uninstalled timidity. This has immediately restored the availability of
the sound output. Also after rebooting, sound output is working again (I
have since rebooted twice).
--
You received this bug notification because you are a
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376574/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I had thought that appending
options snd-hda-intel dmic_detect=0
to /etc/modprobe.d/alsa-base.conf
had fixed the problem. But the problem has since reappeared.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376573/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376569/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376568/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376575/+files/WifiSyslog.txt
** Description changed:
After booting the system the internal laptop speakers and the internal
microphone are sometimes not detected, pavucontrol
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376560/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
After booting the system the internal laptop speakers and the internal
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
They were working fine under ubuntu 18.04, stopped working after upgrading to
19.10 and are still not working under 20.04.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376563/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376566/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376564/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376562/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376565/+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/1880571
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376567/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376561/+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/1880571
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376571/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376572/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376570/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
As asked by @Hui Wang, I have created a separate bug #1880571 for my
problem on focal fossa and run apport-collect. As the data collected by
apport showed that timidity was running I have uninstalled timidity and
this seems to have fixed the problem: audio output was immediately
restored, and
** Also affects: timidity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
** Changed in: pulseaudio (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
I think we have some options to fix this. Yet, which would be a solution
that could be packaged? If I understand
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html
correctly there are the following options:
Keep the GPU-Memory Running
===
I tried Ubuntu 17.04, still the same issue.
--
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/1686189
Title:
External monitor connecting problem on Intel graphics card
Status in linux
The drm nightly kernel works for me (4.12.0-994-lowlatency). However, I
do not have WLAN.
--
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/1686189
Title:
External monitor connecting
@Kai-Heng:
I do use a mini Displayport Cable with a Lenovo Thinkpad T460S. In the
meantime I tried every kernel I could install using ukuu. However, none
of them worked. Prior to Ukuu I did use a kernel from the nightly builds
(drm-intel) and the monitor worked but WLAN not. Therefore, I
Still the same issue:
4.11.7-041107-generic #201706240231 SMP Sat Jun 24 06:33:20 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
VGA compatible controller: Intel Corporation Sky Lake Integrated
Graphics (rev 07)
i915 1495040 9
i2c_algo_bit 16384 1 i915
drm_kms_helper
This should affect all embedded java uses which launch the JVM on the
main thread (the regular java launcher does not do that) and is caused
by the known buggy (http://www.openwall.com/lists/oss-
security/2017/06/22/6) custom CVE-2017-1000364 fix. Testing the upstream
patch on debian it seems to
I just wanted to confirm that Tim's workaround/fix of changing the boot
command line in /etc/default/grub works wonderfully!
--
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/1308264
Title:
51 matches
Mail list logo
