date:20220129

[Touch-packages] [Bug 1959343] Re: deprecation of the Canonical partner archive

2022-01-29 Thread Steve Langasek

I've removed app-install-data-partner, but unfortunately ubuntu-unity-
desktop in the archive still recommends it and I cannot commit to the
master branch for the seeds that this metapackage is built from.  There
was an invitation for ubuntu-core-dev to be added to ~unity7maintainers
but it was never accepted, and having asked the DMB to accept the
invitation now, it seems to have disappeared.  Assigning this to
unity7maintainers for sorting.

** Also affects: ubuntu-unity-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-unity-meta (Ubuntu)
 Assignee: (unassigned) => Unity7 Maintainers Team (unity7maintainers)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1959343

Title:
  deprecation of the Canonical partner archive

Status in subiquity:
  Invalid
Status in app-install-data-partner package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  In Progress
Status in curtin package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-unity-meta package in Ubuntu:
  New

Bug description:
  The Canonical partner archive is no longer being used for publishing
  new packages, and is empty from Ubuntu 20.10 on.  We should stop
  including it in the default sources.list, and clean up references to
  it in our codebase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959343] Re: deprecation of the Canonical partner archive

2022-01-29 Thread Steve Langasek

Removing packages from jammy:
app-install-data-partner 21.10 in jammy
app-install-data-partner 21.10 in jammy amd64
app-install-data-partner 21.10 in jammy arm64
app-install-data-partner 21.10 in jammy armhf
app-install-data-partner 21.10 in jammy i386
app-install-data-partner 21.10 in jammy ppc64el
app-install-data-partner 21.10 in jammy riscv64
app-install-data-partner 21.10 in jammy s390x
Comment: Partner archive is obsolete, package no longer useful; LP: #1959343
1 package successfully removed.


** Changed in: app-install-data-partner (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1959343

Title:
  deprecation of the Canonical partner archive

Status in subiquity:
  Invalid
Status in app-install-data-partner package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  In Progress
Status in curtin package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  The Canonical partner archive is no longer being used for publishing
  new packages, and is empty from Ubuntu 20.10 on.  We should stop
  including it in the default sources.list, and clean up references to
  it in our codebase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

2022-01-29 Thread Matthew D. Mower

I just tested signed Ubuntu kernel 5.13.0-28-generic which is in
Proposed right now, but it does not fix the issue. Brightness
adjustments work, but service fails during startup and screen is at full
brightness every boot (at gdm and at GNOME 3 desktop).

-- 
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/1954843

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 13:29:38 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5095]
  InstallationDate: Installed on 2021-12-12 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XF004WUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1NET44W (1.14)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XF004WUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1NET44W(1.14):bd11/08/2021:br1.14:efr1.14:svnLENOVO:pn20XF004WUS:pvrThinkPadT14sGen2a:rvnLENOVO:rn20XF004WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:

[Touch-packages] [Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

2022-01-29 Thread Matthew D. Mower

I tested some mainline 5.13.x kernels from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and was able to
find a point release where this issue is resolved. Testing results:

Signed Ubuntu kernel 5.13.0-27-generic: brightness adjustments work, but
service fails during startup and screen is at full brightness every boot
(at gdm and at GNOME 3 desktop)

Unsigned mainline kernels:
- 5.13.19 - fixed, service starts successfully automatically
- 5.13.15 - fixed, service starts successfully automatically
- 5.13.12 - fixed, service starts successfully automatically
- 5.13.11 - fixed, service starts successfully automatically
- 5.13.9  - stuck at max brightness, adjustments don't work at all, service 
starts successfully but is ineffective
- 5.13.0  - stuck at max brightness, adjustments don't work at all (forgot to 
check whether service started)

The service I was looking at for status on bootup is: systemd-
backlight@backlight:amdgpu_bl0

-- 
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/1954843

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 13:29:38 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5095]
  InstallationDate: Installed on 2021-12-12 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XF004WUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet spla

[Touch-packages] [Bug 1307109] Re: Alcor Micro AU9540 keeps powering down when card is present

2022-01-29 Thread Ray

I personally couldn't waste anymore time troubleshooting this problem.

