Occurs with 5.15.0-75-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2009672
Title:
Regression: Unable to show the native 1920x1080 mode in
HDMI/DisplayPort
** Description changed:
My computer can not show in 1920x1080 mode with 50Hz or 60Hz refresh
rate. I am using Xubuntu 20.04. In my system HDMI is just a Displayport
connector with an adapter. xrandr lists the video modes of the connected
HDMI monitor, and it does not show any error
** Description changed:
- System can show image in HDMI output during bootup. I don't know which
- mode it is using during bootup. Anyway it can not show image in
- 1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my
- system HDMI is just a Displayport connector with an adapter.
Bug occurs with 5.15.0-71-generic, too.
** Summary changed:
- Regression: Unable to show the native 1920x1080 mode in HDMI output
+ Regression: Unable to show the native 1920x1080 mode in HDMI/DisplayPort
output with best refresh rates
--
You received this bug notification because you are a
$ inxi -G
Graphics: Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics
driver: i915 v: kernel
Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded:
fbdev,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1)
** Summary changed:
- Regression: Unable to show 1920x1080 mode in HDMI output
+ Regression: Unable to show the native 1920x1080 mode in HDMI output
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
Possible dubplicate:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012953
** Summary changed:
- Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics
+ Regression: Unable to show 1920x1080 mode in HDMI output
--
You received this bug notification because you are a
** Description changed:
System can show image in HDMI output during bootup. I don't know which
mode it is using during bootup. Anyway it can not show image in
1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my
system HDMI is just a Displayport connector with an adapter.
This could be a duplicate of the bug I reported:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-5.15/+bug/2009672
Did you try setting a lower resolution?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Summary changed:
- Regression: Unable to show 1920x1080 mode in HDMI output
+ Regression: Unable to show 1920x1080 mode in HDMI output of Intel graphics
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
Bug occurs with 5.15.0-69-generic, too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2009672
Title:
Regression: Unable to show 1920x1080 mode in HDMI output
Status in
** Summary changed:
- Unable to show 1920x1080 mode in HDMI output
+ Regression: Unable to show 1920x1080 mode in HDMI output
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
Public bug reported:
System can show image in HDMI output during bootup. I don't know which
mode it is using during bootup. Anyway it can not show image in
1920x1080 mode when using the GUI. I am using Xubuntu 20.04. In my
system HDMI is just a Displayport connector with an adapter. xrandr
lists
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2000313
Title:
System fails to suspend sometimes
Status in linux-signed-hwe-5.15 package in Ubuntu:
New
Bug
** Attachment added: "journalctl extract in case suspend success"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2000313/+attachment/5637198/+files/success
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
Does not enter suspend state successfully sometimes and can not resume.
Must do shutdown by button then. Might have something to do with Audio
Kontrol 1 -audio adapter of which I have reported a separate bug
1855678. However, I succeed to suspend-resume many times, if I
** Description changed:
$ lsusb
..
Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1
..
If I have the device connected when I choose suspend to RAM then display
blanks, suspend fails and system does not respond to any user input
except power button.
+
Still present in 5.13.0-27-generic.
--
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/1855678
Title:
Will not suspend, if I have Native Instruments Audio Kontrol 1
connected
Status in
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Worked with nvidia-340 driver which is no more updated.
- When I resume, nothing works. Macbook keyboard lights are on, but
- otherwise the machine seems dead. Power button reboot needed.
+
Well after some kernel update it may be that Nvidia driver does not work
anymore so I would have to use nouveau or another card..
--
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/1917265
I switched to nvidia-340 driver (via "Additional Drivers"), rebooted and
tested few times that suspend-resume works.
--
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/1917265
Title:
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+attachment/5471858/+files/syslog
--
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/1917265
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+attachment/5471857/+files/kern.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/1917265
I have been using this computer only occasionally. It seems that with
5.4.0-65-generic and later I have had this problem more frequently, but
I had this bug problem few times in May 2020, too (or at least I did not
resume from suspend), but I had several successful resumes after that
(according to
I tried a couple of times. It does not work no matter which mode I use.
--
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/1917265
Title:
Suspending to RAM freezes computer
Status in linux
According to above, exiting suspend has failed only in deep mode, but I
wonder why there is one s2idle mode. Maybe later I rub some tests.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Guilherme, I have mixed result:
$ LC_ALL=C sudo journalctl | grep "PM: suspend" | tail -n 17
Sep 22 11:19:52 jarnos-OptiPlex-745 kernel: PM: suspend entry (deep)
Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend exit
Sep 22 11:20:14 jarnos-OptiPlex-745 kernel: PM: suspend entry (s2idle)
Public bug reported:
When I try to suspend, it does not work: fans keep spinning, but just
screen blanks and computer does not respond to keyboard. 'journalctl -b
-1' does not tell anything suspicious after shut down - start. This used
to work. Might not be reproduceable always.
ProblemType: Bug
Oh, do I have to make a different bug report or address this one to
another package (which one)?
--
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/1855678
Title:
Will not suspend, if I
Booting mainline kernel did not help. Then I added the kernel parameters
for it.
** Attachment added: "journal-5.11.0-051100rc4-generic.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5456252/+files/journal-5.11.0-051100rc4-generic.log
--
You received this bug
** Attachment added: "journalctl -b -1 -k on focal"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5453567/+files/journal.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: focal
--
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/1855678
Title:
Will not suspend, if I have Native Instruments Audio Kontrol 1
connected
Status in linux package in
No, I would not waste my time on that.
** Also affects: xfce4-screensaver (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Power management: does not suspend
+ Suspend does work only after half minute delay.
** Description changed:
I am using Xubuntu 20.04.
I made a couple of tests by Xubuntu Core 20.04 live USB (downloaded from
https://unit193.net/xubuntu/core/). First time was by default settings
i.e. 'lock screen when system is going to sleep' checked - I think that
is not a good default setting for live - and the other time when it was
not
** Description changed:
I am using Xubuntu 20.04.
xfce4-session-logout --suspend
exits with 0, but does not suspend. Same thing, if I choose suspend from menu
(but it may lock screen depending on settings).
- Reproduceable: at least sometimes; used to work at least sometimes with
- this
Public bug reported:
I am using Xubuntu 20.04.
xfce4-session-logout --suspend
exits with 0, but does not suspend. Same thing, if I choose suspend from menu
(but it may lock screen depending on settings).
Reproduceable: at least sometimes; used to work at least sometimes with
this release.
** Attachment added: "journalctl -b -1 -k"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5311740/+files/journalctl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
$ lsusb
..
Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1
..
If I have the device connected when I choose suspend to RAM then display
blanks, suspend fails and system does not respond to any user input
except power button.
ProblemType: Bug
How do you know it crashes?
--
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/1814068
Title:
Crash/black screen when suspend
Status in linux package in Ubuntu:
Confirmed
Bug
But hardware acceleration does not work and image flickers in Kodi
during playback and in use unlike with nvidia driver.
--
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/1815759
Title:
I tried in Xubuntu 18.04 with HWE, kernel 4.18.0-16-generic,
and I get image on external display via HDMI.
xserver-xorg-video-nouveau-hwe-18.04 1:1.0.15-3~18.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fixed in 340.107-0ubuntu0.16.04.2
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu.
Bug #1819077
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu.
https://bugs.launchpad.net/bugs/1573508
Title:
$ dpkg -l |grep 'linux.*-image.*'
ii linux-image-4.4.0-140-generic 4.4.0-140.166
amd64Linux kernel image for
version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-141-generic
Testing this required updating several packages from xenial-proposed
In order to install them all I ran this:
sudo apt install -t=xenial-proposed linux-signed-generic linux-generic
(which is something that is not told in the previous document)
In its execution an error occurred; here is an
Is there similar verification needed for Xenial?
--
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/1764794
Title:
signing: only install a signed kernel
Status in linux package in Ubuntu:
** Description changed:
MacBook keyboards and other Apple keyboards lack a SysRq key and
therefore lack important kernel functionality that is designed to save
catastrophic data loss if the computer freezes. An equivalent keystroke
should be assigned, for example Fn + Eject, to preserve
Verified unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I can verify the update-notifier 3.168.10
Did not test unattended-upgrades
Did not change the tag since it is the same for unattended-upgrades
unfortunately.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In which versions of the packages the fix is released? Which release of
Ubuntu?
--
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/1757008
Title:
Broadcom wireless drivers failed to build
** Description changed:
- We should switch the default kernle install to the signed kernel. This
+ We should switch the default kernel install to the signed kernel. This
makes it much harder to uninstall the signed kernel in environments
which enforce the kernel to be signed. Boot loaders
I used "dkms status" to get the required information about the module
name (nvidia-340) and version (340.104)
After rebuilding and rebooting at least HDMI works with
4.4.0-116-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
$ dkms list
outputs nothing
--
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/1753050
Title:
Does not recognize external monitor
Status in linux package in Ubuntu:
Confirmed
Bug
As told in the description, with kernel 4.4.0-112-generic the outputs are
recognized and work fine.
The next kernel I installed was 4.4.0-116-generic with which the bug appears.
The bug is not fixed in v4.16-rc4.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Public bug reported:
Neither HDMI (digital) nor VGA (analog) output work with the kernel.
With 4.4.0-112-generic they work fine.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-116-generic 4.4.0-116.140
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname:
Cool, I was not aware of those variables.
--
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/1501884
Title:
linux-image-extra-*-generic postrm script runs install actions
Status in linux
Brian, Where you have uploaded the code? The code at
https://code.launchpad.net/ubuntu/+source/dkms is old.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
Note that the patch in #15 removes the leftovers related to the kernel
version being removed currently. Removing leftovers related to already
purged kernels still have to be done manually, for example by linux-
purge https://www.bountysource.com/issues/38300038-feature-request-the-
According to commant #8
patch against current
https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/update-initramfs
Removes all leftover initramfs files, even after dkms is uninstalled.
** Attachment added: "patch against update-imitramfs"
Oh, I seem to have forgotten to get the possible configurable path to
dpkg in the version 2 of the code. That can be added to it, though I
don't know how much that is required in Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Because the code can be applied in many kernel post-installation
scripts, I have attached it in Bug #1501884 and further updates go
there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is another version for the code. It does not use awk.
** Attachment added: "code to add in probably all post-installation scripts
except initramfs-tools and dkms to exit them before their job in case removing
linux-image-extra (ver. 2)"
Still, it might make more sense to run the scripts in
/etc/kernel/postrm.d and program the exceptions for linux-image-extra
there. For example, check in /etc/kernel/postrm.d/zz-update-grub if we
are removing a linux-image-extra package, and only update grub, if not,
right? And in
I think the problems can be worked around by the attached code by adding
it to post-installation scripts such as apt-auto-removal, unattended-
upgrades, update-notifier, zz-update-grub, but not in initramfs-tools or
dkms.
** Attachment added: "code to add in probably all post-installation scripts
** Attachment added: "code to add in probably all post-installation scripts
except initramfs-tools and dkms to exit them before their job in case removing
linux-image-extra"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4883521/+files/addition2
** Patch removed:
** Patch removed: "code to add before touching /var/run/reboot-required in
post-installation scripts"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4881881/+files/addition
--
You received this bug notification because you are a member of Kernel
Packages, which is
The code could be added to /etc/kernel/postinst.d/zz-update-grub, too,
to avoid unnecessarily updating grub.
--
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/1458204
Title:
removing
An exception for linux-image-extra packages can be added in
/etc/kernel/postinst.d/update-notifier and in /etc/kernel/postinst.d
/unattended-upgrades
Also escape '+' characters, as package name may contain those:
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source
**
An exception for linux-image-extra packages can be added in
/etc/kernel/postinst.d/update-notifier and in /etc/kernel/postinst.d
/unattended-upgrades
** Attachment added: "code to add before touching /var/run/reboot-required in
post-installation scripts"
@Andy, can you give more information about the trigger implementation
you referred to?
--
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/1501884
Title:
linux-image-extra-*-generic postrm
@Andy reboot request notification is triggered by some kernels post-
installation scripts only, so it is related. And as for the second
issue, I have presented different strategy or two in the description of
that bug report.
--
You received this bug notification because you are a member of
Andy, in comment #10 I have mentioned a couple of other side effects of
running post-installation scripts when removing a linux-image-extra
package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
linux-image--generic is present when removing linux-image-
extra--generic. initramfs-tools needs to re-create initrd.img,
at least if linux-image--generic will not be removed. If that
is the only reason, I think it would be better to do the re-creation in
a postrm script than run all postinst
As for the apt-auto-removal problem, it is fixed, right? Bug #1440608
Yet to be fixed at least:
Bug #1458204
Bug #1678187
--
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/1501884
Title:
Steve Langasek, such a bug has been reported (Bug #1501884)
--
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/1458204
Title:
removing kernels should not require a restart afterward
Status
Yes, it is odd. I think the post-installation scripts will be run
because the depending linux-image- package might not get
removed (and is present at the time anyway), thus initramfs-tools is
used to create /boot/initrd.img- without the extra kernel
modules provided by linux-image-extra-. I guess
When removing a linux-image-extra package, kernel post-installation
scripts including /etc/kernel/postinst.d/update-notifier will be run.
That is a symbolic link to /usr/share/update-notifier/notify-reboot-
required, which can be modified to fix this bug.
--
You received this bug notification
** Also affects: update-notifier (Ubuntu)
Importance: Undecided
Status: New
** Also affects: update-notifier
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Why not adding removing to both? That way update-initramfs would remove
the extra ones even if dkms was uninstalled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
Or update-initramfs could do more comprehensive deletion in its delete
function:
rm -f "${initramfs}" "${initramfs}".*
instead of
rm -f "${initramfs}" "${initramfs}.bak"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
Here is the code as a file to retain text formatting.
** Attachment added: "Shell code for removing the backup initrd file for given
kernel"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1515513/+attachment/4852757/+files/remove_initrd_backup
--
You received this bug
The Bourne shell script code to remove the backups could be added in
kernel_prerm.d_dkms (or currently non-existing kernel_postrm.d_dkms) in
dkms package source, but if the package was removed, there would be no
code to remove the backups in conjunction with kernel removing. Thus,
the code could
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
/boot/initrd.img-*.old-dkms files left
By 4.10-rc6 Network Manager tells "Wi-Fi is disabled" even if I check
"Enable Wi-Fi".
** Tags added: bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
By 4.4.0-22 network manager tells "Wi-Fi is disabled" whereas in
4.4.0-51 and later it tells "device not ready". I do not remember, if
this happened after update, but Wi-Fi used to work by the previous
kernels before.
--
You received this bug notification because you are a member of Kernel
S-video works by 4.8 based Yakkety kernel.
--
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/1608236
Title:
Regression: S-video output does not work
Status in linux package in Ubuntu:
I also tried to boot from live USB, both 14.04.1 and 16.04.1 and same thing.
I could not switch wireless on by "Fn + F5" in Linux
https://support.lenovo.com/fi/en/documents/migr-63140
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Public bug reported:
Network manager tells "device not ready". Restarting network manager does not
help.
Wifi failed to work occasionally before, but now it does not work at all.
Hardware may be broken. At least it is as for wired network, I suppose.
ProblemType: Bug
DistroRelease: Ubuntu
Why incomplete?
--
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/1608236
Title:
Regression: S-video output does not work
Status in linux package in Ubuntu:
Incomplete
Status in linux
It works. But colors are gone. Also with 4.4.0-22-generic. Maybe my
hardware is breaking. I also tried to install linux-generic-
hwe-16.04-edge to get newer kernel, but apt failed to fetch the .debs.
--
You received this bug notification because you are a member of Kernel
Packages, which is
The kernel does not resolve the 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/1608236
Title:
Regression: S-video output does not work
Status in linux package in Ubuntu:
In
I get the same kernel (4.4.0.51.54) via , xenial-updates, xenial-
security and xenial-proposed now. The bug is not fixed.
--
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/1608236
Title:
As for #11, it is due to Bug #1274613
--
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/1620648
Title:
[Regression] Pairing bluetooth 0a12:0001 with Bose SoundLink around-
ear II
Yes, it has landed there. Will it land to Xenial soon?
--
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/1608236
Title:
Regression: S-video output does not work
Status in linux package in
I finally was able to make sound work in Xenial.
I did
pactl unload-module module-bluetooth-discover
and
pactl load-module module-bluetooth-discover
on terminal.
Removed and re-added the BOSE device in bluetooth manager. I also had to tweak
bluetooth settings in pavucontrol.
--
You received
I am looking forward to seeing the bug fixed in kernel updates for
Xenial.
--
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/1608236
Title:
Regression: S-video output does not work
Status
In the Trusty machine it helped that I ran
pactl load-module module-bluetooth-discover
--
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/1620648
Title:
[Regression] Pairing bluetooth
4.9-rc2 does not have the 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/1608236
Title:
Regression: S-video output does not work
Status in linux package in Ubuntu:
Confirmed
It does not have the 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/1608236
Title:
Regression: S-video output does not work
Status in linux package in Ubuntu:
Confirmed
Bug
That has the 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/1608236
Title:
Regression: S-video output does not work
Status in linux package in Ubuntu:
Confirmed
Bug
1 - 100 of 184 matches
Mail list logo
