[Touch-packages] [Bug 2012957] Re: Xorg freeze

[Daniel van Vugt]

*** This bug is a duplicate of bug 2007668 ***
https://bugs.launchpad.net/bugs/2007668

This sounds like one of the symptoms of bug 2007668.

I can confirm that Ubuntu 23.04 works more reliably on 12th gen chips,
but that's not officially released yet.

You might also have more luck by installing Ubuntu 22.04 and then
upgrading the kernel like:

  sudo apt install linux-oem-22.04c

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** This bug has been marked a duplicate of bug 2007668
   Intel 12th gen: Noisy screen corruption during cursor movement, and whole 
screen freezes, in 5.19 kernels

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  New

Bug description:
  I'm not sure if this is an xorg bug because i'm pretty sure I'm using
  wayland, however ubuntu-bug says it's an xorg issue.

  I installed the GNOME desktop instead of the ubuntu one, however it
  does happen on the ubuntu desktop as well. It seems to happen less
  often on the GNOME desktop (though still multiple times a day)

  
  When I perform certain actions I can semi-reliably produce a total screen 
freeze. Some examples include using the search menu on gnome, opening a video 
in fullscreen, and clicking buttons in fractal (matrix client.) There are many 
more scenarios that I haven't listed. The screen will completely freeze but the 
computer will keep going normally (e.g. I can type, use the cursor, listen to 
audio, etc.) This can be remedied by pressing CONTROL+ALT+F3 which brings me 
into the console, then waiting about 5 seconds, then switching back with 
CONTROL+ALT+F2

  This doesn't seem to be related to any computer load issues and occurs
  reliably after clicking on something/typing in a text field until the
  offending program is restarted. When the program is restarted, the
  issue sometimes goes away but sometimes persists. This has been
  happening since I installed ubuntu a couple weeks ago.

  I am able to provide more details if necessary and do some debugging
  things, but I'm not a technical user so will need babying.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar 27 12:47:02 2023
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Matsushita Electric Industrial Co., Ltd. Alder Lake-P 
Integrated Graphics Controller [10f7:8338]
  InstallationDate: Installed on 2023-03-15 (12 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Panasonic Connect Co., Ltd. CFFV3-1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=f8060648-d61e-4101-984c-4f5a1ff087f8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2022
  dmi.bios.release: 1.0
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: V1.00L15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CFFV3-1L
  dmi.board.vendor: Panasonic Connect Co., Ltd.
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Connect Co., Ltd.
  dmi.chassis.version: 001
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrV1.00L15:bd05/09/2022:br1.0:efr1.0:svnPanasonicConnectCo.,Ltd.:pnCFFV3-1:pvr001:rvnPanasonicConnectCo.,Ltd.:rnCFFV3-1L:rvr1:cvnPanasonicConnectCo.,Ltd.:ct10:cvr001:skuCF-FV3DFNCR:
  dmi.product.family: Let'snote/TOUGHBOOK
  dmi.product.name: CFFV3-1
  dmi.product.sku: CF-FV3DFNCR
  dmi.product.version: 001
  dmi.sys.vendor: Panasonic Connect Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-v

[Touch-packages] [Bug 1595238] Re: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/gl

[Daniel van Vugt]

*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593

** This bug is no longer a duplicate of bug 1553328
   Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() 
especially with multiple monitors, webbrowser-app or system settings
** This bug has been marked a duplicate of bug 1497593
   [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion 
`kref' failed.

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

Title:
  Unity 8 Desktop Preview System Settings do not work on nouveau
  [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file
  ../../../src/ubuntumirclient/glcontext.cpp, line 239]

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When I try to open System Settings, the Ubuntu logo keeps turning and nothing 
happens.
  I installed unity8-desktop-session-mir on my Xenial 16.04.1 Desktop where I 
use NVIDIA driver GF108[GeForce GT 530]. I also created a new user account with 
English (US) language settings, because Unity 8 does not work well when I use 
my own account with my language settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595238/+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 1623507] Re: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear().

[Daniel van Vugt]

*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593

** This bug is no longer a duplicate of bug 1553328
   Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() 
especially with multiple monitors, webbrowser-app or system settings
** This bug has been marked a duplicate of bug 1497593
   [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion 
`kref' failed.

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

Title:
  unity-system-compositor crashed with "Failed to schedule page flip",
  but only after nouveau crashed in glClear().

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  16.10 first unity 8 run

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Sep 14 10:34:45 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller [1462:7817]
   NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988]
  InstallationDate: Installed on 2016-09-14 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 7
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.70-1
  version.lightdm: lightdm 1.19.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

[Daniel van Vugt]

*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593

** This bug has been marked a duplicate of bug 1497593
   [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion 
`kref' failed.

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

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Triaged
Status in Mesa:
  New
Status in Mir:
  Triaged
Status in Nouveau Xorg driver:
  Unknown
Status in Unity System Compositor:
  Triaged
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1623508] Re: unity8 crashed with SIGSEGV

[Daniel van Vugt]

*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593

** This bug is no longer a duplicate of bug 1553328
   Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() 
especially with multiple monitors, webbrowser-app or system settings
** This bug has been marked a duplicate of bug 1497593
   [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion 
`kref' failed.

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

Title:
  unity8 crashed with SIGSEGV

Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  16.10 first unity 8 run16.10 first unity 8 run

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Sep 14 10:32:07 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-09-14 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913)
  ProcCmdline: unity8 --mode=full-shell
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1623508/+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 1631627] Re: Unity 8 freezes on Nouveau

[Daniel van Vugt]

*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593

** This bug is no longer a duplicate of bug 1553328
   Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() 
especially with multiple monitors, webbrowser-app or system settings
** This bug has been marked a duplicate of bug 1497593
   [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion 
`kref' failed.

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

Title:
  Unity 8 freezes on Nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes
  after I do some clicking around the desktop (using Browser, System
  Settings and the like), I am running it on Nouveau driver for GTX970M,
  I refrained from installing proprietary drivers to test Unity 8, but
  it is unusable and after it freezes I can only power off my laptop as
  nothing works. Is this a known issue? Also Unity 7 does not load at
  all, but I will post a separate bug for that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1631627/+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 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)

[Daniel van Vugt]

"Fix Released" in lunar, assuming it is the above issue. If it's not
then please just change the status back.

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504
   Importance: Unknown
   Status: Unknown

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

** No longer affects: linux (Ubuntu)

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

Title:
  Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page
  fault)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  My desktop unexpectedly freezes or crashes every now and then (once or
  week or less). Typically the machine is not usable but this time I
  managed to log back in via the text console and grab the following
  text from dmesg:

  [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed
  [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245291] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a01000 from client 0x1b (UTCL2)
  [11689.245294] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245296] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245298] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245299] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245301] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245302] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245304] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245311] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0c000 from client 0x1b (UTCL2)
  [11689.245313] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245315] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245316] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245318] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245319] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245320] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245322] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245329] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0b000 from client 0x1b (UTCL2)
  [11689.245331] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245333] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245334] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245336] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245337] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245339] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245340] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245347] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a06000 from client 0x1b (UTCL2)
  [11689.245349] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245350] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245351] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245352] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245354] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245355] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245356] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245362] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0a000 from client 0x1b (UTCL2)
  [11689.245363] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245364] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245366] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245367] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245368] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245369] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245370] amdgpu :09:00.0:

[Touch-packages] [Bug 1672793] Re: unity-system-compositor crashed with SIGSEGV

[Daniel van Vugt]

*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593

** This bug is no longer a duplicate of bug 1553328
   Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() 
especially with multiple monitors, webbrowser-app or system settings
** This bug has been marked a duplicate of bug 1497593
   [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion 
`kref' failed.

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

Title:
  unity-system-compositor crashed with SIGSEGV

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I just got this on the first login to my new Ubuntu user profile

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity-system-compositor 0.9.1+17.04.20170216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 14 20:14:24 2017
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2013-09-15 (1275 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 13 --to-dm-fd 22 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f8dc76dd07f:mov0x8(%r15),%edx
   PC (0x7f8dc76dd07f) ok
   source "0x8(%r15)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: unity-system-compositor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.75-1ubuntu1
  version.lightdm: lightdm 1.21.5-0ubuntu1
  version.mesa: libegl1-mesa-dev 13.0.4-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1672793/+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 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)

[Daniel van Vugt]

Looks most likely to be
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 which is fixed in
Mesa 22.3.1. But then similar bugs still exist like bug 2012819.

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7504
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504

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

Title:
  Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page
  fault)

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  My desktop unexpectedly freezes or crashes every now and then (once or
  week or less). Typically the machine is not usable but this time I
  managed to log back in via the text console and grab the following
  text from dmesg:

  [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed
  [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245291] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a01000 from client 0x1b (UTCL2)
  [11689.245294] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245296] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245298] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245299] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245301] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245302] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245304] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245311] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0c000 from client 0x1b (UTCL2)
  [11689.245313] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245315] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245316] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245318] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245319] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245320] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245322] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245329] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0b000 from client 0x1b (UTCL2)
  [11689.245331] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245333] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245334] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245336] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245337] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245339] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245340] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245347] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a06000 from client 0x1b (UTCL2)
  [11689.245349] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245350] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245351] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245352] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245354] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245355] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245356] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245362] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0a000 from client 0x1b (UTCL2)
  [11689.245363] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245364] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245366] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245367] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245368] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245369] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245370] amdgpu :09:00.0: amdgpu

