[Touch-packages] [Bug 1854689] Re: BlueZ 5.52 release
** Changed in: bluez (Ubuntu) Status: In Progress => Won't Fix ** Changed in: bluez (Ubuntu) Status: Won't Fix => Fix Committed -- 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/1854689 Title: BlueZ 5.52 release Status in bluez package in Ubuntu: Fix Committed Bug description: BlueZ 5.52 release: http://www.bluez.org/release-of-bluez-5-52/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1
@Gord, is your issue with libsnapd-glib or with the fact that the lib recommends snapd and that recommends are pulled in by default? The library as Daniel pointed out shouldn't be an issue, it's small and not doing anything if the service is not there. ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - pulseaudio now depends on libsnapd-glib1 + pulseaudio now depends on libsnapd-glib1 which recommends snapd -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
AFAICT the addition of snapd as an indirect recommends was an unintended consequence of the update, so I'm tagging this regression-update. ** Tags added: regression-update -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
Note also that it's only a recommends, so while the problem is being worked on you can install the SRU using --no-install-recommends as a workaround (or remove snapd again after update) -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
The Xenial/Bionic SRUs have been removed until the Recommends on snapd gets lowered to a Suggest -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
If you are worried about what the Pulse Audio change is actually doing, here's a description: 1. there is a new "snap-policy" PA module that is loaded by default. 2. when a client attempts to use the microphone and has a "snap.*" AppArmor label, it contacts snapd to check whether that app has permission to record audio (as opposed to simply playing sounds). 3. if the client is not a snap application or it is a snap application with record access, then PA will create record stream. So there should be no problem with removing snapd again. In fact the policy module should effectively be inert if no snaps are ever run, not even trying to talk to snapd. The "Recommends: snapd" is definitely too strong for the way Pulse Audio is using libsnapd-glib. Once snapd-glib's dependency is relaxed, we should be able to push this update again. -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
``` E: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/source/Sources Writing more data than expected (434945 > 433931) [IP: 34.229.150.131 80] E: Some index files failed to download. They have been ignored, or old ones used instead. ``` -- 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/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856187] [NEW] Cups wont print to smb-shared printer requiring user authentication via kerberos
Public bug reported: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. That's not true: the printer requires authentication. Maybe a bug. This print server requires any user to be authenticated and have a kerberos ticket. This is true. The user has a kerberos ticket and this user is allowed to print. The users kerberos ticket cache is available in memory and in /tmp/krb5_.keytab. CUPS does not seem to take it into account. May be a bug too. Changing "AuthInfoRequired" from "none" to "username,password" allows cups to print. But this has to be done editing /etc/cups/printers.conf. The web printer configuration just does not allow to set anything else than "none". This is a bug. Documentation misses what "AuthInfoRequired" has to be set for if kerberos authentication will be used. This is a bug too! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 13:54:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856187 Title: Cups wont print to smb-shared printer requiring user authentication via kerberos Status in cups package in Ubuntu: New Bug description: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. Tha
[Touch-packages] [Bug 1856188] [NEW] add-apt-repository -r unable to remove a PPA that no longer has a release file
Public bug reported: Similar to LP: #1855681 in ppa-purge. sudo add-apt-repository -r ppa:jonathonf/python-3.6 This PPA has been removed from public access as part of a protest against the abuse of open-source projects by large companies. For more detail visit the main page here: https://launchpad.net/~jonathonf If you are a company and you would like this PPA to continue then let me know your preferred route for contributions and I will arrange something. If we have already been in contact then ping me your Launchpad ID and I will add you to a private PPA in the meantime. More info: https://launchpad.net/~jonathonf/+archive/ubuntu/python-3.6 Press [ENTER] to continue or Ctrl-c to cancel removing it. Pressing Enter doesn't produce an error, but it doesn't remove the PPA either. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1856188 Title: add-apt-repository -r unable to remove a PPA that no longer has a release file Status in software-properties package in Ubuntu: New Bug description: Similar to LP: #1855681 in ppa-purge. sudo add-apt-repository -r ppa:jonathonf/python-3.6 This PPA has been removed from public access as part of a protest against the abuse of open-source projects by large companies. For more detail visit the main page here: https://launchpad.net/~jonathonf If you are a company and you would like this PPA to continue then let me know your preferred route for contributions and I will arrange something. If we have already been in contact then ping me your Launchpad ID and I will add you to a private PPA in the meantime. More info: https://launchpad.net/~jonathonf/+archive/ubuntu/python-3.6 Press [ENTER] to continue or Ctrl-c to cancel removing it. Pressing Enter doesn't produce an error, but it doesn't remove the PPA either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1856188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856189] [NEW] Trying to delete a printer will fill up the filesystem with logmessages
Public bug reported: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor:
[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Same for adding a new printer. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: New Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Same problem here, the microphone shows as (unplugged) in the PulseAudio Volume Control. Ubuntu 18.04.3 LTS. ❯ uname -a Linux luisz-G3-3590 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ❯ arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3254 Analog [ALC3254 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 2: ALC3254 Alt Analog [ALC3254 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ** Attachment added: "unplugged built-in microphone" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+attachment/5311999/+files/pulseunplugged.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Thank you for your bug report. Could you try on the current Ubuntu serie (focal), it should work there? https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/1.2.1~git20190929.60823f9-1 ** Changed in: libimobiledevice (Ubuntu) Importance: Undecided => High ** Changed in: libplist (Ubuntu) Importance: Undecided => High ** Changed in: libusbmuxd (Ubuntu) Importance: Undecided => High ** Changed in: usbmuxd (Ubuntu) Importance: Undecided => High ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
We first need to assert if it's working in the current version, then it would be nice to backport support to Bionic but that might be non trivial since it involves a soname change/transition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
Maciej, If you see an issue, re-run with debug::acquire::http so you can see if the correct files (by-hash) are fetched. It works for me # apt update -o debug::acquire::http=1 0% [Working]GET /ubuntu/dists/xenial-updates/InRelease HTTP/1.1 Host: us-east-1.ec2.archive.ubuntu.com Cache-Control: max-age=0 Accept: text/* User-Agent: Debian APT-HTTP/1.3 (1.2.32) Answer for: http://us-east-1.ec2.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease HTTP/1.1 200 OK Date: Thu, 12 Dec 2019 13:48:46 GMT Server: Apache/2.4.18 (Ubuntu) Last-Modified: Thu, 12 Dec 2019 13:15:00 GMT ETag: "1aa8c-59981884afd00" Accept-Ranges: bytes Content-Length: 109196 Cache-Control: max-age=0, proxy-revalidate Expires: Thu, 12 Dec 2019 13:48:46 GMT Get:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB] 29% [Working]GET /ubuntu/dists/xenial-updates/main/source/by-hash/SHA256/4c90cfd51700c92be5e841e81f22c09cd620f2ecd4eb5712f0ba1df74f3f253a HTTP/1.1 Host: us-east-1.ec2.archive.ubuntu.com Cache-Control: max-age=0 Accept: text/* User-Agent: Debian APT-HTTP/1.3 (1.2.32) Answer for: http://us-east-1.ec2.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/source/by-hash/SHA256/4c90cfd51700c92be5e841e81f22c09cd620f2ecd4eb5712f0ba1df74f3f253a HTTP/1.1 200 OK Date: Thu, 12 Dec 2019 13:48:47 GMT Server: Apache/2.4.18 (Ubuntu) Last-Modified: Thu, 12 Dec 2019 10:36:41 GMT ETag: "54038-5997f521bc040" Accept-Ranges: bytes Content-Length: 344120 Get:2 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/main Sources [344 kB] Fetched 453 kB in 1s (350 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. -- 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/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+subscriptions -- Mailing
[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
If you find such an instance, it's best to open a new bug, as this bug has been fixed, as can be clearly seen in the log file. -- 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/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856045] Re: capabilities set with setcap are not honoured
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1856045 Title: capabilities set with setcap are not honoured Status in libcap2 package in Ubuntu: New Bug description: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1856045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Same for any page with any printer. CUPS seems to run an endless loop exausting it has done ok. But nothing done at all. Just looping. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: New Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffic
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
** Also affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-bb-incoming rls-xx-incoming ** Tags removed: rls-xx-incoming ** Tags added: rls-x-incoming -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Status in snapd-glib package in Ubuntu: New Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Update Released
The verification of the Stable Release Update for lvm2 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Fix Released
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Fix Committed
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, for users who will see this fixed, will still experience
the situation in standard ISO, since I'm afraid Disco won't produces
new ISO. (it is not recommended to do new disco installs anyway since
it's going EOL shortly) One would need to rely on the mini.iso for
fetching the latest lvm2 package in the archive.
IIRC Bionic will have a new point release somewhere in Feb 2020 but
until then one would need to rely on the mini.iso for fetching the
latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting
[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Did you use the web interface of CUPS? Does the same problem occur when using the "lpadmin" command in a terminal? Does it also occur when using the printer part of the GNOME Control Center or system-config-printer? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: Incomplete Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
This bug was fixed in the package lvm2 - 2.02.176-4.1ubuntu4.2
---
lvm2 (2.02.176-4.1ubuntu4.2) disco; urgency=medium
* d/p/fix-auto-activation-at-boot.patch: (LP: #1854981)
Allow LV auto-activation (e.g. /usr on it's separate LV)
-- Eric Desrochers Thu, 05 Dec 2019
13:13:18 +
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Fix Released
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Fix Released
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, for users who will see this fixed, will still experience
the situation in standard ISO, since I'm afraid Disco won't produces
new ISO. (it is not recommended to do new disco installs anyway since
it's going EOL shortly) One would need to rely on the mini.iso for
fetching the latest lvm2 package in the archive.
IIRC Bionic will have a new point release somewhere in Feb 2020 but
until then one would need to rely on the mini.iso for fetching the
latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because
[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
The loop isn't within cups, but within js running within the browser. Noting this I tried to switch to an other browser to get rid of this loop. But without success: any of the tested ones leads to this loop: - Firefox (stable, esr, nightly) - Chrome (stable, beta, unstable, waterfall) - Chromium (stable, waterfall) - Vivaldi (stable, snapshot) - Opera (stable, beta, snapshot) - otter-browser - lynx -> pages unusable -- did not test further. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: Incomplete Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 0
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
This bug was fixed in the package lvm2 - 2.02.176-4.1ubuntu3.18.04.2
---
lvm2 (2.02.176-4.1ubuntu3.18.04.2) bionic; urgency=medium
* d/p/fix-auto-activation-at-boot.patch: (LP: #1854981)
Allow LV auto-activation (e.g. /usr on it's separate LV)
-- Eric Desrochers Thu, 05 Dec 2019
15:15:56 +
** Changed in: lvm2 (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: lvm2 (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Fix Released
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Fix Released
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, for users who will see this fixed, will still experience
the situation in standard ISO, since I'm afraid Disco won't produces
new ISO. (it is not recommended to do new disco installs anyway since
it's going EOL shortly) One would need to rely on the mini.iso for
fetching the latest lvm2 package in the archive.
IIRC Bionic will have a new point release somewhere in Feb 2020 but
until then one would need to rely on the mini.iso for fetching the
latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ lo
[Touch-packages] [Bug 1781428] Re: please enable snap mediation support
This update has been pulled from -updates by Sebastien as it was causing pulling in snapd via a recommends chain on systems that do not want to have snapd installed. A fix is in the works from what I know. Marking it as verification-failed so that it doesn't get re-released by accident. ** Tags removed: verification-done verification-done-bionic verification-done-xenial ** Tags added: verification-failed verification-failed-bionic verification-failed-xenial -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh c
[Touch-packages] [Bug 1781428] Re: please enable snap mediation support
** Changed in: pulseaudio (Ubuntu Xenial) Status: Fix Released => Fix Committed ** Changed in: pulseaudio (Ubuntu Bionic) Status: Fix Released => Fix Committed -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $ snap connections test-snapd-audio-record # record not connected Interface PlugSlot Notes audio-playback test-sna
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
If you want to speak to the snapd guys and ask them to make libsnapd- glib1 a dependency of snapd, by all means do so. There are no circumstances where it makes sense to have libsnapd-glib1 as a dependency of pulseaudio. Pulseaudio and Snap are two seperate entities, and only those with snapd installed actually need snapd library support. I don't want it. I don't need it, and I certainly don't want the dependencies it drags in. And I don't want to have to make admin changes to accomodate the whims and fanciful notions of others. And that, I think, is all I wish to say on the matter. -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781428] Re: please enable snap mediation support
Note, there is a spread test in snapd that checks for if the mediation patches are dropped (or added). While it is fine for https://launchpad.net/bugs/1856054 to be fast tracked, this pulseaudio bug should not be marked as Fix Released before the end of year break unless you coordinate with the snapd team first so as to avoid the spread test failing when no one is around to fix it. Specifically, snapd needs: https://github.com/snapcore/snapd/pull/7885 https://github.com/snapcore/snapd/pull/7886 To be clear, the snapd deb doesn't need to be involved in any of this; it is just coordinating with upstream so the upstream CI doesn't break over the holidays. -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
Bug #1856196 is now used to SRU the snapd-glib Recommends->Suggests change, closing the pulseaudio side since the update got reverted for now and the actual bug is not there ** No longer affects: snapd-glib (Ubuntu) -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
@Gord > There are no circumstances where it makes sense to have libsnapd-glib1 as a > dependency of > pulseaudio. Really it that it does, it"s a shared library and those are not optional under linux, you can have a read about ELF e.g here if you are intested https://lwn.net/Articles/631631/ Libraries are small and don't create real overhead, you probably have binaries pulling other libs you don't want. GTK for example does pull in libwayland and it's not optional either -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
So for the hp-spectre-x360-convertible-15 laptop, probably the internal mic doesn't connect to the codec, it connects to the PCH directly. So setting 0x12/0x13 to internal mic doesn't work at all. Please install this testing kernel, then boot with this kernel and upload the dmesg, Let us see if the dmic connects to the PCH or not. thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856008] Re: issuse
Thank you for taking the time to report this bug and helping to make Ubuntu better. Packages from third-party repositories can interfere with the way Ubuntu resolves and installs dependencies. Even if you now disabled the third party repositories the packages you installed (possibly during a system upgrade) were not removed. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: https://discourse.ubuntu.com/t/community-support/709 Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete ** Summary changed: - issuse + openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1856008 Title: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed Status in openssh package in Ubuntu: Incomplete Bug description: Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed openssh-sftp-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed i will not installed the open ssh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1856008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856201] [NEW] AuthInfoRequired set for one Printer will set it for all printers
Public bug reported: If at least one printer is set to "AuthInfoRequested negotiate" this will be taken for all printers, even if these have set "AuthInfoRequested none". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:39:56 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856201 Title: AuthInfoRequired set for one Printer will set it for all printers Status in cups package in Ubuntu: New Bug description: If at least one printer is set to "AuthInfoRequested negotiate" this will be taken for all printers, even if these have set "AuthInfoRequested none". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:39:56 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications abou
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Thank you for your feedback. @Stoo: if `rsync -vvv` is the culprit then
[1] is the right upstream bug, however there are so many (mostly stale)
"rsync hangs" upstream bugs [2] that I'm not sure which one is the
correct one to follow-up to here. The command in the description of this
report only has a single -v after all.
I think it won't be easy to make progress here without a reliable way to
reproduce the issue and without the involvement of the upstream
developers. What I suggest is to try to narrow the steps needed to
reproduce the hang, check if it still affects the latest upstream
release, and try to make the most appropriate bug move forward.
[1] https://bugzilla.samba.org/show_bug.cgi?id=11166
[2] https://bugzilla.samba.org/show_bug.cgi?id=11166#c2
** Bug watch added: Samba Bugzilla #11166
https://bugzilla.samba.org/show_bug.cgi?id=11166
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856204] [NEW] If a printer is set to "AuthInfoRequested negotiate" cups asks password for user negotiate
Public bug reported: If a printer is set to "AuthInfoRequested negotiate" cups will ask for password for user "negotiate" instead to exaust an error because "negotiate" isn't a keyword. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:45:11 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856204 Title: If a printer is set to "AuthInfoRequested negotiate" cups asks password for user negotiate Status in cups package in Ubuntu: New Bug description: If a printer is set to "AuthInfoRequested negotiate" cups will ask for password for user "negotiate" instead to exaust an error because "negotiate" isn't a keyword. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:45:11 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None d
[Touch-packages] [Bug 1852170] Re: [amdgpu] Severe screen corruption
*** This bug is a duplicate of bug 1848741 *** https://bugs.launchpad.net/bugs/1848741 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1852170 Title: [amdgpu] Severe screen corruption Status in xorg package in Ubuntu: Confirmed Bug description: Screen occasionally shows strange distortions and corruptions during almost any activity. Static or bars of colour appear in unusual places along the screen. Corruptions are often (though not always) removed in some sections of the screen by the appearance of other display elements (windows, tooltip, mouse-over, etc.) Description: Ubuntu 19.10 Release: 19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 16:13:38 2019 DistUpgraded: 2019-11-07 18:03:17,611 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:506f] InstallationDate: Installed on 2018-09-07 (430 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KUCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro radeon.modeset=0 ivrs_ioapic[32]=00:14.0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-07 (4 days ago) dmi.bios.date: 07/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET47W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KUCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0UET47W(1.27):bd07/16/2018:svnLENOVO:pn20KUCTO1WW:pvrThinkPadE485:rvnLENOVO:rn20KUCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E485 dmi.product.name: 20KUCTO1WW dmi.product.sku: LENOVO_MT_20KU_BU_Think_FM_ThinkPad E485 dmi.product.version: ThinkPad E485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Hey all, got it working on my Asus E200HA @ Xubuntu 19.10. As already mentioned, the installed kernel (currently 5.3.0-24) already brings the driver. What I had to do was uninstalling libasound2 (currently 1.1.9-1), as the sound card is not supported in this version. After uninstalling, I installed the latest alsa-lib [1] (1.2.1.2). Note, that the default installation of the alsa-lib takes place in "/usr/lib", but it should be placed in "/usr/lib/x86_64-linux-gnu/". This can be done by running "./configure --libdir=/usr/lib/x86_64-linux-gnu/". After installing it, I downloaded the latest alsa-ucm-config [2] (1.2.1.2). The content of the ucm2 folder must be stored in "/usr/share/alsa/ucm2/". After a reboot, the sound works :) So, installing the latest libasound2 (= alsa-lib) on the right place and placing the UCM files in the right directory did the trick for me. [1] https://github.com/alsa-project/alsa-lib [2] https://github.com/alsa-project/alsa-ucm-conf/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in panel
The format you are complaining about is American NOT English. I have noticed the same problem, running Gnome Flashback under Ubuntu 18.04, today. System settings show the correct English regional format (eg Thu 12 Dec 2019 18:29:30) but, in the indicator, I get Thu Dec 12 2019 18:29:30. Extremely annoying. gsettings set com.canonical.indicator.datetime custom-time-format "%a %d %b %Y %H:%M:%S" has no effect nor can I find an appropriate valid string to enter in locations. Is this now being handled elsewhere? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in panel Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
At the time I filed the bug, I did not notice an updated build in focal - it was still the same one as in eoan, but perhaps I was just not paying enough attention. I will try it out. That version is likely to be new enough to work, although I know there was an update to libusbmuxd with a version and soname bump in november (although the functional changes are already present in that git revision) and that would be worth having to avoid long term confusion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
I'll try out the focal builds when I get a chance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
** Tags added: bionic ddstreet disco eoan focal sts systemd -- 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/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: In bionic, running systemd 237-3ubuntu10.22 and netplan.io 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface with a static IPv4 address if the statically confiugred address is the same as the interface already has gotten from DHCP. This will cause the interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843812] Re: apt info "please use the '-a' switch"
This bug was fixed in the package apt - 1.9.5 --- apt (1.9.5) experimental; urgency=medium [ Julian Andres Klode ] * Parse 'show' arguments for the 'info' alias as well (LP: #1843812) * patterns: Add base class for regular expression matching * patterns: Add ?version * patterns: Add ?source-name and ?source-version * patterns: Add ?archive * patterns: Add ?origin * patterns: Add ?any-version * patterns: Implement ?narrow(...), as ?any-version(?and(...)) * patterns: Add ?all-versions * patterns: Add ?section * netrc: Restrict auth.conf entries to https by default (Closes: #945911) [ Anatoly Borodin ] * README.md: fix dead anonscm link [ Алексей Шилин ] * Search in all available description translations (Closes: #49) * strutl: Add APT::String::DisplayLength() function * Fix progress bar width for multibyte charsets [ Chris Leick ] * German manpage translation update [ David Kalnischkies ] * Use correct filename on IMS-hit reverify for indices * Remove failed trusted signature instead of index on IMS hit [ Anthony Papillon ] * Fix a mistake in man french translation -- Julian Andres Klode Mon, 02 Dec 2019 18:17:56 +0100 ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1843812 Title: apt info "please use the '-a' switch" Status in apt package in Ubuntu: Fix Released Bug description: When getting info about a package, I see a notice asking me to "Please use the '-a' switch", but the apt program does not accept an '-a' switch. Steps to reproduce: $ apt info docker.io ... N: There is 1 additional record. Please use the '-a' switch to see it $ apt -a info docker.io $ apt info -a docker.io $ apt info docker.io -a Expected outcome: same output as `apt info docker.io` but with the 1 additional record. Seen outcome: E: Command line option 'a' [from -a] is not understood in combination with the other options. Also seen: `apt info $pkg` gives the same output as `apt show $pkg` including the Notice message, but where `apt info -a $pkg` fails, `apt show -a $pkg` succeeds. Workaround: Use `apt show -a $pkg` instead. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apt 1.8.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Sep 12 14:16:09 2019 InstallationDate: Installed on 2018-10-30 (316 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: Upgraded to disco on 2019-04-18 (147 days ago) modified.conffile..etc.logrotate.d.apport: [modified] modified.conffile..etc.logrotate.d.apt: [modified] mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709 mtime.conffile..etc.logrotate.d.apt: 2018-12-13T12:13:41.355709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1843812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
Update: I retested today, and I must have made a mistake in my previous upstream tests; it does appear fixed with upstream systemd, as well as being fixed in Ubuntu E/F. -- 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/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: In bionic, running systemd 237-3ubuntu10.22 and netplan.io 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface with a static IPv4 address if the statically confiugred address is the same as the interface already has gotten from DHCP. This will cause the interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
This bug was fixed in the package lvm2 - 2.02.176-4.1ubuntu3.18.04.2 --- lvm2 (2.02.176-4.1ubuntu3.18.04.2) bionic; urgency=medium * d/p/fix-auto-activation-at-boot.patch: (LP: #1854981) Allow LV auto-activation (e.g. /usr on it's separate LV) --- ** Changed in: lvm2 (Ubuntu) Status: Confirmed => Fix Released ** Also affects: lvm2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial Status in curtin: Invalid Status in MAAS: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Bionic: Fix Released Bug description: Soon after upgrade to Xenial (from 15.10) the boot process got broken. I'm using LVM for /root swap and other partitions. === The current behaviour is: When I boot short after the Grub login screen I'm getting log messages like: --- Scanning for Btrfs filesystems resume: Could not state the resume device file: '/dev/mapper/VolGroup' Please type in the full path... --- Then I press ENTER, for a few minutes some errors about floppy device access are raised (for some reason it tries to scan fd0 when floppy drive is empty). And then: --- Gave up waiting for root device. Common problems: ... ... ALERT! UUID=xxx-xxx does not exist. Dropping to a shell. --- From the BusyBox shell I managed to recover the boot by issuing "lvm vgchange -ay", then exit and then boot continues fine (all LVM file systems are successfully mounted). === One workaround so far is creating /etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange -ay". But I'm looking for cleaner solution. Boot used to work fine with 15.10. Actually the first boot after upgrading to Xenial actually worked OK too, I'm not sure what might changed meanwhile (I've been fixing some packages installation since mysql server upgrade has failed). === # lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1573982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: New Status in systemd source package in Disco: New Bug description: In bionic, running systemd 237-3ubuntu10.22 and netplan.io 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface with a static IPv4 address if the statically confiugred address is the same as the interface already has gotten from DHCP. This will cause the interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- 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/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Bug description: In bionic, running systemd 237-3ubuntu10.22 and netplan.io 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface with a static IPv4 address if the statically confiugred address is the same as the interface already has gotten from DHCP. This will cause the interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
** Description changed: - In bionic, running systemd 237-3ubuntu10.22 and netplan.io - 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface - with a static IPv4 address if the statically confiugred address is the - same as the interface already has gotten from DHCP. + [impact] + + if networkd is configured with a static address, and the address has + already been assigned by dhcp (so that it has finite valid_lft), + networkd will not change the valid_lft to 'forever' during startup, + which leaves networkd thinking the address is static (meaning, networkd + will not attempt to renew the dhcp lease) but the address valid_lft + counting down. + + Once the valid_lft expires, the kernel will remove the address from the + interface, breaking the system's networking. + + [test case] + + configure a system with networkd similar to: + + [Match] + Name=ens3 + + [Network] + DHCP=ipv4 + + restart systemd-networkd, and ens3 should get a DHCP address, e.g.: + + $ ip -4 a show ens3 + 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 + inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 +valid_lft 2295sec preferred_lft 2295sec + + then, edit the networkd config to use a static address, e.g.: + + [Match] + Name=ens3 + + [Network] + Address=192.168.122.147/24 + Gateway=192.168.122.1 + DNS=192.168.122.1 + Domains=vm + + make sure to use the exact same address that was provided by dhcp. + + Then, without rebooting, just restart networkd and check the address + lft: + + $ sudo systemctl restart systemd-networkd + + $ ip -4 a show ens3 + 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 + inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 +valid_lft 2992sec preferred_lft 2992sec + + + the address should have 'forever' valid_lft, but it doesn't. + + [regression potential] + + this changes the details of how networkd updates static addresses during + startup, so any regression would occur at networkd startup when using + static addresses. + + [scope] + + this is needed only in Bionic and Disco. + + this is fixed by upstream: + https://github.com/systemd/systemd/pull/11460/commits + specifically commit a47a6daebe0af26c07d8d423225eb4add110793c + which is included in Eoan and later. + + In Xenial using networkd, testing shows this problem does not occur. + + [other info] + + original description: + --- + + + In bionic, running systemd 237-3ubuntu10.22 and netplan.io 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface with a static IPv4 address if the statically confiugred address is the same as the interface already has gotten from DHCP. This will cause the interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 # apt-cache policy systemd systemd: - Installed: 237-3ubuntu10.22 + Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: - Installed: 0.97-0ubuntu1~18.04.1 + Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. ** Description changed: [impact] if networkd is configured with a static address, and the address has already been assigned by dhcp (so that it has finite valid_lft), networkd will not change the valid_lft to 'forever' during startup, which leaves networkd thinking the address is static (meaning, networkd will not attempt to renew the dhcp lease) but the address valid_lft counting down. Once the valid_lft expires, the kernel will remove the address from the interface, breaking the system's networking. [test case] configure a system with networkd similar to: [Match] Name=ens3 [Network] DHCP=ipv4 restart systemd-networkd, and ens3 should get a DHCP address, e.g.: $ ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 - inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 -valid_lft 2295sec preferred_lft 2295sec + inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 + valid_lft 2295sec preferred_lft 2295sec then, edit the networkd config to use a static address, e.g.: [Match] Name=ens3 [Network] Address=192.168.122.147/24 Gateway=192.168.122.1 DNS=192.168.12
[Touch-packages] [Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
** Tags removed: eoan focal -- 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/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Bug description: [impact] if networkd is configured with a static address, and the address has already been assigned by dhcp (so that it has finite valid_lft), networkd will not change the valid_lft to 'forever' during startup, which leaves networkd thinking the address is static (meaning, networkd will not attempt to renew the dhcp lease) but the address valid_lft counting down. Once the valid_lft expires, the kernel will remove the address from the interface, breaking the system's networking. [test case] configure a system with networkd similar to: [Match] Name=ens3 [Network] DHCP=ipv4 restart systemd-networkd, and ens3 should get a DHCP address, e.g.: $ ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 valid_lft 2295sec preferred_lft 2295sec then, edit the networkd config to use a static address, e.g.: [Match] Name=ens3 [Network] Address=192.168.122.147/24 Gateway=192.168.122.1 DNS=192.168.122.1 Domains=vm make sure to use the exact same address that was provided by dhcp. Then, without rebooting, just restart networkd and check the address lft: $ sudo systemctl restart systemd-networkd $ ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3 valid_lft 2992sec preferred_lft 2992sec the address should have 'forever' valid_lft, but it doesn't. [regression potential] this changes the details of how networkd updates static addresses during startup, so any regression would occur at networkd startup when using static addresses. [scope] this is needed only in Bionic and Disco. this is fixed by upstream: https://github.com/systemd/systemd/pull/11460/commits specifically commit a47a6daebe0af26c07d8d423225eb4add110793c which is included in Eoan and later. In Xenial using networkd, testing shows this problem does not occur, because this older version of networkd removes the 'foreign' dhcp address before re-assigning it as a static address. [other info] original description: --- In bionic, running systemd 237-3ubuntu10.22 and netplan.io 0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface with a static IPv4 address if the statically confiugred address is the same as the interface already has gotten from DHCP. This will cause the interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
> For openvpn + systemd-resolve:
>
> With "up / down" openvpn config file commands you can wrap "systemd-
> resolve --set-dns=XXX" and update the given DNS servers.
There's a package for that: openvpn-systemd-resolved
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 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: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856255] [NEW] Apport-bug wrongly complains about the program not being installed
Public bug reported: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) The error message is clearly wrong: apport-bug must be installed to be able to display this window. --- ProblemType: Bug ApportLog: ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (105 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: apport 2.20.9-0ubuntu7.9 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1856255/+attachment/5312077/+files/apporta.png ** Tags added: apport-collected bionic ** Description changed: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) - The error message is clearly wrong: apport-bug must be installed to be - able to display this window. + The error message is clearly wrong: apport-bug must be installed to be able to display this window. + --- + ProblemType: Bug + ApportLog: + ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 + ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") + ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-08-28 (105 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 + Package: apport 2.20.9-0ubuntu7.9 + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-1065-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1856255 Title: Apport-bug wrongly complains about the program not being installed Status in apport package in Ubuntu: New Bug description: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Includin
[Touch-packages] [Bug 1856255] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1856255/+attachment/5312078/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1856255 Title: Apport-bug wrongly complains about the program not being installed Status in apport package in Ubuntu: New Bug description: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) The error message is clearly wrong: apport-bug must be installed to be able to display this window. --- ProblemType: Bug ApportLog: ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (105 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: apport 2.20.9-0ubuntu7.9 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856255] Re: Apport-bug wrongly complains about the program not being installed
Update: I’ve just typed “apport-collect 1856255” in a terminal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1856255 Title: Apport-bug wrongly complains about the program not being installed Status in apport package in Ubuntu: New Bug description: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) The error message is clearly wrong: apport-bug must be installed to be able to display this window. --- ProblemType: Bug ApportLog: ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (105 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: apport 2.20.9-0ubuntu7.9 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856255] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856255/+attachment/5312079/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1856255 Title: Apport-bug wrongly complains about the program not being installed Status in apport package in Ubuntu: New Bug description: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) The error message is clearly wrong: apport-bug must be installed to be able to display this window. --- ProblemType: Bug ApportLog: ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (105 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: apport 2.20.9-0ubuntu7.9 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This bug was fixed in the package pulseaudio - 1:13.0-1ubuntu5 --- pulseaudio (1:13.0-1ubuntu5) focal; urgency=medium * Add 0031-lp1847570-Revert-switch-on-connect-Do-not-ignore-HDMI-sinks.patch to revert to PulseAudio v12 behaviour and ignore monitors with HDMI ports. At least until a proper solution arrives in PulseAudio v14. (LP: #1847570) -- Daniel van Vugt Wed, 11 Dec 2019 16:34:39 +0800 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856257] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856257/+attachment/5312080/+files/ProcCpuinfoMinimal.txt ** Description changed: - My wifi is no longer working since a recent update. When typing - “ifconfig -a”, I get (among other connections), the following one, which - seems to correspond to my wifi card: + My wifi is no longer working since a recent update (yesterday, I think). + When typing “ifconfig -a”, I get (among other connections), the + following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 - ether 5c:87:9c:fa:81:c9 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 + ether 5c:87:9c:fa:81:c9 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 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. - wlp59s0 IEEE 802.11 ESSID:off/any - Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm - Retry short limit:7 RTS thr:off Fragment thr:off - Power Management:on + wlp59s0 IEEE 802.11 ESSID:off/any + Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm + Retry short limit:7 RTS thr:off Fragment thr:off + Power Management:on $ rfkill list all 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no 1: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` - I’m calling apport-collect on this bug to add othe relevant information. - --- + I’m calling apport-collect on this bug to add other relevant information. + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: - gcc-8-base 8.3.0-6ubuntu1~18.04.1 - libc6 2.27-3ubuntu1 - libgcc1 1:8.3.0-6ubuntu1~18.04.1 - libpcre3 2:8.39-9 - libselinux1 2.7-2build2 + gcc-8-base 8.3.0-6ubuntu1~18.04.1 + libc6 2.27-3ubuntu1 + libgcc1 1:8.3.0-6ubuntu1~18.04.1 + libpcre3 2:8.39-9 + libselinux1 2.7-2build2 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Description changed: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 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 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` + This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions
[Touch-packages] [Bug 1856257] [NEW] SIOCSIFFLAGS: Input/output error
Public bug reported: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 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 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: net-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: My wifi is no longer working since a recent update. When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 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 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add othe relevant information. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + Dependencies: + gcc-8-base 8.3.0-6ubuntu1~18.04.1 + libc6 2.27-3ubuntu1 + libgcc1 1:8.3.0-6ubuntu1~18.04.1 + libpcre3 2:8.39-9 + libselinux1 2.7-2build2 + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-08-28 (106 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 + Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem
[Touch-packages] [Bug 1854689] Re: BlueZ 5.52 release
This bug was fixed in the package bluez - 5.52-0ubuntu1 --- bluez (5.52-0ubuntu1) focal; urgency=medium * New upstream release 5.52 (LP: #1854689): - Fix issue with AVDTP session disconnect timeout handling. - Mark media endpoint APIs as stable interfaces. -- Daniel van Vugt Thu, 12 Dec 2019 09:42:09 +0100 ** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854689 Title: BlueZ 5.52 release Status in bluez package in Ubuntu: Fix Released Bug description: BlueZ 5.52 release: http://www.bluez.org/release-of-bluez-5-52/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835404] Re: bzip2 data integrity error when decompressing
I've encountered the exact same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1835404 Title: bzip2 data integrity error when decompressing Status in bzip2 package in Ubuntu: New Bug description: Hi, With the latest version of bzip2, 1.0.6-8.1ubuntu0.1, I am unable to extract several archives from nvidia.com. For example with archive: https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0 /jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2 Exactly the same archives work perfectly fine with bzip2 version 1.0.6-8 (the previous release before 1.0.6-8.1ubuntu0.1. I am experiencing these issues with bzip2 1.0.6-8.1ubuntu0 on both Ubuntu 16.04 and 18.04. Here are details to reproduce the issue: leon@u1804:~$ apt-cache policy bzip2 bzip2: Installed: 1.0.6-8.1ubuntu0.1 Candidate: 1.0.6-8.1ubuntu0.1 Version table: *** 1.0.6-8.1ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.6-8.1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages leon@u1804:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic leon@u1804:~$ wget https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2 --2019-07-04 10:47:12-- https://developer.download.nvidia.com/embedded/L4T/r32_Release_v1.0/jax-tx2/BSP/JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2 Resolving developer.download.nvidia.com (developer.download.nvidia.com)... 192.229.221.58, 2606:2800:233:ef6:15dd:1ece:1d50:1e1 Connecting to developer.download.nvidia.com (developer.download.nvidia.com)|192.229.221.58|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 125799502 (120M) [application/octet-stream] Saving to: ‘JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2’ JAX-TX2-Jetson_Linux_R32.1.0_aa 100%[===>] 119.97M 27.6MB/sin 4.4s 2019-07-04 10:47:32 (27.2 MB/s) - ‘JAX- TX2-Jetson_Linux_R32.1.0_aarch64.tbz2’ saved [125799502/125799502] leon@u1804:~$ bzip2 -dvv JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2 JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2: [1: huff+mtf rt+rld] [2: huff+mtf rt+rld] [3: huff+mtf rt+rld] [4: huff+mtf rt+rld] [5: huff+mtf bzip2: Data integrity error when decompressing. Input file = JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tbz2, output file = JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tar It is possible that the compressed file(s) have become corrupted. You can use the -tvv option to test integrity of such files. You can use the `bzip2recover' program to attempt to recover data from undamaged sections of corrupted files. bzip2: Deleting output file JAX-TX2-Jetson_Linux_R32.1.0_aarch64.tar, if it exists. Best regards, Leon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1835404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856255] Re: Apport-bug wrongly complains about the program not being installed
Thank you for taking the time to report this bug and helping to make Ubuntu better. There is no package named `ifconfig` so you cannot file a bug against a non-existent package. Your "Apport told me that ifconfig was not installed. But it was!" is incorrect as apport deals with packages not commands. I have `ifconfig` installed on my box too, and a `dpkg -S /sbin/ifconfig` reports "net- tools: /sbin/ifconfig" ie. the command `ifconfig` is found in the "net- tools" package and that is what you should use with appport. Reading your report it appears you are mostly after support. This bug report can be converted to a question (aimed at support, bug reports are aimed and finding problems and fixing so subsequent users won't stumble with the same issue). You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 I'm going to mark this report "incomplete" as it appears to be about support issues. If you believe I'm in error, please respond saying so in comment, and then the Status can be returned to "New". Thanks again for helping make Ubuntu better. ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1856255 Title: Apport-bug wrongly complains about the program not being installed Status in apport package in Ubuntu: Incomplete Bug description: I typed “apport-bug ifconfig” because ifconfig was wrongly behaving. Apport told me that ifconfig was not installed. But it was! So I restarted my computer, just in case, but the bug is still there. And for all programs that it tried. Including Apport itself. Currently, when I type “apport-bug apport-bug”, I get a window “Problem in apport-bug” with the following message: “The problem cannot be reported: This report is about a package that is not installed.” (See screenshot here-attached.) The error message is clearly wrong: apport-bug must be installed to be able to display this window. --- ProblemType: Bug ApportLog: ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: called for pid 7431, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable: /home/martin/.steam/ubuntu12_64/vulkandriverquery (command line "/home/martin/.steam/ubuntu12_32/../ubuntu12_64/vulkandriverquery") ERROR: apport (pid 7467) Thu Dec 12 23:14:13 2019: executable does not belong to a package, ignoring ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (105 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: apport 2.20.9-0ubuntu7.9 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1856255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856257] Re: SIOCSIFFLAGS: Input/output error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1856257 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. To look at your issue I'd like to read `dmesg` output by using built-in tools much detail we look at is included, currently it's not present. I've subsequently marked this incomplete. When apport-collect has been run, please comment as such and return status to "New". ** Changed in: net-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: Incomplete Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 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 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
mvo and others, please test the above fix on Ubuntu 20.04 if it is convenient. When and if confirmed to be working we will propose the same to 19.10. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=
** Description changed: + [impact] + + services configured with both OnFailure= and Restart= directives will + both start the failure service(s), as well as restarting itself. The + documentation (and later versions) indicate that OnFailure= services + will only be started once the service actually does stop (due to + failure) once its restart limit has been exceeded. + + [test case] + + create service files as: + + ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service + [Unit] + OnFailure=failure.service + + [Service] + ExecStart=/bin/sh -c '/bin/sleep 10; /bin/false' + Restart=always + + ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service + [Service] + ExecStart=/bin/true + + + perform daemon-reload, and then start test service: + + ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload + ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl start test + + wait for a while for the test service to exit - at least 10 seconds, as + that's what we configured in the service, although I have waited longer + in this example. Then check the journal for both test and failure + services: + + ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u test + -- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:18:34 UTC. -- + Dec 13 01:17:43 lp1849261-b systemd[1]: Started test.service. + Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE + Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. + Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. + Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. + Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 1. + Dec 13 01:17:53 lp1849261-b systemd[1]: Stopped test.service. + Dec 13 01:17:53 lp1849261-b systemd[1]: Started test.service. + Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE + Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. + Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. + Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. + Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 2. + Dec 13 01:18:04 lp1849261-b systemd[1]: Stopped test.service. + Dec 13 01:18:04 lp1849261-b systemd[1]: Started test.service. + Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE + Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. + Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. + Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. + Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 3. + Dec 13 01:18:14 lp1849261-b systemd[1]: Stopped test.service. + Dec 13 01:18:14 lp1849261-b systemd[1]: Started test.service. + Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE + Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. + Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. + Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. + Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 4. + Dec 13 01:18:24 lp1849261-b systemd[1]: Stopped test.service. + Dec 13 01:18:24 lp1849261-b systemd[1]: Started test.service. + Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE + Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. + Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. + Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. + Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 5. + Dec 13 01:18:34 lp1849261-b systemd[1]: Stopped test.service. + Dec 13 01:18:34 lp1849261-b systemd[1]: Started test.service. + + + ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u failure + -- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:19:15 UTC. -- + Dec 13 01:17:53 lp1849261-b systemd[1]: Started failure.service. + Dec 13 01:18:03 lp1849261-b systemd[1]: Started failure.service. + Dec 13 01:18:14 lp1849261-b systemd[1]: Started failure.service. + Dec 13 01:18:24 lp1849261-b systemd[1]: Started failure.service. + Dec 13 01:18:34 lp1849261-b systemd[1]: Started failure.service. + Dec
[Touch-packages] [Bug 1855647] Re: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc?
If a DVD is loaded, a disc with a DVD tag is displayed on the dock. Why not display a disc with a ISO tag if an ISO is loaded.? -- 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/1855647 Title: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc? Status in glib2.0 package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Dock 3) When an ISO image is loaded, a disc with ISO tag would be displayed on the dock. 4) A disc drive was displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1855647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
