[Touch-packages] [Bug 1953297] [NEW] unmkinitramfs does not work on arm64
Public bug reported: unmkinitramfs in initramfs-tools-core works fine on amd64 but same command fails on arm64 On amd64: $ unmkinitramfs initrd temp $ ls temp early early2 main On arm64: $ unmkinitramfs initrd temp cpio: premature end of archive $ ls temp $ The tested unmkinitramfs is 0.136ubuntu6.6 in focal-update archive ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1953297 Title: unmkinitramfs does not work on arm64 Status in initramfs-tools package in Ubuntu: New Bug description: unmkinitramfs in initramfs-tools-core works fine on amd64 but same command fails on arm64 On amd64: $ unmkinitramfs initrd temp $ ls temp early early2 main On arm64: $ unmkinitramfs initrd temp cpio: premature end of archive $ ls temp $ The tested unmkinitramfs is 0.136ubuntu6.6 in focal-update archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953297/+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 1651044] Re: ProxyDHCP replies on invalid range
[Expired for dnsmasq (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dnsmasq (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1651044 Title: ProxyDHCP replies on invalid range Status in dnsmasq package in Ubuntu: Expired Bug description: In Ubuntu 16.04, I've configured dnsmasq to reply on subnet=10.160.37.0/24, yet it replies even when it gets an IP on subnet=10.161.254.0/24. I've only seen this after clean system restart. If I restart dnsmasq later on, it works as expected. Maybe when dnsmasq starts, the network isn't up yet, and it incorrectly initializes some networking information? I'm using network-manager with DHCP. Details: $ egrep -rv '^#|^$' /etc/dnsmasq.* /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-range=10.160.37.0,proxy /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-range=192.168.67.20,192.168.67.250,8h /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:enable-tftp /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:tftp-root=/var/lib/tftpboot/ /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-option=17,/opt/ltsp/i386 /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-vendorclass=etherboot,Etherboot /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-vendorclass=pxe,PXEClient /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-vendorclass=ltsp,"Linux ipconfig" /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-boot=net:pxe,/ltsp/i386/pxelinux.0 /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-boot=net:etherboot,/ltsp/i386/nbi.img /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-boot=net:ltsp,/ltsp/i386/lts.conf /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-option=vendor:pxe,6,2b /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-no-override /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:pxe-service=X86PC, "Boot from network", /ltsp/i386/pxelinux $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp2s0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether d0:50:99:a6:bc:0a brd ff:ff:ff:ff:ff:ff inet 10.161.254.185/24 brd 10.161.254.255 scope global dynamic enp2s0 valid_lft 431873sec preferred_lft 431873sec inet6 fe80::f363:c1e2:9cb8:d9e2/64 scope link valid_lft forever preferred_lft forever $ sudo netstat -nap | grep dnsmasq [sudo] password for administrator: tcp0 0 0.0.0.0:53 0.0.0.0:* LISTEN 843/dnsmasq tcp6 0 0 :::53 :::*LISTEN 843/dnsmasq udp0 0 0.0.0.0:53 0.0.0.0:* 843/dnsmasq udp0 0 0.0.0.0:67 0.0.0.0:* 843/dnsmasq udp0 0 0.0.0.0:69 0.0.0.0:* 843/dnsmasq udp0 0 0.0.0.0:40110.0.0.0:* 843/dnsmasq udp6 0 0 :::53 :::* 843/dnsmasq udp6 0 0 :::69 :::* 843/dnsmasq unix 2 [ ] DGRAM15746843/dnsmasq $ grep dnsmasq /var/log/syslog | tail -n 30 Dec 19 10:52:17 ltsp-server systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server... Dec 19 10:52:17 ltsp-server dnsmasq[630]: dnsmasq: syntax check OK. Dec 19 10:52:20 ltsp-server dnsmasq[843]: started, version 2.75 cachesize 150 Dec 19 10:52:20 ltsp-server dnsmasq[843]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify Dec 19 10:52:20 ltsp-server dnsmasq[843]: DNS service limited to local subnets Dec 19 10:52:20 ltsp-server dnsmasq-dhcp[843]: DHCP, IP range 192.168.67.20 -- 192.168.67.250, lease time 8h Dec 19 10:52:20 ltsp-server dnsmasq-dhcp[843]: DHCP, proxy on subnet 10.160.37.0 Dec 19 10:52:20 ltsp-server dnsmasq-tftp[843]: TFTP root is /var/lib/tftpboot/ Dec 19 10:52:20 ltsp-server dnsmasq[843]: no servers found in /var/run/dnsmasq/resolv.conf, will retry Dec 19 10:52:20 ltsp-server dnsmasq[843]: read /etc/hosts - 7 addresses Dec 19 10:52:23 ltsp-server systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Dec 19 10:52:29 ltsp-server dnsmasq[843]: reading /var/run/dnsmasq/resolv.conf Dec 19 10:52:29 ltsp-server dnsmasq[843]: ignoring nameserver 127.0.0.1 - local interface Dec 19 10:52:29 ltsp-server dnsmasq[843]: using nameserver 194.63.238.4#53 Dec 19 10:52:29 ltsp-server dnsmasq[843]:
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Patch proposed upstream:
https://lists.zytor.com/archives/klibc/2021-December/004629.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
In Progress
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+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 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
In progress per the above link. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mutter (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/124440 Title: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed Status in gnome-control-center: Unknown Status in GTK+: New Status in Mir: Fix Released Status in Mutter: Unknown Status in Unity: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Won't Fix Bug description: This has been driving me nuts for a while now. The scroll wheel on my desktop mouse (it's an MS wireless optical mouse model 1008) scrolls rather fast. Instead of moving a few lines, it scrolls half a page or more with a very gentle scroll. The bluetooth mouse I use with my laptop does not do this so it's probably somewhat hardware specific. However, I'm wondering if there is a way to modify the speed or sensitivity. I found an answer here from about a year ago (https://answers.launchpad.net/ubuntu/+question/1339) that suggests there isn't a way but I'm wondering if anything has changed since then. I've also skimmed through synaptic but didn't see anything promising (like gsynaptic for touchpads). Thanks. See https://answers.launchpad.net/ubuntu/+question/9200 for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+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 1953262] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: Installing on MBP/M1 w/ARM processor, cored out while installing vagrant Description:Ubuntu 20.04.3 LTS Release:20.04 dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of libguestfs0:arm64: libguestfs0:arm64 depends on lvm2; however: Package lvm2 is not configured yet. dpkg: error processing package libguestfs0:arm64 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of libguestfs-tools: libguestfs-tools depends on libguestfs0 (= 1:1.40.2-7ubuntu5); however: Package libguestfs0:arm64 is not configured yet. dpkg: error processing package libguestfs-tools (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-xfs:arm64: libguestfs-xfs:arm64 depends on libguestfs0 (= 1:1.40.2-7ubuntu5); however: Package libguestfs0:arm64 is not configured yet. dpkg: error processing package libguestfs-xfs:arm64 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of libguestfs-perl: libguestfs-perl depends on libguestfs0 (= 1:1.40.2-7ubuntu5); however: Package libguestfs0:arm64 is not configured yet. dpkg: error processing package libguestfs-perl (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-hfsplus:arm64: libguestfs-hfsplus:arm64 depends on libguestfs0 (= 1:1.40.2-7ubuntu5); however: Package libguestfs0:arm64 is not configured yet. dpkg: error processing package libguestfs-hfsplus:arm64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-reiserfs:arm64: libguestfs-reiserfs:arm64 depends on libguestfs0 (= 1:1.40.2-7ubuntu5); however: Package libguestfs0:arm64 is not configured yet. dpkg: error processing package libguestfs-reiserfs:arm64 (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already Processing triggers for initramfs-tools (0.136ubuntu6.6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic Unsupported platform on EFI system, doing nothing. Errors were encountered while processing: lvm2 libguestfs0:arm64 libguestfs-tools libguestfs-xfs:arm64 libguestfs-perl libguestfs-hfsplus:arm64 libguestfs-reiserfs:arm64 E: Sub-process /usr/bin/dpkg returned an error code (1) W: Operation was interrupted before it could finish ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 CasperMD5CheckResult: pass Date: Sun Dec 5 18:05:26 2021 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-13 (267 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release arm64 (20210201.2) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1953262 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned
[Touch-packages] [Bug 1953258] [NEW] opencv regressed on armhf
Public bug reported: autopkgtests of reverse-dependencies of opencv are failing on armhf with opencv 4.5.4+dfsg-1ubuntu1. A git bisect points to https://github.com/opencv/opencv/commit/eab2b9dc09570b141adeba3814f196a4efd8adb2 as the commit that has introduced the regression. ** Affects: opencv (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1953258 Title: opencv regressed on armhf Status in opencv package in Ubuntu: New Bug description: autopkgtests of reverse-dependencies of opencv are failing on armhf with opencv 4.5.4+dfsg-1ubuntu1. A git bisect points to https://github.com/opencv/opencv/commit/eab2b9dc09570b141adeba3814f196a4efd8adb2 as the commit that has introduced the regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1953258/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
(1) Test passed with Lenovo ThinkEdge SE30(11ND) and Lenovo ThinkEdge SE30(11NE) on Hirsute: * The version of the packages tested: ModemManager: 1.16.6-2~21.04.1 (2) Test passed with Lenovo ThinkEdge SE30(11ND) and Lenovo ThinkEdge SE30(11NE) on Focal: * The version of the packages tested: ModemManager: 1.16.6-2~20.04.1 The detail testing procedure and result is provided as the attached file : "TestReportForHirsuteAndFocal-proposed-1946096.pdf" The regression test report will be provided. ** Attachment added: "TestReportForHirsuteAndFocal-proposed-1946096.pdf" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5545449/+files/TestReportForHirsuteAndFocal-proposed-1946096.pdf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Focal: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the modem is working 4. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 5. Using the firmware upgrading application to upgrade the modem’s firmware 6. Verify if the modem’s firmware upgrading is successful 7. Reboot 8. Verify if the upgraded modem firmware is still working --- Regression test --- Verify if one USB modem are still working with these patches for PCIe modems. [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems *
[Touch-packages] [Bug 1757625] Re: Please port your package away from Qt 4
** Changed in: dee-qt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757625 Title: Please port your package away from Qt 4 Status in dee-qt package in Ubuntu: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee-qt/+bug/1757625/+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 1757884] Re: Please port your package away from Qt 4
** Changed in: syncevolution (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1757884 Title: Please port your package away from Qt 4 Status in syncevolution package in Ubuntu: Fix Released Status in syncevolution package in Debian: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1757884/+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 1757747] Re: Please port your package away from Qt 4
** Changed in: lightdm (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1757747 Title: Please port your package away from Qt 4 Status in lightdm package in Ubuntu: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1952496] Re: ubuntu 20.04 LTS network problem
On Mon, Nov 29, 2021 at 10:33 PM, Trent Lloyd <1952...@bugs.launchpad.net> wrote: > Thanks for the data. I can see you queried 'steven-ubuntu.local' and > that looks like the hostname of the local machine. Can you also query > the hostname of the AFP server you are trying to connect to (using > both > getent hosts and avahi-resolve-host-name). To confirm, 'steven-ubuntu.local' is the hostname of the 20.04 system, where all queries are performed to data requests. New data with a caveat: ** Attachment added: "network_report_2.txt" https://bugs.launchpad.net/bugs/1952496/+attachment/5545421/+files/network_report_2.txt -- 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/1952496 Title: ubuntu 20.04 LTS network problem Status in avahi package in Ubuntu: Incomplete Bug description: Network afp only partially works. Two tries, Elementary OS 6, Ubuntu 20.04 installs both have identical problem. Resolved by reinstalling Ubuntu 18.04 LTS. Using different kernels doesn't matter. Specific problem is with afp protocol name resolution. Searching local network for ip address using afp://ip_address did connect, but using GUI Files/Other Locations/Networks with named hosts will not. Always returns can't resolve hostname.local. Tried multiple edits of different network files, even installed netatalk in attempts. Again, solution is to go back to downgrade, works right out of the box, as did on another, and this before upgrade. This was only attempted with 2 other computers, one mac, one ubuntu/elementary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1952496/+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
