Public bug reported:
U-Boot and EDK II both support secure boot. But
vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not
signed via sbsign.
Please, adjust the RISC-V build system to sign new kernels.
Best regards
Heinrich
** Affects: linux-riscv (Ubuntu)
Importance:
Public bug reported:
[Impact]
New upstream release. This is a database of wireless regulations, and
should updated in all releases to ensure users have the most up-to-date
regulatory information.
[Test Case]
Following reboot after installing the new database, it should be
possible to query and
@72
opening salvo of " Ignorance doesn't mean knowledge, it is quite the
opposite..."
...nd then completely misreading a simple line of text.
k.
where have I said it's something to do w/ the headerz??? I've only meant
that the whole frigging exercise is to get the modules to work on my
site
Hi people,
unfortunately I can't add information regarding the server systems' problems as
I'm not affected. In fact I only have the few information that came in the
bugzilla thread (https://bugzilla.kernel.org/show_bug.cgi?id=213031) and the
fix patch stayed in kernel for only such a short
Public bug reported:
After installing Ubuntu, the touchpad stopped responding and its not
appearing in the devices list, tried installing and removing xserver-
xorg-input-libinput and xserver-xorg-input-synaptics with no success
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1941974
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1941973
When reporting bugs in the future please use apport by using 'ubuntu-
another QA-test install today on same box.
kubuntu wasn't touched in install, but to validate the new install the
system was booted & logged int to ensure it was untouched...
Logging in today was flawless; backgrounds on both displays & quick
exploration of system (to ensure un-impacted by
** Attachment added: "Syslog taken when the headset initiates the connection"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521416/+files/syslog_HeadsetInitiated
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
This issue was first discovered when I got this headset 2 years back:
https://www.amazon.co.uk/gp/product/B01C2QCPYI.
STEPS
* Enable Bluetooth on the PC
* Have music or some video playing on the PC
* Power on the (already-paired) headset. It automatically connects to the PC.
** Attachment added: "HCI snoop taken when the PC initiates the connection"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521417/+files/PCInitiated.snoop
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "Syslog taken when the PC initiates the connection"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521418/+files/syslog_PCInitiated
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
Public bug reported:
Ubuntu version: 18.04
bcc version:0.16.17
I found several bugs in bcc , would you help me to check if these bugs are
true?thanks for your patience.
==
step 1 :
In
That one's clear enough from the earlier log snippet and source:
Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/profile.c:ext_connect() Headset
Voice gateway connected to FC:58:FA:7F:E5:18
Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:change_state()
0x562f6441d710: device
** Description changed:
Ubuntu version: 18.04
bcc version:0.16.17
+ I found several bugs in bcc , would you help me to check if these bugs are
true?thanks for your patience.
+
+
Public bug reported:
Ubuntu version: 18.04
bcc version:0.16.17
I found a bug in bcc , would you help me to check if this bug is true?thanks
for your patience.
==
step 1 :
In file
** Description changed:
Ubuntu version: 18.04
bcc version:0.16.17
-
+ I found several bugs in bcc , would you help me to check if these bugs are
true?thanks for your patience.
I've spent a while studying the snoop/syslogs and Bluez source, and I
believe I've narrowed down the issue.
* From the Headset-Initiated snoop, we can see where the headset
connected the ACL (23:54:47 UTC), followed shortly by connecting HFP
(successfully).
* Very soon after the headset
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1941972
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
Ubuntu version: 18.04
bcc version:0.16.17
I found several bugs in bcc , would you help me to check if these bugs are
true?thanks for your patience.
step 1 :
In
Public bug reported:
Ubuntu version: 18.04
bcc version:0.16.17
I found several bugs in bcc , would you help me to check if these bugs are
true?thanks for your patience.
=
step 1 :
In file
So why did Bluez initiate A2DP even when the headset was the one that
established the ACL?
The bluetoothd logs help out here:
Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/adapter.c:connected_callback()
hci0 device FC:58:FA:7F:E5:18 connected eir_len 5
Aug 29 00:54:47 RhoPC
I attached snoop/logs where the PC initiated the connection, for
comparison. There, the issue doesn't happen, the headset calmly allows
the PC to establish all the profiles since the PC connected the ACL.
One can also see the difference in flow:
Aug 29 01:57:02 RhoPC bluetoothd[4053589]:
These two error messages display when booting and closing live disk
media using 'safe graphics'
gpio gpiochip: (gpio_aaeon): tried to insert a GPIO chip with zero lines
gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22
they do not seem to upset the processes of the
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1941876
Title:
Touchpad Sometimes Doesn't Work at Boot
Status in
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1941937/+attachment/5521322/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1941937/+attachment/5521324/+files/UdevDb.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/1941937/+attachment/5521325/+files/WifiSyslog.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: "acpidump.txt"
https://bugs.launchpad.net/bugs/1941937/+attachment/5521326/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
29 matches
Mail list logo
