[Touch-packages] [Bug 1815760] Re: Additional hooks for update
** Changed in: apt (Ubuntu Trusty) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update::Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => Medium ** Changed in: qtbase-opensource-src (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Status in qtbase-opensource-src source package in Cosmic: Fix Committed Bug description: [Impact] All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. [Test Case] 1) Install a printer that can duplex and configure it to do duplex with long-edge binding from the printer setup dialog. 2) Open a PDF with okular, and open the print dialog. Select the printer above. 3) Press the "Options" button to enlarge the dialog to also present the options. Select the "options" tab, right of "copies". Verify that Duplex Printing is preset to "None" This is wrong, because the printer was configured to do duplex with long-edge binding. 4) Print and close okular. 5) Reopen okular (with the same or another PDF file). Open again the print dialog and select the same printer. 6) Redo 3). Again see that Duplex Printing is preset to "None", instead of being at the default or at the previously used setup. [Regression Potential] The proposed patch only changes the default settings. The regression potential may be that the values are wrong, although they are already wrong. In case there is some bug it may lead to crashes. But this code is in the latest stable Qt release and I am not aware of any such crashes reported. [Other Info] The proposed patch is a backport of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e [Original Description] See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
** No longer affects: mesa (Ubuntu) ** No longer affects: mesa (Ubuntu Bionic) ** No longer affects: mesa (Ubuntu Disco) ** No longer affects: mesa (Ubuntu Cosmic) ** No longer affects: xorg-server-hwe-18.04 (Ubuntu Cosmic) ** No longer affects: xorg-server-hwe-18.04 (Ubuntu Disco) ** No longer affects: xorg-server-hwe-18.04 (Ubuntu) ** Changed in: xorg-server (Ubuntu Bionic) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Importance: Undecided => High -- 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/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Cosmic: Fix Committed Status in xorg-server source package in Disco: Fix Released Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz:
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
** Description changed: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is - asked for user name and password on every jon, insteaf of the + asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS /hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
cups 2.2.7-1ubuntu2.4 is now in bionic-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every jon, insteaf of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+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 1811000] Re: [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] Pulseaudio fails to detect card
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1811000 Title: [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Expired Bug description: 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at d472 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jan 8 21:55:38 2019 InstallationDate: Installed on 2018-10-23 (77 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Green Headphone Out, Right Title: [HP EliteBook 2560p, IDT 92HD81B1X5, Green Headphone Out, Right] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SSU Ver. F.02 dmi.board.name: 162B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 04.1E dmi.chassis.asset.tag: CNU14700DL dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SSUVer.F.02:bd07/26/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001D02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.1E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2560p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811000/+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 1740894] Re: KEY_RFKILL is not passed to userspace
** No longer affects: xkeyboard-config (Ubuntu Disco) ** No longer affects: xkeyboard-config (Ubuntu Cosmic) ** Also affects: xkeyboard-config (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: libxkbcommon (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: xorgproto (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: libxkbcommon (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: libxkbcommon (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: xkeyboard-config (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: xkeyboard-config (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: xorgproto (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: xorgproto (Ubuntu Cosmic) Importance: Undecided => Low ** No longer affects: xkeyboard-config (Ubuntu Bionic) ** Also affects: xkeyboard-config (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libxkbcommon (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorgproto (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libxkbcommon (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: libxkbcommon (Ubuntu Bionic) Status: New => Fix Released ** Changed in: xorgproto (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: xorgproto (Ubuntu Bionic) Status: New => Fix Released ** Changed in: xkeyboard-config (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: xkeyboard-config (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
** Changed in: mesa (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu Bionic) Importance: Undecided => High ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- 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/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1811225] Re: Mesa 18.2.8 stable release
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also several fixes for st/nine subcomponent. - Patch for RADV driver that fixes a hang in Yakuza using DXVK. - There are also fixes for Virgl driver. - Added PCI IDs for VegaM, Vega20 and Vega10. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
** Changed in: mesa (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
** Changed in: network-manager (Ubuntu Bionic)
Importance: Undecided => Medium
--
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/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Fix Committed
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+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 1809132] Re: Updated bionic to the current 1.10 stable version
** Tags added: upgrade-software-version ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- 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/1809132 Title: Updated bionic to the current 1.10 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+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 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
** Changed in: gnome-settings-daemon (Ubuntu) Status: Triaged => Fix Released ** Changed in: libx11 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: x11proto-core (Ubuntu) Status: New => Fix Released ** Changed in: xkeyboard-config (Ubuntu) Status: New => Fix Released ** No longer affects: xserver-xorg-input-evdev (Ubuntu) ** No longer affects: xserver-xorg-input-evdev (Ubuntu Precise) ** No longer affects: xserver-xorg-input-evdev (Ubuntu Raring) ** No longer affects: x11proto-core (Ubuntu Raring) ** No longer affects: xfce4-volumed (Ubuntu) ** No longer affects: xfce4-volumed (Ubuntu Precise) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project raring series: Won't Fix Status in xkeyboard-config: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libx11 package in Ubuntu: Fix Released Status in udev package in Ubuntu: Fix Released Status in x11proto-core package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Precise: Fix Released Status in libx11 source package in Precise: Fix Released Status in udev source package in Precise: Fix Released Status in x11proto-core source package in Precise: Fix Released Status in xkeyboard-config source package in Precise: Fix Released Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
*** This bug is a duplicate of bug 1740894 *** https://bugs.launchpad.net/bugs/1740894 ** This bug has been marked a duplicate of bug 1740894 KEY_RFKILL is not passed to userspace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1819302] [NEW] package apt 1.2.29ubuntu0.1 failed to install/upgrade: 在 conffile 提示时读取标准输入时遭遇 EOF
Public bug reported: dont know whats happen, just when starting my os and receive this problem warning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Mar 8 09:59:48 2019 ErrorMessage: 在 conffile 提示时读取标准输入时遭遇 EOF InstallationDate: Installed on 2018-03-17 (357 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29ubuntu0.1 SourcePackage: apt Title: package apt 1.2.29ubuntu0.1 failed to install/upgrade: 在 conffile 提示时读取标准输入时遭遇 EOF UpgradeStatus: Upgraded to xenial on 2019-03-06 (3 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1819302 Title: package apt 1.2.29ubuntu0.1 failed to install/upgrade: 在 conffile 提示时读取标准输入时遭遇 EOF Status in apt package in Ubuntu: New Bug description: dont know whats happen, just when starting my os and receive this problem warning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Mar 8 09:59:48 2019 ErrorMessage: 在 conffile 提示时读取标准输入时遭遇 EOF InstallationDate: Installed on 2018-03-17 (357 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29ubuntu0.1 SourcePackage: apt Title: package apt 1.2.29ubuntu0.1 failed to install/upgrade: 在 conffile 提示时读取标准输入时遭遇 EOF UpgradeStatus: Upgraded to xenial on 2019-03-06 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1819302/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in upower package in Ubuntu: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) 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/upower/+bug/1796550/+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 1819300] Re: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1819300 Title: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: New Bug description: cant upload packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2018i-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Mar 9 19:41:21 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1819300/+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 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1795764 Title: systemd: core: Fix edge case when processing /proc/self/mountinfo Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when processing /proc/self/mountinfo [03b8cfede] core: make sure to init mount params before calling mount_is_extrinsic() This patch changes mount_setup_unit() to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialised properly. Additionally, the patch got the blessing of 'xnox' who looked at it and mention it looks fine to him. [Pending SRU] Note: No autopkgtests has been reported since systemd (21.5) ... between 21.5 and now (21.11) everything released has been about security fixes : systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU systemd (229-4ubuntu21.10) xenial-security; urgency=medium systemd (229-4ubuntu21.9) xenial-security; urgency=medium systemd (229-4ubuntu21.8) xenial-security; urgency=medium systemd (229-4ubuntu21.6) xenial-security; urgency=medium systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU Note: I don't know the level of adoption of Netplan in Xenial, but I suspect it is low as Netplan replaced ifupdown as the default configuration utility starting with Ubuntu 17.10 Artful only AFAIK. * Regression in autopkgtest for nplan (s390x): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz Error: modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.4.0-138-generic Justification: This above seems to be a recurrent failure since a couple of release already. This wasn't introduce by this particular SRU. I don't think having wifi module is relevant in s390x anyway, so most likely the module is not there on purpose for kernel w/ s390x architecture. * Regression in autopkgtest for nplan (amd64): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz Error: (Ran on autopkgtest Ubuntu infra) test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL test_bridge_priority (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well- known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL Justification: The test are "passing" if ran manually in my own HW : autopkgtest [15:29:15]: host ; command line: /usr/bin/autopkgtest nplan -U --apt-pocket=proposed --log-file /tmp/adt-proposed.out --- qemu /var/lib/libvirt/images/autopkgtest-xenial-amd64.img . Setting up systemd (229-4ubuntu21.11) ... Setting up nplan (0.32~16.04.6) ... Setting up network-manager (1.2.6-0ubuntu0.16.04.3) ...
[Touch-packages] [Bug 1819300] [NEW] package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: cant upload packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2018i-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Mar 9 19:41:21 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-10 (0 days ago) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1819300 Title: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: New Bug description: cant upload packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2018i-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Mar 9 19:41:21 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2018i-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1819300/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic
** Changed in: pymacaroons (Ubuntu Artful) Status: Fix Committed => Won't Fix ** Changed in: py-macaroon-bakery (Ubuntu Artful) Status: In Progress => Won't Fix ** Changed in: protobuf (Ubuntu Artful) Status: Invalid => Fix Released ** Changed in: httmock (Ubuntu Artful) Status: Invalid => Fix Released ** Tags removed: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1735160 Title: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic Status in httmock package in Ubuntu: Fix Released Status in protobuf package in Ubuntu: Fix Released Status in py-macaroon-bakery package in Ubuntu: Fix Released Status in pymacaroons package in Ubuntu: Fix Released Status in httmock source package in Xenial: In Progress Status in protobuf source package in Xenial: Fix Committed Status in py-macaroon-bakery source package in Xenial: In Progress Status in pymacaroons source package in Xenial: Fix Committed Status in httmock source package in Artful: Fix Released Status in protobuf source package in Artful: Fix Released Status in py-macaroon-bakery source package in Artful: Won't Fix Status in pymacaroons source package in Artful: Won't Fix Bug description: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] - for protobuf: $ python3 -c "import google.protobuf" - for protobuf: $ python2 -c "import google.protobuf" - for python3-macaroonbakery: make sure all the tests pass - make sure "snapcraft login" works properly [Regression Potential] - httmock, none has it's not in xenial - protobuf, reduced considering that the code has been backported from master (small changes to make it compatabile py3 compatabile) - pymacaroons, none has 0.12 is backward compatible with 0.9.2 - py-macaroon-bakery, none has it's not in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1815760] Re: Additional hooks for update
** Changed in: apt (Ubuntu Trusty) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Won't Fix Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update::Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Hello Dimitri, or anyone else affected, Accepted ruby-openssl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ruby- openssl/2.0.9-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** No longer affects: python3.6 (Ubuntu) ** No longer affects: python3.7 (Ubuntu) ** Changed in: ruby-openssl (Ubuntu Bionic) Status: New => Fix Committed ** No longer affects: ruby-openssl (Ubuntu) ** No longer affects: ruby2.5 (Ubuntu) -- 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/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: In Progress Status in libio-socket-ssl-perl source package in Bionic: New Status in libnet-ssleay-perl source package in Bionic: New Status in nova source package in Bionic: New Status in openssl source package in Bionic: New Status in python-cryptography source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: New Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
** Tags added: patch-forwarded-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: In Progress Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type:
[Touch-packages] [Bug 1819296] Re: package cups-daemon 2.1.3-4ubuntu0.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1819296 Title: package cups-daemon 2.1.3-4ubuntu0.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: dpkg: erreur de traitement du paquet grub-gfxpayload-lists (--configure) : problèmes de dépendances - laissé non configuré Aucun rapport « apport » écrit car MaxReports a déjà été atteint Des erreurs ont été rencontrées pendant l'exécution : udev xserver-xorg-core-hwe-16.04 cups-daemon kmod avahi-daemon cups-core-drivers cups libnss-mdns:amd64 grub-common grub2-common grub-pc-bin grub-pc snapd ubuntu-core-launcher initramfs-tools-core initramfs-tools avahi-utils os-prober grub-gfxpayload-lists E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.7 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: Date: Sun Mar 10 01:07:04 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-12-05 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5420 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=3e50edc5-a1fd-4be1-8561-0a512c3df7dc ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=3e50edc5-a1fd-4be1-8561-0a512c3df7dc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-10 (0 days ago) dmi.bios.date: 09/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.asset.tag: LT2RJ35S1 dmi.board.name: 0675PR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LT2RJ35S1 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/19/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0675PR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1819296/+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 1819296] [NEW] package cups-daemon 2.1.3-4ubuntu0.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: dpkg: erreur de traitement du paquet grub-gfxpayload-lists (--configure) : problèmes de dépendances - laissé non configuré Aucun rapport « apport » écrit car MaxReports a déjà été atteint Des erreurs ont été rencontrées pendant l'exécution : udev xserver-xorg-core-hwe-16.04 cups-daemon kmod avahi-daemon cups-core-drivers cups libnss-mdns:amd64 grub-common grub2-common grub-pc-bin grub-pc snapd ubuntu-core-launcher initramfs-tools-core initramfs-tools avahi-utils os-prober grub-gfxpayload-lists E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.7 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: Date: Sun Mar 10 01:07:04 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-12-05 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5420 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=3e50edc5-a1fd-4be1-8561-0a512c3df7dc ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=3e50edc5-a1fd-4be1-8561-0a512c3df7dc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-10 (0 days ago) dmi.bios.date: 09/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.asset.tag: LT2RJ35S1 dmi.board.name: 0675PR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: LT2RJ35S1 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/19/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0675PR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1819296 Title: package cups-daemon 2.1.3-4ubuntu0.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: dpkg: erreur de traitement du paquet grub-gfxpayload-lists (--configure) : problèmes de dépendances - laissé non configuré Aucun rapport « apport » écrit car MaxReports a déjà été atteint Des erreurs ont été rencontrées pendant l'exécution : udev xserver-xorg-core-hwe-16.04 cups-daemon kmod avahi-daemon cups-core-drivers cups libnss-mdns:amd64 grub-common grub2-common grub-pc-bin grub-pc snapd ubuntu-core-launcher initramfs-tools-core initramfs-tools avahi-utils os-prober grub-gfxpayload-lists E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.7 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: Date: Sun Mar 10 01:07:04 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-12-05 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001
[Touch-packages] [Bug 1763870] Re: openssl: After symbol versioning, distributed pkgs are missing API symbols (e.g. EVP_PKEY_asn1_set_item)
** Also affects: openssl (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: openssl (Ubuntu) Status: New => Fix Released ** Changed in: openssl (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1763870 Title: openssl: After symbol versioning, distributed pkgs are missing API symbols (e.g. EVP_PKEY_asn1_set_item) Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Xenial: New Status in openssl package in Debian: Fix Released Bug description: I'm developing an ENGINE for OpenSSL, and close to release, I noticed that in Ubuntu 16.04 LTS and in Debian oldstable-backports the build fails with the following output: ``` /usr/bin/cc -fPIC -g -shared -Wl,-soname,liblibsuola.so -o liblibsuola.so CMakeFiles/suola.dir/suola.c.o CMakeFiles/suola.dir/suola_keypair.c.o CMakeFiles/suola.dir/debug/debug.c.o CMakeFiles/suola.dir/meths/X25519_meth.c.o CMakeFiles/suola.dir/meths/ed25519_meth.c.o CMakeFiles/suola.dir/meths/suola_asn1_meth.c.o CMakeFiles/suola.dir/meths/suola_md_identity_meth.c.o CMakeFiles/suola.dir/ossl/ossl_compat.c.o CMakeFiles/suola.dir/ossl/suola_err.c.o CMakeFiles/suola.dir/ossl/suola_objects.c.o CMakeFiles/suola.dir/providers/libsodium/base.c.o CMakeFiles/suola.dir/providers/libsodium/curve25519.c.o CMakeFiles/suola.dir/providers/libsodium/ed25519.c.o -lssl -lcrypto /opt/libsodium-stable/lib/libsodium.so -Wl,-z,defs -Wl,-rpath,/opt/libsodium-stable/lib: CMakeFiles/suola.dir/meths/suola_asn1_meth.c.o: In function `suola_register_asn1_meth': /usr/local/src/libsuola/meths/suola_asn1_meth.c:505: undefined reference to `EVP_PKEY_asn1_set_item' collect2: error: ld returned 1 exit status make[2]: *** [liblibsuola.so] Error 1 CMakeFiles/suola.dir/build.make:412: recipe for target 'liblibsuola.so' failed make[2]: Leaving directory '/usr/local/src/libsuola/build' make[1]: *** [CMakeFiles/suola.dir/all] Error 2 make: *** [all] Error 2 ``` This does not happen linking against the same exact release of openssl compiled from source on the same system. I then learned that one of the patches applied by Debian and inherited also by Ubuntu has the goal of versioning library symbols to avoid conflicts. Unfortunately said patch is not updated regularly with each release of OpenSSL, resulting, like in my case, in symbols available in the public header files but masked through versioning in the shared library binary. The attached patch fixes my need by adding `EVP_PKEY_asn1_set_item` to the list, but you might consider an internal review of your release process to make sure that the list of symbols is updated whenever a new upstream releases makes new functions publicly available. I believe this bug is important, as it stops everyone using official packages from using third-party ENGINEs that require to use that function to set special handling of ASN.1 format, which basically includes every ENGINE that would add support for cryptosystems that upstream OpenSSL does not support (defying the purpose of using some ENGINEs). The patch I propose covers my use case, but basically the package as is results unusable to any user of any application that may require functions available in the public headers but accidentally masked in the symbol versioning step. The ideal outcome of fixing this issue would consist in making the versioning patch dynamic, checking when symbols are added (or removed) in newer releases and updating the list accordingly. You might have the same versioning patch applied in other releases, so it's worth tagging this bug also for those to make the handling of the exposed symbols consistent. Finally I also opened a similar bug against the equivalent Debian oldstable-backports package, but I opened an Ubuntu-specific bug report because 16.04 ships a more recent version of the package and the inherited symbol versioning patch has already been modified compared with the original Debian one. For reference this is the Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895547 -- System information -- # lsv_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 # apt-cache policy libssl-dev libssl-dev: Installed: 1.0.2g-1ubuntu4.11 Candidate: 1.0.2g-1ubuntu4.11 Version table: *** 1.0.2g-1ubuntu4.11 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.2g-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libssl-dev
[Touch-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial
** Also affects: iproute2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu Xenial)
Status: New => Triaged
** Changed in: iproute2 (Ubuntu Xenial)
Importance: Undecided => Wishlist
** Changed in: iproute2 (Ubuntu)
Status: New => Fix Released
** Summary changed:
- iproute2: frr route protocols are not converted to string on xenial
+ Add support for custom protocols from rt_protos.d
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771783
Title:
Add support for custom protocols from rt_protos.d
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Triaged
Bug description:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define
their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Also affects: iproute2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: iproute2 (Ubuntu Xenial)
Importance: Undecided => Wishlist
** Changed in: iproute2 (Ubuntu Xenial)
Status: New => Triaged
** Summary changed:
- iproute2: unable to add ip lwt mpls route on xenial
+ Add encapsulation support to ip route
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771764
Title:
Add encapsulation support to ip route
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Triaged
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Hello Dimitri, or anyone else affected, Accepted r-cran-openssl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/r-cran- openssl/1.0.1-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: r-cran-openssl (Ubuntu Bionic) Status: New => Fix Committed ** No longer affects: r-cran-openssl (Ubuntu) ** No longer affects: libio-socket-ssl-perl (Ubuntu) ** Tags added: verification-needed verification-needed-bionic ** No longer affects: libnet-ssleay-perl (Ubuntu) ** No longer affects: nova (Ubuntu) ** No longer affects: python2.7 (Ubuntu) ** No longer affects: python-cryptography (Ubuntu) -- 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/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: In Progress Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in ruby-openssl package in Ubuntu: New Status in ruby2.5 package in Ubuntu: New Status in libio-socket-ssl-perl source package in Bionic: New Status in libnet-ssleay-perl source package in Bionic: New Status in nova source package in Bionic: New Status in openssl source package in Bionic: New Status in python-cryptography source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: New Status in ruby2.5 source package in Bionic: New Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 To manage notifications about
[Touch-packages] [Bug 1819288] [NEW] avahi-daemon spinning, using 65% of a CPU after connection to Les Schwab wifi
Public bug reported:
After connecting to a guest wifi, I notice that avahi-daemon is using an
unreasonable amount of CPU time on my laptop.
gdb shows a busy loop in avahi_simple_poll_iterate().
strace output looks like:
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "WW", 10) = 2
poll([{fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN}], 10, 0) = 4 ([{fd=16, revents=POLLIN}, {fd=13, revents=POLLIN},
{fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "WW", 10) = 2
poll([{fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN}], 10, 0) = 4 ([{fd=16, revents=POLLIN}, {fd=13, revents=POLLIN},
{fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "", 10) = 4
poll([{fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN}], 10, 0) = 4 ([{fd=16, revents=POLLIN}, {fd=13, revents=POLLIN},
{fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "", 10) = 4
poll([{fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN}], 10, 0) = 4 ([{fd=16, revents=POLLIN}, {fd=13, revents=POLLIN},
{fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
[...]
(repeats endlessly)
fd 6 and 7 are two ends of a pipe that avahi-daemon has open to itself.
It looks like avahi-daemon /eventually/ settles down, but this takes a
long time.
I'm not sure what to look for to explain this busy looping.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: avahi-daemon 0.7-4ubuntu2.1
ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 9 11:27:05 2019
InstallationDate: Installed on 2010-09-24 (3088 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: avahi
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (141 days ago)
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1819288
Title:
avahi-daemon spinning, using 65% of a CPU after connection to Les
Schwab wifi
Status in avahi package in Ubuntu:
New
Bug description:
After connecting to a guest wifi, I notice that avahi-daemon is using
an unreasonable amount of CPU time on my laptop.
gdb shows a busy loop in avahi_simple_poll_iterate().
strace output looks like:
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "WW", 10) = 2
poll([{fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN}], 10, 0) = 4 ([{fd=16, revents=POLLIN}, {fd=13, revents=POLLIN},
{fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "WW", 10) = 2
poll([{fd=6, events=POLLIN}, {fd=16, events=POLLIN}, {fd=15, events=POLLIN},
{fd=14, events=POLLIN}, {fd=13, events=POLLIN}, {fd=12, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=10, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN}], 10, 0) = 4 ([{fd=16, revents=POLLIN}, {fd=13, revents=POLLIN},
{fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7,
[Touch-packages] [Bug 1818520] Re: FFe: tdb 1.3.18
This bug was fixed in the package tdb - 1.3.18-0ubuntu1 --- tdb (1.3.18-0ubuntu1) disco; urgency=medium * New upstream version: 1.3.18 (LP: #1818520) - d/p/40_test_transaction_expand_non_fatal.diff: refresh to get rid of fuzz - d/rules: use "find" for the cleanup target instead of listing every single file or directory we have to remove. - d/libtdb1.symbols: added new symbols for 1.3.17 and 1.3.18 - d/libtdb-dev.install: also install the static library - d/rules: python3 is what the tdb buildsystem looks for by default, which makes --extra-python take python2 and not python3. Also, don't specify PYTHON and let it pick python3 as it wants. -- Andreas Hasenack Fri, 08 Mar 2019 13:10:46 + ** Changed in: tdb (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tdb in Ubuntu. https://bugs.launchpad.net/bugs/1818520 Title: FFe: tdb 1.3.18 Status in tdb package in Ubuntu: Fix Released Bug description: This is part of the effort to remove python2 from the desktop images (see bug #1440381). It's needed for the samba FFe bug #1818518. Samba 4.10.0 needs tdb >= 1.3.17. Version 1.3.18 introduces (python and otherwise) build fixes for issues in 1.3.17. tdb already builds python2 and python3 packages: this bug is about the new version being needed just to satisfy samba 4.10's dependency. We can't drop python-tdb (the py2 version) because bzr-git has a Recommends on it. There are no specific release notes for tdb from upstream, as its development is closely tied to samba. Commit history: https://gitlab.com/samba- team/samba/tree/v4-10-test/lib/tdb https://code.launchpad.net/~ahasenack/ubuntu/+source/tdb/+git/tdb/+ref /disco-tdb-1.3.18 You can diff against "ubuntu/devel" to see what has changed. I will still create MPs in LP for this, and there are likely to be changes coming from review feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tdb/+bug/1818520/+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 1818953] test perl script
--- Comment on attachment From myung...@us.ibm.com 2019-03-09 10:52
EDT---
This perl script will cause an error on Ubuntu 19.04:
# perl test.pl
Calling mblen with str=data
perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
Aborted
** Attachment added: "test perl script"
https://bugs.launchpad.net/bugs/1818953/+attachment/5244974/+files/test.pl
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
Perl core dumping core on UBUNTU 19.04 by executing perl script
Status in The Ubuntu-power-systems project:
Incomplete
Status in perl package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - NAGENDRA P. DONTAMSETTY - 2019-02-28
00:14:49 ==
---Problem Description---
Perl core dumping core on UBUNTU 19.04 by executing perl script
---uname output---
root@p8ct1p13:/tmp# uname -a Linux p8ct1p13.in.ibm.com 4.19.0-13-generic
#14-Ubuntu SMP Thu Feb 7 21:50:00 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = ppc64le and power8
---Debugger Data---
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
---Steps to Reproduce---
Description: Perl core dumpinmg core on UBUNTU 19.04 by exec cmd "mkrsrc"
root@p8ct1p13:/tmp# uname -a
Linux p8ct1p13.in.ibm.com 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:50:00
UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
root@p8ct1p13:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
VERSION_ID="19.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco
root@p8ct1p13:~# ctversion -bv
RSCT_Build_Name=rsholxs002a 3.2.4.2 RSCT_Build_Time=19043.16:11:49
RSCT_Build_Context=ppc64le_linux_2
root@p8ct1p13:/tmp# mkrsrc IBM.Ray Name="fvt1"
NodeNameList={"p8ct1p09.in.ibm.com"} ManualMode=0 Int32=00 String="Initial Test
String 2"
perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
Aborted (core dumped)
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
root@p8ct1p13:/tmp# which mkrsrc
/usr/bin/mkrsrc
root@p8ct1p13:/tmp# file /usr/bin/mkrsrc
/usr/bin/mkrsrc: symbolic link to /opt/rsct/bin/mkrsrc
root@p8ct1p13:/tmp# file /opt/rsct/bin/mkrsrc
/opt/rsct/bin/mkrsrc: Perl script text executable
Contact Information = Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com
Userspace tool common name: perl 5
The userspace tool has the following bit modes: 64bit
Userspace rpm: ii perl 5.28.1-4
ppc64el
Userspace tool obtained from project website: na
*Additional Instructions for Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com:
-Post a private note with access information to the machine that is currently
in the debugger.
-Attach ltrace and strace of userspace application.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 1818953] Comment bridged from LTC Bugzilla
--- Comment From myung...@us.ibm.com 2019-03-09 10:53 EDT---
In fact, this can be easily reproduced using a simple perl script.
test.pl
--
#!//usr/bin/perl
use POSIX qw(mblen);
my $str = "data";
print "Calling mblen with str=$str\n";
my $len = mblen($str, MB_CUR_MAX);
print "mblen returned with len=$len\n";
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
Perl core dumping core on UBUNTU 19.04 by executing perl script
Status in The Ubuntu-power-systems project:
Incomplete
Status in perl package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - NAGENDRA P. DONTAMSETTY - 2019-02-28
00:14:49 ==
---Problem Description---
Perl core dumping core on UBUNTU 19.04 by executing perl script
---uname output---
root@p8ct1p13:/tmp# uname -a Linux p8ct1p13.in.ibm.com 4.19.0-13-generic
#14-Ubuntu SMP Thu Feb 7 21:50:00 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = ppc64le and power8
---Debugger Data---
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
---Steps to Reproduce---
Description: Perl core dumpinmg core on UBUNTU 19.04 by exec cmd "mkrsrc"
root@p8ct1p13:/tmp# uname -a
Linux p8ct1p13.in.ibm.com 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:50:00
UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
root@p8ct1p13:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
VERSION_ID="19.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco
root@p8ct1p13:~# ctversion -bv
RSCT_Build_Name=rsholxs002a 3.2.4.2 RSCT_Build_Time=19043.16:11:49
RSCT_Build_Context=ppc64le_linux_2
root@p8ct1p13:/tmp# mkrsrc IBM.Ray Name="fvt1"
NodeNameList={"p8ct1p09.in.ibm.com"} ManualMode=0 Int32=00 String="Initial Test
String 2"
perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
Aborted (core dumped)
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
root@p8ct1p13:/tmp# which mkrsrc
/usr/bin/mkrsrc
root@p8ct1p13:/tmp# file /usr/bin/mkrsrc
/usr/bin/mkrsrc: symbolic link to /opt/rsct/bin/mkrsrc
root@p8ct1p13:/tmp# file /opt/rsct/bin/mkrsrc
/opt/rsct/bin/mkrsrc: Perl script text executable
Contact Information = Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com
Userspace tool common name: perl 5
The userspace tool has the following bit modes: 64bit
Userspace rpm: ii perl 5.28.1-4
ppc64el
Userspace tool obtained from project website: na
*Additional Instructions for Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com:
-Post a private note with access information to the machine that is currently
in the debugger.
-Attach ltrace and strace of userspace application.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 1819277] Re: I see stripes plomas in full screen mode
https://gitlab.gnome.org/GNOME/totem/issues/307#note_455803 "Bug in mesa, duplicate of #264 (closed)" ** Description changed: https://gitlab.gnome.org/GNOME/totem/issues/307 --- When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. + + The problem occurs with wayland, in xorg it looks good. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) ** No longer affects: wayland (Ubuntu) ** Changed in: totem (Ubuntu) Status: New => Invalid ** Description changed: https://gitlab.gnome.org/GNOME/totem/issues/307 --- When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. - The problem occurs with wayland, in xorg it looks good. + The problem occurs with wayland, in Xorg it looks good. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #307 https://gitlab.gnome.org/GNOME/totem/issues/307 -- 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/1819277 Title: I see stripes plomas in full screen mode Status in mesa package in Ubuntu: Confirmed Status in totem package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/totem/issues/307 --- When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. The problem occurs with wayland, in Xorg it looks good. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+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 1819277] [NEW] I see stripes plomas in full screen mode
Public bug reported: https://gitlab.gnome.org/GNOME/totem/issues/307 --- When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Attachment added: "Captura de pantalla de 2019-03-09 12-11-28.png" https://bugs.launchpad.net/bugs/1819277/+attachment/5244952/+files/Captura%20de%20pantalla%20de%202019-03-09%2012-11-28.png ** Description changed: + https://gitlab.gnome.org/GNOME/totem/issues/307 + + --- + When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also 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 wayland in Ubuntu. https://bugs.launchpad.net/bugs/1819277 Title: I see stripes plomas in full screen mode Status in mesa package in Ubuntu: New Status in totem package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/issues/307 --- When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+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 1819272] [NEW] no print from HP Envy 5530
Public bug reported: cannot print pdf, except first page through Libre Draw. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CupsErrorLog: E [09/Mar/2019:09:19:30 -0500] Unknown directive JobPrivateAccess on line 123 of /etc/cups/cupsd.conf. E [09/Mar/2019:09:19:30 -0500] Unknown directive JobPrivateValues on line 124 of /etc/cups/cupsd.conf. E [09/Mar/2019:09:19:30 -0500] Unknown directive SubscriptionPrivateAccess on line 125 of /etc/cups/cupsd.conf. E [09/Mar/2019:09:19:30 -0500] Unknown directive SubscriptionPrivateValues on line 126 of /etc/cups/cupsd.conf. CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 09:43:09 2019 InstallationDate: Installed on 2019-01-07 (61 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for ENVY-5530-series: hp:/usb/ENVY_5530_series?serial=CN43I210GS05XT device for Generic-CUPS-BRF-Printer: cups-brf:/ MachineType: Dell Inc. Inspiron 5558 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Generic-CUPS-BRF-Printer.ppd', '/etc/cups/ppd/ENVY-5530-series.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Generic-CUPS-BRF-Printer.ppd: Permission denied grep: /etc/cups/ppd/ENVY-5530-series.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=2916d9f1-41e2-4b63-8b0b-4a8c5fd65a11 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0FF8N0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd11/22/2016:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0FF8N0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5558 dmi.product.sku: Inspiron 5558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1819272 Title: no print from HP Envy 5530 Status in cups package in Ubuntu: New Bug description: cannot print pdf, except first page through Libre Draw. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CupsErrorLog: E [09/Mar/2019:09:19:30 -0500] Unknown directive JobPrivateAccess on line 123 of /etc/cups/cupsd.conf. E [09/Mar/2019:09:19:30 -0500] Unknown directive JobPrivateValues on line 124 of /etc/cups/cupsd.conf. E [09/Mar/2019:09:19:30 -0500] Unknown directive SubscriptionPrivateAccess on line 125 of /etc/cups/cupsd.conf. E [09/Mar/2019:09:19:30 -0500] Unknown directive SubscriptionPrivateValues on line 126 of /etc/cups/cupsd.conf. CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 09:43:09 2019 InstallationDate: Installed on 2019-01-07 (61 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for ENVY-5530-series: hp:/usb/ENVY_5530_series?serial=CN43I210GS05XT device for Generic-CUPS-BRF-Printer: cups-brf:/ MachineType: Dell Inc. Inspiron 5558 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Generic-CUPS-BRF-Printer.ppd', '/etc/cups/ppd/ENVY-5530-series.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Generic-CUPS-BRF-Printer.ppd: Permission denied grep: /etc/cups/ppd/ENVY-5530-series.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=2916d9f1-41e2-4b63-8b0b-4a8c5fd65a11 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0FF8N0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1818996] Re: auth.conf.d directory missing
This bug was fixed in the package apt - 1.8.0 --- apt (1.8.0) unstable; urgency=medium [ David Kalnischkies ] * Add explicit message for unsupported binary signature (Closes: #921685) [ Milo Casagrande ] * [l10n] Update Italian translation [ Julian Andres Klode ] * Fix name of APT::Update::Post-Invoke-Stats (was ...Update-Post...) * CMake: Install auth.conf.d directory (LP: #1818996) [ Frans Spiesschaert ] * Dutch program translation update (Closes: #923728) * Dutch manpages translation update (Closes: #923834) -- Julian Andres Klode Fri, 08 Mar 2019 09:41:20 +0100 ** Changed in: apt (Ubuntu Disco) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1818996 Title: auth.conf.d directory missing Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: Fix Released Bug description: [Impact] apt in disco and the current set of SRUs introduce support for .conf snippets in auth.conf.d, but accidentally did not introduce the auth.conf.d directory, making it hard to discover if support for it exists, and requiring users to create the dir if it is missing - that's bad UX. [Test case] Install apt, make sure /etc/apt/auth.conf.d exists [Regression potential] It's just a directory, what could possibly go wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1818996/+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 1819268] Re: package unattended-upgrades 0.90ubuntu0.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1819268 Title: package unattended-upgrades 0.90ubuntu0.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: Hi Team, I'm facing system error as soon as I Login.Seems like i have replaced a file while upgrading . Thanks, Chandra ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.10 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Mar 7 21:49:37 2019 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.10 Installing new version of config file /etc/logrotate.d/unattended-upgrades ... frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-02 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-07 (2 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2019-02-17T17:53:07.538650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1819268/+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 1819268] [NEW] package unattended-upgrades 0.90ubuntu0.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Hi Team, I'm facing system error as soon as I Login.Seems like i have replaced a file while upgrading . Thanks, Chandra ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.10 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Mar 7 21:49:37 2019 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.10 Installing new version of config file /etc/logrotate.d/unattended-upgrades ... frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-02 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-07 (2 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2019-02-17T17:53:07.538650 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1819268 Title: package unattended-upgrades 0.90ubuntu0.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: Hi Team, I'm facing system error as soon as I Login.Seems like i have replaced a file while upgrading . Thanks, Chandra ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.10 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Mar 7 21:49:37 2019 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.10 Installing new version of config file /etc/logrotate.d/unattended-upgrades ... frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-02 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-03-07 (2 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2019-02-17T17:53:07.538650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1819268/+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 1819264] [NEW] Graphis problem
Public bug reported: How can i install graphis in dell inspiron 3442. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 18:33:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-03-08 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3442 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=950331ed-5458-421a-be4b-05d38ca12e30 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0486K1 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0486K1:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3442 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1819264 Title: Graphis problem Status in xorg package in Ubuntu: New Bug description: How can i install graphis in dell inspiron 3442. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 18:33:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-03-08 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3442 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=950331ed-5458-421a-be4b-05d38ca12e30 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0486K1 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0486K1:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3442 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to:
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted figtree into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/figtree/1.4.4-3~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** No longer affects: gettext (Ubuntu) ** No longer affects: figtree (Ubuntu) ** No longer affects: activemq (Ubuntu) ** No longer affects: jxgrabkey (Ubuntu) ** No longer affects: afterburner.fx (Ubuntu) ** No longer affects: annotation-indexer (Ubuntu) ** No longer affects: apache-directory-server (Ubuntu) ** No longer affects: aspectj (Ubuntu) ** No longer affects: aspectj-maven-plugin (Ubuntu) ** No longer affects: batik (Ubuntu) ** No longer affects: bindex (Ubuntu) -- 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 fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in saaj package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 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 hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix
[Touch-packages] [Bug 1819255] Re: Ubuntu 18.04 suspends intermittently
** Description changed: I am using Lenovo Thinkpad E450 with Ubuntu 18.04.2 and kernel version is Linux 4.14.105-0414105-generic. I am currently not able to suspend my laptop properly. I first experienced this when I was using the kernel 4.15.46. Expected behavior when commanded to suspend: Display goes black, the CPU fan is switched off, the power LED pulsates showing that the computer is in suspend mode. This should happen whenever the PC is suspended using the command 'sudo systemctl suspend' or closing the lid or choosing suspend in the menu options by long-pressing the power button. What actually happens: If any of the above methods is used to suspend the PC, the display goes black, the PC goes to suspend state after a few seconds, but remains in suspend only for a maximum of 7-10 seconds. After that it automatically resumes, with the display trying to show the lockscreen if lid is not closed. If lid is closed, then I know it has resumed as the power LED stays on and the fan runs. As time goes, it intermittently goes to suspend for a few seconds and resumes back. There is no unnatural behavior according to 'journalctl' or 'dmesg'. The system supposedly goes to suspend "only for a few seconds" and resumes back. To resolve this issue I tried using 4.18 kernel and still the issue persisted.(Original kernel version was 4.15) In another forum, I was suggested to use 4.14 kernel and even now the issue persists. I don't know if this information would be helpful but during boot, I got these errors: ACPI Error: Needed type [Reference], found [Integer] (ptrval) (20180531/exresop-69) ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20180531/dswexec-427) ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516) + I also did a 'cat /sys/kernel/debug/suspend_stats' which returned 5 + successes and 0 failures of any type. + PS: I don't think this is a bug based on a particular application/package, so I didn't include any. Thanks in advance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1819255 Title: Ubuntu 18.04 suspends intermittently Status in pm-utils package in Ubuntu: New Bug description: I am using Lenovo Thinkpad E450 with Ubuntu 18.04.2 and kernel version is Linux 4.14.105-0414105-generic. I am currently not able to suspend my laptop properly. I first experienced this when I was using the kernel 4.15.46. Expected behavior when commanded to suspend: Display goes black, the CPU fan is switched off, the power LED pulsates showing that the computer is in suspend mode. This should happen whenever the PC is suspended using the command 'sudo systemctl suspend' or closing the lid or choosing suspend in the menu options by long-pressing the power button. What actually happens: If any of the above methods is used to suspend the PC, the display goes black, the PC goes to suspend state after a few seconds, but remains in suspend only for a maximum of 7-10 seconds. After that it automatically resumes, with the display trying to show the lockscreen if lid is not closed. If lid is closed, then I know it has resumed as the power LED stays on and the fan runs. As time goes, it intermittently goes to suspend for a few seconds and resumes back. There is no unnatural behavior according to 'journalctl' or 'dmesg'. The system supposedly goes to suspend "only for a few seconds" and resumes back. To resolve this issue I tried using 4.18 kernel and still the issue persisted.(Original kernel version was 4.15) In another forum, I was suggested to use 4.14 kernel and even now the issue persists. I don't know if this information would be helpful but during boot, I got these errors: ACPI Error: Needed type [Reference], found [Integer] (ptrval) (20180531/exresop-69) ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20180531/dswexec-427) ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516) I also did a 'cat /sys/kernel/debug/suspend_stats' which returned 5 successes and 0 failures of any type. PS: I don't think this is a bug based on a particular application/package, so I didn't include any. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1819255/+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 1817338] Re: HDMI sound output not available
I can confirm it works when booting a live 18.10 session. As to tell exactly when it broke, it's kind of hard, but it was near the beginning of february... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1817338 Title: HDMI sound output not available Status in pulseaudio package in Ubuntu: Incomplete Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1817338/+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 1819255] [NEW] Ubuntu 18.04 suspends intermittently
Public bug reported: I am using Lenovo Thinkpad E450 with Ubuntu 18.04.2 and kernel version is Linux 4.14.105-0414105-generic. I am currently not able to suspend my laptop properly. I first experienced this when I was using the kernel 4.15.46. Expected behavior when commanded to suspend: Display goes black, the CPU fan is switched off, the power LED pulsates showing that the computer is in suspend mode. This should happen whenever the PC is suspended using the command 'sudo systemctl suspend' or closing the lid or choosing suspend in the menu options by long-pressing the power button. What actually happens: If any of the above methods is used to suspend the PC, the display goes black, the PC goes to suspend state after a few seconds, but remains in suspend only for a maximum of 7-10 seconds. After that it automatically resumes, with the display trying to show the lockscreen if lid is not closed. If lid is closed, then I know it has resumed as the power LED stays on and the fan runs. As time goes, it intermittently goes to suspend for a few seconds and resumes back. There is no unnatural behavior according to 'journalctl' or 'dmesg'. The system supposedly goes to suspend "only for a few seconds" and resumes back. To resolve this issue I tried using 4.18 kernel and still the issue persisted.(Original kernel version was 4.15) In another forum, I was suggested to use 4.14 kernel and even now the issue persists. I don't know if this information would be helpful but during boot, I got these errors: ACPI Error: Needed type [Reference], found [Integer] (ptrval) (20180531/exresop-69) ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20180531/dswexec-427) ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516) PS: I don't think this is a bug based on a particular application/package, so I didn't include any. Thanks in advance ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: suspend-resume -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1819255 Title: Ubuntu 18.04 suspends intermittently Status in pm-utils package in Ubuntu: New Bug description: I am using Lenovo Thinkpad E450 with Ubuntu 18.04.2 and kernel version is Linux 4.14.105-0414105-generic. I am currently not able to suspend my laptop properly. I first experienced this when I was using the kernel 4.15.46. Expected behavior when commanded to suspend: Display goes black, the CPU fan is switched off, the power LED pulsates showing that the computer is in suspend mode. This should happen whenever the PC is suspended using the command 'sudo systemctl suspend' or closing the lid or choosing suspend in the menu options by long-pressing the power button. What actually happens: If any of the above methods is used to suspend the PC, the display goes black, the PC goes to suspend state after a few seconds, but remains in suspend only for a maximum of 7-10 seconds. After that it automatically resumes, with the display trying to show the lockscreen if lid is not closed. If lid is closed, then I know it has resumed as the power LED stays on and the fan runs. As time goes, it intermittently goes to suspend for a few seconds and resumes back. There is no unnatural behavior according to 'journalctl' or 'dmesg'. The system supposedly goes to suspend "only for a few seconds" and resumes back. To resolve this issue I tried using 4.18 kernel and still the issue persisted.(Original kernel version was 4.15) In another forum, I was suggested to use 4.14 kernel and even now the issue persists. I don't know if this information would be helpful but during boot, I got these errors: ACPI Error: Needed type [Reference], found [Integer] (ptrval) (20180531/exresop-69) ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20180531/dswexec-427) ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516) PS: I don't think this is a bug based on a particular application/package, so I didn't include any. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1819255/+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
