[Touch-packages] [Bug 1773167]
Here's information about submitting alsa bugs: http://alsa-project.org/main/index.php/Bug_Tracking -- 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/1773167 Title: [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100% of a single CPU core Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Triaged Bug description: On a krez ninja 1103 laptop audio is not working; pulseaudio consumes 100% of a single CPU core. Pulseaudio log atached. According to perf, most CPU is consumed at __memset_erms. Below is the GDB stacktrace of pulseaudio. # gdb -p 1009 -batch -eval-command="thread apply all bt" [New LWP 1028] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x56318e574a30) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 205 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory. Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)): #0 0x7fe2ab063339 in _IO_str_init_static_internal (sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36 #1 0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", maxlen=, flags=1, slen=, format=0x7fe2ac698e8d "%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62 #2 0x7fe2ac6601ca in pa_vsnprintf () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7fe2ac660366 in pa_snprintf () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #4 0x7fe2ac66bda8 in pa_log_levelv_meta () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #5 0x7fe2ac66b655 in pa_log_level_meta () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #6 0x7fe2a52b36ae in ?? () from /usr/lib/pulse-11.1/modules/libalsa-util.so #7 0x7fe2ac68c2a8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #8 0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at pthread_create.c:463 #9 0x7fe2ab0f488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)): #0 0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x56318e574a30) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 #1 do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at sem_waitcommon.c:111 #2 0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, abstime=0x0) at sem_waitcommon.c:181 #3 0x7fe2ac68c502 in pa_semaphore_wait () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #4 0x7fe2ac8cca24 in pa_asyncmsgq_send () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so #5 0x7fe2a6841119 in ?? () from /usr/lib/pulse-11.1/modules/libprotocol-native.so #6 0x7fe2ac675ee2 in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fe2a6844695 in ?? () from /usr/lib/pulse-11.1/modules/libprotocol-native.so #8 0x7fe2ac678bef in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #9 0x7fe2ac67b6ab in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #10 0x7fe2ac67ba49 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #11 0x7fe2ac67c2cf in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #14 0x7fe2ac40e530 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #15 0x56318d445b82 in main () ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: user 1009 F...m pulseaudio /dev/snd/controlC0: user 1009 F pulseaudio Card0.Amixer.info: Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio' Mixer name : '' Components : '' Controls : 15 Simple ctrls : 0 Card0.Amixer.values: CurrentDesktop: LXDE Date: Thu May 24 16:04:13 2018 InstallationDate: Installed on 2018-05-22 (1 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
[Touch-packages] [Bug 1767730] Re: Chrome / Chrome Browser Title Bar Button Bug
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1767730 Title: Chrome / Chrome Browser Title Bar Button Bug Status in Ubuntu theme: Incomplete Status in ubuntu-themes package in Ubuntu: Expired Bug description: Chrome / Chrome Browser Title Bar Button Bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1767730/+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 1762921] Re: xorg
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1762921 Title: xorg Status in xorg package in Ubuntu: Expired Bug description: xorg failure at start up and crashes at times ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-35-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Wed Apr 11 02:13:59 2018 SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2018-02-17 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762921/+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 1779240] [NEW] Unable to Remove Trusted Software Providers From Authentication Tab
Public bug reported: Affected Ubuntu Release: Ubuntu 18.04 LTS Installed Package Version: 0.96.24.32.3 Upon clicking on a trusted software provider in the Authentication tab, and then clicking "Remove" will prompt for a password and do absolutely nothing. I would expect this to remove a software provider from the trusted list. Specifying the -d or -m options for extra information when running the application from a terminal emulator returns no useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jun 28 21:20:48 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-06-19 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1779240 Title: Unable to Remove Trusted Software Providers From Authentication Tab Status in software-properties package in Ubuntu: New Bug description: Affected Ubuntu Release: Ubuntu 18.04 LTS Installed Package Version: 0.96.24.32.3 Upon clicking on a trusted software provider in the Authentication tab, and then clicking "Remove" will prompt for a password and do absolutely nothing. I would expect this to remove a software provider from the trusted list. Specifying the -d or -m options for extra information when running the application from a terminal emulator returns no useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jun 28 21:20:48 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-06-19 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1779240/+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 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+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 1779237] [NEW] package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Public bug reported: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
Nothing was done. The comment: Changed in systemd: status: Unknown → Fix Released is an unfortunate bug in Launchpad. It was briefly tracking: https://github.com/systemd/systemd/issues/9431 which is now closed so Launchpad thought that means "fixed". If you scroll up you will find this bug is now correctly showing as not fixed. -- 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
This bug still exists on xubuntu 18.04 why not fixing this once and for all after all the years ??? is this really important to show this warning or only to warn people ??? what can they do to avoid this message ? update database ? what command-line to do so ?. Though it's just a warning message, it remains annoying and looks pretty sloppy. -- 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/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in kdelibs: Won't Fix Status in shared-mime-info: Won't Fix Status in kde4libs package in Ubuntu: Confirmed Status in shared-mime-info package in Ubuntu: Triaged Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/289592/+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 455219] Re: Bash doesn't find Files - example. thunderbird-bin
Closing per reporter’s feedback; not a bug anymore. ** Changed in: bash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/455219 Title: Bash doesn't find Files - example. thunderbird-bin Status in bash package in Ubuntu: Invalid Bug description: Binary package hint: bash Bash doesn't find files. For example Thunderbird3 Beta4 (at the end). The same Problem with downloaded Firefox(not the buildin one) This Problem came up with new installation of Ubuntu 9.10 Beta(new hdd). :-( Before I run 9.10 Beta as an upgrade from 9.04, all things where right. root@luigi-lnx:/root/thunderbird# ls -l /root/ insgesamt 8 drwxr-xr-x 2 root root 4096 2009-10-17 12:58 Desktop drwxr-xr-x 11 root root 4096 2009-10-19 09:04 thunderbird root@luigi-lnx:/root/thunderbird# ls -l /root/thunderbird/thunderbird* -rwxr-xr-x 1 root root 3891 2009-10-19 09:04 /root/thunderbird/thunderbird -rwxr-xr-x 1 root root 13329140 2009-10-19 09:04 /root/thunderbird/thunderbird-bin root@luigi-lnx:/root/thunderbird# ./thunderbird ./run-mozilla.sh: 399: ./thunderbird-bin: not found root@luigi-lnx:/root/thunderbird# /root/thunderbird/thunderbird-bin bash: /root/thunderbird/thunderbird-bin: No such file or directory waiting 4 answer thx INFO: root@luigi-lnx:/root/thunderbird# lsb_release -rd Description: Ubuntu karmic (development branch) Release: 9.10 root@luigi-lnx:/root/thunderbird# apt-cache policy bash bash: Installiert: 4.0-5ubuntu2 Kandidat: 4.0-5ubuntu2 Versions-Tabelle: *** 4.0-5ubuntu2 0 500 http://de.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: amd64 Date: Mon Oct 19 09:01:28 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: bash 4.0-5ubuntu2 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: bash Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/455219/+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 1779209] [NEW] package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego
Public bug reported: package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-dev 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:41:41 2018 ErrorMessage: problemy z zależnościami - pozostawianie nieskonfigurowanego InstallationDate: Installed on 2018-06-09 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1779209 Title: package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego Status in python3-defaults package in Ubuntu: New Bug description: package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-dev 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:41:41 2018 ErrorMessage: problemy z zależnościami - pozostawianie nieskonfigurowanego InstallationDate: Installed on 2018-06-09 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: problemy z zależnościami - pozostawianie nieskonfigurowanego UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779209/+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 1078924] Re: [Latitude E6520, IDT 92HD90BXX, Black Mic, Left] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1078924 Title: [Latitude E6520, IDT 92HD90BXX, Black Mic, Left] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Well, recording of sound doesn't work. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sb 2291 F pulseaudio /dev/snd/controlC0: sb 2291 F pulseaudio Date: Wed Nov 14 22:48:21 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-27 (110 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sb 2291 F pulseaudio /dev/snd/controlC0: sb 2291 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [Latitude E6520, IDT 92HD90BXX, Black Mic, Left] No sound at all UpgradeStatus: Upgraded to quantal on 2012-10-20 (24 days ago) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-09-08T17:31:40.709380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1078924/+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 1778960] Re: SRU: Update python 2.7 to the final 2.7.15 release
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1778960 Title: SRU: Update python 2.7 to the final 2.7.15 release Status in python2.7 package in Ubuntu: New Bug description: Ubuntu 18.04 LTS shipped with the python 2.7.15 release candidate. Please let's update to the final release. Upstream changes are: - bpo-33374: Tweak the definition of PyGC_Head, so compilers do not believe it is always 16-byte aligned on x86. This prevents crashes with more aggressive optimizations present in GCC 8. - Identify as 2.7.15 instead of 2.7.15rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1778960/+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 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install
Fix is pending: https://github.com/mvo5/unattended-upgrades/pull/131 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install Status in unattended-upgrades package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 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/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1779189] [NEW] /var/log/journal consumed all available disk space
Public bug reported: Running 18.04, systemd 237-3ubuntu10, and all of my available disk space on /var (4.3G) just got eaten up by systemd-journald. /etc/systemd/journald.conf has all the default values (everything commented out). Processes were starting to crash, and I only recovered by running "sudo journalctl --vacuum-files=1" which brought it back down to 25M. My understanding is that the defaults are supposed to prevent this from happening. I'm not familiar enough with systemd to further debug why this might have happened. ** 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/1779189 Title: /var/log/journal consumed all available disk space Status in systemd package in Ubuntu: New Bug description: Running 18.04, systemd 237-3ubuntu10, and all of my available disk space on /var (4.3G) just got eaten up by systemd-journald. /etc/systemd/journald.conf has all the default values (everything commented out). Processes were starting to crash, and I only recovered by running "sudo journalctl --vacuum-files=1" which brought it back down to 25M. My understanding is that the defaults are supposed to prevent this from happening. I'm not familiar enough with systemd to further debug why this might have happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779189/+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 1772632] Update Released
The verification of the Stable Release Update for llvm-toolchain-6.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Committed Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1772632] Re: Backport packages for 16.04.5 HWE stack
This bug was fixed in the package llvm-toolchain-6.0 - 1:6.0-1ubuntu2~16.04.1 --- llvm-toolchain-6.0 (1:6.0-1ubuntu2~16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1772632) - Don't build the Fuzzer library on powerpc. - set BINUTILS_GOLD_ARCHS to match 4.0, dropping arm64 and s390x -- Timo Aaltonen Tue, 22 May 2018 13:54:13 +0300 ** Changed in: llvm-toolchain-6.0 (Ubuntu Xenial) 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/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Committed Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade
Exact same problem here. I assume the quirk added was for the previous version of headphone firmware. -- 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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773697/+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 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
An approximation of the packages that need to be fixed individually are listed here: https://lintian.debian.org/tags/maintainer-script-calls-systemctl.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state Status in init-system-helpers package in Ubuntu: New Status in snapd package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When using unattended-upgrades with "InstallOnShutdown" on Bionic, the package installation on various packages hangs until the systemd ShutdownTimeout (30min) is expired and systemd kills all processes and powers off/reboots the system. This leaves packages in an unconfigured, broken state. At least sometimes this cannot be fixed with a "dpkg --configure -a", but instead requires the user to manually reinstall the package that caused the hang. This appears to be a deadlock, because the hanging commands are always "systemctl stop ..." or "systemctl restart ...", etc.. If I understand this correctly, those systemctl commands block because systemd tries to shutdown the system and tries to satisfy all dependencies for the shutdown targets before those systemctl commands could get executed, which creates a deadlock. Steps to reproduce: - Install 18.04 - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades - disable bionic-updates in /etc/apt/sources.list (more on that later) - execute "unattended-upgrade --download-only" - reboot the system -> The upgrade on shutdown hangs when configuring the apport package. The hanging command is "systemctl stop apport-forward.socket". The system hangs until the systemd ShutdownTimeout expires and systemd forcefully reboots the system. After the system is rebooted the apport package is in "iUR" state, and needs to be reinstalled to fix this. I disabled the bionic-updates pocket in sources.list, because in the default configuration unattended-updates does not use bionic-updates, and seems to have skipped installation of apport from bionic-security (supposedly because an already newer version of apport was in bionic- updates). If my understanding of why apport initially did not get installed is correct, then this would be another problem, because it would mean that unattended-upgrades potentially does not install all available security updates when bionic-updates is enabled in sources.list (which is the default). The problem can also be reproduced without disabling bionic-updates in sources.list, but instead enabling bionic-updates in /etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did hang when installing the package snapd (the hanging command was "systemctl stop snapd.autoimport.service snapd.core-fixup.service snapd.service snapd.snap-repair.service snapd.snap-repair.service snapd.socket snapd.system-shutdown.service"). This leads to the same problems as described above. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: unattended-upgrades 1.1ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1778219/+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 1759836] Re: systemd-udevd consumes 100% of CPU
I am having a similar problem after upgrading to 18.04 on a Dell Precision M4600, with the following specs: - Intel Core i7 2640M - NVidia Quadro 2000M I have disabled Bluetooth entirely, because I don't need it. But the NVidia loading/unloading (add/remove) in udev keeps persisting. I can disable this by removing the nvidia-rules (71-nvidia-rules) from the rules.d-directory, but that also disables the module entirely, and I need the nvidia module, I just wish it would not unload. This issue seems to be about Bluetooth, although plenty of mentions of NVidia, should I create a separate one for the nvidia driver issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Confirmed Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 1779157] [NEW] /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 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/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic ** Affects: unattended-upgrades (Ubuntu) Importance: High Assignee: Balint Reczey (rbalint) Status: In Progress ** Tags: bionic cosmic kylin-18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install Status in unattended-upgrades package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 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/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 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/. + + Traceback + + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 1927, in + sys.exit(main(options)) + File "/usr/bin/unattended-upgrade", line 1782, in main + logfile_dpkg) + File "/usr/bin/unattended-upgrade", line 1057, in do_install + "removal:%s" % "".join([pkg.name for pkg in marked_delete])) + AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic ** Changed in: unattended-upgrades (Ubuntu) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install Status in unattended-upgrades package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 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/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
Last time I tried to reproduce this with a C program I was not successful, hence why I haven't been able to work on this from the upstream side. I will try again... Martin, it would be *very* helpful if you could post code or a script that demonstrates the issue in an automated way. I know you posted details and pseudocode on the ITS but I'm fallible and didn't succeed at turning it into a reproducer so far. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1547927 Title: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS Status in openldap package in Ubuntu: Incomplete Bug description: Tested with vivid and wily... also logged with openldap as http://www.openldap.org/its/index.cgi/Incoming?id=8374 The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs. When accessing server with a self-signed certificate, the results are: ldaps:// neverOK hard Error: can't contact LDAP server demand Error: can't contact LDAP server allowOK try Error: can't contact LDAP server ldap:// plus explicit ldap_start_tls_s() neverOK hard OK demand OK allowOK try OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927/+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 1768379] Please test proposed package
Hello Seth, or anyone else affected, Accepted python3-defaults into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.6.3-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Committed Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Committed Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+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 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
Hello Seth, or anyone else affected, Accepted python3-defaults into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.6.5-3ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: python3-defaults (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: python3-defaults (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Committed Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Committed Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+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 1766542] Re: Installation blocks when the machine is behind a proxy server
I had to tweak the time outs a bit, as I quickly get some errors from the networking stack (like 7s or so), but I could successfully verify the fix now, using a standard ubuntu:bionic lxd container, and modifying the routes, and setting a lower timeout: + ip r del default + ip r add default via 10.33.102.254 dev eth0 + ip -6 r del default + ip -6 r add default via fe80::689a:53ff:fe6f:8f85 dev eth0 RTNETLINK answers: File exists + cat + apt update -o acquire::http::timeout=1 Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease Could not connect to archive.ubuntu.com:80 (91.189.88.162), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::21), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.152), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::11), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.149), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::14), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.161), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::17), connection timed out Err:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Could not connect to archive.ubuntu.com:80 (91.189.88.162). - connect (113: No route to host) Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::21). - connect (113: No route to host) Could not connect to archive.ubuntu.com:80 (91.189.88.152), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::11), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.149), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::14), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.161), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::17), connection timed out Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Could not connect to archive.ubuntu.com:80 (91.189.88.162), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::21), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.152), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::11), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.149), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::14), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.161), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::17), connection timed out W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Could not connect to archive.ubuntu.com:80 (91.189.88.162). - connect (113: No route to host) Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::21). - connect (113: No route to host) Could not connect to archive.ubuntu.com:80 (91.189.88.152), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::11), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.149), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1560:8001::14), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.161), connection timed out Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::17), connection timed out W: Some index files failed to download. They have been ignored, or old ones used instead. real0m6.007s user0m0.139s sys 0m0.026s after 1.6.2: lxc exec bb -- bash $PWD/rep4 apt -y install $PWD/Downloads/*_1.6.2_amd64.deb + ip r del default + ip r add default via 10.33.102.254 dev eth0 + ip -6 r del default + ip -6 r add default via fe80::689a:53ff:fe6f:8f85 dev eth0 + cat + apt -y install /home/jak/Downloads/apt_1.6.2_amd64.deb /home/jak/Downloads/libapt-pkg5.0_1.6.2_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'apt' instead of '/home/jak/Downloads/apt_1.6.2_amd64.deb' Note, selecting 'libapt-pkg5.0' instead of '/home/jak/Downloads/libapt-pkg5.0_1.6.2_amd64.deb' The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. Suggested packages: apt-doc aptitude | synaptic | wajig dpkg-dev The following packages will be REMOVED: apt-utils ubuntu-minimal The following packages will be upgraded: apt libapt-pkg5.0 2 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. Need to get 0 B/1966 kB of archives. After this operation, 835 kB disk space will be
[Touch-packages] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed
Verified now, despite me not changing my verification script. Odd. with 1.2.26, it times out: + lxc exec lp1762766-xenial -- sh -c 'apt-cache policy apt libapt-pkg5.0 | grep Inst ; timeout 5s apt update' Installed: 1.2.26 Installed: 1.2.26 0% [Working]+ lxc stop lp1762766-xenial with 1.2.27, it works fine: + lxc exec lp1762766-xenial -- sh -c 'apt-cache policy apt libapt-pkg5.0 | grep Inst ; timeout 5s apt update' Installed: 1.2.27 Installed: 1.2.27 Reading package lists... Done E: The method driver /usr/lib/apt/methods/httpx could not be found. E: The method driver /usr/lib/apt/methods/httpx could not be found. E: Failed to fetch httpx://invalid.mirror.example.com/dists/bionic/InRelease E: Failed to fetch httpx://invalid.mirror.example.com/dists/bionic-updates/InRelease E: Some index files failed to download. They have been ignored, or old ones used instead. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] Two or more sources with an unknown protocol cause apt update to hang. For example, when using the https method on a system without integrated https support and without apt-transport-https installed. [Test case] Add two or more sources with an unknown protocol and run update [Regression potential] This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods. [Original bug report] When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed
huh, why did it say backports? Me looks again, and sees the package. -- 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/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] Two or more sources with an unknown protocol cause apt update to hang. For example, when using the https method on a system without integrated https support and without apt-transport-https installed. [Test case] Add two or more sources with an unknown protocol and run update [Regression potential] This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods. [Original bug report] When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed
No package in proposed yet. curl http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main /binary-amd64/Packages.xz | xzcat | grep ^Package does not show apt. odd. -- 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/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] Two or more sources with an unknown protocol cause apt update to hang. For example, when using the https method on a system without integrated https support and without apt-transport-https installed. [Test case] Add two or more sources with an unknown protocol and run update [Regression potential] This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods. [Original bug report] When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+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 1779129] [NEW] package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for co
Public bug reported: i was installing latex-maker and as it ended i got that error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 28 07:03:23 2018 DpkgTerminalLog: dpkg: error processing package libfdisk1:amd64 (--configure): package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: util-linux Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1779129 Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux- gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in util-linux package in Ubuntu: New Bug description: i was installing latex-maker and as it ended i got that error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 28 07:03:23 2018 DpkgTerminalLog: dpkg: error processing package libfdisk1:amd64 (--configure): package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: util-linux Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1779129/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
Daniel - please explain what was done to resolve. -- 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+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 1779121] [NEW] mobile broadband is slow to start in wake from suspend (or system startup)
Public bug reported:
On a ThinkPad 470s it takes ~ 40 seconds to gain connectivity on wake or
startup.
The log seems to incidate that there is first a 10 second delay in the
kernel recognising the USB device and assigning a serial port to it, and
then it takes ModemManager 20 seconds to open the device, and a further
13 seconds to go from unlocking the SIM ("locked" state) to getting an
ip address.
Apparently it starts in 10 seconds in Windows (see
https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/SierraWireless-
EM7455-in-X1c5-is-Lenovo-going-to-fix-its-poor/td-p/3716748) so the 40+
seconds it's not a hardware property.
The log goes like this:
Jun 28 15:06:35 myhostname NetworkManager[1302]: [1530187595.7935]
manager: sleep: wake requested (sleeping: yes enabled: yes)
Jun 28 15:06:35 myhostname NetworkManager[1302]: [1530187595.7936]
device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping',
sys-iface-state: 'managed')
Jun 28 15:06:35 myhostname NetworkManager[1302]: [1530187595.8780]
device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed',
sys-iface-state: 'managed')
Jun 28 15:06:36 myhostname kernel: [127229.483041] usb 1-6: config 1 interface
0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
Jun 28 15:06:36 myhostname kernel: [127229.483051] usb 1-6: config 1 interface
0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
Jun 28 15:06:36 myhostname kernel: [127229.483720] usb 1-6: New USB device
found, idVendor=1199, idProduct=9078
Jun 28 15:06:36 myhostname kernel: [127229.483728] usb 1-6: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Jun 28 15:06:36 myhostname kernel: [127229.483734] usb 1-6: Product: Sierra
Wireless EM7455 Qualcomm
Jun 28 15:06:36 myhostname kernel: [127229.483741] usb 1-6: Manufacturer:
Sierra Wireless, Incorporated
Jun 28 15:06:36 myhostname kernel: [127229.483747] usb 1-6: SerialNumber:
LF80875274011022
Jun 28 15:06:36 myhostname kernel: [127229.502644] usb 1-6: USB disconnect,
device number 14
Jun 28 15:06:36 myhostname NetworkManager[1302]: [1530187596.0722]
device (wlp58s0): state change: unmanaged -> unavailable (reason 'managed',
sys-iface-state: 'managed')
Jun 28 15:06:36 myhostname NetworkManager[1302]: [1530187596.0744]
manager: NetworkManager state is now CONNECTED_LOCAL
Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb1/1-6
Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'unbind' on
/sys/devices/pci:00/:00:14.0/usb1/1-6
Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb2/2-3/2-3:1.0
Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb2/2-3
Jun 28 15:06:38 myhostname ModemManager[1312]: Couldn't check support
for device at '/sys/devices/pci:00/:00:1c.2/:3a:00.0': not
supported by any plu
gin
Jun 28 15:06:38 myhostname ModemManager[1312]: Couldn't check support
for device at '/sys/devices/pci:00/:00:1f.6': not supported by any
plugin
Jun 28 15:06:45 myhostname kernel: [127238.486536] usb 1-6: new high-speed USB
device number 15 using xhci_hcd
Jun 28 15:06:45 myhostname kernel: [127238.642917] usb 1-6: config 1 has an
invalid interface number: 12 but max is 4
Jun 28 15:06:45 myhostname kernel: [127238.642920] usb 1-6: config 1 has an
invalid interface number: 13 but max is 4
Jun 28 15:06:45 myhostname kernel: [127238.642921] usb 1-6: config 1 has an
invalid interface number: 13 but max is 4
Jun 28 15:06:45 myhostname kernel: [127238.642923] usb 1-6: config 1 has no
interface number 1
Jun 28 15:06:45 myhostname kernel: [127238.642925] usb 1-6: config 1 has no
interface number 4
Jun 28 15:06:45 myhostname kernel: [127238.643533] usb 1-6: New USB device
found, idVendor=1199, idProduct=9079
Jun 28 15:06:45 myhostname kernel: [127238.643535] usb 1-6: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Jun 28 15:06:45 myhostname kernel: [127238.643537] usb 1-6: Product: Sierra
Wireless EM7455 Qualcomm Snapdragon X7 LTE-A
Jun 28 15:06:45 myhostname kernel: [127238.643539] usb 1-6: Manufacturer:
Sierra Wireless, Incorporated
Jun 28 15:06:45 myhostname kernel: [127238.646888] qcserial 1-6:1.0: Qualcomm
USB modem converter detected
Jun 28 15:06:45 myhostname kernel: [127238.647053] usb 1-6: Qualcomm USB modem
converter now attached to ttyUSB0
Jun 28 15:06:45 myhostname kernel: [127238.647590] qcserial 1-6:1.2: Qualcomm
USB modem converter detected
Jun 28 15:06:45 myhostname kernel: [127238.647791] usb 1-6: Qualcomm USB modem
converter now attached to ttyUSB1
Jun 28 15:06:45 myhostname kernel: [127238.648344] qcserial 1-6:1.3: Qualcomm
USB modem converter detected
Jun 28 15:06:45 myhostname kernel: [127238.648541] usb 1-6: Qualcomm USB modem
converter now attached to ttyUSB2
Jun 28 15:06:45 myhostname NetworkManager[1302]:
[Touch-packages] [Bug 1537528] Re: byobu-config segfault with screen backend
Updated the Debian bug so they are aware as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: Invalid Status in newt package in Ubuntu: Invalid Status in slang2 package in Ubuntu: Fix Released Status in slang2 source package in Xenial: Triaged Status in byobu package in Debian: New Bug description: [Impact] * Backport Debian fix for a crash in byobu due to libslang2 [Test Case] * byobu-screen * in there hit F9 or start byobu-config * without the fix this crashes [Regression Potential] * This is changing a libs implementation and $ reverse-depends src:slang2 -r xenial is quite a long list. OTOH this is somewhat ok as the change is in Debian and Ubuntu for more than three releases now and nothing around it seems to have totally broken. Never the less the biggest risk I see is something unexpected in one of the other libslang2 users. [Other Info] * n/a --- When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1537528] Re: byobu-config segfault with screen backend
I checked once more to be sure, artful (and later) is ok ** Changed in: slang2 (Ubuntu) Status: New => Triaged ** Also affects: newt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: slang2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: byobu (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: newt (Ubuntu Xenial) ** Changed in: byobu (Ubuntu) Status: In Progress => Invalid ** No longer affects: byobu (Ubuntu Xenial) ** Changed in: byobu (Ubuntu) Assignee: Dustin Kirkland (kirkland) => (unassigned) ** Changed in: newt (Ubuntu) Status: Confirmed => Invalid ** Changed in: slang2 (Ubuntu Xenial) Status: New => Triaged ** Changed in: slang2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: Invalid Status in newt package in Ubuntu: Invalid Status in slang2 package in Ubuntu: Fix Released Status in slang2 source package in Xenial: Triaged Status in byobu package in Debian: New Bug description: [Impact] * Backport Debian fix for a crash in byobu due to libslang2 [Test Case] * byobu-screen * in there hit F9 or start byobu-config * without the fix this crashes [Regression Potential] * This is changing a libs implementation and $ reverse-depends src:slang2 -r xenial is quite a long list. OTOH this is somewhat ok as the change is in Debian and Ubuntu for more than three releases now and nothing around it seems to have totally broken. Never the less the biggest risk I see is something unexpected in one of the other libslang2 users. [Other Info] * n/a --- When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1779092] Re: cyclic reboot with latest kernels possibly related to the cpu microcode updater
I rolled back the amd64-microcode to the previous version (3.20180524.1~ubuntu0.14.04.1 to 2.20131007.1+really20130710.1) and it resolved the issue, I can now boot to 151, so it is definitely related to amd64-microcode. I am using AMD Phenom(tm) II X4 975 Processor ** Package changed: xorg (Ubuntu) => amd64-microcode (Ubuntu) ** Summary changed: - cyclic reboot with latest kernels possibly related to the cpu microcode updater + cyclic reboot caused by the amd microcode updater -- 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/1779092 Title: cyclic reboot caused by the amd microcode updater Status in amd64-microcode package in Ubuntu: New Bug description: It happened like this: using kernel 3.13.0-144 (14.04) - ok jun 9: installed kernel 3.13.0-149 and rebooted - ok jun 21: installed some updates including update to the cpu microcode which was set up to execute at the next boot jun 28: rebooted to the same kernel 149 and the system went into cyclic reboot: shows grub screen, when the default kernel is selected reboots immediately with no messages and without creating any logs, nothing in /var/log with appropriate times booted to 144 - no issues tried upgrading to a new kernel (151) - same cyclic reboot booted back to 144 I am not telling the microcode update is the culprit, but it is mighty suspicious. It cannot be uninstalled using standard tools without uninstalling the kernels packages (linux-generic, linux-image-generic, linux-generic-pae, linux-image-generic-pae). I have both intel- microcode and amd64-microcode installed (CPU is AMD phenom X4 975). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 Uname: Linux 3.13.0-144-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Thu Jun 28 13:04:38 2018 InstallationDate: Installed on 2011-08-18 (2505 days ago) InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-10-18 (1349 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1779092/+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 1767740] Re: gnome-shell crashes at startup - segfault in nouveau_dri.so
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1767740 Title: gnome-shell crashes at startup - segfault in nouveau_dri.so Status in mesa package in Ubuntu: Confirmed Bug description: With a live USB stick or a freshly installed version of 18.04, gnome- shell crashes at startup. I get this error in dmesg: gnome-shell[]: segfault at xx ip xx sp xx error 4 in nouveau_dri.so[] The computer is a MacBook Pro with a GeForce 320M GPU. Using the proprietary driver listed in the "additional drivers" tab doesn't work either (I get a black screen at startup with no access to a virtual terminal). Everything was fine on 16.04, with nouveau or nvidia drivers. The only workaround is to blacklist the nouveau driver. I have of course very poor performance then. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 01:34:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro7,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8a41bdcd-9c0e-41b3-8111-94661a72e400 ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0B.1006012305 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0B.1006012305:bd06/01/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1767740/+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 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile
Since Cosmic is still open and auto-syncing I prepared that as fix [1] for Debian to sync it in. [1]: https://salsa.debian.org/ssh-team/openssh/merge_requests/2 -- 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/1771011 Title: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: If environment variable name defined in AuthorizedKeysFile contains underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and throws following error: authorized_keys:1: bad key options: invalid environment string To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1771011/+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 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
I don't think they have: my ticket is still open with them too. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1547927 Title: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS Status in openldap package in Ubuntu: Incomplete Bug description: Tested with vivid and wily... also logged with openldap as http://www.openldap.org/its/index.cgi/Incoming?id=8374 The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs. When accessing server with a self-signed certificate, the results are: ldaps:// neverOK hard Error: can't contact LDAP server demand Error: can't contact LDAP server allowOK try Error: can't contact LDAP server ldap:// plus explicit ldap_start_tls_s() neverOK hard OK demand OK allowOK try OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927/+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 1778932] Re: rsync can trigger system crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reassigning to the kernel since rsync should never be able to crash the system and if it crashes it's usually the kernel or bad hardware that's responsible. ** Package changed: rsync (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1778932 Title: rsync can trigger system crash Status in linux package in Ubuntu: New Bug description: I'm not sure how much of this is rsync or something else in my system. I can reliably trigger this using rsync to transfer files from one drive to another drive on my computer. the source is ssd and destination is mdadm raid 1 partition. will attach syslog messages. after it is triggered, the the system becomes unresponsive and requires a hard reboot. running rysnc as user, no special privileges. root@music:~# lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy rsync rsync: Installed: 3.1.2-2.1ubuntu1 Candidate: 3.1.2-2.1ubuntu1 Version table: *** 3.1.2-2.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 10:08:36 2018 InstallationDate: Installed on 2018-03-31 (87 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778932/+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 1353792] Re: Detect renamed files and handle by renaming instead of delete/re-send
It looks like this bug has gathered quite a bit of attention since it was first filed, so let me set some expectations here. The trouble with patching Ubuntu is that then we're on the hook for maintaining those patches indefinitely. This can cause a great deal of pain if future upstream refactorings mean that the patches need substantial rework, or if upstream decide to implement something very similar but with subtly different semantics. I suggest that to make progress you petition upstream to get this feature landed upstream directly. > Am I correct in the assumption that this has not been done or integrated in rsync in any form(s) at this time? I've not looked, sorry. Someone will have to dig through sources and commit logs and/or release notes and manpages to determine that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1353792 Title: Detect renamed files and handle by renaming instead of delete/re-send Status in rsync package in Ubuntu: Confirmed Bug description: There has been a report in rsync[0] about this issue since 2005, some patches has been developed detect-renamed[1] and detect-renamed-lax[2] to target the issue, I think it would be great if Ubuntu could patch itself rsync to provide such feature. I've updated those[3] patches[4] to apply to the latest rsync package (3.1.1) and they're working great in my own setup, I also put them in a ppa[5] for further testing. The patches aren't intrusive, they provide some extra flags (--detect-renamed, --detec-moved and --detect-renamed-lax) so I think it shouldn't be disastrous for those who won't use the extra features. [0] https://bugzilla.samba.org/show_bug.cgi?id=2294 [1] https://bugzilla.samba.org/attachment.cgi?id=7435 [2] http://gitweb.samba.org/?p=rsync-patches.git;a=blob;f=detect-renamed-lax.diff;h=4cd23bd4524662f1d0db0bcc90336a77d0bb61c9;hb=HEAD [3] https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed.diff [4] https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed-lax.diff [5] https://launchpad.net/~minos-archive/+archive/ubuntu/main/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1353792/+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 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
If you can point to where upstream have fixed it please, then we would have something to work on. Unfortunately I'm not sure we can make any progress without that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1547927 Title: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS Status in openldap package in Ubuntu: Incomplete Bug description: Tested with vivid and wily... also logged with openldap as http://www.openldap.org/its/index.cgi/Incoming?id=8374 The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs. When accessing server with a self-signed certificate, the results are: ldaps:// neverOK hard Error: can't contact LDAP server demand Error: can't contact LDAP server allowOK try Error: can't contact LDAP server ldap:// plus explicit ldap_start_tls_s() neverOK hard OK demand OK allowOK try OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927/+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 1537528] Re: byobu-config segfault with screen backend
** Description changed: + [Impact] + + * Backport Debian fix for a crash in byobu due to libslang2 + + [Test Case] + + * byobu-screen + * in there hit F9 or start byobu-config + * without the fix this crashes + + [Regression Potential] + + * This is changing a libs implementation and + $ reverse-depends src:slang2 -r xenial +is quite a long list. OTOH this is somewhat ok as the change is in +Debian and Ubuntu for more than three releases now and nothing around +it seems to have totally broken. +Never the less the biggest risk I see is something unexpected in one of +the other libslang2 users. + + + [Other Info] + + * n/a + + --- + When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: - Installed: 5.101-0ubuntu1~wily - Candidate: 5.101-0ubuntu1~wily - Version table: - *** 5.101-0ubuntu1~wily 0 - 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages - 100 /var/lib/dpkg/status - 5.97-0ubuntu1 0 - 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages + Installed: 5.101-0ubuntu1~wily + Candidate: 5.101-0ubuntu1~wily + Version table: + *** 5.101-0ubuntu1~wily 0 + 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages + 100 /var/lib/dpkg/status + 5.97-0ubuntu1 0 + 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: In Progress Status in newt package in Ubuntu: Confirmed Status in slang2 package in Ubuntu: New Status in byobu package in Debian: New Bug description: [Impact] * Backport Debian fix for a crash in byobu due to libslang2 [Test Case] * byobu-screen * in there hit F9 or start byobu-config * without the fix this crashes [Regression Potential] * This is changing a libs implementation and $ reverse-depends src:slang2 -r xenial is quite a long list. OTOH this is somewhat ok as the change is in Debian and Ubuntu for more than three releases now and nothing around it seems to have totally broken. Never the less the biggest risk I see is something unexpected in one of the other libslang2 users. [Other Info] * n/a --- When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
Then I guess tis is fixed now. ** Changed in: amd64-microcode (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: Fix Released Status in Ubuntu Kylin: Fix Released Status in amd64-microcode package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. 2017 update, amd64-microcode should also be seeded, as it is useful to have it autoinstallable. In the recent years there have been critical CPU security vulnerabilities which got fixed with microcode updates. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+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 1537528] Re: byobu-config segfault with screen backend
I have built a test ppa with the fix [1]. That fixes the issue for me, I'd need a review [2] to feel confident going forward but it LGTM. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3309 [2]: https://code.launchpad.net/~paelzer/ubuntu/+source/slang2/+git/slang2/+merge/348667 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: In Progress Status in newt package in Ubuntu: Confirmed Status in slang2 package in Ubuntu: New Status in byobu package in Debian: New Bug description: When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1537528] Re: byobu-config segfault with screen backend
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/slang2/+git/slang2/+merge/348667 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: In Progress Status in newt package in Ubuntu: Confirmed Status in slang2 package in Ubuntu: New Status in byobu package in Debian: New Bug description: When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1779092] [NEW] cyclic reboot with latest kernels possibly related to the cpu microcode updater
Public bug reported: It happened like this: using kernel 3.13.0-144 (14.04) - ok jun 9: installed kernel 3.13.0-149 and rebooted - ok jun 21: installed some updates including update to the cpu microcode which was set up to execute at the next boot jun 28: rebooted to the same kernel 149 and the system went into cyclic reboot: shows grub screen, when the default kernel is selected reboots immediately with no messages and without creating any logs, nothing in /var/log with appropriate times booted to 144 - no issues tried upgrading to a new kernel (151) - same cyclic reboot booted back to 144 I am not telling the microcode update is the culprit, but it is mighty suspicious. It cannot be uninstalled using standard tools without uninstalling the kernels packages (linux-generic, linux-image-generic, linux-generic-pae, linux-image-generic-pae). I have both intel-microcode and amd64-microcode installed (CPU is AMD phenom X4 975). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 Uname: Linux 3.13.0-144-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Thu Jun 28 13:04:38 2018 InstallationDate: Installed on 2011-08-18 (2505 days ago) InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-10-18 (1349 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1779092 Title: cyclic reboot with latest kernels possibly related to the cpu microcode updater Status in xorg package in Ubuntu: New Bug description: It happened like this: using kernel 3.13.0-144 (14.04) - ok jun 9: installed kernel 3.13.0-149 and rebooted - ok jun 21: installed some updates including update to the cpu microcode which was set up to execute at the next boot jun 28: rebooted to the same kernel 149 and the system went into cyclic reboot: shows grub screen, when the default kernel is selected reboots immediately with no messages and without creating any logs, nothing in /var/log with appropriate times booted to 144 - no issues tried upgrading to a new kernel (151) - same cyclic reboot booted back to 144 I am not telling the microcode update is the culprit, but it is mighty suspicious. It cannot be uninstalled using standard tools without uninstalling the kernels packages (linux-generic, linux-image-generic, linux-generic-pae, linux-image-generic-pae). I have both intel- microcode and amd64-microcode installed (CPU is AMD phenom X4 975). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 Uname: Linux 3.13.0-144-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Thu Jun 28 13:04:38 2018 InstallationDate: Installed on 2011-08-18 (2505 days ago) InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-10-18 (1349 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1779092/+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 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.
*** This bug is a duplicate of bug 1652282 *** https://bugs.launchpad.net/bugs/1652282 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gparted (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1744372 Title: gparted does not start - Unit -.mount does not exist, proceeding anyway. Status in gparted package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Invalid Bug description: 1. fresh ubuntu 18.04 daily: lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. install gparted with Software: gparted: Installiert: 0.30.0-3ubuntu1 Installationskandidat: 0.30.0-3ubuntu1 Versionstabelle: *** 0.30.0-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. launch with icon - enter password - nothing. 4.launch in terminal: Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. How to Fix: run xhost +local: before gparted! # this only bypass the wayland restriction; meaning a security violation (not a fix !!! ) thomas@ubuntu-1804:~$ xhost +local: non-network local connections being added to access control list thomas@ubuntu-1804:~$ gparted Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. Gtk-Message: Failed to load module "canberra-gtk-module" == libparted : 3.2 == Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gparted 0.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 19:45:14 2018 InstallationDate: Installed on 2018-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1744372/+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 1762766] Re: apt-get update hangs when apt-transport-https is not installed
** Description changed: - When "apt-get update" is run on a docker container running Ubuntu v16.04 - and containing an additional apt source repository hosted on an https - webserver, the "apt-get update" command hangs. + [Impact] + Two or more sources with an unknown protocol cause apt update to hang + + [Test case] + Add two or more sources with an unknown protocol and run update + + [Regression potential] + This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods. + + [Original bug report] + When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( ** Description changed: [Impact] - Two or more sources with an unknown protocol cause apt update to hang + Two or more sources with an unknown protocol cause apt update to hang. For example, when using the https method on a system without integrated https support and without apt-transport-https installed. [Test case] Add two or more sources with an unknown protocol and run update [Regression potential] This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods. [Original bug report] When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( -- 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/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] Two or more sources with an unknown protocol cause apt update to hang. For example, when using the https method on a system without integrated https support and without apt-transport-https installed. [Test case] Add two or more sources with an unknown protocol
[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution
Verified. The first dirmngr started by 1.6.1 stayed alive even after 1.6.2 finished executing; the dirmngr started by 1.6.2 was not alive anymore. + lxc launch -e ubuntu:bionic lp1773992-bionic Creating lp1773992-bionic Starting lp1773992-bionic + sleep 5 + lxc exec lp1773992-bionic -- sh -c 'apt-cache policy apt | grep Inst ; apt-key adv --recv-keys 843938DF228D22F7B3742BC0D94AA3F0EFE21092 < /dev/null ; sleep 2; ps aux' Installed: 1.6.1 Executing: /tmp/apt-key-gpghome.UEzrZXm31Q/gpg.1.sh --recv-keys 843938DF228D22F7B3742BC0D94AA3F0EFE21092 [...] root 326 0.0 0.0 173060 13952 ?Ss 09:39 0:00 dirmngr --daemon --homedir /tmp/apt-key-gpghome.UEzrZXm31Q root 411 0.0 0.0 37792 3428 ?R+ 09:40 0:00 ps aux + lxc exec lp1773992-bionic -- sh -c 'echo deb http://archive.ubuntu.com/ubuntu bionic-proposed main >> /etc/apt/sources.list && apt-get update && apt-get -y install apt/bionic-proposed' dpkg-preconfigure: unable to re-open stdin: No such file or directory + lxc exec lp1773992-bionic -- sh -c 'apt-cache policy apt | grep Inst ; apt-key adv --recv-keys 843938DF228D22F7B3742BC0D94AA3F0EFE21092 < /dev/null ; sleep 2; ps aux' Installed: 1.6.2 Executing: /tmp/apt-key-gpghome.EAd3H1TKh1/gpg.1.sh --recv-keys 843938DF228D22F7B3742BC0D94AA3F0EFE21092 gpg: key D94AA3F0EFE21092: 45 signatures not checked due to missing keys gpg: key D94AA3F0EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 159664 8980 ?Ss 09:39 0:00 /sbin/init root51 0.0 0.0 78436 9844 ?Ss 09:39 0:00 /lib/systemd/systemd-journald root63 0.0 0.0 33348 3580 ?Ss 09:39 0:00 /lib/systemd/systemd-udevd systemd+ 151 0.0 0.0 80012 5340 ?Ss 09:39 0:00 /lib/systemd/systemd-networkd systemd+ 152 0.0 0.0 70608 5332 ?Ss 09:39 0:00 /lib/systemd/systemd-resolved daemon 189 0.0 0.0 28332 2404 ?Ss 09:39 0:00 /usr/sbin/atd -f root 191 0.0 0.0 31748 3180 ?Ss 09:39 0:00 /usr/sbin/cron -f root 192 0.0 0.0 287988 7072 ?Ssl 09:39 0:00 /usr/lib/accountsservice/accounts-daemon root 194 0.0 0.0 61996 5736 ?Ss 09:39 0:00 /lib/systemd/systemd-logind syslog 196 0.0 0.0 197636 4336 ?Ssl 09:39 0:00 /usr/sbin/rsyslogd -n root 197 0.0 0.0 1434880 21332 ? Ssl 09:39 0:00 /usr/lib/snapd/snapd root 201 0.0 0.0 170864 17152 ?Ssl 09:39 0:00 /usr/bin/python3 /usr/bin/networkd-dispatcher message+ 202 0.0 0.0 50052 4472 ?Ss 09:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only root 206 0.0 0.0 28 6696 ?Ssl 09:39 0:00 /usr/lib/policykit-1/polkitd --no-debug root 218 0.0 0.0 72296 5840 ?Ss 09:39 0:00 /usr/sbin/sshd -D root 227 0.0 0.0 16412 2404 console Ss+ 09:39 0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud console 115200,38400,9600 linux root 326 0.0 0.0 173060 13952 ?Ss 09:39 0:00 dirmngr --daemon --homedir /tmp/apt-key-gpghome.UEzrZXm31Q root 1445 0.0 0.0 4628 808 ?Ss+ 09:40 0:00 sh -c apt-cache policy apt | grep Inst ; apt-key adv --recv-keys 843938DF228D22F7B3742BC0D94AA3F0EFE21092 < /dev/null ; sleep 2; ps aux root 1563 0.0 0.0 37792 3252 ?R+ 09:40 0:00 ps aux ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1773992 Title: apt-key adv should gpgconf --kill all the things after execution Status in apt package in Ubuntu: Fix Released Status
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Description changed: + [Impact] + + * It should be possible to change DRM driver without rebooting. + * It should be possible to correctly suspend & resume, whilst preserving driver state. + * This bug is for userspace/logind fixes, required to get above working. + * Related kernel change is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658 + * https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59 + + [Test Case] + + * Test and verify that on machines with Nvidia discrete graphics, one + can change performance/power-saving modes without rebooting. + + [Regression Potential] + + * There are changes to the fd handling that are passed to logind. At + worst, fd to the NVIDIA driver will still be held, and thus one would + continue to not be able to switch graphics modes without rebooting. + + [Other Info] + + * original bug report: + refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => In Progress -- 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/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: In Progress Bug description: [Impact] * It should be possible to change DRM driver without rebooting. * It should be possible to correctly suspend & resume, whilst preserving driver state. * This bug is for userspace/logind fixes, required to get above working. * Related kernel change is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658 * https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59 [Test Case] * Test and verify that on machines with Nvidia discrete graphics, one can change performance/power-saving modes without rebooting. [Regression Potential] * There are changes to the fd handling that are passed to logind. At worst, fd to the NVIDIA driver will still be held, and thus one would continue to not be able to switch graphics modes without rebooting. [Other Info] * original bug report: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1778547] Re: Broken system lock counting
=== bionic OK (1.6.1 -> 1.6.2) =
+ lxc launch -e ubuntu:bionic lp1778547-bionic
Creating lp1778547-bionic
Starting lp1778547-bionic
+ sleep 5
+ lxc exec lp1778547-bionic -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.6.1
[('0', '/dev/pts/5'), ('1', '/dev/pts/5'), ('2', '/dev/pts/5'), ('3',
'pipe:[749881]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[43872]')]
[('0', '/dev/pts/5'), ('1', '/dev/pts/5'), ('2', '/dev/pts/5'), ('3',
'pipe:[749881]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[43872]')]
+ lxc exec lp1778547-bionic -- sh -c 'echo deb http://archive.ubuntu.com/ubuntu
bionic-proposed main >> /etc/apt/sources.list && apt-get update && apt-get -qy
install libapt-pkg5.0'
dpkg-preconfigure: unable to re-open stdin: No such file or directory
+ lxc exec lp1778547-bionic -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.6.2
[('0', '/dev/pts/4'), ('1', '/dev/pts/4'), ('2', '/dev/pts/4'), ('3',
'pipe:[779703]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[43872]')]
[('0', '/dev/pts/4'), ('1', '/dev/pts/4'), ('2', '/dev/pts/4'), ('3',
'pipe:[779703]'), ('4', ''), ('17', 'socket:[43872]')]
+ lxc stop lp1778547-bionic
artful OK (1.5.1 -> 1.5.2) ===
+ lxc launch -e ubuntu:artful lp1778547-artful
Creating lp1778547-artful
Starting lp1778547-artful
+ sleep 5
+ lxc exec lp1778547-artful -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.5.1
[('0', '/dev/pts/4'), ('1', '/dev/pts/4'), ('2', '/dev/pts/4'), ('3',
'pipe:[818873]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[43872]')]
[('0', '/dev/pts/4'), ('1', '/dev/pts/4'), ('2', '/dev/pts/4'), ('3',
'pipe:[818873]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[43872]')]
+ lxc exec lp1778547-artful -- sh -c 'echo deb http://archive.ubuntu.com/ubuntu
artful-proposed main >> /etc/apt/sources.list && apt-get update && apt-cache
policy libapt-pkg5.0 && apt-get -y install libapt-pkg5.0'
dpkg-preconfigure: unable to re-open stdin: No such file or directory
+ lxc exec lp1778547-artful -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.5.2
[('0', '/dev/pts/4'), ('1', '/dev/pts/4'), ('2', '/dev/pts/4'), ('3',
'pipe:[826053]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[43872]')]
[('0', '/dev/pts/4'), ('1', '/dev/pts/4'), ('2', '/dev/pts/4'), ('3',
'pipe:[826053]'), ('4', ''), ('17', 'socket:[43872]')]
== xenial OK (1.2.26->1.2.27) =
+ lxc launch -e ubuntu:xenial lp1778547-xenial
Creating lp1778547-xenial
Starting lp1778547-xenial
+ sleep 5
+ lxc exec lp1778547-xenial -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.2.26
[('0', '/dev/pts/6'), ('1', '/dev/pts/6'), ('2', '/dev/pts/6'), ('3',
'pipe:[764358]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[43872]')]
[('0', '/dev/pts/6'), ('1', '/dev/pts/6'), ('2', '/dev/pts/6'), ('3',
'pipe:[764358]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[43872]')]
+ lxc exec lp1778547-xenial -- sh -c 'echo deb http://archive.ubuntu.com/ubuntu
xenial-proposed main >> /etc/apt/sources.list && apt-get update && apt-get -qy
install libapt-pkg5.0'
dpkg-preconfigure: unable to re-open stdin: No such file or directory
+ lxc exec lp1778547-xenial -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.2.27
[('0', '/dev/pts/3'), ('1', '/dev/pts/3'), ('2', '/dev/pts/3'), ('3',
'pipe:[781507]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[43872]')]
[('0', '/dev/pts/3'), ('1', '/dev/pts/3'), ('2', '/dev/pts/3'), ('3',
'pipe:[781507]'), ('4', ''), ('17', 'socket:[43872]')]
+ lxc stop lp1778547-xenial
** Tags removed: verification-needed verification-needed-artful
verification-needed-bionic verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-bionic verification-done-xenial
--
You received this bug
[Touch-packages] [Bug 1537528] Re: byobu-config segfault with screen backend
** Also affects: slang2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: In Progress Status in newt package in Ubuntu: Confirmed Status in slang2 package in Ubuntu: New Status in byobu package in Debian: New Bug description: When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1772632] Re: Backport packages for 16.04.5 HWE stack
thanks for testing, marking as verified ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1772632] Re: Backport packages for 16.04.5 HWE stack
QA also tested Intel platform below: CPU/GPU: - Intel(R) Pentium(R) Silver J5005 CPU @ 1.50GHz - Intel Corporation Device 3184 (rev 03) Xorg: ii python3-xkit 0.5.0ubuntu2 all library for the manipulation of xorg.conf files (Python 3) ii xorg 1:7.7+13ubuntu3 amd64X.Org X Window System ii xorg-docs-core 1:1.7.1-1ubuntu1 all Core documentation for the X.org X Window System ii xserver-xorg-core-hwe-16.042:1.19.6-1ubuntu4~16.04.1 amd64Xorg X server - core server ii xserver-xorg-hwe-16.04 1:7.7+16ubuntu3~16.04.1 amd64X.Org X server ii xserver-xorg-input-all-hwe-16.04 1:7.7+16ubuntu3~16.04.1 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-evdev-hwe-16.04 1:2.10.5-1ubuntu1~16.04.1 amd64X.Org X server -- evdev input driver ii xserver-xorg-input-synaptics-hwe-16.04 1.9.0-1ubuntu1~16.04.1 amd64Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-wacom-hwe-16.04 1:0.34.0-0ubuntu2~16.04.1 amd64X.Org X server -- Wacom input driver ii xserver-xorg-legacy-hwe-16.04 2:1.19.6-1ubuntu4~16.04.1 amd64setuid root Xorg server wrapper ii xserver-xorg-video-all-hwe-16.04 1:7.7+16ubuntu3~16.04.1 amd64X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu-hwe-16.0418.0.1-1~16.04.1 amd64X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati-hwe-16.04 1:18.0.1-1~16.04.1 amd64X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev-hwe-16.04 1:0.4.4-1build6~16.04.1 amd64X.Org X server -- fbdev display driver ii xserver-xorg-video-intel-hwe-16.04 2:2.99.917+git20171229-1~16.04.1 amd64X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-nouveau-hwe-16.04 1:1.0.15-2~16.04.1 amd64X.Org X server -- Nouveau display driver ii xserver-xorg-video-qxl-hwe-16.04 0.1.5-2build1~16.04.1 amd64X.Org X server -- QXL display driver ii xserver-xorg-video-radeon-hwe-16.041:18.0.1-1~16.04.1 amd64X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa-hwe-16.04 1:2.3.4-1build3~16.04.1 amd64X.Org X server -- VESA display driver ii xserver-xorg-video-vmware-hwe-16.041:13.2.1-1build1~16.04.1 amd64X.Org X server -- VMware display driver Mesa: ii libegl1-mesa:amd64 18.0.5-0ubuntu0~16.04.1 amd64free implementation of the EGL API -- runtime ii libgl1-mesa-dri:amd64 18.0.5-0ubuntu0~16.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 18.0.5-0ubuntu0~16.04.1 amd64free implementation of the OpenGL API -- GLX runtime ii libglapi-mesa:amd6418.0.5-0ubuntu0~16.04.1 amd64free implementation of the GL API -- shared library ii libglu1-mesa:amd64 9.0.0-2.1 amd64Mesa OpenGL utility library (GLU) ii libtxc-dxtn-s2tc0:amd640~git20131104-1.1 amd64Texture compression library for Mesa ii libwayland-egl1-mesa:amd64 18.0.5-0ubuntu0~16.04.1 amd64implementation of the Wayland EGL platform -- runtime ii mesa-utils 8.3.0-1 amd64Miscellaneous Mesa GL utilities llvm: ii libllvm5.0:amd64 1:5.0-3~16.04.1 amd64Modular compiler and toolchain technologies, runtime library ii libllvm6.0:amd64 1:6.0-1ubuntu2~16.04.1 amd64Modular compiler and toolchain technologies, runtime library -- 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/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid
[Touch-packages] [Bug 1778547] Re: Broken system lock counting
Sorry, few typos in the script
** Description changed:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the following script should show one lock file in the first
line, and none in the last line.
def maybe_readlink(path):
- try:
- return os.readlink("/proc/self/fd/" + p)
- except:
- return ""
+ try:
+ return os.readlink(path)
+ except:
+ return ""
import os, apt_pkg
apt_pkg.init()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_unlock()
apt_pkg.pkgsystem_unlock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
-
[Test output]
good, cosmic:
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'/var/lib/dpkg/lock'), ('4', '')]
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'')]
bad, bionic:
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[53931]')]
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[53931]')]
-
[Regression potential]
A locking change can potentially break locking, but this one seems like an
obvious off-by-one error.
** Description changed:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the following script should show one lock file in the first
line, and none in the last line.
def maybe_readlink(path):
try:
return os.readlink(path)
except:
return ""
import os, apt_pkg
apt_pkg.init()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_lock()
+ print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
apt_pkg.pkgsystem_unlock()
apt_pkg.pkgsystem_unlock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
[Test output]
good, cosmic:
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'/var/lib/dpkg/lock'), ('4', '')]
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'')]
bad, bionic:
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[53931]')]
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[53931]')]
[Regression potential]
A locking change can potentially break locking, but this one seems like an
obvious off-by-one error.
--
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/1778547
Title:
Broken system lock counting
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Artful:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the following script should show one lock file in the first
line, and none in the last line.
def maybe_readlink(path):
try:
return os.readlink(path)
except:
return ""
import os, apt_pkg
apt_pkg.init()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_lock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
apt_pkg.pkgsystem_unlock()
apt_pkg.pkgsystem_unlock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
[Test output]
good, cosmic:
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'/var/lib/dpkg/lock'), ('4', '')]
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'')]
bad, bionic:
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[53931]')]
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[53931]')]
[Regression potential]
A locking change can potentially break locking, but this one seems like an
obvious off-by-one error.
To manage notifications about this bug
[Touch-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack
Hello Timo, QA tested A+A platforms below, and user can login to the system via Graphics mode. AMD CPU/GPU: - AMD PRO A12-9800E R7, 12 COMPUTE CORES 4C+8G - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:9874 AMD CPU/GPU: - AMD E2-9000 RADEON R2, 4 COMPUTE CORES 2C+2G - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:98e4 Here is the list of package version that should meet your expectations, BTW. Xorg: ii python3-xkit 0.5.0ubuntu2 all library for the manipulation of xorg.conf files (Python 3) ii xorg 1:7.7+13ubuntu3 amd64X.Org X Window System ii xorg-docs-core 1:1.7.1-1ubuntu1 all Core documentation for the X.org X Window System ii xserver-xorg-core-hwe-16.042:1.19.6-1ubuntu4~16.04.1 amd64Xorg X server - core server ii xserver-xorg-hwe-16.04 1:7.7+16ubuntu3~16.04.1 amd64X.Org X server ii xserver-xorg-input-all-hwe-16.04 1:7.7+16ubuntu3~16.04.1 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-evdev-hwe-16.04 1:2.10.5-1ubuntu1~16.04.1 amd64X.Org X server -- evdev input driver ii xserver-xorg-input-synaptics-hwe-16.04 1.9.0-1ubuntu1~16.04.1 amd64Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-wacom-hwe-16.04 1:0.34.0-0ubuntu2~16.04.1 amd64X.Org X server -- Wacom input driver ii xserver-xorg-legacy-hwe-16.04 2:1.19.6-1ubuntu4~16.04.1 amd64setuid root Xorg server wrapper ii xserver-xorg-video-all-hwe-16.04 1:7.7+16ubuntu3~16.04.1 amd64X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu-hwe-16.0418.0.1-1~16.04.1 amd64X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati-hwe-16.04 1:18.0.1-1~16.04.1 amd64X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev-hwe-16.04 1:0.4.4-1build6~16.04.1 amd64X.Org X server -- fbdev display driver ii xserver-xorg-video-intel-hwe-16.04 2:2.99.917+git20171229-1~16.04.1 amd64X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-nouveau-hwe-16.04 1:1.0.15-2~16.04.1 amd64X.Org X server -- Nouveau display driver ii xserver-xorg-video-qxl-hwe-16.04 0.1.5-2build1~16.04.1 amd64X.Org X server -- QXL display driver ii xserver-xorg-video-radeon-hwe-16.041:18.0.1-1~16.04.1 amd64X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa-hwe-16.04 1:2.3.4-1build3~16.04.1 amd64X.Org X server -- VESA display driver ii xserver-xorg-video-vmware-hwe-16.041:13.2.1-1build1~16.04.1 amd64X.Org X server -- VMware display driver Mesa: ii libegl1-mesa:amd64 18.0.5-0ubuntu0~16.04.1 amd64free implementation of the EGL API -- runtime ii libgl1-mesa-dri:amd64 18.0.5-0ubuntu0~16.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 18.0.5-0ubuntu0~16.04.1 amd64free implementation of the OpenGL API -- GLX runtime ii libglapi-mesa:amd6418.0.5-0ubuntu0~16.04.1 amd64free implementation of the GL API -- shared library ii libglu1-mesa:amd64 9.0.0-2.1 amd64Mesa OpenGL utility library (GLU) ii libtxc-dxtn-s2tc0:amd640~git20131104-1.1 amd64Texture compression library for Mesa ii libwayland-egl1-mesa:amd64 18.0.5-0ubuntu0~16.04.1 amd64implementation of the Wayland EGL platform -- runtime ii mesa-utils 8.3.0-1 amd64Miscellaneous Mesa GL utilities libllvm: ii libllvm4.0:amd64 1:4.0-1ubuntu1~16.04.2 amd64Modular compiler and toolchain technologies, runtime library ii libllvm6.0:amd64 1:6.0-1ubuntu2~16.04.1 amd64Modular compiler and toolchain technologies, runtime library -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is
[Touch-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack
** Changed in: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu) Status: New => Invalid ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu) ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu Xenial) ** No longer affects: xserver-xorg-video-ati (Ubuntu) ** No longer affects: xserver-xorg-video-ati (Ubuntu Xenial) ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** No longer affects: xserver-xorg-video-intel (Ubuntu Xenial) ** Changed in: xserver-xorg-video-ati-hwe-16.04 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-intel-hwe-16.04 (Ubuntu) Status: New => Invalid -- 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/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1772844] Re: snapd didn't initialize all the seeded snaps
This got fixed in the cosmic seeds in https://git.launchpad.net/~ubuntu- core-dev/ubuntu- seeds/+git/ubuntu/commit/?id=764ab69745c53d8009b7cf9317df1fd9e26bbca2 and in bionic with https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/?id=2c2f14307069e1554eaba0b3882e8fb41a2c4877 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Confirmed Status in snapd: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+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 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Changed in: python3-defaults (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: In Progress Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: In Progress Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+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 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
This bug was fixed in the package rfkill - 0.5-1ubuntu3.1 --- rfkill (0.5-1ubuntu3.1) xenial; urgency=medium * postinst: do not fail in case udev is not available (e.g. chroot) (LP: #1777476) -- Gianfranco Costamagna Mon, 18 Jun 2018 17:53:33 +0200 ** Changed in: rfkill (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: Fix Released Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+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 1777476] Update Released
The verification of the Stable Release Update for rfkill has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: Fix Released Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+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 1597733] Re: ModemManager crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1569522 *** https://bugs.launchpad.net/bugs/1569522 Seems duplicate of non-private (public) bug #1099766: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1099766 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1597733 Title: ModemManager crashed with SIGABRT in g_assertion_message() Status in modemmanager package in Ubuntu: New Bug description: I got this crash while browsing my smartphone with my PC ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: modemmanager 1.4.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jun 30 13:42:53 2016 ExecutablePath: /usr/sbin/ModemManager InstallationDate: Installed on 2015-10-08 (265 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: /usr/sbin/ModemManager ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: modemmanager StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 mm_port_probe_run () mm_plugin_supports_port () ?? () Title: ModemManager crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to xenial on 2016-04-26 (64 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1597733/+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 1099766] Re: modem-manager crashed with SIGABRT in g_assertion_message()
Still happens on Ubuntu 18.04. Maybe duplicate of bug #1099766 (and in turn of bug #1569522)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1099766 Title: modem-manager crashed with SIGABRT in g_assertion_message() Status in modemmanager package in Ubuntu: Confirmed Bug description: ran dist-upgrade and rebooted, noticed this crash after login ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: modemmanager 0.6.0.0.really-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Jan 15 14:33:29 2013 ExecutablePath: /usr/sbin/modem-manager MarkForUpload: True ProcCmdline: /usr/sbin/modem-manager ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: modemmanager StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () mm_plugin_base_supports_task_complete () Title: modem-manager crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1099766/+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
