[Touch-packages] [Bug 1999320] [NEW] Font alignment issue when using scaling factor > 1
Public bug reported: When I use a desktop interface text scaling factor of 1.5, the alignment text in the applications menu search bar is not set properly I have attached a screenshot showing the issue. 1) Description:Ubuntu 22.04.1 LTS Release:22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) text was centered 4) it is not centered ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-12-11 01-10-12.png" https://bugs.launchpad.net/bugs/1999320/+attachment/5635299/+files/Screenshot%20from%202022-12-11%2001-10-12.png -- 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/1999320 Title: Font alignment issue when using scaling factor > 1 Status in xorg package in Ubuntu: New Bug description: When I use a desktop interface text scaling factor of 1.5, the alignment text in the applications menu search bar is not set properly I have attached a screenshot showing the issue. 1) Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) text was centered 4) it is not centered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1999320/+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 1898207] Re: package logsave (not installed) failed to install/upgrade: no package named 'logsave' is installed, cannot configure
[Expired for e2fsprogs (Ubuntu) because there has been no activity for 60 days.] ** Changed in: e2fsprogs (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1898207 Title: package logsave (not installed) failed to install/upgrade: no package named 'logsave' is installed, cannot configure Status in e2fsprogs package in Ubuntu: Expired Bug description: updating crashes as suggested I did apt-get install -f now everything is working fine. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: logsave (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 2 12:45:08 2020 DpkgTerminalLog: dpkg: error processing package logsave (--configure): no package named 'logsave' is installed, cannot configure ErrorMessage: no package named 'logsave' is installed, cannot configure InstallationDate: Installed on 2016-02-08 (1697 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: e2fsprogs Title: package logsave (not installed) failed to install/upgrade: no package named 'logsave' is installed, cannot configure UpgradeStatus: Upgraded to focal on 2020-10-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1898207/+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 1992364] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1992364 Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Expired Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Oct 10 19:26:40 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992364/+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 1999207] Re: Error in dead key management of latin keyboards
I also tested on Xubuntu 22.10, which I happen to have access to. The reason is that I there (unlike on GNOME) can disable ibus completely. Using the Mozilla tool you linked to, and with ibus disabled, I get: compositionstart: compositionend: in the event log (even if the û character is shown as expected). Then I enabled ibus, and got this in the event log: compositionstart: compositionupdate: ^ compositionupdate: û compositionend: û So ibus is indeed involved somehow, but not (for me) in a way that results in an issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in ibus package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1999207/+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 1999207] Re: Error in dead key management of latin keyboards
Thanks for your report. I can't reproduce it, though. Whether the layout is "French (alt., Latin-9 only)" or "Swedish" I can type the dead_circumflex symbol followed by u, and get û. For me that works also with Firefox. Which physical keys are you using to type dead_circumflex? To access that symbol on "French (alt., Latin-9 only)" I need to hold + while pressing the key to the very right at the third row (to the left of the Return key). ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in ibus package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1999207/+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 1988418] Re: Please merge initramfs-tools 0.142 from Debian unstable.
This bug was fixed in the package initramfs-tools - 0.142ubuntu1 --- initramfs-tools (0.142ubuntu1) lunar; urgency=medium * Merge from Debian unstable (LP: #1988418). Remaining changes: - Make busybox-initramfs a real runtime dependency, fixing kernel install failures with cryptsetup - support mounting of loopback devices via loop*= parameters - Drop hooks/keymap, scripts/init-top/keymap, and associated code; console-setup takes care of this in Ubuntu. - Add a new 'fixrtc' script that tries to set the system clock forward based on the last mount time of the root disk; without this kludge, systems without a working RTC will end up in a perpetual reboot loop. - Trim leading whitespaces in dumpe2fs output so date command is happy in the fixrtc script - scripts/local-premount/fixrtc: ensure that the fixrtc script doesn't produce extraneous output from wait-for-root and date - Set hostname at boot, for the benefit of mdadm autoassembly. - Allow scripts and hooks to specify OPTION=VAR, and unless VAR is set to something other than "n", the script will not be included. - Restore the framebuffer hook and script, copying KMS and other framebuffer drivers into the initramfs, but make them optional; you need to set FRAMEBUFFER=y for these to be included. - Add hwaddr= alias for BOOTIF= for compatibility. - Automatically blacklist vga16fb when vga= or video= specified on kernel command-line. - add squashfs to list of 'most' modules - Add vfat and nls modules to the initramfs. - Add Hyper-V paravirtualised device drivers to the initramfs to allow booting of stock images in a Hyper-V guest. - ppc64el: enable PowerPC NX Crypto Coprocessor - Revised mountroot failure support. This is now deprecated and effectively removed. However, to prevent breakage in other packages the add_mountroot_fail_hook function is still present as an empty stub. - resume: only resume when the partition contains a resume image - Fix resuming a hibernate session from a swapfile - Add new initramfs-tools-bin package containing a binary that uses libudev to wait for udev to create the udev device, or wait for udev to finish processing if we catch it in the act, and returns the filesystem type as already probed by udev. - local_device_setup: use wait-for-root if it supports the device alias type - debian/control: update Vcs-* links for Ubuntu. - Add support for uppercase and lowercase uuids. - init: Don't interpret "rootdelay" as a static sleep. - src/wait-for-root.c, scripts/local: add explicit support for PARTUUID, a syntax we may prefer for images that might boot without an initramfs. - scripts/local: Let rootdelay determine the wait-for-root timeout. - Increase rootdelay to 180s on powerpc/ppc64/ppc64el - Support roottimeout= as the authoritative name for rootdelay= since the Ubuntu interpretation of rootdelay is *not* a delay and this causes inconsistent behavior depending on whether the kernel or an initramfs is interpreting it. - scripts/functions: by default, when setting up networking, use dhclient if we're asked to do DHCP explicitly, or if we otherwise are expected to do things automatically. - scripts/functions: make sure we can try to start all available and suitable interfaces if ip= isn't set when setting up the network, and exit as soon as we get an IP address. - split out IPv6 options in its own cmdline parameter: ip6= ; always use dhclient in this case if the value set is anything other than 'off' or 'none'. Furthermore, parse anything other than 'on', 'dhcp' or 'any' as the name of an interface. - rework the stop conditions so that we properly handle the ROUNDTTT loop, timing out after a short period of time and trying again after a short sleep. - add a 'done' parameter for both ip= and ip6= so that we can properly exit the ROUNDTTT loop once we know that either there is no work to do, or that we've achieved what we wanted (that is, to bring up IPv4, IPv6, or possibly both). - Just let dhclient scan the interfaces if none is specified for IPv6. (previously unnoted) - Do not handle ip=rarp specially (ipconfig hasn't supported it for some time) - Call dhclient in simple cases for IPv4 (this makes some small observable changes -- for example ip=bootp will now make a DHCP request too -- but nothing that seems important). - Do not let dhclient processes hang around past the pivot and have them respect the shorter timeouts ipconfig was given. - Only source ipv4 config in configure_networking() if it exists. - hook-functions, mkinitramfs, scripts/functions: support usage of dns after configure_networking. - Run unittests during
Re: [Touch-packages] [Bug 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
The bug reports stopped working all together, too. Sent with Proton Mail secure email. --- Original Message --- On Saturday, December 10th, 2022 at 4:59 PM, ke7in.dev wrote: > Yeah, I just removed 22.10. It was just far too unstable. I had a crash where > I couldn't do anything, not even shut my system down, it appeared to be a kde > issue. So I am now testing 22.04 on my desktop and mint 21 on my laptop. > > > > > Sent with Proton Mail secure email. > > > --- Original Message --- > On Monday, December 5th, 2022 at 1:19 PM, Benjamin Drung > 1998...@bugs.launchpad.net wrote: > > > > > If the upload was successful, you can find the oops UUID in > > "/var/crash/*.uploaded". After the Ubuntu release, bugs are reported > > only to the error tracker by default. See > > https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash_in_the_stable_release > > > > I tried to reproduce it a an Kubuntu 22.10 VM: > > > > 1. type 'ubuntu-bug' in konsole > > 2. click audio related > > 3. PolicyKit1-KDE-Agent pops up twice asking for the password. Hit OK or > > cancel > > 4. Problem report overview appears > > > > So that works as expected, but following causes a hang: > > > > 1. type 'ubuntu-bug' in konsole > > 2. click 'display (X.org)' related and then OK > > 3. On the next page, don't click "OK", click "Cancel" > > > > I retried these steps on GNOME and it works there without a hand. > > Therefore this hang is tied to apport-kde. I will update this bug report > > to just be about this apport-kde hand on cancel the display related > > report. If you find other issues with apport, do not hesistate to report > > new bug reports. > > > > ** Summary changed: > > > > - attempted to report a few of the bugs I'm experiencing using 22.10 (I'm > > using on 2 machines)...and the bug reporter crashed when I tried to exit / > > redo. > > + apport-kde hangs when canceling a display related report > > > > ** Description changed: > > > > - 1. Ubuntu 22.10 (studio install) > > + apport-kde hangs when canceling a display related report: > > > > - 2. 2.23.1-0ubuntu3 500 > > + 1. Log-in to a KDE session > > + 2. type 'ubuntu-bug' in konsole > > + 3. click 'display (X.org)' related and then OK > > + 4. On the next page, don't click "OK", click "Cancel" > > > > - 3. I was on generic bug selection screen and picked the "best fitting" > > - one (konsole popped up 1319), but realized there were no great options > > - and went to 'x' it out to dig a little more... > > - > > - 4. crash. > > + The windows will hang. See screenshot in comment 3. > > > > ProblemType: Bug > > DistroRelease: Ubuntu 22.10 > > Package: apport-kde 2.23.1-0ubuntu3 > > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > > Uname: Linux 5.19.0-1009-lowlatency x86_64 > > ApportVersion: 2.23.1-0ubuntu3 > > Architecture: amd64 > > CasperMD5CheckResult: unknown > > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > > -0500:2022-11-30 02:13:35.548841973 > > -0500:/var/crash/_usr_bin_avplayer.1000.crash > > CurrentDesktop: KDE > > Date: Wed Nov 30 03:11:50 2022 > > InstallationDate: Installed on 2022-11-29 (0 days ago) > > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > > (20221017.1) > > PackageArchitecture: all > > SourcePackage: apport > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > ** Changed in: apport (Ubuntu) > > Status: Incomplete => Triaged > > > > ** Description changed: > > > > apport-kde hangs when canceling a display related report: > > > > 1. Log-in to a KDE session > > 2. type 'ubuntu-bug' in konsole > > 3. click 'display (X.org)' related and then OK > > 4. On the next page, don't click "OK", click "Cancel" > > > > The windows will hang. See screenshot in comment 3. > > + > > + Workaround > > + == > > + > > + Kill apport-kde since you already clicked cancel which should just close > > + apport. > > > > ProblemType: Bug > > DistroRelease: Ubuntu 22.10 > > Package: apport-kde 2.23.1-0ubuntu3 > > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > > Uname: Linux 5.19.0-1009-lowlatency x86_64 > > ApportVersion: 2.23.1-0ubuntu3 > > Architecture: amd64 > > CasperMD5CheckResult: unknown > > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > > -0500:2022-11-30 02:13:35.548841973 > > -0500:/var/crash/_usr_bin_avplayer.1000.crash > > CurrentDesktop: KDE > > Date: Wed Nov 30 03:11:50 2022 > > InstallationDate: Installed on 2022-11-29 (0 days ago) > > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > > (20221017.1) > > PackageArchitecture: all > > SourcePackage: apport > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > ** Changed in: apport (Ubuntu) > > Importance: Undecided => Low > > > > ** Description changed: > > > > apport-kde hangs when canceling a display related report: > > > > 1. Log-in to a KDE session > > 2. type 'ubuntu-bug' in
Re: [Touch-packages] [Bug 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
Yeah, I just removed 22.10. It was just far too unstable. I had a crash where I couldn't do anything, not even shut my system down, it appeared to be a kde issue. So I am now testing 22.04 on my desktop and mint 21 on my laptop. Sent with Proton Mail secure email. --- Original Message --- On Monday, December 5th, 2022 at 1:19 PM, Benjamin Drung <1998...@bugs.launchpad.net> wrote: > If the upload was successful, you can find the oops UUID in > "/var/crash/*.uploaded". After the Ubuntu release, bugs are reported > only to the error tracker by default. See > https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash_in_the_stable_release > > I tried to reproduce it a an Kubuntu 22.10 VM: > > 1. type 'ubuntu-bug' in konsole > 2. click audio related > 3. PolicyKit1-KDE-Agent pops up twice asking for the password. Hit OK or > cancel > 4. Problem report overview appears > > So that works as expected, but following causes a hang: > > 1. type 'ubuntu-bug' in konsole > 2. click 'display (X.org)' related and then OK > 3. On the next page, don't click "OK", click "Cancel" > > I retried these steps on GNOME and it works there without a hand. > Therefore this hang is tied to apport-kde. I will update this bug report > to just be about this apport-kde hand on cancel the display related > report. If you find other issues with apport, do not hesistate to report > new bug reports. > > ** Summary changed: > > - attempted to report a few of the bugs I'm experiencing using 22.10 (I'm > using on 2 machines)...and the bug reporter crashed when I tried to exit / > redo. > + apport-kde hangs when canceling a display related report > > ** Description changed: > > - 1. Ubuntu 22.10 (studio install) > + apport-kde hangs when canceling a display related report: > > - 2. 2.23.1-0ubuntu3 500 > + 1. Log-in to a KDE session > + 2. type 'ubuntu-bug' in konsole > + 3. click 'display (X.org)' related and then OK > + 4. On the next page, don't click "OK", click "Cancel" > > - 3. I was on generic bug selection screen and picked the "best fitting" > - one (konsole popped up 1319), but realized there were no great options > - and went to 'x' it out to dig a little more... > - > - 4. crash. > + The windows will hang. See screenshot in comment 3. > > ProblemType: Bug > DistroRelease: Ubuntu 22.10 > Package: apport-kde 2.23.1-0ubuntu3 > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > Uname: Linux 5.19.0-1009-lowlatency x86_64 > ApportVersion: 2.23.1-0ubuntu3 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > -0500:2022-11-30 02:13:35.548841973 > -0500:/var/crash/_usr_bin_avplayer.1000.crash > CurrentDesktop: KDE > Date: Wed Nov 30 03:11:50 2022 > InstallationDate: Installed on 2022-11-29 (0 days ago) > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > (20221017.1) > PackageArchitecture: all > SourcePackage: apport > UpgradeStatus: No upgrade log present (probably fresh install) > > ** Changed in: apport (Ubuntu) > Status: Incomplete => Triaged > > > ** Description changed: > > apport-kde hangs when canceling a display related report: > > 1. Log-in to a KDE session > 2. type 'ubuntu-bug' in konsole > 3. click 'display (X.org)' related and then OK > 4. On the next page, don't click "OK", click "Cancel" > > The windows will hang. See screenshot in comment 3. > + > + Workaround > + == > + > + Kill apport-kde since you already clicked cancel which should just close > + apport. > > ProblemType: Bug > DistroRelease: Ubuntu 22.10 > Package: apport-kde 2.23.1-0ubuntu3 > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > Uname: Linux 5.19.0-1009-lowlatency x86_64 > ApportVersion: 2.23.1-0ubuntu3 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > -0500:2022-11-30 02:13:35.548841973 > -0500:/var/crash/_usr_bin_avplayer.1000.crash > CurrentDesktop: KDE > Date: Wed Nov 30 03:11:50 2022 > InstallationDate: Installed on 2022-11-29 (0 days ago) > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > (20221017.1) > PackageArchitecture: all > SourcePackage: apport > UpgradeStatus: No upgrade log present (probably fresh install) > > ** Changed in: apport (Ubuntu) > Importance: Undecided => Low > > > ** Description changed: > > apport-kde hangs when canceling a display related report: > > 1. Log-in to a KDE session > 2. type 'ubuntu-bug' in konsole > 3. click 'display (X.org)' related and then OK > 4. On the next page, don't click "OK", click "Cancel" > > The windows will hang. See screenshot in comment 3. > - > - Workaround > - == > - > - Kill apport-kde since you already clicked cancel which should just close > - apport. > > ProblemType: Bug > DistroRelease: Ubuntu 22.10 > Package: apport-kde 2.23.1-0ubuntu3 > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > Uname:
[Touch-packages] [Bug 1999171] Re: tparm dynamic variables broken
Dynamic variables are maintained as part of the currently opened terminal. As noted, if you want to open a bug against ncurses (rather than Ubuntu packaging), this won't get as much attention as the bug-ncurses mailing list, or the Debian package (which Ubuntu provides without change). ** Changed in: ncurses (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1999171 Title: tparm dynamic variables broken Status in ncurses package in Ubuntu: Invalid Bug description: I use the Python curses library for convenience, but this seems to be an ncurses bug as Python simply wraps the ncurses library. As you can see from example below, the dynamic variable x gets stored as 4, but, when it's recalled, 0 is returned instead of 4. This was on 22.04 and 20.04 with libncurses6 6.3-2. I've confirm the behavior is correct on Fedora 36 with ncurses- libs-6.2-9.20210508. I apologize I haven't been able to narrow it down farther, but figured it would be good to get a bug logged in case someone has more insight. ``` Python 3.10.6 (main, Nov 2 2022, 18:53:38) [GCC 11.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import curses >>> curses.setupterm() >>> curses.tparm(b'%p1%Px', 4) b'' >>> curses.tparm(b'%gx%d') b'0' ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1999171/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
** No longer affects: gnome-font-viewer (Ubuntu) ** No longer affects: fontforge (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: Fix Released Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1999171] Re: tparm dynamic variables broken
I was able to confirm this also fails on Fedora 37 with ncurses- libs-6.3-3.20220501, so this looks like a regression in 6.3 @dickey-his, it looks like there were several changes to tparm between 6.2 and 6.3. Is it possible this could have caused the issue? Static (uppercase) variables are working as expected, but dynamic (lowercase) variables don't seem to get set. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1999171 Title: tparm dynamic variables broken Status in ncurses package in Ubuntu: New Bug description: I use the Python curses library for convenience, but this seems to be an ncurses bug as Python simply wraps the ncurses library. As you can see from example below, the dynamic variable x gets stored as 4, but, when it's recalled, 0 is returned instead of 4. This was on 22.04 and 20.04 with libncurses6 6.3-2. I've confirm the behavior is correct on Fedora 36 with ncurses- libs-6.2-9.20210508. I apologize I haven't been able to narrow it down farther, but figured it would be good to get a bug logged in case someone has more insight. ``` Python 3.10.6 (main, Nov 2 2022, 18:53:38) [GCC 11.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import curses >>> curses.setupterm() >>> curses.tparm(b'%p1%Px', 4) b'' >>> curses.tparm(b'%gx%d') b'0' ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1999171/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
This bug was fixed in the package fonts-dejavu - 2.37-2build2 --- fonts-dejavu (2.37-2build2) lunar; urgency=medium * No-change rebuild with newer fontforge to fix LP: #1992369. -- Steve Langasek Thu, 08 Dec 2022 16:23:21 + ** Changed in: fonts-dejavu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Fix Released Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+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] Re: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources
This bug was fixed in the package apt - 2.5.4 --- apt (2.5.4) unstable; urgency=medium [ David Kalnischkies ] * Report failures back from debSystem::AddStatusFiles * Avoid dealing with a fake dpkg stanza in the tests * Allow apt to run if no dpkg/status file exists [ Johannes Schauer Marin Rodrigues ] * since base-passwd 3.6.1 the _apt user is in the default /etc/passwd [ Boyuan Yang ] * po/zh_CN.po: Update translation for apt/2.5.3 [ quazgar ] * Documentation for autopurge command [ Julian Andres Klode ] * Actually delete temporary apt-key.*.asc helper files (LP: #1995247) -- Julian Andres Klode Mon, 31 Oct 2022 12:11:04 +0100 ** Changed in: apt (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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: In Progress 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 1999220] Re: libQt5Core.so.5 incompatible with older kernels (<3.15)
Ubuntu 22.04 (jammy), the current LTS release, has kernel 5.15. Ubuntu 20.04 (focal), the previous LTS release, has kernel 5.4. Ubuntu 18.04 (bionic) has kernel 4.15. Ubuntu 16.04 (xenial) has kernel 4.4. The version of libQt5Core.so.5 in jammy requires kernel 3.17. This kernel is present in all mentioned releases. I think it's a reasonable requirement, we cannot support ancient kernels forever. This requirement is needed for getrandom feature. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1999220 Title: libQt5Core.so.5 incompatible with older kernels (<3.15) Status in qtbase-opensource-src package in Ubuntu: Won't Fix Bug description: When running programs that use libQt5Core.so.5 on pre-3.15 kernels (e.g. from a container) one gets error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory A workaround (from https://github.com/dnschneid/crouton/wiki/Fix- error-while-loading-shared-libraries:-libQt5Core.so.5): sudo strip --remove-section=.note.ABI-tag /usr/lib64/libQt5Core.so.5 At least 20.04 and 22.04 are affected. I guess, something can be changed in the way the library compiles to make it more portable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1999220/+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 1991919] Re: libgoogle-glog-dev has unmet dependencies due to libunwind
Looks like the libunwind-dev and libunwind-14-dev indeed conflict with each other. This in turn affect other packages if you try to install them with one or the other dev library already in place. Might be a duplicate of bug 1989124. ** Also affects: libunwind (Ubuntu) Importance: Undecided Status: New ** Changed in: libunwind (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1991919 Title: libgoogle-glog-dev has unmet dependencies due to libunwind Status in google-glog package in Ubuntu: Confirmed Status in libunwind package in Ubuntu: Confirmed Bug description: # Error Description Installing `libgoogle-glog-dev` results in an error: ``` $ sudo apt install libgoogle-glog-dev Reading package lists... Done Building dependency tree... Done Reading state information... 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: libunwind-14-dev : Breaks: libunwind-dev but 1.3.2-2build2 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ``` # Comments I have the packages libc++-14-dev and libc++-dev installed. The package libgoogle-glog-dev dependes on "libunwind-dev | libunwind7-dev". But Package 'libunwind7-dev' has no installation candidate. Package 'libunwind-dev' is incompatible with libc++-14-dev and libc++-dev: ``` $ sudo apt install libunwind-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libc++-14-dev libc++-dev libunwind-14-dev The following NEW packages will be installed: libunwind-dev 0 upgraded, 1 newly installed, 3 to remove and 14 not upgraded. Need to get 0 B/1.882 kB of archives. After this operation, 3.176 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. ``` # Additional information: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ apt-cache policy libgoogle-glog-dev libgoogle-glog-dev: Installed: (none) Candidate: 0.5.0+really0.4.0-2 Version table: 0.5.0+really0.4.0-2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages $ apt show libgoogle-glog-dev Package: libgoogle-glog-dev Version: 0.5.0+really0.4.0-2 Priority: optional Section: universe/libdevel Source: google-glog Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Laszlo Boszormenyi (GCS) Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 388 kB Depends: libgoogle-glog0v5 (= 0.5.0+really0.4.0-2), libgflags-dev, libunwind-dev | libunwind7-dev Homepage: https://github.com/google/glog Download-Size: 91,9 kB APT-Sources: http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Description: library that implements application-level logging. This library provides logging APIs based on C++-style streams and various helper macros. . This package contains static and debug libraries and header files for developing applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-glog/+bug/1991919/+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