Ensure you are using a Smartcard Reader that is compatible with the CCID
(Chip/Smart Card Interface Devices) and ICCD (Integrated Circuit(s) Card
Devices) driver.

Supported CCID readers/ICCD tokens:
https://ccid.apdu.fr/ccid/supported.html

Here are some Smart Card Readers that were intermittently working in Linux:
[ray@ThinkPad ~]$ lsusb
Bus 005 Device 021: ID 0bda:0165 Realtek Semiconductor Corp. Smart Card Reader 
Interface
Bus 003 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader

The Realtek Semiconductor Corp. Smart Card Reader Interface (0bda:0165) is 
actually a Stanley Global SGT111 Smart Card Reader.
The Alcor Micro Corp. AU9540 Smartcard Reader (058f:9540) is a smart card 
reader that I added when I bought my Lenovo ThinkPad T14 (not knowing that it 
had compatibility issues with Linux).

After running pcsc_scan, I could see the both of the above card readers 
fluctuate between:
Card state: Card removed AND Card state: Card inserted. This would cause my 
VMware Horizon Client to randomly disconnect from Desktop Anywhere (very 
annoying).

Here are the Smart Card Readers that I ended up buying on Amazon and
eBay because they are fully supported by the CCID driver:

SCM Microsystems Inc. SCR 3310 USB Smart Card Reader:
https://ccid.apdu.fr/ccid/supported.html#0x04E60x5116

CHERRY SmartTerminal ST-1144: 
https://ccid.apdu.fr/ccid/supported.html#0x046A0x002D
(Features: “One-hand operation“ possible due to heavy weight and stable base.)

[ray@ThinkPad ~]$ lsusb
Bus 005 Device 020: ID 04e6:5116 SCM Microsystems, Inc. SCR331-LC1 / SCR3310 
SmartCard Reader
Bus 005 Device 022: ID 046a:002d Cherry GmbH SmartTerminal XX44

I haven't had any issues with the using the above supported Card
Readers. I use the CHERRY SmartTerminal ST-1144  when I'm at my desk,
and the Identiv SCR3310v2.0 USB Smart Card Reader when I have to travel
for work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1307109

Title:
  Alcor Micro AU9540 keeps powering down when card is present

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  I have smart card reader built-into this laptop, however, whenever I
  insert a card - it'll read it for a few seconds, then the USB
  connection to the reader gets powered down and thus the card
  disappears in the systems eyes.

  After a few seconds, it comes back and everything's happy.

  Then the cycle repeats again and again and again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: 
boot/vmlinuz-3.13.0-23-generic]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpds   3933 F pulseaudio
   /dev/snd/controlC0:  jpds   3933 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr  6 18:37:24 2014
  HibernationDevice: RESUME=UUID=05490d4c-6800-46a1-b5ba-8b32bdc57e89
  InstallationDate: Installed on 2014-04-06 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-23-generic N/A
   linux-backports-modules-3.13.0-23-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L83 Ver. 01.05
  dmi.board.name: 213E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.2A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 1040 G1
  dmi.product.version: A3009DD18303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1307109/+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 1838372] Re: 'ubuntu-bug -w' doesn't work under wayland

2022-01-29 Thread corrado venturini

Try to report on Settings i write 'ubuntu-bug' in terminal and after the 
message ...close
i try to select the settings window but the cros for select does not appear.
closing with cntrl+c i have:
corrado@corrado-n3-jj-0103:~$ ubuntu-bug -w
^CTraceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 597, in 
app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 734, in run_argv
(out, err) = xprop.communicate()
  File "/usr/lib/python3.9/subprocess.py", line 1134, in communicate
stdout, stderr = self._communicate(input, endtime, timeout)
  File "/usr/lib/python3.9/subprocess.py", line 1979, in _communicate
ready = selector.select(timeout)
  File "/usr/lib/python3.9/selectors.py", line 416, in select
fd_event_list = self._selector.poll(timeout)
KeyboardInterrupt

corrado@corrado-n3-jj-0103:~$

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1838372

Title:
  'ubuntu-bug -w' doesn't work under wayland

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  
  'ubuntu-bug -w' doesn't work for most applications such nautilus, gedit, 
settings, etc. under wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1838372/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2022-01-29 Thread Thiago Jung Bauermann

