[Touch-packages] [Bug 1595752] Re: lightdm crashed with SIGSEGV
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- 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/1595752 Title: lightdm crashed with SIGSEGV Status in lightdm package in Ubuntu: Expired Bug description: On boot. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 Date: Wed Jun 22 17:58:23 2016 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2016-04-28 (56 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha i386 (20160426) ProcCmdline: lightdm --session-child 12 19 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0xb774e953:mov0x4(%eax),%edi PC (0xb774e953) ok source "0x4(%eax)" (0xb6f42d08) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () from /lib/ld-linux.so.2 ?? () from /lib/ld-linux.so.2 ?? () from /lib/ld-linux.so.2 ?? () from /lib/ld-linux.so.2 ?? () from /lib/i386-linux-gnu/libdl.so.2 Title: lightdm crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1595752/+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 1635933] Re: package avahi-dnsconfd (not installed) failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
[Expired for avahi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: avahi (Ubuntu) Status: Incomplete => Expired -- 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/1635933 Title: package avahi-dnsconfd (not installed) failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück Status in avahi package in Ubuntu: Expired Bug description: happened while uninstalling ProblemType: Package DistroRelease: Ubuntu 16.10 Package: avahi-dnsconfd (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Oct 22 22:31:09 2016 ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2016-10-14 (8 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: avahi Title: package avahi-dnsconfd (not installed) failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to yakkety on 2016-10-14 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1635933/+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 1638833] Re: at-spi-bus-launcher crashed with SIGSEGV in strlen()
[Expired for at-spi2-core (Ubuntu) because there has been no activity for 60 days.] ** Changed in: at-spi2-core (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1638833 Title: at-spi-bus-launcher crashed with SIGSEGV in strlen() Status in at-spi2-core package in Ubuntu: Expired Bug description: Pops up shortly after starting the desktop. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: at-spi2-core 2.22.0-3 ProcVersionSignature: Ubuntu 4.8.0-26.28-powerpc-smp 4.8.0 Uname: Linux 4.8.0-26-powerpc-smp ppc ApportVersion: 2.20.3-0ubuntu8 Architecture: powerpc Date: Thu Nov 3 08:36:20 2016 ExecutablePath: /usr/lib/at-spi2-core/at-spi-bus-launcher InstallationDate: Installed on 2016-11-03 (0 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161103) ProcCmdline: /usr/lib/at-spi2-core/at-spi-bus-launcher ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=de_AT:de LANG=de_AT.UTF-8 Signal: 11 SourcePackage: at-spi2-core StacktraceTop: strlen () at ../sysdeps/powerpc/powerpc32/strlen.S:98 g_variant_is_object_path () from /lib/powerpc-linux-gnu/libglib-2.0.so.0 g_dbus_proxy_new_for_bus () from /usr/lib/powerpc-linux-gnu/libgio-2.0.so.0 ?? () ?? () Title: at-spi-bus-launcher crashed with SIGSEGV in strlen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1638833/+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 1599401] Re: crash in XTranslateCoordinates from gdk_x11_display_translate_event
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Expired -- 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/1599401 Title: crash in XTranslateCoordinates from gdk_x11_display_translate_event Status in gtk+3.0 package in Ubuntu: Expired Bug description: polihron@polihron-K56CA:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mate-settings-daemon 1.14.0-1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jul 6 10:50:49 2016 ExecutablePath: /usr/bin/mate-settings-daemon InstallationDate: Installed on 2016-07-01 (4 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160629.1) ProcCmdline: /usr/bin/mate-settings-daemon Signal: 5 SourcePackage: mate-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: mate-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1599401/+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 1665359] Re: apport-gtk crashed with SIGABRT in raise()
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1665359 Title: apport-gtk crashed with SIGABRT in raise() Status in apport package in Ubuntu: Expired Bug description: No further information available. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: apport-gtk 2.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5 Uname: Linux 4.9.0-15-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Thu Feb 16 14:46:52 2017 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2011-10-14 (1952 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk Signal: 6 SourcePackage: apport StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1665359/+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 1674072] Re: fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
[Expired for fluidsynth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: fluidsynth (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1674072 Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer() Status in fluidsynth package in Ubuntu: Expired Bug description: Just tried starting it from the command line with a midi file. Jack available but not running at the time I tried this. I cannot vouch whether this was started with or without pasuspender: I tried both since without pasuspender fluidsynth (or jack) complained about Pulseaudio hogging the device. It could have crashed after the complaint, or it could have crashed independently without such a complaint. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: fluidsynth 1.1.6-4 ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1 Uname: Linux 4.10.0-11-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sun Mar 19 09:28:47 2017 ExecutablePath: /usr/bin/fluidsynth InstallationDate: Installed on 2011-10-14 (1982 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: fluidsynth /home/username/scores/tabber.midi SegvAnalysis: Segfault happened at: 0xf72d9194 : mov 0xc(%esi),%edx PC (0xf72d9194) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: fluidsynth StacktraceTop: jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0 fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1 ?? () from /usr/lib/i386-linux-gnu/libjack.so.0 start_thread (arg=0xf6809b40) at pthread_create.c:333 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113 Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer() UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1674072/+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 1519216] Re: On fail not out from program
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1519216 Title: On fail not out from program Status in initramfs-tools package in Ubuntu: Expired Bug description: On -k argument wrong update-initramfs print "fatal" error but still running. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: initramfs-tools 0.120ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CurrentDesktop: MATE Date: Tue Nov 24 08:01:35 2015 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to wily on 2015-11-02 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1519216/+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 1670463] Re: crash in XGetWindowProperty from gdk_check_wm_desktop_changed
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Expired -- 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/1670463 Title: crash in XGetWindowProperty from gdk_check_wm_desktop_changed Status in gtk+3.0 package in Ubuntu: Expired Bug description: start up error ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-settings-daemon 1.17.1-0~ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Mon Mar 6 20:29:40 2017 ExecutablePath: /usr/bin/mate-settings-daemon InstallationDate: Installed on 2016-09-09 (177 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/bin/mate-settings-daemon Signal: 5 SourcePackage: mate-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: mate-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: Upgraded to zesty on 2016-10-16 (140 days ago) UserGroups: adm audio cdrom dialout dip lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1670463/+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 1617756] Re: apt-get crashed with SIGSEGV in std::__cxx11::basic_string, std::allocator >::compare()
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1617756 Title: apt-get crashed with SIGSEGV in std::__cxx11::basic_string, std::allocator >::compare() Status in apt package in Ubuntu: Expired Bug description: Was doing a command line install in terminal.Install failed. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: apt 1.3~rc2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sun Aug 28 09:05:50 2016 ExecutablePath: /usr/bin/apt-get InstallationDate: Installed on 2016-08-27 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160824.1) ProcCmdline: apt-get update ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fbe9c32f7f0 <__memcmp_sse4_1+3504>: mov -0x6(%rdi),%eax PC (0x7fbe9c32f7f0) ok source "-0x6(%rdi)" (0x616e69622f737070) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: apt StacktraceTop: std::__cxx11::basic_string, std::allocator >::compare(unsigned long, unsigned long, std::__cxx11::basic_string, std::allocator > const&) const () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 APT::String::Startswith(std::__cxx11::basic_string, std::allocator > const&, std::__cxx11::basic_string, std::allocator > const&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 pkgAcquire::Worker::QueueItem(pkgAcquire::Queue::QItem*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 pkgAcquire::Queue::Cycle() () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 Title: apt-get crashed with SIGSEGV in std::__cxx11::basic_string, std::allocator >::compare() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1617756/+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 1520300] Re: package gettext 0.19.4-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for gettext (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gettext (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1520300 Title: package gettext 0.19.4-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gettext package in Ubuntu: Expired Bug description: I was trying to install the Epson linux drivers for Workforce printers. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: gettext 0.19.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptOrdering: gettext: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon Nov 23 22:02:56 2015 DpkgTerminalLog: dpkg: error processing package gettext (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:gettext:0.19.4-1ubuntu3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-21 (35 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150924) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: gettext Title: package gettext 0.19.4-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1520300/+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 1530092] Re: package fontconfig 2.11.1-0ubuntu6 [modified: usr/bin/fc-cache usr/bin/fc-cat usr/bin/fc-list usr/bin/fc-match usr/bin/fc-pattern usr/bin/fc-query usr/bin/fc-scan us
[Expired for fontconfig (Ubuntu) because there has been no activity for 60 days.] ** Changed in: fontconfig (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1530092 Title: package fontconfig 2.11.1-0ubuntu6 [modified: usr/bin/fc-cache usr/bin/fc-cat usr/bin/fc-list usr/bin/fc-match usr/bin/fc-pattern usr/bin/fc-query usr/bin/fc-scan usr/bin/fc-validate] failed to install/upgrade: ciclo nei trigger, abbandono Status in fontconfig package in Ubuntu: Expired Bug description: I don't know what can I say: I did'nt undestand what happened and what the problem is ProblemType: Package DistroRelease: Ubuntu 15.10 Package: fontconfig 2.11.1-0ubuntu6 [modified: usr/bin/fc-cache usr/bin/fc-cat usr/bin/fc-list usr/bin/fc-match usr/bin/fc-pattern usr/bin/fc-query usr/bin/fc-scan usr/bin/fc-validate] ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic i686 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Wed Dec 30 11:18:32 2015 ErrorMessage: ciclo nei trigger, abbandono InstallationDate: Installed on 2015-05-13 (230 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 (20150422.1) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: fontconfig Title: package fontconfig 2.11.1-0ubuntu6 [modified: usr/bin/fc-cache usr/bin/fc-cat usr/bin/fc-list usr/bin/fc-match usr/bin/fc-pattern usr/bin/fc-query usr/bin/fc-scan usr/bin/fc-validate] failed to install/upgrade: ciclo nei trigger, abbandono UpgradeStatus: Upgraded to wily on 2015-12-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1530092/+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 1559672] Re: package libqt4-svg:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befor
[Expired for qt4-x11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qt4-x11 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1559672 Title: package libqt4-svg:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in qt4-x11 package in Ubuntu: Expired Bug description: under ubuntu MATE 15-10 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libqt4-svg:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Mar 20 11:26:50 2016 DuplicateSignature: package:libqt4-svg:amd64:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-03-11 (8 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: qt4-x11 Title: package libqt4-svg:amd64 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1559672/+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 1516391] Re: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
[Expired for avahi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: avahi (Ubuntu) Status: Incomplete => Expired -- 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/1516391 Title: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1 Status in avahi package in Ubuntu: Expired Bug description: Uninstalling this package sometimes does not work, especially in Synaptic. Finally I managed to uninstall it with apt-get. I work on a VirtualBox. This bug wants to be reported, so I report it. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: avahi-dnsconfd 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Sun Nov 15 15:34:15 2015 ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1 InstallationDate: Installed on 2015-11-15 (0 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1516391/+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 1561931] Re: package libcurl3-gnutls:i386 7.43.0-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
[Expired for curl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: curl (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1561931 Title: package libcurl3-gnutls:i386 7.43.0-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in curl package in Ubuntu: Expired Bug description: minecraft does not work any more ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libcurl3-gnutls:i386 7.43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 Date: Fri Mar 25 11:07:03 2016 DuplicateSignature: package:libcurl3-gnutls:i386:7.43.0-1ubuntu2.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-12-04 (111 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: curl Title: package libcurl3-gnutls:i386 7.43.0-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1561931/+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 1533412] Re: package libxcb1:i386 1.11-0ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить
[Expired for libxcb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libxcb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1533412 Title: package libxcb1:i386 1.11-0ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить Status in libxcb package in Ubuntu: Expired Bug description: automatically crashed ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libxcb1:i386 1.11-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Wed Jan 13 04:30:17 2016 DpkgTerminalLog: Log ended: 2016-01-13 04:23:36 Log started: 2016-01-13 04:30:17 dpkg: ошибка при обработке пакета libxcb1:i386 (--remove): пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить DuplicateSignature: package:libxcb1:i386:1.11-0ubuntu1:пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить ErrorMessage: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить InstallationDate: Installed on 2016-01-12 (0 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: libxcb Title: package libxcb1:i386 1.11-0ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед попыткой удаления его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1533412/+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 1756581] Re: Greeter is not showing. I get wallpaper and can enter password.
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- 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/1756581 Title: Greeter is not showing. I get wallpaper and can enter password. Status in lightdm package in Ubuntu: Expired Bug description: I'm only seeing greeter wall paper. There is no username or dialog box to enter my password -- no prompt. However, if I blindly type my password, I can log on. I was installing cuda 8.0 today. I entered: sudo nvidia-xconfig --enable-all-gpus sudo nvidia-xconfig --cool-bits=12 and then I restarted lightdm with sudo systemctl restart lightdm.service After that the system rebooted, and I no longer saw a greeter prompt. I appreciate any help. Thank you, MikeyBee ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: MATE Date: Sat Mar 17 14:47:20 2018 InstallationDate: Installed on 2017-05-08 (313 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756581/+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 1671885] Re: synapse crashed with SIGSEGV in __GI___libc_free()
[Expired for libzeitgeist (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libzeitgeist (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1671885 Title: synapse crashed with SIGSEGV in __GI___libc_free() Status in libzeitgeist package in Ubuntu: Expired Status in synapse package in Ubuntu: Expired Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: synapse 0.2.99.2-2 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 10 19:07:46 2017 ExecutablePath: /usr/bin/synapse InstallationDate: Installed on 2017-03-09 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: synapse ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb4b2545162 <__GI___libc_free+34>: mov -0x8(%rdi),%rax PC (0x7fb4b2545162) ok source "-0x8(%rdi)" (0x3fb0101010101008) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: synapse StacktraceTop: __GI___libc_free (mem=0x3fb0101010101010) at malloc.c:2963 zeitgeist_symbol_info_register () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_symbol_initialize_symbols () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_symbol_get_all_children () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_db_reader_get_where_clause_for_symbol () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 Title: synapse crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzeitgeist/+bug/1671885/+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 1671885] Re: synapse crashed with SIGSEGV in __GI___libc_free()
[Expired for synapse (Ubuntu) because there has been no activity for 60 days.] ** Changed in: synapse (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1671885 Title: synapse crashed with SIGSEGV in __GI___libc_free() Status in libzeitgeist package in Ubuntu: Expired Status in synapse package in Ubuntu: Expired Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: synapse 0.2.99.2-2 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 10 19:07:46 2017 ExecutablePath: /usr/bin/synapse InstallationDate: Installed on 2017-03-09 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: synapse ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb4b2545162 <__GI___libc_free+34>: mov -0x8(%rdi),%rax PC (0x7fb4b2545162) ok source "-0x8(%rdi)" (0x3fb0101010101008) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: synapse StacktraceTop: __GI___libc_free (mem=0x3fb0101010101010) at malloc.c:2963 zeitgeist_symbol_info_register () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_symbol_initialize_symbols () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_symbol_get_all_children () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_db_reader_get_where_clause_for_symbol () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 Title: synapse crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzeitgeist/+bug/1671885/+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 1703176] Re: jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed.
[Expired for jackd2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: jackd2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1703176 Title: jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. Status in jackd2 package in Ubuntu: Expired Bug description: This may or may not be an artifact of me running a 32-bit userland on a 64-bit kernel (for debugging and testing purposes). However, preceding the command line with "setarch i386" does not help. The exact command line used was jackd -d alsa -X raw -d hw:0 To trigger the bug, it is important that there actually is a raw Midi device available on the system. Any such device will trigger the problem in my experience. Here is the complete output: jackdmp 1.9.11 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 2 periods for playback scan: added port hw:1,0,0 in-hw-1-0-0-UM-4-MIDI-1 scan: added port hw:1,0,1 in-hw-1-0-1-UM-4-MIDI-2 scan: added port hw:1,0,2 in-hw-1-0-2-UM-4-MIDI-3 scan: added port hw:1,0,3 in-hw-1-0-3-UM-4-MIDI-4 scan: added port hw:1,0,0 out-hw-1-0-0-UM-4-MIDI-1 scan: added port hw:1,0,1 out-hw-1-0-1-UM-4-MIDI-2 scan: added port hw:1,0,2 out-hw-1-0-2-UM-4-MIDI-3 scan: added port hw:1,0,3 out-hw-1-0-3-UM-4-MIDI-4 ALSA lib rawmidi_hw.c:100:(snd_rawmidi_hw_params) SNDRV_RAWMIDI_IOCTL_PARAMS failed: Invalid argument jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. Aborted (core dumped) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17 Uname: Linux 4.10.0-26-lowlatency x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AssertionMessage: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. CurrentDesktop: MATE Date: Sun Jul 9 10:27:38 2017 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2094 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: jackd -d alsa -X raw -d hw:0 Signal: 6 SourcePackage: jackd2 StacktraceTop: __assert_fail_base (fmt=0xf743009c "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0xf6f38cd3 "err >= 0", file=0xf6f48d35 "rawmidi.c", line=268, function=0xf6f49588 "snd_rawmidi_open_conf") at assert.c:92 __GI___assert_fail (assertion=0xf6f38cd3 "err >= 0", file=0xf6f48d35 "rawmidi.c", line=268, function=0xf6f49588 "snd_rawmidi_open_conf") at assert.c:101 () at /usr/lib/i386-linux-gnu/libasound.so.2 () at /usr/lib/i386-linux-gnu/libasound.so.2 snd_rawmidi_open () at /usr/lib/i386-linux-gnu/libasound.so.2 Title: jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. UpgradeStatus: Upgraded to artful on 2017-05-03 (66 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1703176/+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 1711132] Re: make crashed with SIGSEGV in variable_hash_1()
[Expired for make-dfsg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: make-dfsg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1711132 Title: make crashed with SIGSEGV in variable_hash_1() Status in make-dfsg package in Ubuntu: Expired Bug description: i don't know ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: make 4.1-9.1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 Date: Wed Aug 16 17:37:40 2017 Dependencies: gcc-7-base 7.1.0-13ubuntu1 libc6 2.24-12ubuntu1 libgcc1 1:7.1.0-13ubuntu1 ExecutablePath: /usr/bin/make InstallationDate: Installed on 2017-08-02 (14 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) ProcCmdline: make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-375/375.82/build ProcEnviron: LC_COLLATE=C PATH=(custom, no user) LC_NUMERIC=C LANG=en_US.UTF-8 TERM=linux SegvAnalysis: Segfault happened at: 0x698913f28f: movzbl (%rax),%esi PC (0x698913f28f) ok source "(%rax)" (0x406989d94420) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: make-dfsg StacktraceTop: ?? () hash_find_slot () target_environment () ?? () ?? () Title: make crashed with SIGSEGV in hash_find_slot() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1711132/+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 1705570] Re: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped()
[Expired for jackd2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: jackd2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1705570 Title: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped() Status in jackd2 package in Ubuntu: Expired Bug description: Started jackd (version 2) with jackd -d firewire -r 96000 and had a Mackie Onyx 1620 (with Firewire extension card) and an Alesis iO|14 connected in series. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency i686 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 20 22:22:11 2017 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2106 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: jackd -d firewire -r 96000 SegvAnalysis: Segfault happened at: 0xb5e9df68 <_ZN9Streaming15StreamProcessor14packetsStoppedEv+16>: movl $0x2,0x34(%eax) PC (0xb5e9df68) ok source "$0x2" ok destination "0x34(%eax)" (0x0034) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: jackd2 StacktraceTop: Streaming::StreamProcessor::packetsStopped() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::disable() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::~IsoHandler() () at /usr/lib/libffado.so.2 IsoHandlerManager::pruneHandlers() () at /usr/lib/libffado.so.2 IsoHandlerManager::unregisterStream(Streaming::StreamProcessor*) () at /usr/lib/libffado.so.2 Title: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1705570/+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 1716126] Re: mobile broadband connection can't be added
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1716126 Title: mobile broadband connection can't be added Status in network-manager package in Ubuntu: Expired Bug description: Ubuntu Mate Beta1 amd64 live-iso I tried adding a Mobile Broadband Connection (LTE), i clicked "New Mobile Broadband connection..." in the drop-down Network Menu from Desktop. I Followed the dialog and selected My Country and my Network-provider after the last step a error-message pops up: title: "Connection failure" "Failed to add/activate connection" "(7) gsm.username: property is empty" [Close] No new connection is added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1716126/+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 1725631] Re: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width()
[Expired for gdk-pixbuf (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdk-pixbuf (Ubuntu) Status: Incomplete => Expired -- 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/1725631 Title: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width() Status in gdk-pixbuf package in Ubuntu: Expired Status in mate-dock-applet package in Ubuntu: Expired Bug description: I had just installed Planner 0.14.6 and attempting to move the dock icon which disappeared and the crash occurred. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: mate-dock-applet 0.79-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 21 11:37:17 2017 ExecutablePath: /usr/lib/mate-applets/mate-dock-applet/dock_applet.py InstallationDate: Installed on 2017-09-29 (21 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterpreterPath: /usr/bin/python3.6 ProcCmdline: python3 /usr/lib/mate-applets/mate-dock-applet/dock_applet.py ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb63b6d5246 : cmp %rax,(%rdx) PC (0x7fb63b6d5246) ok source "%rax" ok destination "(%rdx)" (0x7fb63dd4ff3abb49) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-dock-applet StacktraceTop: gdk_pixbuf_get_width () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1725631/+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 1725631] Re: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width()
[Expired for mate-dock-applet (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-dock-applet (Ubuntu) Status: Incomplete => Expired -- 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/1725631 Title: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width() Status in gdk-pixbuf package in Ubuntu: Expired Status in mate-dock-applet package in Ubuntu: Expired Bug description: I had just installed Planner 0.14.6 and attempting to move the dock icon which disappeared and the crash occurred. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: mate-dock-applet 0.79-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 21 11:37:17 2017 ExecutablePath: /usr/lib/mate-applets/mate-dock-applet/dock_applet.py InstallationDate: Installed on 2017-09-29 (21 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterpreterPath: /usr/bin/python3.6 ProcCmdline: python3 /usr/lib/mate-applets/mate-dock-applet/dock_applet.py ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb63b6d5246 : cmp %rax,(%rdx) PC (0x7fb63b6d5246) ok source "%rax" ok destination "(%rdx)" (0x7fb63dd4ff3abb49) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-dock-applet StacktraceTop: gdk_pixbuf_get_width () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1725631/+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 1725019] Re: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1725019 Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Expired Bug description: upgrading ubuntu-mate ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 Uname: Linux 4.1.18-v7+ armv7l ApportVersion: 2.20.7-0ubuntu3 Architecture: armhf Date: Thu Oct 19 18:20:45 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725019/+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 1728253] Re: package dictionaries-common 1.27.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
[Expired for dictionaries-common (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dictionaries-common (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1728253 Title: package dictionaries-common 1.27.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in dictionaries-common package in Ubuntu: Expired Bug description: freezing on upgrade clock ,processes etc... ProblemType: Package DistroRelease: Ubuntu 17.10 Package: dictionaries-common 1.27.2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: i386 Date: Sat Oct 28 10:33:01 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2017-10-28 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170829.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: dictionaries-common Title: package dictionaries-common 1.27.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1728253/+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 1359308] Re: crash due to assertion in gail_focus_notify_when_idle: code should not be reached
[Expired for gtk+2.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+2.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1359308 Title: crash due to assertion in gail_focus_notify_when_idle: code should not be reached Status in gtk+2.0 package in Ubuntu: Expired Bug description: On an Ubuntu MATE utopic amd64 system, mate-panel 1.8.0+dfsg1-2 crashed when I clicked on an item in the window list (located in the bottom panel). The panel reappeared and continued working correctly. This happened while apt-get was upgrading packages, but mate-panel was not one of the packages being upgraded. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-panel 1.8.0+dfsg1-2 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 Date: Wed Aug 20 13:21:43 2014 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2014-08-19 (1 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731) ProcCmdline: mate-panel ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1359308/+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 1377434] Re: Ubuntu Mate 14.10 Beta 2 upower error on system startup
[Expired for upower (Ubuntu) because there has been no activity for 60 days.] ** Changed in: upower (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1377434 Title: Ubuntu Mate 14.10 Beta 2 upower error on system startup Status in upower package in Ubuntu: Expired Bug description: Ubuntu Mate 14.10 Beta 2 upower error when starting system. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Sat Oct 4 07:30:10 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-09-26 (7 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta2 amd64 (20140925) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1377434/+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 1369958] Re: indicator-keyboard crashes in Ubuntu MATE live installer
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- 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/1369958 Title: indicator-keyboard crashes in Ubuntu MATE live installer Status in lightdm package in Ubuntu: Expired Bug description: I am the maintainer of Ubuntu MATE Remix, we are currently working towards being an official Ubuntu flavour. While trying to resolve an issue with lightdm crashing (https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1369952) I noticed .xsession-errors was complaining indicators were not available in the live installer. I have recently added the following indicators to the live installer: * indicator-application * indicator-datetime * indicator-keyboard * indicator-power * indicator-session The others appear to be working correctly but I just found crash dump in /var/crash for indicator-keyboard. You can download a Ubuntu MATE iso image that exhibits this issue from https://ubuntu- mate.org/1369958/ ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: indicator-keyboard 0.0.0+14.10.20140620.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CasperVersion: 1.344 Date: Tue Sep 16 09:06:58 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service LiveMediaBuild: Ubuntu MATE 14.10 "Utopic Unicorn" - pre-beta2.25818 amd64 (20140915) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= Signal: 5 SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1369958/+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 1367098] Re: Pulseaudio doesn't start at boot
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1367098 Title: Pulseaudio doesn't start at boot Status in pulseaudio package in Ubuntu: Expired Bug description: It's been happening for a week now. When I log in, I hear no sound, and when I check the sound setup and it shows no sound card. I tried to kill pulseaudio and then restart it, but sometimes it can't even be killed. The most embarrasing thing about this is that the system cannot be shut down properly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mate 1947 F pulseaudio /dev/snd/controlC0: mate 1947 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 9 06:43:45 2014 InstallationDate: Installed on 2014-04-20 (141 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Pumori dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.20:bd10/24/2012:svnTOSHIBA:pnSATELLITEC855D-15V:pvrPSKD6E-005004HU:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C855D-15V dmi.product.version: PSKD6E-005004HU dmi.sys.vendor: TOSHIBA modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2014-06-08T06:32:23.092640 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1367098/+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 1376249] Re: Ubuntu Mate 14.10 Beta2 Upowerd package error message during boot
[Expired for upower (Ubuntu) because there has been no activity for 60 days.] ** Changed in: upower (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1376249 Title: Ubuntu Mate 14.10 Beta2 Upowerd package error message during boot Status in upower package in Ubuntu: Expired Bug description: Error message during boot-up of Ubuntu Mate 14.10 Beta2. No further information. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Wed Oct 1 07:55:04 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-09-26 (4 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta2 amd64 (20140925) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1376249/+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 1399854] Re: Hangs at logoff or shutdown
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- 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/1399854 Title: Hangs at logoff or shutdown Status in lightdm package in Ubuntu: Expired Bug description: I use a desktop environment MATE. When I try to shut down the computer or log off the screen freezes for 30 seconds, then turns black. The computer does not respond to keyboard and mouse, I can turn it off only with the aid of keys Alt + SysRq + O. After installing the kernel http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.17.1-utopic/ problem disappeared. If you are using the latest kernel from the repository or http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.16.7-ckt2-utopic/ problem exists. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 6 05:57:38 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.lightdm.conf: [modified] mtime.conffile..etc.init.lightdm.conf: 2014-11-12T21:32:04.127872 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1399854/+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 1405976] Re: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it b
[Expired for jackd2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: jackd2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1405976 Title: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in jackd2 package in Ubuntu: Expired Bug description: I was loading the Mate desktop through the terminal while browsing with Chromium when eventoccurred. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 27 11:30:18 2014 DuplicateSignature: package:libjack-jackd2-0:i386:1.9.9.5+20130622git7de15e7a-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-08-19 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: i386 SourcePackage: jackd2 Title: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1405976/+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 1434402] Re: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы
[Expired for fontconfig (Ubuntu) because there has been no activity for 60 days.] ** Changed in: fontconfig (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1434402 Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы Status in fontconfig package in Ubuntu: Expired Bug description: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fontconfig 2.11.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 Date: Fri Mar 20 08:52:32 2015 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2015-03-19 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha amd64 (20150225) SourcePackage: fontconfig Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1434402/+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 1429222] Re: lightdm fails to start on boot of ubuntu mate but starts when restarted
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- 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/1429222 Title: lightdm fails to start on boot of ubuntu mate but starts when restarted Status in lightdm package in Ubuntu: Expired Bug description: boot March 6th daily ubuntu mate installation went fine restarted got to grub started up and did not load any further switched to tty and no gui or splash screen came up. I switched to tty 1 and was able to login. lightdm: Installed: 1.13.1-0ubuntu2 Candidate: 1.13.1-0ubuntu2 Version table: *** 1.13.1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 to reproduce install ubuntu-mate using manaul partitioning using an ext4 / partition and reusing an xfs /home. I expected lightdm to come up and display a GUI and I could get it to start by restarting it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 6 09:45:52 2015 InstallationDate: Installed on 2015-03-06 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1429222/+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 1439074] Re: GDB (multiarch) crashed while debugging optimized ARM code
[Expired for gdb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1439074 Title: GDB (multiarch) crashed while debugging optimized ARM code Status in gdb package in Ubuntu: Expired Bug description: I have a code in which some of functions are optimized but some not. So when I try to debug unoptimized function called from optimized one then gdb have produced an error and wanted to exit: /build/buildd/gdb-7.7.1/gdb/inline-frame.c:168: internal-error: inline_frame_this_id: Assertion `frame_id_p (*this_id)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdb-multiarch 7.7.1-0ubuntu5~14.04.2 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: MATE Date: Wed Apr 1 12:03:46 2015 InstallationDate: Installed on 2014-07-14 (261 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1439074/+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 1441754] Re: package emacs24 24.4+1-4ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for dictionaries-common (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dictionaries-common (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1441754 Title: package emacs24 24.4+1-4ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in dictionaries-common package in Ubuntu: Expired Bug description: . ProblemType: Package DistroRelease: Ubuntu 15.04 Package: emacs24 24.4+1-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Wed Apr 8 19:02:45 2015 DuplicateSignature: package:emacs24:24.4+1-4ubuntu5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-02-13 (54 days ago) InstallationMedia: Ubuntu MATE 15.04 "Vivid Vervet" - Alpha2 amd64 (20150123) RelatedPackageVersions: dpkg 1.17.24ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: emacs24 Title: package emacs24 24.4+1-4ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1441754/+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 1448605] Re: package libsqlite3-0:i386 3.8.7.4-1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured
[Expired for sqlite3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: sqlite3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1448605 Title: package libsqlite3-0:i386 3.8.7.4-1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured Status in sqlite3 package in Ubuntu: Expired Bug description: Don't know, I am relatively new to bug reports! ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libsqlite3-0:i386 3.8.7.4-1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3 Architecture: amd64 CrashReports: 600:0:119:438468:2015-04-26 16:57:42.337173223 +1000:2015-04-26 16:57:43.337173223 +1000:/var/crash/libssl1.0.0:i386.0.crash 640:1000:119:15552325:2015-04-25 16:09:33.959912807 +1000:2015-04-25 18:53:09.238786763 +1000:/var/crash/_usr_bin_caja.1000.crash 600:0:119:438463:2015-04-26 16:57:42.313156604 +1000:2015-04-26 16:57:43.313156604 +1000:/var/crash/libsqlite3-0:i386.0.crash 600:0:119:438462:2015-04-26 16:57:43.249112800 +1000:2015-04-26 16:57:41.792113154 +1000:/var/crash/libjson-c2:i386.0.crash Date: Sun Apr 26 16:57:43 2015 Dependencies: gcc-5-base 5.1~rc1-0ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.1~rc1-0ubuntu1 multiarch-support 2.21-0ubuntu4 DuplicateSignature: package:libsqlite3-0:i386:3.8.7.4-1:package libsqlite3-0:i386 is already installed and configured ErrorMessage: package libsqlite3-0:i386 is already installed and configured InstallationDate: Installed on 2015-04-25 (1 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: sqlite3 Title: package libsqlite3-0:i386 3.8.7.4-1 failed to install/upgrade: package libsqlite3-0:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1448605/+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 1460347] Re: B43 did not offer channel 11-13
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1460347 Title: B43 did not offer channel 11-13 Status in network-manager package in Ubuntu: Expired Bug description: Ubuntu Mate 15.04 i386 / Lenovo ideapad S10-2 / Broadcom 4312 After install simple login and take a look at available wlans in the area. You will see all between 1 and 10, but none in the 11-13 range. It's also not possible to connect them as hidden network. In physical this machine was shipped with windows and it can use full range in Europe / Germany Under ubuntu we see: eric@selene:~$ iwlist chan wlan0 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Full range but network-manager is in denial of that. eric@selene:~$ iw reg get country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 40), (N/A, 20), (N/A), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), (0 ms), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), (0 ms), DFS (57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: MATE Date: Sat May 30 23:17:24 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-30 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 (20150422.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.101 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Elysion20 30f1d787-c4d3-4652-950f-e656990cbe9d 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- Kabelnetzwerkverbindung 1 aae849bd-3bcc-49fb-bd6c-8aff25c05e51 802-3-ethernet 1433020571 Sa 30 Mai 2015 23:16:11 CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/2 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Kabelnetzwerkverbindung 1 aae849bd-3bcc-49fb-bd6c-8aff25c05e51 /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- ttyACM1 gsm unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1460347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1481449] Re: DBUS racing condition on pluma and other application
[Expired for dbus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1481449 Title: DBUS racing condition on pluma and other application Status in dbus package in Ubuntu: Expired Bug description: just typing in a shell (logged with my current user) : pluma file& generate this warning: trebe03@m193543:~/bin$ pluma youtube-dl.py & [1] 19036 trebe03@m193543:~/bin$ ** (pluma:19036): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-UF9kBx3qDw: Connexion refusée [1]+ Finipluma youtube-dl.py trebe03@m193543:~/bin$ and this bug was generated by typing : trebe03@m193543:~$ ubuntu-bug dbus ** (apport-gtk:20256): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-UF9kBx3qDw: Connexion refusée (process:20711): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed trebe03@m193543:~$ It doesn't disturb much the OS but is annoying the user. ;=) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dbus 1.8.12-1ubuntu5 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 4 14:54:03 2015 InstallationDate: Installed on 2015-07-22 (12 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150721) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1481449/+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 1502747] Re: package libssl1.0.0:i386 1.0.2d-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
[Expired for openssl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssl (Ubuntu) Status: Incomplete => Expired -- 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/1502747 Title: package libssl1.0.0:i386 1.0.2d-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in openssl package in Ubuntu: Expired Bug description: initializing with this problem ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libssl1.0.0:i386 1.0.2d-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 Date: Mon Oct 5 00:10:21 2015 DuplicateSignature: package:libssl1.0.0:i386:1.0.2d-0ubuntu1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2015-09-21 (14 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.9.7ubuntu4.1 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2d-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1502747/+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 1504981] Re: package shared-mime-info 1.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 143
[Expired for shared-mime-info (Ubuntu) because there has been no activity for 60 days.] ** Changed in: shared-mime-info (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1504981 Title: package shared-mime-info 1.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 143 Status in shared-mime-info package in Ubuntu: Expired Bug description: bug reporting tool ProblemType: Package DistroRelease: Ubuntu 15.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 3.16.0-37.51-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Mon Oct 5 23:00:42 2015 DuplicateSignature: package:shared-mime-info:1.3-1:subprocess installed post-installation script returned error exit status 143 ErrorMessage: subprocess installed post-installation script returned error exit status 143 InstallationDate: Installed on 2015-03-31 (194 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 143 UpgradeStatus: Upgraded to vivid on 2015-05-24 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1504981/+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 1581820] Re: lightdm does not work, no background is displayed
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- 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/1581820 Title: lightdm does not work, no background is displayed Status in lightdm package in Ubuntu: Expired Bug description: None background user is displayed on the login screenand it is impossible to remove the system directory /var/lib/lightdm-date/lightdm ~$ lightdm --test-mode /bin/rm: can not remove '/var/lib/lightdm-date/lightdm": Permission denied ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39 Uname: Linux 3.13.0-86-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: MATE Date: Sat May 14 16:24:21 2016 InstallationDate: Installed on 2015-08-25 (263 days ago) InstallationMedia: LightdmConfig: [SeatDefaults] user-session=mate greeter-session=lightdm-gtk-greeter greeter-setup-script=/usr/bin/numlockx on allow-guest=true LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Jun 17 2015, 00:46:44) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf ** (lightdm-gtk-greeter:2201): WARNING **: [PIDs] Failed to execute command: upstart SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2016-01-22 (112 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581820/+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 1572057] Re: rhythmbox not start the files of a mtp device connected
[Expired for gstreamer1.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer1.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1572057 Title: rhythmbox not start the files of a mtp device connected Status in gstreamer1.0 package in Ubuntu: Expired Bug description: $ rhythmbox (rhythmbox:14782): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (rhythmbox:14782): Gtk-CRITICAL **: gtk_css_provider_load_from_path: assertion 'path != NULL' failed (rhythmbox:14782): GLib-GObject-CRITICAL **: object SoupServer 0x99184f8 finalized while still in-construction (rhythmbox:14782): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead. (rhythmbox:14782): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files segmentation fault ( core dump created ) lsb_release -rd Description: Ubuntu 14.04.4 LTS Release: 14.04 CurrentDesktop: MATE Architecture: i386 $ apt-cache policy libgstreamer* libgstreamer-plugins-bad1.0-0: Installed: 1.2.4-1~ubuntu1 Candidate: 1.2.4-1~ubuntu1 version table: *** 1.2.4-1~ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe i386 Packages 100 /var/lib/dpkg/status 1.2.3-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages libgstreamer-perl: Installato: (nessuno) Candidato: 0.19-1 version table: 0.19-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages libgstreamer0.10-0: Installato: 0.10.36-1.2ubuntu3 Candidato: 0.10.36-1.2ubuntu3 version table: *** 0.10.36-1.2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status libgstreamer-plugins-base1.0-0: Installato: 1.2.4-1~ubuntu2 Candidato: 1.2.4-1~ubuntu2 version table: *** 1.2.4-1~ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 1.2.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages libgstreamer-plugins-bad0.10-dev: Installato: (nessuno) Candidato: 0.10.23-7.2ubuntu1.1 version table: 0.10.23-7.2ubuntu1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe i386 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/universe i386 Packages 0.10.23-7.2ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages libgstreamer-plugins-good1.0-0: Installato: 1.2.4-1~ubuntu1 Candidato: 1.2.4-1~ubuntu1 version table: *** 1.2.4-1~ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 1.2.3-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages libgstreamer-plugins-base0.10-dev: Installato: (nessuno) Candidato: 0.10.36-1.1ubuntu2 version table: 0.10.36-1.1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages libgstreamer1.0-0-dbg: Installato: (nessuno) Candidato: 1.2.4-0ubuntu1 Tabella versione: 1.2.4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 1.2.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages libgstreamer-ocaml-dev-gb8r9: Installato: (nessuno) Candidato: (nessuno) version table: libgstreamer-plugins-base0.10-0: Installato: 0.10.36-1.1ubuntu2 Candidato: 0.10.36-1.1ubuntu2 version table: *** 0.10.36-1.1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status libgstreamer0.10-dev: Installato: 0.10.36-1.2ubuntu3 Candidato: 0.10.36-1.2ubuntu3 version table: *** 0.10.36-1.2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status libgstreamer-plugins-base1.0-dev: Installato: (nessuno) Candidato: 1.2.4-1~ubuntu2 version table: 1.2.4-1~ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 1.2.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages libgstreamer0.10-cil-dev: Installato: (nessuno) Candidato: 0.9.2-4ubuntu1 version table: 0.9.2-4ubuntu1 0
[Touch-packages] [Bug 1638283] Re: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1638283 Title: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 Status in mesa package in Ubuntu: Expired Bug description: This resulted from trying to install libgli from http://packages.ubuntu.com/trusty/i386/libgl1-mesa-dri/download Presumably, it's the wrong package? Following the instructions below: ubuntu-bug mesa failed reporting that it wasn't installed. Well that was because the installation was what failed. rrogers@rrogers-desktop:~/tmp$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 rrogers@rrogers-desktop:~/tmp$ apt-cache policy libgl1-mesa-dri* N: Unable to locate package libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb N: Couldn't find any package by regex 'libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb' Ray ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Oct 31 17:16:07 2016 DpkgTerminalLog: Preparing to unpack .../libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb ... Unpacking libgl1-mesa-dri:i386 (10.1.3-0ubuntu0.6) over (10.1.0-4ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz]:trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 InstallationDate: Installed on 2016-10-19 (12 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: mesa Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1638283/+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 1612181] Re: package libgtk-3-0-dbg 3.10.8-0ubuntu1.6 failed to install/upgrade: trying to overwrite shared '/usr/lib/debug/usr/bin/gtk3-demo-application', which is different fro
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Expired -- 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/1612181 Title: package libgtk-3-0-dbg 3.10.8-0ubuntu1.6 failed to install/upgrade: trying to overwrite shared '/usr/lib/debug/usr/bin/gtk3-demo- application', which is different from other instances of package libgtk-3-0-dbg:i386 Status in gtk+3.0 package in Ubuntu: Expired Bug description: any fix? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgtk-3-0-dbg 3.10.8-0ubuntu1.6 ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-77-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Aug 11 18:36:34 2016 DuplicateSignature: package:libgtk-3-0-dbg:3.10.8-0ubuntu1.6:trying to overwrite shared '/usr/lib/debug/usr/bin/gtk3-demo-application', which is different from other instances of package libgtk-3-0-dbg:i386 ErrorMessage: trying to overwrite shared '/usr/lib/debug/usr/bin/gtk3-demo-application', which is different from other instances of package libgtk-3-0-dbg:i386 InstallationDate: Installed on 2016-08-11 (0 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: gtk+3.0 Title: package libgtk-3-0-dbg 3.10.8-0ubuntu1.6 failed to install/upgrade: trying to overwrite shared '/usr/lib/debug/usr/bin/gtk3-demo-application', which is different from other instances of package libgtk-3-0-dbg:i386 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/1612181/+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 1903916] Re: Default keys cannot be restored from keyserver
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903916 Title: Default keys cannot be restored from keyserver Status in software-properties package in Ubuntu: Expired Bug description: Hi all, the default keys for trustworthy software sources are gone (or at least won't display) in software-properties-gtk in Groovy Gorilla MATE. I tried to recreate them by using the button in bottom right corner. After entering system password no change seems to be done. However, keyserver de.archive.ubuntu.com seems to work for updates. Can this be fixed easily? Kind regards Stefan ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 22:06:38 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-09-25 (778 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to groovy on 2020-11-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903916/+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 1650688] Re: timedatectl set-timezone fails on UC16
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: New Bug description: Impish feature freeze bug fix (sort of) exception request = I (Ratchanan) would like ubuntu-release to verify if the proposed merge for Impish qualify as a bug fix per [1]. Strictly speaking, as there's no core snap from an interim release, this issue doesn't directly effect Impish. However, to comply with the SRU requirement, and to let the patches carry to the 22.04 release, I would like this to be included in Impish. One of the patch has a small possibility to create a problem on classic systems, so testing in a development release is a good idea. Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [2] on the system. [1] https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_for_bugfix-only_updates [2] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-core/hooks/08-etc-writable.chroot?h=ubuntu/focal - SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link
[Touch-packages] [Bug 1945418] Re: Hibernate doesn't support as the default action in Ubuntu when critical power
@seb128,
got it, I created this one for discussion.
https://gitlab.freedesktop.org/upower/upower/-/issues/156
** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #156
https://gitlab.freedesktop.org/upower/upower/-/issues/156
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1945418
Title:
Hibernate doesn't support as the default action in Ubuntu when
critical power
Status in OEM Priority Project:
Confirmed
Status in gnome-settings-daemon package in Ubuntu:
New
Status in upower package in Ubuntu:
New
Bug description:
In a stock ubuntu 20.04.3, g-s-d will notify the critical action when battery
is lower than warned critical threshold.
The notification is "The battery is below the critical level and this
computer is about to hibernate."
When hitting critical threshold, it takes "HybirdSleep" as the action.
```
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd[1]: Reached target Sleep.
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd[1]: Starting Hybrid Suspend+Hibernate...
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
kernel: PM: Image not found (code -22)
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd-sleep[3212]: Suspending system...
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
kernel: PM: hibernation: hibernation entry
```
You could see the hibernation called by logind but it will fail to
restore since either not enough SWAP or resume address is not specify
to kernel.
It confusing users about the critical actions.
In UPower.conf:
```
$ tail etc/UPower.conf
# reached for the batteries (UPS or laptop batteries) supplying the computer
#
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
#
# If HybridSleep isn't available, Hibernate will be used
# If Hibernate isn't available, PowerOff will be used
CriticalPowerAction=HybridSleep
```
In g-s-d:
```
/* We don't make the difference between HybridSleep and Hibernate
*/
if (g_strcmp0 (action, "PowerOff") == 0)
policy = GSD_POWER_ACTION_SHUTDOWN;
else
policy = GSD_POWER_ACTION_HIBERNATE;
...
/* use different text for different actions */
if (policy == GSD_POWER_ACTION_HIBERNATE) {
/* TRANSLATORS: computer will hibernate */
message = g_strdup (_("The battery is below the
critical level and "
"this computer is about to
hibernate."));
```
There are two approach if possible:
1) change "CriticalPowerAction" to "PowerOff" because the suspend to ram is
almost useless when battery is in critical threshold and the suspend to disk is
usually not working in default installed ubuntu.
2) have a new "GsdPowerActionType" type for "HybridSleep" to show the
appropriate message but taking the same action (notify logind).
---
$ dpkg -l | grep -i 'upower\|gnome-settings-daemon'
ii gir1.2-upowerglib-1.0:amd640.99.11-1build2
amd64GObject introspection data for upower
ii gnome-settings-daemon 3.36.1-0ubuntu1.1
amd64daemon handling the GNOME session settings
ii gnome-settings-daemon-common 3.36.1-0ubuntu1.1
all daemon handling the GNOME session settings - common files
ii libupower-glib3:amd64 0.99.11-1build2
amd64abstraction for power management - shared library
ii upower 0.99.11-1build2
amd64abstraction for power managemen
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1945418/+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 1945535] Re: Xorg freeze
*** This bug is a duplicate of bug 1944397 *** https://bugs.launchpad.net/bugs/1944397 It seems to be the vc4 kernel driver (Broadcom graphics) that keeps crashing. I suggest we treat this as a duplicate of bug 1944397 unless proven otherwise. ** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu) ** This bug has been marked a duplicate of bug 1944397 HDMI does not display anything with Impish RPi desktop image -- 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/1945535 Title: Xorg freeze Status in linux-raspi package in Ubuntu: New Bug description: gnome constantly freezes on ubuntu 21.10. steps to reproduce: open chromium-browser Click on the top bar gnome freezes instantly, requiring a hard reset. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-1007.8-hostname 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:39:12 2021 DistUpgraded: 2021-09-29 14:59:02,376 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1360x768M@60 smsc95xx.macaddr=E4:5F:01:2C:45:7B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1945535/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1944107] Re: No archive files for static compilation are included in the -dev package
This bug was fixed in the package libdrm - 2.4.107-8 --- libdrm (2.4.107-8) unstable; urgency=medium * rules: Forcibly disable valgrind. -- Timo Aaltonen Mon, 27 Sep 2021 20:10:39 +0300 ** Changed in: libdrm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1944107 Title: No archive files for static compilation are included in the -dev package Status in libdrm package in Ubuntu: Fix Released Bug description: There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not possible to compile statically against this library. See attached debdiff to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+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 1945465] Re: Can't turn bluetooth on
Is it because you updated the kernel or linux-firmware recently? If possible, please roll back previous kernel to have a test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1945465 Title: Can't turn bluetooth on Status in alsa-driver package in Ubuntu: New Bug description: When I try to turn on my bluetooth, it simply doesn't turn on. This just came from one day to another. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pc27999 F pulseaudio /dev/snd/pcmC0D0p: pc27999 F...m pulseaudio /dev/snd/controlC1: pc27999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:02:30 2021 InstallationDate: Installed on 2021-06-28 (93 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac12,1:pvr1.0:sku:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1945465/+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 1945527] Re: Update tzdata to version 2021a-2
** Also affects: tzdata (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
In Progress
Status in tzdata source package in Focal:
In Progress
Status in tzdata source package in Hirsute:
In Progress
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
As seb128 found, the issue is also affecting the debian package of snapd since when we call mksquashfs, we actually have code which specifically calls mksquashfs from the "system" snap which is either the snapd snap or the core snap, this is presumably to ensure that a consistent mksquashfs is used always and to avoid snaps from being packed with too old or new mksquashfs's. So the net effect is that the fix for this that was landed into the snapd snap will also probably need to be added to the core snap for completeness, and also means that the only way to avoid snap pack from failing is to have a snapd snap with the fix which is only available on the edge channel currently. So long story short, if you are affected by this today, a short-term workaround is to use the edge channel of the snapd snap by running snap refresh snapd --edge We have already included the fix into the snapd snap that is built on edge and it will be included in the release branch for 2.52, meaning that the next bugfix release on 2.52 will have the fix, we do plan on doing a 2.52.1 release in short order after 2.52 is complete, but it may be a few weeks from now before that is on stable. ** Changed in: snapd Milestone: None => 2.52 -- 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/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: Fix Committed Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1945535] [NEW] Xorg freeze
Public bug reported: gnome constantly freezes on ubuntu 21.10. steps to reproduce: open chromium-browser Click on the top bar gnome freezes instantly, requiring a hard reset. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-1007.8-hostname 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:39:12 2021 DistUpgraded: 2021-09-29 14:59:02,376 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1360x768M@60 smsc95xx.macaddr=E4:5F:01:2C:45:7B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image freeze impish raspi-image third-party-packages ubuntu wayland-session -- 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/1945535 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: gnome constantly freezes on ubuntu 21.10. steps to reproduce: open chromium-browser Click on the top bar gnome freezes instantly, requiring a hard reset. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-1007.8-hostname 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:39:12 2021 DistUpgraded: 2021-09-29 14:59:02,376 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1360x768M@60 smsc95xx.macaddr=E4:5F:01:2C:45:7B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1
[Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
** Changed in: indicator-sound (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: Fix Committed Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1945527] Re: Update tzdata to version 2021a-2
** Changed in: tzdata (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: tzdata (Ubuntu Focal)
Status: New => In Progress
** Changed in: tzdata (Ubuntu Bionic)
Status: New => In Progress
** Changed in: tzdata (Ubuntu Bionic)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: tzdata (Ubuntu Focal)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: tzdata (Ubuntu Hirsute)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
In Progress
Status in tzdata source package in Focal:
In Progress
Status in tzdata source package in Hirsute:
In Progress
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
This bug was fixed in the package linux-firmware - 1.201 --- linux-firmware (1.201) impish; urgency=medium * Rebase to upstream commit 7a30050592e20f494ad331b90737913d59167c3f Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - i915: Update ADLP DMC v2.12 - amdgpu: add initial firmware for Yellow Carp (LP: #1945227) - iwlwifi: add FWs for new So device types with multiple RF modules - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - qed: Add firmware 8.59.1.0 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - cxgb4: Update firmware to revision 1.26.2.0 - amdgpu: Add initial firmware for Beige Goby - amdgpu: update VCN firmware for raven - amdgpu: update VCN firmware for raven2 - amdgpu: update VCN firmware for picasso - amdgpu: update VCN firmware for renoir - amdgpu: update VCN firmware for vangogh - amdgpu: update VCN firmware for sienna cichlid - amdgpu: update VCN firmware for navy flounder - amdgpu: update VCN firmware for dimgrey cavefish - linux-firmware: Update firmware file for Intel Bluetooth 9462 - brcm: Add 43455 based AP6255 NVRAM for the ACEPC T8 Mini PC -- Timo Aaltonen Wed, 29 Sep 2021 11:36:54 +0300 ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-465 (Ubuntu) Status: New => Confirmed -- 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/1933880 Title: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a restart, run `sudo apt autoremove nvidia-driver-465`. 2. Leaving the terminal open, suspend the machine. Expected behavior: the machine suspend successfully and can be woken up successfully. Actual behavior: the machine doesn't suspend. It either: - hang with no respond other than SysRq+REISUB (or maybe network, but I didn't test), or - return you back to the login screen. Upon logging in, you'll notice that the terminal you opened is gone. Upon further inspection (on a session that doesn't hang), it's been found that X server died with: Fatal server error: [66.422] (EE) systemd-logind disappeared (stopped/restarted?) And checking journal for systemd-logind log, it said: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service is masked. before the new process takes it place. The system is Ubuntu 20.04, X.org session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 03:34:00 2021 InstallationDate: Installed on 2021-03-15 (105 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=th_TH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+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 1945527] [NEW] Update tzdata to version 2021a-2
Public bug reported:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets changed
in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed. If
those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut
-d' ' -f2-)
Nothing should be returned by the above command.
** Affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
** Affects: tzdata (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: tzdata (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1945527
Title:
Update tzdata to version 2021a-2
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
New
Status in tzdata source package in Focal:
New
Status in tzdata source package in Hirsute:
New
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Pacific/Apia
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Pacific/Apia | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+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 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu
** Information type changed from Private to Public -- 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/1856480 Title: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu Status in cups package in Ubuntu: New Bug description: Whenever I attempt to print a document to a printer over the network, Ubuntu finds the printer and acts as if it is configured until I actually send a print job. When I do this, I get a message that says "Printing" in LibreOffice, but then nothing happens because the printers are not configured according to Ubuntu. I expected the document I sent over the network to print without issue. However, I am unable to on ubuntu because it is apparently not configured. Description: Ubuntu 19.10 Release: 19.10 cups: Installed: 2.2.12-2ubuntu1 Candidate: 2.2.12-2ubuntu1 Version table: *** 2.2.12-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 15:01:50 2019 InstallationDate: Installed on 2019-11-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Officejet_Pro_8600_AB0C33_: ipp://HP843497AB0C33.local:631/ipp/printer Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 Papersize: letter ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Officejet_Pro_8600_AB0C33_: ipp://HP843497AB0C33.local:631/ipp/printer Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 Package: cups 2.2.12-2ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 To manage notifications about
[Touch-packages] [Bug 1944419] Re: vim: impish missing in debchangelog.vim
This bug was fixed in the package vim - 2:8.2.2434-3ubuntu3 --- vim (2:8.2.2434-3ubuntu3) impish; urgency=medium * Add impish to supported releases (LP: #1944419) -- Heinrich Schuchardt Tue, 21 Sep 2021 10:39:53 +0200 ** Changed in: vim (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1944419 Title: vim: impish missing in debchangelog.vim Status in vim package in Ubuntu: Fix Released Bug description: debchangelog.vim and debsources.vim are used for syntax highlighting in vim. impish is missing in the list of supported Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1944419/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
@Khurshid: Please see comment on the merge request. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1650688] Re: timedatectl set-timezone fails on UC16
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: New Bug description: Impish feature freeze bug fix (sort of) exception request = I (Ratchanan) would like ubuntu-release to verify if the proposed merge for Impish qualify as a bug fix per [1]. Strictly speaking, as there's no core snap from an interim release, this issue doesn't directly effect Impish. However, to comply with the SRU requirement, and to let the patches carry to the 22.04 release, I would like this to be included in Impish. One of the patch has a small possibility to create a problem on classic systems, so testing in a development release is a good idea. Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [2] on the system. [1] https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_for_bugfix-only_updates [2] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-core/hooks/08-etc-writable.chroot?h=ubuntu/focal - SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is
[Touch-packages] [Bug 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
unsure if the bug should be made to affect to snapd ubuntu package? -- 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/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: Fix Committed Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
The issue is impacting impish daily
$ sudo snap pack src
libgcc_s.so.1 must be installed for pthread_cancel to work
erreur : cannot pack "src": mksquashfs call failed
$ snap version
snap2.53~pre1.git19b68f708
snapd 2.53~pre1.git19b68f708
series 16
ubuntu 21.10
kernel 5.13.0-16-generic
$ dpkg -l snapd
ii snapd 2.53~pre1.git19b68f708 amd64Daemon and tooling that >
Using SNAPD_DEBUG=1 gives
2021/09/29 17:42:27.460907 tool_linux.go:93: DEBUG: snap (at
"/snap/snapd/current") is older ("2.51.7") than distribution package
("2.53~pre1.git19b68f708")
Sounds like an issue we should fix for release so tagging rls incoming
** Tags added: impish rls-ii-incoming
--
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/1943077
Title:
snapd fails to autopkgtest on mksquashfs, which is looking for
libgcc_s
Status in snapd:
Fix Committed
Status in openssh package in Ubuntu:
New
Status in squashfs-tools package in Ubuntu:
New
Bug description:
During current snapd autopkgtest, a failure can be observed:
https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz
error: cannot pack
"/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox":
mksquashfs call failed:
-
libgcc_s.so.1 must be installed for pthread_cancel to work
Parallel mksquashfs: Using 1 processor
Creating 4.0 filesystem on
/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap,
block size 131072.
-
error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945"
is not a snap or snapdir
I traced the underlying call to the following:
"/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path"
"/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu"
"/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs
(the real call has more arguments, this is a simplified version that
produces the failure)
To observe this, one can create a VM based a cloud image from
https://cloud-images.ubuntu.com/impish/current, then run the above command in
the resulting environment.
Doing so will test against snapd v2.51.4 (12883).
Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent
result.
Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf
asdf.squashfs` without messing with library paths has mksquashfs behaving as
expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating
from
2.51.3 -> 2.51.4 also works.
One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute
and placing it in the library path for the above call.
In the working scenario, it appears that libgcc_s is being obtained
from outside of /snap (and also libz). In the failing scenario, this
external copy of libgcc_s is not being loaded (per gdb info sharedlibrary),
but libz still is.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1943077/+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 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package python-debian - 0.1.39ubuntu1
---
python-debian (0.1.39ubuntu1) impish; urgency=medium
* Add support for zstd compression format (LP: #1923845)
-- Athos Ribeiro Thu, 19 Aug 2021
14:50:49 -0300
** Changed in: python-debian (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Fix Released
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in python-debian package in Ubuntu:
Fix Released
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in reprepro source package in Focal:
Fix Released
Status in reprepro source package in Groovy:
Fix Released
Status in reprepro source package in Hirsute:
Fix Released
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's
[Touch-packages] [Bug 1945205] Re: [FFe] Add zstd support
As an effort to verify this is not triggered by this upload, I was able to reproduce the failure locally with $ autopkgtest-buildvm-ubuntu-cloud -r impish -v $ autopkgtest autopkgtest -U -- qemu ./autopkgtest-impish-amd64.img and $ autopkgtest autopkgtest -U --apt-pocket=proposed -- qemu ./autopkgtest-impish-amd64.img Output is attached.?field.comment=As an effort to verify this is not triggered by this upload, I was able to reproduce the failure locally with $ autopkgtest-buildvm-ubuntu-cloud -r impish -v $ autopkgtest autopkgtest -U -- qemu ./autopkgtest-impish-amd64.img and $ autopkgtest autopkgtest -U --apt-pocket=proposed -- qemu ./autopkgtest-impish-amd64.img Output is attached. ** Attachment added: "autopktest.log" https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1945205/+attachment/5529155/+files/autopktest.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1945205 Title: [FFe] Add zstd support Status in python-debian package in Ubuntu: Confirmed Bug description: [Feature Freeze Exception] Now that dpkg-deb defaults to compressing with zstd, python-debian can no longer decompress the compressed data into the binary package archive [1]. The proposed change, created as an MP at [2], introduces zstd support to python-debian 0.1.39 by adding a dependency to zstd to the package and by extending the python-debian xz support for python < 3.3, where xz was still not supported by tarfile, to also support the zstd compression. It is also important to note that, for python-debian 0.1.40, the relevant (here patched) code was re-worked (python < 3.3 support was dropped) and this proposed patch, along with the relevant proposed unit test, will need to be re-written. This re-writing effort is already an ongoing work proposed upstream in [3]. Once [3] is merged, this patch can be dropped and python-debian can be sync'd from upstream again. If there is a need to merge python-debian before [3] is accepted and released upstream, the next version of python-debian will need to drop the proposed patch and apply [3] instead, for the reasons listed above. While python-debian is not completely broken without this FFe patch, some of its features will not work properly on Ubuntu packages now they are compressed with zstd. For instance, any packages or scripts that try to use python-debian for extracting data from deb packages will no longer work. Namely, dh-cmake FTBFS when trying to decompress a deb package during its unit test run step [4]. A PPA with the proposed fix is available at [5], along with the build logs. I ran the dep8 test suite locally with the following results: autopkgtest [20:04:02]: summary python3-debian PASS I am also attaching the logs for installation, removal and upgrades of the patched package. [1] https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1923845 [2] https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-debian/+git/python-debian/+merge/407413 [3] https://salsa.debian.org/python-debian-team/python-debian/-/merge_requests/65 [4] https://launchpadlibrarian.net/552708462/buildlog_ubuntu-impish-amd64.dh-cmake_0.6.1_BUILDING.txt.gz [5] https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp-1923845-python-debian/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1945205/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
** Description changed: [Impact] New hardware support for AMD's Yellow Carp need five commits backported - to mesa and new firmware. This is only needed on focal, skipping - hirsute/impish (no kernel support there). + to mesa and new firmware. This is only needed on focal, skipping hirsute + (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
@brian-murray - Yes I will continue to test but fyi - I have run 24 tests on Xubuntu (18 different ISO´s) since the original report without being able to reproduce the error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Pulseaudio hasn't been updated since mid-August so it'd be helpful if you were to do some additional testing leok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
@Gunnar, regarding indicator-sound, My merge requests is here https://code.launchpad.net/~khurshid-alam/indicator-sound/fix-build- impish/+merge/409379 & build-recipe (https://code.launchpad.net/~khurshid-alam/+recipe/indicator-sound- ftbfs-hirsuit), I have disabled the failing tests for now as most are related to phone or works on phone environment. I have no way to debug that. As per my testing this doesn't hamper functionality on desktop, indicator-sound works as expected but perhaps more testing requires on different hardware. These tests can be enabled for desktop later if someone able to fix those...may be ask 3v1n0 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1943984] Re: No archive files for static compilation are included in the -dev package
On Wed, Sep 29, 2021 at 1:35 PM Mattia Rizzolo <1943...@bugs.launchpad.net> wrote: > > As a member of the Debian LibreOffice Team, and also as an Ubuntu > Developer, I'm likewise not convinced that starting to build and ship > graphite2's static library is a really useful thing to do. > > I'm personally generically against static libraries, since I regularly see > grief caused by poor tracking of statically-builtand or embedded things. Well, I have seen grief caused by shared libraries pulling too many dependencies or by shared libraries updates that break applications even though in theory the ABI compatibility has been kept. Also, there is actually a trend towards static compilation (golang, rust), so I do not think I'm the only one seeing this. But that is not really relevant. There are valid uses of static libraries, and the developers should have the option to choose between shared and static. The patch does not prevent using shared libraries, it just gives more options to application developers. > > And I don't really buy the need to save space when talking about a 137328 > bytes shared lib (taken from the last build of graphite2 in Sid, that's the > size of the .so). > It feels like you are building some kind to system image that you'd then > flash into some embedded thingy. I don't think there is much value in > saving...what, a dozen kB perhaps? (I haven't tried building the .a, so > happy to get the number). If your system is so constrained in space you're > likely going to need some much more dedicated work to reduce the size of > all components anyway; similarly if you are after the (normally > uncountable) performance improvement of statically linked binaries. Nobody said this was about saving space. libgraphite was being pulled as many other dependencies and I wanted to have all statically compiled instead of some static, some dynamic. Said this, I agree in not carrying a delta between Debian and Ubuntu as this library does not pull additional dependencies and is small, so additional maintenance is not worth the effort. > > On Wed, 29 Sep 2021, 1:06 pm Sebastien Bacher, <1943...@bugs.launchpad.net> > wrote: > > > Debian wontfixed the change so it means we will need to carry a delta at > > the cost of increased workload from our team if we take the change. Not > > saying that we should be we need to weight the cost over time and the > > benefit > > > > -- > > You received this bug notification because you are subscribed to Ubuntu. > > https://bugs.launchpad.net/bugs/1943984 > > > > Title: > > No archive files for static compilation are included in the -dev > > package > > > > Status in graphite2 package in Ubuntu: > > New > > Status in graphite2 package in Debian: > > Won't Fix > > > > Bug description: > > There is no libgraphite2.a file, so it is not possible to compile > > statically against this library. See attached patch to solve this. > > > > To manage notifications about this bug go to: > > > > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > > > > > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1943984 > > Title: > No archive files for static compilation are included in the -dev > package > > Status in graphite2 package in Ubuntu: > New > Status in graphite2 package in Debian: > Won't Fix > > Bug description: > There is no libgraphite2.a file, so it is not possible to compile > statically against this library. See attached patch to solve this. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Status in graphite2 package in Debian: Won't Fix Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1375821] Re: ifupdown doesn't bring loopback to state up
Hello, Trusty reached "End of Standard Support" a while ago and so I am marking this as "Won't Fix". Thank you. ** Changed in: ifupdown (Ubuntu Trusty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1375821 Title: ifupdown doesn't bring loopback to state up Status in ifupdown package in Ubuntu: Fix Released Status in mailman package in Ubuntu: Invalid Status in ifupdown source package in Trusty: Won't Fix Status in mailman source package in Trusty: Invalid Bug description: Upon booting a machine with the following setup on a relatively slimmed down netboot machine the loopback interface isn't brought up properly: cat /etc/network/interfaces auto lo iface lo inet loopback iface lo inet6 loopback auto eth0 iface eth0 inet6 auto dhcp 1 #iface eth0 inet ipv4ll auto eth1 iface eth1 inet6 auto dhcp 1 #iface eth1 inet ipv4ll Upon boot Loopback is unconfigured: root@:~# ip addr show dev lo 1: lo: mtu 65536 qdisc noop state DOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 Try to bring the interface up: root@:~# ifup -v lo ifup: interface lo already configured Bring it down and up: root@:~# ifdown -v lo Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-down.d run-parts: executing /etc/network/if-down.d/avahi-autoipd run-parts: executing /etc/network/if-down.d/upstart run-parts --verbose /etc/network/if-post-down.d Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-down.d run-parts: executing /etc/network/if-down.d/avahi-autoipd run-parts: executing /etc/network/if-down.d/upstart run-parts --verbose /etc/network/if-post-down.d Configuring interface lo=lo (inet6) run-parts --verbose /etc/network/if-down.d run-parts: executing /etc/network/if-down.d/avahi-autoipd run-parts: executing /etc/network/if-down.d/upstart run-parts --verbose /etc/network/if-post-down.d root@:~# ifup -v lo Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart Configuring interface lo=lo (inet6) run-parts --verbose /etc/network/if-pre-up.d run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart no change: root@:~# ip addr show dev lo 1: lo: mtu 65536 qdisc noop state DOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 bring it down again: root@:~# ifdown lo And up, but this time with --no-loopback: root@:~# ifup -v --no-loopback lo Configuring interface lo=lo (inet) run-parts --verbose /etc/network/if-pre-up.d ip link set dev lo up run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart Configuring interface lo=lo (inet6) run-parts --verbose /etc/network/if-pre-up.d ip link set dev lo up 2>/dev/null ip addr add dev lo ::1 2>/dev/null run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart now it seems like something actually happened! check: root@:~# ip addr show dev lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default 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 All seems fine, everything is working from here on. My expectation is that ifup should configure the interface and set state to up, and ifdown should set state to down, even though it's a loopback that may or may not be magically autoconfigured somewhere else. And a question: If the case is that ifup shouldn't configure the loopback, what should configure it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1375821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1791958] Re: iptables-restore is missing -w option
> I'll monitor the "-backports" discussion and let's see from there. Looks like the backports pocket will be available again. I added bionic- backports so that this request can be found from that end, since it looks like backports was something being considered. I don't intend to imply any particular opinion about the best route. ** Also affects: bionic-backports Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1791958 Title: iptables-restore is missing -w option Status in Bionic Backports: New Status in iptables package in Ubuntu: Confirmed Bug description: For CRIU we need to have iptables version 1.6.2 which includes the '-w' option in iptables-restore. This is a request to update iptables to 1.6.2 in 18.10 and if possible backport the necessary changes to 18.04. The CRIU project gets right now many bug reports (mostly in the combination LXD + CRIU) due to the missing '-w' option in iptables- restore. Especially as 18.04 will be around for some time it would be good to have iptables-restore available with '-w'. This is one example bug report: https://github.com/checkpoint- restore/criu/issues/551 But not only CRIU would benefit from this change. It seems also problematic with Kubernetes: https://github.com/kubernetes/kubernetes/pull/60978 So if possible, please update iptables to 1.6.2 (or backport changes) to support -w in iptables-restore. To manage notifications about this bug go to: https://bugs.launchpad.net/bionic-backports/+bug/1791958/+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 1785383] Re: missing EDNS0 record confuses systemd-resolved
MP to fix this bug in Bionic, already reviewed and uploaded:
https://code.launchpad.net/~paride/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/409149
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dnsmasq source package in Bionic:
In Progress
Status in systemd source package in Bionic:
Fix Released
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Fix Released
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records [1] when returning an
empty answer for a domain it is authoritative for. systemd-resolved
seems to get confused by this in certain circumstances; when using the
stub resolver and requesting an address for which there are no
records, there can sometimes be a five second hang in resolution.
[1] https://en.wikipedia.org/wiki/Extension_Mechanisms_for_DNS
[Test Plan]
Test case for bionic:
-
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# returns "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't.
# does so with the -proposed package.
-
[Where problems could occur]
Problems may occur in case a client queries dnsmasq and relies on
EDNS0 not being available for behaving correctly. This covers cases
where the software querying dnsmasq is buggy or misconfigured.
[Development Fix]
Fixed upstream in dnsmasq >= 2.80.
[Stable Fix]
Partial cherry-pick of upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
The cherry-pick is partial because half if it is already in the
package .diff we have in Bionic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1785383/+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 1945465] [NEW] Can't turn bluetooth on
Public bug reported: When I try to turn on my bluetooth, it simply doesn't turn on. This just came from one day to another. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pc27999 F pulseaudio /dev/snd/pcmC0D0p: pc27999 F...m pulseaudio /dev/snd/controlC1: pc27999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:02:30 2021 InstallationDate: Installed on 2021-06-28 (93 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac12,1:pvr1.0:sku:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1945465 Title: Can't turn bluetooth on Status in alsa-driver package in Ubuntu: New Bug description: When I try to turn on my bluetooth, it simply doesn't turn on. This just came from one day to another. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pc27999 F pulseaudio /dev/snd/pcmC0D0p: pc27999 F...m pulseaudio /dev/snd/controlC1: pc27999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:02:30 2021 InstallationDate: Installed on 2021-06-28 (93 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac12,1:pvr1.0:sku:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1945465/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Tested Xubuntu Impish daily 29-09-2021 and was unable to to reproduce the bug - This test was on the same machine (Lenovo V14-IIL) as my initial report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1931958] Re: 0~git20200629+e7aa92a-8 is FTFBS
The deprecation warning was fixed in libcamera upstream in
https://github.com/kbingham/libcamera/commit/19652e502
The build still fails with that fix due to
'FAILED: src/libcamera/libcamera.so.0.1.0.p/object.cpp.o
c++ -Isrc/libcamera/libcamera.so.0.1.0.p -Isrc/libcamera -I../src/libcamera
-Iinclude -I../include -Iinclude/libcamera -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Werror
-std=c++14 -Wno-unused-parameter -include config.h -g -O2
'-ffile-prefix-map=/<>/libcamera-0~git20200629+e7aa92a=.' -flto=auto
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/libcamera/libcamera.so.0.1.0.p/object.cpp.o -MF
src/libcamera/libcamera.so.0.1.0.p/object.cpp.o.d -o
src/libcamera/libcamera.so.0.1.0.p/object.cpp.o -c ../src/libcamera/object.cpp
In file included from ../src/libcamera/object.cpp:15:
../src/libcamera/object.cpp: In member function
‘libcamera::Object::notifyThreadMove()’:
../include/libcamera/internal/message.h:57:47: error: array subscript ‘const
struct InvokeMessage[0]’ is partly outside array bounds of ‘struct Message[1]’
[-Werror=array-bounds]
57 | Semaphore *semaphore() const { return semaphore_; }
| ^~
../src/libcamera/object.cpp:217:17: note: while referencing ‘msg’
217 | Message msg(Message::ThreadMoveMessage);
| ^~~
cc1plus: all warnings being treated as errors'
Failing build on warnings is probably not we want on the package or we
will get similar issues again as libraries deprecated functions or
compiler change, which aren't enough of a reason to break a package
build, let's disable Werror instead
** Changed in: libcamera (Ubuntu)
Importance: Undecided => High
** Changed in: libcamera (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1931958
Title:
0~git20200629+e7aa92a-8 is FTFBS
Status in gstreamer1.0 package in Ubuntu:
New
Status in libcamera package in Ubuntu:
In Progress
Bug description:
Fails to build due to gstreamer using deprecated g_memdup:
/usr/include/gstreamer-1.0/gst/base/gstbytereader.h: In function ‘guint8*
gst_byte_reader_dup_data_unchecked(GstByteReader*, guint)’:
/usr/include/gstreamer-1.0/gst/base/gstbytereader.h:365:41: error: ‘void*
g_memdup(gconstpointer, guint)’ is deprecated: Use 'g_memdup2' instead
[-Werror=deprecated-declarations]
365 | return (guint8 *) g_memdup (data, size);
| ^
In file included from /usr/include/glib-2.0/glib.h:82,
from /usr/include/gstreamer-1.0/gst/gst.h:27,
from ../src/gstreamer/gstlibcamerasrc.h:12,
from ../src/gstreamer/gstlibcamerasrc.cpp:34:
/usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
257 | gpointer g_memdup (gconstpointer mem,
Fixed in gstreamer upstream:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b16e96dd878e0c5e7baeb8fad62ca43de1f66982
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1931958/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Changed in: util-linux (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: Confirmed Bug description: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
With manually placing firmware in /lib/firmware (since SRU not started for that) and using 5.14 kernel confirmed that mesa looks good. Since we don't have linux-firmware SRU package yet and they are combined on this bug report I will not add "verification-done-focal". # glxinfo | grep "OpenGL render" -i OpenGL renderer string: AMD YELLOW_CARP (DRM 3.42.0, 5.14.0, LLVM 12.0.0) # dpkg -l | grep 21.0.3-0ubuntu0.3 ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor library ii libgbm1:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64generic buffer management API -- runtime ii libgl1-mesa-dri:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- GLX vendor library -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute/impish (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Could someone report the issue upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues ? it seems a problem with the new code to handle session closing correctly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1943984] Re: No archive files for static compilation are included in the -dev package
As a member of the Debian LibreOffice Team, and also as an Ubuntu Developer, I'm likewise not convinced that starting to build and ship graphite2's static library is a really useful thing to do. I'm personally generically against static libraries, since I regularly see grief caused by poor tracking of statically-builtand or embedded things. And I don't really buy the need to save space when talking about a 137328 bytes shared lib (taken from the last build of graphite2 in Sid, that's the size of the .so). It feels like you are building some kind to system image that you'd then flash into some embedded thingy. I don't think there is much value in saving...what, a dozen kB perhaps? (I haven't tried building the .a, so happy to get the number). If your system is so constrained in space you're likely going to need some much more dedicated work to reduce the size of all components anyway; similarly if you are after the (normally uncountable) performance improvement of statically linked binaries. On Wed, 29 Sep 2021, 1:06 pm Sebastien Bacher, <1943...@bugs.launchpad.net> wrote: > Debian wontfixed the change so it means we will need to carry a delta at > the cost of increased workload from our team if we take the change. Not > saying that we should be we need to weight the cost over time and the > benefit > > -- > You received this bug notification because you are subscribed to Ubuntu. > https://bugs.launchpad.net/bugs/1943984 > > Title: > No archive files for static compilation are included in the -dev > package > > Status in graphite2 package in Ubuntu: > New > Status in graphite2 package in Debian: > Won't Fix > > Bug description: > There is no libgraphite2.a file, so it is not possible to compile > statically against this library. See attached patch to solve this. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Status in graphite2 package in Debian: Won't Fix Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1945418] Re: Hibernate doesn't support as the default action in Ubuntu when critical power
Thanks Jeremy, could you open it for discussion upstream. There had been
similar problems discussed in the past, see
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/547 , is
the outcome matching what you can observe?
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #547
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/547
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1945418
Title:
Hibernate doesn't support as the default action in Ubuntu when
critical power
Status in OEM Priority Project:
Confirmed
Status in gnome-settings-daemon package in Ubuntu:
New
Status in upower package in Ubuntu:
New
Bug description:
In a stock ubuntu 20.04.3, g-s-d will notify the critical action when battery
is lower than warned critical threshold.
The notification is "The battery is below the critical level and this
computer is about to hibernate."
When hitting critical threshold, it takes "HybirdSleep" as the action.
```
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd[1]: Reached target Sleep.
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd[1]: Starting Hybrid Suspend+Hibernate...
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
kernel: PM: Image not found (code -22)
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd-sleep[3212]: Suspending system...
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
kernel: PM: hibernation: hibernation entry
```
You could see the hibernation called by logind but it will fail to
restore since either not enough SWAP or resume address is not specify
to kernel.
It confusing users about the critical actions.
In UPower.conf:
```
$ tail etc/UPower.conf
# reached for the batteries (UPS or laptop batteries) supplying the computer
#
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
#
# If HybridSleep isn't available, Hibernate will be used
# If Hibernate isn't available, PowerOff will be used
CriticalPowerAction=HybridSleep
```
In g-s-d:
```
/* We don't make the difference between HybridSleep and Hibernate
*/
if (g_strcmp0 (action, "PowerOff") == 0)
policy = GSD_POWER_ACTION_SHUTDOWN;
else
policy = GSD_POWER_ACTION_HIBERNATE;
...
/* use different text for different actions */
if (policy == GSD_POWER_ACTION_HIBERNATE) {
/* TRANSLATORS: computer will hibernate */
message = g_strdup (_("The battery is below the
critical level and "
"this computer is about to
hibernate."));
```
There are two approach if possible:
1) change "CriticalPowerAction" to "PowerOff" because the suspend to ram is
almost useless when battery is in critical threshold and the suspend to disk is
usually not working in default installed ubuntu.
2) have a new "GsdPowerActionType" type for "HybridSleep" to show the
appropriate message but taking the same action (notify logind).
---
$ dpkg -l | grep -i 'upower\|gnome-settings-daemon'
ii gir1.2-upowerglib-1.0:amd640.99.11-1build2
amd64GObject introspection data for upower
ii gnome-settings-daemon 3.36.1-0ubuntu1.1
amd64daemon handling the GNOME session settings
ii gnome-settings-daemon-common 3.36.1-0ubuntu1.1
all daemon handling the GNOME session settings - common files
ii libupower-glib3:amd64 0.99.11-1build2
amd64abstraction for power management - shared library
ii upower 0.99.11-1build2
amd64abstraction for power managemen
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1945418/+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 1943984] Re: No archive files for static compilation are included in the -dev package
Debian wontfixed the change so it means we will need to carry a delta at the cost of increased workload from our team if we take the change. Not saying that we should be we need to weight the cost over time and the benefit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Status in graphite2 package in Debian: Won't Fix Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt
Martin, I almost expected that would be the call but wanted to leave it to you
to decide.
Thank you as always!
o/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Title:
umockdev 0.16.3-1 breaks autopkgtest of bolt
Status in bolt package in Ubuntu:
In Progress
Status in umockdev package in Ubuntu:
Invalid
Status in umockdev package in Debian:
Unknown
Bug description:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
python3-dbusmock and the new version causes this.
Retrying autopkgtest locally with no, all and just umockdev from proposed
and it seems reproducible.
- impish-release - works
- impish-all-proposed - crashes
- impish-release + umockdev+libc6 from proposed - crashes
Repro:
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
FYI:
Downgrading to umockdev 0.16.2-1 in the same environment does not
eliminate the issue. So it might happen at the bolt test-build time.
Debian has the same issue in:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz
The new mockdev fails to create /sys/bus which is requested by the test.
From there the error path is what crashes, but the root cause is why we enter
the error-path in the first place.
One should be aware, this fail is "normal" if the environment is not mocked.
Even in the good case the different calls with/without umockdev lead to
exactly the same crash.
# good
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
# same crash as the new version has with umockdev-wrapper
$ gdb /usr/libexec/installed-tests/bolt/test-power
This is based on ldpreload.
$ cat /usr/bin/umockdev-wrapper
#!/bin/sh
# Wrapper program to preload the libumockdev library, so that test programs
can
# set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"
Gut feeling: it seems the mocking no more happens, and due to that
it runs into the non-mocked crash
Debugging with that:
$ pull-lp-source bolt
$ cd bolt-0.9.1/tests
$ gdb /usr/libexec/installed-tests/bolt/test-power
(gdb) set environment LD_PRELOAD libumockdev-preload.so.0
(gdb) b mock_sysfs_init
(gdb) run
With that we can see that while the crash is somewhere inside g_warning the
reason is in the g_mkdir failing with the new umockdev.
Good-case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 11444)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 11445)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = 0
(gdb) n
188 cls = g_build_filename (sys, "class", NULL);
Bad-Case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 17082)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 17083)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = -1
(gdb) n
186 g_warning ("could not create %s", bus);
(gdb) n
** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus
Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.
I'll tag this
[Touch-packages] [Bug 1943984] Re: No archive files for static compilation are included in the -dev package
** Changed in: graphite2 (Debian) Status: Unknown => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Status in graphite2 package in Debian: Won't Fix Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1945205] Re: [FFe] Add zstd support
Held back in proposed migration: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/a/autopkgtest/20210929_062309_c71f0@/log.gz That test fail can't be reproduced in local autopkgtest (LXD init is different in the autopkgtest infra compared to a "normal" cloudimage) nor does it seem to be triggered by this upload. Most likely a regression-in-release due to image/lxd changes but one will have to do the homework to verify and then fix or test-hint this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1945205 Title: [FFe] Add zstd support Status in python-debian package in Ubuntu: Confirmed Bug description: [Feature Freeze Exception] Now that dpkg-deb defaults to compressing with zstd, python-debian can no longer decompress the compressed data into the binary package archive [1]. The proposed change, created as an MP at [2], introduces zstd support to python-debian 0.1.39 by adding a dependency to zstd to the package and by extending the python-debian xz support for python < 3.3, where xz was still not supported by tarfile, to also support the zstd compression. It is also important to note that, for python-debian 0.1.40, the relevant (here patched) code was re-worked (python < 3.3 support was dropped) and this proposed patch, along with the relevant proposed unit test, will need to be re-written. This re-writing effort is already an ongoing work proposed upstream in [3]. Once [3] is merged, this patch can be dropped and python-debian can be sync'd from upstream again. If there is a need to merge python-debian before [3] is accepted and released upstream, the next version of python-debian will need to drop the proposed patch and apply [3] instead, for the reasons listed above. While python-debian is not completely broken without this FFe patch, some of its features will not work properly on Ubuntu packages now they are compressed with zstd. For instance, any packages or scripts that try to use python-debian for extracting data from deb packages will no longer work. Namely, dh-cmake FTBFS when trying to decompress a deb package during its unit test run step [4]. A PPA with the proposed fix is available at [5], along with the build logs. I ran the dep8 test suite locally with the following results: autopkgtest [20:04:02]: summary python3-debian PASS I am also attaching the logs for installation, removal and upgrades of the patched package. [1] https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1923845 [2] https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-debian/+git/python-debian/+merge/407413 [3] https://salsa.debian.org/python-debian-team/python-debian/-/merge_requests/65 [4] https://launchpadlibrarian.net/552708462/buildlog_ubuntu-impish-amd64.dh-cmake_0.6.1_BUILDING.txt.gz [5] https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp-1923845-python-debian/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1945205/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** No longer affects: libx11 (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 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/mutter/+bug/1942031/+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 1934199] Re: Switch from Livepatch service to UA client
** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Changed in: software-properties (Ubuntu Xenial) Status: New => Triaged ** Changed in: software-properties (Ubuntu Bionic) Status: New => Triaged ** Changed in: software-properties (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934199 Title: Switch from Livepatch service to UA client Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Xenial: Triaged Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Focal: Triaged Status in software-properties source package in Hirsute: Won't Fix Status in software-properties source package in Impish: Won't Fix Bug description: software-properties currently uses a HTTP over Unix domain socket service from the livepatch snap to get the status and enable/disable it. This service is being deprecated with the 'ua' command line tool now providing this functionality. software-properties also installed the snap to gain access to this service. This is no longer required as the 'ua' tool does this. (*) The Livepatch service is a HTTP over Unix domain service running on livepatchd.sock inside the livepatch snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1945418] [NEW] Hibernate doesn't support as the default action in Ubuntu when critical power
Public bug reported:
In a stock ubuntu 20.04.3, g-s-d will notify the critical action when battery
is lower than warned critical threshold.
The notification is "The battery is below the critical level and this computer
is about to hibernate."
When hitting critical threshold, it takes "HybirdSleep" as the action.
```
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd[1]: Reached target Sleep.
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd[1]: Starting Hybrid Suspend+Hibernate...
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
kernel: PM: Image not found (code -22)
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
systemd-sleep[3212]: Suspending system...
九 29 11:24:48 ubuntu-HP-ZBook-Studio-15-6-Inch-G8-Mobile-Workstation-PC
kernel: PM: hibernation: hibernation entry
```
You could see the hibernation called by logind but it will fail to
restore since either not enough SWAP or resume address is not specify to
kernel.
It confusing users about the critical actions.
In UPower.conf:
```
$ tail etc/UPower.conf
# reached for the batteries (UPS or laptop batteries) supplying the computer
#
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
#
# If HybridSleep isn't available, Hibernate will be used
# If Hibernate isn't available, PowerOff will be used
CriticalPowerAction=HybridSleep
```
In g-s-d:
```
/* We don't make the difference between HybridSleep and Hibernate */
if (g_strcmp0 (action, "PowerOff") == 0)
policy = GSD_POWER_ACTION_SHUTDOWN;
else
policy = GSD_POWER_ACTION_HIBERNATE;
...
/* use different text for different actions */
if (policy == GSD_POWER_ACTION_HIBERNATE) {
/* TRANSLATORS: computer will hibernate */
message = g_strdup (_("The battery is below the
critical level and "
"this computer is about to
hibernate."));
```
There are two approach if possible:
1) change "CriticalPowerAction" to "PowerOff" because the suspend to ram is
almost useless when battery is in critical threshold and the suspend to disk is
usually not working in default installed ubuntu.
2) have a new "GsdPowerActionType" type for "HybridSleep" to show the
appropriate message but taking the same action (notify logind).
---
$ dpkg -l | grep -i 'upower\|gnome-settings-daemon'
ii gir1.2-upowerglib-1.0:amd640.99.11-1build2
amd64GObject introspection data for upower
ii gnome-settings-daemon 3.36.1-0ubuntu1.1
amd64daemon handling the GNOME session settings
ii gnome-settings-daemon-common 3.36.1-0ubuntu1.1
all daemon handling the GNOME session settings - common files
ii libupower-glib3:amd64 0.99.11-1build2
amd64abstraction for power management - shared library
ii upower 0.99.11-1build2
amd64abstraction for power managemen
** Affects: oem-priority
Importance: High
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority originate-from-1911231 originate-from-1943959 stella
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Tags added: oem-priority originate-from-1943959 stella
** Tags added: originate-from-1911231
** Summary changed:
- Hibernate is not the default action in Ubuntu when critical power
+ Hibernate doesn't support as the default action in Ubuntu when critical power
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1945418
Title:
Hibernate doesn't support as the default action in Ubuntu when
critical power
Status in OEM Priority Project:
Confirmed
Status in gnome-settings-daemon package in Ubuntu:
New
Status in upower package in Ubuntu:
New
Bug description:
In a stock ubuntu 20.04.3, g-s-d will notify the critical action when battery
is lower than warned critical threshold.
The notification is "The battery is below the critical level and this