[Touch-packages] [Bug 2008897] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2008897

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page
  fault)

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  My desktop unexpectedly freezes or crashes every now and then (once or
  week or less). Typically the machine is not usable but this time I
  managed to log back in via the text console and grab the following
  text from dmesg:

  [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed
  [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245291] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a01000 from client 0x1b (UTCL2)
  [11689.245294] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245296] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245298] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245299] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245301] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245302] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245304] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245311] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0c000 from client 0x1b (UTCL2)
  [11689.245313] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245315] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245316] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245318] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245319] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245320] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245322] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245329] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0b000 from client 0x1b (UTCL2)
  [11689.245331] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245333] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245334] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245336] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245337] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245339] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245340] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245347] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a06000 from client 0x1b (UTCL2)
  [11689.245349] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245350] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245351] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245352] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245354] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245355] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245356] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245362] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0a000 from client 0x1b (UTCL2)
  [11689.245363] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245364] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245366] amdgpu :09:00.0: amdgpu

[Touch-packages] [Bug 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)

[Daniel van Vugt]

** Summary changed:

- Desktop freezes or crashes intermittently
+ Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)

** Package changed: kwin (Ubuntu) => linux (Ubuntu)

** Tags added: amdgpu

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

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

Title:
  Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page
  fault)

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  My desktop unexpectedly freezes or crashes every now and then (once or
  week or less). Typically the machine is not usable but this time I
  managed to log back in via the text console and grab the following
  text from dmesg:

  [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed
  [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245291] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a01000 from client 0x1b (UTCL2)
  [11689.245294] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245296] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245298] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245299] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245301] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245302] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245304] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245311] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0c000 from client 0x1b (UTCL2)
  [11689.245313] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
  [11689.245315] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [11689.245316] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x1
  [11689.245318] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245319] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [11689.245320] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245322] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245329] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0b000 from client 0x1b (UTCL2)
  [11689.245331] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245333] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245334] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245336] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245337] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245339] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245340] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245347] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a06000 from client 0x1b (UTCL2)
  [11689.245349] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245350] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245351] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245352] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245354] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245355] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245356] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 
ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 
pid 1369)
  [11689.245362] amdgpu :09:00.0: amdgpu:   in page starting at address 
0x800598a0a000 from client 0x1b (UTCL2)
  [11689.245363] amdgpu :09:00.0: amdgpu: 
GCVM_L2_PROTECTION_FAULT_STATUS:0x
  [11689.245364] amdgpu :09:00.0: amdgpu:  Faulty UTCL2 client ID: 
CB/DB (0x0)
  [11689.245366] amdgpu :09:00.0: amdgpu:  MORE_FAULTS: 0x0
  [11689.245367] amdgpu :09:00.0: amdgpu:  WALKER_ERROR: 0x0
  [11689.245368] amdgpu :09:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [11689.245369] amdgpu :09:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [11689.245370] amdgpu :09:00.0: amdgpu:  RW: 0x0
  [11689.245374] a

[Touch-packages] [Bug 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

[Daniel van Vugt]

** Tags added: fixed-in-accountsservice-23.12ish fixed-upstream

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [accountsservice]

Status in accountsservice:
  New
Status in gnome-control-center:
  Unknown
Status in accountsservice package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is now the #1 gnome-shell crasher in Ubuntu 23.04.

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: comple

[Touch-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[AceLan Kao]

The BT adv feature
1. works with 5.15 + bluez (20/stable) 5.53-7
2. doesn't work with 5.15 + bluez (22/beta) 5.64-3
3. (from Dilyn and Wendell) works with 5.19 + bluez (22/beta)

It's still unclear why bluez requires specific version of kernel.
Do we have a bluez expert to consult what kind of features the 5.15 kernel are 
missing?
Or could our customer stick with bluez (20/stable)?

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

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2012992] [NEW] kernel-5.19.0-38 battery charge fails

[John Thompson]

Public bug reported:

I just installed linux-image-5.19.0-38 on my HP ProBook 640 G2 with
Ubuntu-22.0.4LTS and my battery no longer charges. Battery reports 77%
charge, but "pending charge." Leaving it connected to charger give no
change in charge status. Booting to Windows-10 shows charge at 77%,
status charging, and charge report increasing as expected. Reverting to
kernel-5.15.0-69 shows 76% charge, status "charging."

john@stolat:~$ upower -i /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   Hewlett-Packard
  model:Primary
  serial:   36600 2017/12/20
  power supply: yes
  updated:  Mon 27 Mar 2023 08:18:01 PM CDT (114 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
warning-level:   none
energy:  31.1106 Wh
energy-empty:0 Wh
energy-full: 40.5954 Wh
energy-full-design:  48.0168 Wh
energy-rate: 0 W
voltage: 12.15 V
charge-cycles:   57
percentage:  76%
capacity:84.5442%
technology:  lithium-ion
icon-name:  'battery-full-charging-symbolic'

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  kernel-5.19.0-38 battery charge fails

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I just installed linux-image-5.19.0-38 on my HP ProBook 640 G2 with
  Ubuntu-22.0.4LTS and my battery no longer charges. Battery reports 77%
  charge, but "pending charge." Leaving it connected to charger give no
  change in charge status. Booting to Windows-10 shows charge at 77%,
  status charging, and charge report increasing as expected. Reverting
  to kernel-5.15.0-69 shows 76% charge, status "charging."

  john@stolat:~$ upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Hewlett-Packard
model:Primary
serial:   36600 2017/12/20
power supply: yes
updated:  Mon 27 Mar 2023 08:18:01 PM CDT (114 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   charging
  warning-level:   none
  energy:  31.1106 Wh
  energy-empty:0 Wh
  energy-full: 40.5954 Wh
  energy-full-design:  48.0168 Wh
  energy-rate: 0 W
  voltage: 12.15 V
  charge-cycles:   57
  percentage:  76%
  capacity:84.5442%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2012992/+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 2004039] Update Released

[Brian Murray]

The verification of the Stable Release Update for libunwind has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with
  bigger page sizes

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * On kernels with page size > 4K Xorg (and presumably other applications
     relying on libunwind) crashes on startup. This affects anyone
     running the official arm64 generic-64k kernel or custom non 4k kernels
     (as used by e.g. apple silicon).

 The exact error I am seeing in the logs is:

  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 0: 
/usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaab456ca998]
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 
unw_get_proc_info failed: no unwind info found [-10]
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Segmentation 
fault at address 0x0
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Fatal server error:
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Please consult the 
The X.Org Foundation support
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]:  at 
http://wiki.x.org
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]:  for help.
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)

I have not found a workaround other than using wayland (which has other
limitations). To reproduce use a kernel configured with a page size of
16K (CONFIG_ARM64_16K_PAGES=y or CONFIG_ARM64_64K_PAGES=y or) and try
to start "Ubuntu on Xorg" in gdm.

  [ Test Plan ]

   * Make sure Xorg doesn't crash on 4K, 16K and 64K kernels.

  [ Where problems could occur ]

   * We will have to make sure the fixed version still works with 4k
     kernels. The patch is already widely in use so the risk seems low if
     we test properly.

  [ Other Info ]

   * The lunar version ships the bug fix synced from debian

   * Debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1026217

   * Upstream fix:
  
https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

[Launchpad Bug Tracker]

This bug was fixed in the package libunwind - 1.6.2-0ubuntu1.1

---
libunwind (1.6.2-0ubuntu1.1) kinetic; urgency=medium

  * Backport debian bug fix for dynamic page size (LP: #2004039)
- Add upstream change to determine the page size dynamically,
  thanks to Thomas Glanzmann. (Closes: #1026217)

 -- Tobias Heider   Mon, 30 Jan 2023
11:30:11 +0100

** Changed in: libunwind (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with
  bigger page sizes

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * On kernels with page size > 4K Xorg (and presumably other applications
     relying on libunwind) crashes on startup. This affects anyone
     running the official arm64 generic-64k kernel or custom non 4k kernels
     (as used by e.g. apple silicon).

 The exact error I am seeing in the logs is:

  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 0: 
/usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaab456ca998]
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 
unw_get_proc_info failed: no unwind info found [-10]
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Segmentation 
fault at address 0x0
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Fatal server error:
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Please consult the 
The X.Org Foundation support
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]:  at 
http://wiki.x.org
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]:  for help.
  Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE)

I have not found a workaround other than using wayland (which has other
limitations). To reproduce use a kernel configured with a page size of
16K (CONFIG_ARM64_16K_PAGES=y or CONFIG_ARM64_64K_PAGES=y or) and try
to start "Ubuntu on Xorg" in gdm.

  [ Test Plan ]

   * Make sure Xorg doesn't crash on 4K, 16K and 64K kernels.

  [ Where problems could occur ]

   * We will have to make sure the fixed version still works with 4k
     kernels. The patch is already widely in use so the risk seems low if
     we test properly.

  [ Other Info ]

   * The lunar version ships the bug fix synced from debian

   * Debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1026217

   * Upstream fix:
  
https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2012599] Autopkgtest regression report (tzdata/2023b-0ubuntu0.22.10.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2023b-0ubuntu0.22.10.0) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2008952] Re: DNS failure while trying to fetch user-data

