[Touch-packages] [Bug 1956350] Re: xdg-desktop-portal-gnome missing in Jammy ISO
** Changed in: ubuntu-meta (Ubuntu) Milestone: None => ubuntu-22.04-feature-freeze -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956350 Title: xdg-desktop-portal-gnome missing in Jammy ISO Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Ubuntu Jammy ISO contains xdg-desktop-portal-gtk but xdg-desktop-portal-gnome is missing. xdg-desktop-portal-gnome is needed for GIMP Color picker and Flameshot on Wayland. see https://gitlab.gnome.org/GNOME/gimp/-/issues/1074 apt show xdg-desktop-portal-gnome says: Non-GNOME GTK-based desktop environments should normally use xdg-desktop-portal-gtk or their own portal implementation instead of this one. and Ubuntu 22.04 is a GNOME desktop, so xdg-desktop-portal-gnome should be included in the ISO image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
The gdb autopkgtest test failures listed in comment #24 are actually not regressions as the test result is "neutral" and they quit early due to not having machine-level isolation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Committed Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956637] Re: I have disabled the touchpad through settings, but that has no effect
To try something else I uninstalled touchpad-indicator and not the Settings for the touchpad work as expected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1956637 Title: I have disabled the touchpad through settings, but that has no effect Status in ubuntu-settings package in Ubuntu: New Bug description: I'm running Ubuntu 21.10 on a laptop Ubuntu-settings is V 21.10.4 Disabling the touchpad on my new laptop has no effect. The only way to disable the touchpad was to install Touchpad-indicator ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-settings 21.10.4 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 7 12:05:10 2022 InstallationDate: Installed on 2021-12-31 (6 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1956637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1955347] Re: rsync works bad with encfs now
Hi Christian and thank you for answer.
As you said --ignore-errors could work, but il would be very very
dangerous.
I had tried --exclude=PATTERN (more precisely
--filter "- /home/claude/Documents_chiffres/") and it seemed to work
better because there's not more the "IO error encountered -- skipping
file deletion" error.
rsync did not save the virtual directory corresponding to the encrypted
directory but that's no matter because the user's script does it.
It could be good BUT because of the --delete-excluded option,
rsync deletes the backup of the existing virtual directory
corresponding to the encrypted directory.
I've found a way modifying my backup's script : first it moves the
backup of the virtual directory to a safe place before rsync acts and
after it moves it back to the previous place.
It works but it could be better I think.
Best regards.
Claude MICOUIN
Le lundi 03 janvier 2022 à 14:05 +, Christian Ehrhardt a écrit :
> Hi,
> I'm not 100% sure but to me that is a setup and configuration issue
> with the new version being a bit more insisting that it can
> read/access paths it is supposed to back up.
>
> The new behavior can be disabled with --ignore-errors, but I'm
> tempted
> to consider this dangerous as you could have any other I/O error and
> it
> would still delete things.
>
> Did you try to use --exclude=PATTERN and if that matches your use
> case
> --delete-excluded to make the new version behave as you were used
> from
> the older one?
>
> ** Changed in: rsync (Ubuntu)
>Status: New => Incomplete
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1955347
Title:
rsync works bad with encfs now
Status in rsync package in Ubuntu:
Incomplete
Bug description:
Hello,
I think rsync works bad with encfs now.
When root uses it, rsync cannot read a directory encrypted with encfs
by a user. More precisely, it cannot read the mounted directory, the
virtual one where the user can read the datas.
Until now there was only a warning like this
"rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
Permission denied (13)"
and the software went on working (only ignoring the content of the mounted
directory and of course without saving this content)
But recently there is this more:
"IO error encountered -- skipping file deletion"
and because of this "skipping file deletion", the software can't work
normally. The destination gets bigger more and more because the deleted files
in the source are not deleted in the destination.
Thanks for reading me.
rsync 3.1.3-8ubuntu0.1
Description:Ubuntu 20.04.3 LTS
Release:20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1955347/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)
ubiquity (22.04.3) jammy; urgency=medium
* tests/test_timezone.py:
- update for changes in the new tzdata
-- Sebastien Bacher Tue, 23 Nov 2021 23:37:23
+0100
** Changed in: ubiquity (Ubuntu Jammy)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1951519
Title:
ubiquity 20.04.15.17 fails to build (test_timezone)
Status in tzdata package in Ubuntu:
Invalid
Status in ubiquity package in Ubuntu:
Fix Released
Status in tzdata source package in Focal:
Invalid
Status in ubiquity source package in Focal:
In Progress
Status in tzdata source package in Jammy:
Invalid
Status in ubiquity source package in Jammy:
Fix Released
Bug description:
Description: Ubuntu 20.04.3 LTS
Release: 20.04
When trying to build ubiquity from source,
sudo apt update
sudo apt -y dist-upgrade
sudo apt-get build-dep ubiquity
sudo apt install -y fakeroot
apt source ubiquity
cd ubiquity-*
dpkg-buildpackage -us -uc
[...]
test_has_battery (test_upower.UPowerTests) ... ok
test_check_hostname (test_usersetup.UserSetupTests) ... ok
test_check_username (test_usersetup.UserSetupTests) ... ok
test_default_username (test_usersetup.UserSetupTests) ... ok
test_default_username_strips_invalid_characters
(test_usersetup.UserSetupTests) ... ok
test_hostname_check (test_usersetup.UserSetupTests) ... ok
test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
test_unicode (test_usersetup.UserSetupTests) ... ok
==
FAIL: test_city_entry (test_timezone.TimezoneTests)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in
test_city_entry
self.assertEqual(set(results), set(expected))
AssertionError: Items in the first set but not the second:
('Eastern', 'Bahamas')
Items in the second set but not the first:
('Eastern', 'Canada')
--
Ran 89 tests in 19.319s
FAILED (failures=1)
xauth/Xrdb output:
make: *** [debian/rules:228: tests] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
exit status 2
It keeps failing regardless of release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1951519/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1951454] Re: package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
Hi Niranjana, Thank you for taking the time to file a bug report. > When I connect a headphone and a speaker via bluetooth and > select headphone as the output device, the sound is still > putout from the speaker Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community Thank you, once again. \o/ ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1951454 Title: package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: When I connect a headphone and a speaker via bluetooth and select headphone as the output device, the sound is still putout from the speaker ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: gir1.2-accountsservice-1.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 18 10:16:05 2021 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-01 (566 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 98: Bad configuration option: ServerAliveInterval /etc/ssh/sshd_config: line 99: Bad configuration option: ServerAliveCountMax /etc/ssh/sshd_config: terminating, 2 bad configuration options SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1951454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950473] Re: SSH keygen, Key enrollment failed: requested feature not supported
Hi Hveem,
Thanks for letting us know. I am, therefore, closing this bug. \o/
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
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/1950473
Title:
SSH keygen, Key enrollment failed: requested feature not supported
Status in openssh package in Ubuntu:
Invalid
Bug description:
Bug report:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.10
Release: 21.10
Codename: impish
uname -r
5.13.0-21-generic
Yubikey device: yubikey 5 NFC
ssh -V
OpenSSH_8.4p1 Ubuntu-6ubuntu2, OpenSSL 1.1.1l 24 Aug 2021
Dmesg output:
21.960057] usb 1-3: new full-speed USB device number 4 using xhci_hcd
[ 22.296859] usb 1-3: New USB device found, idVendor=1050, idProduct=0407,
bcdDevice= 5.12
[ 22.296869] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 22.296873] usb 1-3: Product: YubiKey OTP+FIDO+CCID
[ 22.296876] usb 1-3: Manufacturer: Yubico
[ 22.296879] usb 1-3: SerialNumber: 0009031500
[ 22.331164] input: Yubico YubiKey OTP+FIDO+CCID as
/devices/pci:00/:00:01.3/:02:00.0/usb1/1-3/1-3:1.0/0003:1050:0407.0004/input/input19
[ 22.388838] hid-generic 0003:1050:0407.0004: input,hidraw3: USB HID v1.10
Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input0
[ 22.396252] hid-generic 0003:1050:0407.0005: hiddev2,hidraw4: USB HID
v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input1
lsusb -v 2>/dev/null | grep -A2 Yubico | grep "bcdDevice" | awk '{print $2}'
5.12 ( Yubikey firmware )
Tried with the key pin:
ssh-keygen -t ed25519-sk -O resident -vvv
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter PIN for authenticator:
debug3: start_helper: started pid=2678
debug3: ssh_msg_send: type 5
debug3: ssh_msg_recv entering
debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper
debug1: sshsk_enroll: provider "internal", device "(null)", application
"ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin
debug1: sshsk_enroll: using random challenge
debug1: sk_probe: 1 device(s) detected
debug1: sk_probe: selecting sk by touch
debug1: ssh_sk_enroll: using device /dev/hidraw4
debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to
create unprotected resident/verify-required key
debug1: sshsk_enroll: provider "internal" returned failure -2
debug1: ssh-sk-helper: Enrollment failed: requested feature not supported
debug1: ssh-sk-helper: reply len 8
debug3: ssh_msg_send: type 5
debug1: client_converse: helper returned error -59
debug3: reap_helper: pid=2678
Key enrollment failed: requested feature not supported
Tried with touching the key:
$ ssh-keygen -t ed25519-sk -O resident -vvv
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter PIN for authenticator:
debug3: start_helper: started pid=2681
debug3: ssh_msg_send: type 5
debug3: ssh_msg_recv entering
debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper
debug1: sshsk_enroll: provider "internal", device "(null)", application
"ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin
debug1: sshsk_enroll: using random challenge
debug1: sk_probe: 1 device(s) detected
debug1: sk_probe: selecting sk by touch
debug1: ssh_sk_enroll: using device /dev/hidraw4
debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to
create unprotected resident/verify-required key
debug1: sshsk_enroll: provider "internal" returned failure -2
debug1: ssh-sk-helper: Enrollment failed: requested feature not supported
debug1: ssh-sk-helper: reply len 8
debug3: ssh_msg_send: type 5
debug1: client_converse: helper returned error -59
debug3: reap_helper: pid=2681
Key enrollment failed: requested feature not supported
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1950473/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform
The attachment "lp1955997-add-a-whitelist-to-unblock-intel-hid-on-HP- machines.debdiff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
