FIX (Maybe?)
I put the keyboard aside for (about) a week. During this time the laptop when
through a usual
'apt update/apt upgrade' process and reboot.
When I tried to subsequently re-pair the keyboard, the 'passcode dialog' stayed
visible,
and the keyboard paired.
Considerations:
- This
Public bug reported:
There is an error in the recording of timezones for some cities.
Cities such as Zhanjiang are located in Guangdong Province, which is in the
East 8 time zone, which is in the Asia/Shanghai time zone.but in the file
timezonemap/src/data/cities15000.txt the city is recorded
I am seeing this bug in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1
Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html
I have managed to have it working in the past, but the 6-digit code pop-
up disappears very quickly (as described,
- This occurs on my daily use laptop which has been upgraded from 23.04
-> 23.10
- I have just tried to pair on another laptop with freshly installed 23.10
- The dialog displaying the pairing code persists
and I can pair correctly with same keyboard (it can pair with 3 separate
devices)
Related to https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2052492
Title:
Pairing: passcode dialogue disappears
Public bug reported:
UPDATE: I am creating this bug in case it comes back again. My Fix was to put
the bluetooth keyboard
aside for a week (not use it), then reconnect after the laptop had been
rebooted after an update
and daily use.
I will post the things that I tried, just in case:
1)
Some things that I have tried which didn't immediately fix the problem.
Resetting the bluez package did NOT fix the problem.
Removing the bluez package(s), removing /var/lib/bluetooth and re-installing.
sudo apt remove --purge bluez
rm -rf /var/lib/bluetooth
sudo apt install bluez
Note: snap now vendors apparmor so reinstalling/removing the system
apparmor package with not affect snapd's use of apparmor.
You can temporarily (for the boot) disable apparmor in the grub command
line by adding apparmor=0 to the kernel parameters.
>From the logs the following adjustments need
Permissions problem wit LightDM?
>>>
mafoelffen@noble-mate-01:~$ sudo systemctl status lightdm --no-pager -l
● lightdm.service - Light Display Manager
Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; preset:
enabled)
Active: active (running) since Mon 2024-02-05 21:24:19
Reinstalling lightdm and trying to start it manually, brings it right to
the same failure point, where it hangs on a black screen. I think there
is a problem with LightDM not displaying on this install.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Attachment added: "_usr_lib_xorg_Xorg.0.crash"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+attachment/5744811/+files/_usr_lib_xorg_Xorg.0.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
If I reinstalled apparmor thorugh apt, then reinstalled snapd-desktop
integration... Then gave it
>>>
startx
>>>
Then the desktop come up.
But it will not boot to the Mate Desktop. Wait one.
Reinstalled lightdm. Still boots to black screen.
If you give it a nomodeset boot parameter, it boots
That was the first boot. Machine was KVM VM: i9-138900K, 4GB RAM 25 GB
vDisk, UEFI, SecureBoot off.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2052489
Title:
Mate
Had to collect report remotely to my workstation:
** Attachment added: "apport.apparmor.2jwsui89.apport"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+attachment/5744810/+files/apport.apparmor.2jwsui89.apport
--
You received this bug notification because you are a member
Public bug reported:
Noble Mate Daily 20230205 ISO
Boots up past Splash to black screen. Last errors in logs are about
apparmor denied on snap desktop integration...
So the graphics layer is being denied because of an apparmor error.
** Affects: apparmor (Ubuntu)
Importance: Undecided
The remaining autopkgtest failures are due to the following unrelated
bugs:
cmake-extras/armhf: bug 2052360
livecd-rootfs/amd64: bug 2045586
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
Please check that this isn't being caused by local extensions. You can
remove them by running:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem persists after that then please
run:
gnome-extensions list --enabled > extensions.txt
and attach the
Public bug reported:
ssh-clent:
uname -a :5.15.0-48-generic #54-Ubuntu
```
Ubuntu 22.04.3 LTS
OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022
```
ssh-server:
```
OracleLinux 8.9
OpenSSH_8.0p1, OpenSSL 1.1.1k FIPS 25 Mar 2021
```
```
userxxx@userxxx-H3C-X7-030s-0274:~$ ssh
** Changed in: pulseaudio (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2025169
Title:
pasdsp LIB dir incorrect
Public bug reported:
When I use Alt+` it will switch to the first application in the list,
rather than between different windows of the same application I am
running.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
I've also encountered this bug in Ubuntu 22.04 LTS. I'd get an error in
/etc/network/if-up.d/resolved unless I change 'return' to 'exit' in the
affected line. After the change I'd no longer encounter an error.
I have /bin/sh symlinked to bash as requirement to build some software.
--
You
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2052297
Title:
Please add opt.keybase.keybase profile
$ git tag --contains 85c975df2c2
v9.1
v9.2
v9.3
v9.4
$ git tag --contains 92cb8427c53
v9.1
v9.2
v9.3
v9.4
$
Ubuntu 23.10 includes coreutils 9.1, 24.04 LTS will include coreutils
9.4. So this bug is fixed in the latest release of Ubuntu.
** Changed in: coreutils (Ubuntu)
Status: Confirmed
** Also affects: ubuntu-translations
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/2052405
Title:
Translation error in
I am closing this bug since the issue appears to be in Oracle Linux and
is being tracked here:
https://github.com/oracle/oracle-linux/issues/125
Thanks!
** Bug watch added: github.com/oracle/oracle-linux/issues #125
https://github.com/oracle/oracle-linux/issues/125
** Changed in: openssh
While the above MP is now merged, I still see additional potential races
in the code. For example, anything calling mount_partition() for the
first partition, and also maybe bug 2030771. I don't see a good way to
solve that w/o `udevadm lock` because these functions don't currently
know what the
Thank you Marc and ibauto. I'll try to investigate/report on the Oracle
Linux 8 side.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2052328
Title:
openssh-client
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I believe this issue is caused by a bad backport in Oracle's
8.0p1-19.el8_9.2 package. I think their fix for CVE-2023-48795 isn't
properly adding kex-strict-s-...@openssh.com to their KEX. Downgrading
the Ubuntu package works around the problem as that prevents the client
from offering
OK, I have managed to locate the Oracle binary packages for
8.0p1-19.el8_9.2 and can confirm the issue. This is curious as the same
packages from RockyLinux appear to work. I will attempt to investigate
the differences.
--
You received this bug notification because you are a member of Ubuntu
This is not fixed. See bug #2052422.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1950828
Title:
ibus-daemon crashed with SIGABRT in g_mutex_clear().
Status in ibus
** Changed in: ibus (Ubuntu)
Assignee: Marcos Casquero (mcasquero) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1950828
Title:
ibus-daemon crashed
The Oracle Linux I'm running is the v8 developer preview, as that is the
only freely downloadable version.
I couldn't reproduce the issue with openssh-server-8.0p1-17.el8.x86_64.
Since I can't get newer packages from Oracle with this version, I
installed openssh, openssh-askpass, openssh-client
We are having the same with OL8 8.9
Openssh used om OL8 = 8.0p1-19.el8_9.2
Ubuntu 18.04, 20.04 and 22.04 who update to are having a problem
We downgraded our versions temporary to
18.04: openssh-server=1:7.6p1-4ubuntu0.7
20.04: openssh-server=1:8.2p1-4
22.04: openssh-server=1:8.9p1-3
--
You
Legion Slim 7 16IRH8 quirk added with this commit:
https://github.com/torvalds/linux/commit/99af5b11c57d33c32d761797f6308b40936c22ed
This is in 6.7.1+.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
(In reply to Jacob Garby from comment #816)
> (In reply to Lukas from comment #814)
> > (In reply to Jacob Garby from comment #813)
> > > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of
> nowhere,
> > > the speaker started working. I have no idea how -- I did not change
> >
That sounds even more like a RAM issue (that it stopped occurring with
the same kernel and software version).
Perhaps when you switched away from Wayland, your graphics card is now
used less heavily, and when the GPU was used more, the RAM got hotter or
got minimally less power and therefore had
*** This bug is a duplicate of bug 1950828 ***
https://bugs.launchpad.net/bugs/1950828
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1950828, so is being marked as such.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
40 matches
Mail list logo