[Chad Smith]

jsonschema 2.6.0 is now dropped from latest ubuntu-desktop-snap version
0+get.98600e08 in stable channel as of a couple hours ago per this
issue/fix[1]. This resolves issues with curtin Tracebacks on
jsonschema.validate(). Additionally cloud-init has a PR in progress[2]
to avoid registering a strict draft4 schema with
additionalProperties=False. The cloud-init fix is now unnecessary given
the changes already published in ubuntu-desktop-installer to drop
jsonschema 2.6.0 from the snap.


[1] drop duplicate python dependencies from site-packages
https://github.com/canonical/ubuntu-desktop-installer/issues/1714

[2] https://github.com/canonical/cloud-init/pull/2098


** Bug watch added: github.com/canonical/ubuntu-desktop-installer/issues #1714
   https://github.com/canonical/ubuntu-desktop-installer/issues/1714

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

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  In Progress
Status in netplan:
  Invalid
Status in subiquity:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2012980] [NEW] package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Drew Howden]

Public bug reported:

This happened when I upgraded the kernel with "sudo apt upgrade".

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-69-generic 5.15.0-69.76
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  drew   1508 F pulseaudio
CasperMD5CheckResult: unknown
Date: Mon Mar 27 16:28:39 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-12-22 (460 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: LENOVO 80XS
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2019
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: 5QCN24WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15ABR
dmi.ec.firmware.release: 1.24
dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN24WW:bd07/29/2019:br1.24:efr1.24:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR:
dmi.product.family: ideapad 320-15ABR
dmi.product.name: 80XS
dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR
dmi.product.version: Lenovo ideapad 320-15ABR
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This happened when I upgraded the kernel with "sudo apt upgrade".

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-69-generic 5.15.0-69.76
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  drew   1508 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Mon Mar 27 16:28:39 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-12-22 (460 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 80XS
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-69-generic 5.15.0-69.76 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN24WW:bd07/29/2019:br1.24:efr1.24:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.sku

[Touch-packages] [Bug 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

[Sebastien Bacher]

** Changed in: accountsservice (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [accountsservice]

Status in accountsservice:
  New
Status in gnome-control-center:
  Unknown
Status in accountsservice package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is now the #1 gnome-shell crasher in Ubuntu 23.04.

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0

[Touch-packages] [Bug 2012943] Re: Systemd-resolved is crashing

[Nick Rosbrook]

I have prepared the fix for this in git because I have more context from
other discussions, but can you please add a bit more detail here? E.g.
at least provide the stack trace you have observed which suggests the
above patch is correct?

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

Title:
  Systemd-resolved is crashing

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system.

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  [ Where problems could occur ]

  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
  This commit is resolving the issue which is observed.

  Please refer to the above commit to assess the risk involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2012943] Re: Systemd-resolved is crashing

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/439761

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

Title:
  Systemd-resolved is crashing

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system.

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  [ Where problems could occur ]

  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
  This commit is resolving the issue which is observed.

  Please refer to the above commit to assess the risk involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2006940] Re: PIN validation affects interface even if the manual token button is selected

[Nathan Teodosio]

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  PIN validation affects interface even if the manual token button is
  selected

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  1. software-properties-gtk 
  2. Go to Ubuntu Pro 
  3. Go to Enable Ubuntu Pro 
  4. Press "Or add token manually button" radio
  5. Go to ubuntu.com/pro/attach and submit the PIN

  Expected: Nothing happens until the user clicks "Enter code..." radio.

  Observed: UI is locked with "Valid token" message next to the manual
  token field, which won't allow to attach the token received from PIN
  validation.

  Similar issue happens when PIN expires instead of being validated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2006940/+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 2012969] Re: apport-gtk crashed with signal 5 in g_log_writer_default()

[Apport retracing service]

*** This bug is a duplicate of bug 2006981 ***
https://bugs.launchpad.net/bugs/2006981

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2006981, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2012969/+attachment/5657973/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2012969/+attachment/5657976/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2012969/+attachment/5657979/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2012969/+attachment/5657980/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2012969/+attachment/5657981/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2012969/+attachment/5657982/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2012969/+attachment/5657983/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 2006981

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with signal 5 in g_log_writer_default()

Status in apport package in Ubuntu:
  New

Bug description:
  Had just booted ubuntu daily build (previously updated with today's changes) 
in QEMU/KVM, and then logged on.
  I was twidling the VM View menu (i.e.) not doing anything specific with the 
client system when the error occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apport-gtk 2.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 14:57:48 2023
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2023-03-23 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230323)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  Signal: 5
  SourcePackage: apport
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: apport-gtk crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2012969/+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 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes

[Nick Rosbrook]

I have re-confirmed the fix using systemd 251.4-1ubuntu7.3 from kinetic-
proposed:

root@kinetic:~# apt-cache policy systemd
systemd:
  Installed: 251.4-1ubuntu7.3
  Candidate: 251.4-1ubuntu7.3
  Version table:
 *** 251.4-1ubuntu7.3 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 251.4-1ubuntu7.1 500
500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu kinetic-security/main amd64 
Packages
 251.4-1ubuntu7 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
root@kinetic:~# ip link add veth0 up type veth peer name veth1
root@kinetic:~# ip addr add 172.20.0.1/24 dev veth0
root@kinetic:~# cat > /etc/netplan/60-veth1.yaml  /etc/netplan/60-veth1.yaml 

[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes

[Nick Rosbrook]

I have re-confirmed the fix using systemd 249.11-0ubuntu3.9 from jammy-
proposed:

root@jammy:~# apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.9
  Candidate: 249.11-0ubuntu3.9
  Version table:
 *** 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@jammy:~# ip link add veth0 up type veth peer name veth1
root@jammy:~# ip addr add 172.20.0.1/24 dev veth0
root@jammy:~# cat > /etc/netplan/60-veth1.yaml  /etc/netplan/60-veth1.yaml 

[Touch-packages] [Bug 2000880] Re: systemd-networkd: ActivationPolicy ignored in VLANs

[Nick Rosbrook]

I re-confirmed the fix using systemd 249.11-0ubuntu3.9 from jammy-
proposed:

$ apt-cache policy systemd
systemd:
  Installed: 249.11-0ubuntu3.9
  Candidate: 249.11-0ubuntu3.9
  Version table:
 *** 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ cat /etc/systemd/network/10-vlan18.netdev 
[NetDev]
Name=vlan18
Kind=vlan

[VLAN]
Id=18
$ cat /etc/systemd/network/20-vlan18.network 
[Match]
Name=vlan18

[Network]
Address=10.10.1.1/24

[Link]
ActivationPolicy=manual
$ cat /etc/systemd/network/30-ens3.network 
[Match]
Name=ens3

[Network]
DHCP=ipv4
$ ip a show vlan18
3: vlan18@ens3:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
link/ether 52:54:00:c6:8b:40 brd ff:ff:ff:ff:ff:ff


** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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

Title:
  systemd-networkd: ActivationPolicy ignored in VLANs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  The ActivationPolicy property in .network files is ignored for VLANs.

  [Test Plan]

  * On a Jammy machine with an interface named ens3, create the
  following configs:

  $ cat > /etc/systemd/network/10-vlan18.netdev << EOF
  [NetDev]
  Name=vlan18
  Kind=vlan

  [VLAN]
  Id=18
  EOF

  $ cat > /etc/systemd/network/20-vlan18.network << EOF
  [Match]
  Name=vlan18

  [Network]
  Address=10.10.1.1/24

  [Link]
  ActivationPolicy=manual
  EOF

  $ cat > /etc/systemd/network/30-ens3.network << EOF
  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  VLAN=vlan18
  EOF

  * Reboot the machine
  * On an affected machine, the vlan18@ens3 interface will have a configured IP 
at boot, despite the ActivationPolicy=manual setting in 
/etc/systemd/network/20-vlan18.network. On a patched machine, the interface 
should not have a configured IP.

  [Where problems could occur]

  The patch adds a condition where a netdev is not yet ready to be
  created. Specifically, it makes sure stacked netdevs are not created
  before their underlying link is activated. If we saw any problems, it
  would be related to netdev creation.

  [Original Description]

  This has been fixed upstream, see

  Upstream bug: https://github.com/systemd/systemd/issues/22593

  Any chance of a backport of the fix to 22.04?

  Fix: https://github.com/systemd/systemd-stable/pull/211

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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 2002445] Re: udev NIC renaming race with mlx5_core driver

[Nick Rosbrook]

** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit).

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import json
  import logging
  import os
  import sys
  from enum import Enum

  import pycloudlib

  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba]
  """

  #source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # - apt install systemd udev -y --allow-unauthenticated

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: {source}
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  class BootCondition(Enum):
  SUCCESS_WITHOUT_RENAME_RACE = "network bringup success without rename 
race"
  SUCCESS_WITH_RENAME_RACE = "network bringup success rename race condition"
  ERROR_NETWORK_TIMEOUT = "error: timeout on systemd-networkd-wait-online"

  
  def batch_launch_vm(
  client, instance_type, image_id, user_data, instance_count=5
  ):
  instances = []
  while len(instances) < instance_count:
  instances.append(
  client.launch(
  image_id=image_id,
  instance_type=instance_type,
  user_data=user_data,
  )
  )
  return instances

  
  def get_boot_condition(test_idx, instance):
  blame = instance.execute("systemd-analyze blame").splitlines()
  try:
  LOG.info(
  f"--- Attempt {test_idx} ssh ubuntu@{instance.ip} Blame: 
{blame[0]}"
  )
  except IndexError:
  LOG.warning("--- Attempt {test_idx} Empty blame {blame}?")
  LOG.info(instance.execute("systemd-analyze blame"))
  blame = [""]
  altnames_persisted = False
  ip_addr = json.loads(instance.execute("ip -j addr").stdout)
  rename_race_present = False  # set true when we see eth1 not renamed
  for d in ip_addr:
  if d["ifname"] == "eth1":
  rename_race_present = True
  if len(d.get("altnames", [])) > 1:
  LOG.info(
  f"--- SUCCESS persisting altnames {d['altnames']} due to 
rename race on resource busy on {d['ifname']}"
  )
  altnames_persisted = True
  else:
 

[Touch-packages] [Bug 2012957] [NEW] Xorg freeze

[Nial Burns]

Public bug reported:

I'm not sure if this is an xorg bug because i'm pretty sure I'm using
wayland, however ubuntu-bug says it's an xorg issue.

I installed the GNOME desktop instead of the ubuntu one, however it does
happen on the ubuntu desktop as well. It seems to happen less often on
the GNOME desktop (though still multiple times a day)


When I perform certain actions I can semi-reliably produce a total screen 
freeze. Some examples include using the search menu on gnome, opening a video 
in fullscreen, and clicking buttons in fractal (matrix client.) There are many 
more scenarios that I haven't listed. The screen will completely freeze but the 
computer will keep going normally (e.g. I can type, use the cursor, listen to 
audio, etc.) This can be remedied by pressing CONTROL+ALT+F3 which brings me 
into the console, then waiting about 5 seconds, then switching back with 
CONTROL+ALT+F2

This doesn't seem to be related to any computer load issues and occurs
reliably after clicking on something/typing in a text field until the
offending program is restarted. When the program is restarted, the issue
sometimes goes away but sometimes persists. This has been happening
since I installed ubuntu a couple weeks ago.

I am able to provide more details if necessary and do some debugging
things, but I'm not a technical user so will need babying.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Mar 27 12:47:02 2023
DistUpgraded: Fresh install
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Matsushita Electric Industrial Co., Ltd. Alder Lake-P Integrated 
Graphics Controller [10f7:8338]
InstallationDate: Installed on 2023-03-15 (12 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: Panasonic Connect Co., Ltd. CFFV3-1
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=f8060648-d61e-4101-984c-4f5a1ff087f8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2022
dmi.bios.release: 1.0
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: V1.00L15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: CFFV3-1L
dmi.board.vendor: Panasonic Connect Co., Ltd.
dmi.board.version: 1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Panasonic Connect Co., Ltd.
dmi.chassis.version: 001
dmi.ec.firmware.release: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrV1.00L15:bd05/09/2022:br1.0:efr1.0:svnPanasonicConnectCo.,Ltd.:pnCFFV3-1:pvr001:rvnPanasonicConnectCo.,Ltd.:rnCFFV3-1L:rvr1:cvnPanasonicConnectCo.,Ltd.:ct10:cvr001:skuCF-FV3DFNCR:
dmi.product.family: Let'snote/TOUGHBOOK
dmi.product.name: CFFV3-1
dmi.product.sku: CF-FV3DFNCR
dmi.product.version: 001
dmi.sys.vendor: Panasonic Connect Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze kinetic ubuntu wayland-session

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not sure if this is an xorg bug because i'm pretty sure I'm using
  wayland, however ubuntu-bug says it's an xorg issue.

  I installed the GNOME desktop instead of the ubuntu one, however it
  does happen on the ubuntu desktop as well. It seems to happen less
  often on the GNOME desktop (though still multiple times a day)

  
  When I perform certain actions I can semi-reliably produce a total screen 
freeze. Some examples include using the s

[Touch-packages] [Bug 2012943] Re: Systemd-resolved is crashing

[Nick Rosbrook]

>From what I can tell, this patch is present in Jammy and newer, but not
Focal.

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: systemd (Ubuntu Focal)
   Status: New => Triaged

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

Title:
  Systemd-resolved is crashing

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system.

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  [ Where problems could occur ]

  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
  This commit is resolving the issue which is observed.

  Please refer to the above commit to assess the risk involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2012943] [NEW] Systemd-resolved is crashing

[Naveen chand]

Public bug reported:

[ Impact ]

The continuous systemd-resolved crashes delay/hang the device startup.
And this leads to unresponsive devices in the system.

[ Test Plan ]

The exact steps to reproduce this issue are still not known.
But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
But we were not able to see this crash in DHCP mode.

Steps to reproduce:
1) Powercycle the device.
2) Soft-reboot.

[ Where problems could occur ]

https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
This commit is resolving the issue which is observed.

Please refer to the above commit to assess the risk involved.

** 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/2012943

Title:
  Systemd-resolved is crashing

Status in systemd package in Ubuntu:
  New

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system.

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  [ Where problems could occur ]

  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b.
  This commit is resolving the issue which is observed.

  Please refer to the above commit to assess the risk involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2001556] Re: systemd-cryptenroll poorly communicates libtss2-rc0 dependency

[Nick Rosbrook]

I missed this my first time looking at the code, but the specific
filename is logged at the debug level. So you can at least do:

$ SYSTEMD_LOG_LEVEL=debug systemd-cryptenroll --tpm2-device=list
libtss2-esys.so.0 is not installed: libtss2-esys.so.0: cannot open shared 
object file: No such file or directory
TPM2 support is not installed.

We could probably up the log level so that this is printed by default,
but for now this is a decent workaround.

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

Title:
  systemd-cryptenroll poorly communicates libtss2-rc0 dependency

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Description:

  tpm2 support was added to jammy in 249.11-0ubuntu3.3 via LP1969375.
  libtss2-rc0 was added as a suggested package.

  $ systemd-cryptenroll --tpm2-device=list
  TPM2 support is not installed.

  Installing libtss2-rc0 allows this to resolve:
  $ sudo apt install libtss2-rc0
  $ systemd-cryptenroll --tpm2-device=list
  PATHDEVICE  DRIVER
  /dev/tpmrm0 VTPM0101:00 tpm_crb

  While this isn't inherently an issue, two things are notable:

  + The manpage for systemd-cryptenroll makes no mention that the
  suggested package needs to be installed (that I could find), this is
  only noted via `apt depends`. I only happened to find this while
  building from source.

  + The presented error implies that the pkg was build with -Dtpm2=false
  (as I read it), which is not actually the case. It should properly
  indicate the missing dep.

  The choice to leave this as a suggested dep was deliberate, so I
  believe resolution of the above two issues would suffice to provide
  enduser clarity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2001556/+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 2012788] Re: Entering Unicode characters with code points broken

[Gunnar Hjalmarsson]

If I install ibus 1.5.28-2 from experimental on Debian, there is no code
point issue. While the source is identical with 1.5.28-2 on Ubuntu, the
binaries on Debian were built with older versions of some libraries.

I'm not sure that the problem lies in glib. It's simply my intuition. ;)

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Entering Unicode characters with code points broken

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+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 1775566] Re: networkd not applying config - missing events?

[Lukas Märdian]

Netplan was ruled out (comment #4), so keep its status as "Invalid"

** Changed in: netplan.io (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  networkd not applying config - missing events?

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,

  TL;DR:
  - networkd config written by netplan
  - it seems we can eliminate netplan from this and still have the issue
  - networkd seems to miss the event of the devices and therefore consider them 
unmanaged
  - rebinding them makes it work
  - the way to trigger this I found so far are q35 KVM guests (PCIe), but 
there might be more

  ---

  I miss some hidden trigger of "netplan apply" to understand the
  following case.

  I have kvm guests, you can spawn your own one to reproduce via:
   $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
   $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
     virsh start bionic-netplan

  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
   ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:68:4b:62

  I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
     If there are match: rules, then the ID field is a purely opaque name which 
is only being used
     for references from definitions of compound devices in the config

  And I found it works just fine when I run "sudo netplan apply".

  This was odd, so to summarize up to here:
  - PCIe based virt guest
  - netplan egenrated config not working after (re)boot
  - "netplan apply" makes it working

  I disabled any cloud init things as recommended by the comment
    /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
    network: {config: disabled}
  So that I can rely on my netplan yaml to stay as is.
  I tried various things but so far can't find what magic "netplan apply" does 
which is missing to my boot.

  I checked after reboot the devices are considered unmanaged by networkctl
  $ networkctl list
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier unmanaged
    2 enp0s3   ether  off unmanaged

  But the config was generated:
  $ ll /run/systemd/network/
  total 32
  drwxr-xr-x  2 root root 200 Jun  7 09:02 ./
  drwxr-xr-x 22 root root 500 Jun  7 09:02 ../
  -rw-r--r--  1 root root  69 Jun  7 09:02 10-netplan-enp0s3.link
  -rw-r--r--  1 root root 104 Jun  7 09:02 10-netplan-enp0s3.network

  I checked the log and saw that apply restarts networkd.
  So I thought might just restart networkd, so I ran
   $ sudo systemctl restart systemd-networkd.service
  But things stayed as-is without the config being picked up.

  With some nice discussion and help on IRC I also tried to disable netplan and 
check if this is networkd only.
  # make this static networkd
  $ sudo cp /run/systemd/network/10-netplan-enp0s* /etc/systemd/network/
  # no netplan config
  $ sudo mv /etc/netplan/* /root

  That was supposed to show if networkd itself (or its config files) had issues.
  And with that it still did not work, so is the error in networkd instead?
  If so what magic thing does "netplan apply" do to fix it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1775566/+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 1877450] Re: Executing "sudo apport-bug /var/crash/some-path.crash" leads to "ERROR: Cannot update /var/crash/some-path.crash: [Errno 13] Permission denied" very often

[Lei Zhao]

My feeling is that this is due to the fact that the owner of the file is
not root. I have the same problem.  In my case, it was the `kernoops`
who owns the `linux-image-5.15.0-67-generic.33564.crash` file, which is
why `apport-cli` (or `apport-bug` in your case) cannot modify updating
the file.  After manually `chown` the file to root, I no longer have the
problem.  It is just weird that the apport didn't consider situations
like these.

In your case, it is the `mate` who owns the crash file.

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

Title:
  Executing "sudo apport-bug /var/crash/some-path.crash" leads to
  "ERROR: Cannot update /var/crash/some-path.crash: [Errno 13]
  Permission denied" very often

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Get some crash file of crashed application (in my example it was 
/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash )
  3. Try to send this crash file to launchpad using `sudo apport-bug 
/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash`

  Expected results:
  * apport opened window about sending the crash report and then opened Firefox 
allowing user to login to Launchoad and then to fill some details about the 
bug-report

  Actual results:
  * apport opened window about sending the crash, but Firefox is not opened; 
instead shows the error in the terminal

  ```
  $ sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash
  [sudo] password for mate:
  ERROR: Cannot update /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash: 
[Errno 13] Permission denied: 
'/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash'

  ```

  Note: what is interesting in this case the upload was successful:

  ```
  $ ls -alt /var/crash/
  total 5252
  -rw---  1 whoopsie whoopsie  37 May  7 23:19 
_usr_lib_mate-panel_clock-applet.1000.uploaded
  drwxrwsrwt  2 root whoopsie4096 May  7 23:19 .
  -rw-r--r--  1 root whoopsie   0 May  7 23:19 
_usr_lib_mate-panel_clock-applet.1000.upload
  -rw-r-  1 mate whoopsie 5364223 May  7 23:12 
_usr_lib_mate-panel_clock-applet.1000.crash
  drwxr-xr-x 14 root root4096 Apr 23 10:48 ..

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportLog:
   ERROR: apport (pid 2675) Thu May  7 23:10:51 2020: called for pid 2659, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2675) Thu May  7 23:10:51 2020: executable: 
/usr/lib/mate-panel/clock-applet (command line 
"/usr/lib/mate-panel/clock-applet")
   ERROR: apport (pid 2675) Thu May  7 23:10:51 2020: debug: session gdbus 
call: (true,)

   ERROR: apport (pid 2675) Thu May  7 23:10:54 2020: wrote report 
/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   600:121:127:37:2020-05-07 23:19:38.692947366 +0300:2020-05-07 
23:11:44.888143341 
+0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.uploaded
   644:0:127:0:2020-05-07 23:19:37.976589335 +0300:2020-05-07 
23:19:37.976589335 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.upload
   640:1000:127:5364223:2020-05-07 23:12:22.348865032 +0300:2020-05-07 
23:19:44.571885615 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash
  CurrentDesktop: MATE
  Date: Thu May  7 23:20:20 2020
  InstallationDate: Installed on 2020-04-23 (14 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1877450/+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 1877450] Re: Executing "sudo apport-bug /var/crash/some-path.crash" leads to "ERROR: Cannot update /var/crash/some-path.crash: [Errno 13] Permission denied" very often

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apport (Ubuntu)
   Status: New => Confirmed

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

Title:
  Executing "sudo apport-bug /var/crash/some-path.crash" leads to
  "ERROR: Cannot update /var/crash/some-path.crash: [Errno 13]
  Permission denied" very often

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Get some crash file of crashed application (in my example it was 
/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash )
  3. Try to send this crash file to launchpad using `sudo apport-bug 
/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash`

  Expected results:
  * apport opened window about sending the crash report and then opened Firefox 
allowing user to login to Launchoad and then to fill some details about the 
bug-report

  Actual results:
  * apport opened window about sending the crash, but Firefox is not opened; 
instead shows the error in the terminal

  ```
  $ sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash
  [sudo] password for mate:
  ERROR: Cannot update /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash: 
[Errno 13] Permission denied: 
'/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash'

  ```

  Note: what is interesting in this case the upload was successful:

  ```
  $ ls -alt /var/crash/
  total 5252
  -rw---  1 whoopsie whoopsie  37 May  7 23:19 
_usr_lib_mate-panel_clock-applet.1000.uploaded
  drwxrwsrwt  2 root whoopsie4096 May  7 23:19 .
  -rw-r--r--  1 root whoopsie   0 May  7 23:19 
_usr_lib_mate-panel_clock-applet.1000.upload
  -rw-r-  1 mate whoopsie 5364223 May  7 23:12 
_usr_lib_mate-panel_clock-applet.1000.crash
  drwxr-xr-x 14 root root4096 Apr 23 10:48 ..

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportLog:
   ERROR: apport (pid 2675) Thu May  7 23:10:51 2020: called for pid 2659, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2675) Thu May  7 23:10:51 2020: executable: 
/usr/lib/mate-panel/clock-applet (command line 
"/usr/lib/mate-panel/clock-applet")
   ERROR: apport (pid 2675) Thu May  7 23:10:51 2020: debug: session gdbus 
call: (true,)

   ERROR: apport (pid 2675) Thu May  7 23:10:54 2020: wrote report 
/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   600:121:127:37:2020-05-07 23:19:38.692947366 +0300:2020-05-07 
23:11:44.888143341 
+0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.uploaded
   644:0:127:0:2020-05-07 23:19:37.976589335 +0300:2020-05-07 
23:19:37.976589335 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.upload
   640:1000:127:5364223:2020-05-07 23:12:22.348865032 +0300:2020-05-07 
23:19:44.571885615 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash
  CurrentDesktop: MATE
  Date: Thu May  7 23:20:20 2020
  InstallationDate: Installed on 2020-04-23 (14 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1877450/+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 1822712] Re: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not cont

[Heinrich Schuchardt]

Splitting above sources.list line results in:
['deb', '[', 'arch=riscv64', ']', 'http://ports.ubuntu.com/ubuntu-ports/', 
'lunar', 'main', 'restricted']

Method _get_primary_mirror_from_apt_sources() incorrectly assumes that
if the second field in the line starts with '[' the next field is the
mirror url. Instead the method should look for the matching ']'. The
field after ']' is the mirror.

@staticmethod
def _get_primary_mirror_from_apt_sources(apt_sources):
"""Heuristically determine primary mirror from an apt sources.list."""
with open(apt_sources, encoding="utf-8") as f:
for line in f:
fields = line.split()
if len(fields) >= 3 and fields[0] == "deb":
if fields[1].startswith("["):
# options given, mirror is in third field
mirror_idx = 2
else:
mirror_idx = 1
if fields[mirror_idx].startswith("http://";) or fields[
mirror_idx
].startswith("https://";):
return fields[mirror_idx]

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

Title:
  https mirrors apport-retrace crashed with SystemError in
  _get_primary_mirror_from_apt_sources(): cannot determine default
  mirror: /etc/apt/sources.list does not contain a valid deb line

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  1. Have other crash occur.
  2. Click retrace locally.
  3. apport-retrace crashes.

  The only thing I can think is it's the fact that i changed my mirror to:
  deb https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe 
multiverse
  deb-src https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted 
universe multiverse

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: apport-retrace 2.20.10-0ubuntu23
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: called for pid 8661, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: executable: 
/usr/bin/gedit (command line "/usr/bin/gedit --gapplication-service")
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 10677) Mon Apr  1 19:40:42 2019: wrote report 
/var/crash/_usr_bin_gedit.1000.crash
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CrashReports:
   640:1000:117:8118520:2019-04-01 20:06:04.204469680 -0700:2019-04-01 
20:06:05.204469680 -0700:/var/crash/_usr_bin_gedit.1000.crash
   640:1000:117:23602:2019-04-01 20:06:21.172740697 -0700:2019-04-01 
20:06:22.172740697 -0700:/var/crash/_usr_bin_apport-retrace.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 20:06:22 2019
  ExecutablePath: /usr/bin/apport-retrace
  InstallationDate: Installed on 2018-04-14 (352 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -S system -C 
/home/username/.cache/apport/retrace -v --output 
/var/crash/_usr_bin_gedit.1000.crash /var/crash/_usr_bin_gedit.1000.crash
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.2-1
  PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', 
'/home/username/.cache/apport/retrace', '-v', '--output', 
'/var/crash/_usr_bin_gedit.1000.crash', '/var/crash/_usr_bin_gedit.1000.crash']
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  SourcePackage: apport
  Title: apport-retrace crashed with SystemError in 
_get_primary_mirror_from_apt_sources(): cannot determine default mirror: 
/etc/apt/sources.list does not contain a valid deb line
  UpgradeStatus: Upgraded to disco on 2019-01-05 (86 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1822712/+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 1822712] Re: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not cont

[Heinrich Schuchardt]

My sources.list file has this first deb line:

deb [ arch=riscv64 ] http://ports.ubuntu.com/ubuntu-ports/ lunar main
restricted

root@unmatched2:/var/crash# apport-retrace --gdb --sandbox system --cache 
~/.cache/apport-retrace/ _usr_bin_qemu-x86_64-static.1000.crash 
Traceback (most recent call last):
  File "/usr/bin/apport-retrace", line 743, in 
main()
  File "/usr/bin/apport-retrace", line 487, in main
sandbox, cache, outdated_msg = apport.sandboxutils.make_sandbox(
   ^
  File "/usr/lib/python3/dist-packages/apport/sandboxutils.py", line 277, in 
make_sandbox
pkg = packaging.get_file_package(
  ^^^
  File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py", line 
536, in get_file_package
return self._search_contents(file, map_cachedir, release, arch)
   
  File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py", line 
1478, in _search_contents
self._get_mirror(),
^^
  File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py", line 
1426, in _get_mirror
self._mirror = self._get_primary_mirror_from_apt_sources(
   ^^
  File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py", line 
1414, in _get_primary_mirror_from_apt_sources
raise SystemError(
SystemError: cannot determine default mirror: /etc/apt/sources.list does not 
contain a valid deb line
root@unmatched2:/var/crash# 

** Changed in: apport (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  https mirrors apport-retrace crashed with SystemError in
  _get_primary_mirror_from_apt_sources(): cannot determine default
  mirror: /etc/apt/sources.list does not contain a valid deb line

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  1. Have other crash occur.
  2. Click retrace locally.
  3. apport-retrace crashes.

  The only thing I can think is it's the fact that i changed my mirror to:
  deb https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe 
multiverse
  deb-src https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted 
universe multiverse

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: apport-retrace 2.20.10-0ubuntu23
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: called for pid 8661, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: executable: 
/usr/bin/gedit (command line "/usr/bin/gedit --gapplication-service")
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 10677) Mon Apr  1 19:40:42 2019: wrote report 
/var/crash/_usr_bin_gedit.1000.crash
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CrashReports:
   640:1000:117:8118520:2019-04-01 20:06:04.204469680 -0700:2019-04-01 
20:06:05.204469680 -0700:/var/crash/_usr_bin_gedit.1000.crash
   640:1000:117:23602:2019-04-01 20:06:21.172740697 -0700:2019-04-01 
20:06:22.172740697 -0700:/var/crash/_usr_bin_apport-retrace.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 20:06:22 2019
  ExecutablePath: /usr/bin/apport-retrace
  InstallationDate: Installed on 2018-04-14 (352 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -S system -C 
/home/username/.cache/apport/retrace -v --output 
/var/crash/_usr_bin_gedit.1000.crash /var/crash/_usr_bin_gedit.1000.crash
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.2-1
  PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', 
'/home/username/.cache/apport/retrace', '-v', '--output', 
'/var/crash/_usr_bin_gedit.1000.crash', '/var/crash/_usr_bin_gedit.1000.crash']
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  SourcePackage: apport
  Title: apport-retrace crashed with SystemError in 
_get_primary_mirror_from_apt_sources(): cannot determine default mirror: 
/etc/apt/sources.list does not contain a valid deb line
  UpgradeStatus: Upgraded to disco on 2019-01-05 (86 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1822712/+subscriptions


-- 
Mailing list:

[Touch-packages] [Bug 1966905] Re: Segfault in g_type_check_instance_cast → free_fetch_user_request → fetch_user_incrementally → on_find_user_by_name_finished → g_task_return_now

[Daniel van Vugt]

** Summary changed:

- Invalid memory access in accountsservice: free_fetch_user_request()
+ Segfault in g_type_check_instance_cast → free_fetch_user_request → 
fetch_user_incrementally → on_find_user_by_name_finished → g_task_return_now

** Description changed:

+ This is now the #1 gnome-shell crasher in Ubuntu 23.04.
+ 
  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114
  
  Valgrind memory errors in gnome-shell 42 from accountsservice:
  
  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun 

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

[Heinrich Schuchardt]

The problem is reproducible on amd64, arm64, riscv64.

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

Title:
  Entering Unicode characters with code points broken

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+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 2012788] Re: Entering Unicode characters with code points broken

[Gunnar Hjalmarsson]

Yes, Heinrich, on the surface this seems to be an ibus issue. But I
think the root cause lies in some package which ibus is built with.

If I downgrade to the binaries built by ibus 1.5.28-1 on February 23,
using code points works fine. In 1.5.28-2 two upstream commits were
added as patches, but if I now build ibus with those patches disabled,
it doesn't help. A no-change rebuild does not help either.

Maybe glib is the culprit? ibus 1.5.28-1 was built with glib 2.74.

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Entering Unicode characters with code points broken

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8

---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)

  * overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle idmapped mounts in ovl_do_(set|remove)xattr

  * Some QHD panels fail to refresh when PSR2 enabled (LP: #2009014)
- SAUCE: drm/i915/psr: Use calculated io and fast wake lines

  * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118)
- wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  * Update dg2_dmc to 2.08 (LP: #1999375)
- drm/i915/dmc: Update DG2 DMC version to v2.08

  * New DG2 workarounds (LP: #2006945)
- drm/i915/dg2: Introduce Wa_18017747507
- drm/i915/dg2: Introduce Wa_18018764978
- drm/i915/dg2: Introduce Wa_18019271663

  * Screen backlight keeps in minimized and can't change it with amdgpu
(LP: #2008871)
- SAUCE: ACPI: video: Add backlight=native DMI quirk for Dell Vostro 15 3535

  * Remove all other acpi_video backlight interface on Dell AIO platforms
(LP: #2008882)
- SAUCE: ACPI: video: Dell AIO UART backlight detection

  * screen flicker after PSR2 enabled (LP: #2007516)
- SAUCE: drm/i915/display/psr: Disable PSR2 sel fetch on panel SHP 5457

  * rtcpie in timers from ubuntu_kernel_selftests randomly failing
(LP: #1814234)
- SAUCE: selftest: rtcpie: Force passing unreliable subtest

  * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331)
- Bluetooth: btrtl: Add btrealtek data struct
- Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific
  chip

  * Jammy update: v6.1.14 upstream stable release (LP: #2008708)
- drm/etnaviv: don't truncate physical page address
- wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while
  recovery
- wifi: rtl8xxxu: gen2: Turn on the rate control
- drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink
- clk: mxl: Switch from direct readl/writel based IO to regmap based IO
- clk: mxl: Remove redundant spinlocks
- clk: mxl: Add option to override gate clks
- clk: mxl: Fix a clk entry by adding relevant flags
- powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G
- clk: mxl: syscon_node_to_regmap() returns error pointers
- sched/psi: Stop relying on timer_pending() for poll_work rescheduling
- random: always mix cycle counter in add_latent_entropy()
- scsi: libsas: Add smp_ata_check_ready_type()
- scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset
- spi: mediatek: Enable irq when pdata is ready
- docs: perf: Fix PMU instance name of hisi-pcie-pmu
- KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception
- KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid
- KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS
- can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len
- powerpc: dts: t208x: Disable 10G on MAC1 and MAC2
- spi: mediatek: Enable irq before the spi registration
- drm/i915: Remove __maybe_unused from mtl_info
- KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET
- selftests: kvm: move declaration at the beginning of main()
- powerpc/64s/radix: Fix RWX mapping with relocated kernel
- nfp: ethtool: support reporting link modes
- nfp: ethtool: fix the bug of setting unsupported port speed
- uaccess: Add speculation barrier to copy_from_user()
- x86/alternatives: Introduce int3_emulate_jcc()
- x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions
- x86/static_call: Add support for Jcc tail-calls
- Bluetooth: btusb: Add more device IDs for WCN6855
- riscv: remove special treatment for the link order of head.o
- arm64: remove special treatment for the link order of head.o
- arch: fix broken BuildID for arm64 and riscv
- powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT
- powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds
- s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36
- sh: define RUNTIME_DISCARD_EXIT
- wifi: mwifiex: Add missing compatible string for SD8787
- audit: update the mailing list in MAINTAINERS
- platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY
- platform/x86: nvidia-wmi-ec-backlight: Add force module parameter
- ext4: Fix function prototype mismatch for ext4_feat_ktype
- randstruct: disable Clang 15 support
- bpf: add missing header file include
- Linux 6.1.14
- upstream stable to v6.1.14

  * Jammy update: v6.1.13 upstream stable release (LP: #2008707)
- mptcp: sockopt: make 'tcp_fastopen_connect' generic
- mptcp: fix locking for setsockopt corner-case
- mptcp: deduplicate error paths on endpoint creation
  

[Touch-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1013.13

---
linux-oem-6.0 (6.0.0-1013.13) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1013.13 -proposed tracker (LP: #2008351)

  * CVE-2023-1281
- net/sched: tcindex: update imperfect hash filters respecting rcu

  * CVE-2023-1032
- net: avoid double iput when sock_alloc_file fails

  * rtcpie in timers from ubuntu_kernel_selftests randomly failing
(LP: #1814234)
- SAUCE: selftest: rtcpie: Force passing unreliable subtest

  * CVE-2022-2196
- KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS

  * Fix HFP mSBC support on Realtek Bluetooth USB controller (LP: #2007331)
- Bluetooth: btrtl: Add btrealtek data struct
- Bluetooth: btusb: Ignore zero length of USB packets on ALT 6 for specific
  chip

 -- Timo Aaltonen   Thu, 16 Mar 2023
17:59:47 +0200

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: Won't Fix => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2196

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1032

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1281

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Fix HFP mSBC support on Realtek Bluetooth USB controller

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in pulseaudio source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in pulseaudio source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in pulseaudio source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When a BT headset is connected Realtek BT USB controller, HFP profile can't 
play or record sound when mSBC codec is used.

  [Fix]
  At Linux kernel side, add a Realtek specific quirk to support mSBC.

  At PulseAudio side, send more data frames until the connected device
  sends response.

  [Test]
  Connect different headsets to the said controller, HFP can play and record 
sounds now.
  Also verified A2DP profile is unaffected.

  [Where problems could occur]
  The kernel part is Realtek specific, so the regression risk is very limited.

  The pulseaudio side only affects HFP profile, since the codeflow only
  changes when a mic is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 1995100] Re: /usr/share/apport/whoopsie-upload-all:ValueError:/usr/share/apport/whoopsie-upload-all@249:main:collect_info:process_report:load

[Benjamin Drung]

Verified for kinetic:

```
$ echo > malformed.crash
$ apport-unpack malformed.crash unpack
ERROR: Malformed problem report: Line '\n' does not contain a colon for 
separating the key from the value.
```

** Tags removed: verification-needed verification-needed-kinetic
** Tags added: verification-done verification-done-kinetic

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:ValueError:/usr/share/apport/whoopsie-upload-
  all@249:main:collect_info:process_report:load

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  ==

  apport-unpack and whoopsie-upload-all can crash when fed with a
  malformed problem report. They should print a proper error message
  instead of crashing. This is the most occurring apport bug in Ubuntu
  22.10 (kinetic) with as of writing 14,822 reported crashes.

  Test Plan
  =

  1. Create malformed report:
  ```
  echo > malformed.crash
  ```
  2. Try to unpack it:
  ```
  apport-unpack malformed.crash unpack
  ```

  It should print an error message instead of a stack trace.

  Where problems could occur
  ==

  The patch touches the problem report handling and therefore can affect
  apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
  with tests and apport has a test suite running during build and as
  autopkgtest.

  Original report
  ===

  ```
  Traceback (most recent call last):
    File "/usr/share/apport/whoopsie-upload-all", line 249, in 
  main()
    File "/usr/share/apport/whoopsie-upload-all", line 231, in main
  stamps = collect_info()
    File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
  res = process_report(r)
    File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report
  r.load(f, binary="compressed")
    File "/usr/lib/python3/dist-packages/problem_report.py", line 166, in load
  (key, value) = line.split(b":", 1)
  ValueError: not enough values to unpack (expected 2, got 1)
  ```

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.23.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/134ffbe13e7dd9a7f79ad6a455c6e560669a9928 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1995100/+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 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56

[Benjamin Drung]

Verified:

```
$ printf 'AB\xfc:CD\n' > malformed.crash
$ apport-unpack malformed.crash unpack
ERROR: Malformed problem report: 'ascii' codec can't decode byte 0xfc in 
position 2: ordinal not in range(128). Is this a proper .crash text file?
```

** Tags removed: verification-needed verification-needed-kinetic
** Tags added: verification-done verification-done-kinetic

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

Title:
  apport-unpack cannot load gitkraken crash report - 'ascii' codec can't
  decode byte 0xfc in position 56

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  ==

  apport-unpack and whoopsie-upload-all can crash when fed with a
  malformed problem report. They should print a proper error message
  instead of crashing. This bug does not happen that often, but the fix
  for this bug is the foundation for the fix for bug #1995100.

  Test Plan
  =

  1. Create malformed report:
  ```
  printf 'AB\xfc:CD\n' > malformed.crash
  ```
  2. Try to unpack it:
  ```
  apport-unpack malformed.crash unpack
  ```

  It should print an error message instead of a stack trace.

  Where problems could occur
  ==

  The patch touches the problem report handling and therefore can affect
  apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
  with tests and apport has a test suite running during build and as
  autopkgtest.

  Original report
  ===

  The latest GitKraken client (8.10.2 x64) is crashed every minute in
  cycle when you doing a rebase. When I try to inspect crash log to find
  the reason, the apport-unpack is not be able to process it:

  /var/lib/apport/coredump$ sudo apport-unpack 
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
 unpack
  [sudo] пароль для mingun:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 59, in 
  pr.load(f, binary=False)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
  key = key.decode('ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: 
ordinal not in range(128)

  Unfortunately, crash file is too big (~9GB) and does not compress
  further

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1996040/+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 1997759] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@596:__init__

[Benjamin Drung]

Verified:

```
$ apt install python3-apport/kinetic-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '2.23.1-0ubuntu3.1' (Ubuntu:22.10/kinetic-proposed [all]) for 
'python3-apport'
The following additional packages will be installed:
  apport apport-gtk python3-problem-report
The following packages will be upgraded:
  apport apport-gtk python3-apport python3-problem-report
4 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 193 kB of archives.
After this operation, 7168 B disk space will be freed.
[...]
```

** Tags removed: verification-needed verification-needed-kinetic
** Tags added: verification-done verification-done-kinetic

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@596:__init__

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  ==

  The Apport GUI will not start if the apport/apport-gtk/apport-kde
  package is older than 2.23.1 but python3-apport was upgraded to >=
  2.23.1. ubuntu-bug will crash:

  Traceback (most recent call last):
    File "/usr/share/apport/apport-gtk", line 596, in 
  app = GTKUserInterface()
    File "/usr/share/apport/apport-gtk", line 56, in __init__
  apport.ui.UserInterface.__init__(self)
  TypeError: UserInterface.__init__() missing 1 required positional argument: 
'argv'

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.23.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/feb7fb0f8e0c34715dc6cf742f9d16824c977662 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Test Plan
  =

  1. Install apport from jammy:
  ```
  sudo apt install apport/jammy apport-gtk/jammy python3-apport/jammy 
python3-problem-report/jammy
  ```
  2. Upgrade python3-apport:
  ```
  sudo apt install python3-apport/kinetic-proposed
  ```
  3. Launch apport-bug:
  ```
  apport-bug
  ```

  All four apport package should be upgraded and apport-bug should
  launch without problems.

  Where problems could occur
  ==

  The added Breaks will affect how APT handles the packages and could
  trigger/reveal bug there or could put pressure on APT finding a
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1997759/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

** Tags removed: verification-bionic-bionic
** Tags added: verification-done-bionic

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2003797] Re: Pre-1970 timestamps are knowingly wrong

[Benjamin Drung]

Verified successful autopkgtest on
https://autopkgtest.ubuntu.com/packages/tzdata:

kinetic:

* amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/t/tzdata/20230325_002604_b0976@/log.gz
* arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/t/tzdata/20230325_030734_7c004@/log.gz
* armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/armhf/t/tzdata/20230324_202757_068f8@/log.gz
* ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/ppc64el/t/tzdata/20230324_202842_068f8@/log.gz
* s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/s390x/t/tzdata/20230323_181059_8456e@/log.gz

jammy:

* amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/t/tzdata/20230325_014013_602ca@/log.gz
* arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/t/tzdata/20230325_025254_6c459@/log.gz
* armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/t/tzdata/20230325_18_a8d6b@/log.gz
* ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/t/tzdata/20230325_000151_7b7b6@/log.gz
* s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/t/tzdata/20230324_012146_1b785@/log.gz

focal:

* amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/t/tzdata/20230325_020652_ddd0c@/log.gz
* arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/t/tzdata/20230325_030744_8614c@/log.gz
* armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/t/tzdata/20230324_235911_b14f3@/log.gz
* ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/t/tzdata/20230325_32_c8a5a@/log.gz
* s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/t/tzdata/20230323_234702_402d8@/log.gz

** Tags removed: verification-needed verification-needed-focal 
verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done verification-done-focal 
verification-done-jammy verification-done-kinetic

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

Title:
  Pre-1970 timestamps are knowingly wrong

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build
  with 'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."

  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are
  identical since 1970, but they differed before 1965. Berlin observed
  no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So
  summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin:

  ```
  $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
  Fri Jul  1 12:00:00 CEST 1960
  $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z"
  Fri Jul  1 11:00:00 CET 1960
  ```

  There was a big debate upstream (see https://lwn.net/Articles/870478/
  or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The
  Debian/Ubuntu package should ship timezones from backzone. Users that
  care about pre-1970 timestamps will be satisfied and users not caring
  will probably not care about the additional timezones.

  The install size will increase by around 20% and the amount of
  distinct (i.e. not symlinked) timezones will increase by 33%:

  

[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

Remaining test for bionic:

```
$ apt install tzdata=2023b-0ubuntu0.18.04.0
$ diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)
$
```

Also verified that all autopkgtest succeeded:
https://autopkgtest.ubuntu.com/packages/tzdata

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012902] Re: netplan plugin: generated NM config when using globbing will be used for only one connection

[Lukas Märdian]

** Tags added: netplan-everywhere

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

Title:
  netplan plugin: generated NM config when using globbing will be used
  for only one connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  There is a mismatch between what netplan expresses when using globbing
  in a netplan file and what NM understands when using a match setting.
  For instance:

  network:
  version: 2
  ethernets:
  all-en:
  match:
  name: "en*"
  dhcp4: true

  Generates a NM connection in /run/NetworkManager/system-connections:

  ...
  [match]
  interface-name=en*;
  ...

  But an NM connection can only match one interface, so if two
  interfaces like ens2 and ens3 exist, only one of them will be
  configured, even though the netplan configuration is expected to be
  applied to both.

  Solving this might involve generating one NM connection in the netplan
  plugin per detected interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2012902/+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 2012902] [NEW] netplan plugin: generated NM config when using globbing will be used for only one connection

[Alfonso Sanchez-Beato]

Public bug reported:

There is a mismatch between what netplan expresses when using globbing
in a netplan file and what NM understands when using a match setting.
For instance:

network:
version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4: true

Generates a NM connection in /run/NetworkManager/system-connections:

...
[match]
interface-name=en*;
...

But an NM connection can only match one interface, so if two interfaces
like ens2 and ens3 exist, only one of them will be configured, even
though the netplan configuration is expected to be applied to both.

Solving this might involve generating one NM connection in the netplan
plugin per detected interface.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  netplan plugin: generated NM config when using globbing will be used
  for only one connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  There is a mismatch between what netplan expresses when using globbing
  in a netplan file and what NM understands when using a match setting.
  For instance:

  network:
  version: 2
  ethernets:
  all-en:
  match:
  name: "en*"
  dhcp4: true

  Generates a NM connection in /run/NetworkManager/system-connections:

  ...
  [match]
  interface-name=en*;
  ...

  But an NM connection can only match one interface, so if two
  interfaces like ens2 and ens3 exist, only one of them will be
  configured, even though the netplan configuration is expected to be
  applied to both.

  Solving this might involve generating one NM connection in the netplan
  plugin per detected interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2012902/+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 2012788] Re: Entering Unicode characters with code points broken

[Heinrich Schuchardt]

See https://wiki.archlinux.org/title/IBus#Unicode_input

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

Title:
  Entering Unicode characters with code points broken

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012788/+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 2012788] Re: Entering Unicode characters with code points broken

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ibus (Ubuntu)
   Status: New => Confirmed

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

Title:
  Entering Unicode characters with code points broken

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012788/+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 2012788] Re: Entering Unicode characters with code points broken

[Heinrich Schuchardt]

The same problem exists on KDE. So this looks more like an issue in ibus
then in gnome-shell.

** Package changed: gnome-shell (Ubuntu) => ibus (Ubuntu)

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

Title:
  Entering Unicode characters with code points broken

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012788/+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 2012788] [NEW] Entering Unicode characters with code points broken

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On an updated lunar, following this instruction:

https://help.ubuntu.com/stable/ubuntu-help/tips-
specialchars.html#ctrlshiftu

no longer works. If I press for instance

Ctrl+Shift+U followed by 2014

I see u2014 (underlined) on the screen. But it's not replaced with the
expected character (in this case an Em Dash) when I confirm with Space
or Enter — it just disappears.

** Affects: ibus (Ubuntu)
 Importance: High
 Status: New


** Tags: lunar regression-release rls-ll-incoming
-- 
Entering Unicode characters with code points broken
https://bugs.launchpad.net/bugs/2012788
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ibus in Ubuntu.

-- 
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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

[Łukasz Zemczak]

Hello Stefan, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Focal)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Łukasz Zemczak]

Hello Kleber, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [SRU Impact]

  Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, 
test_protect_syscall
  sysctl is called with the expectation the error result is EFAULT and not 
ENOSYS.
  This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, 
oem, gke, oracle).

  [Fix]
  Assertion checks if either EFAULT or ENOSYS is returned. This way it will 
work for focal-5.4 kernels and focal-5.15 kernels.

  [Test to reproduce the issue]
  1. Create a vm and install one of the focal-5.15 kernels (i.e 
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
  2. Run the autotests for upstream and/or root-unittests:
  autopkgtest --test-name=upstream systemd -- qemu 

  [Test to verify the fix]
  1. Same as above
  2. Apply the fix in your local repo and run the tests using your local repo
  autopkgtest --test-name=upstream  -- qemu 

  [Where problems could occur]
  This is not gonna affect end users since it is a change in the test only.
  It may impact autotests, but it's a very low probability.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)

  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion
  failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 2002445] Re: udev NIC renaming race with mlx5_core driver

[Łukasz Zemczak]

Hello Nick, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.21 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit).

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import json
  import logging
  import os
  import sys
  from enum import Enum

  import pycloudlib

  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba]
  """

  #source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # - apt install systemd udev -y --allow-unauthenticated

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: {source}
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  class BootCondition(Enum):
  SUCCESS_WITHOUT_RENAME_RACE = "network bringup success without rename 
