[Touch-packages] [Bug 388850] Re: /etc/init.d/cups writes to /usr
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/388850 Title: /etc/init.d/cups writes to /usr Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups Hello, in /etc/init.d/cups it writes to /usr hierarchy, as fas as I understood violating FHS. chown root:lpadmin /usr/share/ppd/custom 2>/dev/null || true chmod 3775 /usr/share/ppd/custom 2>/dev/null || true Don't know if at runtime write access is necessary, but that directory should then moved to /var $ lsb_release -rd Description: Ubuntu karmic (development branch) Release: 9.10 $ LANG= apt-cache policy cups cups: Installed: 1.3.10-5 Candidate: 1.3.10-5 Version table: *** 1.3.10-5 0 500 http://nl.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status This is the only package I have seen, writing unattended to /usr Best regards, Roland "Test-tools" Bär To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/388850/+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 426776] Re: Deleted printer comes back
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/426776 Title: Deleted printer comes back Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups I have an HP 6310 All In One printer/scanner/copier/fax device. Firstly, thanks for making this device painless to use in Ubuntu, I love it! The issue is that the device is a scanner and printer (via USB) and a printer (via Ethernet). I print to it from multiple computers, so I have them all set to print over the network. This works fine. However on the desktop PC it is sat next to, it is also connected via USB, and as such gets auto detected and I now have two printers on my desktop. The name doesn't explicitly identify which is the 'usb connected' one and which is the 'network connected' one. I deleted the USB connected printer because I want all machines to print over the network, even this one. However the next time I booted up the printer it was re-detected and reappeared on my desktop. I would like a deleted printer to go away and stay away. I appreciate this may not be a bug, it may be a wishlist item, I just wanted it to be noted that there is a use case for a printer to be removed. I don't want to have to maintain multiple printer definitions on my desktop PC. ProblemType: Bug Architecture: amd64 Date: Wed Sep 9 12:56:24 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Officejet-6300-series: hp:/usb/Officejet_6300_series?serial=CN88BFB5N204M4 device for Officejet-6300-series-Fax: hpfax:/usb/Officejet_6300_series?serial=CN88BFB5N204M4 device for Officejet-6300_Network: dnssd://Officejet%206300%20series%20%5B4337AB%5D._pdl-datastream._tcp.local/ MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: cups 1.4.0-5 Papersize: a4 PccardctlIdent: PccardctlStatus: PpdFiles: Officejet-6300-series-Fax: HP Fax hpcups Officejet-6300_Network: HP Officejet 6300 Series, hpcups 3.9.8 Officejet-6300-series: HP Officejet 6300 Series, hpcups 3.9.8 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-9-generic root=UUID=c0284904-fb40-40a3-bf9b-7d7fd302fb33 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-9.29-generic SourcePackage: cups Uname: Linux 2.6.31-9-generic x86_64 dmi.bios.date: 04/24/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N32-E SLI ACPI BIOS Revision 1801 dmi.board.name: P5N32-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIACPIBIOSRevision1801:bd04/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/426776/+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 437302] Re: cups [Job 61] Stopping job because the scheduler could not open the output file.
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/437302 Title: cups [Job 61] Stopping job because the scheduler could not open the output file. Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups Hello all, No more possible to print. lpstat -t le programmateur s’exécute destination système par défaut : RX425 périphérique pour RX425 : ///dev/usb/usbmon3 RX425 acceptant des requêtes depuis sam. 26 sept. 2009 19:45:07 CEST l’imprimante RX425 est inactive, mais activée depuis sam. 26 sept. 2009 19:45:07 CEST guy@guy-desktop:/var/log/cups$ D [26/Sep/2009:19:45:01 +0200] cupsdReadClient: 9 1.1 Get-Printer-Attributes 1 D [26/Sep/2009:19:45:01 +0200] Get-Printer-Attributes ipp://localhost/printers/RX425 D [26/Sep/2009:19:45:01 +0200] Returning IPP successful-ok for Get-Printer-Attributes (ipp://localhost/printers/RX425) from localhost D [26/Sep/2009:19:45:01 +0200] cupsdSetBusyState: Not busy D [26/Sep/2009:19:45:07 +0200] cupsdAcceptClient: 10 from localhost (Domain) D [26/Sep/2009:19:45:07 +0200] cupsdReadClient: 10 POST /printers/RX425 HTTP/1.1 D [26/Sep/2009:19:45:07 +0200] cupsdSetBusyState: Active clients D [26/Sep/2009:19:45:07 +0200] cupsdAuthorize: No authentication data provided. D [26/Sep/2009:19:45:07 +0200] cupsdReadClient: 10 1.1 Print-Job 1 D [26/Sep/2009:19:45:07 +0200] Print-Job ipp://localhost/printers/RX425 D [26/Sep/2009:19:45:07 +0200] [Job ???] Auto-typing file... I [26/Sep/2009:19:45:07 +0200] [Job ???] Request file type is application/postscript. D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(J-) D [26/Sep/2009:19:45:07 +0200] cupsdSetBusyState: Active clients and dirty files D [26/Sep/2009:19:45:07 +0200] add_job: requesting-user-name="guy" D [26/Sep/2009:19:45:07 +0200] Adding default job-sheets values "none,none"... I [26/Sep/2009:19:45:07 +0200] [Job 61] Adding start banner page "none". D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(-S) D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(J-) I [26/Sep/2009:19:45:07 +0200] [Job 61] Adding end banner page "none". I [26/Sep/2009:19:45:07 +0200] [Job 61] File of type application/postscript queued by "guy". D [26/Sep/2009:19:45:07 +0200] [Job 61] hold_until=0 I [26/Sep/2009:19:45:07 +0200] [Job 61] Queued on "RX425" by "guy". D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(J-) D [26/Sep/2009:19:45:07 +0200] cupsdSetBusyState: Active clients, printing jobs, and dirty files D [26/Sep/2009:19:45:07 +0200] cupsdMarkDirty(-S) D [26/Sep/2009:19:45:07 +0200] [Job 61] job-sheets=none,none D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[0]="RX425" D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[1]="61" D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[2]="guy" D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[3]="Test Page" D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[4]="1" D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[5]="PageSize=A4 job-uuid=urn:uuid:dcddb2ee-42ec-3869-5c98-1911b0e554e7 job-originating-host-name=localhost" D [26/Sep/2009:19:45:07 +0200] [Job 61] argv[6]="/var/spool/cups/d00061-001" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[0]="CUPS_CACHEDIR=/var/cache/cups" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[1]="CUPS_DATADIR=/usr/share/cups" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[2]="CUPS_DOCROOT=/usr/share/cups/doc-root" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[4]="CUPS_REQUESTROOT=/var/spool/cups" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[5]="CUPS_SERVERBIN=/usr/lib/cups" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[6]="CUPS_SERVERROOT=/etc/cups" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[7]="CUPS_STATEDIR=/var/run/cups" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[8]="HOME=/var/spool/cups/tmp" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[9]="PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[10]="SERVER_ADMIN=root@guy-desktop" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[11]="SOFTWARE=CUPS/1.4.1" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[12]="TMPDIR=/var/spool/cups/tmp" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[13]="TZ=Europe/Paris" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[14]="USER=root" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[15]="CUPS_SERVER=/var/run/cups/cups.sock" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[16]="CUPS_ENCRYPTION=IfRequested" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[17]="CHARSET=utf-8" D [26/Sep/2009:19:45:07 +0200] [Job 61] envp[18]="LANG=fr_FR.UTF-8" D [26/Sep/2009:19:45:07 +0200] [Job 61]
[Touch-packages] [Bug 405320] Re: crash CUPS after print logout
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/405320 Title: crash CUPS after print logout Status in cups package in Ubuntu: Expired Bug description: Binary package hint: libdebian-installer4-udeb iacnt print from my Ubuntu jaunty on Epson c90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/405320/+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 413867] Re: something touched my cupsd.conf
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/413867 Title: something touched my cupsd.conf Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups On this system I never had a printer. However, my cupsd.conf file was modified somehow: Setting up cups (1.3.11-1ubuntu6) ... Configuration file `/etc/cups/cupsd.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. Maybe its not cups itself that changed the conf file - I dont know, but something did as I get what i pasted above. Are there packages that are known to touch that file? If so, please add the packages that do that without me touching printing ;). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/413867/+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 425176] Re: Can't remove old shared printers
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/425176 Title: Can't remove old shared printers Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups Under Jaunty. I can't remove old shared printers automatically found by cups. There are still present in client but no more here on my servers (no more physically, and no more shared by cups on my server). At the end, the client offers me to print under 5 or 6 printers that do not exist since one year. And I can't remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/425176/+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 445700] Re: cupsd taking 100% cpu after unsucessful network printer search
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/445700 Title: cupsd taking 100% cpu after unsucessful network printer search Status in cups package in Ubuntu: Expired Bug description: I tried to search for a new printer and the system-config-printer hang forever. I closed it (the system asked me to "force quit" or "wait", I had to "force quit"). After some hours I noticed that cupsd is taking 100% of one of my cpus. Also the tray icon disapeared, but I'm not sure if this has something to do with it (it no longer appears when I print something). And I can print normaly, on the other side. This is a desktop and server, so I did not reboot it very often. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/445700/+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 400855] Re: CUPS interface is unintuitive
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/400855 Title: CUPS interface is unintuitive Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups I'm using Kubuntu 9.04. There does not seem to be any usable GUI for printers. I added a printer using "Printer Configuration" in KDE's "System Settings". I used it once successfully - but next day, the printer seems to have disappeared, even though it still shows up in some (but not all!) print dialogs. Should it actually show up in the list in "Printer Configuration"? Or is it only used for adding new printers? I decided to go to the CUPS web interface, http://localhost:631, expecting to find some authoritative information there - but I'm still confused. The printers tab says "Showing 0 of 1 printer." Uh ok. So where is that one printer? The jobs tab shows that my second job is in state "aborted". Why? Who aborted it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/400855/+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 446246] Re: printing two files in a row makes wait for 'getting printer info'
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/446246 Title: printing two files in a row makes wait for 'getting printer info' Status in cups package in Ubuntu: Expired Bug description: Binary package hint: gedit when printing the first file prints immediately (without that printer status is checked). when printing a second file while the first is still printing then the printer status is checked and users have to wait till they can click to print the second file. this is different than in jaunty. ProblemType: Bug Architecture: i386 CheckboxSubmission: 71519a5e155620fc8a489e4b79619f6a CheckboxSystem: 2abf16d4e86c450ae46e3232dd0d1917 Date: Thu Oct 8 13:26:55 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gedit Package: gedit 2.28.0-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.39-generic SourcePackage: gedit Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/446246/+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 444752] Re: cant print at school
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/444752 Title: cant print at school Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups Bug in both Jaunty and Karmic CUPS version 1.3.9-17ubuntu3.2 (Jaunty) When i try to print at my school, the file isn't send to the printer I added the printer as an Internet Printing Protocol (https) with the following url: https://po.fontys.nl:443/printers//.printer When i go to cups 'webpage' (http://localhost:631/) i see the following error: Error: "Printing: Printer does not support IPP/1.1, trying IPP/1.0..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/444752/+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 1795439] Re: Triple 4K displays Intel HD620 max output of 8192x8192
*** This bug is a duplicate of bug 1714178 *** https://bugs.launchpad.net/bugs/1714178 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1714178, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1714178 Triple 4K monitor display failed (modesetting driver limited to 8192x8192) -- 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/1795439 Title: Triple 4K displays Intel HD620 max output of 8192x8192 Status in xorg package in Ubuntu: New Bug description: Brand new Shuttle PC direct from factory, Kaby Lake with Intel HD620 (which uses part of the 16GB RAM) with Bionic-Beaver-latest install last month (september 2018) for Cancer Research. The application is Libre Office 6.0.6.2 with very many linked graphics per sheet (nearly all columns used for some analyses). The Display Port plus HDMI1 plus HDMI2 outputs are all simultaneous 4K (unlike the Intel HD600) which is ideal for this type of research work (all three monitors are very large 42"+). One application across all three monitors to compare any detail. Else than a presentation luxury, it's where the whole work was headed since four years - like engineering, the size of the surface of a table. The Xorg interpretation that shows up in xrandr is default limit at 8192x8192 but the user doesn't know it. Bionic Beaver "settings" allows attempts to move and modify, illustrates the effort, finds then loses the third screen, crashes if the user persists and doesn't mention the limit. It works (and very well) only if two displays are left-right and one is placed underneath or over the top. It is possible to find that out by trial (and lots of error). According to askubuntu, the Intel gen 6 and up (or thereabouts) all support 16384x16384. One user confirms Ubuntu 18.04 offers that full boundary if the driver is Nvidia but not if it's Intel i915. The user also stated that this was "a known problem with ubuntu17 and gnome and fixed" but I can't find any reference about that, nor how to do it. A suggested source code "Intel side" patch was commented on this askubuntu page last week https://askubuntu.com/questions/1045664/kubuntu-18-7th-gen-intel-graphics-incorrect-max-resolution Intel sites suggest contacting Ubuntu and the Vendor first. So I post the bug here. [By the way, the other PC was on 18.04 Lubuntu with Libreoffice 6.10 and crashed or froze about ten times per day (Open GL or without). This new PC and the previous are now both with Bionic Beaver and Gnome and not once has either hesitated, not one single stoppage of any type. Absolutely amazing. Wonderful. The stability is crucial and I hope developers and Canonical receive praise - an important decision in favour of users. My suffering is ended. Thankyou]. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Mon Oct 1 16:50:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 620 [1297:4052] InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:c30a Logitech, Inc. iTouch Composite Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. DS77U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=9cdb8aeb-51e4-4cb5-95e7-b58572bf4dd7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.08 dmi.board.asset.tag: Default string dmi.board.name: FS77U dmi.board.vendor: Shuttle Inc.
[Touch-packages] [Bug 1775068] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1775068 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
** Also affects: libappindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver Status in glib2.0 package in Ubuntu: Confirmed Status in libappindicator package in Ubuntu: New Bug description: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+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 1775068] Re: Volume control not working Dell XPS 27 (7760)
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
** Changed in: ubuntu-themes (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ubuntu-themes
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Fix Committed
Status in ubuntu-themes package in Ubuntu:
Fix Committed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+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 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection
Oh. Except comment #13 says not. ** Changed in: canonical-devices-system-image Status: Fix Released => Confirmed ** Changed in: bluez (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1527354 Title: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: While debugging some re-factoring work on the ofono upower plugin, I noticed that I wasn't able to answer or terminate calls using my Jawbone ERA headset. I bought this headset last year, and although it's an older model, it's spec sheet states that it supports HSP 1.1, and HFP 1.5. I can pair the device with my krillin, and it properly auto connects ( note, this seems to work better than my iPhone ). In-call audio works for both incoming and outgoing calls, however I get no ringtone in the headset and as mentioned above, I can't answer or terminate the call. I've verified on my iPhone6, that the headset works. In addition to a ringtone in the earpiece, the headset also announces the incoming phone number. From looking at the ofono debug output, I'm never seeing a new HFP connection occur. I noticed as the upower plugin uses a foreach_atom (HFP) style call to update the battery indicators on all attached HFP devices. I've tested this extensively on krillin, running rc-proposed: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 205 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-16 17:53:19 version version: 205 version ubuntu: 20151216 version device: 20151204-2254a36 version custom: 2015--36-46-vivid I've also tested on mako, rc-proposed ( #317 ). For reference here's the versions of bluez, ofono, and PulseAudio on the device: bluez 5.36-0ubuntu2~overlay1 ofono 1.17.bzr6908+15.04.20151203-0ubuntu1~awe3 pulseaudio1:6.0-0ubuntu9.11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+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 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection
I assume this was released... https://code.launchpad.net/~bluetooth/bluez/new-rel-5-37-plus-touch- xenial-sync/+merge/283734 ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Released ** Changed in: canonical-devices-system-image Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1527354 Title: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: While debugging some re-factoring work on the ofono upower plugin, I noticed that I wasn't able to answer or terminate calls using my Jawbone ERA headset. I bought this headset last year, and although it's an older model, it's spec sheet states that it supports HSP 1.1, and HFP 1.5. I can pair the device with my krillin, and it properly auto connects ( note, this seems to work better than my iPhone ). In-call audio works for both incoming and outgoing calls, however I get no ringtone in the headset and as mentioned above, I can't answer or terminate the call. I've verified on my iPhone6, that the headset works. In addition to a ringtone in the earpiece, the headset also announces the incoming phone number. From looking at the ofono debug output, I'm never seeing a new HFP connection occur. I noticed as the upower plugin uses a foreach_atom (HFP) style call to update the battery indicators on all attached HFP devices. I've tested this extensively on krillin, running rc-proposed: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 205 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-16 17:53:19 version version: 205 version ubuntu: 20151216 version device: 20151204-2254a36 version custom: 2015--36-46-vivid I've also tested on mako, rc-proposed ( #317 ). For reference here's the versions of bluez, ofono, and PulseAudio on the device: bluez 5.36-0ubuntu2~overlay1 ofono 1.17.bzr6908+15.04.20151203-0ubuntu1~awe3 pulseaudio1:6.0-0ubuntu9.11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+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 1795464] Re: Intermittent black screen
Hello, you will probably need to contact whoever owns the repository LP- PPA-oibaf-graphics-drivers that provided you with your drivers. Thanks -- 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/1795464 Title: Intermittent black screen Status in xorg package in Ubuntu: New Bug description: On occasion the screen will go black, and also gnome will reset ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.16.0-041600-lowlatency x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 09:34:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1657] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-03-10 (569 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600-lowlatency root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume radeon.modeset=1 intel_idle.max_cstate=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1657 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn1657:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124461620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.94+git1809210630.4ec31f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1809281930.cb863d~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809281930.cb863d~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0+git1809261933.80514b~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1809061934.25c9a2~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b xserver.bootTime: Wed Sep 19 12:05:29 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1795464/+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 1795464] Re: Intermittent black screen
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1795464 Title: Intermittent black screen Status in xorg package in Ubuntu: New Bug description: On occasion the screen will go black, and also gnome will reset ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.16.0-041600-lowlatency x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 09:34:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1657] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-03-10 (569 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600-lowlatency root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume radeon.modeset=1 intel_idle.max_cstate=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1657 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn1657:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124461620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.94+git1809210630.4ec31f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1809281930.cb863d~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809281930.cb863d~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0+git1809261933.80514b~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1809061934.25c9a2~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b xserver.bootTime: Wed Sep 19 12:05:29 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1795464/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
This is not reproducible with netplan in an Ubuntu 18.04 container (on an Ubuntu cosmic host). With the following netplan config: $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: false bridges: br0: interfaces: [eth0] dhcp4: true addresses: ["fe81::32a5:bc5f:287f:8db8/64"] $ The container network comes up with: $ ip addr show dev br0 2: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether da:af:7e:76:48:8a brd ff:ff:ff:ff:ff:ff inet 10.141.225.180/24 brd 10.141.225.255 scope global dynamic br0 valid_lft 3341sec preferred_lft 3341sec inet6 fd42:c560:e275:f583:d8af:7eff:fe76:488a/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 3340sec preferred_lft 3340sec inet6 fe81::32a5:bc5f:287f:8db8/64 scope link valid_lft forever preferred_lft forever inet6 fe80::d8af:7eff:fe76:488a/64 scope link valid_lft forever preferred_lft forever $ As NetworkManager is not the supported network renderer for Ubuntu Server, please provide a reproducer for this using netplan and systemd- networkd. ** Package changed: dhcpcd (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: New Status in network-manager package in Ubuntu: Incomplete Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog
[Touch-packages] [Bug 1794478] [NEW] Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
You have been subscribed to a public bug: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto >From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! ** Affects: ubuntu-z-systems Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Incomplete ** Tags: architecture-s39064 bugnameltc-171765 severity-high targetmilestone-inin1804 -- Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it https://bugs.launchpad.net/bugs/1794478 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- 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 1795465] Re: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: console-setup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1795465 Title: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in console-setup package in Ubuntu: Invalid Bug description: Happened during installation, at the first update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup-linux 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Oct 1 18:37:10 2018 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-10-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1795465/+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 1795307] Re: package util-linux 2.27.1-6ubuntu3.6 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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1795307 Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: The procedure is too complicated for me. I do not know what to say or what to do Thanks for your help Claude ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.6 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Oct 1 09:12:03 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-30 (792 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1795307/+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 1795307] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello, it looks like your torque-scheduler isn't happy. I hope this helps you address your issue. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1795307 Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: The procedure is too complicated for me. I do not know what to say or what to do Thanks for your help Claude ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.6 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Oct 1 09:12:03 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-30 (792 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1795307/+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 1795307] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1795307 Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: The procedure is too complicated for me. I do not know what to say or what to do Thanks for your help Claude ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.6 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Oct 1 09:12:03 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-30 (792 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1795307/+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 1202754] Re: update-manager crashed with SystemExit in exit(): 0
** No longer affects: update-manager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-update-manager in Ubuntu. https://bugs.launchpad.net/bugs/1202754 Title: update-manager crashed with SystemExit in exit(): 0 Status in Ubuntu Kylin: Fix Released Status in click-update-manager package in Ubuntu: Fix Released Bug description: Errors bucket https://errors.ubuntu.com/bucket/?id=/usr/bin/update-manager:SystemExit:commit:_inline_callbacks:_show_transaction:_inline_callbacks:commit:_action_done:exit I was going to check for updates, but the Update-Manager has closed itself. ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: update-manager 1:0.189 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Thu Jul 18 20:46:05 2013 ExecutablePath: /usr/bin/update-manager InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']SourcePackage: update-manager Title: update-manager crashed with SystemExit in exit(): 0 UpgradeStatus: Upgraded to saucy on 2013-03-21 (118 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1202754/+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 1795242] Re: Digicert certificate is not included
This certificate does appear to be installed by default in the ca- certificates package: $ dpkg -L ca-certificates | grep DigiCert /usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_CA.crt /usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_G2.crt /usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_G3.crt /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_CA.crt /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_G2.crt /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_G3.crt /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt /usr/share/ca-certificates/mozilla/DigiCert_Trusted_Root_G4.crt $ sha256sum /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt d98f681c3a7dce812b90bf7c68046827f3bf5607357f1e4918c5dc813b359bf1 /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt $ ls -l /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt -rw-r--r-- 1 root root 1367 Apr 9 16:43 /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt $ ls -l /etc/ssl/certs/DigiCert*EV* lrwxrwxrwx 1 root root 73 Oct 17 2012 /etc/ssl/certs/DigiCert_High_Assurance_EV_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt Does this file exist on your system? Does this symlink exist on your system? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1795242 Title: Digicert certificate is not included Status in ca-certificates package in Ubuntu: Incomplete Bug description: The "DigiCert High Assurance EV Root CA" certificate is missing, which means that the system does not trust web sites that are using SSL certificates signed by that root. An example is a popular website in the Netherlands https://marktplaats.nl. The result is that no resources other that the text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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 1795242] Re: Digicert certificate is not included
** Changed in: ca-certificates (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1795242 Title: Digicert certificate is not included Status in ca-certificates package in Ubuntu: Incomplete Bug description: The "DigiCert High Assurance EV Root CA" certificate is missing, which means that the system does not trust web sites that are using SSL certificates signed by that root. An example is a popular website in the Netherlands https://marktplaats.nl. The result is that no resources other that the text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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 1793222] Re: Mousepad doesn't take input after canceled save dialog
Indeed. I took some hours to try it myself on a fresh installation. The bug didn't appear. I will try to find out more about the environment and post infos as soon as I have them. Maybe it's something that only happens through the upgrade... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1793222 Title: Mousepad doesn't take input after canceled save dialog Status in ibus package in Ubuntu: New Bug description: 1 Open Mousepad 2 Write something 3 Ctrl+S for save -> dialog opens 4 Exit dialog with ESC -> Mousepad will not take any keyboard input anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mousepad 0.4.0-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 19 07:17:27 2018 InstallationDate: Installed on 2018-02-12 (218 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: mousepad UpgradeStatus: Upgraded to bionic on 2018-08-25 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1793222/+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 1793550] Re: tracker library needs ontology files from tracker binary package
** Changed in: nautilus (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1793550 Title: tracker library needs ontology files from tracker binary package Status in nautilus package in Ubuntu: Triaged Status in tracker package in Ubuntu: Triaged Status in tracker package in Debian: Unknown Bug description: See the Debian bug for more details. The tracker 2.1.4 libraries will exit with an error, basically crashing the app if they can't find /usr/share/tracker/domain- ontologies/default.rule which is currently provided by the tracker binary package. The most obvious consequence is this means that nautilus won't run if tracker is not installed. But the tracker binary package isn't yet in main. The MIR is LP: #1770877 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793550/+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 1756006] Re: FFe: Support suspend-then-hibernate
Try d-feet as root. I think I recalled seeing this too. -- 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/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1756006] Re: FFe: Support suspend-then-hibernate
I used d-feet to Execute org.freedesktop.login1 org.freedesktop.login1.Manager CanSuspendThenHibernate If my swapfile was too small, I got the response 'na'. When I used a bigger swapfile, I got the response 'no'. -- 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/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1793550] Re: tracker library needs ontology files from tracker binary package
** Changed in: nautilus (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1793550 Title: tracker library needs ontology files from tracker binary package Status in nautilus package in Ubuntu: Invalid Status in tracker package in Ubuntu: Triaged Status in tracker package in Debian: Unknown Bug description: See the Debian bug for more details. The tracker 2.1.4 libraries will exit with an error, basically crashing the app if they can't find /usr/share/tracker/domain- ontologies/default.rule which is currently provided by the tracker binary package. The most obvious consequence is this means that nautilus won't run if tracker is not installed. But the tracker binary package isn't yet in main. The MIR is LP: #1770877 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793550/+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 1756006] Re: FFe: Support suspend-then-hibernate
When I did those PR upstream I did it with a swapfile actually on Ubuntu. The key comes down to how initramfs-tools hands off the offsets. It's kinda a jumbled mess though. I started a discussion here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950 but it got stalled and I got busy with other stuff and didn't resume it. ** Bug watch added: Debian Bug tracker #890950 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950 -- 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/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1756006] Re: FFe: Support suspend-then-hibernate
sufficiently large swapfile should be enough, as systemd has support to hibernate to a file offset. However, none-the-less, I did not manage to resume off that myself yet. -- 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/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Bug is also happening on 18.10 -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1756006] Re: FFe: Support suspend-then-hibernate
Ubuntu 18.10 has this feature as part of GNOME 3.30. There are some complaints though: https://lwn.net/Articles/764841/ https://bugs.debian.org/908930 On the other hand, Simon's comment on the Debian bug indicates that feature won't work if the system uses a swap file which Ubuntu 18.04 LTS and newer does by default. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Triaged => Fix Released ** Also affects: gnome-settings-daemon (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-settings-daemon (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-settings-daemon (Ubuntu Bionic) Importance: Undecided => Low ** No longer affects: systemd (Ubuntu Bionic) ** Bug watch added: Debian Bug tracker #908930 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908930 -- 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/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1761003] Re: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS
Bug is also happening 18.10 -- 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/1761003 Title: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Hello, since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the dual boot Windows 10 environment it is still working with the same certificates. It is a hidden network, adding it by "connect to a hidden network" entering SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate password. Tried a lot not getting it working. The password entry dialog for the network is always popping up upon connection trials. The password is for sure the correct one, checked it very often. If I'm able to I'll attach a syslog and kern.log of error occurense. Thanks for investigation and inputs. Best regards Kitsab ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 3 23:52:23 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-02-14 (1144 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1761003/+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 1781169] Re: frontend locking
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.28 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-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/1781169 Title: frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in dpkg source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in dpkg source package in Bionic: New Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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 1698159] Please test proposed package
Hello Ian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.28 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case] Make sure that linux-cloud-tools for protected kernels are listed in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Regression Potential] some linux-cloud-tools will linger around, so it takes more space. [Other info] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted] modified.conffile..etc.update-motd.d.98-reboot-required: [deleted] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+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 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
Thanks! Would it be maybe possible to actually check if the cloud-tools packages aren't auto-removed by unattended-upgrades as well besides just looking at the APT::NeverAutoRemove rules? ** Changed in: apt (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case] Make sure that linux-cloud-tools for protected kernels are listed in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Regression Potential] some linux-cloud-tools will linger around, so it takes more space. [Other info] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted] modified.conffile..etc.update-motd.d.98-reboot-required: [deleted] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+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 1794053] Re: pkgCacheFile unlocks in destructor even if it did not acquire lock
Hello Julian, or anyone else affected,
Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.28 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: apt (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Tags added: verification-needed-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/1794053
Title:
pkgCacheFile unlocks in destructor even if it did not acquire lock
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Trusty:
Triaged
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Cosmic:
Fix Released
Bug description:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly
breaks ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens
a cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That
said, any potential regression should be easily noticable, as it would
be a case of not unlocking where we were unlocking before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+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 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
** Description changed: - When running kernel version 4.4.0-78 (for example) and the unattended- - upgrade packages installs a new kernel 4.4.0-79 (for example) the linux- - cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are - removed by the Remove-Unused-Dependencies rule, because unlike "normal" - kernel packages they are not excluded by /etc/apt/apt.conf.d - /01autoremove-kernels. + [Impact] + When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. + + [Test case] + + Make sure that linux-cloud-tools for protected kernels are listed in + APT::NeverAutoRemove, for example, on cosmic: + +"^linux-cloud-tools-4\.17\.0-9-generic$"; +"^linux-cloud-tools-4\.18\.0-7-generic$"; + + Those are in 01autoremove-kernels + + [Regression Potential] + some linux-cloud-tools will linger around, so it takes more space. + + [Other info] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted] modified.conffile..etc.update-motd.d.98-reboot-required: [deleted] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64 -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case] Make sure that linux-cloud-tools for protected kernels are listed in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Regression Potential] some linux-cloud-tools will linger around, so it takes more space. [Other info] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
[Touch-packages] [Bug 1787120] Re: apt show fails to show large records
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.28 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: apt (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-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/1787120 Title: apt show fails to show large records Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt package in Debian: Confirmed Bug description: [Impact] apt show can't show records that are larger than 32 KB, e.g. records with long lists of provides [Test case] A test case is provided in autopkgtest, hence validates automatically. See https://salsa.debian.org/apt-team/apt/commit/409ceec9ed30cbebd8ece1ef7ce667ab5a32f9df for details. [Other info] This is a duplicate of Debian bug #905527. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+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 1794957] Re: pipelining on archive.u.c aborts after 101 packages
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.28 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: apt (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags added: verification-needed-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/1794957 Title: pipelining on archive.u.c aborts after 101 packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough) * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+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 1795407] Re: python-apt frontend locking
Hello Julian, or anyone else affected, Accepted python-apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python- apt/1.1.0~beta1ubuntu0.16.04.3 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: python-apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package linux - 4.18.0-8.9 --- linux (4.18.0-8.9) cosmic; urgency=medium * linux: 4.18.0-8.9 -proposed tracker (LP: #1791663) * Cosmic update to v4.18.7 stable release (LP: #1791660) - rcu: Make expedited GPs handle CPU 0 being offline - net: 6lowpan: fix reserved space for single frames - net: mac802154: tx: expand tailroom if necessary - 9p/net: Fix zero-copy path in the 9p virtio transport - spi: davinci: fix a NULL pointer dereference - spi: pxa2xx: Add support for Intel Ice Lake - spi: spi-fsl-dspi: Fix imprecise abort on VF500 during probe - spi: cadence: Change usleep_range() to udelay(), for atomic context - mmc: block: Fix unsupported parallel dispatch of requests - mmc: renesas_sdhi_internal_dmac: mask DMAC interrupts - mmc: renesas_sdhi_internal_dmac: fix #define RST_RESERVED_BITS - readahead: stricter check for bdi io_pages - block: fix infinite loop if the device loses discard capability - block: blk_init_allocated_queue() set q->fq as NULL in the fail case - block: really disable runtime-pm for blk-mq - blkcg: Introduce blkg_root_lookup() - block: Introduce blk_exit_queue() - block: Ensure that a request queue is dissociated from the cgroup controller - apparmor: fix bad debug check in apparmor_secid_to_secctx() - dma-buf: Move BUG_ON from _add_shared_fence to _add_shared_inplace - libertas: fix suspend and resume for SDIO connected cards - media: Revert "[media] tvp5150: fix pad format frame height" - mailbox: xgene-slimpro: Fix potential NULL pointer dereference - Replace magic for trusting the secondary keyring with #define - Fix kexec forbidding kernels signed with keys in the secondary keyring to boot - powerpc/fadump: handle crash memory ranges array index overflow - powerpc/64s: Fix page table fragment refcount race vs speculative references - powerpc/pseries: Fix endianness while restoring of r3 in MCE handler. - powerpc/pkeys: Give all threads control of their key permissions - powerpc/pkeys: Deny read/write/execute by default - powerpc/pkeys: key allocation/deallocation must not change pkey registers - powerpc/pkeys: Save the pkey registers before fork - powerpc/pkeys: Fix calculation of total pkeys. - powerpc/pkeys: Preallocate execute-only key - powerpc/nohash: fix pte_access_permitted() - powerpc64/ftrace: Include ftrace.h needed for enable/disable calls - powerpc/powernv/pci: Work around races in PCI bridge enabling - cxl: Fix wrong comparison in cxl_adapter_context_get() - IB/mlx5: Honor cnt_set_id_valid flag instead of set_id - IB/mlx5: Fix leaking stack memory to userspace - IB/srpt: Fix srpt_cm_req_recv() error path (1/2) - IB/srpt: Fix srpt_cm_req_recv() error path (2/2) - IB/srpt: Support HCAs with more than two ports - overflow.h: Add arithmetic shift helper - RDMA/mlx5: Fix shift overflow in mlx5_ib_create_wq - ib_srpt: Fix a use-after-free in srpt_close_ch() - ib_srpt: Fix a use-after-free in __srpt_close_all_ch() - RDMA/rxe: Set wqe->status correctly if an unexpected response is received - 9p: fix multiple NULL-pointer-dereferences - fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr failed - 9p/virtio: fix off-by-one error in sg list bounds check - net/9p/client.c: version pointer uninitialized - net/9p/trans_fd.c: fix race-condition by flushing workqueue before the kfree() - dm integrity: change 'suspending' variable from bool to int - dm thin: stop no_space_timeout worker when switching to write-mode - dm cache metadata: save in-core policy_hint_size to on-disk superblock - dm cache metadata: set dirty on all cache blocks after a crash - dm crypt: don't decrease device limits - dm writecache: fix a crash due to reading past end of dirty_bitmap - uart: fix race between uart_put_char() and uart_shutdown() - Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer() - Drivers: hv: vmbus: Reset the channel callback in vmbus_onoffer_rescind() - iio: sca3000: Fix missing return in switch - iio: ad9523: Fix displayed phase - iio: ad9523: Fix return value for ad952x_store() - extcon: Release locking when sending the notification of connector state - eventpoll.h: wrap casts in () properly - vmw_balloon: fix inflation of 64-bit GFNs - vmw_balloon: do not use 2MB without batching - vmw_balloon: VMCI_DOORBELL_SET does not check status - vmw_balloon: fix VMCI use when balloon built into kernel - rtc: omap: fix resource leak in registration error path - rtc: omap: fix potential crash on power off - tracing: Do not call start/stop() functions when tracing_on does not change - tracing/blktrace: Fix to allow setting same value - printk/tracing: Do not trace printk_nmi_enter() - livepatch:
[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
We would need some SRU information here. Since this is part of the xenial apt SRU, we'd need to have reliable testing steps for verification of the update. Thank you! -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case] Make sure that linux-cloud-tools for protected kernels are listed in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Regression Potential] some linux-cloud-tools will linger around, so it takes more space. [Other info] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted] modified.conffile..etc.update-motd.d.98-reboot-required: [deleted] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+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 1762385] Re: dell_wmi: Unknown key codes
This bug was fixed in the package linux - 4.15.0-36.39
---
linux (4.15.0-36.39) bionic; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.15.0-35.38) bionic; urgency=medium
* linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
* device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
* L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has
too
much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
* CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
* CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
* Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
* Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
* Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
* Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
* CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
* Support Power Management for Thunderbolt Controller (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
* random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
* [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
* Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
response"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix comments for
hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for using wrong mask and
shift in hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for reset_level default
assignment probelm"
- Revert "UBUNTU: SAUCE: {topost} net: hns3:
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
This bug was fixed in the package linux - 4.15.0-36.39
---
linux (4.15.0-36.39) bionic; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.15.0-35.38) bionic; urgency=medium
* linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
* device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
* L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has
too
much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
* CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
* CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
* Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
* Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
* Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
* Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
* CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
* Support Power Management for Thunderbolt Controller (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
* random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
* [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
* Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
response"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix comments for
hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for using wrong mask and
shift in hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for reset_level default
assignment probelm"
- Revert "UBUNTU: SAUCE: {topost} net: hns3:
[Touch-packages] [Bug 1795407] Re: python-apt frontend locking
Hello Julian, or anyone else affected, Accepted python-apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-apt/1.6.3 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: python-apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: In Progress Status in python-apt source package in Bionic: Fix Committed Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1719612] Re: non-us keyboard layout not setup in initramfs
Hello, I have been having this issue for a while now... at least 5-years (using an azerty board). I have still use the encryption drive for security reasons... Today, when I type the password at boot time to decrypt the drive, I can't get access to it ? If I boot up with a with a USB version and type the same password to decrypt the connected drive it works fine? Anyone knows whazup? Thx ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1719612 Title: non-us keyboard layout not setup in initramfs Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Artful: Triaged Bug description: Description:Ubuntu Artful Aardvark (development branch) Release:17.10 In Artful the /etc/console/cached.kmap.gz file does not exists, in its place, it uses some files with more precise names susch as cached_UTF-8_del.kmap.gz. However the initramfs scripts still uses cached.kmap.gz . The consequence is that the keyboard layout remains US in the initramfs which is a problem for full encrypted installation when entering passphrase. Proposed solution is to make a symbolic link from cached_UTF-8_del.kmap.gz to cached.kmap.gz. Then the initramfs tools will find the /etc/console/cached.kmap.gz file and includes it in the initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1719612/+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 1795479] [NEW] ark does not save pdf from internal viewer
Public bug reported:
Open a zip file with ark
in ark settings choose preview the file with internal previewer.
Open a pdf file from the zip archive.
Save the file using "Save as by choosing a new directory (outside /tmp/)
The file is saved, but when the PDF previewer is closed, the file disappears.
an strace of the ark process shows
unlink("/home/elgaard/foo.pdf")
which is where the PDF was saved to.
I did have a similar problems years ago, and I am almost sure that I checked
the option "open the file with associated application" back then and suspect
that the setting was changed behind my back at a later update.
** Affects: shared-mime-info (Ubuntu)
Importance: Undecided
Status: New
** Tags: ark
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1795479
Title:
ark does not save pdf from internal viewer
Status in shared-mime-info package in Ubuntu:
New
Bug description:
Open a zip file with ark
in ark settings choose preview the file with internal previewer.
Open a pdf file from the zip archive.
Save the file using "Save as by choosing a new directory (outside
/tmp/)
The file is saved, but when the PDF previewer is closed, the file disappears.
an strace of the ark process shows
unlink("/home/elgaard/foo.pdf")
which is where the PDF was saved to.
I did have a similar problems years ago, and I am almost sure that I checked
the option "open the file with associated application" back then and suspect
that the setting was changed behind my back at a later update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1795479/+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 1787120] Re: apt show fails to show large records
As per commit message, this is basically 'fixed' in 1.7.x (in a rewrite of the same code that made the problem go away before getting reported). Marking it as 'Invalid' since I guess that's the most fitting way. ** Changed in: apt (Ubuntu) Status: New => Invalid ** Changed in: apt (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787120 Title: apt show fails to show large records Status in apt package in Ubuntu: Invalid Status in apt source package in Bionic: Fix Committed Status in apt package in Debian: Confirmed Bug description: [Impact] apt show can't show records that are larger than 32 KB, e.g. records with long lists of provides [Test case] A test case is provided in autopkgtest, hence validates automatically. See https://salsa.debian.org/apt-team/apt/commit/409ceec9ed30cbebd8ece1ef7ce667ab5a32f9df for details. [Other info] This is a duplicate of Debian bug #905527. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+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 1781169] Re: frontend locking
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.5 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: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1781169 Title: frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in dpkg source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in dpkg source package in Bionic: New Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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 1787120] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.5 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. -- 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/1787120 Title: apt show fails to show large records Status in apt package in Ubuntu: Invalid Status in apt source package in Bionic: Fix Committed Status in apt package in Debian: Confirmed Bug description: [Impact] apt show can't show records that are larger than 32 KB, e.g. records with long lists of provides [Test case] A test case is provided in autopkgtest, hence validates automatically. See https://salsa.debian.org/apt-team/apt/commit/409ceec9ed30cbebd8ece1ef7ce667ab5a32f9df for details. [Other info] This is a duplicate of Debian bug #905527. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+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 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package linux - 4.15.0-36.39
---
linux (4.15.0-36.39) bionic; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.15.0-35.38) bionic; urgency=medium
* linux: 4.15.0-35.38 -proposed tracker (LP: #1791719)
* device hotplug of vfio devices can lead to deadlock in vfio_pci_release
(LP: #1792099)
- SAUCE: vfio -- release device lock before userspace requests
* L1TF mitigation not effective in some CPU and RAM combinations
(LP: #1788563)
- x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit
- x86/speculation/l1tf: Fix off-by-one error when warning that system has
too
much RAM
- x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+
* CVE-2018-15594
- x86/paravirt: Fix spectre-v2 mitigations for paravirt guests
* CVE-2017-5715 (Spectre v2 s390x)
- KVM: s390: implement CPU model only facilities
- s390: detect etoken facility
- KVM: s390: add etoken support for guests
- s390/lib: use expoline for all bcr instructions
- s390: fix br_r1_trampoline for machines without exrl
- SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT
* Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state
disabled (performance) (LP: #1790602)
- cpuidle: powernv: Fix promotion from snooze if next state disabled
* Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636)
- powerpc: hard disable irqs in smp_send_stop loop
- powerpc: Fix deadlock with multiple calls to smp_send_stop
- powerpc: smp_send_stop do not offline stopped CPUs
- powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled
* Security fix: check if IOMMU page is contained in the pinned physical page
(LP: #1785675)
- vfio/spapr: Use IOMMU pageshift rather than pagesize
- KVM: PPC: Check if IOMMU page is contained in the pinned physical page
* Missing Intel GPU pci-id's (LP: #1789924)
- drm/i915/kbl: Add KBL GT2 sku
- drm/i915/whl: Introducing Whiskey Lake platform
- drm/i915/aml: Introducing Amber Lake platform
- drm/i915/cfl: Add a new CFL PCI ID.
* CVE-2018-15572
- x86/speculation: Protect against userspace-userspace spectreRSB
* Support Power Management for Thunderbolt Controller (LP: #1789358)
- thunderbolt: Handle NULL boot ACL entries properly
- thunderbolt: Notify userspace when boot_acl is changed
- thunderbolt: Use 64-bit DMA mask if supported by the platform
- thunderbolt: Do not unnecessarily call ICM get route
- thunderbolt: No need to take tb->lock in domain suspend/complete
- thunderbolt: Use correct ICM commands in system suspend
- thunderbolt: Add support for runtime PM
* random oopses on s390 systems using NVMe devices (LP: #1790480)
- s390/pci: fix out of bounds access during irq setup
* [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support
for arm64 using SMC firmware call to set a hardware chicken bit
(LP: #1787993) // CVE-2018-3639 (arm64)
- arm64: alternatives: Add dynamic patching feature
- KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state
- KVM: arm64: Avoid storing the vcpu pointer on the stack
- arm/arm64: smccc: Add SMCCC-specific return codes
- arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1
- arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2
- arm64: Add ARCH_WORKAROUND_2 probing
- arm64: Add 'ssbd' command-line option
- arm64: ssbd: Add global mitigation state accessor
- arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation
- arm64: ssbd: Restore mitigation status on CPU resume
- arm64: ssbd: Introduce thread flag to control userspace mitigation
- arm64: ssbd: Add prctl interface for per-thread mitigation
- arm64: KVM: Add HYP per-cpu accessors
- arm64: KVM: Add ARCH_WORKAROUND_2 support for guests
- arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
- arm64: KVM: Add ARCH_WORKAROUND_2 discovery through ARCH_FEATURES_FUNC_ID
- [Config] ARM64_SSBD=y
* Reconcile hns3 SAUCE patches with upstream (LP: #1787477)
- Revert "UBUNTU: SAUCE: net: hns3: Optimize PF CMDQ interrupt switching
process"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown
message"
- Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox cannot receiving PF
response"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix comments for
hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for using wrong mask and
shift in hclge_get_ring_chain_from_mbx"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: fix for reset_level default
assignment probelm"
- Revert "UBUNTU: SAUCE: {topost} net: hns3:
[Touch-packages] [Bug 1794053] Re: pkgCacheFile unlocks in destructor even if it did not acquire lock
Hello Julian, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.5 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: apt (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794053
Title:
pkgCacheFile unlocks in destructor even if it did not acquire lock
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Trusty:
Triaged
Status in apt source package in Xenial:
Triaged
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Cosmic:
Fix Released
Bug description:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly
breaks ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens
a cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That
said, any potential regression should be easily noticable, as it would
be a case of not unlocking where we were unlocking before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+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 1794957] Re: pipelining on archive.u.c aborts after 101 packages
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.5 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: apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1794957 Title: pipelining on archive.u.c aborts after 101 packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Fix Committed Bug description: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough) * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+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 1795465] Re: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1795465 Title: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in console-setup package in Ubuntu: New Bug description: Happened during installation, at the first update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup-linux 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Oct 1 18:37:10 2018 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-10-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1795465/+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 1795465] [NEW] package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Happened during installation, at the first update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup-linux 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Oct 1 18:37:10 2018 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-10-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1795465 Title: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in console-setup package in Ubuntu: New Bug description: Happened during installation, at the first update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup-linux 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Oct 1 18:37:10 2018 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-10-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup-linux 1.178ubuntu2.3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1795465/+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 1775068] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195374/+files/CurrentDmesg.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] Re: Volume control not working Dell XPS 27 (7760)
apport information ** Tags added: apport-collected bionic ** Description changed: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: trolinka 1610 F pulseaudio + /dev/snd/controlC1: trolinka 1610 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-06-02 (121 days ago) + InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: pulseaudio 1:11.1-1ubuntu7.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-34-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video + _MarkForUpload: True + dmi.bios.date: 07/13/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.4.0 + dmi.board.name: 0T12MX + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 13 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 7760 AIO + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195373/+files/AlsaInfo.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1535058] Re: applications close instantly when launched from the launcher or dash
@bozubuntu hey, thanks for the report, but this bug is for the discontinued unity8 desktop. I suggest you log a bug against ubuntu-desktop with as much information as you can supply: https://bugs.launchpad.net/~ubuntu-desktop exo-open is new to me, have you tried xdg-open? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1535058 Title: applications close instantly when launched from the launcher or dash Status in Canonical System Image: Fix Released Status in cgmanager package in Ubuntu: Incomplete Status in qtmir package in Ubuntu: Invalid Status in ubuntu-app-launch package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: xenial applications close instantly when launched from the launcher or dash but... if i launch the apps from a VT (for ex firefox using Xmir or gedit native --), the app loads ok. what close instantly means.. it opens the window and then it closes instantly in ~0.3s --- This has been traced to two causes: pam was not installed, it is now a dependency of ubuntu-app-launch or can be installed directly $ sudo apt-get install libpam-cgfs and cgmanager is not enabled by default on systems that were upgraded and not clean installs. To enable it $ sudo systemctl enable cgmanager To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1535058/+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 1775068] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195380/+files/CurrentDmesg.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195379/+files/AlsaInfo.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195377/+files/ProcEnviron.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195376/+files/ProcCpuinfoMinimal.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195375/+files/Dependencies.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195378/+files/PulseList.txt ** Description changed: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: trolinka 1610 F pulseaudio + /dev/snd/controlC1: trolinka 1610 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-06-02 (121 days ago) + InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: pulseaudio 1:11.1-1ubuntu7.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-34-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video + _MarkForUpload: True + dmi.bios.date: 07/13/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.4.0 + dmi.board.name: 0T12MX + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 13 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 7760 AIO + dmi.sys.vendor: Dell Inc. -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1775068] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195382/+files/ProcCpuinfoMinimal.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195381/+files/Dependencies.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195383/+files/ProcEnviron.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1775068] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195384/+files/PulseList.txt ** Description changed: - - Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. + Pressing vol up/vol down show OSD change up/down but volume all time is + at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: trolinka 1610 F pulseaudio - /dev/snd/controlC1: trolinka 1610 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: trolinka 1610 F pulseaudio + /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. - --- - ProblemType: Bug - ApportVersion: 2.20.9-0ubuntu7.4 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: trolinka 1610 F pulseaudio - /dev/snd/controlC1: trolinka 1610 F pulseaudio - CurrentDesktop: MATE - DistroRelease: Ubuntu 18.04 - InstallationDate: Installed on 2018-06-02 (121 days ago) - InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) - Package: pulseaudio 1:11.1-1ubuntu7.1 - PackageArchitecture: amd64 - ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 - Tags: bionic - Uname: Linux 4.15.0-34-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video - _MarkForUpload: True - dmi.bios.date: 07/13/2018 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 2.4.0 - dmi.board.name: 0T12MX - dmi.board.vendor: Dell Inc. - dmi.board.version: A00 - dmi.chassis.type: 13 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: - dmi.product.family: XPS - dmi.product.name: XPS 7760 AIO - dmi.sys.vendor: Dell Inc. + --- -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO
[Touch-packages] [Bug 1775068] Re: Volume control not working Dell XPS 27 (7760)
Hi, Volume slider works partialy. It's have 0% muted and "one next pixel" jump to about 90% volume. Slider works like 0-9092-94-96 -98-100% -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775068/+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 1795145] Re: Turn on background plugin by default (Ubuntu 18.10)
I'm unsubscribing ubuntu-sponsors since I uploaded this to the cosmic UNAPPROVED queue. A Release Team member will need to manually approve this upload. ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1795145 Title: Turn on background plugin by default (Ubuntu 18.10) Status in ubuntu-settings package in Ubuntu: Fix Committed Bug description: In https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu- settings/tree/debian/ubuntu-settings.gsettings-override#n139 we have, [org.gnome.settings-daemon.plugins.background:ubuntu] active = false which disables the plugin. Gnome-settings-daemon doesn't use that key anymore (They are auto started by desktop files), But unity-settings- daemon now requires it to be enabled by default due to recent changes in lightdm and u-s-d Lightdm now use AccountsService extension system for extended greeter information (like wallpaper) used by unity-greeter (https://github.com/CanonicalLtd/lightdm/commit/6015bce25f241e7580c03594d846769f8236232f) And unity-settings-daemon now depends on new AccountsService method of setting background file for unity greeter. (https://bazaar.launchpad.net/~unity-settings-daemon-team/unity- settings-daemon/trunk/revision/4179) How-to-reproduce: -- 1) First disable the background plugin if it is already enabled. gsettings set org.gnome.settings-daemon.plugins.sharing active false 2) Change the wallpaper from unity-control-center. 3) Log out. Unity-greeter should reflect the change of wallpaper. But it doesn't. 4) Re-enable the background plugin. gsettings set org.gnome.settings-daemon.plugins.sharing active true 5) Change the wallpaper again and then log out. Unity-greeter now reflects the change in wallpaper properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795145/+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 1793670] Re: Update libgtk-3-0 to 3.24.1
** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1793670 Title: Update libgtk-3-0 to 3.24.1 Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Merge from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1793670/+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 1795407] Re: python-apt frontend locking
** Changed in: python-apt (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: python-apt (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: In Progress Status in python-apt source package in Bionic: In Progress Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1795439] [NEW] Triple 4K displays Intel HD620 max output of 8192x8192
Public bug reported: Brand new Shuttle PC direct from factory, Kaby Lake with Intel HD620 (which uses part of the 16GB RAM) with Bionic-Beaver-latest install last month (september 2018) for Cancer Research. The application is Libre Office 6.0.6.2 with very many linked graphics per sheet (nearly all columns used for some analyses). The Display Port plus HDMI1 plus HDMI2 outputs are all simultaneous 4K (unlike the Intel HD600) which is ideal for this type of research work (all three monitors are very large 42"+). One application across all three monitors to compare any detail. Else than a presentation luxury, it's where the whole work was headed since four years - like engineering, the size of the surface of a table. The Xorg interpretation that shows up in xrandr is default limit at 8192x8192 but the user doesn't know it. Bionic Beaver "settings" allows attempts to move and modify, illustrates the effort, finds then loses the third screen, crashes if the user persists and doesn't mention the limit. It works (and very well) only if two displays are left-right and one is placed underneath or over the top. It is possible to find that out by trial (and lots of error). According to askubuntu, the Intel gen 6 and up (or thereabouts) all support 16384x16384. One user confirms Ubuntu 18.04 offers that full boundary if the driver is Nvidia but not if it's Intel i915. The user also stated that this was "a known problem with ubuntu17 and gnome and fixed" but I can't find any reference about that, nor how to do it. A suggested source code "Intel side" patch was commented on this askubuntu page last week https://askubuntu.com/questions/1045664/kubuntu-18-7th-gen-intel-graphics-incorrect-max-resolution Intel sites suggest contacting Ubuntu and the Vendor first. So I post the bug here. [By the way, the other PC was on 18.04 Lubuntu with Libreoffice 6.10 and crashed or froze about ten times per day (Open GL or without). This new PC and the previous are now both with Bionic Beaver and Gnome and not once has either hesitated, not one single stoppage of any type. Absolutely amazing. Wonderful. The stability is crucial and I hope developers and Canonical receive praise - an important decision in favour of users. My suffering is ended. Thankyou]. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Mon Oct 1 16:50:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 620 [1297:4052] InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:c30a Logitech, Inc. iTouch Composite Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. DS77U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=9cdb8aeb-51e4-4cb5-95e7-b58572bf4dd7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.08 dmi.board.asset.tag: Default string dmi.board.name: FS77U dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.08:bd03/12/2018:svnShuttleInc.:pnDS77U:pvrV1.0:rvnShuttleInc.:rnFS77U:rvr1.0:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: D dmi.product.name: DS77U dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** 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-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
I have updated the patch with required changes. Thanks.
** Patch added: "telepathy-purple.patch"
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/5195357/+files/telepathy-purple.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+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 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
Mh, not that I'm aware of, but also not having a full stacktrace doesn't help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver Status in glib2.0 package in Ubuntu: Confirmed Bug description: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+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 1708375] Re: Add support for purple-telegram (telepathy-haze)
I recommend changing these to be:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2/*.so mr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
owner @{HOME}/.telegram-purple/ rw,
owner @{HOME}/{,.purple/}telegram-purple/** rw,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+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 1770082] Re: systemd-networkd not renaming devices on boot
Sorry for being such a buzzkill, but it's still not working on my side :( = Reinstalled 18.04.1 server x64 from scratch in a clean VirtualBox VM. = # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic = Enabled -proposed repo and updated netplan.io = # dpkg -s netplan.io | grep Version Version: 0.40~18.04.1 Set a very basic network configuration # cat /etc/netplan/01-netcfg.yaml network: version: 2 renderer: networkd ethernets: id0: match: macaddress: 08:00:27:6b:d8:91 set-name: eth_lan addresses: [ 192.168.1.10/24 ] gateway4: 192.168.1.1 nameservers: addresses: [ 8.8.4.4 ] After reboot the interface is renamed but IP address is not set # ifconfig -a eth_lan: flags=4098 mtu 1500 ether 08:00:27:6b:d8:91 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 ... === After manually running "netplan apply" (after boot) things go even worst: network interface is renamed again to "id0" === # netplan apply # ifconfig -a id0: flags=4098 mtu 1500 ether 08:00:27:6b:d8:91 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 ... ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic ** Tags removed: verification-needed -- 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/1770082 Title: systemd-networkd not renaming devices on boot Status in netplan: Fix Released Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in nplan source package in Xenial: Fix Released Status in netplan.io source package in Bionic: Fix Committed Bug description: [Impact] Systems relying on renaming network interfaces at boot and when 'netplan apply' is run. [Test case] - Write a new netplan YAML (adjusting for current system as necessary): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: myif0 - Run 'netplan apply' - Verify that the device is correctly renamed to 'myif0'. - Reboot. - Make sure the device is correctly renamed to 'myif0'. [Regression potential] Changes in rename logic to add udev rules may otherwise impact applying different settings to the network interfaces. Changes in settings on network interfaces, missing parameters (especially on bonds, bridges) should be investigated as potential regressions. Other failures to apply network settings might also happen if there's a race between applying renames via the udev rules, and using the new names to apply configuration changes to the interfaces. === systemd issue === Renaming devices doesn't seem to work. If I disable all other network configuration and create /etc/systemd/network/10-network.link with: [Match] MACAddress=52:54:00:c1:c9:bb [Link] Name=myiface3 I expect this to cause the device with that MAC address to be renamed to myiface3. However, when I reboot, I instead see: $ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff The device is not renamed. This link file is pretty much identical to Example 2 in https://www.freedesktop.org/software/systemd/man/systemd.link.html. The renaming does work if I boot with net.ifnames=0, and oddly, it also works if I unbind the device and rebind it as netplan apply does. No setting of NamePolicy seems to help. === Original Bug == 'set-name:' doesn't change the name of a network interface on boot, it only works when you do netplan apply. Say I take this
[Touch-packages] [Bug 1795407] Re: python-apt frontend locking
** Description changed: [Impact] - foo + Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: + + (1) The archives lock was only taken for a short time, when it should + have been kept for the duration of an installation, as otherwise debs + could disappear from archives/ while the install is running. + + (2) There was no lock handling at all. Tools essentially acquire the + lock, and then release it before commit(). + + The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage + both the frontend and the normal lock, and allows code to call + apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() + around dpkg invocations to release the inner lock. + + Cache.commit() takes care of locking itself now. It releases the inner + lock as needed for dpkg invocations. It also now requires + apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] - bar + 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. + 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released + 3. Observe that the archive lock is not released until the last dpkg run + + The locking behavior can be observed via strace. [Regression potential] - baz + The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. + + The archive lock done by commit()/fetch_archives() in apt.Cache() is now + hold as long as the fetcher object exists though (as it uses the + fetcher's get_lock method), which might cause unexpected behavior in + apps not expecting that. + + The lists/ lock is unaffected by the changes, so there should not be any + regressions when it comes to updating index files. ** Description changed: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. + + [Other info] + CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status
[Touch-packages] [Bug 1792356] Re: [ffe] Update to 1.4.3
This was uploaded to the queue, and I reviewed it there. It's in now. ** Changed in: colord (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1792356 Title: [ffe] Update to 1.4.3 Status in colord package in Ubuntu: Fix Released Bug description: Debian got the new version, it would be nice to have in cosmic now. Although the upgrade from our current 1.3.3 to 1.4.3 might seem a big jump, colord upstream does not see a lot of development activity; most changes here are bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1792356/+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 1708375] Re: Add support for purple-telegram (telepathy-haze)
Updated the patch as quilt patch
** Patch added: "telepathy-purple.patch"
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/5195339/+files/telepathy-purple.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+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 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
Marco, you did that SRU. Did you see/hear about other similar problems? Any idea what the issue could be? ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver Status in glib2.0 package in Ubuntu: Confirmed Bug description: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+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 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
The bug is not easy to work on without a reproducer or a debug backtrace. Can you share the binary you are using which is hitting the issue? If not could you at least get a debug backtrace (install the debug symbols for libappindicator and libglib2.0-0, see https://wiki.ubuntu.com/DebuggingProgramCrash for detailled instructions on how to do that) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver Status in glib2.0 package in Ubuntu: Confirmed Bug description: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+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 1795412] Re: Allow read access to /usr/share/unity/themes/ for telepathy-haze
telepathy-haze-fix.patch ** Patch added: "tellepathy-haze-fix.patch" https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1795412/+attachment/5195338/+files/tellepathy-haze-fix.patch ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1795412 Title: Allow read access to /usr/share/unity/themes/ for telepathy-haze Status in telepathy-mission-control-5 package in Ubuntu: Confirmed Bug description: When You open empathy with a active telepathy-haze connection, syslog reports, Oct 1 03:05:57 cosmic-dev kernel: [ 192.196337] audit: type=1400 audit(1538343357.649:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-*" name="/usr/share/unity/themes/" pid=1696 comm="telepathy-haze" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 though it is not critical, it doesn't hurt give telepathy-haze read access to that folder. I can't open merge request since I can't find lp:telepathy-mission- control-5, I am attaching a quilt patch here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1795412/+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 1795412] [NEW] Allow read access to /usr/share/unity/themes/ for telepathy-haze
Public bug reported: When You open empathy with a active telepathy-haze connection, syslog reports, Oct 1 03:05:57 cosmic-dev kernel: [ 192.196337] audit: type=1400 audit(1538343357.649:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-*" name="/usr/share/unity/themes/" pid=1696 comm="telepathy-haze" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 though it is not critical, it doesn't hurt give telepathy-haze read access to that folder. I can't open merge request since I can't find lp:telepathy-mission- control-5, I am attaching a quilt patch here. ** Affects: telepathy-mission-control-5 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1795412 Title: Allow read access to /usr/share/unity/themes/ for telepathy-haze Status in telepathy-mission-control-5 package in Ubuntu: Confirmed Bug description: When You open empathy with a active telepathy-haze connection, syslog reports, Oct 1 03:05:57 cosmic-dev kernel: [ 192.196337] audit: type=1400 audit(1538343357.649:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-*" name="/usr/share/unity/themes/" pid=1696 comm="telepathy-haze" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 though it is not critical, it doesn't hurt give telepathy-haze read access to that folder. I can't open merge request since I can't find lp:telepathy-mission- control-5, I am attaching a quilt patch here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1795412/+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 1795410] Re: cannot bring up window menu via keybinding (alt-space or otherwise)
** Package changed: ubuntu-meta (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795410 Title: cannot bring up window menu via keybinding (alt-space or otherwise) Status in mutter package in Ubuntu: New Bug description: I'm accustomed to hitting 'alt-space' to 'Activate the window menu' where there are options like 'Always on Top' or 'Always on visible workspace'. After an upgrade today I can no longer bring up that menu. Alt-space simply does nothing. Configuring the keyboard shortcut in gnome-control-center to another shortcut has no effect. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-desktop 1.424 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 10:13:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1166 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795410/+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 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
Thanks a lot Vishnu! Since it's not a security udpate issue I'll notice and add the desktop team to handle with this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver Status in glib2.0 package in Ubuntu: Confirmed Bug description: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+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 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver Status in glib2.0 package in Ubuntu: Confirmed Bug description: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+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 1795410] [NEW] cannot bring up window menu via keybinding (alt-space or otherwise)
Public bug reported: I'm accustomed to hitting 'alt-space' to 'Activate the window menu' where there are options like 'Always on Top' or 'Always on visible workspace'. After an upgrade today I can no longer bring up that menu. Alt-space simply does nothing. Configuring the keyboard shortcut in gnome-control-center to another shortcut has no effect. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-desktop 1.424 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 10:13:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1166 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795410 Title: cannot bring up window menu via keybinding (alt-space or otherwise) Status in mutter package in Ubuntu: New Bug description: I'm accustomed to hitting 'alt-space' to 'Activate the window menu' where there are options like 'Always on Top' or 'Always on visible workspace'. After an upgrade today I can no longer bring up that menu. Alt-space simply does nothing. Configuring the keyboard shortcut in gnome-control-center to another shortcut has no effect. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-desktop 1.424 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 10:13:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1166 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795410/+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 1764533] Re: package ca-certificates 20180409 failed to install/upgrade: Unterprozess installed ca-certificates package post-installation script gab den Fehler-Ausgangsstatus 24
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ca-certificates (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764533 Title: package ca-certificates 20180409 failed to install/upgrade: Unterprozess installed ca-certificates package post-installation script gab den Fehler-Ausgangsstatus 24 zurück Status in ca-certificates package in Ubuntu: Confirmed Bug description: Hello, after apt-get update && apt-get upgrade -y an error appeared with CA- certificates. While apt-get upgrade process there was a terminal entry which certs I trust and I've got to select them manually (all mozilla certs). Mozilla Firefox is working anyway. Best regards Kitsab ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Mon Apr 16 23:10:31 2018 ErrorMessage: Unterprozess installed ca-certificates package post-installation script gab den Fehler-Ausgangsstatus 24 zurück InstallationDate: Installed on 2015-02-14 (1157 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: Unterprozess installed ca-certificates package post-installation script gab den Fehler-Ausgangsstatus 24 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1764533/+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 1795407] [NEW] python-apt frontend locking
Public bug reported: [Impact] foo [Test case] bar [Regression potential] baz ** Affects: python-apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Status: New => Fix Released ** Changed in: python-apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: python-apt (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Triaged Status in python-apt source package in Bionic: Triaged Bug description: [Impact] foo [Test case] bar [Regression potential] baz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
@xnox, can you SRU to xenial please. ** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Won't Fix -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in debhelper source package in Xenial: Won't Fix Status in rsyslog source package in Xenial: Invalid Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: Won't Fix Status in rsyslog source package in Artful: Invalid Status in systemd source package in Artful: Won't Fix Status in debhelper source package in Bionic: Won't Fix Status in rsyslog source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 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 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tree Reading state
[Touch-packages] [Bug 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver
We tried with the package which was given above (AMD64 - https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3389-deletedppa/+build/15310024) , and still we facing the same issue and same gdb back trace as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795230 Title: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver Status in glib2.0 package in Ubuntu: New Bug description: Our product is using LibAppIndicator Please find the dependency tree below for libappindicator, it is using libglib libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1 libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7 libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 Our product is crashing after upgrading libglib to the latest version glib2.0 2.56.2 released on 19-Sep-2018. https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230/+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 1781169] Re: frontend locking
** No longer affects: dpkg (Ubuntu) -- 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/1781169 Title: frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in dpkg source package in Xenial: New Status in apt source package in Bionic: In Progress Status in dpkg source package in Bionic: New Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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 1778844] Re: nvme multipath does not report path relationships
** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in makedumpfile source package in Cosmic: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 0e4f79d56818 [ 73.058099] GPR20: 0e4f79d8d5d8
