[Touch-packages] [Bug 1800836] Re: systemd-networkd doesn't process IPv6 RA properly
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1800836 Title: systemd-networkd doesn't process IPv6 RA properly Status in systemd package in Ubuntu: Expired Bug description: The gateways/firewalls in our DC are highly available and when there is a failover their IPv6 VIP (fe80::1) moves from the master to the backup one. We found that only our Bionic VMs behind those gateways had issues after a failover. Those Bionic VMs were all running systemd-networkd (from netplan) and before the failover they had: $ ip -6 route ... default via fe80::1 dev eth0 proto ra metric 1024 pref medium But after a failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 And after another failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1 This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as their default gateway even when this gateway is unavailable: $ ip -6 route get :: :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src fe80::a800:ff:fe51:8c37 metric 1024 pref medium We concluded it was a systemd-networkd bug after checking that the following combinations were NOT affected: 1) Xenial+4.4 kernel 2) Xenial+4.15 kernel 3) Bionic+ifupdown Additional information: $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 08:47:28 2018 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=43b7ee2e-2ab1-4505-8e0b-d9fe0563a034 ro console=ttyS0 net.ifnames=0 vsyscall=none kaslr nmi_watchdog=0 possible_cpus=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800836/+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 1854195] Re: pc wont resolve any names until /etc/resolv.conf is edited by hand
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1854195 Title: pc wont resolve any names until /etc/resolv.conf is edited by hand Status in systemd package in Ubuntu: Expired Bug description: In /etc/systemd/resolved.conf I've entered the nameserver to use: [Resolve] DNS=172.18.8.1 #FallbackDNS= Domains=fritz.box #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes In /etc/resolv.conf after rebooting: nameserver 127.0.0.53 options edns0 search fritz.box No names from anywhere are solved. This systemd-resolver just does nothing. It does not even forward any request to 172.18.8.1! As soon as I edit /etc/resolv.conf, replacing 127.0.0.53 with 172.18.8.1 it starts to work as it is expected to. Looks like systemd- resolved is broken by design. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 27 19:16:22 2019 InstallationDate: Installed on 2019-09-09 (79 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-23-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. mtime.conffile..etc.systemd.resolved.conf: 2019-09-24T10:52:27.095603 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1854195/+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 1852903] Re: systemd Caught , dumped core
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1852903 Title: systemd Caught , dumped core Status in systemd package in Ubuntu: Expired Bug description: Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 237-3ubuntu10.31 This caused systemd to segfault and stop receiving any systemctl command (they timeout). [ 198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 7ffc9c3ea890 error 4 in systemd (deleted)[5630ddcc1000+14e000] [ 278.664729] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Connection refused [ 368.462136] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 458.496689] systemd-journald[451]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected I downgraded to 237-3ubuntu10.29 to no avail. Then I downgraded to 237-3ubuntu10: apt install udev=237-3ubuntu10 systemd=237-3ubuntu10 systemd-sysv=237-3ubuntu10 libsystemd0:amd64=237-3ubuntu10 libudev1:amd64=237-3ubuntu10 libnss-systemd:amd64=237-3ubuntu10 and that did not help either. The machine is unusable at the moment. Attaching coredump of systemd (version 237-3ubuntu10.31) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+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 1861594] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1861594 Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt Status in avahi package in Ubuntu: New Bug description: New to ubuntu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-76.86~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Sat Feb 1 19:06:33 2020 ErrorMessage: end of file on stdin at conffile prompt RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: avahi Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to xenial on 2020-01-27 (5 days ago) modified.conffile..etc.avahi.hosts: [modified] modified.conffile..etc.dbus-1.system.d.avahi-dbus.conf: [modified] modified.conffile..etc.default.avahi-daemon: [modified] modified.conffile..etc.init.avahi-daemon.conf: [modified] modified.conffile..etc.init.d.avahi-daemon: [modified] modified.conffile..etc.network.if-up.d.avahi-daemon: [modified] mtime.conffile..etc.avahi.avahi-daemon.conf: 2015-11-24T16:30:19 mtime.conffile..etc.avahi.hosts: 2015-11-24T16:30:19 mtime.conffile..etc.dbus-1.system.d.avahi-dbus.conf: 2015-11-24T16:30:19 mtime.conffile..etc.default.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.init.avahi-cups-reload.conf: 2015-11-24T14:01:36 mtime.conffile..etc.init.avahi-daemon.conf: 2015-11-24T14:01:36 mtime.conffile..etc.init.d.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.network.if-up.d.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.resolvconf.update-libc.d.avahi-daemon: 2015-11-24T16:30:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1861594/+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 1861594] [NEW] package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: New to ubuntu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-76.86~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Sat Feb 1 19:06:33 2020 ErrorMessage: end of file on stdin at conffile prompt RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: avahi Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to xenial on 2020-01-27 (5 days ago) modified.conffile..etc.avahi.hosts: [modified] modified.conffile..etc.dbus-1.system.d.avahi-dbus.conf: [modified] modified.conffile..etc.default.avahi-daemon: [modified] modified.conffile..etc.init.avahi-daemon.conf: [modified] modified.conffile..etc.init.d.avahi-daemon: [modified] modified.conffile..etc.network.if-up.d.avahi-daemon: [modified] mtime.conffile..etc.avahi.avahi-daemon.conf: 2015-11-24T16:30:19 mtime.conffile..etc.avahi.hosts: 2015-11-24T16:30:19 mtime.conffile..etc.dbus-1.system.d.avahi-dbus.conf: 2015-11-24T16:30:19 mtime.conffile..etc.default.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.init.avahi-cups-reload.conf: 2015-11-24T14:01:36 mtime.conffile..etc.init.avahi-daemon.conf: 2015-11-24T14:01:36 mtime.conffile..etc.init.d.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.network.if-up.d.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.resolvconf.update-libc.d.avahi-daemon: 2015-11-24T16:30:22 ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1861594 Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt Status in avahi package in Ubuntu: New Bug description: New to ubuntu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-76.86~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Sat Feb 1 19:06:33 2020 ErrorMessage: end of file on stdin at conffile prompt RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: avahi Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to xenial on 2020-01-27 (5 days ago) modified.conffile..etc.avahi.hosts: [modified] modified.conffile..etc.dbus-1.system.d.avahi-dbus.conf: [modified] modified.conffile..etc.default.avahi-daemon: [modified] modified.conffile..etc.init.avahi-daemon.conf: [modified] modified.conffile..etc.init.d.avahi-daemon: [modified] modified.conffile..etc.network.if-up.d.avahi-daemon: [modified] mtime.conffile..etc.avahi.avahi-daemon.conf: 2015-11-24T16:30:19 mtime.conffile..etc.avahi.hosts: 2015-11-24T16:30:19 mtime.conffile..etc.dbus-1.system.d.avahi-dbus.conf: 2015-11-24T16:30:19 mtime.conffile..etc.default.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.init.avahi-cups-reload.conf: 2015-11-24T14:01:36 mtime.conffile..etc.init.avahi-daemon.conf: 2015-11-24T14:01:36 mtime.conffile..etc.init.d.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.network.if-up.d.avahi-daemon: 2015-11-05T02:33:19 mtime.conffile..etc.resolvconf.update-libc.d.avahi-daemon: 2015-11-24T16:30:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1861594/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
** Changed in: openssl (Ubuntu Cosmic) Status: Fix Committed => Won't Fix ** Tags removed: libssl1.1 verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Released Status in openssl source package in Cosmic: Won't Fix Status in openssl source package in Disco: Fix Released Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * Systems that have in error removed debconf database fail to upgrade libssl1.1 (as e.g. is known to be done in some vagrant boxes) * libssl1.1 tries to use debconf template from libc6 package, but doesn't ship one by itself as it should for shared templates. As it is not guaranteed that template will be available. [TestCase] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 Then upgrade from bionic-release to the -proposed package and it should work. It should not fail with exit code 10. [Regression Potential] * A new template is added, an identical import from glibc without any further changes. This registers the template in debconf, for this package, preventing the above describe error. This has no codechanges, only metadata. [Other Info] * Original bug report The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 [ WORKAROUND TO RECOVER YOUR SYSTEM ] $ sudo dpkg-reconfigure libc6 $ sudo dpkg --configure libssl1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1832421] Re: openssl reboot needed message using incorrect path to X server
** Changed in: openssl (Ubuntu Cosmic) Status: Fix Committed => Won't Fix ** Tags removed: removal-candidate verification-needed verification- needed-cosmic verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832421 Title: openssl reboot needed message using incorrect path to X server Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Released Status in openssl source package in Cosmic: Won't Fix Status in openssl source package in Disco: Fix Released Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * On desktop, upgrading libssl1.1 does not show reboot required notification [Test Case] * Boot ubuntu desktop * Upgrade libssl1.1 * Observe reboot notification pop-up from update-notifier is _not_ shown [Regression Potential] * Tweaking postinst only to correct for the Xorg path. Current code is innert, but is well excercised in prior releases. [Other Info] * Original bug report: Hello, the openssl library postinst file is using pidof /usr/bin/X, but that doesn't appear to be the path to the X11 server any more: debian/libssl1.1.postinst: # Only issue the reboot notification for servers; we proxy this by # testing that the X server is not running (LP: #244250) if ! pidof /usr/bin/X > /dev/null && [ -x /usr/share/update-notifier/notify-reboot-required ]; then /usr/share/update-notifier/notify-reboot-required fi On my 18.04 LTS laptop: $ ps auxw | grep Xorg root 2440 0.5 0.4 495932 78996 tty7 Rsl+ May10 264:45 /usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/l Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Jun 11 18:06:51 2019 InstallationDate: Installed on 2012-10-18 (2427 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to bionic on 2018-05-02 (406 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832421/+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 1828215] Re: openssl ca -spkac output regressed
** Changed in: openssl (Ubuntu Cosmic) Status: Fix Committed => Won't Fix ** Tags removed: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1828215 Title: openssl ca -spkac output regressed Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Released Status in openssl source package in Cosmic: Won't Fix Status in openssl source package in Disco: Fix Released Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * openssl command line utility option parsing has regressed in 1.1.0i+ and produces binary output, where text output is expected, breaking applications that parse that. [Test Case] Setup CA: $ apt install openssl $ mkdir -p demoCA/private demoCA/newcerts $ touch demoCA/index.txt $ echo 01 > demoCA/serial $ openssl req -new -x509 -days 365 -newkey rsa:4096 -keyout demoCA/private/cakey.pem -out demoCA/cacert.pem # Use password test # Accept defaults for all other settings $ openssl req -new -days 365 -newkey rsa:4096 -keyout demoCA/sslkey.pem -out demoCA/sslcert.pem Generate regular request / key: # Use password test # Set common name to: example.com # Accept defaults for all other settings Generate spkac request: $ openssl spkac -key demoCA/sslkey.pem -out demoCA/sslcert.spkac $ cat <>demoCA/sslcert.spkac countryName=AU stateOrProvinceName=Some-State organizationName=Internet Widgits Pty Ltd commonName=example.com EOF Sign spkac request: $ echo test | openssl ca -passin stdin -batch -spkac demoCA/sslcert.spkac -startdate 190121130654Z Expected: pure text output Unexpected: binary output for the signed cert Currently produces binary goop. Should produce PEM format Base64 encoded certificate data in a block surrounded with BEGIN/END certificate. [Regression Potential] * This is a regression in cosmic and up, and impeding regression in bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream. [Other Info] * Originally reported https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1828215/+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 1832522] Re: openssl maintainer scripts do not trigger services restart
** Changed in: openssl (Ubuntu Cosmic) Status: Fix Committed => Won't Fix ** Tags removed: removal-candidate verification-needed verification- needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832522 Title: openssl maintainer scripts do not trigger services restart Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Released Status in openssl source package in Cosmic: Won't Fix Status in openssl source package in Disco: Fix Released Bug description: [Impact] * Major libssl ugprades require services to be restarted, for them to continue to function correctly at runtime. * The maintainer scripts were not adjusted to trigger. [Test Case] * Install bionic from release pocket and install ssl using daemon e.g. openssh-server libapache-mod-ssl * Upgrade libssl1.1 * Ensure that services that use openssl are offered to be restarted. [Regression Potential] * We are rebuilding libssl1.1 and changing maintainer scripts. Given that we have missed upgrade trigger, we will ask users to restart services again even if they may have restarted them already. [Other Info] * Previous major libssl upgrade issue of similar nature was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743889 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832522/+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 1832659] Re: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350
** Changed in: openssl (Ubuntu Cosmic) Status: Fix Committed => Won't Fix ** Tags removed: verification-done verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832659 Title: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350 Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Released Status in openssl source package in Cosmic: Won't Fix Status in openssl source package in Disco: Fix Released Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * Regression was introduced in OpenSSL 1.1.1 and fixed in 1.1.1b that prevents initialising libcrypto/libssl multiple times, and/or with different options. * This breaks existing applications that correctly use init API, ie. initialise libcrypto before/separately from libssl and/or with different options. [Test Case] * wget https://bugs.launchpad.net/ubuntu/cosmic/+source/openssl/+bug/1832659/+attachment/5270802/+files/test_multiple_libssl_libcrypto_init.py * python3 ./test_multiple_libssl_libcrypto_init.py test_multiple_init (__main__.TestMultipleInit) ... ok -- Ran 1 test in 0.014s OK [Regression Potential] * This is a cherrypick from upstream, and is backwards compatible with existing code. Simply init succeeds under more conditions now, than it did previously in 1.1.1. Also with this fix, OpenSSL is back to how things used to work with 1.1.0 and prior releases. [Original Bug report] After the update of openssl in bionic, I started having an issue and after troubleshooting found this issue: https://github.com/openssl/openssl/issues/7350 Applying the patch linked in that issue and rebuilding the openssl package avoided the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssl 1.1.1-1ubuntu2.1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Thu Jun 13 00:21:16 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1832659/+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 1773859] Re: upgrades to 18.04 fail
Just did an do-release-upgrade from 16.04 to 18.04 and ran into this issue as well. The following fixed it like mentioned above. sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak sudo apt-get install -f sudo apt dist-upgrade sudo apt autoremove -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1858092] Re: Network Manager not saving OpenVPN password
** Tags removed: kwallet manager network openvpn ** Tags added: regression-release -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1780996] Re: Convert triggers to noawait
** Changed in: clutter-imcontext (Ubuntu) Status: Triaged => Won't Fix ** Changed in: libomxil-bellagio (Ubuntu) Status: Triaged => Won't Fix ** Changed in: libomxil-bellagio (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: libomxil-bellagio (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: maxima (Ubuntu Xenial) Status: Fix Committed => Won't Fix ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Won't Fix Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Fix Released Status in guile-2.2 package in Ubuntu: Fix Released Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Won't Fix Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Released Status in bumblebee source package in Xenial: Fix Released Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: Fix Released Status in dochelp source package in Xenial: Fix Released Status in dovecot source package in Xenial: Fix Released Status in fusiondirectory source package in Xenial: Fix Released Status in gdk-pixbuf source package in Xenial: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Fix Released Status in hicolor-icon-theme source package in Xenial: Fix Released Status in libomxil-bellagio source package in Xenial: Won't Fix Status in libreoffice source package in Xenial: Fix Released Status in ltsp source package in Xenial: Fix Released Status in mate-icon-theme source package in Xenial: Fix Released Status in maxima source package in Xenial: Won't Fix Status in neurodebian source package in Xenial: Fix Released Status in nevow source package in Xenial: Fix Released Status in octave source package in Xenial: Fix Released Status in packagekit source package in Xenial: Fix Released Status in pike7.8 source package in Xenial: Fix Released Status in pike8.0 source package in Xenial: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in qgis source package in Xenial: Fix Released Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Released Status in sphinx source package in Xenial: Fix Released Status in syslog-ng-incubator source package in Xenial: Fix Released Status in tex-common source package in Xenial: Fix Released Status in wokkel source package in Xenial: Fix Released Status in xpdf source package in Xenial: Fix Released Status in yorick source package in Xenial: Fix Released Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in
[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
** Bug watch removed: github.com/systemd/systemd/issues #14567 https://github.com/systemd/systemd/issues/14567 -- 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/1762391 Title: pam_group.so is not evaluated by gnome-terminal Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: Fix Released Bug description: [Impact] pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that processes were never getting group membership they were expected to get via pam_group module. [Test Case] * Add a /etc/security/group.conf entry, e.g. *;*;*;Al-2400;dialout,users * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus). Expected result: Logged in user is a member of 'dialout' and 'users' groups. Actual result: no group membership gained from pam_group. [Regression Potential] * It introduces a new PAM warning message in some scenarios (e.g. for systemd DynamicUser=1 units) for users that can't authenticate (pam_setcred fails in such case). * In certain systems user group membership may be extended by pam_group. [Other Info] Original bug description: We are using Ubuntu in a university network with lots of ldap users. To automatically map ldap users/groups to local groups we are using pam_group.so. This has worked for years. With the upgrade from Xenial to Bionic /etc/security/group.conf is not evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm, ssh, su, and tty* however do work as expected. Only the default gnome-terminal behaves different. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might not be a bug, but a feature. Nevertheless this behavior is very unexpected when upgrading from Xenial to Bionic and therefore should at least added to the changelog. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 13:17:52 2018 InstallationDate: Installed on 2018-03-29 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
** Changed in: pango Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) Status in Pango: Fix Released Status in pango1.0 package in Ubuntu: Triaged Bug description: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) gnome-font-viewer does not list any of the installed bitmap fonts. While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1861340/+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 1848865] Re: Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8
Sorry for the delay. This has fallen through the crack. I've, in fact, reduced the testing environment down to just X, twm, and xterm and the bug is still reproducible. Also, I've tested it on Fedora 31 XFCE spin, and cannot reproduce it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1848865 Title: Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8 Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: New Bug description: GTK+3 will emit spurious "key_press_event" if the focus is currently on "GtkEntry" and the locale is set to th_TH.UTF-8. This issue seems to disappear if the locale is set to something else (tested with C.UTF-8 and en_US.UTF-8), and the presence of iBus and gnome-shell affects this. Step to reproduce: 1. Boot into Xubuntu. Install package "language-pack-th" (for locale) and "libgtk-3-dev" for compiling demo program. 2. Download & compile the demo program "gtk3-entry-keyboard-event" attached in this bug. (The program is licensed under MIT.) 3. Run the program with LANG=th_TH.UTF-8. The window will contain an input box on top and a button on the bottom. 4. Click in the input box, then press a key on the keyboard. The program will print one line for each "key_press_event" delivered to the window, with keyval and hardware_keycode. Expected result: only a single line is printed. For example for "a": "window: 0x0061 0x0026" Actual result: - With LANG=th_TH.UTF-8, two lines are printed. The first line is the above line, while the second line has both values as zero: "window: 00 00" - If, instead, the locale is LANG=C.UTF-8, the program will print only one line as expected. - If iBus is installed and enabled, then 2 lines are printed with both lines containing the same code, no matter which locale it runs under. - If this same program is run in Gnome-based Ubuntu session, then only one line is printed no matter which locale it runs under. This program is tested on Fedora and Manjaro with the correct result. Thus, this issue is Ubuntu-specific. I've tested it on Ubuntu 19.10 with pretty much the same result, except the iBus case is now working correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk-3-0 3.22.30-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 19 18:06:23 2019 InstallationDate: Installed on 2018-05-03 (533 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1848865/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
Indeed, that's an upstream pango decision to drop support for bitmap fonts ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => Low ** Changed in: pango1.0 (Ubuntu) Status: New => Confirmed ** Changed in: pango1.0 (Ubuntu) Status: Confirmed => Triaged ** Also affects: pango via https://gitlab.gnome.org/GNOME/pango/issues/386 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) Status in Pango: Unknown Status in pango1.0 package in Ubuntu: Triaged Bug description: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) gnome-font-viewer does not list any of the installed bitmap fonts. While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1861340/+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 1861528] Re: screen corruption/UI glitching
Thank you for your bug report. What video driver do you use? Could you include a screenshot showing the issue and a 'journalctl -b 0' log of the system after triggering the issue? ** Changed in: xorg (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/1861528 Title: screen corruption/UI glitching Status in xorg package in Ubuntu: Incomplete Bug description: The user interface in ubuntu 19.10-20.04 is having glitches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.438 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 19:48:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: HP-Pavilion KE568AA-ABA m8357c ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.04 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd12/12/2007:svnHP-Pavilion:pnKE568AA-ABAm8357c:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KE568AA-ABA m8357c dmi.product.sku: KE568AA#ABA dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1861528/+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 1861532] Re: brightness control not working
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-435 (Ubuntu) -- 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/1861532 Title: brightness control not working Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: after selecting nvidia-driver-435 in livepatch- additional drivers the brightness control stops working after the first reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 22:00:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ffc] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=084301b5-fdae-4c92-811e-0536a3b7555b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-17IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81Q4:pvrLegionY540-17IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLegionY540-17IRH: dmi.product.family: Legion Y540-17IRH dmi.product.name: 81Q4 dmi.product.sku: LENOVO_MT_81Q4_BU_idea_FM_Legion Y540-17IRH dmi.product.version: Legion Y540-17IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1861532/+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 1861540] Re: typo in man page
Thank you for your bug report. Closing the bug since it's fixed in the current release. A bionic targetted task could be opened if we believe it's worth a SRU but it sounds rather a low importance/priority issue ** Changed in: netcat-openbsd (Ubuntu) Importance: Undecided => Low ** Changed in: netcat-openbsd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1861540 Title: typo in man page Status in netcat-openbsd package in Ubuntu: Fix Released Bug description: "respectively" is wrongly spelled: -l Used to specify that nc should listen for an incoming connection rather than initiate a connection to a remote host. The destination and port to listen on can be specified either as non- optional arguments, or with options -s and -p *respctively*. This is corrected on 19.10 onwards at least; but given this is on an LTS release, opening the bug. Found and reported by "sabrina" via email. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: netcat-openbsd 1.187-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Feb 1 01:07:19 2020 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libbsd0 0.8.7-1ubuntu0.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 SourcePackage: netcat-openbsd UpgradeStatus: Upgraded to bionic on 2018-07-28 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1861540/+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 1861558] [NEW] Snap 'ed applicaitons have garbage on top of the window Close [x] button
Public bug reported: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: adwaita-icon-theme (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-themes-extra (Ubuntu) Importance: Undecided Status: New ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-mono (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "GNOME Calculator with garbage on top of the window Close [x] button" https://bugs.launchpad.net/bugs/1861558/+attachment/5324652/+files/snapped-gnome-calculator_bad_close_button.png ** Also affects: adwaita-icon-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-themes-extra (Ubuntu) Importance: Undecided Status: New ** Also affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mono (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: New Status in gnome-themes-extra package in Ubuntu: New Status in humanity-icon-theme package in Ubuntu: New Status in snapd package in Ubuntu: New Status in ubuntu-mono package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color
[Touch-packages] [Bug 1861556] Re: g-ir-scanner doesn't work
Upgrading python3-minimal to 3.8.0-3 which has been stuck in proposed fixes this issue, but gobject-introspection doesn't reflect a relationship upon this. # apt show gobject-introspection |grep Dep Depends: libc6 (>= 2.29), libffi7 (>= 3.3~20180313), libgirepository-1.0-1 (= 1.62.0-4ubuntu1), libglib2.0-0 (>= 2.58.0), python3:any, build-essential, python3-distutils, python3-mako, python3-markdown ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1861556 Title: g-ir-scanner doesn't work Status in gobject-introspection package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: Running g-ir-scanner doesn't work anymore after a recent upgrade with a fully up to date focal: Traceback (most recent call last): File "/usr/bin/g-ir-scanner", line 99, in from giscanner.scannermain import scanner_main File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/scannermain.py", line 35, in from giscanner.ast import Include, Namespace File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/ast.py", line 29, in from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/sourcescanner.py", line 33, in from giscanner._giscanner import SourceScanner as CSourceScanner ModuleNotFoundError: No module named 'giscanner._giscanner' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gobject-introspection 1.62.0-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 07:04:11 2020 InstallationDate: Installed on 2019-08-13 (171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gobject-introspection UpgradeStatus: Upgraded to focal on 2019-11-04 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1861556/+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 1861556] Re: g-ir-scanner doesn't work
It appears to me to be happening because gobject-introspection only ships a python file for python3.8 not python3.7 which is the default in focal. $ python3.7 /usr/bin/g-ir-scanner Traceback (most recent call last): File "/usr/bin/g-ir-scanner", line 99, in from giscanner.scannermain import scanner_main File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/scannermain.py", line 35, in from giscanner.ast import Include, Namespace File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/ast.py", line 29, in from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/sourcescanner.py", line 33, in from giscanner._giscanner import SourceScanner as CSourceScanner ModuleNotFoundError: No module named 'giscanner._giscanner' $ python3.8 /usr/bin/g-ir-scanner ERROR: Need at least one filename $ ls -alh /usr/bin/python3 lrwxrwxrwx 1 root root 9 Oct 18 10:23 /usr/bin/python3 -> python3.7 ** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1861556 Title: g-ir-scanner doesn't work Status in gobject-introspection package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: Running g-ir-scanner doesn't work anymore after a recent upgrade with a fully up to date focal: Traceback (most recent call last): File "/usr/bin/g-ir-scanner", line 99, in from giscanner.scannermain import scanner_main File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/scannermain.py", line 35, in from giscanner.ast import Include, Namespace File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/ast.py", line 29, in from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/sourcescanner.py", line 33, in from giscanner._giscanner import SourceScanner as CSourceScanner ModuleNotFoundError: No module named 'giscanner._giscanner' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gobject-introspection 1.62.0-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 07:04:11 2020 InstallationDate: Installed on 2019-08-13 (171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gobject-introspection UpgradeStatus: Upgraded to focal on 2019-11-04 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1861556/+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 1861556] [NEW] g-ir-scanner doesn't work
Public bug reported: Running g-ir-scanner doesn't work anymore after a recent upgrade with a fully up to date focal: Traceback (most recent call last): File "/usr/bin/g-ir-scanner", line 99, in from giscanner.scannermain import scanner_main File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/scannermain.py", line 35, in from giscanner.ast import Include, Namespace File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/ast.py", line 29, in from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/sourcescanner.py", line 33, in from giscanner._giscanner import SourceScanner as CSourceScanner ModuleNotFoundError: No module named 'giscanner._giscanner' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gobject-introspection 1.62.0-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 07:04:11 2020 InstallationDate: Installed on 2019-08-13 (171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gobject-introspection UpgradeStatus: Upgraded to focal on 2019-11-04 (89 days ago) ** Affects: gobject-introspection (Ubuntu) Importance: Undecided Status: New ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1861556 Title: g-ir-scanner doesn't work Status in gobject-introspection package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: Running g-ir-scanner doesn't work anymore after a recent upgrade with a fully up to date focal: Traceback (most recent call last): File "/usr/bin/g-ir-scanner", line 99, in from giscanner.scannermain import scanner_main File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/scannermain.py", line 35, in from giscanner.ast import Include, Namespace File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/ast.py", line 29, in from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF File "/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/sourcescanner.py", line 33, in from giscanner._giscanner import SourceScanner as CSourceScanner ModuleNotFoundError: No module named 'giscanner._giscanner' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gobject-introspection 1.62.0-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 07:04:11 2020 InstallationDate: Installed on 2019-08-13 (171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gobject-introspection UpgradeStatus: Upgraded to focal on 2019-11-04 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1861556/+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 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
I updated libpoppler90 and related packages to 0.80.0-0ubuntu1.1, the crash is now fixed for me. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Eoan: Fix Committed Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 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/ubuntu/+source/poppler/+bug/1849773/+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 1861481] Re: language-options causes live CD sessions to be untranslated
On a focal live cd, I tried to downgrade lightdm and accountsservice to their bionic versions and restart their services without rebooting, yet again the session was not translated. So I'm at a loss on which package was the one that caused the change in 19.10, maybe even glibc itself. Nevertheless, I was able to reproduce a similar problem in a normal (non-live) focal installation, by just purging language-pack-el, or by just moving aside the directory /usr/share/locale-langpack/el and restarting accounts-daemon and lightdm. Without the language pack, my LANGUAGE is "en" and my session is untranslated. And if I launch d-feet and check /org/freedesktop/Accounts/User1000 => org.freedesktop.Accounts.User => property Language, it says "en". I think that is the problem, accountsservice should report that my language is either "el" or empty, but definitely not "en". Even if the langpack isn't there, LANG in /etc/default/locale is el_GR.UTF-8, and I don't have "en" defined anywhere in my system or my account; and MATE can show Greek even without a langpack. I think then LightDM will work fine without any changes. Does this approach sound OK? ** Changed in: accountsservice (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Confirmed Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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
