[Touch-packages] [Bug 1357529] Re: Magenta Toner Icon is yellow and Yellow Toner Icon is magenta
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1357529 Title: Magenta Toner Icon is yellow and Yellow Toner Icon is magenta Status in cups package in Ubuntu: Expired Bug description: I've a Brother-HL-3070CW LED printer. When fetching Printer Properties and selecting Ink/Toner Levels I observe the Magenta Toner Icon is yellow and Yellow Toner Icon is magenta. So it's difficult to see what toner cartridge is high or low because I don't know it the Icon is correct or the Text Below the Icon is correct. package=cups loodje@moosker:~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 loodje@moosker:~$ apt-cache policy cups cups: Installed: 1.7.2-0ubuntu1.1 Candidate: 1.7.2-0ubuntu1.1 Version table: *** 1.7.2-0ubuntu1.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1.7.2-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages loodje@moosker:~$ Expectation: Icon graphic colour matches text description Happened: They do not match - see attachment: Screenshot from 2014-08-15 12:46:47.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Fri Aug 15 12:37:31 2014 InstallationDate: Installed on 2014-08-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lpstat: device for Brother-HL-3070CW: dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V GEN3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-21 (105 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HL-3070CW: dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/ MachineType: System manufacturer System Product Name Package: cups 2.2.7-1ubuntu2.1 PackageArchitecture: amd64 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HL-3070CW.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HL-3070CW.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d64f5cbf-8b52-40c4-9cfb-5444655bd5bf ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V GEN3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1801439] Re: Unable to add PPA's via the software-properties
I followed TEST instructions in description I got exactly the same output guiverc@dx6120lu:~$ sudo software-properties-qt QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Traceback (most recent call last): File "/usr/lib/python3/dist-pack ... [redacted ] ... has no attribute 'keyserver' (I saved my output & copy/pasted output from description then `diff -Zb` them & only difference was prompt & XDG_RUNTIME_DIR lines..) guiverc@dx6120lu:~$ apt-cache policy software-properties-qt software-properties-qt: Installed: 0.96.27 Candidate: 0.96.27 Version table: *** 0.96.27 500 500 http://ftp.iinet.net.au/pub/ubuntu cosmic/universe i386 Packages 100 /var/lib/dpkg/status // note: my arch is x86 i686 -- 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/1801439 Title: Unable to add PPA's via the software-properties Status in software-properties package in Ubuntu: Confirmed Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801439] Re: Unable to add PPA's via the software-properties
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1801439 Title: Unable to add PPA's via the software-properties Status in software-properties package in Ubuntu: Confirmed Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801439] [NEW] Unable to add PPA's via the software-properties
Public bug reported: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1801439 Title: Unable to add PPA's via the software-properties Status in software-properties package in Ubuntu: New Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package
Hello Brian, or anyone else affected,
Accepted apport into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.10-0ubuntu13.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: apport (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-cosmic
--
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/1760220
Title:
ubuntu-bug with program path says as a snap does not belong to a
package
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
In Progress
Status in apport source package in Cosmic:
Fix Committed
Bug description:
[Impact]
ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---
apport's ui.py file contains the following code:
809 # executable?
810 elif '/' in self.args[0]:
811 pkg = apport.packaging.get_file_package(self.args[0])
812 if not pkg:
813 optparser.error('%s does not belong to a package.' %
self.args[0])
814 sys.exit(1)
815 self.args = []
816 self.options.filebug = True
817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760220/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799629] Re: package linux-image-extra-4.4.0-130-generic 4.4.0-130.156 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1799629 Title: package linux-image-extra-4.4.0-130-generic 4.4.0-130.156 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: alam@alam:~$ sudo apt-get -f install linux-image-4.4.0-135-generic Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools linux-headers-4.4.0-135-generic The following packages will be REMOVED: linux-image-extra-4.4.0-128-generic linux-image-extra-4.4.0-130-generic The following NEW packages will be installed: linux-image-4.4.0-135-generic 0 upgraded, 1 newly installed, 2 to remove and 312 not upgraded. 18 not fully installed or removed. Need to get 0 B/22.1 MB of archives. After this operation, 244 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 445898 files and directories currently installed.) Removing linux-image-extra-4.4.0-128-generic (4.4.0-128.154) ... depmod: FATAL: could not load /boot/System.map-4.4.0-128-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic update-initramfs: Generating /boot/initrd.img-4.4.0-128-generic WARNING: missing /lib/modules/4.4.0-128-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.4.0-128-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_gCUcDz/lib/modules/4.4.0-128-generic/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_gCUcDz/lib/modules/4.4.0-128-generic/modules.builtin: No such file or directory xz: (stdout): Write error: No space left on device E: mkinitramfs failure cpio 141 xz --check=crc32 1 update-initramfs: failed for /boot/initrd.img-4.4.0-128-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.4.0-128-generic (--remove): subprocess installed post-removal script returned error exit status 1 Removing linux-image-extra-4.4.0-130-generic (4.4.0-130.156) ... depmod: FATAL: could not load /boot/System.map-4.4.0-130-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic update-initramfs: Generating /boot/initrd.img-4.4.0-130-generic WARNING: missing /lib/modules/4.4.0-130-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.4.0-130-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_rpJGqk/lib/modules/4.4.0-130-generic/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_rpJGqk/lib/modules/4.4.0-130-generic/modules.builtin: No such file or directory xz: (stdout): Write error: No space left on device E: mkinitramfs failure cpio 141 xz --check=crc32 1 update-initramfs: failed for /boot/initrd.img-4.4.0-130-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.4.0-130-generic (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-extra-4.4.0-128-generic linux-image-extra-4.4.0-130-generic E: Sub-process /usr/bin/dpkg returned an error code (1) alam@alam:~$ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alam 2744 F pulseaudio Date: Wed Oct 24 11:03:03 2018 DpkgHistoryLog: Start-Date: 2018-10-24 11:02:40 Commandline: apt-get -f install linux-image-4.4.0-135-generic Requested-By: alam (1000)
[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: unattended-upgrades (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: unattended-upgrades (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
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/1778219
Title:
unattended-upgrades hangs on shutdown, leaves system in a broken state
Status in apt package in Ubuntu:
Invalid
Status in init-system-helpers package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
New
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in init-system-helpers source package in Bionic:
New
Status in snapd source package in Bionic:
New
Status in unattended-upgrades source package in Bionic:
In Progress
Bug description:
[Impact]
* Unattended-upgrades hangs and gets killed when installing upgrades
that stat/stop services on shutdown, leaving the system in a broken
state
[Test Case]
* Install an updated bionic system:
$ lxc launch ubuntu:18.04 uu-shutdown-test
# apt update
...
* When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
# systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket"
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
* Configure u-u to run on shutdown and install -updates:
# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
* Downgrade snapd:
# apt install snapd=2.32.5+18.04
* # reboot
* With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
`-{unattended-upgr}
* With fixed u-u observe snapd update taking place and system
rebooting after a few seconds with all updates installed
* Since this fix is partially reverting the fix for LP: #1654600
please test LP: #1654600 as well to avoid regressions.
[Regression Potential]
* As part of the fix manual changes were made to postinst to properly
transition from coupling u-u.service with multi-user.target to coupling it with
shutdown.target again which can make u-u started during normal boot when there
is a bug in the implementation.
on-testing the SRU.
* Due to relationship changes between u-u.service, other services and
targets u-u may fail to run on shutdown in case of an unexpected regression.
[Original Bug Text]
When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
package installation on various packages hangs until the systemd
ShutdownTimeout (30min) is expired and systemd kills all processes and
powers off/reboots the system.
This leaves packages in an unconfigured, broken state. At least
sometimes this cannot be fixed with a "dpkg --configure -a", but
instead requires the user to manually reinstall the package that
caused the hang.
This appears to be a deadlock, because the hanging commands are always
"systemctl stop ..." or "systemctl restart ...", etc.. If I understand
this correctly, those systemctl commands block because systemd tries
to shutdown the system and tries to satisfy all dependencies for the
shutdown targets before those systemctl commands could get executed,
which creates a deadlock.
Steps to reproduce:
- Install 18.04
- activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
- disable bionic-updates in /etc/apt/sources.list (more on that later)
- execute "unattended-upgrade --download-only"
- reboot the system
-> The upgrade on shutdown hangs when configuring the apport package.
The hanging command is "systemctl stop apport-forward.socket". The
system
[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: unattended-upgrades (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: unattended-upgrades (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
Thanks for getting back to me! I no longer have this piece of hardware so it's ok for me to close this one for now. -- 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/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Yes, I'll be SRU'ing Bionic and Xenial as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: Confirmed Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Well in fact for Xenial there is an email thread already to do a full backport : https://lists.canonical.com/mailman/listinfo/openstack-devops https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1702793 So I'll SRU Bionic and let the full backport discussion to finish for Xenial, as I don't want to interfere. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: Confirmed Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800723] Re: Missing package python3.7-pip
Ok, I see. Python3-pip [1] depends on python3, which is pointing at the default python3 version. In Ubuntu at the moment, this is 3.6. Presumably at some point in the future the default will be changed to 3.7, and then any packages using python3 will install that instead. I am not sure if this will retroactively happen for older Ubuntu releases. [1] https://packages.ubuntu.com/bionic/python3-pip ** Package changed: python3.7 (Ubuntu) => python3-defaults (Ubuntu) ** Changed in: python3-defaults (Ubuntu) Status: Incomplete => New ** Changed in: python-pip (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1800723 Title: Missing package python3.7-pip Status in python-pip package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800723] [NEW] Missing package python3.7-pip
You have been subscribed to a public bug: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. ** Affects: python-pip (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic bot-comment cosmic -- Missing package python3.7-pip https://bugs.launchpad.net/bugs/1800723 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
@Marcos,#80: ubuntu-18.04-server-amd64.iso is exactly the ISO I'm using
for my installations.
@Mathieu,#82: you've removed the verification-failed-bionic tag but
0.40.1~18.04.2 is still not working on my side, both on VirtualBox VM and on
Proxmox VM (KDE).
Interface renaming works but IP address/netmask doesn't.
I'm using ubuntu-18.04-server-amd64.iso to install both of them, and they both
have the same issue.
PS: I actually have a production server VM witn netplan-0.40.1~18.04.2 and,
after reboot, I need to connect to it (thanks to Proxmox HTTP-VNC console) and
manually execute "netplan apply" to bring the network up.
This is unaccetable so I'll soon remove netplan and switch back to the rock
solid ifupdown for such a simple newtork configuration like mine.
Sorry to say that netplan brought me nothing but issues...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
[Touch-packages] [Bug 1734669] Re: Long texts in windows overlap with icon on the left
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1734669 Title: Long texts in windows overlap with icon on the left Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The attached screenshot should make clear what I mean. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 27 12:39:02 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['appindicatorsupp...@rgcjonas.gmail.com', 'ubuntu-d...@ubuntu.com', 'updateindica...@aegirxx.googlemail.com', 'dejadup-launcher@stefano.facchini', 'active-notifications-indicator@nls1729', 'xcaffe...@asegner.gmail.com', 'gnome-shell-screens...@ttll.de', 'clipboard-indica...@tudmotu.com', 'caffe...@patapon.info', 'updates-dia...@rtcm.fedorapeople.org', 'drop-down-termi...@gs-extensions.zzrough.org', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'tinkerer@joebodo', 'apt-update-indica...@franglais125.gmail.com', 'topic...@phocean.net']" b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'google-chrome.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2017-11-12 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (2017) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1734669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
note that the sound devices seem to be correctly detected by the kernel: [ 28.963298] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=2 (0x14/0x1b/0x0/0x0/0x0) [ 28.963299] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 28.963300] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 28.963302] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [ 28.963302] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 28.963304] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 28.963306] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 28.975012] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input16 [ 28.975048] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input17 [ 28.975079] input: HDA Intel PCH Speaker Surround as /devices/pci:00/:00:1f.3/sound/card0/input18 but I can't find any devices for them under /dev: root@viper:~# find /dev | grep sound root@viper:~# find /dev | grep card -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
yes, that's where I've been looking. nothing listed for input or output in the sound control panel. ** Attachment added: "Screenshot from 2018-11-02 10-44-35.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+attachment/5208409/+files/Screenshot%20from%202018-11-02%2010-44-35.png -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Yes, that's because it doesn't appear like the issues you have are a
regression caused by the updates, and we don't know what's wrong. You
have a bug open for your issue, and we still need to figure out what
doesn't work there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope
[Touch-packages] [Bug 1797649] Re: receive authentication canceled in terminal when changing options in "Other Software"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1797649 Title: receive authentication canceled in terminal when changing options in "Other Software" Status in software-properties package in Ubuntu: Confirmed Bug description: I've tried to disable some PPAs in the "Other Software" tab of software-properties and whenever I check a box for the first time I get a message in the terminal about "ERROR:root:Authentication canceled, changes have not been saved" (although an authentication dialog has not appeared) and the dialog box greys out. However, frequently upon clicking the box for a second time (when it is greyed out) I am then presented with an authentication dialog. This seems quite odd. I've tested this the following versions of software-properties-gtk. 0.96.24.32.5 from bionic 0.26.27 from cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797649] Re: receive authentication canceled in terminal when changing options in "Other Software"
I can confirm Brian's experience _and_ I'm not prompted for authentication when launching the .desktop file from ubuntu-session. -- 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/1797649 Title: receive authentication canceled in terminal when changing options in "Other Software" Status in software-properties package in Ubuntu: Confirmed Bug description: I've tried to disable some PPAs in the "Other Software" tab of software-properties and whenever I check a box for the first time I get a message in the terminal about "ERROR:root:Authentication canceled, changes have not been saved" (although an authentication dialog has not appeared) and the dialog box greys out. However, frequently upon clicking the box for a second time (when it is greyed out) I am then presented with an authentication dialog. This seems quite odd. I've tested this the following versions of software-properties-gtk. 0.96.24.32.5 from bionic 0.26.27 from cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801394] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: 設定 lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) 11月 02 21:51:31 longman-UX510UX systemd[1]: Started LVM2 metadata daemon. 11月 03 00:05:57 longman-UX510UX systemd[1]: Stopping LVM2 metadata daemon... 11月 03 00:05:57 longman-UX510UX systemd[1]: Stopped LVM2 metadata daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.3) ... Processing triggers for initramfs-tools (0.130ubuntu3.5) ... update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic 處理時發生錯誤： lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Nov 3 01:10:15 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-11-17 (350 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-30 (2 days ago) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1801394 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: 設定 lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) 11月 02 21:51:31 longman-UX510UX systemd[1]: Started LVM2 metadata daemon. 11月 03 00:05:57 longman-UX510UX systemd[1]: Stopping LVM2 metadata daemon... 11月 03 00:05:57 longman-UX510UX systemd[1]: Stopped LVM2 metadata daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.3) ... Processing triggers for initramfs-tools (0.130ubuntu3.5) ... update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic 處理時發生錯誤： lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Nov 3 01:10:15 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-11-17 (350 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-30 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1801394/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package
** Description changed:
+ [Impact]
+ ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin
+
+ [Test Case]
+ 1) Run ubuntu-bug /snap/bin/juju
+ 2) Read "/snap/bin/juju does not belong to a package"
+
+ With the version of apport in -proposed you'll receive a more
+ informative message about where you might get help regarding the issue
+ you are experiencing.
+
+ [Regression Potential]
+ The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
+
+ Original Report
+ ---
apport's ui.py file contains the following code:
- 809 # executable?
- 810 elif '/' in self.args[0]:
- 811 pkg = apport.packaging.get_file_package(self.args[0])
- 812 if not pkg:
- 813 optparser.error('%s does not belong to a package.' %
self.args[0])
- 814 sys.exit(1)
- 815 self.args = []
- 816 self.options.filebug = True
- 817 self.options.package = pkg
+ 809 # executable?
+ 810 elif '/' in self.args[0]:
+ 811 pkg = apport.packaging.get_file_package(self.args[0])
+ 812 if not pkg:
+ 813 optparser.error('%s does not belong to a package.' %
self.args[0])
+ 814 sys.exit(1)
+ 815 self.args = []
+ 816 self.options.filebug = True
+ 817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
** Description changed:
[Impact]
- ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin
+ ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---
apport's ui.py file contains the following code:
809 # executable?
810 elif '/' in self.args[0]:
811 pkg = apport.packaging.get_file_package(self.args[0])
812 if not pkg:
813 optparser.error('%s does not belong to a package.' %
self.args[0])
814 sys.exit(1)
815 self.args = []
816 self.options.filebug = True
817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
** Changed in: apport (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: apport (Ubuntu Cosmic)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
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/1760220
Title:
ubuntu-bug with program path says as a snap does not belong to a
package
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
In Progress
Status in apport source package in Cosmic:
In Progress
Bug description:
[Impact]
ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---
apport's
[Touch-packages] [Bug 1801382] Re: printing complex documents does not reproduce screen image on paper
Checked by myself now. Opened the original file with evince, opened the print dialog and clicked the preview button. The preview already shows the problem. So the problem already occurs before the job gets to CUPS. It is a problem of evince and/or GTK. Moving ... ** Changed in: cups (Ubuntu) Status: Incomplete => Confirmed ** Package changed: cups (Ubuntu) => evince (Ubuntu) ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/1801382 Title: printing complex documents does not reproduce screen image on paper Status in evince package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1801382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801382] Re: printing complex documents does not reproduce screen image on paper
How did you print the file? Did you print it out of a PDF viewer? Which one? Could you try another PDF viewer or direct printing from the command line? In the PDF viewer with which you obtain the problem, does the print preview already show the problem? How did you obtain the file which you have attached to comment #2? ** 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/1801382 Title: printing complex documents does not reproduce screen image on paper Status in evince package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1801382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Hi Eric, I confirm that this behaviour can only be reproduced in 'uu' context and only in 'shutdown mode'. I can also confirm that the upgrade process is now OK in Bionic with your test package : - unattended-upgrades version after the test package installation : ii unattended-upgrades 1.1ubuntu1.18.04.6+testpkgb1 all automatic installation of security upgrades - dpkg status for linux-cloud-tools-common after reboot + 'uu' in 'shutdown mode' : ii linux-cloud-tools-common 4.15.0-36.39 all Linux kernel version specific cloud tools for version 4.15.0 - APT logs for linux-cloud-tools-common : Start-Date: 2018-11-02 16:28:56 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-cloud-tools-common:amd64 (4.15.0-34.37, 4.15.0-36.39) End-Date: 2018-11-02 16:29:01 Would it also be possible to backport the fix in Xenial, as this version is also impacted ? Thanks a lot for your help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: Confirmed Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 603128] Re: python-magic is incomplete on Ubuntu LTS?
** Tags removed: bionic cosmic ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/603128 Title: python-magic is incomplete on Ubuntu LTS? Status in file package in Ubuntu: Confirmed Bug description: Binary package hint: file I'm running Ubuntu 10.04 LTS. I installed python-magic with: sudo apt-get install python-magic (the file that gets installed is python-magic_5.03-5ubuntu1_i386.deb) However, when I start Python (version 2.6.5) and I "import magic" and I then do "dir(magic)", it seems as though the module does not contain all the definitions that I can see on python-magic's github repo (i.e. the Ubuntu package seems outdated): ['MAGIC_APPLE', 'MAGIC_CHECK', 'MAGIC_COMPRESS', 'MAGIC_CONTINUE', 'MAGIC_DEBUG', 'MAGIC_DEVICES', 'MAGIC_ERROR', 'MAGIC_MIME', 'MAGIC_MIME_ENCODING', 'MAGIC_MIME_TYPE', 'MAGIC_NONE', 'MAGIC_NO_CHECK_APPTYPE', 'MAGIC_NO_CHECK_CDF', 'MAGIC_NO_CHECK_COMPRESS', 'MAGIC_NO_CHECK_ELF', 'MAGIC_NO_CHECK_ENCODING', 'MAGIC_NO_CHECK_SOFT', 'MAGIC_NO_CHECK_TAR', 'MAGIC_NO_CHECK_TEXT', 'MAGIC_NO_CHECK_TOKENS', 'MAGIC_PRESERVE_ATIME', 'MAGIC_RAW', 'MAGIC_SYMLINK', '__doc__', '__file__', '__name__', '__package__', 'error', 'open'] What's up? Am I doing something wrong? Joubert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/603128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801382] Re: printing complex documents does not reproduce screen image on paper
** Attachment added: "This is the printed document with blackened images (s. page 7)" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801382/+attachment/5208359/+files/StepStone_Eyetracking_Whitepaper_after_printing_with_cups.pdf -- 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/1801382 Title: printing complex documents does not reproduce screen image on paper Status in cups package in Ubuntu: New Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801382] [NEW] printing complex documents does not reproduce screen image on paper
Public bug reported: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "Original PDF with embedded images" https://bugs.launchpad.net/bugs/1801382/+attachment/5208346/+files/StepStone_Eyetracking_Whitepaper.pdf -- 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/1801382 Title: printing complex documents does not reproduce screen image on paper Status in cups package in Ubuntu: New Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw:
[Touch-packages] [Bug 1780767] Re: Some tests are flaky due to timeout
** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Bionic) Status: New => In Progress ** Changed in: apport (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1780767 Title: Some tests are flaky due to timeout Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Bug description: The autopkgtests are sometimes passing, sometimes stuck for more than 2h: http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64. It's blocking randomly on different tests. All tests that are stucked, implements closing a request via a timeout (and then, executing "run"). The bet is that the timeout is short enough (1s) so that, when autopkgtests infra is busy, time to execute the bash subcommand is taking more than a second, and so "dismissing" is ran before execution happens and the whole testsuite hangs. There are few instances of setting this timeout function: $ grep eout_add_sec test/* test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) Short term solution could be to increase the timeout. Long term would be to eliminate this potential race implementing cancelling differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1741128] Re: libmagic1 in 16.04 reports XLS files as application/CDFV2-unknown
This bug was fixed upstream almost a year ago. It would be nice to see this addressed in Ubuntu 16.04 LTS, which is still on libmagic1 version 5.25. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1741128 Title: libmagic1 in 16.04 reports XLS files as application/CDFV2-unknown Status in file package in Ubuntu: Confirmed Bug description: The libmagic1 package repots XLS files as application/CDFV2-unknown This is a bug in the libmagic code and has been fixed in version 5.31 and up. see: https://github.com/mscdex/mmmagic/issues/107 We have a file transfer app running on LTS 16.04 and it's constantly rejecting files of .xls Deleted /companies/5412/FROM/RDMS_History.XLS Mime Type:application/CDFV2-unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1741128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784023] Re: Update profiles for usrmerge
I took a look because this appeared on the Debian package tracker for
apparmor-profiles-extra. At least 1.24 (just uploaded to sid) seems to
be OK. I've not checked older versions so I don't know when exactly the
problem that affected this package (which seems unspecified here) was
fixed. If there's anything left to fix in this package, please let me
know :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1784023
Title:
Update profiles for usrmerge
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
New
Status in dhcpcanon package in Ubuntu:
New
Status in ejabberd package in Ubuntu:
New
Status in firefox package in Ubuntu:
In Progress
Status in fwknop package in Ubuntu:
New
Status in i2p package in Ubuntu:
New
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in kopanocore package in Ubuntu:
New
Status in libvirt package in Ubuntu:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
Fix Released
Status in lightdm-remote-session-x2go package in Ubuntu:
Fix Released
Status in man-db package in Ubuntu:
Fix Released
Status in strongswan package in Ubuntu:
Fix Released
Status in surf package in Ubuntu:
New
Status in telepathy-mission-control-5 package in Ubuntu:
Fix Released
Status in strongswan package in Debian:
New
Bug description:
this is about / and /usr merge.
/bin & /sbin merge is out of scope. Anything that was in /sbin/ will
remain in /{,usr/}sbin/.
= src:apparmor =
usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles
upstream git tree
/usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs
= other packages =
Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/
$ sudo grep '[[:space:]]/bin' -r .
./usr.bin.man: /bin/bzip2 rmCx -> _filter,
./usr.bin.man: /bin/gzip rmCx -> _filter,
./usr.bin.man: /bin/bzip2 rm,
./usr.bin.man: /bin/gzip rm,
./usr.sbin.libvirtd: /bin/* PUx,
./abstractions/lightdm: /bin/ rmix,
./abstractions/lightdm: /bin/fusermount Px,
./abstractions/lightdm: /bin/** rmix,
./abstractions/libvirt-qemu: /bin/uname rmix,
./abstractions/libvirt-qemu: /bin/grep rmix,
./usr.bin.chromium-browser: /bin/ps Uxr,
./usr.bin.chromium-browser:/bin/dash ixr,
./usr.bin.chromium-browser:/bin/grep ixr,
./usr.bin.chromium-browser:/bin/readlink ixr,
./usr.bin.chromium-browser:/bin/sed ixr,
./usr.bin.chromium-browser:/bin/which ixr,
./usr.bin.chromium-browser:/bin/mkdir ixr,
./usr.bin.chromium-browser:/bin/mv ixr,
./usr.bin.chromium-browser:/bin/touch ixr,
./usr.bin.chromium-browser:/bin/dash ixr,
./usr.bin.firefox: /bin/which ixr,
./usr.bin.firefox: /bin/ps Uxr,
./usr.bin.firefox: /bin/uname Uxr,
./usr.bin.firefox:/bin/dash ixr,
./sbin.dhclient: /bin/bash mr,
$ sudo grep '[[:space:]]/sbin' -r .
./usr.lib.telepathy:deny /sbin/ldconfig x,
./usr.sbin.libvirtd: /sbin/* PUx,
./abstractions/lightdm: /sbin/ r,
./abstractions/lightdm: /sbin/** rmixk,
./usr.bin.firefox: /sbin/killall5 ixr,
./sbin.dhclient: /sbin/dhclient mr,
./sbin.dhclient: # daemon to run arbitrary code via /sbin/dhclient-script,
it would need to be
./sbin.dhclient: /sbin/dhclient-script Uxr,
$ sudo grep '[[:space:]]/lib' -r .
./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr,
# drop
./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
./abstractions/lightdm: /lib/ r,
./abstractions/lightdm: /lib/** rmixk,
./abstractions/lightdm: /lib32/ r,
./abstractions/lightdm: /lib32/** rmixk,
./abstractions/lightdm: /lib64/ r,
./abstractions/lightdm: /lib64/** rmixk,
./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
[Touch-packages] [Bug 902535] Re: Unable to print with Lexmark S400 series since upgrade to 11.10
** Attachment removed: "rou.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/902535/+attachment/5204779/+files/rou.png -- 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/902535 Title: Unable to print with Lexmark S400 series since upgrade to 11.10 Status in cups package in Ubuntu: Confirmed Status in cups source package in Precise: Incomplete Bug description: Following the upgrade from 11.04 to 11.10 my Lexmark S405 now is unable to print. After removing all previous drivers (i.e. from a clean install of the printer), I have two options to proceed: If I connect the printer via USB and wait for "auto-detection", the system is able to determine that a Lexmark S405 has been added (and adds the printer as a "S300-S400-Series". However at the same time I get the following error message: "Not supported by this backend. The action is not supported by this backend. Please report a bug as this should not have happened. Provided postscript-driver not supported" The printer is added and does show up in CUPS. The device URI is given as: "://Lexmark/S300-S400%20Series?serial=90T409817388744=1". Previously two packages were also added via the Software Centre ( "lexmark-legacy-wsu (1.0-1)" and "lexmark-inkjet-legacy-wjre (1.0-1)" but my most recent attempt to rectify this fault was following updates to fix bug 897309. On this occasion (following the updated ghostscript) no software was added via the Software Centre. I also have the drivers from Lexmark (the second install option). These drivers will install (but if they detect either of the above mentioned packages then installation will fail) but, once you are prompted to connect the printer via USB the error message highlighted above also appears. The results from this approach is that two printers are installed...but neither of them work. Either method of installing the printer results in the same scenario - the printer is listed as "installed", but items in the print queue remain there without no response from the printer. A Test Page shows the printer as "Processing page 1" before eventually throwing an error. Incidentally it is possible to scan from the printer (it's an all-in- one printer) into Ubuntu, but it seems to be impossible to print out from Ubuntu. Also previous work suggested that this may be connected to bug 883585. Also, despite CUPS referring to itself as 1.5, the intro screen says "what's new in CUPS 1.4". The printer does show up in CUPS, but it seems to be impossible to carry out any maintenance on the printer within CUPS (but this may be my "newbie-ness" showing though). My first bug report so hope I've included everything! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/902535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797040] Re: QtWebkit - missing doxygen tags file
Thanks. Committed as https://salsa.debian.org/qt-kde- team/qt/qt5webkit/commit/edfff7e6eeb3d08ccee40e059c26de3b5a3bd663, will be in the next upload. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)
Hi Eric,
This is the v3 debdiff with the patches updated to apply with no offset
messages per your request.
Thanks,
Mauricio
--
Applying patch debian/patches/1008-vf_trust_dddf1b44126e.patch
patching file include/linux/if_link.h
Applying patch debian/patches/1009-vf_trust_b6d77d9ee312.patch
patching file ip/iplink.c
patching file man/man8/ip-link.8.in
Applying patch debian/patches/1010-vf_trust_fe9322781e63.patch
patching file ip/ipaddress.c
Now at patch debian/patches/1010-vf_trust_fe9322781e63.patch
** Patch removed: "iproute2_xenial_vf-trust_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207902/+files/iproute2_xenial_vf-trust_v2.debdiff
** Patch added: "iproute2_xenial_vf-trust_v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5208317/+files/iproute2_xenial_vf-trust_v3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1800877
Title:
iproute2/xenial: Add support for the VF Trust setting (fix IPv6
multicast under SR-IOV on Mellanox adapters)
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
In Progress
Bug description:
[Impact]
* An VM's VF cannot receive IPv6 multicast traffic
from other VMs' VFs in the same Mellanox adapter
_if_ its VF trust setting is not enabled, and on
Xenial currently iproute2 _cannot_ enable it.
* This breaks IPv6 NDP (Neighbor Discovery Protocol)
in that scenario.
* This upload adds three iproute2 upstream commits
to enable/disable the VF setting, which resolves
that problem/limitation.
[Test Case]
* Check 'ip link help' for the 'trust' option:
Before:
# ip link help 2>&1 | grep trust
After:
# ip link help 2>&1 | grep trust
[ trust { on | off} ] ]
* Check 'ip link show dev PF' for 'trust on|off' field in VFs.
Before: (trust field _is not_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
After: (trust field _is_ present)
# ip link show dev ens1f0
...
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
* Set the VF trust on/off and check it:
Set VF 0 trust on:
# ip link set ens1f0 vf 0 trust on
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
Set VF 0 trust off:
# ip link set ens1f0 vf 0 trust off
# ip link show dev ens1f0 | grep trust
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
[Regression Potential]
* Regression potential is low because the commits just add the
netlink attribute for the userspace-kernel interface and the
ways to set/clear it, and show the current value to the user.
* Regressions could happen _if_ the user turns the setting on
(it's disabled by default) and there's a problem/bug likely
in _other_ component that depends on that setting (which is
something to fix on such component).
[Other Info]
* The users that reported this problem have verified
the test package with these changes, and confirmed
that it now works correctly for IPv6 NDP/multicast.
* Upstream commits:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312
* Only affect Xenial release :
# rmadison iproute2
iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
iproute2 | 4.15.0-2ubuntu1| bionic
iproute2 | 4.18.0-1ubuntu2| cosmic
iproute2 | 4.18.0-1ubuntu2| disco
# iproute2 upstream vcs
$ git describe --contains dddf1b44126e
v4.4.0~67
$ git describe --contains b6d77d9ee312
v4.5.0~47
$ git describe --contains fe9322781e63
v4.6.0~32
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working properly.
Cory, problem is not related, but I agree that this must be fix eventually in Ubuntu. I have to check if it was fix upstream. Can you please report a new bug about it ? -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Fix Released Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Fix Released Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in Disco: Invalid Status in systemd source package in Disco: Won't Fix Bug description: [Impact] * network menu in recovery mode doesn't work correctly, blocking at starting systemd services depends to enable networking. [Test Case] * Boot w/ Xenial or Bionic in recovery mode via grub * Choose "network" in friendly-recovery menu The network won't be activated and it'll be stuck at systemd-tty-ask- password : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask [Regression Potential] * Low. * All options works fine. * Cosmic has the same changes already in place. * According to xnox, resume option fails to boot now. After verification the 'resume' has the same effect before/after that change, it boots up but still seems to stick in 'recovery' option according to /proc/cmdline so I don't see any obvious behaviour change before and after. [Other Info] * Upstream : https://bazaar.launchpad.net/~ubuntu-core-dev/friendly-recovery/ubuntu/changes/161?start_revid=161 Revision 154 to 161 [Original Description] This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 805303] Re: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui
Uninstalling overlay-scrollbar package seems to work for me. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/805303 Title: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui Status in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in The Oneiric Ocelot: Fix Released Status in qt4-x11 source package in Oneiric: Fix Released Status in xorg-server source package in Oneiric: Invalid Bug description: vlc will hang when trying to open anything additional - it also appears to crash unity-window-decorator among other things (have crash report on that) Ex.'s - the playlist, tools > preferences and so forth Switching the qt4 gui to anything but 'default' (gtk+) in qtconfig-qt4 and it works without incidence (tooltips are empty bit otherwise good). Will attach xsession.errors, reflects a login, opening vlc, opening xsession.errors, then attempting to open playlist window in vlc. (using nvidia-current) Note to Vlc users - I've found clearlooks to be best choice, should be good for other apps as well. Also do as mentioned in comment 13 Note to Anki users - please review comments 20, 22 for current workaround This happens with many Qt4 and PyQt4 applications. Some errors displayed (from comments 16 and 18): (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed QWidget::setMinimumSize: (/MainWindow) The largest allowed size is (16777215,16777215) X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 X Error: BadAlloc (insufficient resources for operation) 11 Major opcode: 53 (X_CreatePixmap) Resource id: 0x15a X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension:152 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x42004f6 X Error: RenderBadPicture (invalid Picture parameter) 174 Extension:152 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x42004f6 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x42004f6 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: vlc 1.1.10-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-9.43lp760131v201106060906-generic 2.6.38.7 Uname: Linux 2.6.38-9-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun Jul 3 23:23:42 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to oneiric on 2011-07-03 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/805303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801325] Re: User processes/sessions lingering after logoff
Note that I filed this under ubuntu-mate because I only verified this behaviour under MATE, so I assumed it could be a mate-session-manager issue. Of course, I suspect it's really a systemd-logind problem, but I thought it might be wise to give it the benefit of the doubt… ;) -- 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/1801325 Title: User processes/sessions lingering after logoff Status in ubuntu-mate: In Progress Status in systemd package in Ubuntu: Confirmed Bug description: Hi! Logoff doesn't terminate all user processes/sessions, which means after mutiple logon/logoff operations lots of sessions and processes are leaking (you can see them with systemctl status). Verified with redshift(-gtk), at least. This can be worked around with KillUserProcesses=yes on /etc/systemd/logind.conf, but it breaks GNU Screen, for example. Tested on 18.04 and 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1801325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756324] Re: No signal after upgrading on 18.04
I having the same error with a clean install and am foreced to use 'nomodeset' just to get to the desktop. Any attempt to install the proper AMD drivers just puts me right back to a blackscreen on bootup. [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting Current Graphics: llvmpipe (LLVM 6.0, 128 bits) Cannot play Arma 3 on steam or any games for that matter as Open GL is not enabled. -- 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/1756324 Title: No signal after upgrading on 18.04 Status in xorg package in Ubuntu: Confirmed Bug description: Basically, yesterday I upgraded from 17.10 to 18.04 Bionic Beaver. At the reboot, when I boot onto Ubuntu, after the GRUB has been shown, it just boots to nothing, my screen display "No signal detected", although I can hear the drum sound. Using nomodeset works but my computer is set at a wrong frequency (stuck to 77Hz, even forcing via xrandr doesn't work). So using nomodeset I got into i3, downloaded mesa drivers and tried radeon too, and rebooted. Now still shows no signal, but I can get into a fluent 60Hz i3, if I go to recovery mode, then press normal boot. The problem also with that is that GNOME doesn't work, when I leave i3, log onto GNOME, it shows a blackscreen and just sends me back to the login menu. I've noticed this error appeared at boot: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Here's xrandr output: xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 0.00* 1280x1024 0.00 1024x768 0.00 800x6000.00 640x4800.00 Thanks for any future help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
Same question, will it be backported to Ubuntu 18.04 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Bionic: Confirmed Bug description: In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797040] Re: QtWebkit - missing doxygen tags file
Hi, Dmitry. The patch is pushed to upstream: https://github.com/annulen/webkit/commit/efa87bd9862e5c7b769efa137bf39d2b0efca264 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801354] [NEW] package dbus 1.12.2-1ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: While doing normal sudo apt get upgrade. Could be related to: https://bugs.launchpad.net/bugs/1485970 https://bugs.launchpad.net/bugs/1485266 https://bugs.launchpad.net/bugs/1487589 but an updated version? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Nov 2 13:04:40 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-07-12 (477 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-08-23 (71 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1801354 Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in dbus package in Ubuntu: New Bug description: While doing normal sudo apt get upgrade. Could be related to: https://bugs.launchpad.net/bugs/1485970 https://bugs.launchpad.net/bugs/1485266 https://bugs.launchpad.net/bugs/1487589 but an updated version? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Nov 2 13:04:40 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-07-12 (477 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-08-23 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1801354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
The testcase needs the “package test;” in the first line removed / commented-out, then it works. This works in 11.0.1+13-2 on Debian sid, as a new data point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: New Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801325] Re: User processes/sessions lingering after logoff
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1801325 Title: User processes/sessions lingering after logoff Status in ubuntu-mate: In Progress Status in systemd package in Ubuntu: Confirmed Bug description: Hi! Logoff doesn't terminate all user processes/sessions, which means after mutiple logon/logoff operations lots of sessions and processes are leaking (you can see them with systemctl status). Verified with redshift(-gtk), at least. This can be worked around with KillUserProcesses=yes on /etc/systemd/logind.conf, but it breaks GNU Screen, for example. Tested on 18.04 and 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1801325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801325] Re: User processes/sessions lingering after logoff
This is probably a systemd issue, but we can account for it and fix it in mate-session-manager. Working on a solution at the moment ** Changed in: ubuntu-mate Status: Invalid => In Progress ** Changed in: ubuntu-mate Assignee: (unassigned) => Victor Kareh (vkareh) -- 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/1801325 Title: User processes/sessions lingering after logoff Status in ubuntu-mate: In Progress Status in systemd package in Ubuntu: Confirmed Bug description: Hi! Logoff doesn't terminate all user processes/sessions, which means after mutiple logon/logoff operations lots of sessions and processes are leaking (you can see them with systemctl status). Verified with redshift(-gtk), at least. This can be worked around with KillUserProcesses=yes on /etc/systemd/logind.conf, but it breaks GNU Screen, for example. Tested on 18.04 and 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1801325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
PS: workaround by Mihai to mirror displays works for me too, to get something on the external display. Same as for Mihai, the display is not listed anywhere. Here is the xrandr output: xrandr Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192 eDP-1 connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 293mm x 164mm 1600x900 60.00*+ 59.9959.9459.9559.82 1440x900 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected 1600x900+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1600x900 60.00* DP-1 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525
[Touch-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Also affected with Asus Zenbook UX31E and Ubuntu 18.04.01. Cannot connect external display via HDMI. Tried to add the hdmi output manually with xrandr as well but I cannot get the external display to be listed anywhere. xrandr program version 1.5.0 Server reports RandR version 1.5 Looks like the Monitor gets some information about the HDMI cable being connected - but no display signal is received and monitor just goes to sleep. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052
[Touch-packages] [Bug 1799111] Proposed package upload rejected
An upload of qtbase-opensource-src to cosmic-proposed has been rejected from the upload queue for the following reason: "Per our IRC discussion, this should be fixed in the buggy tool, not the package that surfaced the bug.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1799111 Title: lots of Classes missing from docs (e.g. QFileInfo) Status in qtbase-opensource-src package in Ubuntu: New Status in qtbase-opensource-src package in Debian: Unknown Bug description: [Impact] The packaged Qt documentation, which can be viewed in browser (qt*-doc-html packages) or in Qt Assistant (qt*-doc packages) is missing all documentation generated from C++ files. Only the static text is present. Qt is split by many modules (qtbase, qtdeclarative, qtwebengine, etc.). I am now fixing it for qtbase, the largest module, but I may fix it for other modules if someone requests it. [Test Case] 1. Install qtbase5-doc-html package. 2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present. [Regression Potential] The proposed fix only adds a new build-dependency. There is absolutely no regression potential. [Other Info] Description of the fix: qdoc is a tool that parses C++ source files and generates documentation from them. Recently, qdoc began using clang instead of its own C++ parser. Clang needs the C++ standard library to work. qdoc build system uses a build-time macro (CLANG_RESOURCE_DIR) that hard- codes the path to standard library in the executable: https://code.qt.io/cgit/qt/qttools.git/tree/src/qdoc/qdoc.pro?h=5.11#n19. From qttools-opensource-src 5.11.1-5 build log in Cosmic amd64, one can see that qdoc was compiled with -D'CLANG_RESOURCE_DIR="/usr/lib/llvm-6.0/lib/clang/6.0.1/include"'. So this directory needs to be present when qdoc is used. This directory is provided by libclang-common-6.0-dev package. So adding it to build- dependencies makes the documentation build correctly. This is the minimal fix for Cosmic. For Ubuntu 19.04, I will try to use a better solution like moving the clang standard library detection from build time to run time, or making qttools5-dev-tools depend on the needed -dev packages. [Original Description] The Qt offline documentation for cosmic is incomplete. In fact there's virtually no content what so ever. It would be easier I think to list what actually got picked up that what was missed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
It's unclear if xenial's apt is affected or not, we did not get to testing that yet. ** Changed in: apt (Ubuntu Bionic) Status: New => Triaged ** Changed in: apt (Ubuntu) Status: New => Triaged ** Changed in: apt (Ubuntu Cosmic) Status: New => Triaged -- 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/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] [NEW] apt fails to properly handle server-side connection closure
Public bug reported: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. ** Affects: apt (Ubuntu) Importance: Undecided Status: Triaged ** Affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: apt (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: apt (Ubuntu Cosmic) Importance: Undecided Status: Triaged ** Tags: regression-update ** Tags added: regression-update ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
W: Der Download wird als root und nicht Sandbox-geschützt durchgeführt, da auf die Datei »/root/.synaptic/tmp//tmp_cl« durch den Benutzer »_apt« nicht zugegriffen werden kann. - pkgAcquire::Run (13: Keine Berechtigung) -- 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/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Vormals nicht ausgewähltes Paket xul-ext-lightning wird gewählt. (Lese Datenbank ... 360184 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../xul-ext-lightning_1%3a60.2.1+build1-0ubuntu0.18.04.2_amd64.deb ... Entpacken von xul-ext-lightning (1:60.2.1+build1-0ubuntu0.18.04.2) ... xul-ext-lightning (1:60.2.1+build1-0ubuntu0.18.04.2) wird eingerichtet ... W: Der Download wird als root und nicht Sandbox-geschützt durchgeführt, da auf die Datei »/root/.synaptic/tmp//tmp_cl« durch den Benutzer »_apt« nicht zugegriffen werden kann. - pkgAcquire::Run (13: Keine Berechtigung) Ubuntu 18.04 -> Linux Mint 19.0 x64 Cinnamon -- 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/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801325] Re: User processes/sessions lingering after logoff
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: New => Invalid -- 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/1801325 Title: User processes/sessions lingering after logoff Status in ubuntu-mate: Invalid Status in systemd package in Ubuntu: New Bug description: Hi! Logoff doesn't terminate all user processes/sessions, which means after mutiple logon/logoff operations lots of sessions and processes are leaking (you can see them with systemctl status). Verified with redshift(-gtk), at least. This can be worked around with KillUserProcesses=yes on /etc/systemd/logind.conf, but it breaks GNU Screen, for example. Tested on 18.04 and 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1801325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801320] [NEW] new icons on desktop should appear on primary display
Public bug reported: Have ubuntu 18.04 with communitheme Ubuntu is running on laptop (on my left side) while I have my external monitor in front of me (so on right side of the laptop), and primary desktop is on external monitor. If I create a new file on desktop the icon is aligned on left side is considering both screens, it should be aligned on left side only considering primary display. ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1801320 Title: new icons on desktop should appear on primary display Status in librsvg package in Ubuntu: New Bug description: Have ubuntu 18.04 with communitheme Ubuntu is running on laptop (on my left side) while I have my external monitor in front of me (so on right side of the laptop), and primary desktop is on external monitor. If I create a new file on desktop the icon is aligned on left side is considering both screens, it should be aligned on left side only considering primary display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1801320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801302] [NEW] Disconnected wired connection on dock after startup - reason 'carrier-changed' after update to 18.10
Public bug reported: I have a problem with wired connection while connected in docking station on startup after update from Ubuntu 18.04 to 18.10. HW info: Manufacturer: LENOVO Product Name: 20HGS27000 Version: ThinkPad T470s Serial Number: PC0MJA2W BIOS Version: N1WET51W (Release Date: 09/14/2018) System info: $ lsb_release -rd Description:Ubuntu 18.10 Release:18.10 $ apt-cache policy network-manager network-manager: Installed: 1.12.4-1ubuntu1 Candidate: 1.12.4-1ubuntu1 Version table: *** 1.12.4-1ubuntu1 500 500 http://sk.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -a Linux citadel 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Steps to reproduce: 1. Update Ubuntu from 18.04 to 18.10 2. Start the laptop on docking station 3. Laptop is trying to connect automatically on wired connection after startup, but not successfully. Log: $ journalctl -u NetworkManager nov 02 07:34:30 citadel NetworkManager[1158]: [1541140470.6335] device (enp0s31f6): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') nov 02 07:34:30 citadel NetworkManager[1158]: [1541140470.6979] dhcp4 (enp0s31f6): canceled DHCP transaction, DHCP client pid 3447 nov 02 07:34:30 citadel NetworkManager[1158]: [1541140470.6979] dhcp4 (enp0s31f6): state changed unknown -> done nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.3778] device (enp0s31f6): carrier: link connected nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.3780] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.3787] policy: auto-activating connection 'Wired connection' (9a6bb9a9-2739-4bdc-b853-0eec29c6e42d) nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.3797] device (enp0s31f6): Activation: starting connection 'Wired connection' (9a6bb9a9-2739-4bdc-b853-0eec29c6e42d) nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.3799] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.4719] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.4725] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.4728] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) nov 02 07:34:32 citadel NetworkManager[1158]: [1541140472.4778] dhcp4 (enp0s31f6): dhclient started with pid 3689 nov 02 07:34:32 citadel dhclient[3689]: DHCPREQUEST of 10.10.20.214 on enp0s31f6 to 255.255.255.255 port 67 (xid=0x687f173) nov 02 07:34:35 citadel dhclient[3689]: DHCPREQUEST of 10.10.20.214 on enp0s31f6 to 255.255.255.255 port 67 (xid=0x687f173) nov 02 07:34:38 citadel NetworkManager[1158]: [1541140478.4738] device (enp0s31f6): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') nov 02 07:34:38 citadel NetworkManager[1158]: [1541140478.5066] dhcp4 (enp0s31f6): canceled DHCP transaction, DHCP client pid 3689 nov 02 07:34:38 citadel NetworkManager[1158]: [1541140478.5067] dhcp4 (enp0s31f6): state changed unknown -> done nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.2266] device (enp0s31f6): carrier: link connected nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.2273] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.2298] policy: auto-activating connection 'Wired connection' (9a6bb9a9-2739-4bdc-b853-0eec29c6e42d) nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.2354] device (enp0s31f6): Activation: starting connection 'Wired connection' (9a6bb9a9-2739-4bdc-b853-0eec29c6e42d) nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.2361] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.3299] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.3315] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.3319] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) nov 02 07:34:40 citadel NetworkManager[1158]: [1541140480.3340] dhcp4 (enp0s31f6): dhclient started with pid 3739 nov 02 07:34:40 citadel dhclient[3739]: DHCPREQUEST of 10.10.20.214 on enp0s31f6 to
[Touch-packages] [Bug 1800272] Re: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- 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/1800272 Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Invalid Bug description: After update to 18.10 no sound in internal speakers and jackport. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 11:10:22 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (820 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-10-21 (6 days ago) dmi.bios.date: 02/14/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.00 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.3E dmi.chassis.asset.tag: CNU14045VQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.00:bd02/14/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.3E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 6460b dmi.product.sku: LG643EA#AKD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
Do you see the list via command `iw`? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800272] Re: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card
This helped to solve the problem. Thank you very much. -- 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/1800272 Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: After update to 18.10 no sound in internal speakers and jackport. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 11:10:22 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (820 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-10-21 (6 days ago) dmi.bios.date: 02/14/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.00 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.3E dmi.chassis.asset.tag: CNU14045VQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.00:bd02/14/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.3E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 6460b dmi.product.sku: LG643EA#AKD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
