I got some more accessories to try yesterday, turns out the problem is related
to micro usb to usb type-A/tupe-C adapter, only one of the five I tried worked
both in armhf and arm64 images.
With that one, everything looks fine now.
--
You received this bug notification because you are a member
Public bug reported:
[Summary]
USB devices are not working on Raspberry pi zero 2 with arm64 image.
I have tried following devices with adapters:
rpiz2 micro usb -> usb type-c -> usb type-c storage
rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a storage
rpiz2 micro usb -> usb type-c ->
I've installed Evolution 3.44.1-0ubuntu1 from the proposed updates and
text now displays background as expected. This is resolved for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Hi,
Sure, the output is as follows:
gsettings get org.gnome.desktop.interface gtk-theme
'Yaru-blue-dark'
gsettings get org.gnome.desktop.interface color-scheme
'prefer-dark'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Evolution-3.44.0-1ubuntu1 in Jammy proposed fixes the issue.
** Changed in: webkit2gtk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967020
Title:
This is not a bug rather a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Evolution dark background in HTML message (Jammy 22.04)
To manage notifications about this bug
This bug may be related to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1272001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Evolution dark background in HTML message
Attached crash file.
** Attachment added: "_usr_bin_evolution.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+attachment/5581391/+files/_usr_bin_evolution.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Apr 19 16:00:48 ROC-Cube systemd[4105]:
app-gnome-org.inkscape.Inkscape-29481.scope: Consumed 25.374s CPU time.
Apr 19 16:00:51 ROC-Cube kernel: [ 2524.702434] evolution[28125]: segfault at 0
ip 7f6cf7dc4536 sp 7ffc3fc482e8 error 4 in
libwebkit2gtk-4.0.so.37.56.4[7f6cf7872000+2739000]
Actually, a correction. Evolution starts fine but if I go to type an
email (or reply) the editor window is blank. Closing the new or reply
message window THEN crashes Evolution.
** Attachment added: "image832.png"
I'm also having this with Jammy. I am using Wayland with the AMD opensource
GPU drivers.
The following appears in syslog:
Apr 19 15:45:56 ROC-Cube kernel: [ 1629.677203] evolution[23936]: segfault at 0
ip 7fef9c195536 sp 7ffe2be1cf88 error 4 in
One quick question.
On 21.10 the preview rendered with a white background even when using a dark
theme.
Please see the attached.
And thanks for looking at this bug/question. I appreciate it. :)
G.
** Attachment added: "White background previously with 21.10"
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969251
Title:
Evolution dark background in HTML message (Jammy 22.04)
To manage notifications about this bug go to:
Public bug reported:
When using a dark theme in Jammy (22.04) beta, Evolution will display a
dark background with black text for HTML emails in the message preview.
Previously in Impish, the background was white with dark text.
This only occurs when using a dark theme, If you use a light theme,
It was an error on my part, I resolved the issue
Sent from my iPhone
> On Mar 11, 2022, at 1:00 PM, Brian Murray <1964...@bugs.launchpad.net> wrote:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It seems that there was an error on your system when
>
Public bug reported:
I'm unable to download newer version of Python
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion:
Public bug reported:
Don't know
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.32
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
CrashDB:
ubuntu@ubuntu:~$ sudo apt install linux-firmware
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
linux-firmware
1 upgraded, 0 newly installed, 0 to remove and 87 not upgraded.
Need to get 199 MB of
** Tags added: sru
** Description changed:
[Description]
Failed to upgrade linux-firmware on rpi3a+
[Steps to reproduce]
1. Flash following image on rpi3a+:
-
https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz
+
** Description changed:
[Description]
Unable to boot rpi3a+ after apt dist-upgrade
[Steps to reproduce]
1. Flash following image on rpi3a+:
-
Public bug reported:
[Description]
Failed to upgrade linux-firmware on rpi3a+
[Steps to reproduce]
1. Flash following image on rpi3a+:
https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz
2. Boot into system
3. sudo apt update
4. sudo apt
** Summary changed:
- [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
+ [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade
** Description changed:
[Description]
- Unable to boot rpi3+ after apt dist-upgrade
+ Unable to boot rpi3a+ after apt dist-upgrade
[Steps to
** Tags added: sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961186
Title:
[SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade
To manage notifications about this bug go to:
** Package changed: linux-firmware-raspi2 (Ubuntu) => linux-raspi
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961186
Title:
[SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
To
** Summary changed:
- [SRU] Unable to boot rpi3+ after apt dist-upgrade
+ [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961186
Title:
** Summary changed:
- [SRU] Kernel is not upgraded on rpi3+ when running apt dist-upgrade
+ [SRU] Unable to boot rpi3+ after apt dist-upgrade
** Description changed:
[Description]
- Kernel is not upgraded on rpi3a+ when running apt dist-upgrade
+ Unable to boot rpi3+ after apt dist-upgrade
** Attachment added: "dist-upgrade.log"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1961186/+attachment/5561576/+files/dist-upgrade.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Description]
Unable to boot rpi3+ after apt dist-upgrade
[Steps to reproduce]
1. Flash following image on rpi3a+:
** Description changed:
[Description]
Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel
5.11.0-1022.23-raspi
[Steps to reproduce]
1. Flash image (see additional information)
2. Boot into system
3. apt dist-upgrade all packages and reboot
4. Enable
** Tags added: sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950117
Title:
[Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
5.13.0-1010.11-raspi
To manage notifications about
** Tags added: sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950064
Title:
[Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after
upgrade to kernel 5.11.0-1022.23-raspi
To
** Summary changed:
- Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel
5.11.0-1022.23-raspi
+ [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to
kernel 5.11.0-1022.23-raspi
--
You received this bug notification because you are a member of
** Attachment added: "console log from rpi3b"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+attachment/5538767/+files/impish_console_rpi3b.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "console log from cm3+"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+attachment/5538768/+files/impish_console_cm3p.log
** Description changed:
[Description]
Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi.
Fail
** Description changed:
[Description]
Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel
5.11.0-1022.23-raspi
[Steps to reproduce]
1. Flash image (see additional information)
2. Boot into system
3. apt dist-upgrade all packages and reboot
4. Enable
Public bug reported:
[Description]
Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi.
Fail rate: 12 times out of 14 attempts
[Steps to reproduce]
1. Flash image (see additional information)
2. Boot into system
3. apt dist-upgrade all packages and reboot
4. Enable
** Attachment added: "console log from rpi3a+"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538596/+files/console_rpi3ap.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "console log from rpi2"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538595/+files/console_rpi2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "console log from cm3+"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538594/+files/console_cm3p.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "console log from rpi3b+"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538593/+files/console_log.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Description]
Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel
5.11.0-1022.23-raspi
[Steps to reproduce]
1. Flash image (see additional information)
2. Boot into system
3. apt dist-upgrade all packages and reboot
4. Enable proposed repository
5.
Hi Varisht, rpi4b is not supported by this 4.15 kernel, please try
ubuntu 18.04.6 or 20.04 image:
https://ubuntu.com/download/raspberry-pi
** Tags added: sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1887520 ***
https://bugs.launchpad.net/bugs/1887520
Public bug reported:
I get an error at every update of the following form
[[
Setting up console-data (2:1.12-8) ...
Use of uninitialized value $_[1] in join or string at
** Description changed:
[Description]
WLAN device disappear after upgrading linux-firmware-raspi2
Package Version: 1.20200601+arm64-0ubuntu2~18.04.1 [upgradable from:
1.20190215-0ubuntu0.18.04.1]
[Steps to reproduce]
1. Flash image
$ apt-cache policy nextcloud-desktop
nextcloud-desktop:
Installed: 3.1.1-1ubuntu1.1
Candidate: 3.1.1-1ubuntu1.1
Version table:
*** 3.1.1-1ubuntu1.1 500
500 http://gb.archive.ubuntu.com/ubuntu hirsute-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
Public bug reported:
Ubuntu 20 being installed over previous Ubuntu 18 installation.
Dual Boot computer with Windows 10.
Installation works fine until grub install.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic
Public bug reported:
[Description]
Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall server
image.
This only happens on armhf image.
[Steps to reproduce]
1. Flash image
Also happens on 20.04 armhf released image after dist-upgrade everything
with proposed repository enabled.
Image:
ubuntu-20.04.1-preinstalled-server-armhf+raspi.img.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also happens on 20.04 armhf and 20.10 armhf released image after dist-
upgrade everything with proposed repository enabled.
Image:
ubuntu-20.04.1-preinstalled-server-armhf+raspi.img.xz
ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz
--
You received this bug notification because you are a
Public bug reported:
[Description]
WLAN device disappear after upgrading linux-firmware-raspi2
Package Version: 1.20200601+arm64-0ubuntu2~18.04.1 [upgradable from:
1.20190215-0ubuntu0.18.04.1]
[Steps to reproduce]
1. Flash image
** Tags added: cert-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908713
Title:
Fix suspend error of SOF driver
To manage notifications about this bug go to:
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909249
Title:
Wireless device disappear after upgrading to b/4.15.0-1072.76-raspi2
Public bug reported:
Wireless device disappear after upgrading to b/4.15.0-1072.76-raspi2 kernel
This also happens on all current b/4.15.0 kernels after 1072.76.
[Reproduce steps]
1. Flash image ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img.xz
2. Upgrade to latest kernel
3. Reboot
4. Check
Public bug reported:
Bug appeared after upgrading Ubuntu 20 LTS. Version of gThumb is 3.8.0.
Viewing SVG with transparency set used to show as white. Now it shows as
checkerboard. After googling I changed settings in Image Viewer but not
picked up in gThumb. Maybe it needs a restart .. anyway I
Hi,
Sorry for the delay in getting back to you.
As mentioned, adding the absolut path to my auto.DataVol1 file has fixed the
issue for me.
I think it would be preferably to add files to nsswitch.conf rather than
looking for conf entries in /etc/sssd.
For me, the only thing inside /etc/sssd is a
Andreas,
As per comment #25, I've added the absolute path to auto.DataVol1 in
/etc/auto.master as I can confirm it working.
With you comment on having:
automount: sss [NOTFOUND=continue] files
as part of /etc/nsswitch.conf, I suggest that to not break people's existing
configs, that this may be
** Summary changed:
- Wifi device disappear after upgrading linux-firmware-raspi2
+ Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3
preinstalled image
** Summary changed:
- Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3
preinstalled image
+
Public bug reported:
[Impact]
Wifi device disappear after upgrading linux-firmware-raspi2.
Can reproduce on rpi3b, rpi3b+, and rpi3a+.
[Test Case]
1. dd the image in an SD card:
http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz
2. Boot
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Well this explains why this is starting to happen:
https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity-1/+merge/390221
They're adding Active Directory to the new user creation in the
installer.
There's also a design doc that explicitly mentions SSSD:
Same here aas in comment #15. I didn't have SSSD installed prior to the
upgrade and it was "ubuntu-desktop-minimal" that pulled SSSD in. Not
only did it break my automount but also login and sudo would take about
a 4 seconds delay to succeed - as I guess it was trying to auth via SSS.
Grepped
I wouldn't suggest that SSSD has anything done particularly for AutoFS
but I would make a case for the package maintainers having a default
/etc/sssd config file(s) that if nothing else has options
commented/hashed out and ready ti be uncommented and used. This would
be much like how *insert your
Understood.
I guess the last thing I can do here is take the 20.04 VM I've made and
upgrade it to Groovy to see if SSSD is installed as a dependancy of
something else.
I'll do that over the next day or two.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After doing a fresh install of 20.04 in a VM and then installing autofs, I've
concluded that SSSD isn't needed for my setup.
This does leave the question why SSSD was installed and if it was installed
upon upgrade to Groovy.
Either way, it seems that when SSSD is installed (either on 20.04 or
I installed 20.04 fresh in a Gnome Boxes VM and installed autofs (sudo apt-get
install autofs).
SSSD was not installed as a dependancy.
Then, I installed SSSD (sudo apt-get install sssd) just to see what
/etc/sssd looked like and it's actually the same. there's no config file
under /etc/sssd and
Nope, there's no files under /etc/sssd and I didn't touch this directory
when upgrading to the Groovy daily image. When I have a moment, I'll
install 20.04 in a VM for a comparison of what should be in /etc/sssd
But as far as /etc/nsswitch.conf goes:
# /etc/nsswitch.conf
#
# Example
I never looked at SSD closely prior to upgrading from 20.04 to 20.10 so I don't
know what was there before as it 'just worked'.
Presently though, the only thing under /etc/sssd is an empty conf.d
(/etc/sssd/conf.d) directory.
I did reinstall the SSSD packages after upgrade to 20.10 however the
Trying to restart SSSD give the following errors with journlctl -xe:
The job identifier is 11972 and the job result is failed.
Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD Sudo Service
responder socket.
░░ Subject: A start job for unit sssd-sudo.socket has failed
░░ Defined-By:
Public bug reported:
Using the same automount config from 20.04, Groovy Gorilla fails to automount
mount points with SSD errors such as the following:
-From journalctl -xe:
Sep 25 04:04:43 ROC-Cube systemd[1]: Stopping Automounts filesystems on
demand...
░░ Subject: A stop job for unit
Additional points:
* Able to always reproduce
* Able to manually mount volumes (doing so as temp workaround)
dpkg -l sssd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err:
I have not had the same issue with Chromium, but I suspect you might be
right and it's still related. Any thoughts right now on when 450 reaches
official?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, Daniel... I don't know as I run Firefox rather than Chromium.
Let me fire it up and play with it for a day or two and see if I get the
same issue. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Uploading additional grab with my camera showing the corruption on Gnome
Tweaks window where it looks as though a terminal window behind Firefox
(two windows back from this) is showing through.
** Attachment added: "IMG_20200901_095617.jpg"
Just tried my HDStar DVB-S2 USB tuner again on Ubuntu 20.04 with a 5.8.5
kernel. The issue persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326761
Title:
Tevii S471 DVB-S2 card hangs on
Please see attached. As you can see I have the Ubuntu Software tool to
the right, and I have Gnome Tweaks open to the left. You can also see
other apps that are showing normal functioning. Gnome Tweaks
particularly doesn't seem to show corrupted window decorations unless
Ubuntu Software is open.
Public bug reported:
NVidia drivers in Ubuntu 20.04 show corruption in certain applications.
Most egregious bug appears to be "Ubuntu Software Center" which is
almost completely transparent and unusable.
Also see occasional corruption in window decorations in other apps,
namely Gnome Tweaks as a
** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882039
Title:
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882039
Title:
The thread level parallelism would be a bottleneck when
This patch has been merged by libva
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879796
Title:
File descriptor leak in libva2
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because
modification is only in replacing the write lock to a read one. And
there is no modification inside the loop. The regression probability is
low.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Gavin Guo (mimi0213kimo)
Status: New
** Tags: sts
--
You received this bug noti
Public bug reported:
I believe there is a file descriptor leak in libva.
I have attached sample code which simply opens and calls vaInitialize
and vaTerminate in a loop. Running this code will eventually run out of
file descriptors.
I have submitted a pull request here:
Public bug reported:
UC20 stuck at installing system on some Intel NUC systems with nvme.
Tried system with/without secure boot, both can reproduce this issue.
Tried system with/without hardware TPM 2.0, both can reproduce this issue.
Screen capture:
I found there's already a bug for this issue, closing this one:
https://bugs.launchpad.net/argos/+bug/1779115
** Changed in: ubuntu
Status: New => Invalid
** Description changed:
Failed to build knem.ko after upgrading kernel to 4.15.0-100.101~16.04.1.
Didn't see function lost in the
I found there's already a bug for this issue in the project, closing
this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877969
Title:
Failed to build knem.ko on on xenial-hwe 4.15 kernel
To
** Description changed:
- Failed to build tp-smapi dkms after upgrading kernel to
- 4.15.0-100.101~16.04.1-generic.
+ Failed to build tp-smapi dkms after upgrading kernel to
4.15.0-100.101~16.04.1-generic.
+ Didn't see function lost in the test.
+
Test output:
4 modules for
Public bug reported:
Failed to build knem.ko after upgrading kernel to 4.15.0-100.101~16.04.1.
Didn't see function lost in the test.
Test Output:
Found dkms build error messages in /var/log/apt/term.log
=== build log ===
ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is
Public bug reported:
Failed to build tp-smapi dkms after upgrading kernel to
4.15.0-100.101~16.04.1-generic.
Didn't see function lost in the test.
Test output:
4 modules for 4.4.0-179-generic
3 modules for 4.15.0-100-generic
DKMS module number is inconsistent. Some modules may not be built.
Public bug reported:
I can find monitor in display list, but no output from it.
Also, I can't switch to extend mode, it failed to apply the setting and
switched back to mirror mode.
[Steps]
1. Connect a thunderbolt docking station to thunderbolt port.
2. Connect HDMI monitor to HDMI port on the
** Description changed:
I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
profile, but I can't get audio input and output work in HSP/HFP profile.
+ [Reproduce steps]
+ 1. Scan and pair BT headset in Bluetooth setting
+ 2. Switch to HSP/HFP profile in Sound setting
+ 3.
** This bug is no longer a duplicate of bug 1576559
Refused to switch profile to headset_head_unit: Not connected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871794
Title:
[Bluetooth] No
Public bug reported:
I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
profile, but I can't get audio input and output work in HSP/HFP profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
DeepLens:
https://certification.canonical.com/hardware/201801-26078/submission/163784/
DeepRacer:
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865495
Title:
xenial/linux-deeplens: 4.15.0-1019.19
Test result:
https://docs.google.com/spreadsheets/d/1A_nTnwoxzFGpirKbqpQL4bYVBD0ZbDJVicjuZpgVbv4/edit#gid=566033014
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854485
Title:
Introduce the new
Seems no official image will upgrade to this kernel, confirming if this
test should be skipped.
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
Rpi2b-armhf:
https://certification.canonical.com/hardware/201906-27188/submission/163332/
Rpi3b-arm64:
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
Rpi2b-armhf:
https://certification.canonical.com/hardware/201906-27188/submission/162883/
Rpi3b-arm64:
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
rpi2-armhf:
https://certification.canonical.com/hardware/201906-27188/submission/163237/
** Changed in: kernel-sru-workflow/certification-testing
Status: In
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865140
Title:
bionic/linux-hwe-5.0:
1 - 100 of 1405 matches
Mail list logo
