[Touch-packages] [Bug 2001922] Re: Xorg crash
Please tell us the contents of /var/crash/_usr_lib_xorg_Xorg.0.uploaded as it will contain the unique ID of the Xorg crash. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias:
[Touch-packages] [Bug 1783689] Re: [Dell XPS 15 9560] No sound from speakers
Zero speaker_outs sounds like the issue: [4.273272] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3266: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [4.273274] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.273276] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.273277] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.273278] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.273280] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x18 [4.273282] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [4.273283] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 ** Summary changed: - [HDA-Intel - HDA Intel PCH, playback] No sound at all + [Dell XPS 15 9560] No sound from speakers ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: jammy kinetic ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1783689 Title: [Dell XPS 15 9560] No sound from speakers Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Speakers work from windows partition. Hear sounds when ubuntu log in page comes up. Once logged in cannot hear sound using alsa or pulseaudio. No reports of speaker problems or app complaints ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon1974 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 25 22:26:23 2018 InstallationDate: Installed on 2018-01-05 (201 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon1974 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1783689/+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 1668317] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 ** This bug has been marked a duplicate of bug 1783689 [HDA-Intel - HDA Intel PCH, playback] No sound at all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1668317 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu 16.04.1 on Dell XPS15 9650 dose not have sound after installing Graphics Drivers Nvidia375.39 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Feb 27 16:03:02 2017 InstallationDate: Installed on 2017-02-27 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1668317/+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 1965750] Re: [jammy regression] No sound from onboard audio (playback / record)
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 ** This bug has been marked a duplicate of bug 1783689 [Dell XPS 15 9560] No sound from speakers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965750 Title: [jammy regression] No sound from onboard audio (playback / record) Status in alsa-driver package in Ubuntu: New Bug description: After updates I applied last friday, my onboard audio has ceased to function. No audio comes out the laptop speakers and no audio goes in the internal microphone (built in audio). If I connect my bluetooth headset (Bose NC700) the audio works, but only ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono. I tried switching from pulseaudio to pipewire and pipewire-pulse, and I kind of made it work - the bluetooth headset works correctly, and the onboard audio works again after switching default inputs and outputs a number of times. I just want to stress my laptop's audio has worked fine for years in all versions of ubuntu including Jammy, but only up until Friday Jan the 18th 2022. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Mon Mar 21 11:48:25 2022 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750/+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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 Tracking in bug 1783689. ** This bug has been marked a duplicate of bug 1783689 [Dell XPS 15 9560] No sound from speakers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 It looks like ALSA (the kernel) needs some tweaking because it is reporting "speaker_outs=0" Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3266: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: inputs: Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x18 Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 ** Summary changed: - Pipewire correctly detects laptop sound & speakers but no sound + [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound ** Changed in: pipewire (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: pipewire (Ubuntu) ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 1988859] Re: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]
Likely (the proper) fix committed to mesa in: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20397 ** Changed in: mesa (Ubuntu) Status: New => Triaged -- 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/1988859 Title: Periodic black frames and stutter [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)] Status in Mesa: New Status in Mutter: New Status in mesa package in Ubuntu: Triaged Status in mutter package in Ubuntu: In Progress Bug description: Every so often, the desktop will go black and then re appear on Ubuntu 22.10 Wayland Session which should not be occurring (this does not happen on 22.04.) Note that only the cursor can be seen. Reporting this before release so that it can be patched for (at least) the RasPi. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8 Uname: Linux 5.19.0-1001-raspi aarch64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.23.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 16:10:37 2022 DisplayManager: gdm3 ImageMediaBuild: 20220826 RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1988859/+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 83628] Re: Stuff from imagemagick ends up as environment variables
EDIT: Sorry, just realized how old this was; will leave this for
posterity and anyone coming in...
@husoki, did you see this comment --
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/83628/comments/1?
This is part of the very mature, much adored "bash completion" protocol
that allows authors to implement custom bash shell autocomplete
suggestion intelligence for their shell apps. If you're not familiar,
suggestions take place when you press TAB (twice in a row, usually)
whilst somewhere in the course of writing a command into the shell. A
common built-in example would be to type `/usr/b`, then TAB + TAB, at
which point `/usr/bin` would autofill in. If multiple possible results
exist, they would be displayed exhaustively in a useful, interactive
listing.
Apps often implement completion for everything from flags and param
names to subcommands even all the way to param values that require
external network traffic to fetch results, e.g.:
```
# TAB completion custom example
$ example-cloud-app get-user-d
_[TAB + TAB autofills to the following...]_
$ example-cloud-app get-user-details
_[user continues typing]...
$ example-cloud-app get-user-details --user-name=
_[TAB + TAB fetches users from remote and shows possible values...]_
$ example-cloud-app get-user-details --user-name=
zekev husoski johnd
$ example-cloud-app get-user-details --user-name=h
_[TAB + TAB]_
$ example-cloud-app get-user-details --user-name=husoski
```
In this example, the authors of `example-cloud-app` would have also
authored their bash_completion script, which would usually consist of a
callback function for the bash_completion lib to call when TAB + TAB is
pressed and the user wants results. That callback function is what you
see loaded into the env from the dump in here. If you want to see only
env vars without functions, you can just use the `env` command or
`printenv` and avoid using `set` which as discovered here also does
include functions in its output—a behavior that one can assume with
almost total certainty will probably never be removed given the
ubiquitous, simple alternatives and current historical expectations
which seem to me to be eminently reasonable. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/83628
Title:
Stuff from imagemagick ends up as environment variables
Status in bash package in Ubuntu:
Invalid
Bug description:
Binary package hint: imagemagick
When running the 'set' command, stuff from ImageMagick ends up in the
output.
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_COMPLETION=/etc/bash_completion
BASH_COMPLETION_DIR=/etc/bash_completion.d
BASH_LINENO=()
BASH_SOURCE=()
bash205='3.2.9(1)-release'
bash205b='3.2.9(1)-release'
bash3='3.2.9(1)-release'
_ImageMagick ()
{
local prev;
prev=${COMP_WORDS[COMP_CWORD-1]};
case "$prev" in
-channel)
COMPREPLY=($( compgen -W 'Red Green Blue Opacity \
Matte Cyan Magenta Yellow Black' -- $cur ));
return 0
;;
-colormap)
COMPREPLY=($( compgen -W 'shared private' -- $cur ));
return 0
;;
-colorspace)
COMPREPLY=($( compgen -W 'GRAY OHTA RGB Transparent \
XYZ YCbCr YIQ YPbPr YUV CMYK' -- $cur ));
return 0
;;
-compose)
COMPREPLY=($( compgen -W 'Over In Out Atop Xor Plus \
Minus Add Subtract Difference Multiply
Bumpmap\
Copy CopyRed CopyGreen CopyBlue CopyOpacity'
-- $cur ));
return 0
;;
...
etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/83628/+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 2002043] [NEW] Python extension modules get built using wrong compiler flags with python2
Public bug reported:
Compiling a Python extension using Python2 (Python 2.7.18) is making use
of wrong compiler flags, hence dropping required optimizations when
required. This is happening only when python2 is installed from Ubuntu's
repositories. By default, Python's distutils module uses compiler and
linker flags used to compile Python itself to be used to compile
extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch there
as well. Patch used on python3, is not modifying the cflags completely and
instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
** Affects: python2.7 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Python extension modules get build using wrong compiler flags with python2
+ Python extension modules get built using wrong compiler flags with python2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
[Touch-packages] [Bug 1881504] Re: cross-testing essential packages fails
This continues to be an issue and one which I ran into recently: runner/autopkgtest --setup-commands="dpkg --add-architecture i386; apt-get update" --architecture i386 gzip -- qemu --ram-size=4096 --cpus=4 /srv/vms/autopkgtest-lunar-amd64.img ... Broken gzip:amd64 Conflicts on gzip:i386 < none -> 1.12-1ubuntu1 @un puN Ib > Considering gzip:i386 5103 as a solution to gzip:amd64 5103 Removing gzip:amd64 rather than change gzip:i386 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gzip : Conflicts: gzip:i386 but 1.12-1ubuntu1 is to be installed gzip:i386 : Conflicts: gzip but 1.12-1ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. simple-gzip FAIL badpkg blame: gzip badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. autopkgtest [14:05:26]: summary simple-gzip FAIL badpkg blame: gzip badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. qemu-system-x86_64: terminating on signal 15 from pid 1828712 (/usr/bin/python3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1881504 Title: cross-testing essential packages fails Status in apt package in Ubuntu: Won't Fix Status in autopkgtest package in Ubuntu: Confirmed Status in gzip package in Ubuntu: New Bug description: Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz ... autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1 autopkgtest [19:51:38]: build not needed autopkgtest [19:51:38]: test simple-gzip: preparing testbed Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages will be REMOVED: gzip The following NEW packages will be installed: build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0 libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22 libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1 linux-libc-dev WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! gzip 0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. E: Failed to process build dependencies ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1881504/+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 1699942] Re: network-manager fails to deprecate addresses
** Changed in: systemd (Ubuntu) Status: New => Won't Fix ** Changed in: systemd (Ubuntu) Status: Won't Fix => Incomplete -- 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/1699942 Title: network-manager fails to deprecate addresses Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI Status in systemd package in Ubuntu: Incomplete Bug description: Hi there! I'm running ubuntu 22.04.1 LTS installed via the ISO image ubuntu-22.04.1-desktop-amd64.iso. This issue affects both the Live CD and installed operating system. I have configured my modem's DHCP server to push my adguard home DNS server (cloud-hosted) as the DNS for the network. I have an access point that is setup to do the same. With the Live CD and installed operating system, there is a local DNS server installed that runs on 127.0.0.1:53. Somehow this bypasses the DNS servers I've configured for the network and suddenly websites that have been blocked for being malicious or harmful are now accessible. There is no option in the installer or GUI to disable this. Changing the network DNS settings via the GUI of either the live cd or installation do not change the behavior and do not result in the specified DNS server(s) being used. The 127.0.0.1:53 server still overrides anything set in the GUI. The only way I have found to override this behavior is to edit /etc/systemd/resolved.conf: 1) uncomment DNSStubListener=yes 2) change yes to no 3) save file 4) run the following commands in terminal: sudo systemctl daemon-reload sudo systemctl restart systemd-networkd sudo systemctl restart systemd-resolved After doing so, the DNS servers that have been provided by DHCP are properly used. This is considered a security vulnerability due to there being no way for a normal user to change this setting without editing system configuration files and no warning given to the user that the settings they are applying in the GUI have not been applied due to this default configuration. This is considered a hack if this is the intentional configuration as it overrides network configuration options set by the DHCP server. I've resolved it for myself for now by making a custom iso image that removes this configuration by default and instead installs the /etc/systemd/resolved.conf file attached to this bug report. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.4 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 21:18:35 2022 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 2022.08.28 LTS "Custom Jammy Jellyfish" (20220828) MachineType: Micro-Star International Co., Ltd. GS75 Stealth 9SG ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2019 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17G1IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-17G1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17G1IMS.10C:bd03/26/2019:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGS75Stealth9SG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17G1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17G1.1: dmi.product.family: GS dmi.product.name: GS75 Stealth 9SG dmi.product.sku: 17G1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. mtime.conffile..etc.systemd.resolved.conf: 2022-08-28T19:29:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+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 772024] Re: tzdata update keeps changing my timezone
Tested on Ubuntu 22.04 (jammy) and 23.04 (lunar) and the issue is still there: ``` apt install -y tzdata echo "US/Central" > /etc/timezone ln -sf /usr/share/zoneinfo/US/Central /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` The dpkg-reconfigure says "Current default time zone: 'America/Chicago'". -- 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/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Triaged Status in tzdata package in Debian: New Bug description: Binary package hint: tzdata Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+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 868395] Re: Bug in Europe/Russia timezones
I can reproduce this slowdown in a Ubuntu jammy chroot:
```
apt install -y gcc tzdata
printf '#include \n#include \n\nint main() {\n time_t t =
time(0);\n int i;\n struct tm result;\n for(i=0; i < 1000; i++)\n
localtime_r(, );\n puts(ctime());\n return 0;\n}\n' > bug.c
gcc ./bug.c
time ./a.out
ln -sf /usr/share/zoneinfo/Europe/Moscow /etc/localtime
dpkg-reconfigure --frontend noninteractive tzdata
time ./a.out
```
On my machine it takes 0.284s for Etc/UTC but 1.276s for Europe/Moscow.
Europe/Berlin takes 0.378s. This needs to be reported upstream.
** Changed in: tzdata (Ubuntu)
Status: Confirmed => Triaged
--
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/868395
Title:
Bug in Europe/Russia timezones
Status in tzdata package in Ubuntu:
Triaged
Bug description:
In version tzdata-2011j (tzdata-2011k also affected) was founded strange bug
in russian timezones.
Because of a law "On the Calculation of Time" there were changes in zone like:
3:00 Russia MSK/MSD 2011
changed to:
3:00 Russia MSK/MSD 2011 Mar 27 2:00s
4:00 - MSK
But if no rule used for this change (using "-" instead of rule "Russia"),
calling of system function localtime_r() takes more time (takes more than 40%
time longer).
I used following code for measuring:
==
#include
#include
int main() {
time_t t = time(0);
int i;
struct tm result;
for(i=0; i < 1000; i++)
localtime_r(, );
puts(ctime());
return 0;
}
==
and also this sql code in mysql db:
select benchmark(100, from_unixtime(1317044847));
For example, when I'm using new tzdata-2011j results are:
1. time ./a.out (c code)
real 0m5.165s
user 0m5.140s
sys 0m0.000s
2. sql query
mysql> select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (1.03 sec).
And when I'm using old tzdata-2008b:
1. time ./a.out (c code)
real 0m1.675s
user 0m1.450s
sys 0m0.000s
2. sql query
mysql> select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (0.65 sec)
This bug seemed critical on high loaded systems (for example, for
databases that using unix timestamps).
My configuration was:
Description: Ubuntu 8.04.1
Release: 8.04
Packages: 2011j~repack-0ubuntu0.8.04 and 2008b-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/+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 640753] Re: Latvia time zone during installation is wrong
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug report is quite old. Do you still experience this issue? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/640753 Title: Latvia time zone during installation is wrong Status in tzdata package in Ubuntu: Incomplete Bug description: Binary package hint: tzdata Latvia time zone during installation is wrong. In BIOS there is correct time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/640753/+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 1648556] Re: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Description changed: - no details + Setting up tzdata (2016j-0ubuntu0.16.04) ... + Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. + Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67. + Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68. + Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. + Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67. + Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68. + Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. + Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67. + Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68. + Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 109. + dpkg: error processing package tzdata (--configure): + subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016j-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 8 17:56:04 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2013-05-30 (1288 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all RelatedPackageVersions: - dpkg 1.18.4ubuntu1.1 - apt 1.2.15 + dpkg 1.18.4ubuntu1.1 + apt 1.2.15 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-08-30 (99 days ago) -- 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/1648556 Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in tzdata package in Ubuntu: Confirmed Bug description: Setting up tzdata (2016j-0ubuntu0.16.04) ... Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67. Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68. Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67. Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68. Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67. Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68. Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 109. dpkg: error processing package tzdata (--configure): subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016j-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 8 17:56:04 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2013-05-30 (1288 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-08-30 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1648556/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1672111] Re: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Description changed: - 1 + Setting up tzdata (2016j-0ubuntu0.16.04) ... + + Current default time zone: 'America/Los_Angeles' + date: invalid date 'Sun Mar 12 02:38:57 UTC 2017' + dpkg: error processing package tzdata (--configure): + subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016j-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Mar 11 18:38:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-02-15 (24 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: - dpkg 1.18.4ubuntu1.1 - apt 1.2.19 + dpkg 1.18.4ubuntu1.1 + apt 1.2.19 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1672111 Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: Confirmed Bug description: Setting up tzdata (2016j-0ubuntu0.16.04) ... Current default time zone: 'America/Los_Angeles' date: invalid date 'Sun Mar 12 02:38:57 UTC 2017' dpkg: error processing package tzdata (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016j-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Mar 11 18:38:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-02-15 (24 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1672111/+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 600410] Re: BIOS "power on at specified time" stops working if "tzdata" not updated after 14 days
Thank you for taking the time to report this bug and helping to make Ubuntu better. I am really puzzled how a pending update for tzdata could cause this behavior. Do you still have that server and experience this problem? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/600410 Title: BIOS "power on at specified time" stops working if "tzdata" not updated after 14 days Status in tzdata package in Ubuntu: Incomplete Bug description: Binary package hint: tzdata My backup server is configured in BIOS to auto power on at 0300 daily and backup my main server. I recently realised that for the last week it has not been powering on and running backups. When I look in the syslog I can see that it was running fine until a week ago and has not powered on since. "sudo apt-get dist-upgrade" shows one package "tzdata" awaiting installation on this machine. I can see that this package became available 2 weeks before BIOS auto power on stopped working - it was reported as available for 14 days and on the 15th day (and every day since) the auto power on did not happen. Having manually installed the "tzdata" update, the server is now working correctly again. The exact same problem happened many months ago and by looking back through logs I can see that again it happened 14 days after a "tzdata" update became available. On that previous occasion when I installed this package manually the server again started powering up correctly. As such there seems to be some link between "tzdata" packages available but not installed, and the ability of BIOS auto power on to function correctly. ProblemType: Bug Architecture: i386 Date: Wed Jun 30 22:54:21 2010 SourcePackage: tzdata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/600410/+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 546210] Re: Indian Standard Time needs update
I checked tzdata 2022g. There we have Asia/Kolkata. So your point A was addressed. I am marking this bug as fixed. If there are issues remaining, please contact the upstream mailing list t...@iana.org to get it fixed there. The fix will then trickle down to Ubuntu. ** Changed in: tzdata (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/546210 Title: Indian Standard Time needs update Status in tzdata package in Ubuntu: Fix Released Bug description: Binary package hint: tzdata Hi, I would like to suggest important updates to the Indian Time Zone (IST). 1. The timezone is sometimes listed as Asia/Calcutta. There are three things wrong with using "Calcutta". A] The city is now Kolkata (I think I have seen Asia/Kolkata somewhere). B] Kolkata is no longer the largest city in India. C] No time-keeping related activity is associated with Kolkata. (IST is measured from Mirpur, near Allahabad) So, instead of using Kolkata, please change it to the capital city, New Delhi. 2. In the list of Indian cities, the old city names are present, and not the new. It's been 15 years since some of the city names have been changed, but no such updates are seen in Ubuntu. eg, Bombay > Mumbai, Calcutta > Kolkata, Madras > Chennai, Bangalore > Bengaluru. Instead of deleting the old names, I would suggest that new entries be copied from the old names so that Bombay and Mumbai both exist. I am interested in adding more Indian cities to the list of available cities in India when selecting a time zone. How do I do this? ProblemType: Bug Architecture: amd64 Date: Thu Mar 25 01:31:31 2010 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: wl nvidia Package: tzdata 2010e-0ubuntu0.9.10 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.57-generic SourcePackage: tzdata Uname: Linux 2.6.31-20-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/546210/+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 458331] Re: time-admin doesn't have Brazil's official time zone
Thank you for taking the time to report this bug and helping to make Ubuntu better. As of tzdata 2022g there are following timezones of Brazil: America/Noronha America/Belem America/Santarem America/Fortaleza America/Recife America/Araguaina America/Maceio America/Bahia America/Sao_Paulo America/Campo_Grande America/Cuiaba America/Porto_Velho America/Boa_Vista America/Manaus America/Eirunepe America/Rio_Branco See https://data.iana.org/time-zones/tz-link.html for details about the naming. Quote from there: "Timezones are typically identified by continent or ocean and then by the name of the largest city within the region containing the clocks." This kind of change must be done via the upstream project instead of only in Ubuntu. Please contact upstream via the t...@iana.org mailing list. Expect them to ask for evidence. Having Brasília time publicly used might convince them to change this timezone name. I am marking this bug as "Won't Fix" (as in not deviating from the upstream naming) for the Ubuntu tzdata package. Upstream changes will trickle down to Ubuntu. ** Changed in: tzdata (Ubuntu) Status: Triaged => Won't Fix -- 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/458331 Title: time-admin doesn't have Brazil's official time zone Status in gnome-system-tools package in Ubuntu: Triaged Status in tzdata package in Ubuntu: Won't Fix Bug description: Binary package hint: gnome-system-tools This is a feature request. Brazil's official time zone, Brasília time (GMT -3), is not on Ubuntu's Time Zone list. This is a very important time zone for us, because practically all national events are advertised as "X hours, Brasília time". The current workaround is to set it to America/Sao_Paulo, because the city of São Paulo follows the country's official time, but Ubuntu would feel a lot more comfortable to us brazilians if there was an America/Brasilia time zone to choose. Not to mention that, although São Paulo is Brazil's biggest city, Brasília is the actual capital, and because it is nowhere near São Paulo (they're a thousand km apart), it is not obvious that they share the same time zone. ProblemType: Bug Architecture: i386 Date: Thu Oct 22 12:40:19 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/time-admin Package: gnome-system-tools 2.28.1-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-system-tools Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/458331/+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 308983] Re: timezone info is forgotten at reboot
Nowadays /etc/localtime is a symlink to the timezone data in /usr/share/zoneinfo. Do you still see the same problem with recent Ubuntu version or was it fixed since then? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/308983 Title: timezone info is forgotten at reboot Status in tzdata package in Ubuntu: Incomplete Bug description: My timezone is +0530 UTC. I store my local time in the BIOS. After upgrading from hardy to intrepid, my time always runs +0530 faster than my local time zone, making it in effect +1100 UTC. Even after configuring the time with the 'date' command, this doesn't stay between reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/308983/+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
Let's reopen this bug report again.
** Changed in: apport (Ubuntu)
Status: Fix Released => Triaged
** Changed in: apport
Milestone: 2.24.0 => 2.25.0
** Changed in: apport
Status: Fix Released => Triaged
--
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:
Triaged
Status in apport package in Ubuntu:
Triaged
Status in apport source package in Kinetic:
New
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 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56
Upstream merge request to fix that case:
https://github.com/canonical/apport/pull/52
--
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:
Triaged
Status in apport package in Ubuntu:
Triaged
Status in apport source package in Kinetic:
New
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 1457285] Re: Request for Russian Antarctic stations
Feedback from the upstream mailing list: * Are there sources and citations for these locations? * Do they have Daylight Saving Time? * How does the time shown on the wall at these stations differ from existing time zones, what is the history of the zone at each station, and how can it be verified? Please answer these question (either here or on the upstream mailing list). ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/1457285 Title: Request for Russian Antarctic stations Status in tzdata package in Ubuntu: Incomplete Bug description: Please add Russian Antarctic research stations to tzdata. They are: AQ -6212-05858 Antarctica/Bellingshausen Bellingshausen Station, Vaterloo Island, GMT-4 AQ -7046+01149 Antarctica/Novolasarevskaya Novolasarevskaya Station, GMT AQ -6739+04530 Antarctica/Molodezhnaya Molodezhnaya Station, GMT+3 AQ -6633+09300 Antarctica/Mirniy Mirniy Station, GMT+7 AQ -6930+15923 Antarctica/Leningradskaya Leningradskaya Station, GMT+10 AQ -7445-13648 Antarctica/Russkaya Russkaya Station, GMT-6 AQ -6922+07623 Antarctica/Progress Progress Station, GMT+5 AQ -6944+07342 Antarctica/Druzhnaya Druzhnaya Station, GMT+5 Please mean that GMT data given are POSIX inversed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1457285/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
I have accomplished the steps in the test plan: * for jammy with language-selector-[common,gnome] 0.219.1 * for kinetic with language-selector-[common,gnome] 0.219.22.10.1 and can verify the expected improvement. (The kinetic verification was made on Xubuntu 22.10 where fonts-noto-core is installed by default for all users. The configuration tweak has the same effect on Xubuntu as on Ubuntu, though.) ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done 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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 1995247] Autopkgtest regression report (apt/2.4.9)
All autopkgtests for the newly accepted apt (2.4.9) for jammy have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.11-0ubuntu82.3 (armhf, arm64, amd64) 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/jammy/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1995247 Title: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Kinetic: Fix Committed Status in apt source package in Lunar: Fix Released Bug description: [Impact] When keys are embedded into deb822 sources files as Signed-By, apt writes them to a temporary file, but the code to delete them accidentally had an if (0) in front of the deletion, so they don't get deleted and accumulate with each `apt update` run. [Test plan] Including a test case for this in our comprehensive integration test suite which runs as autopkgtest, so passing autopkgtest = good. [Where problems could occur] Files could end up being removed too soon if the code is otherwise wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995247/+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
If the intent was to have apport-unpack deal with any invalid crash file, then
it's not complete. This still happens now:
ubuntu@k-apport:~$ apport-unpack /bin/ls unpack
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 174, in load
(key, value) = line.split(b":", 1)
ValueError: not enough values to unpack (expected 2, got 1)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 66, in
pr = load_report(args.report)
File "/usr/bin/apport-unpack", line 47, in load_report
pr.load(f, binary=False)
File "/usr/lib/python3/dist-packages/problem_report.py", line 177, in load
f"Malformed problem report: Line {line.decode()!r}"
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb0 in position 24:
invalid start byte
Is this something you would still like to address?
--
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:
New
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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Hello Aurora, or anyone else affected, Accepted language-selector into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/language- selector/0.219.22.10.1 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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: language-selector (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic ** Changed in: language-selector (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however
[Touch-packages] [Bug 2000551] Please test proposed package
Hello Aurora, or anyone else affected, Accepted language-selector into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/language- selector/0.219.1 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review
[Touch-packages] [Bug 853762] Re: Name of my native city is given in Russian transliteration
After several years this has been finally be fixed in tzdata 2022b where Europe/Kiev was renamed to Europe/Kyiv. ** Changed in: tzdata (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/853762 Title: Name of my native city is given in Russian transliteration Status in tzdata package in Ubuntu: Fix Released Bug description: During Ubuntu installation I can't choose Kyiv as location - only Kiev proposed. But it is not Ukrainian transliteration - this is Russian pronounce. Also "Kyiv" not in write checking dictionary - writing this message I see it marked as error. An example of proper name: http://www.kyivpost.ua/ Hope to see Kyiv in next release Also when I'm choosing city location on the map - Ubuntu identifies this location as Kiev. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 Date: Mon Sep 19 13:28:32 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/853762/+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 1457285] Re: Request for Russian Antarctic stations
Forwarded upstream: https://mm.icann.org/pipermail/tz/2023-January/032478.html ** Changed in: tzdata (Ubuntu) Importance: Undecided => Wishlist -- 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/1457285 Title: Request for Russian Antarctic stations Status in tzdata package in Ubuntu: New Bug description: Please add Russian Antarctic research stations to tzdata. They are: AQ -6212-05858 Antarctica/Bellingshausen Bellingshausen Station, Vaterloo Island, GMT-4 AQ -7046+01149 Antarctica/Novolasarevskaya Novolasarevskaya Station, GMT AQ -6739+04530 Antarctica/Molodezhnaya Molodezhnaya Station, GMT+3 AQ -6633+09300 Antarctica/Mirniy Mirniy Station, GMT+7 AQ -6930+15923 Antarctica/Leningradskaya Leningradskaya Station, GMT+10 AQ -7445-13648 Antarctica/Russkaya Russkaya Station, GMT-6 AQ -6922+07623 Antarctica/Progress Progress Station, GMT+5 AQ -6944+07342 Antarctica/Druzhnaya Druzhnaya Station, GMT+5 Please mean that GMT data given are POSIX inversed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1457285/+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 1731867] Re: davmail 4.8.0.2479 reports System tray not avaiable in thread SWT
So I am closing this bug as Invalid for tzdata. ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- 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/1731867 Title: davmail 4.8.0.2479 reports System tray not avaiable in thread SWT Status in tzdata package in Ubuntu: Invalid Bug description: In 17.10: Exception in thread "SWT" java.lang.Error: System tray not available at davmail.ui.tray.SwtGatewayTray$5.run(SwtGatewayTray.java:232) davmail_4.8.0.3-2488-1 seems to fix the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1731867/+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 1851438] Re: cloud-init disk_setup fails to partition disk for Ubuntu18
Fixed in https://github.com/canonical/cloud-init/pull/1932 ** Changed in: cloud-init Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1851438 Title: cloud-init disk_setup fails to partition disk for Ubuntu18 Status in cloud-init: Fix Committed Status in util-linux package in Ubuntu: New Status in util-linux source package in Xenial: New Status in util-linux source package in Bionic: New Status in util-linux source package in Eoan: New Status in util-linux source package in Focal: New Bug description: Pasting disk_setup for cloud-config: disk_setup: /dev/xvde: layout: True overwrite: False type: mbr fs_setup: -device: /dev/xvde filesystem: ext4 label: data overwrite: false partition: auto I want to attach and mount a /data disk on the VM using cloud-init so I just want to single partition 100% of the disk. Error while running the sfdisk command for partitioning the disk (please see attached file). OS: Ubuntu18 How I repro-ed it outside cloud-init environment: 1. Open XenCenter, add a new disk, say /dev/xvdc 2. Run `/sbin/sfdisk --Linux --unit=S --force /dev/xvdc` and specify start sector as 0. Because from the cloud-init logs and source code, I figured that it was picking start sector as 0. Save it and see the error. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1851438/+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 1731815] Re: Alphabetic time zone abbreviation not being returned for Asia/Bangkok
The change was intentional made upstream:
https://github.com/eggert/tz/commit/1b99dcde6342dd10969041b32b00b813d4f4a36e
("Remove many invented abbreviations in 'asia'"). The upstream
maintainer invented ICT:
https://github.com/eggert/tz/commit/1b99dcde6342dd10969041b32b00b813d4f4a36e#commitcomment-22025554
I am marking this bug as Won't Fix. If you want to get ICT back, this
needs to be done upstream on the t...@iana.org mailing list.
** Changed in: tzdata (Ubuntu)
Status: Triaged => Won't Fix
--
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/1731815
Title:
Alphabetic time zone abbreviation not being returned for Asia/Bangkok
Status in tzdata package in Ubuntu:
Won't Fix
Bug description:
Since upgrade "tzdata:amd64 (2016j-0ubuntu0.16.04,
2017c-0ubuntu0.16.04)"
Output of:
date +%Z
is:
"+07"
Expected value is:
"ICT"
Where:
"more /etc/timezone"
is:
"Asia/Bangkok"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1731815/+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 1731815] Re: Alphabetic time zone abbreviation not being returned for Asia/Bangkok
/usr/share/zoneinfo/tzdata.zi says: ``` Z Asia/Bangkok 6:42:4 - LMT 1880 6:42:4 - BMT 1920 Ap 7 - +07 ``` -- 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/1731815 Title: Alphabetic time zone abbreviation not being returned for Asia/Bangkok Status in tzdata package in Ubuntu: Won't Fix Bug description: Since upgrade "tzdata:amd64 (2016j-0ubuntu0.16.04, 2017c-0ubuntu0.16.04)" Output of: date +%Z is: "+07" Expected value is: "ICT" Where: "more /etc/timezone" is: "Asia/Bangkok" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1731815/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()
Sadly you cannot catch a C library segfault within Python code. -- 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/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value() Status in apport package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in apport source package in Focal: Triaged Status in gtk+3.0 source package in Focal: Confirmed Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Stack trace --- Python: ``` File "apport-gtk", line 703, in app = GTKUserInterface(sys.argv) File "apport-gtk", line 68, in GTKUserInterface.__init__ self.widgets.add_from_file( os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui") ) ``` StacktraceTop: _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319 gtk_css_value_icon_theme_compute (icon_theme=, property_id=, provider=, style=, parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84 gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, provider=provider@entry=0x0, style=style@entry=0x1e7c320, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1731815] Re: Alphabetic time zone abbreviation not being returned for Asia/Bangkok
Thank you for taking the time to report this bug and helping to make Ubuntu better. I can reproduce with tzdata 2022g-1ubuntu1 on the latest Ubuntu development release by running: TZ='Asia/Bangkok' date +%Z It returns "+07". ** Description changed: Since upgrade "tzdata:amd64 (2016j-0ubuntu0.16.04, 2017c-0ubuntu0.16.04)" Output of: - date %+Z + date +%Z is: "+07" Expected value is: "ICT" Where: "more /etc/timezone" is: "Asia/Bangkok" ** Changed in: tzdata (Ubuntu) Status: New => Confirmed ** Changed in: tzdata (Ubuntu) Status: Confirmed => Triaged -- 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/1731815 Title: Alphabetic time zone abbreviation not being returned for Asia/Bangkok Status in tzdata package in Ubuntu: Triaged Bug description: Since upgrade "tzdata:amd64 (2016j-0ubuntu0.16.04, 2017c-0ubuntu0.16.04)" Output of: date +%Z is: "+07" Expected value is: "ICT" Where: "more /etc/timezone" is: "Asia/Bangkok" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1731815/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()
@bdrung - Speaking to the desktop team they indicated apport should catch the error and work around the issue given that a gtk fix isn't forthcoming. -- 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/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value() Status in apport package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in apport source package in Focal: Triaged Status in gtk+3.0 source package in Focal: Confirmed Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Stack trace --- Python: ``` File "apport-gtk", line 703, in app = GTKUserInterface(sys.argv) File "apport-gtk", line 68, in GTKUserInterface.__init__ self.widgets.add_from_file( os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui") ) ``` StacktraceTop: _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319 gtk_css_value_icon_theme_compute (icon_theme=, property_id=, provider=, style=, parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84 gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, provider=provider@entry=0x0, style=style@entry=0x1e7c320, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1899343] Re: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC`
** Changed in: tzdata (Ubuntu) Status: Confirmed => Triaged -- 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/1899343 Title: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC` Status in tzdata package in Ubuntu: Triaged Bug description: When installed within the `ubuntu` Docker container, `tzdata` sets `etc/timezone` to `/UTC`, not `Etc/UTC`, which breaks applications that are reading `etc/timezone` and expecting a valid timezone name. I'm guess that this wasn't noticed, since technically `/usr/share/zoneinfo//UTC` (double slash) still works. Here is a Dockerfile that reproduces the issue: ```dockerfile FROM ubuntu RUN apt-get update && \ apt-get install -y tzdata ``` Here is the output of `docker build`: ``` test (master)$ docker build --no-cache -t tztest . Sending build context to Docker daemon 2.56kB Step 1/3 : FROM ubuntu ---> 9140108b62dc Step 2/3 : RUN apt-get update && apt install -y tzdata ---> Running in 03da406f73cb Get:1 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [75.9 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:6 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [1169 B] Get:7 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [626 kB] Get:8 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 kB] Get:9 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 kB] Get:10 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 MB] Get:11 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [406 kB] Get:12 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [745 kB] Get:14 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [832 kB] Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [88.7 kB] Get:16 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [21.6 kB] Get:17 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [4277 B] Fetched 16.2 MB in 4s (3919 kB/s) Reading package lists... WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: tzdata 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 293 kB of archives. After this operation, 4026 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 tzdata all 2020a-0ubuntu0.20.04 [293 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 293 kB in 1s (262 kB/s) Selecting previously unselected package tzdata. (Reading database ... 4121 files and directories currently installed.) Preparing to unpack .../tzdata_2020a-0ubuntu0.20.04_all.deb ... Unpacking tzdata (2020a-0ubuntu0.20.04) ... Setting up tzdata (2020a-0ubuntu0.20.04) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Configuring tzdata -- Please select the geographic area in which you live. Subsequent configuration questions will narrow this down by presenting a list of cities, representing the time zones in which they are located. 1. Africa 4. Australia 7. Atlantic 10. Pacific 13. Etc 2. America 5. Arctic 8. Europe11. SystemV 3. Antarctica 6. Asia 9. Indian12. US Geographic area: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111. Current default time zone: '/UTC' Local time is now: Sun Oct 11 11:35:33 UTC 2020. Universal Time is now: Sun Oct 11 11:35:33 UTC 2020. Run 'dpkg-reconfigure tzdata' if you wish to change it.
[Touch-packages] [Bug 1946623] Re: Asia/Novosibirsk zoneinfo file contains string 'Asia/Novosibirsk' instead of actual zone info
I just checked Ubuntu 18.04 with the latest tzdata 2022g-0ubuntu0.18.04 and the file is correct there: ``` (bionic)root@host:~# hd /usr/share/zoneinfo/Asia/Novosibirsk | head -n 3 54 5a 69 66 32 00 00 00 00 00 00 00 00 00 00 00 |TZif2...| 0010 00 00 00 00 00 00 00 0a 00 00 00 0a 00 00 00 00 || 0020 00 00 00 45 00 00 00 0a 00 00 00 10 80 00 00 00 |...E| ``` So I assume that it was fixed since your report. If you still experience this issue, please reopen this bug report to investigate further. ** Changed in: tzdata (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1946623 Title: Asia/Novosibirsk zoneinfo file contains string 'Asia/Novosibirsk' instead of actual zone info Status in tzdata package in Ubuntu: Fix Released Bug description: OS: Ubuntu 18.04.6 LTS tzdata package: 2021a-2ubuntu0.18.04 Problem: the packages updates file /usr/share/zoneinfo/Asia/Novosibirsk with 17-byte file containing string 'Asia/Novosibirsk', instead of actual zone info file. The above leads to multiple hard to handle issues with a number of installed software (e.g. PHP function mktime() begins to segfault without a reason). To fix that, I copy a valid file from 20.04.* distribution's latest tzdata. The above (mentioned file replacement) happens periodically without any visible logic in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1946623/+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 1899343] Re: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC`
Thank you for taking the time to report this bug and helping to make Ubuntu better. I can reproduce it with the provided dockerfile and command. The ubuntu Docker image currently points at 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/1899343 Title: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC` Status in tzdata package in Ubuntu: Triaged Bug description: When installed within the `ubuntu` Docker container, `tzdata` sets `etc/timezone` to `/UTC`, not `Etc/UTC`, which breaks applications that are reading `etc/timezone` and expecting a valid timezone name. I'm guess that this wasn't noticed, since technically `/usr/share/zoneinfo//UTC` (double slash) still works. Here is a Dockerfile that reproduces the issue: ```dockerfile FROM ubuntu RUN apt-get update && \ apt-get install -y tzdata ``` Here is the output of `docker build`: ``` test (master)$ docker build --no-cache -t tztest . Sending build context to Docker daemon 2.56kB Step 1/3 : FROM ubuntu ---> 9140108b62dc Step 2/3 : RUN apt-get update && apt install -y tzdata ---> Running in 03da406f73cb Get:1 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [75.9 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:6 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [1169 B] Get:7 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [626 kB] Get:8 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 kB] Get:9 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 kB] Get:10 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 MB] Get:11 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [406 kB] Get:12 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [745 kB] Get:14 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [832 kB] Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [88.7 kB] Get:16 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [21.6 kB] Get:17 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [4277 B] Fetched 16.2 MB in 4s (3919 kB/s) Reading package lists... WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: tzdata 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 293 kB of archives. After this operation, 4026 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 tzdata all 2020a-0ubuntu0.20.04 [293 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 293 kB in 1s (262 kB/s) Selecting previously unselected package tzdata. (Reading database ... 4121 files and directories currently installed.) Preparing to unpack .../tzdata_2020a-0ubuntu0.20.04_all.deb ... Unpacking tzdata (2020a-0ubuntu0.20.04) ... Setting up tzdata (2020a-0ubuntu0.20.04) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Configuring tzdata -- Please select the geographic area in which you live. Subsequent configuration questions will narrow this down by presenting a list of cities, representing the time zones in which they are located. 1. Africa 4. Australia 7. Atlantic 10. Pacific 13. Etc 2. America 5. Arctic 8. Europe11. SystemV 3. Antarctica 6. Asia 9. Indian12. US Geographic area: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111. Current default time zone: '/UTC' Local time is now: Sun Oct 11
[Touch-packages] [Bug 1971712] Re: Add support for Intel DG2
It seems like there is no more force-probe required for oem-6.1, works fine out-of-the-box now. When is the 22.2 mesa from ppa:canonical-x/x-staging going to be released, currently using the linux-oem-6.1 kernel together with the 23.0 mesa from the Intel Arc package sources. -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1911472] Re: ubuntu 16.04.7 timedatectl
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since the faulty tzdata version has been fixed, I am marking this bug as fixed. ** Changed in: tzdata (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1911472 Title: ubuntu 16.04.7 timedatectl Status in tzdata package in Ubuntu: Fix Released Bug description: Hello, after recent tzdata update in ubuntu 16.04.7 (Desktop), the "timedatectl" command shows this error: user@host:~$ timedatectl Assertion 'xstrftime: a[] must be big enough' failed at ../src/timedate/timedatectl.c:113, function print_status_info(). Aborting. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1911472/+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 1971712] Re: Add support for Intel DG2
oem-6.1 is now in jammy-proposed ** Package changed: linux-oem-6.0 (Ubuntu) => linux-oem-6.1 (Ubuntu) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 2001922] [NEW] Xorg crash
Public bug reported: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN dmi.product.version: ThinkBook 13s G3 ACN dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Ok, Robie, you win. :) I have uploaded to the kinetic unapproved queue too. Hopefully the version string (0.219.22.10.1) makes sense. ** Changed in: language-selector (Ubuntu Kinetic) Importance: Undecided => Wishlist ** Changed in: language-selector (Ubuntu Kinetic) Status: Won't Fix => In Progress ** Changed in: language-selector (Ubuntu Kinetic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Description changed: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] - * Install language-selector-[common,gnome] from jammy-proposed. + * Install language-selector-[common,gnome] from + [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the - improvement. (Also I (Gunnar), who don't speak Sinhala, - notice a remarkable difference.) + improvement. (Also I (Gunnar), who don't speak Sinhala, + notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: In Progress Status in language-selector source package in Kinetic: In Progress Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
For me
sudo apt remove libcanberra-gtk3-module
solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Thank you for the updates! It looks like you responded appropriately to all of my points, but I'd like to clarify one thing about version numbers and Kinetic. > If a user with an updated jammy (including this fix) upgrades to kinetic, they will still have version 0.219.1 of the language-selector-* packages, since the version string in kinetic is lower. So no regression. If you're not intending to fix Kinetic, then we'll need to use a different package version for Jammy. We generally avoid the version situation you describe, since that makes it difficult to reliably issue an update for users for the package in Kinetic. Consider if a security update were then required, for example. It would be possible to fix, but only if someone were to notice the unusual situation first. And it's confusing for Kinetic users to be on a different package version depending on whether or not they upgraded from Jammy or not. That situation means there are more combinations of interactions with other packages that might lead to different behaviours and different bugs. So we avoid it. Using a "compliant" version for the Jammy SRU, the original point about regressions on upgrade still stands, but see https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases for instructions and policy for this situation. It may still acceptable if you insist on not updating Kinetic. But we will want to adjust the version string for Jammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: In Progress Status in language-selector source package in Kinetic: Won't Fix Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from jammy-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2.
[Touch-packages] [Bug 2001890] Re: Network Manager cannot using the 'add' button for openvpn
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/2001890 Title: Network Manager cannot using the 'add' button for openvpn Status in network-manager package in Ubuntu: Confirmed Bug description: Hi everyone, This issue is related to network-manager with an openvpn connection on Ubuntu 22.10. I am using a openvpn connection with as connection type "Password with Certificate (TLS)". After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer able to save the TLS certificate password for my user only. If I select the "for my user only" option, I cannot save the profile (i.e. button is disabled). The only option I currently have is to never save the password, which does work. This issue only popped up after the upgrade to 22.10. Not touching the VPN connection makes network-manager ask for the password. Have a look at the screenshot below for further information. Any help would be appreciated. Thank you in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
Yeah kinetic doesn't have this bug so we can probably fix jammy via the backport without knowing which commits are most important. -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 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/mesa/+bug/1972977/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
or, just accept the current upload and revisit it again with the 22.2 backport if needed, but in any case I don't think this bug should block either one from getting into updates -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 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/mesa/+bug/1972977/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
but it is in 22.2.x which we need in proposed asap anyway, so I'll drop this from the current upload so that it can be fast-tracked through, as #1998893 is even more urgent. -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 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/mesa/+bug/1972977/+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 2001890] Re: Network Manager cannot using the 'add' button for openvpn
As you can see in the screenshot I am using the following settings and I cannot click the 'add' button. ** Attachment added: "Screenshot2.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+attachment/5639245/+files/Screenshot2.png ** Description changed: Hi everyone, - After upgrading my laptop to ubuntu 22.10 I cannot add an openvpn in the - network settings. + This issue is related to network-manager with an openvpn connection on + Ubuntu 22.10. + + I am using a openvpn connection with as connection type "Password with + Certificate (TLS)". + + After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer able to save the TLS certificate password + for my user only. + If I select the "for my user only" option, I cannot save the profile (i.e. button is disabled). + + The only option I currently have is to never save the password, which + does work. + + This issue only popped up after the upgrade to 22.10. Not touching the VPN connection makes network-manager ask for + the password. Have a look at the screenshot below for further information. + Any help would be appreciated. + Thank you in advance! -- 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/2001890 Title: Network Manager cannot using the 'add' button for openvpn Status in network-manager package in Ubuntu: New Bug description: Hi everyone, This issue is related to network-manager with an openvpn connection on Ubuntu 22.10. I am using a openvpn connection with as connection type "Password with Certificate (TLS)". After upgrading my laptop from ubuntu 22.04 to ubuntu 22.10, I am no longer able to save the TLS certificate password for my user only. If I select the "for my user only" option, I cannot save the profile (i.e. button is disabled). The only option I currently have is to never save the password, which does work. This issue only popped up after the upgrade to 22.10. Not touching the VPN connection makes network-manager ask for the password. Have a look at the screenshot below for further information. Any help would be appreciated. Thank you in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2001890/+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 2000798] Re: cannot connect to K380 bluetooth keyboard
That's generally possible, but unlikely, given that everything worked well for a couple of months and then suddenly stopped working altogether (rather than occasionally). -- 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/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)
Test re-triggered and passed, hints removed. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: apparmor (Ubuntu) Status: New => Fix Released ** Changed in: apparmor (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2000359 Title: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable) Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Kinetic: Invalid Bug description: Issue found on Kinetic 5.19 ARM64 systems, The ApparmorTestsuites.test_regression_testsuite in ubuntu_qrt_apparmor will fail with posix_ipc test: running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable It's a bit hard to find which one is failing, here is the test output of ApparmorTestsuites.test_regression_testsuite: == BEGIN OF TEST OUPTUT == running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309514 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309547 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309797 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309826 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309861 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309896 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309931 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount using mount rules ... running mult_mount running named_pipe running namespaces running net_raw running open running openat running pipe running pivot_root kernel does not support pivot_root domain transitions - skipping tests ... running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable running ptrace using ptrace v6 tests ... running pwrite running query_label running regex running rename running readdir running rw running socketpair running swap running sd_flags running setattr running symlink running syscall WARNING: syscall sysctl not supported by kernel headers, skipping tests ... running sysv_ipc Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ... running tcp running unix_fd_server running unix_socket_pathname xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw) xpass: AF_UNIX pathname socket (dgram); confined client w/
[Touch-packages] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
Tested jammy with crocus on an i5-4300U, both 22.0.5-0ubuntu0.1 and 22.0.5-0ubuntu0.2 gnome-shell's RSS grows but seems to plateau similarly with both. Based on upstream's comments, I started counting i915.gem instances in /proc/PID/smaps and found that both 22.0.5-0ubuntu0.1 and 22.0.5-0ubuntu0.2 seem to leak them equally. Never reached the point of crashing but the evidence is that mesa 22.0.5-0ubuntu0.2 makes gnome- shell leak almost as much as 22.0.5-0ubuntu0.1 ... That said, I expect most graphics leaks to be hardware independent and the fault of gnome- shell/mutter, not mesa. Looking at the upstream fix again I realize it's not fixing all the leaks that's important here, but avoiding crashes when they occur. And for that we are missing the correct patch: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17615/diffs It's not in mesa_22.0.5-0ubuntu0.2.diff.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-failed-jammy -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 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/mesa/+bug/1972977/+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