race"
  SUCCESS_WITH_RENAME_RACE = "network bringup success rename race condition"
  ERROR_NETWORK_TIMEOUT = "error: timeout on systemd-networkd-wait-online"

  
  def batch_launch_vm(
  client, instance_type, image_id, user_data, instance_count=5
  ):
  instances = []
  while len(in

[Touch-packages] [Bug 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Dariusz Gadomski]

Bionic verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023

After upgrade to 2023b-0ubuntu0.18.04.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 01:00:01 EET 2023

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-bionic-bionic verification-done

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Dariusz Gadomski]

Focal verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023

After upgrade to 2023b-0ubuntu0.20.04.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 01:00:01 EET 2023

** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Dariusz Gadomski]

Jammy verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023

After upgrade to 2023b-0ubuntu0.22.04.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 01:00:01 EET 2023

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Dariusz Gadomski]

Kinetic verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023

After upgrade to 2023b-0ubuntu0.22.10.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 01:00:01 EET 2023

** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 1966905] Re: Invalid memory access in accountsservice: free_fetch_user_request()

[Daniel van Vugt]

Tracking also in
https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

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

Title:
  Invalid memory access in accountsservice: free_fetch_user_request()

Status in accountsservice:
  New
Status in gnome-control-center:
  Unknown
Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==  Address 0x185b5110 is 0 bytes inside a 