Hello Juerg,

Em quinta-feira, 20 de janeiro de 2022, às 12:32:48 -03, Juerg Haefliger 
escreveu:
> If you want this fixed in Ubuntu I need to know what series are
> affected. Hirsute goes EOL at the end of the month. Are Impish and/or
> Jammy working or affected as well?

I upgraded to Impish a while ago.

I haven’t seen “retry page fault” messages in a long while (I don’t think 
it’s related to the distro upgrade, but not sure) so I’d say this 
particular bug is fixed at least for me (I have a Picasso GPU).

Which is not to say that things are rosy, unfortunately. But the other 
issues I see don’t cause any message to appear in dmesg so it’s hard to 
search for existing bug reports about them or open a new one.

The following is off-topic for this bug report, but I’ll mention anyway, 
hope you’ll bear with me:

One thing I noticed is that things did get rosy when I did two things:

1. Switched from Xorg to Wayland.
2. Switched Firefox to use Wayland as well.

This led me to the conclusion that the bugs that plague my machine are 
triggered by something that Firefox does when it uses X (both “natively” or 
via XWayland). For some reason, when it uses Wayland it doesn’t trigger 
these GPU bugs.

Another thing that might be relevant is that I have tons of tabs open 
(probably more than 200) distributed in 27 open windows. Perhaps I’m 
stressing some kind of resource limit in the driver or firmware?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1928393

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Incomplete

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1928393/+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 1959488] Re: Error loading key ".../id_ed25519.pub": error in libcrypto

2022-01-29 Thread Thomas

curl -s https://launchpadlibrarian.net/582802175/Dependencies.txt | awk
'{print $1}' |  xargs -L1 debsums -lc

Reports also nothing, so all Dependencies are okay.

-- 
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/1959488

Title:
  Error loading key ".../id_ed25519.pub": error in libcrypto

Status in openssh package in Ubuntu:
  New

