[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session
Seems fixed. Huzzah! $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu3 Candidate: 1:9.2p1-2ubuntu3 Version table: *** 1:9.2p1-2ubuntu3 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session Status in openssh package in Ubuntu: Fix Committed Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2021409] [NEW] mdns failng with current versions of libnss-mdns and avahi-daemon
Public bug reported: I have Ubuntu Server 22.04.2 I have installed avahi-daemon and libnss-mdns, but mdns resolution is not occurring over my primary network interface: Note that this is with `allow-interfaces=ens160` set /etc/avahi/avahi- daemon.conf. (22:25:17 Sat May 27 2023 jeremy@cid pts/0 aarch64) [648] ~ $ sudo resolvectl mdns ens160 1 (22:25:22 Sat May 27 2023 jeremy@cid pts/0 aarch64) [649] ~ $ resolvectl status Global Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens160) Current Scopes: DNS mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 2601:647:6680:4b95::1 DNS Servers: 10.1.30.1 2601:647:6680:4b95::1 DNS Domain: localdomain (22:25:27 Sat May 27 2023 jeremy@cid pts/0 aarch64) [650] ~ $ avahi-resolve -n cid.local Failed to resolve host name 'cid.local': Timeout reached (22:26:03 Sat May 27 2023 jeremy@cid pts/0 aarch64) [651] ~ $ avahi-resolve -a 10.0.30.1 Failed to resolve address '10.0.30.1': Timeout reached (22:26:13 Sat May 27 2023 jeremy@cid pts/0 aarch64) [652] ~ $ sudo systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-05-27 22:22:29 UTC; 3min 51s ago TriggeredBy: ● avahi-daemon.socket Main PID: 850 (avahi-daemon) Status: "avahi-daemon 0.8 starting up." Tasks: 2 (limit: 4523) Memory: 1.5M CPU: 15ms CGroup: /system.slice/avahi-daemon.service ├─850 "avahi-daemon: running [cid.local]" └─891 "avahi-daemon: chroot helper" May 27 22:22:29 cid avahi-daemon[850]: No service file found in /etc/avahi/services. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv6 with address 2601:647:6680:4b95:20c:29ff:fe42:f399. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv6 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv4 with address 10.1.30.2. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv4 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Network interface enumeration completed. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 2601:647:6680:4b95:20c:29ff:fe42:f399 on ens160.*. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 10.1.30.2 on ens160.IPv4. May 27 22:22:30 cid avahi-daemon[850]: Server startup complete. Host name is cid.local. Local service cookie is 2371061072. May 27 22:26:11 cid avahi-daemon[850]: wide-area.c: Query timed out. (22:27:14 Sat May 27 2023 jeremy@cid pts/0 aarch64) [657] ~ $ grep hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns --- If I set 'allow-interfaces=ens160,lo`, we are able to resolve cid.local to localhost: $ avahi-resolve -n cid.local cid.local 127.0.0.1 but I cannot lookup anything else on my network via the ens160 interface. I *can* resolve cid.local (10.1.30.2) from other devices on my network for a brief moment after I restart avahi-daemon. ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Project changed: launchpad => avahi (Ubuntu) -- 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/2021409 Title: mdns failng with current versions of libnss-mdns and avahi-daemon Status in avahi package in Ubuntu: New Bug description: I have Ubuntu Server 22.04.2 I have installed avahi-daemon and libnss-mdns, but mdns resolution is not occurring over my primary network interface: Note that this is with `allow-interfaces=ens160` set /etc/avahi/avahi- daemon.conf. (22:25:17 Sat May 27 2023 jeremy@cid pts/0 aarch64) [648] ~ $ sudo resolvectl mdns ens160 1 (22:25:22 Sat May 27 2023 jeremy@cid pts/0 aarch64) [649] ~ $ resolvectl status Global Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens160) Current Scopes: DNS mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 2601:647:6680:4b95::1 DNS Servers: 10.1.30.1 2601:647:6680:4b95::1 DNS Domain: localdomain (22:25:27 Sat May 27 2023 jeremy@cid pts/0 aarch64) [650] ~ $ avahi-resolve -n cid.local Failed to resolve host name 'cid.local': Timeout reached (22:26:03 Sat May 27 2023 jeremy@cid pts/0 aarch64) [651] ~ $ avahi-resolve -a 10.0.30.1 Failed to resolve address '10.0.30.1': Timeout reached (22:26:13 Sat May 27 2023 jeremy@cid pts/0 aarch64) [652] ~ $ sudo systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded
[Touch-packages] [Bug 1970047] Re: GTK file open dialog hangs Chrome/Brave
Disabling hardware acceleration in Chrome didn't work for me. But, I can confirm that: `gsettings set org.gnome.desktop.sound input-feedback-sounds false` worked for me. Chrome Browser: Version 113.0.5672.126 (Official Build) (64-bit) OS: Ubuntu 22.04.2 LTS Processor: AMD® Ryzen 7 pro 6850u with radeon graphics × 16 Kernel: 5.15.0-72-generic GNOME version: 42.5 Graphics: REMBRANDT (rembrandt, LLVM 15.0.7, DRM 3.42, 5.15.0-72-generic) -- 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/1970047 Title: GTK file open dialog hangs Chrome/Brave Status in gtk+3.0 package in Ubuntu: Expired Bug description: I removed xdg-desktop-portal because I use Xorg, don't use any snaps or flatpaks and GTK file open dialog is better than portal one. But GTK file open dialog makes Chrome/Brave freeze after closing it. Steps to reproduce: 1. Install Chrome or Brave 2. Remove xdg-desktop-portal so Chrome/Brave use GTK file open dialog instead of portal one 3. Press Ctrl+O to open file open dialog 4. Close dialog or choose any file, does not matter, browser is stuck I don't see this behavior on Debian that I also use, so I guess bug is in GTK rather than Chrome/Brave. Fresh install of Ubuntu 22.04 lsb_release: Description: Ubuntu 22.04 LTS Release: 22.04 libgtk-3-0: Installed: 3.24.33-1ubuntu1 Candidate: 3.24.33-1ubuntu1 Version table: *** 3.24.33-1ubuntu1 500 500 http://rs.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 19:27:45 2022 InstallationDate: Installed on 2022-04-22 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047/+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 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
Thank you for the workaround which works in my case as well. Ubuntu 23.04 6.2.0-20-generic libheif 1.14.2-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Confirmed Status in gdk-pixbuf package in Ubuntu: Confirmed Status in libheif package in Ubuntu: Confirmed Bug description: In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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 2021400] [NEW] I dont find my intel hd graphics driver
Public bug reported: I dont find my intel hd graphics driver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 27 17:11:36 2023 DistUpgraded: 2023-05-27 16:15:33,109 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2023-05-26 (0 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) MachineType: LENOVO 20157 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=0a4685c6-4b44-4a89-be67-813e2fa77c59 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2023-05-27 (0 days ago) dmi.bios.date: 10/23/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN42WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake 2 dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr62CN42WW:bd10/23/2012:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 20157 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 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 xserver.bootTime: Sat May 27 15:58:40 2023 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5543 vendor CMO xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty 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/2021400 Title: I dont find my intel hd graphics driver Status in xorg package in Ubuntu: New Bug description: I dont find my intel hd graphics driver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 27 17:11:36 2023 DistUpgraded: 2023-05-27 16:15:33,109 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2023-05-26 (0 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) MachineType: LENOVO 20157 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=0a4685c6-4b44-4a89-be67-813e2fa77c59 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2023-05-27 (0 days ago) dmi.bios.date: 10/23/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN42WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake 2 dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr62CN42WW:bd10/23/2012:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 20157 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
[Touch-packages] [Bug 1410968] Re: In image 195 krillin 163 mako system settings is not showing updates
If you are experiencing an issue where the system settings are not showing updates on image 195, it could be due to various reasons. Here are a few suggestions to troubleshoot the problem: https://cryptonewstoken.com/why-is-crypto-crashing/ Check for network connectivity: Ensure that your device has a stable internet connection. System updates typically require an active internet connection to download and install the latest updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1410968 Title: In image 195 krillin 163 mako system settings is not showing updates Status in Telegram app: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in ubuntu-touch-meta package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu RTM: Fix Released Status in ubuntu-touch-meta package in Ubuntu RTM: New Bug description: STEPS: Setup 1 Enable developer mode 2 from pc phablet-config writable-image 3 adb shell 4 sudo vim.tiny /etc/system-image/channel.ini 5 last 2 lines change the number to be back 10 images i.e. change the 195 to 185 6 sudo rm /userdata/.writable_image 7 rm .local/share/ubuntu-push-client/level.db 8 sudo reboot Test 1 Wait for the announcement of a new image 2 Drag down the indicator 3 Click on the image notification 4 Setting page opens on updates but is blank EXPECTED: The updates page is shown and you can click on update ACTUAL: The header is shown other wise it is a blank page after the spinner finishes spinning. To manage notifications about this bug go to: https://bugs.launchpad.net/telegram-app/+bug/1410968/+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 2018538] Re: All PDFs when printed come out mirror image
I could reproduce it now with Ondrej's PPD file, thank you very much, Ondrej. I also found the default PPD file for the HP Colour LaserJet CP2025dn (the PostScript one of HPLIP), the printer of the original poster, Hugo Squelch, thanks, Hugo. With this I fixed it upstream now: https://github.com/OpenPrinting/libppd/commit/a86f9993674f1 All PPD files with "MirrorPrint" option cuased mirrored printout If a PPD contains an option "MirrorPrint", the ppdFilterLoadPPD() sent the option "mirror=true" to the filter functions, regardless of the actual setting of "MirrorPrint" (which is usually "False" by default). This made all printouts on printers using a PPD file with a "MirrorPrint" option coming out mirrored, with no way to counteract this by any options or attributes. This is fixed now by checking the setting of "MirrorPrint". ** Changed in: cups (Ubuntu) Status: Incomplete => In Progress ** Package changed: cups (Ubuntu) => libppd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2018538 Title: All PDFs when printed come out mirror image Status in libppd package in Ubuntu: In Progress Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libppd/+bug/2018538/+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 1288539] Re: [mako] progressive shearing
The attached video will be useful in better understanding the problem. To further investigate and address the issue, it might be beneficial to gather more specific https://technology-geek.com/garage-door- springs-how-to-identify-repair-and-replace/">identify repair information or reach out to the development team for assistance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1288539 Title: [mako] progressive shearing Status in camera-app: Confirmed Status in android package in Ubuntu: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: On my mako device, in both the mwc image and r203, I've seen the camera get out of alignment with itself, shearing gradually more and more sideways (portrait mode sideways), with noise lines sometimes appearing, then looping around. This shows up both in the image preview and in the picture produced after pressing the shutter button. I'm not sure how to reproduce the issue, but I've seen it a total of three times out of about a hundred invocations of the camera app, and someone else in QA saw it during our daily standup. I've attached a video showing what it looks like. In general, it seems like this either happens within ~10 seconds or so of starting the app, or it won't happen during that session. I think it may help to shake the phone and/or touch the image to focus, to trigger the issue, but I have not been able to trigger it on purpose yet. So... not much genuinely useful information yet. But if it continues to happen, hopefully we can gather more details here. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1288539/+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 1401488] Re: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption
Experiencing crashes in the malloc function due to heap corruption can be challenging to resolve. Here are a few steps you can consider to address this issue: https://cryptocointricks.com/how-does-spot-trading-in-cryptocurrency-work/ Review code for memory errors: Carefully review your code for any memory-related errors, such as buffer overflows, use-after-free, or invalid pointer operations. These issues can lead to heap corruption and subsequent crashes. Use tools like memory debuggers or sanitizers to identify potential problems. -- 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/1401488 Title: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption Status in GLib: Expired Status in Mir: Fix Released Status in Mir 0.9 series: Won't Fix Status in glib2.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Bug description: This happens randomly when using the phone ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.0.5+15.04.20141204-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf AssertionMessage: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** CrashCounter: 1 Date: Wed Dec 10 19:28:35 2014 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1417733344 GraphicsCard: InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141211-020204) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 9 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_message (do_abort=, fmt=0xb68e3628 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (action=1, str=0xb68e366c "corrupted double-linked list", ptr=) at malloc.c:4996 malloc_consolidate (av=av@entry=0xaa800010) at malloc.c:4165 _int_malloc (av=av@entry=0xaa800010, bytes=bytes@entry=1264) at malloc.c:3423 __GI___libc_malloc (bytes=1264) at malloc.c:2891 Title: unity-system-compositor assert failure: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.58-2 version.lightdm: lightdm 1.13.0-0ubuntu2 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1401488/+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 1415029] Re: Not yet available but configured providers should be added as soon as they become available
it is a good practice to configure and prepare for the addition of providers that are not yet available. By setting up the necessary configurations in advance, you can https://cryptorealtrading.com/gangster-coin-flip-general-introduction/ ensure a smoother transition and faster integration when the providers become available. This proactive approach helps save time and enables you to take advantage of new opportunities as soon as they arise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1415029 Title: Not yet available but configured providers should be added as soon as they become available Status in Canonical System Image: Fix Released Status in location-service package in Ubuntu: In Progress Status in ubuntu-location-provider-here package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Invalid Status in ubuntu-location-provider-here package in Ubuntu RTM: Fix Released Bug description: Right now, the location service tries to instantiate configured providers at startup. In specific corner cases, some of the configured sensors might not be available and the service should be able to be notified when those providers become available. In particular, this affects the wizard running on first boot, and subsequent login to the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415029/+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 2021409] Re: mdns failng with current versions of libnss-mdns and avahi-daemon
Also: [659] /etc/avahi/services $ avahi-browse -a + lo IPv4 cid SSH Remote Terminal local + lo IPv4 cid SFTP File Transfer local It's as if something is causing the network interface to not support mdns, but everyhing looks configured to me... what am I missing? It should really not be this difficult... ** Package changed: avahi (Ubuntu) => nss-mdns (Ubuntu) ** Also affects: avahi (Ubuntu) Importance: Undecided Status: New ** Also affects: avahi Importance: Undecided Status: New ** Bug watch added: github.com/lathiat/nss-mdns/issues #87 https://github.com/lathiat/nss-mdns/issues/87 ** Changed in: avahi Importance: Undecided => Unknown ** Changed in: avahi Status: New => Unknown ** Changed in: avahi Remote watch: None => github.com/lathiat/nss-mdns/issues #87 -- 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/2021409 Title: mdns failng with current versions of libnss-mdns and avahi-daemon Status in Avahi: Unknown Status in avahi package in Ubuntu: New Status in nss-mdns package in Ubuntu: New Bug description: I have Ubuntu Server 22.04.2 I have installed avahi-daemon and libnss-mdns, but mdns resolution is not occurring over my primary network interface: Note that this is with `allow-interfaces=ens160` set /etc/avahi/avahi- daemon.conf. (22:25:17 Sat May 27 2023 jeremy@cid pts/0 aarch64) [648] ~ $ sudo resolvectl mdns ens160 1 (22:25:22 Sat May 27 2023 jeremy@cid pts/0 aarch64) [649] ~ $ resolvectl status Global Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens160) Current Scopes: DNS mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 2601:647:6680:4b95::1 DNS Servers: 10.1.30.1 2601:647:6680:4b95::1 DNS Domain: localdomain (22:25:27 Sat May 27 2023 jeremy@cid pts/0 aarch64) [650] ~ $ avahi-resolve -n cid.local Failed to resolve host name 'cid.local': Timeout reached (22:26:03 Sat May 27 2023 jeremy@cid pts/0 aarch64) [651] ~ $ avahi-resolve -a 10.0.30.1 Failed to resolve address '10.0.30.1': Timeout reached (22:26:13 Sat May 27 2023 jeremy@cid pts/0 aarch64) [652] ~ $ sudo systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-05-27 22:22:29 UTC; 3min 51s ago TriggeredBy: ● avahi-daemon.socket Main PID: 850 (avahi-daemon) Status: "avahi-daemon 0.8 starting up." Tasks: 2 (limit: 4523) Memory: 1.5M CPU: 15ms CGroup: /system.slice/avahi-daemon.service ├─850 "avahi-daemon: running [cid.local]" └─891 "avahi-daemon: chroot helper" May 27 22:22:29 cid avahi-daemon[850]: No service file found in /etc/avahi/services. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv6 with address 2601:647:6680:4b95:20c:29ff:fe42:f399. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv6 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv4 with address 10.1.30.2. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv4 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Network interface enumeration completed. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 2601:647:6680:4b95:20c:29ff:fe42:f399 on ens160.*. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 10.1.30.2 on ens160.IPv4. May 27 22:22:30 cid avahi-daemon[850]: Server startup complete. Host name is cid.local. Local service cookie is 2371061072. May 27 22:26:11 cid avahi-daemon[850]: wide-area.c: Query timed out. (22:27:14 Sat May 27 2023 jeremy@cid pts/0 aarch64) [657] ~ $ grep hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns --- If I set 'allow-interfaces=ens160,lo`, we are able to resolve cid.local to localhost: $ avahi-resolve -n cid.local cid.local 127.0.0.1 but I cannot lookup anything else on my network via the ens160 interface. I *can* resolve cid.local (10.1.30.2) from other devices on my network for a brief moment after I restart avahi-daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/2021409/+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 2021409] Re: mdns failng with current versions of libnss-mdns and avahi-daemon
** Changed in: avahi Status: Unknown => New -- 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/2021409 Title: mdns failng with current versions of libnss-mdns and avahi-daemon Status in Avahi: New Status in avahi package in Ubuntu: New Status in nss-mdns package in Ubuntu: New Bug description: I have Ubuntu Server 22.04.2 I have installed avahi-daemon and libnss-mdns, but mdns resolution is not occurring over my primary network interface: Note that this is with `allow-interfaces=ens160` set /etc/avahi/avahi- daemon.conf. (22:25:17 Sat May 27 2023 jeremy@cid pts/0 aarch64) [648] ~ $ sudo resolvectl mdns ens160 1 (22:25:22 Sat May 27 2023 jeremy@cid pts/0 aarch64) [649] ~ $ resolvectl status Global Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens160) Current Scopes: DNS mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 2601:647:6680:4b95::1 DNS Servers: 10.1.30.1 2601:647:6680:4b95::1 DNS Domain: localdomain (22:25:27 Sat May 27 2023 jeremy@cid pts/0 aarch64) [650] ~ $ avahi-resolve -n cid.local Failed to resolve host name 'cid.local': Timeout reached (22:26:03 Sat May 27 2023 jeremy@cid pts/0 aarch64) [651] ~ $ avahi-resolve -a 10.0.30.1 Failed to resolve address '10.0.30.1': Timeout reached (22:26:13 Sat May 27 2023 jeremy@cid pts/0 aarch64) [652] ~ $ sudo systemctl status avahi-daemon ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-05-27 22:22:29 UTC; 3min 51s ago TriggeredBy: ● avahi-daemon.socket Main PID: 850 (avahi-daemon) Status: "avahi-daemon 0.8 starting up." Tasks: 2 (limit: 4523) Memory: 1.5M CPU: 15ms CGroup: /system.slice/avahi-daemon.service ├─850 "avahi-daemon: running [cid.local]" └─891 "avahi-daemon: chroot helper" May 27 22:22:29 cid avahi-daemon[850]: No service file found in /etc/avahi/services. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv6 with address 2601:647:6680:4b95:20c:29ff:fe42:f399. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv6 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Joining mDNS multicast group on interface ens160.IPv4 with address 10.1.30.2. May 27 22:22:29 cid avahi-daemon[850]: New relevant interface ens160.IPv4 for mDNS. May 27 22:22:29 cid avahi-daemon[850]: Network interface enumeration completed. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 2601:647:6680:4b95:20c:29ff:fe42:f399 on ens160.*. May 27 22:22:29 cid avahi-daemon[850]: Registering new address record for 10.1.30.2 on ens160.IPv4. May 27 22:22:30 cid avahi-daemon[850]: Server startup complete. Host name is cid.local. Local service cookie is 2371061072. May 27 22:26:11 cid avahi-daemon[850]: wide-area.c: Query timed out. (22:27:14 Sat May 27 2023 jeremy@cid pts/0 aarch64) [657] ~ $ grep hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns --- If I set 'allow-interfaces=ens160,lo`, we are able to resolve cid.local to localhost: $ avahi-resolve -n cid.local cid.local 127.0.0.1 but I cannot lookup anything else on my network via the ens160 interface. I *can* resolve cid.local (10.1.30.2) from other devices on my network for a brief moment after I restart avahi-daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/2021409/+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