[Touch-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice

[Daniel van Vugt]

Upstream reckons this has fixed it for gnome-control-center:
https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/1681

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2348
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2348

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2348
   Importance: Unknown
   Status: Unknown

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Fix Released

** Tags added: fixed-in-gnome-control-center-44.rc

** Summary changed:

- Memory access errors in gnome-shell from accountsservice
+ Invalid memory access in accountsservice: free_fetch_user_request()

** Description changed:

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
+ https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114
  
  Valgrind memory errors in gnome-shell 42 from accountsservice:
  
  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_con

[Touch-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice

[Daniel van Vugt]

See also bug 2012879

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

Title:
  Invalid memory access in accountsservice: free_fetch_user_request()

Status in accountsservice:
  New
Status in gnome-control-center:
  Unknown
Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4:

[Touch-packages] [Bug 2012879] Re: Crash in indicator-messages-service

[Daniel van Vugt]

Tracking in
https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d

** Tags added: jammy kinetic

** Description changed:

+ https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d
+ 
  Crash in indicator-messages-service
  
  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 14:25:09 2023
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
  ExecutableTimestamp: 1633601577
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
  ProcCwd: /home/dan
  ProcEnviron:
-  LANG=en_AU.UTF-8
-  LANGUAGE=en_AU:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=en_AU.UTF-8
+  LANGUAGE=en_AU:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: indicator-messages
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

** Summary changed:

- Crash in indicator-messages-service
+ indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from 
_act_user_update_from_object_path() from fetch_user_incrementally() from 
on_find_user_by_name_finished() from g_task_return_now()

** Package changed: indicator-messages (Ubuntu) => accountsservice
(Ubuntu)

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

Title:
  indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from
  _act_user_update_from_object_path() from fetch_user_incrementally()
  from on_find_user_by_name_finished() from g_task_return_now()

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d

  Crash in indicator-messages-service

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 14:25:09 2023
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
  ExecutableTimestamp: 1633601577
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
  ProcCwd: /home/dan
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: indicator-messages
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 2012879] [NEW] indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d

Crash in indicator-messages-service

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
Uname: Linux 6.2.0-18-generic x86_64
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 14:25:09 2023
ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
ExecutableTimestamp: 1633601577
ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
ProcCwd: /home/dan
ProcEnviron:
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
Signal: 11
SourcePackage: indicator-messages
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

** Affects: accountsservice (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-crash jammy kinetic lunar rls-ll-incoming
-- 
indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from 
_act_user_update_from_object_path() from fetch_user_incrementally() from 
on_find_user_by_name_finished() from g_task_return_now()
https://bugs.launchpad.net/bugs/2012879
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to accountsservice in Ubuntu.

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