Bug description:
  I can't add my ED25519 ssh-key to my ssh-agent. I am getting this
  error message:

  user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub
  Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto

  I have setup key agent for KDE like this:

  user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh
  #!/bin/bash

  [ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)"

  user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh
  #!/bin/bash

  [ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass

  user@pcc:~$ cat ~/.config/plasma-workspace/shutdown/ssh-agent-shutdown.sh 
  #!/bin/bash

  [ -z "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -k)"

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-client 1:8.7p1-4
  Uname: Linux 5.15.0-051500-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Jan 29 16:43:55 2022
  InstallationDate: Installed on 2022-01-21 (7 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1959488/+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 1959488] [NEW] Error loading key ".../id_ed25519.pub": error in libcrypto

2022-01-29 Thread Thomas

Public bug reported:

I can't add my ED25519 ssh-key to my ssh-agent. I am getting this error
message:

user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub
Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto

I have setup key agent for KDE like this:

user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh
#!/bin/bash

[ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)"

user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh
#!/bin/bash

[ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass

user@pcc:~$ cat ~/.config/plasma-workspace/shutdown/ssh-agent-shutdown.sh 
#!/bin/bash

[ -z "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -k)"


ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: openssh-client 1:8.7p1-4
Uname: Linux 5.15.0-051500-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sat Jan 29 16:43:55 2022
InstallationDate: Installed on 2022-01-21 (7 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Description changed:

- I cant add my ED25519 ssh key to my ssh-agent. I am getting this error
+ I can't add my ED25519 ssh-key to my ssh-agent. I am getting this error
  message:
  
  user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub
  Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto
  
+ 
  I have setup key agent for KDE like this:
  
- user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh 
+ 
+ user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh
  #!/bin/bash
  
  [ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)"
- user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh 
+ 
+ 
+ user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh
  #!/bin/bash
  
  [ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-client 1:8.7p1-4
  Uname: Linux 5.15.0-051500-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Jan 29 16:43:55 2022
  InstallationDate: Installed on 2022-01-21 (7 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
-  ssh-askpass   N/A
-  libpam-sshN/A
-  keychain  N/A
-  ssh-askpass-gnome N/A
+  ssh-askpass   N/A
+  libpam-sshN/A
+  keychain  N/A
+  ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I can't add my ED25519 ssh-key to my ssh-agent. I am getting this error
  message:
  
  user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub
  Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto
  
- 
  I have setup key agent for KDE like this:
- 
  
  user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh
  #!/bin/bash
  
  [ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)"
  
- 
  user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh
  #!/bin/bash
  
  [ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass
+ 
+ user@pcc:~$ cat ~/.config/plasma-workspace/shutdown/ssh-agent-shutdown.sh 
+ #!/bin/bash
+ 
+ [ -z "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -k)"
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-client 1:8.7p1-4
  Uname: Linux 5.15.0-051500-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Jan 29 16:43:55 2022
  InstallationDate: Installed on 2022-01-21 (7 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
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/1959488

Title:
  Error loading key ".../id_ed25519.pub": error in libcrypto

Status in openssh package in Ubuntu:
  New

Bug description:
  I can't add my ED25519 ssh-key to my ssh-agent. I am getting this
  error message:

  us

[Touch-packages] [Bug 1177132] Re: iptables-save fails silently when run as non-root user

2022-01-29 Thread Oibaf

BTW this is fixed also when using the "legacy" backend:
$ iptables-legacy-save 
Failed to list table names in /proc/net/ip_tables_names: Permission denied

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1177132

Title:
  iptables-save fails silently when run as non-root user

Status in iptables package in Ubuntu:
  Fix Released

Bug description:
  When running iptables-save as a non-root user it produces no output on
  stdout or stderr and exists with success. strace reveals that opening
  /proc/net/ip_tables_names fails with EACCES. This error should be
  written to stderr and the exit code should indicate failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: iptables 1.4.12-1ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
  Uname: Linux 3.2.0-40-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  Date: Tue May  7 00:38:40 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  SourcePackage: iptables
  UpgradeStatus: Upgraded to precise on 2012-05-08 (363 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1177132/+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 1492837] Re: iptables nat prerouting slight problem with adapter aliases

2022-01-29 Thread Oibaf

Is this still an issue with a newer Ubuntu?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1492837

Title:
  iptables nat prerouting slight problem with adapter aliases

Status in iptables package in Ubuntu:
  New

Bug description:
  There seems to be a slight problem with iptables + adapter aliases.

  Take the alias eth0:1 for example...

  ifconfig eth0:1
  eth0:1Link encap:Ethernet  HWaddr 00:25:90:eb:cb:ae  
inet addr:158.69.167.64  Bcast:158.69.255.255  Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

  1) This rule works + seems incorrect (notice -i rather than -i eth0:1)

 iptables -w -t nat -A PREROUTING -i eth0 -p tcp --dst
  158.69.167.64 --dport 80 -j DNAT --to 10.0.3.189 80

  2) This rule fails + seems correct (notice -i eth0:1)

 iptables -w -t nat -A PREROUTING -i eth0:1 -p tcp --dst
  158.69.167.64 --dport 80 -j DNAT --to 10.0.3.189 80

  In #2 the rule is consumed without generating any error.

  Seems like either eth0:1 should be accepted + should work or should
  generate an error.

  The iptables man page says -i is the "Name of an interface via which a
  packet was received" so I'm guessing anytime -i is passed with an
  alias, then the correct action is to either generate an error + die or
  better generate a warning that the alias has been converted to the
  base interface (any :\d+ has been stripped).

  This is a low priority item + at the same time can suck a huge amount
  of time debugging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1492837/+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 1177132] Re: iptables-save fails silently when run as non-root user

2022-01-29 Thread Oibaf

This is fixed, at least in 1.8.7:
$ iptables-save
iptables-save v1.8.7 (nf_tables): Could not fetch rule set generation id: 
Permission denied (you must be root)

** Changed in: iptables (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1177132

Title:
  iptables-save fails silently when run as non-root user

Status in iptables package in Ubuntu:
  Fix Released

Bug description:
  When running iptables-save as a non-root user it produces no output on
  stdout or stderr and exists with success. strace reveals that opening
  /proc/net/ip_tables_names fails with EACCES. This error should be
  written to stderr and the exit code should indicate failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: iptables 1.4.12-1ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
  Uname: Linux 3.2.0-40-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  Date: Tue May  7 00:38:40 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  SourcePackage: iptables
  UpgradeStatus: Upgraded to precise on 2012-05-08 (363 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1177132/+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 1290438] Re: iptables -m state --state UNTRACKED uses SNAT state instead

2022-01-29 Thread Oibaf

Fixed since Ubuntu 14.04.

** Changed in: iptables (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1290438

Title:
  iptables -m state --state UNTRACKED uses SNAT state instead

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables package in Debian:
  Fix Released

Bug description:
  An input rule like -A INPUT -m addrtype -m state --state
  NEW,RELATED,UNTRACKED -j whatever

  creates a rule that actually refers to the SNAT state.

  Chain INPUT (policy ACCEPT)
  [...]
  whatever all  --  anywhere anywhere state 
NEW,RELATED,SNAT

  This was apparently fixed upstream in 1.4.19. I will link the debian
  report (700066) in a moment

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: iptables 1.4.18-1.1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Mar 10 12:24:44 2014
  MarkForUpload: True
  SourcePackage: iptables
  UpgradeStatus: Upgraded to saucy on 2013-11-01 (129 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1290438/+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 1959475] Re: "machinectl shell" connections immediately terminated

2022-01-29 Thread renbag

Sorry, the host was running Ubuntu jammy with systemd 249.9-0ubuntu2.

-- 
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/1959475

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1959475] Re: "machinectl shell" connections immediately terminated

2022-01-29 Thread renbag

>From the last comments in:

https://github.com/systemd/systemd/issues/22234

the problem is due to an incompatibility of the new versions of systemd with 
older ones.
In fact the container was running ubuntu focal, with systemd_245.4-4ubuntu3.15, 
and the host was running ubuntu focal with systemd 249.9-0ubuntu2.
So the problem should be ideally solved by including the patch in:

https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

also in older versions of systemd.

** Bug watch added: github.com/systemd/systemd/issues #22234
   https://github.com/systemd/systemd/issues/22234

-- 
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/1959475

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

2022-01-29 Thread Bug Watch Updater

** Changed in: binutils (Debian)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1958389

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  In Progress
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  Confirmed

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 
ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in 
libc.so.6[7f241f2e2000+194000]
  Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[417179

[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages

2022-01-29 Thread Heinrich Schuchardt

As building GRUB fails on RISC-V too with the new binutils:
Patch created for GRUB and sent upstreams:
[PATCH] riscv: adjust -march flags for binutils 2.38
https://lists.gnu.org/archive/html/grub-devel/2022-01/msg00173.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1959325

Title:
  New binutils causes build failures for many RISC-V packages

Status in binutils package in Ubuntu:
  Confirmed
Status in binutils source package in Jammy:
  Confirmed

Bug description:
  binutils 2.37.90.20220126-0ubuntu1 changes the -march flags.
  We see a lot of packages not building in proposed anymore: OpenSBI, 
ktexteditor, ...

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1959475] Re: "machinectl shell" connections immediately terminated

2022-01-29 Thread renbag

These are the messages reported by journalctl inside the container:

Jan 29 12:27:53 ns-xxx systemd[153]: Assertion 'a' failed at 
src/basic/path-util.c:486, function path_compare(). Aborting.
Jan 29 12:27:53 ns-xxx systemd[1]: container-shell@2.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit container-shell@2.service has successfully entered the 'dead' state.

-- 
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/1959475

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1959475] Re: "machinectl shell" connections immediately terminated

2022-01-29 Thread renbag

Sorry, the patch in:

https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

is already applied in systemd 249.9-0ubuntu2, so that is not the
solution.

-- 
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/1959475

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1952107] Re: Google Contacts API Deprecated

2022-01-29 Thread Alfred Porter

I also upgraded to 3.36.5-0ubuntu2 in focal.  After reloading the
address book and re-authenticating, it returns an HTTP 400 (Bad
Request).  The log file is from the addressbook factory with debugging
of google and carddav backend enabled.

** Attachment added: "evolution-addressbook-factory debug log"
   
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1952107/+attachment/5558170/+files/evolution-google-contacts-log.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1952107

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Fix Committed
Status in evolution-data-server source package in Focal:
  Fix Committed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

2022-01-29 Thread Guy Rouillier

Norbert, thank you for the quick response. I'm very impressed with
apport automatically updating this bug report with requested info!

I will try the FlatPak version when I have some time, since the next LTS
release isn't until April 2022.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1959473

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959473] ProcEnviron.txt

2022-01-29 Thread Guy Rouillier

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1959473/+attachment/5558143/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1959473

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959473] ProcCpuinfoMinimal.txt

2022-01-29 Thread Guy Rouillier

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1959473/+attachment/5558142/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1959473

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

2022-01-29 Thread Guy Rouillier

apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I use
  Evolution for email and calendar.  Tonight I got this message:
  
  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”
  
  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==
  
  I went to report this on the GNOME bug tracker and found this existing
  issue:
  
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655
  
  That issue was closed with this comment:
  ==
  "Andre Klapper
  
  Issue found on latest Evolution in Debian 11 (3.38.3-1)
  
  That version is ancient and not maintained anymore by GNOME developers.
  Feel free to file a bug report in your distribution's issue tracker."
  
  The version in MATE is even older: 3.36.5-0ubuntu1
  
- So apparently Evolution in MATE is currently not functional.  We need to
- update to a later release.  I will update to the newer LTS of MATE when
- it is released.
+ So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2018-10-05 (1212 days ago)
+ InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ Package: evolution-data-server
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
+ Tags: third-party-packages focal
+ Uname: Linux 5.4.0-92-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1959473/+attachment/5558141/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1959473

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

2022-01-29 Thread Norbert

Probably you can try Flatpak version of Evolution from
https://flathub.org/apps/details/org.gnome.Evolution as a workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1959473

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need
  to update to a later release.  I will update to the newer LTS of MATE
  when it is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959475] [NEW] "machinectl shell" connections immediately terminated

2022-01-29 Thread renbag

Public bug reported:

The command "machinectl shell" does not work in systemd 249.9-0ubuntu2:

$ sudo machinectl shell ns-xxx
Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

Connection to machine ns-xxx terminated.

The issue seems to be described here:
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
https://github.com/systemd/systemd/issues/22234

and solved here:

https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1959475

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

2022-01-29 Thread Norbert

Please run

apport-collect 1959473

** Also affects: evolution (Ubuntu)
   Importance: Undecided
   Status: New

** Tags removed: api contacts evolution google
** Tags added: focal

** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #1655
   https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

** Also affects: evolution via
   https://gitlab.gnome.org/GNOME/evolution/-/issues/1655
   Importance: Unknown
   Status: Unknown

** Also affects: evolution-data-server (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1959473

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need
  to update to a later release.  I will update to the newer LTS of MATE
  when it is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959343] Re: deprecation of the Canonical partner archive

[Touch-packages] [Bug 1959343] Re: deprecation of the Canonical partner archive

[Touch-packages] [Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Touch-packages] [Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Touch-packages] [Bug 1307109] Re: Alcor Micro AU9540 keeps powering down when card is present

[Touch-packages] [Bug 1838372] Re: 'ubuntu-bug -w' doesn't work under wayland

Re: [Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Touch-packages] [Bug 1959488] Re: Error loading key ".../id_ed25519.pub": error in libcrypto

[Touch-packages] [Bug 1959488] [NEW] Error loading key ".../id_ed25519.pub": error in libcrypto

[Touch-packages] [Bug 1177132] Re: iptables-save fails silently when run as non-root user

[Touch-packages] [Bug 1492837] Re: iptables nat prerouting slight problem with adapter aliases

[Touch-packages] [Bug 1177132] Re: iptables-save fails silently when run as non-root user

[Touch-packages] [Bug 1290438] Re: iptables -m state --state UNTRACKED uses SNAT state instead

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

[Touch-packages] [Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated

[Touch-packages] [Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

[Touch-packages] [Bug 1959473] ProcEnviron.txt

[Touch-packages] [Bug 1959473] ProcCpuinfoMinimal.txt

[Touch-packages] [Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

[Touch-packages] [Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

[Touch-packages] [Bug 1959475] [NEW] "machinectl shell" connections immediately terminated

[Touch-packages] [Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

27 matches

Site Navigation

Mail list logo

Footer information