[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Ubuntu 18 is still with the same bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1888101] Re: 'unsupported protocol' error when using PyMySQL
Hi, I'm having a similar issue. Mariadb server with ssl connection, I'm trying to connect a software called Superset with PyMySQL driver. Error message looks identical: WARNING:superset.views.core:Connection failed (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on '' ([SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1108))") (Background on this error at: http://sqlalche.me/e/13/e3q8) Client running on Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1888101 Title: 'unsupported protocol' error when using PyMySQL Status in openssl package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) openssl: Installiert: 1.1.1f-1ubuntu2 Installationskandidat: 1.1.1f-1ubuntu2 Versionstabelle: *** 1.1.1f-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) + 4) I am trying to connect to my MariaDB with python package "PyMySQL" and SSL enabled. On my old installation (Kubuntu 19.10) this worked. With the new installation (also new PC: Xubuntu 20.04) I get this error message: ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1108) Here are my installation details: Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 28 May 2019 New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 31 Mar 2020 When I use python with a different SSL version...: this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does not work together with PyMySQL. Some more details I have posted here: https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssl 1.1.1f-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jul 18 15:42:27 2020 InstallationDate: Installed on 2020-07-13 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1888101/+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 1888101] Re: 'unsupported protocol' error when using PyMySQL
Hi Seth, In my case its sort of a complicated setup. We have a MariaDB running on an Ubuntu 18.04 server with SSL and ed25519. Then, I followed the instructions on the Superset documentation for manual installation (https://superset.incubator.apache.org/installation.html) and installed the software on an Ubuntu 20.04. When using the mysqldb python driver the Superset software was giving out an error and I decided to try to change to PyMySQL (since superset uses SLQAlchemy should not make a big difference). Then the error is shown when trying to connect. I haven't tried another version of Python or Openssl. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1888101 Title: 'unsupported protocol' error when using PyMySQL Status in openssl package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) openssl: Installiert: 1.1.1f-1ubuntu2 Installationskandidat: 1.1.1f-1ubuntu2 Versionstabelle: *** 1.1.1f-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) + 4) I am trying to connect to my MariaDB with python package "PyMySQL" and SSL enabled. On my old installation (Kubuntu 19.10) this worked. With the new installation (also new PC: Xubuntu 20.04) I get this error message: ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1108) Here are my installation details: Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 28 May 2019 New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 31 Mar 2020 When I use python with a different SSL version...: this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does not work together with PyMySQL. Some more details I have posted here: https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssl 1.1.1f-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jul 18 15:42:27 2020 InstallationDate: Installed on 2020-07-13 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1888101/+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 1517569] [NEW] after change my password using a character * i was unable to login in graphic mode, but in terminal it works ok, i change to a password without * and it works fine
Public bug reported: I'm using ubuntu 15.10 and recently change my password it works ok, but after reboot my machine i can't login anymore using the graphic interface, but when i enter the command line mode i can login normally. I make sure that the problem was the password changed instaling ubuntu in a virtual machine and trying the same thing, i realize that when i use the * character in my password this error occurs. Once occurred the first time i try to change the password and login again in graphic mode but it doesn't work, only reinstalling the system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Wed Nov 18 15:21:05 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-06 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1517569 Title: after change my password using a character * i was unable to login in graphic mode, but in terminal it works ok, i change to a password without * and it works fine in all, graphic and terminal. Status in lightdm package in Ubuntu: New Bug description: I'm using ubuntu 15.10 and recently change my password it works ok, but after reboot my machine i can't login anymore using the graphic interface, but when i enter the command line mode i can login normally. I make sure that the problem was the password changed instaling ubuntu in a virtual machine and trying the same thing, i realize that when i use the * character in my password this error occurs. Once occurred the first time i try to change the password and login again in graphic mode but it doesn't work, only reinstalling the system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Wed Nov 18 15:21:05 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-06 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1517569/+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 1529123] [NEW] package libjpeg62-turbo-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-d
Public bug reported: package libjpeg62-turbo-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 ProblemType: Package DistroRelease: Kali 2.0 Package: libjpeg62-turbo-dev (not installed) ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Thu Dec 24 13:10:11 2015 DuplicateSignature: package:libjpeg62-turbo-dev:(not installed):a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 ErrorMessage: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-12-24 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: libjpeg-turbo Title: package libjpeg62-turbo-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check sana -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1529123 Title: package libjpeg62-turbo-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 Status in libjpeg-turbo package in Ubuntu: New Bug description: package libjpeg62-turbo-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 ProblemType: Package DistroRelease: Kali 2.0 Package: libjpeg62-turbo-dev (not installed) ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Thu Dec 24 13:10:11 2015 DuplicateSignature: package:libjpeg62-turbo-dev:(not installed):a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 ErrorMessage: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-12-24 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: libjpeg-turbo Title: package libjpeg62-turbo-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/jpeglib.h', que também está no pacote libjpeg-turbo8-dev:amd64 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1529123/+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 1461668] [NEW] ir-keytable presses recognised but not working
Public bug reported: I'm using ir-keytable to map button presses on a remote control to keyboard presses. I'm using an old Apple remote and after scanning for the keycodes I've produced a keymap file which is loaded by ir-keytable. However, I have only succeeded in getting the arrow keys and enter working (KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_ENTER). All the other keypresses that I've tried are recognised by ir-keytable, but are not being passed to the system. For example, the KEY_BACKSPACE which I need. Running ir-keytable -t and pressing the relevant remote button I get: 1433359068.641206: event type EV_KEY(0x01) key_down: KEY_BACKSPACE(0x0001) 1433359068.641206: event type EV_SYN(0x00). 1433359068.641230: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641230: event type EV_SYN(0x00). 1433359068.641235: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641235: event type EV_SYN(0x00). But it never works as backspace. For example, if I open a text editor and use the arrow or enter keys, I can see the cursor moving around. But the backspace does not work. Also any other keymap that I've tried (e.g. numbers, letters) does not work. I'm using ir-keytable 1.6.0-2 in xubuntu 15.04. My system is a NUC5i5RYHK, the IR driver is nuvoton-cir. The output of ir-keytable is: Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver nuvoton-cir, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ SHARP XMP other Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC Name: Nuvoton w836x7hg Infrared Remote bus: 25, vendor/product: 1050:00c3, version: 0x0033 Repeat delay = 500 ms, repeat period = 125 ms ** Affects: v4l-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1461668 Title: ir-keytable presses recognised but not working Status in v4l-utils package in Ubuntu: New Bug description: I'm using ir-keytable to map button presses on a remote control to keyboard presses. I'm using an old Apple remote and after scanning for the keycodes I've produced a keymap file which is loaded by ir- keytable. However, I have only succeeded in getting the arrow keys and enter working (KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_ENTER). All the other keypresses that I've tried are recognised by ir-keytable, but are not being passed to the system. For example, the KEY_BACKSPACE which I need. Running ir-keytable -t and pressing the relevant remote button I get: 1433359068.641206: event type EV_KEY(0x01) key_down: KEY_BACKSPACE(0x0001) 1433359068.641206: event type EV_SYN(0x00). 1433359068.641230: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641230: event type EV_SYN(0x00). 1433359068.641235: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641235: event type EV_SYN(0x00). But it never works as backspace. For example, if I open a text editor and use the arrow or enter keys, I can see the cursor moving around. But the backspace does not work. Also any other keymap that I've tried (e.g. numbers, letters) does not work. I'm using ir-keytable 1.6.0-2 in xubuntu 15.04. My system is a NUC5i5RYHK, the IR driver is nuvoton-cir. The output of ir-keytable is: Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver nuvoton-cir, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ SHARP XMP other Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC Name: Nuvoton w836x7hg Infrared Remote bus: 25, vendor/product: 1050:00c3, version: 0x0033 Repeat delay = 500 ms, repeat period = 125 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1461668/+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 1461668] Re: ir-keytable presses recognised but not working
I should also add that I'm using an upstream kernel (3.19.8-992-generic #201505300306) due to some issue with the HDMI sound, but with the default kernel I had before the remote issue was exactly the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1461668 Title: ir-keytable presses recognised but not working Status in v4l-utils package in Ubuntu: New Bug description: I'm using ir-keytable to map button presses on a remote control to keyboard presses. I'm using an old Apple remote and after scanning for the keycodes I've produced a keymap file which is loaded by ir- keytable. However, I have only succeeded in getting the arrow keys and enter working (KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_ENTER). All the other keypresses that I've tried are recognised by ir-keytable, but are not being passed to the system. For example, the KEY_BACKSPACE which I need. Running ir-keytable -t and pressing the relevant remote button I get: 1433359068.641206: event type EV_KEY(0x01) key_down: KEY_BACKSPACE(0x0001) 1433359068.641206: event type EV_SYN(0x00). 1433359068.641230: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641230: event type EV_SYN(0x00). 1433359068.641235: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641235: event type EV_SYN(0x00). But it never works as backspace. For example, if I open a text editor and use the arrow or enter keys, I can see the cursor moving around. But the backspace does not work. Also any other keymap that I've tried (e.g. numbers, letters) does not work. I'm using ir-keytable 1.6.0-2 in xubuntu 15.04. My system is a NUC5i5RYHK, the IR driver is nuvoton-cir. The output of ir-keytable is: Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver nuvoton-cir, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ SHARP XMP other Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC Name: Nuvoton w836x7hg Infrared Remote bus: 25, vendor/product: 1050:00c3, version: 0x0033 Repeat delay = 500 ms, repeat period = 125 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1461668/+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 1461668] Re: ir-keytable presses recognised but not working
Hi, I've just tried swapping the key code for up and back, and now the old button for backspace does up as intended, but the old button for up never does backspace. This is my mapping file: ==> universal_wr7 <== # Adapted from Apple Remote by Sab, Universal WR7 0x77e1503d KEY_UP 0x77e1303d KEY_DOWN 0x77e1903d KEY_LEFT 0x77e1603d KEY_RIGHT 0x77e1a03d KEY_ENTER 0x77e1c03d KEY_BACKSPACE I have a init.d script that is the following: #!/usr/bin/env bash echo 'Modprobing...' modprobe -r nuvoton_cir sleep 1 echo 'Echoing...' echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources sleep 1 echo 'Modprobing...' modprobe nuvoton-cir sleep 1 echo 'Clearing the old keytable...' ir-keytable -c sleep 1 echo 'Injecting the new keytable...' ir-keytable -p NEC,RC-5,RC-6,JVC,SONY,LIRC -w /etc/rc_keymaps/universal_wr7 echo 'Done.' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1461668 Title: ir-keytable presses recognised but not working Status in v4l-utils package in Ubuntu: New Bug description: I'm using ir-keytable to map button presses on a remote control to keyboard presses. I'm using an old Apple remote and after scanning for the keycodes I've produced a keymap file which is loaded by ir- keytable. However, I have only succeeded in getting the arrow keys and enter working (KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_ENTER). All the other keypresses that I've tried are recognised by ir-keytable, but are not being passed to the system. For example, the KEY_BACKSPACE which I need. Running ir-keytable -t and pressing the relevant remote button I get: 1433359068.641206: event type EV_KEY(0x01) key_down: KEY_BACKSPACE(0x0001) 1433359068.641206: event type EV_SYN(0x00). 1433359068.641230: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641230: event type EV_SYN(0x00). 1433359068.641235: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641235: event type EV_SYN(0x00). But it never works as backspace. For example, if I open a text editor and use the arrow or enter keys, I can see the cursor moving around. But the backspace does not work. Also any other keymap that I've tried (e.g. numbers, letters) does not work. I'm using ir-keytable 1.6.0-2 in xubuntu 15.04. My system is a NUC5i5RYHK, the IR driver is nuvoton-cir. The output of ir-keytable is: Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver nuvoton-cir, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ SHARP XMP other Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC Name: Nuvoton w836x7hg Infrared Remote bus: 25, vendor/product: 1050:00c3, version: 0x0033 Repeat delay = 500 ms, repeat period = 125 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1461668/+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 1461668] Re: ir-keytable presses recognised but not working
Using evtest it does show all keypresses, including the KEY_BACKSPACE that doesn't seem to work anywhere else. Example: Event: time 1433538659.320476, type 1 (EV_KEY), code 14 (KEY_BACKSPACE), value 1 Event: time 1433538659.320476, -- EV_SYN Event: time 1433538659.320499, type 4 (EV_MSC), code 4 (MSC_SCAN), value 77e1c03d Event: time 1433538659.320499, -- EV_SYN Event: time 1433538659.320501, type 4 (EV_MSC), code 4 (MSC_SCAN), value 77e1c03d Event: time 1433538659.320501, -- EV_SYN Event: time 1433538659.571124, type 1 (EV_KEY), code 14 (KEY_BACKSPACE), value 0 Event: time 1433538659.571124, -- EV_SYN -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1461668 Title: ir-keytable presses recognised but not working Status in v4l-utils package in Ubuntu: New Bug description: I'm using ir-keytable to map button presses on a remote control to keyboard presses. I'm using an old Apple remote and after scanning for the keycodes I've produced a keymap file which is loaded by ir- keytable. However, I have only succeeded in getting the arrow keys and enter working (KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_ENTER). All the other keypresses that I've tried are recognised by ir-keytable, but are not being passed to the system. For example, the KEY_BACKSPACE which I need. Running ir-keytable -t and pressing the relevant remote button I get: 1433359068.641206: event type EV_KEY(0x01) key_down: KEY_BACKSPACE(0x0001) 1433359068.641206: event type EV_SYN(0x00). 1433359068.641230: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641230: event type EV_SYN(0x00). 1433359068.641235: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641235: event type EV_SYN(0x00). But it never works as backspace. For example, if I open a text editor and use the arrow or enter keys, I can see the cursor moving around. But the backspace does not work. Also any other keymap that I've tried (e.g. numbers, letters) does not work. I'm using ir-keytable 1.6.0-2 in xubuntu 15.04. My system is a NUC5i5RYHK, the IR driver is nuvoton-cir. The output of ir-keytable is: Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver nuvoton-cir, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ SHARP XMP other Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC Name: Nuvoton w836x7hg Infrared Remote bus: 25, vendor/product: 1050:00c3, version: 0x0033 Repeat delay = 500 ms, repeat period = 125 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1461668/+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 1461668] Re: ir-keytable presses recognised but not working
I've managed to fix the problem. Turns out lirc was the culprit here. Uninstalling lirc and making sure that the file with my keymaps is in /etc/rc_maps.cfg solves the problem. ** Changed in: v4l-utils (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1461668 Title: ir-keytable presses recognised but not working Status in v4l-utils package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Bug description: I'm using ir-keytable to map button presses on a remote control to keyboard presses. I'm using an old Apple remote and after scanning for the keycodes I've produced a keymap file which is loaded by ir- keytable. However, I have only succeeded in getting the arrow keys and enter working (KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_ENTER). All the other keypresses that I've tried are recognised by ir-keytable, but are not being passed to the system. For example, the KEY_BACKSPACE which I need. Running ir-keytable -t and pressing the relevant remote button I get: 1433359068.641206: event type EV_KEY(0x01) key_down: KEY_BACKSPACE(0x0001) 1433359068.641206: event type EV_SYN(0x00). 1433359068.641230: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641230: event type EV_SYN(0x00). 1433359068.641235: event type EV_MSC(0x04): scancode = 0x77e1c03d 1433359068.641235: event type EV_SYN(0x00). But it never works as backspace. For example, if I open a text editor and use the arrow or enter keys, I can see the cursor moving around. But the backspace does not work. Also any other keymap that I've tried (e.g. numbers, letters) does not work. I'm using ir-keytable 1.6.0-2 in xubuntu 15.04. My system is a NUC5i5RYHK, the IR driver is nuvoton-cir. The output of ir-keytable is: Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver nuvoton-cir, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ SHARP XMP other Enabled protocols: NEC RC-5 RC-6 JVC SONY LIRC Name: Nuvoton w836x7hg Infrared Remote bus: 25, vendor/product: 1050:00c3, version: 0x0033 Repeat delay = 500 ms, repeat period = 125 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1461668/+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 1334617] Re: [X550LB, Realtek ALC233, Mic, Internal] not working Ubuntu 14.04
** Changed in: alsa-driver (Ubuntu) Status: Expired => 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/1334617 Title: [X550LB, Realtek ALC233, Mic, Internal] not working Ubuntu 14.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: http://www.alsa- project.org/db/?f=70fd0de0d58f680c5a74ff1fbcf6dc46de5e5dc8 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexander 2433 F pulseaudio /dev/snd/controlC1: alexander 2433 F pulseaudio alexander 3242 F alsamixer CurrentDesktop: Unity Date: Thu Jun 26 13:22:07 2014 InstallationDate: Installed on 2014-06-23 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexander 2433 F pulseaudio /dev/snd/controlC1: alexander 2433 F pulseaudio alexander 3242 F alsamixer Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X550LB, Realtek ALC233, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LB.402 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LB.402:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334617/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
I am running Ubuntu 16.04 with plasma. I was experiencing this issue and downgraded the network-manager package to 1.2.2-0ubuntu0.16.04.4. Since the downgrade I haven't had any trouble. Waiting for fix in the latest version :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1615474] Re: Network Indicator / Connectivity-API is not accessible
rm .config/connectivity-service/config.ini.lock solved my problem instantly! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1615474 Title: Network Indicator / Connectivity-API is not accessible Status in Canonical System Image: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: Sometime in the last few days my phone lost the ability to connect to wifi networks and the network indicator at the top has stopped working. Currently between "Bluetooth" and "Sound" I have a gear icon and the caption "indicator-network". When I select it, the rest of the screen is blank. There are no settings available and no way to connect to a wifi network. On the System Settings app, if I tap on the "Wi-Fi" icon, I can see "Previous networks". But below that the page is just white, there is no way to select a wifi network. Rebooting the phone doesn't seem to fix the problem. Given that this is an MX4 and therefore the USB port doesn't work, and there's no SD card slot, there's vanishingly few ways to get data in and out of this phone now. If there's a solution to the problem, it's going to have to involve something other than updating system software. Current system software is Ubuntu 15.05 (OTA-12). - Per the comments the .config/connectivity-service/config.ini file seems to hold bad or outdated info and needs to be manually deleted and then recreated by the service. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+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 1468103] Re: rc.local runs earlier than cloud-init.service
A simple fix is something like this: Create the /etc/systemd/system/rc-local.service file with the following contents: [Unit] Description=/etc/rc.local Compatibility [Service] Type=idle ExecStart=/etc/rc.systemd TimeoutSec=0 RemainAfterExit=yes [Install] WantedBy=multi-user.target Create a file /etc/rc.systemd with whatever you want to run, set it to executable. Delete everything you added from rc.local until this gets properly fixed run systemctl daemon-reload Reboot to test it. Working for me at the moment -- 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/1468103 Title: rc.local runs earlier than cloud-init.service Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: per https://www.debian.org/doc/manuals/debian-faq/ch-customizing.en.html | The rc.local script is executed at the end of each multiuser runlevel. Generally speaking people expect rc.local to be run as "the last thing in boot". currently it is being run by systemd much earlier. Provided in the attached is user-data that tells cloud-init to write a file in /usr/local/bin/rc-local-message and edit set rc.local to execute it. On current wily, under most scenarios the script will not be executed as rc.local will most likely run before the cloud-init service has a chance to update /etc/rc.local. To reproduce: a.) launch an instance with provided user-data Expected behavior would be: 1. /run/rc-local-message exists with contents of /proc/uptime at the time it was run 2. /rc-local-message.mark exists with the number of times this script has been run ('1' after first boot) 3. /var/log/rc-local-message.log exists with a message like: [/var/log/rc-local-message.log] === successful boot 1 4. console log should also have message like in 3 with '/dev/console' 4 is broken as rc.local output is not sent to console as reported separately at bug 1468102. Related bugs: * bug 1468102: rc.local output does not go to console ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 220-7ubuntu1 ProcVersionSignature: User Name 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Tue Jun 23 20:21:50 2015 Ec2AMI: ami-0434 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2014.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2014.1.4 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1468103/+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 1527863] [NEW] screen display
Public bug reported: on eeepc 901, lost in 3/4 of screen , boot on systemd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 19 12:02:02 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] Subsystem: ASUSTeK Computer Inc. Device [1043:830f] InstallationDate: Installed on 2015-12-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209) MachineType: ASUSTeK Computer INC. 901 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash init=/sbin/upstart SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 901 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 901 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1 version.libdrm2: libdrm2 2.4.65-3 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Dec 19 12:00:39 2015 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 1612 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 805 vendor HSD xserver.version: 2:1.17.3-2ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 corruption i386 ubuntu xenial -- 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/1527863 Title: screen display Status in xorg package in Ubuntu: New Bug description: on eeepc 901, lost in 3/4 of screen , boot on systemd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 19 12:02:02 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] Subsystem: ASUSTeK Computer Inc. Device [1043:830f] InstallationDate: Installed on 2015-12-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209) MachineType: ASUSTeK Computer INC. 901 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash init=/sbin/upstart SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 901 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag:
[Touch-packages] [Bug 1527874] Re: lost 3/4 screen
boot systemd -- 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/1527874 Title: lost 3/4 screen Status in xorg package in Ubuntu: New Bug description: lost 3/4 screen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Dec 19 12:17:42 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] Subsystem: ASUSTeK Computer Inc. Device [1043:830f] InstallationDate: Installed on 2015-12-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209) MachineType: ASUSTeK Computer INC. 901 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 901 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 901 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1 version.libdrm2: libdrm2 2.4.65-3 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Dec 19 12:15:15 2015 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 824 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 805 vendor HSD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1527874/+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 1527874] [NEW] lost 3/4 screen
Public bug reported: lost 3/4 screen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Dec 19 12:17:42 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] Subsystem: ASUSTeK Computer Inc. Device [1043:830f] InstallationDate: Installed on 2015-12-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209) MachineType: ASUSTeK Computer INC. 901 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 901 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 901 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1 version.libdrm2: libdrm2 2.4.65-3 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Dec 19 12:15:15 2015 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 824 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 805 vendor HSD xserver.version: 2:1.17.3-2ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug corruption i386 ubuntu xenial -- 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/1527874 Title: lost 3/4 screen Status in xorg package in Ubuntu: New Bug description: lost 3/4 screen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Dec 19 12:17:42 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] Subsystem: ASUSTeK Computer Inc. Device [1043:830f] InstallationDate: Installed on 2015-12-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209) MachineType: ASUSTeK Computer INC. 901 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 901 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 901 dmi.product.version: x.x dmi.sys.vendor: A
[Touch-packages] [Bug 1527863] Re: screen display
boot upstart -- 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/1527863 Title: screen display Status in xorg package in Ubuntu: New Bug description: on eeepc 901, lost in 3/4 of screen , boot on systemd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 19 12:02:02 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:830f] Subsystem: ASUSTeK Computer Inc. Device [1043:830f] InstallationDate: Installed on 2015-12-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151209) MachineType: ASUSTeK Computer INC. 901 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash init=/sbin/upstart SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 901 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 901 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20151026-0ubuntu1 version.libdrm2: libdrm2 2.4.65-3 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Dec 19 12:00:39 2015 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 1612 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 805 vendor HSD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1527863/+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 1377742] Re: Window header mistype on selecting best server (portuguese system language, at least)
@mpt The bug should be assigned to the ubuntu-l10n-pt team, since it is in Portuguese, and not Brazilian Portuguese. I tried to assign to ubuntu-l10n-pt, but think I don't have privileges to do it. ** Changed in: software-properties (Ubuntu) Assignee: Ubuntu Brazilian Portuguese Translators (ubuntu-l10n-pt-br) => (unassigned) -- 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/1377742 Title: Window header mistype on selecting best server (portuguese system language, at least) Status in software-properties package in Ubuntu: Confirmed Bug description: I believe there is a mistype preventing text from being displayed as the window's header. The "" tag was closed incorrectly and so displayed as ordinary text. I do not know if this happens with any other version of Ubuntu except for the Portuguese version. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 23:28:28 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2014-09-21 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash 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/1377742/+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 592923] Re: Thompson-Wheeler logo in Haskell files
** Description changed: Binary package hint: humanity-icon-theme Wishlist: In the same fashion as Python and Ruby source code files have the text file background with their logo in the foreground, would it be possible to make the same in Haskell source code files (text/x-haskell and text/x-literate-haskell ; .hs and .lhs respectively) with the - Thompson-Wheeler logo [http://www.haskell.org/haskellwiki/Thompson- - Wheeler_logo] ? + Thompson-Wheeler logo [https://wiki.haskell.org/Thompson-Wheeler_logo] ? Thanks in advance. Post Scriptum: Literate Haskell is being listed as "LHS source code (text/x-literate-haskell)" and not as "Literate Haskell source code (text/x-literate-haskell)" as it should be. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/592923 Title: Thompson-Wheeler logo in Haskell files Status in humanity-icon-theme package in Ubuntu: Triaged Bug description: Binary package hint: humanity-icon-theme Wishlist: In the same fashion as Python and Ruby source code files have the text file background with their logo in the foreground, would it be possible to make the same in Haskell source code files (text/x-haskell and text/x-literate-haskell ; .hs and .lhs respectively) with the Thompson-Wheeler logo [https://wiki.haskell.org /Thompson-Wheeler_logo] ? Thanks in advance. Post Scriptum: Literate Haskell is being listed as "LHS source code (text/x-literate-haskell)" and not as "Literate Haskell source code (text/x-literate-haskell)" as it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/592923/+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 2000173] Re: Xorg freeze
I would also like to add that this issue also manifests when the display goes to sleep. Moving the mouse or touching the keyboard (which should wake the display up) produces no effect and requires turning the monitor off and on again. -- 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/2000173 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hello, I have a persistent issue where my freshly installed Ubuntu sleeps the monitor after booting. The solution is to turn the monitor off and on again. After turning it on the login screen is displayed. Note that when the screen is off even the combination CTRL+ALT+F2 to switch to a console TTY will not work. Rarely the system will boot to the login sleep without the screen going to sleep. There is the following message on dmesg: [ 63.052273] amdgpu :0a:00.0: [drm] *ERROR* mstb d9e48d98 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed System: Ubuntu 22.04.1 LTS CPU: AMD Ryzen 5 5600x 6-core processor × 12 GPU: AMD Radeon rx 6900 xt Monitor: DELL Ultrasharp U3415W connected with a Display Port <-> mini-Display Port cable. Using the default Ubuntu graphical drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 20 18:21:07 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 6900 XT [1002:0e3a] InstallationDate: Installed on 2022-12-05 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=UUID=08da7c47-3c82-4be1-8f1e-3546fd436ec5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2423 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2423:bd08/11/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2000173/+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 1449250] Re: Keyboard Layout "Portuguese (Brazil, nativo for US keyboards)" doesn't respect US keyboard layout.
Ubuntu 18.04.2 LTS and the problem still persist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1449250 Title: Keyboard Layout "Portuguese (Brazil, nativo for US keyboards)" doesn't respect US keyboard layout. Status in ibus package in Ubuntu: Confirmed Bug description: When setting up the keyboard layout to my bluetooth keyboard on my machine I saw the option to add a layout specific to Portuguese with the promise it would work with USA keyboards. But many letters are assigned to the wrong codes. 1. I'm using Ubuntu 14.04 2. I don't know the package responsible for this behaviour 3. I expected a behaviour similar to English USA International layout, but with cedilla when you press ' + C instead of the "ć" it currently generates. Pressing all characters keys on a USA keyboard should give the following result(with spaces between them and enter after each row of keys): ` 1 2 3 4 5 6 7 8 9 0 - = q w e r t y u i o p [ ] \ a s d f g h j k l ; ' z x c v b n m , . / 4. While using "Portuguese (Brazil, nativo for USA keyboards)" layout it gives = 1 2 3 4 5 6 7 8 9 0 [ ] / , . h x w l t c p ~ - ' i e a o u m d s r n ' y ; j b k q v g f z If you look at the keyboard layout chart, you'll see it has nothing to do with USA keyboards and specially nothing like to what is sold here in Brazil. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1449250/+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 1264311] Re: BCM43142 bluetooth adapter not finding any bluetooth devices
Installing the package Claus Allweil posted plus copying the hcd file to fw-105b_e065.hcd worked for me too. I tried to find a canonical package for that and failed. I think something was missing from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1161261. From https://bugzilla.kernel.org/show_bug.cgi?id=73411 it seems that the issue is distributing firmware without a license, which makes complete sense. ** Bug watch added: Linux Kernel Bug Tracker #73411 http://bugzilla.kernel.org/show_bug.cgi?id=73411 -- 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/1264311 Title: BCM43142 bluetooth adapter not finding any bluetooth devices Status in “bluez” package in Ubuntu: Confirmed Bug description: On my officially Ubuntu-certified Lenovo B590 laptop the BCM43142 bluetooth adapter is not working. I have two further bluetooth devices placed closely to the laptop, non-paired and each being able to discover the other respectively. None of them is able to discover the laptop, nor does 'hcitool scan' on the laptop find any devices. It does not give any errors though. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Dec 26 15:34:08 2013 InstallationDate: Installed on 2013-12-25 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 37613EG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=UUID=c379c17a-9869-47a8-b9b3-83be4e302040 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET74WW(1.11) dmi.board.asset.tag: Not Available dmi.board.name: 37613EG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn37613EG:pvrLenovoB590:rvnLENOVO:rn37613EG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37613EG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 1C:3E:84:E8:81:98 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1244 acl:0 sco:0 events:81 errors:0 TX bytes:2820 acl:0 sco:0 commands:77 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311/+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 1377624] Re: udev requires hotplug support, thus upgrades fail
Ugly Temporary fix: After getting this error: nano /etc/init.d/udev After the ### END INIT INFO add: exit 0 Save and exit. apt-get -f install Edit the file again, and remove the exit 0, save & exit Works for me -- 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/1377624 Title: udev requires hotplug support, thus upgrades fail Status in “systemd” package in Ubuntu: Confirmed Status in “systemd” source package in Trusty: Confirmed Bug description: I'm running 14.04 LTS in an OpenVZ container. Upgrades failed today, due to failure to configure udev: $ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up udev (204-5ubuntu20.7) ... * udev requires hotplug support, not started ...fail! invoke-rc.d: initscript udev, action "restart" failed. dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of systemd-services: systemd-services depends on udev (>= 175-0ubuntu23); however: Package udev is not configured yet. dpkg: error processing package systemd-services (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libpam-systemd:amd64: libpam-systemd:amd64 depends on systemd-services (= 204-5ubuntu20.7); however: Package systemd-services is not configured yet. dpkg: error processing package libpam-systemd:amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: udev systemd-services libpam-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1377624/+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 1616028] [NEW] does not detect bluetooth mouse Thinkpad X1
Public bug reported: does not list the device. some help to debug. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1616028 Title: does not detect bluetooth mouse Thinkpad X1 Status in bluez package in Ubuntu: New Bug description: does not list the device. some help to debug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1616028/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
** Also affects: freetype (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: freetype (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: openjdk-lts (Ubuntu) Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: Confirmed Status in freetype source package in Bionic: New Status in openjdk-lts source package in Bionic: New Status in freetype source package in Cosmic: New Status in openjdk-lts source package in Cosmic: New Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jtreg (Ubuntu) Importance: Undecided Status: New ** Also affects: libcommons-lang3-java (Ubuntu) Importance: Undecided Status: New ** Also affects: testng (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: clojure1.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: dd-plist (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-compiler-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: plexus-languages (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj (Ubuntu) Importance: Undecided Status: New ** Also affects: surefire (Ubuntu) Importance: Undecided Status: New ** Also affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Also affects: groovy (Ubuntu) Importance: Undecided Status: New ** Also affects: jaxws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: jws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: metro-policy (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj-ri (Ubuntu) Importance: Undecided Status: New ** Also affects: junit4 (Ubuntu) Importance: Undecided Status: New ** Also affects: gettext (Ubuntu) Importance: Undecided Status: New ** Also affects: scala (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: - update to openjdk 11 in 18.04 LTS + Transition OpenJDK 11 to 18.04 LTS. + + This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: + - openjdk-lts 11 needs newer build dependencies + - various packages have runtime failures when run with openjdk-11 + + A few packages *must* be updated/patched before openjdk-11 itself is uploaded: + TBD -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - openjdk-lts 11 needs newer build dependencies - various packages have runtime failures when run with openjdk-11 A few packages *must* be updated/patched before openjdk-11 itself is uploaded: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. - This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - - openjdk-lts 11 needs newer build dependencies - - various packages have runtime failures when run with openjdk-11 + This transition is a security update of openjdk-lts from openjdk-10 to + openjdk-11. This introduces runtime and FTBFS issues which requires + backports of multiple packages into the security pocket as well. - A few packages *must* be updated/patched before openjdk-11 itself is uploaded: - TBD + The packages are being build on PPAs under the + https://launchpad.net/~openjdk-11-transition team. The PPAs depend + solely on the security pocket and are separated in stages. + + The agreed process among foundations and the security team is that + packages in the PPAs will be binary copied into bionic-proposed, checked + for migration issues, and - no issues pending - copied into bionic- + security. + + A few packages might also need to be updated in Cosmic, but as an + exception that will be done after the Bionic transition is worked out. + + + [2018-02-21] + Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. + + Notes: + - jtreg and testng are new versions required as build dependencies of openjdk-11 + - all other packages are backports that must be build/bootstrapped with openjdk-10 + + PPAs: + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 + + + Please copy them in the following order/grouping. + + Group 1: + * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 2: + * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) + * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) + + Please upload libcommons-lang3-java from stage 2 (ignore the version in + stage 1). + + Group 3: + * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) + * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 4: + * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 5: + * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + + Packages from stage 3 and later are not yet reviewed and should not be uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. A few packages
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic- security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. - [2018-02-21] + [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) - Packages from stage 3 and later are not yet reviewed and should not be + + [2019-02-22] + Packages in stage 3 that are waiting for security team review. Copy only after OK is received. + + PPAs: + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 + + Please copy them in the following order/grouping. + Group 1: + * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) + * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07) + + Group 2: + * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago) + * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20) + * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19) + * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19) + * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20) + + Packages from stage 4 and later are not yet reviewed and should not be uploaded. ** Also affects: java-common (Ubuntu) Importance: Undecided Status: New ** Also affects: javatools (Ubuntu) Importance: Undecided Status: New ** Also affects: insubstantial (Ubuntu) Importance: Undecided Status: New ** No longer affects: saaj-ri (Ubuntu) ** Also affects: libgpars-groovy-java (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in metro-policy package in Ubuntu
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: logback (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-javadoc-plugin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3 that are waiting for security team review. Copy only after OK is received. PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 Please copy them in the following order/grouping. Group 1: * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: libhibernate-validator-java (Ubuntu) Importance: Undecided Status: New ** Also affects: jasperreports (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-bundle-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-enforcer (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-jaxb2-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-plugin-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer
Re: [Touch-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
> Just a question, is this update going to affect these packages: > jabref > scilab > octave > pdfsam > ? > > Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding > OpenJdk-11 and its dependant packages to facilitate the maintenance > burden. Yes, we are planning to update java apps that are affected by this transition. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)
Re: [Touch-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
> > Just a question, is this update going to affect these packages: > > jabref > > scilab > > octave > > pdfsam > > ? > > > > Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding > > OpenJdk-11 and its dependant packages to facilitate the maintenance > > burden. > > Yes, we are planning to update java apps that are affected by this transition. To be more specific, any package that fails to run correctly with openjdk-11 will be investigated and is a candidate for a update. The update does not necessarily imply we will use the latest version: we might simply apply or backport changes that allow them to work under openjdk-11. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle
[Touch-packages] [Bug 1814133]
affects Ubuntu/jabref affects Ubuntu/scilab affects Ubuntu/scilab affects Ubuntu/pdfsam -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in pdfsam package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in scilab package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jabref (Ubuntu) Importance: Undecided Status: New ** Also affects: octave (Ubuntu) Importance: Undecided Status: New ** Also affects: pdfsam (Ubuntu) Importance: Undecided Status: New ** Also affects: scilab (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in pdfsam package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in scilab package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer
[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
** Tags added: bionic xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: update-initramfs hangs on upgrade, dpkg unusable, unbootable system Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic ^CFailed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-63-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-4.4.0-63-generic: linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic (= 4.4.0-63.84); however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-generic: linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; however: Package linux-signed-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-63-generic: linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-extra-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 4.4.0.6
[Touch-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu) Importance: Undecided => Medium ** Changed in: dkms (Ubuntu) Status: New => Confirmed ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu Xenial) Status: New => Invalid ** Changed in: dkms (Ubuntu Bionic) Status: New => Invalid ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] - As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. + As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. - This assumes a new Xenial schroot. + This assumes a new Xenial/Bionic schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools + * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 + * bionic: + TBD 3) install the headers for the old kernels (forces dkms to run) + * xenial: sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic + * bionic: + TBD 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: TBD 3) install the headers for the old kernels (f
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
** Summary changed: - remove /boot/initrd.img-*.old-dkms files left behind + [SRU] remove orphaned initrd old-dkms files in /boot ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. - bug 1515513 dealt with removing initrd.img-.old-dkms files - using the kernel's prerm hook, but that is only executed for the kernel - version being removed: any other old-dkms file generated prior to that - would not be removed by the hook, taking space in the /boot directory. + bug 1515513 dealt with removing old-dkms initrd files using the kernel's + prerm hook, but that is only executed for the kernel version being + removed: any other old-dkms file generated prior to that would not be + removed by the hook, taking space in the /boot directory and being + carried forward with every upgrade. - Note: Filling up the /boot partition causes updates to fail. + Note: Filling up the /boot partition causes updates and upgrades to + fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. - This assumes a new Xenial/Bionic schroot. + This assumes a new Xenial/Bionic/Cosmic schroot. - 1) create a file to work as a placeholder for the initrd.img old dkms file - sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms + 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) + sudo touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: + TBD + * cosmic: TBD 3) install the headers for the old kernels (forces dkms to run) * xenial: sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: TBD + * cosmic: + TBD - 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel + 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools - 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel + 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ** Patch removed: "initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187601/+files/initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to t
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
attaching xenial sru patch ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. - This assumes a new Xenial/Bionic/Cosmic schroot. + This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) - sudo touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms + touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: - sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 + apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: - TBD - * cosmic: - TBD + apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: - sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic + apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: - TBD - * cosmic: - TBD + apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel - ls /boot/*.old-dkms + ls -1 /boot/*.old-dkms - 5) install the initramfs-tools that contains this fix - sudo apt-get install -y initramfs-tools + 5) install the initramfs-tools from proposed that contains this fix + apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms - 7) autoremove the older kernel - sudo apt-get autoremove -y + 7) mark kernel images and headers as automatically installed + apt-mark auto linux-image-4*-generic linux-headers-4*-generic - 8) verify that there are now only 2 old-dkms, one for each installed kernel - ls /boot/*.old-dkms + 8) autoremove the older kernel + apt-get autoremove -y + + 9) verify that there are now only 2 old-dkms, one for each installed kernel + ls -1 /boot/*.old-dkms + + + These steps guarantees that: + - orphaned old-dkms are correctly removed from /boot + - non-orphaned old-dkms are kept + - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ** Patch added: "initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187982/+files/initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invali
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
attaching bionic sru patch ** Patch added: "initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187983/+files/initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
attaching cosmic patch ** Patch added: "initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187984/+files/initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
** Description changed: - At least four users, including myself, are having an issue with update- - initramfs hanging while updating ubuntu 16.04. The bug has been - documented while attempting an update to multiple kernel versions ( - 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or - install to fail, and may also lead to an unbootable system. + [Impact] + If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. + + [Test Case] + One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. + + 1. Setup a nfs server and export a directory with write permissions for + the client + + 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) + $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress + Note: adjust the "count" accordingly to how fast/slow your system is. + + 3. Call sync and verify that it only finished after "dd" is done. + + 4. Repeat step #2 and now call "sync -f /boot/". + Verify that it finished immediatly. + + [Regression Potential] + Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. + + [Other] + If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). + + The 'sync' and 'syncfs' specifications are pretty much similar and + syncfs is expected to work the same as a normal sync regarding data + integrity. Also altought the patch introduces the initrd file as an + extra argument which would cause 'sync -f' to fail if the file does not + exist, the update-initramfs script would fail earlier than that because + that file is created by the 'mv' call a few lines above. Thus no + regressions are expected. + + [References] + [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 + [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html + + [Original bug report] + At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade - Fetched 1,571 MB in 2min 9s (12.2 MB/s) + Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic - (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. + (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic - (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
[Touch-packages] [Bug 1667512] Re: [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system
** Summary changed: - update-initramfs hangs on upgrade, dpkg unusable, unbootable system + [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system ** Summary changed: - [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system + [SRU] update-initramfs should sync only the filesystem containing the initramfs image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.post
[Touch-packages] [Bug 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
SRU as a merge proposal for both this and bug 1791959 available at Bionic: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 Xenial: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic (/boot/vmlinuz-4.4.0-6
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
SRU as a merge proposal for both this and bug 1667512 available at Bionic: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 Xenial: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 ** No longer affects: dkms (Ubuntu) ** No longer affects: dkms (Ubuntu Xenial) ** No longer affects: dkms (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
** Merge proposal unlinked: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355188 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1792189] Re: linux-firmware does not depend on initramfs-tools
** Changed in: initramfs-tools (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1792189 Title: linux-firmware does not depend on initramfs-tools Status in initramfs-tools package in Ubuntu: Confirmed Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
Verification done on Xenial by following the test case. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
Verification failed on Bionic when following the test case, the postinst script has a bad check for the previous version of initramfs-tools it expected - it is testing against a version from Xenial, not the Bionic version. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
Verification done in Xenial and Bionic as per the test case. It works fine and will prevent update-initramfs from being stuck in the described scenarios. ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
I have prepared a new merge proposal that includes the right version check in the postinst for Bionic. This has been uploaded to the Bionic queue as 0.130ubuntu3.5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
Verified that initramfs-tools 0.130ubuntu3.5 in bionic-proposed now works as expected after following through the testcase. As expected orphaned old-dkms files are properly removed and no other files are affected. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
Did the testcase verification again for the new 0.130ubuntu3.5 bionic- proposed upload and I confirm again that it works as expected. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
> 7) Execute "gdb --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core' --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug'" Try setting the debug-file-directory first, it should work. gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug' --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core' Still, this does not seem to invalidate the original bug report or the one in comment #4, as they are setting 'file' and 'core' last. It is just that comment #12 does not seem to indicate a valid reproducer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink Status in Apport: Fix Released Status in apport package in Ubuntu: New Status in gdb package in Ubuntu: Confirmed Bug description: As far as I can tell gdb version 8.2.90 isn't searching the debug- file-directory, which I set, for the '.gnu_debugaltlink' which is in the debug symbols. Here's the error I'm seeing: Type "apropos word" to search for commands related to "word". Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox//usr/bin/gnome-calculator... Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug... could not find '.gnu_debugaltlink' file for /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug) Here's part of an strace of what's going on behind the scenes: lstat("/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug", {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 openat(AT_FDCWD, "/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) This is the only time "/usr/lib/debug" is searched, generally "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox/usr/lib/debug/" is used. I'll attach the full strace though. For completeness here's the gdb command I'm using: Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute- prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64 -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox- dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox//usr/bin/gnome-calculator"' --ex 'core-file /tmp/apport_core_1b6dn6np' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
I tried the testcase from comment #12 in Focal and Hirsute and it worked just fine: $ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug' --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core' Type "apropos word" to search for commands related to "word". Reading symbols from /bin/cat... Reading symbols from /tmp/dbgsym/usr/lib/debug/.build-id/b3/57ed53c8c9cb1a312f83b28982304effae0135.debug... [New LWP 2094475] Core was generated by `/bin/cat'. Program terminated with signal SIGTSTP, Stopped (user). #0 0x77eb6142 in __GI___libc_read (fd=fd@entry=0, buf=buf@entry=0x77faa000, nbytes=nbytes@entry=131072) at ../sysdeps/unix/sysv/linux/read.c:26 # hirsute $ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug' --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core' Reading symbols from /bin/cat... Reading symbols from /tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug... [New LWP 14651] Core was generated by `/usr/bin/cat'. Program terminated with signal SIGTSTP, Stopped (user). #0 0x77edccb2 in __GI___libc_read (fd=fd@entry=0, buf=buf@entry=0x7791e000, nbytes=nbytes@entry=131072) at ../sysdeps/unix/sysv/linux/read.c:26 26 ../sysdeps/unix/sysv/linux/read.c: No such file or directory. If the dbgsym is installed and I use (with intentional typo): set debug-file-directory /tmp/dbgsym/usr/lib/debugnot:/usr/lib/debug it then loads symbols correctly from /usr/lib/debug Note, this was tested under Focal (host) and Hirsute (lxd container). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink Status in Apport: Fix Released Status in apport package in Ubuntu: New Status in gdb package in Ubuntu: Confirmed Bug description: As far as I can tell gdb version 8.2.90 isn't searching the debug- file-directory, which I set, for the '.gnu_debugaltlink' which is in the debug symbols. Here's the error I'm seeing: Type "apropos word" to search for commands related to "word". Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox//usr/bin/gnome-calculator... Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug... could not find '.gnu_debugaltlink' file for /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug) Here's part of an strace of what's going on behind the scenes: lstat("/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug", {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 openat(AT_FDCWD, "/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) This is the only time "/usr/lib/debug" is searched, generally "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox/usr/lib/debug/" is used. I'll attach the full strace though. For completeness here's the gdb command I'm using: Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute- prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64 -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox- dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox//usr/bin/gnome-calculator"' --ex 'core-file /tmp/apport_core_1b6dn6np' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
I was able to reproduce what Brian is reporting here. If the -dbgsym for the package is installed, gdb works and reports that it is reading from the /tmp/dbgsym path. When -dbgsym package is not installed then it fails with the 'could not find '.gnu_debugaltlink' file for ...' message -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink Status in Apport: Fix Released Status in apport package in Ubuntu: New Status in gdb package in Ubuntu: Confirmed Bug description: As far as I can tell gdb version 8.2.90 isn't searching the debug- file-directory, which I set, for the '.gnu_debugaltlink' which is in the debug symbols. Here's the error I'm seeing: Type "apropos word" to search for commands related to "word". Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox//usr/bin/gnome-calculator... Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug... could not find '.gnu_debugaltlink' file for /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug) Here's part of an strace of what's going on behind the scenes: lstat("/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug", {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 openat(AT_FDCWD, "/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) This is the only time "/usr/lib/debug" is searched, generally "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox/usr/lib/debug/" is used. I'll attach the full strace though. For completeness here's the gdb command I'm using: Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute- prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64 -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox- dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox//usr/bin/gnome-calculator"' --ex 'core-file /tmp/apport_core_1b6dn6np' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
So the issue is: if there is a .gnu_debugaltlink GDB will try to load that file and throw an error if it can't. That path is absolute and GDB does _not_ look for that path/file anywhere else, not even inside 'debug-file-directory'. GDB seems to only look at section .gnu_debugaltlink in debug/.build- id/nn/nn.debug, it does not seem to use that section from the binary at all. Due to that, another workaround is to modify that section to point to the 'right' place: 1) use objcopy to dump .gnu_debugaltlink from debug/.build-id/nn/nn.debug into a file 2) use sed to modify the path in the dump file 3) use objcopy to update .gnu_debugaltlink section in debug/.build-id/nn/nn.debug As in: $ objcopy --dump-section .gnu_debugaltlink=altlink /tmp/dbgsym/usr/lib/debug/.build-id/76/e9f820204912084fd156c593b2c92f1a4b51f1.debug $ sed -i 's:^:/tmp/dbgsym:' altlink $ objcopy --update-section .gnu_debugaltlink=altlink /tmp/dbgsym/usr/lib/debug/.build-id/76/e9f820204912084fd156c593b2c92f1a4b51f1.debug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink Status in Apport: Fix Released Status in apport package in Ubuntu: New Status in gdb package in Ubuntu: Confirmed Bug description: As far as I can tell gdb version 8.2.90 isn't searching the debug- file-directory, which I set, for the '.gnu_debugaltlink' which is in the debug symbols. Here's the error I'm seeing: Type "apropos word" to search for commands related to "word". Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox//usr/bin/gnome-calculator... Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug... could not find '.gnu_debugaltlink' file for /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug) Here's part of an strace of what's going on behind the scenes: lstat("/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug", {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 openat(AT_FDCWD, "/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) This is the only time "/usr/lib/debug" is searched, generally "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox/usr/lib/debug/" is used. I'll attach the full strace though. For completeness here's the gdb command I'm using: Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute- prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64 -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox- dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox//usr/bin/gnome-calculator"' --ex 'core-file /tmp/apport_core_1b6dn6np' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
@sergiodj many thanks for the help here It was a dwz man page somewhere that made me think we might be misusing .gnu_debugaltlink somehow (didn't even know about dh_dwz), but on a quick search I couldn't understand how the path was supposed to look like so I could test that idea with my replace-altlink-section-hack. And if GDB can support looking for .dwz on the debug-file-drectory even with hardcoded paths, all the better. Many, many thanks for taking the time to look at this and come up with these 2 solutions. We really appreciate it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink Status in Apport: Fix Released Status in apport package in Ubuntu: New Status in gdb package in Ubuntu: Confirmed Bug description: As far as I can tell gdb version 8.2.90 isn't searching the debug- file-directory, which I set, for the '.gnu_debugaltlink' which is in the debug symbols. Here's the error I'm seeing: Type "apropos word" to search for commands related to "word". Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox//usr/bin/gnome-calculator... Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug... could not find '.gnu_debugaltlink' file for /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug) Here's part of an strace of what's going on behind the scenes: lstat("/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug", {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 openat(AT_FDCWD, "/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) This is the only time "/usr/lib/debug" is searched, generally "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox/usr/lib/debug/" is used. I'll attach the full strace though. For completeness here's the gdb command I'm using: Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute- prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64 -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox- dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox//usr/bin/gnome-calculator"' --ex 'core-file /tmp/apport_core_1b6dn6np' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+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 1870088] Re: xz-utils ftbfs in focal
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Confirmed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1870088] Re: xz-utils ftbfs in focal
Installed xz-utils 5.2.4-1ubuntu1 on Focal from focal-proposed, works fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Confirmed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1870088] Re: xz-utils ftbfs in focal
** Changed in: xz-utils (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Fix Committed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1870088] Re: xz-utils ftbfs in focal
** Tags removed: block-proposed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Fix Committed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
** Branch linked: lp:~tdaitx/ubuntu/groovy/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775219 Title: incorrectly reports package as unsupported if apt cache is empty Status in apport package in Ubuntu: Confirmed Bug description: Cloud images ship with empty /var/lib/apt/lists/ to save on size. Running 'ubuntu-bug ' will erroneously report that the package is unsupported: $ ubuntu-bug coreutils *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Problem in coreutils The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. A simpler recreate is: $ python3 -c 'import apport;print(apport.packaging.is_distro_package("coreutils"))' False $ sudo apt update -qq All packages are up to date. $ python3 -c 'import apport;print(apport.packaging.is_distro_package("coreutils"))' True Desired result: The message should instruct the user to run 'apt update' as root if they think this is in error. That would improve usability and avoid false reports about apport incorrectly flagging a package as unsupported. Additionally, if the user is root (and optionally if the set of package candidates only contains a 'now' component) self._cache.update(); self._cache.open() could be called to download lists. Alternatively it could just check to see if lists have been downloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+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 1679865] Re: coreutils FTBFS during zesty test rebuild
This is caused by a change in the new TZ as reported at [1]. A fix is provided in [2] but required a small change for the first chunk to apply cleanly - see attached debdiff. Other option is to sync the newest version, 8.28-1 [3,4], which includes the fix upstream and builds cleanly. [1] http://lists.gnu.org/archive/html/coreutils/2017-03/msg00026.html [2] http://lists.gnu.org/archive/html/coreutils/2017-03/msg00031.html [3] http://snapshot.debian.org/package/coreutils/8.28-1/ [4] https://tracker.debian.org/pkg/coreutils ** Patch added: "coreutils_8.26-3ubuntu3_8.26-3ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1679865/+attachment/4963059/+files/coreutils_8.26-3ubuntu3_8.26-3ubuntu3.debdiff ** Changed in: coreutils (Ubuntu) Assignee: Matthias Klose (doko) => (unassigned) ** Changed in: coreutils (Ubuntu) Status: New => Confirmed ** Tags added: patch ** Tags added: artful ** Summary changed: - coreutils FTBFS during zesty test rebuild + coreutils FTBFS during zesty/artful test rebuild -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1679865 Title: coreutils FTBFS during zesty/artful test rebuild Status in coreutils package in Ubuntu: Confirmed Bug description: coreutils version 8.26-3ubuntu3 in zesty failed to build on all arches during a test rebuild of the archive. The build log can be found here: https://launchpadlibrarian.net/312365438/buildlog_ubuntu-zesty- amd64.coreutils_8.26-3ubuntu3_BUILDING.txt.gz The failure seems to be: FAIL: tests/misc/date-debug === --- exp3 2017-03-25 05:27:00.477874098 + +++ out3 2017-03-25 05:27:00.481874118 + @@ -4,4 +4,4 @@ date: final: 1.0 (epoch-seconds) date: final: (Y-M-D) 1970-01-01 00:00:01 (UTC0) date: final: (Y-M-D) 1969-12-31 19:00:01 (output timezone TZ=-05:00) -Wed Dec 31 19:00:01 PET 1969 +Wed Dec 31 19:00:01 -05 1969 FAIL tests/misc/date-debug.sh (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1679865/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
This is the proposed openjdk-8 hook. ** Description changed: - This is for Tiago's openjdk apport package hook. + OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to + a Crash report under the HotspotError key. The hook is currently limited + to attaching files under 100 KB. + + Please add HotspotError key to the whitelist in order for it to be + available in error tracker. ** Attachment added: "source-openjdk-8.py" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892544/+files/source-openjdk-8.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: New Bug description: OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
** Attachment removed: "source-openjdk-8.py" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892544/+files/source-openjdk-8.py ** Attachment added: "source-openjdk-8.py" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892554/+files/source-openjdk-8.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: New Bug description: OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1647638] Re: W: APT had planned for dpkg to do more than it reported back
I could replicate it on my system, I got the following message on the tests: W: APT had planned for dpkg to do more than it reported back (0 vs 4). Affected packages: linux-image-4.10.0-22-generic:amd64 == Reproducer == $ sudo tee /etc/kernel/postinst.d/zz-fail
[Touch-packages] [Bug 1647638] Re: W: APT had planned for dpkg to do more than it reported back
Small correction to get the right zz-fail file (needs to escape $), please run: $ sudo tee /etc/kernel/postinst.d/zz-fail
[Touch-packages] [Bug 1655022] Re: Image preview no longer works
** Branch linked: lp:~phablet-team/messaging-app/fix-attachments-preview -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1655022 Title: Image preview no longer works Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Confirmed Bug description: rc-proposed Tap on an image attachment and nothing happens. Works fine on OTA 14. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1655022/+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 1711449] [NEW] [FTBFS] lxc build fails due to gcc-7
Public bug reported: Currently lxc FTBFS due to a GCC-7 bug. There's a upstream report for gcc-7 [1], but meanwhile lxc upstream has applied a workaround that fixes the build [1]. cgroups/cgfsng.c: In function ‘cgfsng_create’: cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be truncated before the last format character [-Werror=format-truncation=] snprintf(offset, 5, "-%d", idx); ^ In file included from /usr/include/stdio.h:938:0, from cgroups/cgfsng.c:44: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of size 5 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, ^~~~ __bos (__s), __fmt, __va_arg_pack ()); ~ cc1: all warnings being treated as errors [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #853531 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853531 ** Also affects: lxc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853531 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1711449 Title: [FTBFS] lxc build fails due to gcc-7 Status in lxc package in Ubuntu: New Status in lxc package in Debian: Unknown Bug description: Currently lxc FTBFS due to a GCC-7 bug. There's a upstream report for gcc-7 [1], but meanwhile lxc upstream has applied a workaround that fixes the build [1]. cgroups/cgfsng.c: In function ‘cgfsng_create’: cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be truncated before the last format character [-Werror=format-truncation=] snprintf(offset, 5, "-%d", idx); ^ In file included from /usr/include/stdio.h:938:0, from cgroups/cgfsng.c:44: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of size 5 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, ^~~~ __bos (__s), __fmt, __va_arg_pack ()); ~ cc1: all warnings being treated as errors [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1711449/+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 1711449] Re: [FTBFS] lxc build fails due to gcc-7
** Patch added: "lxc_2.0.8-0ubuntu4_2.0.8-0ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1711449/+attachment/4934433/+files/lxc_2.0.8-0ubuntu4_2.0.8-0ubuntu5.debdiff ** Tags added: artful ftbfs patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1711449 Title: [FTBFS] lxc build fails due to gcc-7 Status in lxc package in Ubuntu: New Status in lxc package in Debian: Unknown Bug description: Currently lxc FTBFS due to a GCC-7 bug. There's a upstream report for gcc-7 [1], but meanwhile lxc upstream has applied a workaround that fixes the build [1]. cgroups/cgfsng.c: In function ‘cgfsng_create’: cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be truncated before the last format character [-Werror=format-truncation=] snprintf(offset, 5, "-%d", idx); ^ In file included from /usr/include/stdio.h:938:0, from cgroups/cgfsng.c:44: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of size 5 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, ^~~~ __bos (__s), __fmt, __va_arg_pack ()); ~ cc1: all warnings being treated as errors [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1711449/+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 1662868] [NEW] Changes to organizationName management break qt-labs-settings
Public bug reported: Recent changes to the way ubuntu-ui-toolkit handles the organizationName break the qml Settings component. It cannot access the right configuration files as organizationName is used to build the configuration file paths. I added more details to this comment on the MR that introduced the regression: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/organizedWindow/+merge/314631/comments/820497 ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Assignee: Christian Dywan (kalikiana) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1662868 Title: Changes to organizationName management break qt-labs-settings Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Recent changes to the way ubuntu-ui-toolkit handles the organizationName break the qml Settings component. It cannot access the right configuration files as organizationName is used to build the configuration file paths. I added more details to this comment on the MR that introduced the regression: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/organizedWindow/+merge/314631/comments/820497 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1662868/+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 1637239] Re: Please merge ncurses 6.0+20160917-1 (main) from Debian unstable (main)
Patch to merge latest debian version (6.0+20161126-1) into to Ubuntu (last merge was 6.0+20160625-1ubuntu1). Remaining changes: - Add a simple autopkgtest to the package. - Build x32 packages. - Build lib32 packages on s390x. The changes have been forwarded to Debian: - http://bugs.debian.org/857000 (autopkgtest) - http://bugs.debian.org/857001 (lib32 packages on s390x) - http://bugs.debian.org/857003 (x32 packages) Thanks to Steve Langasek for the info bellow: The x32 multilib packages (libx32ncurses5) makes as much sense to include in the package as lib32ncurses5 and lib64ncurses5 which are being shipped, and for the same rationale. It's also relevant that there is no official x32 port in either Debian or Ubuntu from which to install the multiarch binaries. Still it might be controversial on Debian because https://bugs.debian.org/848163 requests the removal of the multilib binaries for other arche; has also not been acted on but might be after Debian stretch is released. For now we will be keeping the x32 multilib as it is and going forward with the merge. ** Bug watch added: Debian Bug tracker #857000 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857000 ** Bug watch added: Debian Bug tracker #857001 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857001 ** Bug watch added: Debian Bug tracker #857003 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857003 ** Bug watch added: Debian Bug tracker #848163 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848163 ** Patch added: "ncurses_6.0+20161126-1_ncurses_6.0+20161126-1ubuntu1.diff" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1637239/+attachment/4833150/+files/ncurses_6.0+20161126-1_ncurses_6.0+20161126-1ubuntu1.diff ** Changed in: ncurses (Ubuntu) Assignee: Tiago Stürmer Daitx (tdaitx) => (unassigned) ** Changed in: ncurses (Ubuntu) Status: In Progress => Confirmed ** Description changed: Ubuntu version: 6.0+20160625-1ubuntu1 - Debian verison: 6.0+20160917-1 + Debian verison: 6.0+20161126-1 Details: https://merges.ubuntu.com/n/ncurses/REPORT ** Summary changed: - Please merge ncurses 6.0+20160917-1 (main) from Debian unstable (main) + Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1637239 Title: Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: Confirmed Bug description: Ubuntu version: 6.0+20160625-1ubuntu1 Debian verison: 6.0+20161126-1 Details: https://merges.ubuntu.com/n/ncurses/REPORT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1637239/+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 1640320] Re: FTBFS in zesty
I believe that the failed builds were re-run since the first report by Dimitri and then failed due to googletest. After fixing the googletest issues then we end up with another FTBFS caused by missing 'vector' includes. I have added a merge proposal with the fixes in place. ** Branch linked: lp:~tdaitx/location-service/lp-1640320-ftbfs-fix ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty Status in location-service package in Ubuntu: Confirmed Bug description: FTBFS in zesty during a no change rebuild against new boost Please see build logs at: https://launchpad.net/ubuntu/+source /location-service/3.0.0+16.10.20160912-0ubuntu2 Please help fix this [ 10%] Building CXX object src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o cd /<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location && /usr/bin/g++ -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS -Dubuntu_location_service_connectivity_EXPORTS -I/<>/location-service-3.0.0+16.10.20160912/3rd-party -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/json-c -I/<>/location-service-3.0.0+16.10.20160912/include/location_service -I/<>/location-service-3.0.0+16.10.20160912/src/location_service -I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service -I/usr/include/ubuntu -g -O2 -fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra -fPIC -Wno-error=unused-local-typedefs -fPIC -o CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o -c /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp In file included from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0, from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19: /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14: error: ‘vector’ in namespace ‘std’ does not name a template type std::vector xtra_hosts ^~ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10: warning: extra ‘;’ [-Wpedantic] }; ^ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18: error: ‘vector’ in namespace ‘std’ does not name a template type virtual std::vector download_xtra_data(const Configuration& config) = 0; ^~ make -f po/CMakeFiles/pofiles_70.dir/build.make po/CMakeFiles/pofiles_70.dir/depend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+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 1704174] [NEW] update apparmor rules to include wicd's dhclient.conf file
Public bug reported: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "sbin.dhclient-wicd.patch" https://bugs.launchpad.net/bugs/1704174/+attachment/4914177/+files/sbin.dhclient-wicd.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1704174 Title: update apparmor rules to include wicd's dhclient.conf file Status in isc-dhcp package in Ubuntu: New Bug description: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1704174/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
** Description changed: - OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to - a Crash report under the HotspotError key. The hook is currently limited - to attaching files under 100 KB. + [Impact] + By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. + + OpenJDK 8 now includes a new apport hook to collect additional data from + crash reports as well as the hs_err log file (in the new HotspotError + key). + + A new release is soon reaching Zesty and Xenial with the hook included + and without SRU'ing this fix the hs_err file won't be uploaded to the + error tracker. + + [Test Case] + 1. Start any java program using OpenJDK 8 + 2. Kill it with SIGILL + 3. Check that the created report contains the hs_err file + + [Regression Potential] + If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. + + [Original bug report] + OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Triaged Status in whoopsie source package in Zesty: Triaged Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] 1. Start any java program using OpenJDK 8 2. Kill it with SIGILL 3. Check that the created report contains the hs_err file [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1705320] Re: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix
** Patch added: "whoopsie_0.2.52.3_0.2.52.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+attachment/4917748/+files/whoopsie_0.2.52.3_0.2.52.4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1705320 Title: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix Status in whoopsie package in Ubuntu: New Bug description: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+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 1705320] [NEW] [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix
Public bug reported: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1705320 Title: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix Status in whoopsie package in Ubuntu: New Bug description: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+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 1705320] Re: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix
** Patch added: "whoopsie_0.2.55_0.2.55.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+attachment/4917749/+files/whoopsie_0.2.55_0.2.55.1.debdiff ** Description changed: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. - The first fix is #1696814 and was added to whoopsie 0.2.56/artful. It - adds the new HotspotError key into the acceptable_fields so that the new - apport hook from OpenJDK 8 can upload the hs_err file generated by - OpenJDK crashes. The file is limited to 100 KB by the hook. + The first fix is tracked by bug #1696814 and was added to whoopsie + 0.2.56/artful. It adds the new HotspotError key into the + acceptable_fields so that the new apport hook from OpenJDK 8 can upload + the hs_err file generated by OpenJDK crashes. The file is limited to 100 + KB by the hook. - The second fix is #1697375 and was added to whoopsie 0.2.57/artful. It - fixes whoopsie queries for NetworkManager state. + The second fix is tracked by bug #1697375 and was added to whoopsie + 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. - The impact, testcase and regression potential are discussed directly on + The impact, testcase and regression potential are discussed directly in the bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1705320 Title: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix Status in whoopsie package in Ubuntu: New Bug description: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
** Description changed: - [Impact] + [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] - 1. Start any java program using OpenJDK 8 - 2. Kill it with SIGILL - 3. Check that the created report contains the hs_err file + Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). - [Regression Potential] + # SleepTest.java + public class SleepTest { + public static void main(String[] args) throws Exception { + Thread.sleep(5000); + } + } + + 1. Run whoopsie: + $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f + + 2. Run the SleepTest and SIGKILL it in another terminal: + $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" + + 3. View the crash report and submit it: + $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash + 3a) View the report + 3b) [Optional] Search for the "HotspotError" key + 3c) Send the report + + 4. Verify that the report was saved, including the hs_err content: + 4a) In whoopsie terminal, check the OOPS ID code + 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID + 4c) Confirm that the HotspotError was added to the report + + [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). # SleepTest.java public class SleepTest { public static void main(String[] args) throws Exception { Thread.sleep(5000); } } 1. Run whoopsie: $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 2. Run the SleepTest and SIGKILL it in another terminal: $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" 3. View the crash report and submit it: $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash 3a) View the report 3b) [Optional] Search for the "HotspotError" key 3c) Send the report 4. Verify that the report was saved, including the hs_err content: 4a) In whoopsie terminal, ch
[Touch-packages] [Bug 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Results from tests on Xenial: - current whoopsie 0.2.52.3: no HotspotError (as expected) https://errors.staging.ubuntu.com/oops/5e77a89e-6e4a-11e7-8a18-fa163eaf9b83 - proposed whoopsie 0.2.52.4: HotspotError is present (as expected) https://errors.staging.ubuntu.com/oops/cfa0113c-6e4a-11e7-8a18-fa163eaf9b83 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). # SleepTest.java public class SleepTest { public static void main(String[] args) throws Exception { Thread.sleep(5000); } } 1. Run whoopsie: $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 2. Run the SleepTest and SIGKILL it in another terminal: $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" 3. View the crash report and submit it: $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash 3a) View the report 3b) [Optional] Search for the "HotspotError" key 3c) Send the report 4. Verify that the report was saved, including the hs_err content: 4a) In whoopsie terminal, check the OOPS ID code 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID 4c) Confirm that the HotspotError was added to the report [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Results from the testcase in Zesty: - current whoopsie 0.2.55: no HotspotError (as expected) https://errors.staging.ubuntu.com/oops/90d56bae-6e50-11e7-8a18-fa163eaf9b83 - proposed whoopsie 0.2.55.1: HotspotError is present (as expected) https://errors.staging.ubuntu.com/oops/3e464710-6e4f-11e7-8a18-fa163eaf9b83 ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). # SleepTest.java public class SleepTest { public static void main(String[] args) throws Exception { Thread.sleep(5000); } } 1. Run whoopsie: $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 2. Run the SleepTest and SIGKILL it in another terminal: $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" 3. View the crash report and submit it: $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash 3a) View the report 3b) [Optional] Search for the "HotspotError" key 3c) Send the report 4. Verify that the report was saved, including the hs_err content: 4a) In whoopsie terminal, check the OOPS ID code 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID 4c) Confirm that the HotspotError was added to the report [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Import notes about running the testcase in Xenial and Zesty: 1. OpenJDK 8 has not yet been released with the apport hook on Xenial and Zesty; I copied the source_openjdk-8.py hook file from the apport package-hooks directory from OpenJDK 8 in artful to the right place in order to test it in Xenial and Zesty. 2. The HotspotError key was present in all cases when viewing the report with the apport-cli tool, as expected, and whoopsie *without* the fix ignored the key and didn't upload it, also as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). # SleepTest.java public class SleepTest { public static void main(String[] args) throws Exception { Thread.sleep(5000); } } 1. Run whoopsie: $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 2. Run the SleepTest and SIGKILL it in another terminal: $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" 3. View the crash report and submit it: $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash 3a) View the report 3b) [Optional] Search for the "HotspotError" key 3c) Send the report 4. Verify that the report was saved, including the hs_err content: 4a) In whoopsie terminal, check the OOPS ID code 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID 4c) Confirm that the HotspotError was added to the report [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1483888] Re: Ringtone cannot be heard when jack/headphones plugged
** Branch linked: lp:~tiagosh/telepathy-ofono/play_ringtone_speakers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1483888 Title: Ringtone cannot be heard when jack/headphones plugged Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in telephony-service package in Ubuntu: Confirmed Bug description: Aquaris E5: Ringtone cannot be heard when jack/headphones are plugged. This I consider a bug, since user cannot depend on the such a device with hearing calls in the morning. Typical scenario: listening to music/watching movies during the night and falling asleep. It already happened several times to me that I did not get awakened by the phone in the morning, since headphones were plugged into the device and all the sounds could be heard only in headphones. (The equivalent for the alarm clock is bug 1364647.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483888/+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 1489512] Re: slow to match contact name on messaging-app startup
@themeles What image version are you using? This is only present on rc- proposed channel yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1489512 Title: slow to match contact name on messaging-app startup Status in Canonical System Image: Fix Committed Status in address-book-service package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Confirmed Bug description: when Messages view loads for the first time, there is a delay (1-3 seconds) where the phone numbers are shown in the view and then after some time the contact matching occurs and the contact name fills in. This should be faster, also immediate really. We need to optimize how this lookup is done so it can happen more instantly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489512/+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 1513082] [NEW] Ringtone in silent mode not playing on wired headsets
Public bug reported: Currently telepathy-ofono changes the audio route according to its internal state. Considering that the audio route affects other components like telephony-service-approver/indicator, the audio routing should be done in telephony-service instead. Cases like playing ringtones in the headset while in silent mode, and handling incoming calls from other connection managers (sip for example) will require the audio routing being done in telephony-service as well. ** Affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Audio routing should be done outside telepathy-ofono + Ringtone in silent mode not playing on wired headsets -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1513082 Title: Ringtone in silent mode not playing on wired headsets Status in telepathy-ofono package in Ubuntu: New Bug description: Currently telepathy-ofono changes the audio route according to its internal state. Considering that the audio route affects other components like telephony-service-approver/indicator, the audio routing should be done in telephony-service instead. Cases like playing ringtones in the headset while in silent mode, and handling incoming calls from other connection managers (sip for example) will require the audio routing being done in telephony- service as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1513082/+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 1512132] Re: sometimes no ring for incoming calls.
@roa Do you at least see the snap decision (notification with the slider) to accept the call? Could you run the following command and paste the output for us? zgrep "Failed to get current playback position" $HOME/.cache/upstart/* Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: In Progress Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1512132] Re: sometimes no ring for incoming calls.
** Branch unlinked: lp:~tiagosh/telephony-service/fix-1512132 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: Incomplete Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1515677] Re: default sim not selected when opening message from indicator
** Branch linked: lp:~tiagosh/messaging-app/fix-preselect-default-sim -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1515677 Title: default sim not selected when opening message from indicator Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Confirmed Bug description: on latest rc-proposed r175 on krillin Make sure messaging app is closed and you have a default sim to send messages on in settings 1) send message to phone 2) open the message by clicking on the notification or opening from the messaging menu 3) messaging app launched and the message thread is displayed expected results: SIM selector in header should be selected with default sim choosen in settings actual result: No selection in SIM selector To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1515677/+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 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
Yes, this is still an issue. We agreed with Alfonso that ofono will use AccountsService to get the default sim card for calls. It needs some work on telephony-service and system-settings. -- 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/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: Triaged Status in telephony-service package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+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 1518344] Re: "Swipe to reveal actions" label needs more space.
** Branch linked: lp:~radonapps/messaging-app/fix_swipe- demo_text_position -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1518344 Title: "Swipe to reveal actions" label needs more space. Status in Canonical System Image: Triaged Status in messaging-app package in Ubuntu: Confirmed Bug description: Hi! I translated the following string to Hungarian: "Swipe to reveal actions" But it needs more space (see attached screenshot). Additional info: In the Phone app the same translation looks okay. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518344/+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 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)
The SIM information on the incoming call screen is about the sim card that's receiving the call from that contact, and not the sim card where that contact was originally stored. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1460301 Title: [Dialer] Incoming call - no info which SIM card was called (dual SIM) Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Committed Status in telephony-service package in Ubuntu: Fix Released Bug description: Ubuntu 14.10 (r22) (Don't know how to find a package version :/, but I checked for updates on 29-05-2015 and all apps are up to date) I have two SIM cards inserted into BQ Aquaris 4.5 On incoming call I expect to see information if SIM1 or SIM2 was dialled by caller alongside caller ID. I see only caller ID. It may be useful if one of the SIM cards is in roaming, or when one of the SIMs is a company number while other is a private number. UX comment --- The SIM card indication should replace the "Incoming call" text. This applies only for dual SIM devices. On a single SIM device the "Incoming call" labe remains. Please see attached wireframe for the exact solution. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1460301/+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 1513082] Re: Ringtone in silent mode not playing on wired headsets
** Branch linked: lp:~tiagosh/telephony-service/headset-silent-mode -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1513082 Title: Ringtone in silent mode not playing on wired headsets Status in Canonical System Image: Confirmed Status in telepathy-ofono package in Ubuntu: Confirmed Bug description: Currently telepathy-ofono changes the audio route according to its internal state. Considering that the audio route affects other components like telephony-service-approver/indicator, the audio routing should be done in telephony-service instead. Cases like playing ringtones in the headset while in silent mode, and handling incoming calls from other connection managers (sip for example) will require the audio routing being done in telephony- service as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513082/+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 1546094] [NEW] messaging-app apparmor profile deny reading dconf files
Public bug reported: Messaging-app is now running confined, but it can't recover some settings as read access to /home/phablet/.config/dconf/user is getting denied by the apparmor profile by default. This is currently causing problems to read the default sim card for messages and the mms group chat option under the settings panel. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~tiagosh/messaging-app/allow-reading-dconf-files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1546094 Title: messaging-app apparmor profile deny reading dconf files Status in messaging-app package in Ubuntu: New Bug description: Messaging-app is now running confined, but it can't recover some settings as read access to /home/phablet/.config/dconf/user is getting denied by the apparmor profile by default. This is currently causing problems to read the default sim card for messages and the mms group chat option under the settings panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1546094/+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 1503018] Re: Messages are not broken into lines on full word boundaries
** Branch linked: lp:~tiagosh/messaging-app/no-nbsp-in-bubbles -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1503018 Title: Messages are not broken into lines on full word boundaries Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Confirmed Bug description: The breaks are made within words and the formatting looks bad. This has regressed since ota6 in stable MX4 running 130 proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1503018/+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 1503018] Re: Messages are not broken into lines on full word boundaries
** Branch linked: lp:~tiagosh/messaging-app/revert_nbsp_replace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1503018 Title: Messages are not broken into lines on full word boundaries Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Confirmed Bug description: The breaks are made within words and the formatting looks bad. This has regressed since ota6 in stable MX4 running 130 proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1503018/+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 1503450] [NEW] mesa FTBFS due to missing Requires in mirclient
Public bug reported: mesa currently FTBFS due to a missing mirclient dependency during build time. Failed build at https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519 Build log: === /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\" -DPACKAGE_STRING=\"Mesa\ 11.0.2\" -DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\"; -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 -DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1 -DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1 -DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1 -DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1 -DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1 -DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1 -DHAVE_FUNC_ATTRIBUTE_PACKED=1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1 -DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl -D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main -I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS -D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP -DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS -DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2 -fvisibility=hidden -I/usr/include/libdrm -D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM -DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM -I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader -I../../../../src/egl/drivers/dri2 -I../../../../src/ gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl -I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm -DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\" -D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -std=c99 -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp -MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo ../../../../src/egl/main/eglfallbacks.c &&\ In file included from ../../../../src/egl/main/egldisplay.c:61:0: /usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal error: mir_toolkit/client_types.h: No such file or directory compilation terminated. make[3]: *** [main/egldisplay.lo] Error 1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1503450 Title: mesa FTBFS due to missing Requires in mirclient Status in mesa package in Ubuntu: New Bug description: mesa currently FTBFS due to a missing mirclient dependency during build time. Failed build at https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519 Build log: === /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\" -DPACKAGE_STRING=\"Mesa\ 11.0.2\" -DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\"; -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 -DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1 -DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1 -DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1 -DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1 -DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1 -DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1 -DHAVE_FUNC_ATTRIBUTE_PACKED= 1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1 -DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl -D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main -I../../../../src/gbm/main -I../../../..