[Touch-packages] [Bug 1798400]
Noticed that in the forthcoming LibO 24.2, the "remote" is being given prominence, by moving its settings from the Tools ▸ Options ▸ LibreOffice Impress configuration dialog to the Slide Show ▸ Slide Show Settings menu. IMHO this makes it quite important to have this feature working as intended on all the supported platforms. The remote is meant to work either with a WIFI connection or a Bluetooth one. The current bug is about the Bluetooth connection. Bluetooth Connection As of today, because of the issue at hand, the Bluetooth connection is completely unusable on standard Linux distributions that use Pulseaudio (a detailed discussion why is in the previous comments). Notwithstanding the fact that this but is about the Bluetooth connection, I am providing also a few notes about the Wifi connection to highlight why the Bluetooth connection is so important and should be fixed. WIFI Connection --- Unfortunately, the WIFI option is practically unusable in almost every professional working environment, including universities and conferencing sites. This is because in all these environments the network is completely out of the user control, restricted in any possible way, heavily firewalled, with the wifi framework consisting of multiple access points under the same SSID. In a similar arrangement the possibility of the remote to reach LibO at a non-standard TCP port is erratic if not negligible. The impossibility to use the WIFI connection precisely in those real world environments where the usage of the remote would be most important is the reason why a working Bluetooth connection is needed. Note that in practice the WIFI connection situation could be improved by suggesting the possibility to let the presenter laptop connect to the internet via the mobile phone hotspot. This would need the remote app to try to connect to LibO not just via the phone default interface, but also on the network used for the hotspot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor:
[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
After further investigation, I would say that "Discover" wants to upgrade a package (libmm-glib0) notwithstanding the fact that it is phased and that apt does not want to upgrade it. Funny enough, Discover does not indicate the other phased packages (it is up to 24!) as upgradable. -- 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/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately Status in apt package in Ubuntu: Triaged Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
There is a further problem, I do not know if it should be a separate issue. The updates icon in the system tray now appears also when there are in fact no updates that can be applied. Don't know if this actually depends on the presence of updates that are phased out or on the presence of Ubuntu Pro (esm-apps) that are not enabled. -- 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/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately Status in apt package in Ubuntu: Triaged Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
Noticed that among the many tips of the day, LibO also suggests to use Android or IPhone to remotely control an Impress presentation. The "more info" page then excplicitly declares that the feature is cross platform "GNU/Linux, Windows or macOS." either via Bluetooth or Wifi. However to use the feature with bluetooth on linux has been impossible for the last 5 years, because the feature is broken on this platform (this bug provides a diagnosis of the underlying issue). Using the feature with wifi is equally problematic, because those places where you need to deliver a presentation are typically those very places where you do not control the wifi network that may make it impossible for the computer and the phone to communicate. As a consequence, this tip of the day looks inappropriate on linux, making many users waste a significant amount of time trying to use a feature that simply cannot work. May I suggest removing this tip of the day on linux? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing
Would it then be possible to: 1. silence `apt upgrade` wrt the kept back packages 2. update `apt list --upgradable` to say which upgradable packages are phased out (i.e. not upgraded right now by `apt upgrade` 3. Update the bug report guidelines suggesting to `apt install` the troublesome package and retrying before opening a bug 4. update `aptitude` to behave as `apt` wrt to kept back packages? -- 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/1988819 Title: When apt keeps back packages due to phased updates, it should say nothing Status in apt package in Ubuntu: Triaged Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing
As the original reporter, I am a bit unconvinced by this change of perspective in how to fix the issue. I agree that being silent is easier, but does not feel quite the right thing to do for me, at least unless an option or something is added to see which upgrades are in progress and phased back. - It is untrue that from the user perspective these packages do not exist yet, as suggested. > from their perspective, the packages don't actually exist yet. The packages do exist and can be quite visible to the user. If you `apt install`, it is the most recent version of the packages that gets installed. - It is generally considered bad practice to open bugs without first trying the most recent version of some troublesome software Hiding the phased out packages takes away the opportunity to users who are experiencing problems to try the most recent version before opening a bug. - When neighboring machines start running different versions of the software and the user has the belief that they should be aligned because they use the same distribution, if trouble occurs the user may be lead to wrong conclusions (e.g. inculpate the hardware). Again the user should be able to easily check if there is the opportunity to try the last version of something when that something is giving trouble. - Finally, I am afraid that being non-transparent may lead users to develop non standard hacks to see (and maybe immediately install) the phased out packages. Incidentally, currently `aptitude upgrade` installs the phased out packages. -- 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/1988819 Title: When apt keeps back packages due to phased updates, it should say nothing Status in apt package in Ubuntu: Triaged Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988819] [NEW] When apt keeps back packages due to phased updates, it should say so
Public bug reported: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1988819 Title: When apt keeps back packages due to phased updates, it should say so Status in apt package in Ubuntu: New Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979079] [NEW] Can print to (brother) driverless printer only using aa-complain cupsd
Public bug reported: The apparmor configuration for cupsd is incorrect and makes it impossible to print to driverless printers (at least to the brother printer I am trying). Cups cannot obtain the IP address of the printer. You get "No suitable Destination Host found by cups-browsed" There are multiple reports of this issue on the network, also wrt debian. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-daemon 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 17 18:19:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (852 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-06-03 (14 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1979079 Title: Can print to (brother) driverless printer only using aa-complain cupsd Status in cups package in Ubuntu: New Bug description: The apparmor configuration for cupsd is incorrect and makes it impossible to print to driverless printers (at least to the brother printer I am trying). Cups cannot obtain the IP address of the printer. You get "No suitable Destination Host found by cups-browsed" There are multiple reports of this issue on the network, also wrt debian. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-daemon 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 17 18:19:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (852 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-06-03 (14 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1979079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
Is 2:2.10-6ubuntu2 the same as 2:2.10-9ubuntu1 in #76? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
#76 works here too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: New Bug description: wpa built with in openssl3 fails to connect to TLS 1.1 or lower server those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974040] Re: Cannot connect to PEAP wifi (eduroam)
*** This bug is a duplicate of bug 1958267 *** https://bugs.launchpad.net/bugs/1958267 Same issue here: the updated 2:2.10-6ubuntu1 version of wpasupplicant still gives wpa_supplicant[33522]: SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error wpa_supplicant[33522]: OpenSSL: openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal error wpa_supplicant[33522]: wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed Similarly, the workarounds in comments #22 and #36 in bug #1958267 do not work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1974040 Title: Cannot connect to PEAP wifi (eduroam) Status in wpa package in Ubuntu: Confirmed Bug description: Connection to wifi fails with May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL: openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal error Description:Ubuntu 22.04 LTS Release:22.04 wpasupplicant: Installed: 2:2.10-6ubuntu1 Candidate: 2:2.10-6ubuntu1 Version table: *** 2:2.10-6ubuntu1 1 (phased 40%) 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:2.10-6 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed May 18 15:13:41 2022 InstallationDate: Installed on 2019-10-22 (938 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: wpa UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
The bug is still there as of LibO 7.3.x. Up in comment 12 (https://bugs.documentfoundation.org/show_bug.cgi?id=120663#c12) there is a nice analysis of the underlying problem why the remote cannot work. Established that, I think that most users go used to the fact that the remote functionality does not work in linux. Personally, I have uninstalled the android app on the phone so I do not have an unfortunate reminder about it. In fact, the real issue is probably the advertisement of a functionality that is not there. For the time being I suggest disabling the remote-via-bluetooth functionality in linux and closing the bug by simply saying that the remote via bluetooth cannot be supported on linux where there are evidently issues that span other software pieces such as the bluetooth stack and pulse audio. To the best of my understanding, these involve the hijacking of the default rfcomm channel by pulse audio before it even needs it and the lack of a standard approach to let other applications find a free channel to use and advertise it to their counterparts. Alternatively (but I would not consider this a good solution), the configuration options could be enhanced to add the possibility to choose a bluetooth channel in libreoffice and in the mobile phone application, so that the user can manually work around the fact that the predefined channel is locked by some other application. As a final point, note that even if the remote-via-wifi may seem a good alternative, in fact in most cases it is practically useless. In most cases, presentations will not be given at a place where you control the network, but at sites with site-provided wifi, such as universities, schools, conference places, business sites, etc. All these locations tend to have wifi deployments that block stuff on the ports used by impress remote. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook
[Touch-packages] [Bug 1798400] Re: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic
Bug still there. In most situations the remote cannot be used at all. Not via bluetooth (because of this issue), neither via wifi (because you typically do presentations at sites where you do not control the wifi network and traffic to the relevant ports gets blocked). Suggested upstream some possible solutions including stop advertising the functionality. Consider closing as Wontfix because I think there is really nothing that downstream can do about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952784] [NEW] systemd-resolved cannot do dns over tls with server using self signed certificates
Public bug reported: While testing functionalities of knot resolver, I am experiencing issues in how systemd-resolved interacts with it. I have the caching and forwarding knot resolver running on a debian machine and systemd- resolved running on an ubuntu focal machine. It looks like systemd-resolved cannot communicate with kresd, when told to do so using dns over tls. I think that this is because kresd by default uses a self signed certificate for TLS and systemd-resolved does not like it. In fact, if I set dnsovertls on resolved and enable debug logging, I see in the journal entries like: Failed to invoke gnutls_handshake: Error in the certificate verification. and the name resolution fails: resolvectl query lwn.net lwn.net: resolve call failed: All attempts to contact name servers or networks failed On the other hand if I set dnsovertls to opportunistic, things seem to work, but the log reports that systemd-resolved is "Using degraded feature set UDP for DNS server". It is my understanding that systemd-resolved should accept self-signed certificates and should do certificate validation only if a special syntax is used for for specifying the DNS server to also include a hostname for the DNS server (see https://wiki.archlinux.org/title/Systemd-resolved#DNS_over_TLS). In fact, the documentation of systemd-resolved seems to be a bit thin on the matter, particularly because I understand that behaviors are changing across different systemd-resolved versions. In any case, being able to make systemd-resolved work with DoT with servers using self signed certificages would be very useful for testing and learning. Unfortunately, trying a more recent version of systemd-resolved is not really easy without firing up a virtual machine because it is impossible to update systemd-resolved independently of all the init system, with some obvious risk of breaking a system. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952784 Title: systemd-resolved cannot do dns over tls with server using self signed certificates Status in systemd package in Ubuntu: New Bug description: While testing functionalities of knot resolver, I am experiencing issues in how systemd-resolved interacts with it. I have the caching and forwarding knot resolver running on a debian machine and systemd- resolved running on an ubuntu focal machine. It looks like systemd-resolved cannot communicate with kresd, when told to do so using dns over tls. I think that this is because kresd by default uses a self signed certificate for TLS and systemd-resolved does not like it. In fact, if I set dnsovertls on resolved and enable debug logging, I see in the journal entries like: Failed to invoke gnutls_handshake: Error in the certificate verification. and the name resolution fails: resolvectl query lwn.net lwn.net: resolve call failed: All attempts to contact name servers or networks failed On the other hand if I set dnsovertls to opportunistic, things seem to work, but the log reports that systemd-resolved is "Using degraded feature set UDP for DNS server". It is my understanding that systemd-resolved should accept self-signed certificates and should do certificate validation only if a special syntax is used for for specifying the DNS server to also include a hostname for the DNS server (see https://wiki.archlinux.org/title/Systemd-resolved#DNS_over_TLS). In fact, the documentation of systemd-resolved seems to be a bit thin on the matter, particularly because I understand that behaviors are changing across different systemd-resolved versions. In any case, being able to make systemd-resolved work with DoT with servers using self signed certificages would be very useful for testing and learning. Unfortunately, trying a more recent version of systemd-resolved is not really easy without firing up a virtual machine because it is impossible to update systemd-resolved independently of all the init system, with some obvious risk of breaking a system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950850] Re: Systemd-resolved gets confused and replies to SOA queries for local breaking mDNS resolution
Looks like the DNS provided by Cloudflare (1.1.1.1 and 1.0.0.1) has picked up with standards and is also delivering NXDOMAIN together with an authority section with a SOA when you query anything in local. . 86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2021112100 1800 900 604800 86400 Hence also cloudflare is now unusable with the default configuration of ubuntu 20.04 because it ends up breaking local name resolution via mDNS. This follows from the fact that ubuntu focal relies on systemd-resolved by default and uses version 245.4 which is broken as per this bug (and also unsupported by upstream that would like not to be questioned for anything apart the last two versions). I have been pointed to a PPA providing daily builds of systemd, but obviously replacing your init system daily with the associated risk of breaking boot and not being able to access apt to restore the system is not feasible outside of a test-and-throw-away virtual machine. Please, try to have this bug fixed, because having a broken DNS stub resolver by default is a bit of a pain. If possible, also try to (downstream) decouple initialized services from init supervision itself so that when a service like systemd-resolved reveals an issue it is possible to try addressing it without having to replace the whole of the init system — risking serious system breakage — or without having to move to a different codebase to provide the same or a similar service — overriding the system default. -- 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/1950850 Title: Systemd-resolved gets confused and replies to SOA queries for local breaking mDNS resolution Status in systemd package in Ubuntu: New Bug description: As discussed on https://gitlab.nic.cz/knot/knot-resolver/-/issues/686, DNS servers are expected to immediately answer any queries within local by NXDOMAIN. See https://datatracker.ietf.org/doc/html/rfc6762#section-22.1 in this respect. However, while they do so they seem to be also expected to deliver an AUTHORITY section with a SOA. As a matter of fact, I am being told the relevant RFCs do not explicitly mention that SOA should be there, but that NXDOMAIN without a SOA is generally considered incorrect, e.g. it necessarily causes caching issues due to missing TTL. The problem is that such SOA confuses systemd-resolved (at least the version distributed with Ubuntu Focal) that ends up converting the NXDOMAIN reply into a positive reply with such a SOA. The final consequence is that local name resolution via mDNS is broken with the default ubuntu focal setup. A detailed discussion of the matter and of the scenario triggering the issue follows. Suppose that on your network you have a DNS server following the .local blocking indicated in https://datatracker.ietf.org/doc/html/rfc6762#section-22.1 (bullet 4). An example of a modern DNS that has already implemented this feature is knot resolver and the feature is also present in some routers notably the Turris Omnia series. Such a DNS server would reply to queries to local in this way: $ dig local ;; WARNING: .local is reserved for Multicast DNS ;; You are currently testing what happens when an mDNS query is leaked to DNS ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56352 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;local. IN A ;; AUTHORITY SECTION: local. 10800 IN SOA local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT “Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use- domain-names.xhtml” Now let's see what happens to Ubuntu Focal hosts when such a DNS server is deployed in the network and you try to reach a local host: 1. You do something like ping foo.local or ssh foo.local 2. Ubuntu focal has by default the host field in nsswitch.conf set to: hosts: files mdns4_minimal [NOTFOUND=return] dns so it tries the /etc/hosts/ file and then mdns via the nss mdns4_minimal client 3. The mdns4_minimal client before doing anything else tries unicast DNS looking for a SOA for local. This mechanism is present in the mdns4_minimal client to avoid issues when local is under DNS control and is documented at https://github.com/lathiat/nss-mdns/blob/master/README.md 4. Ubuntu focal uses by default systemd-resolved as a caching DNS, so the query from mdns4_minimal gets to systemd-resolved 5. systemd-resolved passes the query to the DNS it is configured to use. If this is a modern DNS server blocking local it gets
[Touch-packages] [Bug 1950520] Re: systemd-resolved delivers SOA information when it should not
Thanks, I'll try that and try to report. I have already asked on various forums if there is any way to replace /only/ the stub resolver (systemd- resolved) with a more recent version without replacing all the code related to init and the system initialization and been told there is no safe way, hence I understand the fact that ubuntu has a single package for the whole of systemd. Unfortunately, that means that even if https://launchpad.net/~ubuntu- support-team/+archive/ubuntu/systemd fixes the issue in a vm it will probably be impossible to practically deploy daily updated init, etc on a machine that must be reliably on daily use. On the other side, I have found that it is relatively easy to workaround the issue in systemd-resolved by making the local DNS server slightly deviate from standards so that it responds SERVERFAIL instead of NXDOMAIN for queries in .local. As a final note, as mentioned above, I have moved this discussion by closing this issue and opening a new one, where the problem in systemd- resolved is properly identified. Please see bug 1950850. -- 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/1950520 Title: systemd-resolved delivers SOA information when it should not Status in systemd package in Ubuntu: Invalid Bug description: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd-resolved than the one shipped in ubuntu focal. Interestingly, the issue seems to bite those running omnia turris router too (see https://forum.turris.cz/t/avahi-local-domain-warning- on-ubuntu/13437). Maybe they use knot-resolver as their caching nameserver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950850] [NEW] Systemd-resolved gets confused and replies to SOA queries for local breaking mDNS resolution
Public bug reported: As discussed on https://gitlab.nic.cz/knot/knot-resolver/-/issues/686, DNS servers are expected to immediately answer any queries within local by NXDOMAIN. See https://datatracker.ietf.org/doc/html/rfc6762#section-22.1 in this respect. However, while they do so they seem to be also expected to deliver an AUTHORITY section with a SOA. As a matter of fact, I am being told the relevant RFCs do not explicitly mention that SOA should be there, but that NXDOMAIN without a SOA is generally considered incorrect, e.g. it necessarily causes caching issues due to missing TTL. The problem is that such SOA confuses systemd-resolved (at least the version distributed with Ubuntu Focal) that ends up converting the NXDOMAIN reply into a positive reply with such a SOA. The final consequence is that local name resolution via mDNS is broken with the default ubuntu focal setup. A detailed discussion of the matter and of the scenario triggering the issue follows. Suppose that on your network you have a DNS server following the .local blocking indicated in https://datatracker.ietf.org/doc/html/rfc6762#section-22.1 (bullet 4). An example of a modern DNS that has already implemented this feature is knot resolver and the feature is also present in some routers notably the Turris Omnia series. Such a DNS server would reply to queries to local in this way: $ dig local ;; WARNING: .local is reserved for Multicast DNS ;; You are currently testing what happens when an mDNS query is leaked to DNS ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56352 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;local. IN A ;; AUTHORITY SECTION: local. 10800 IN SOA local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT “Blocking is mandated by standards, see references on https://www.iana.org/assignments/special- use-domain-names/special-use-domain-names.xhtml” Now let's see what happens to Ubuntu Focal hosts when such a DNS server is deployed in the network and you try to reach a local host: 1. You do something like ping foo.local or ssh foo.local 2. Ubuntu focal has by default the host field in nsswitch.conf set to: hosts: files mdns4_minimal [NOTFOUND=return] dns so it tries the /etc/hosts/ file and then mdns via the nss mdns4_minimal client 3. The mdns4_minimal client before doing anything else tries unicast DNS looking for a SOA for local. This mechanism is present in the mdns4_minimal client to avoid issues when local is under DNS control and is documented at https://github.com/lathiat/nss-mdns/blob/master/README.md 4. Ubuntu focal uses by default systemd-resolved as a caching DNS, so the query from mdns4_minimal gets to systemd-resolved 5. systemd-resolved passes the query to the DNS it is configured to use. If this is a modern DNS server blocking local it gets NXDOMAIN together withthat special SOA in the authority section and because it is buggy, it turns it into a regular SOA reply (no NXDOMAIN) 6. mdns4_minimal receives a SOA reply for local and gives up thinking that in the particular environment local is under unicast DNS control 7. At this point, according to the nsswitch configuration, DNS is tried. So we are back to systemd-resolved now trying to get the A field for foo.local. 8. By default systemd-resolved on ubuntu is configured not to do mDNS itself (even if it has this capability). Hence the query fails. 9. Rather than reaching foo.local you get an error. This is a nasty but, although it is possibly not frequently hit yet because the number of DNS servers that have already implemented local blocking is probably modest. You can only expect it to be on the rise, though. It may be the case that more recent versions of systemd than the one shipped in Ubuntu Focal have already corrected the issue. Preliminary tests on arch seem to support this hypothesis. If this is the case, it may be possible to backport the fix. In any case, I think that an update to the Ubuntu Focal systemd package should be provided, because Focal deployments are expected to exist for many years ahead. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1950850 Title: Systemd-resolved gets confused and replies to SOA queries for local breaking mDNS resolution Status in systemd package in Ubuntu: New Bug description: As discussed on https://gitlab.nic.cz/knot/knot-resolver/-/issues/686, DNS servers are expected to immediately answer any queries within local by NXDOMAIN. See https://datatracker.ietf.org/doc/html/rfc6762#section-22.1 in this respect. However,
[Touch-packages] [Bug 1950520] Re: systemd-resolved delivers SOA information when it should not
Marked by myself the issue as invalid, since when I reported the issue my understanding of it was to o modest. Will open a new more appropriate issue. ** Changed in: systemd (Ubuntu) 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/1950520 Title: systemd-resolved delivers SOA information when it should not Status in systemd package in Ubuntu: Invalid Bug description: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd-resolved than the one shipped in ubuntu focal. Interestingly, the issue seems to bite those running omnia turris router too (see https://forum.turris.cz/t/avahi-local-domain-warning- on-ubuntu/13437). Maybe they use knot-resolver as their caching nameserver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950520] Re: systemd-resolved delivers SOA information when it should not
Unfortunately, I have no idea on how to bisect this, due to the fact that there is not an independent repo for systemd-resolved and attempting to work on the whole systemd seems to dounting and risky as an experience for me. Is there a ppa with a more recent systemd- resolved to try on focal without the risk of breaking all the system init? Is it possible to compile just the resolve subtree from the systemd sources? -- 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/1950520 Title: systemd-resolved delivers SOA information when it should not Status in systemd package in Ubuntu: New Bug description: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd-resolved than the one shipped in ubuntu focal. Interestingly, the issue seems to bite those running omnia turris router too (see https://forum.turris.cz/t/avahi-local-domain-warning- on-ubuntu/13437). Maybe they use knot-resolver as their caching nameserver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950520] Re: systemd-resolved delivers SOA information when it should not
Tested on a manjaro system that being rolling uses the latest systemd. There is no issue there. Hence the problem appears to be a systemd-resolved bug specific to the systemd version shipped with ubuntu 20.04. Because the issue breaks local resolution via mDNS in some configurations, I think that the fix that has evidently been made in recent systemd-resolved should be backported. -- 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/1950520 Title: systemd-resolved delivers SOA information when it should not Status in systemd package in Ubuntu: New Bug description: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd-resolved than the one shipped in ubuntu focal. Interestingly, the issue seems to bite those running omnia turris router too (see https://forum.turris.cz/t/avahi-local-domain-warning- on-ubuntu/13437). Maybe they use knot-resolver as their caching nameserver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950520] [NEW] systemd-resolved delivers SOA information when it should not
Public bug reported: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd- resolved than the one shipped in ubuntu focal. Interestingly, the issue seems to bite those running omnia turris router too (see https://forum.turris.cz/t/avahi-local-domain-warning-on- ubuntu/13437). Maybe they use knot-resolver as their caching nameserver. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1950520 Title: systemd-resolved delivers SOA information when it should not Status in systemd package in Ubuntu: New Bug description: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd-resolved than the one shipped in ubuntu focal.
[Touch-packages] [Bug 1926737] [NEW] Lack of permissions to access display on X11 causes QT to dump core
Public bug reported: Lack of permissions to access the display causes QT to dump core. You get Qt WARNING: could not connect to display Qt FATAL: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted (core dumped) but this should not be a condition to abort with a core dump, rather a mere error on which the application should exit (as I believe it used to do until not long ago) To trigger the issue it is enough to be on X11, su to another user (not having permission to use the display) try to launch a QT application from that user. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libqt5core5a 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Apr 30 11:31:57 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (439 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to focal on 2020-05-23 (342 days ago) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Description changed: - Lack of permissions to access the display causes X11 to dump core. + Lack of permissions to access the display causes QT to dump core. You get - Qt WARNING: could not connect to display + Qt WARNING: could not connect to display Qt FATAL: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted (core dumped) but this should not be a condition to abort with a core dump, rather a mere error on which the application should exit (as I believe it used to do until not long ago) To trigger the issue it is enough to be on X11, su to another user (not having permission to use the display) try to launch a QT application from that user. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libqt5core5a 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Apr 30 11:31:57 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (439 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to focal on 2020-05-23 (342 days ago) -- 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/1926737 Title: Lack of permissions to access display on X11 causes QT to dump core Status in qtbase-opensource-src package in Ubuntu: New Bug description: Lack of permissions to access the display causes QT to dump core. You get Qt WARNING: could not connect to display Qt FATAL: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted (core dumped) but this should not be a condition to abort with a core dump, rather a mere error on which the application should exit (as I believe it used to do until not long ago) To trigger the issue it is enough to be on X11, su to another user (not having permission to use the display) try to launch a QT application from that user. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libqt5core5a 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Apr 30 11:31:57 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (439 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to focal on 2020-05-23 (342 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 1920781] Re: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
Happened again today. How do you disable dnssec completely in systemd-resolved? resolvectl does not seem to have an option for that. Is editing resolved.conf and restarting resolved the only way? In any case I could not try, I was too much on a hurry and reconfiguring network manager to use google dns for the connection was quicker. Still: why should one need to disable dnssec globally when there is a per connection setting? -- 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/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1920781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920781] [NEW] Mobile phone hotspot unusable due to systemd-resolved not liking the DNS
Public bug reported: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Mar 22 15:39:23 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (400 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (303 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-02-10T11:20:21.512139 mtime.conffile..etc.systemd.sleep.conf: 2020-08-13T07:55:23.365733 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1920781 Title: Mobile phone hotspot unusable due to systemd-resolved not liking the DNS Status in systemd package in Ubuntu: New Bug description: Seen in 20.04. Trying to connect to the internet using the mobile phone hotspot is impossible due to systemd-resolved not resolving and reporting things like: resolve call failed: DNSSEC validation failed: incompatible-server and systemd-resolved[81699]: DNSSEC validation failed for question d.3.1.b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature DNSSEC validation failed for question b.d.e.1.e.1.6.9.e.7.8.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature etc etc. Name resolution works just fine from the mobile phone. Funny thing is that the issue persists if DNSSEC is disabled via resolvectl for the interface: Link 3 (wlan0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: opportunistic DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.43.1 DNS Servers: 192.168.43.1 Systemd-resolved won't accept the issue to be reported upstream saying that a too old version of systemd is being used. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.5 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip
[Touch-packages] [Bug 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10
Still true of the deb packages provided by upstream for Virtualbox 6.1.18. The problem is really with the packaging on their side which does not target ubuntu 20.10. In fact, they say so by indicating that they have a deb up to 19.10 and 20.04. I guess there is little that ubuntu can do if Virtualbox does not want to package a deb for ubuntu 20.10 that is not an LTS. Most likely, they'll stick to 20.04 and start supporting newer ubuntu at 21.10 in preparation for the 22.04 LTS release. On the other hand, I believe that ubuntu could help a lot here by making the current virtualbox always available in testing version on a PPA. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 Status in dh-python package in Ubuntu: Confirmed Status in what-is-python package in Ubuntu: Incomplete Bug description: Sorry I couldn't file this bug against the correct packages. The form told me there are no such packages as python-is-python3 and dh-python in Ubuntu... Release: Groovy Gorilla (Ubuntu 20.10). Package versions: python-is-python3 3.8.2-4 dh-python 4.20200925 The release of Ubuntu 20.10 is less than two weeks out, so I'd like to draw attention to a problem I've run into. It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it. I don't mind having _both_ python2 (apparently a requirement of VirtualBox) and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh- python and python-six. Ia there something the python packagers do about this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1899288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883793] Re: systemd-resolved leaks mDNS queries to DNS
Finished my investigation. Guess it is not a bug after all, rather — I would say — a matter of extremely dispersed documentation plus very unfriendly behavior from the ISP. The situation is that even if you put mdns_minimal in front of other entries in hosts in nsswitch, mdns /is not queried/ if the DNS declares SOA for the "local" domain. Mine does. This is the reason why I was getting the impression of systemd-resolved passing queries to DNS even when it should not have. It was actually nss_mdns to let it do so. The fact that for some time my isp has directed all dns queries to its own nameserver even when another one was selected did not help in verifying the behavior with a dns not declaring SOA for local. Yet, this aspect of the linux mdns implementation should be documented with much better emphasis, or even better, there should be a way to make mdns_minimal report/log what it is doing. Currently, you find mention of the mdns "handover" to dns for local only looking at the very end of /usr/share/doc/libnss-mdns/README.md.gz where the heuristics is explained. Because heuristics /can go wrong/, the item should IMHO be given much better emphasis. For instance, I suggest that ubuntu ships with a man page for nss_mdns and nss_mdns_minimal. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Package changed: systemd (Ubuntu) => nss-mdns (Ubuntu) -- 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/1883793 Title: systemd-resolved leaks mDNS queries to DNS Status in nss-mdns package in Ubuntu: Invalid Bug description: On a freshly installed ubuntu focal machine, access to local machines advertised via mDNS is now broken. This is a regression wrt eoan where it used to work. Trying to ping something like .local invariably results in pinging 40.68.249.35 because systemd-resolved passes the query to the DNS even if .local is reserved for multicast DNS and for some reasons .local seems to resolve to 40.68.249.35. This happens even if the avahi daemon is up and running. Stopping systemd-resolved makes the mDNS resolution work as expected. Not only this breaks standard workflows, but it also means that anyone pretending to be 40.68.249.35 on the network could probably impersonate any local host. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 16 23:43:22 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (121 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (24 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1883793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883793] Re: systemd-resolved leaks mDNS queries to DNS
Host entry in nsswitch.conf is: files mdns4_minimal [NOTFOUND=return] dns Note that I do not see the issue anymore, because the ISP has (for the time being) stopped messing so aggressively with dns. In any case, I've moved to using dns over tls which systemd.resolved supports perfectly with 1.1.1.1 or 9.9.9.9, which should prevent the isp from troubling me even if they restart doing weird things (wonder if it was some sort of experiment on their side). Nonetheless, I believe that the system should avoid breaking .local resolution and obey the priorities in the nsswitch file. -- 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/1883793 Title: systemd-resolved leaks mDNS queries to DNS Status in systemd package in Ubuntu: New Bug description: On a freshly installed ubuntu focal machine, access to local machines advertised via mDNS is now broken. This is a regression wrt eoan where it used to work. Trying to ping something like .local invariably results in pinging 40.68.249.35 because systemd-resolved passes the query to the DNS even if .local is reserved for multicast DNS and for some reasons .local seems to resolve to 40.68.249.35. This happens even if the avahi daemon is up and running. Stopping systemd-resolved makes the mDNS resolution work as expected. Not only this breaks standard workflows, but it also means that anyone pretending to be 40.68.249.35 on the network could probably impersonate any local host. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 16 23:43:22 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (121 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (24 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902539] Re: Intel iris graphic driver breaks java applications in ubuntu 20.04
Tested with latest mesa 20.3 from oibaf ppa and issue is still present. Same behavior is also observed with the zink driver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902539 Title: Intel iris graphic driver breaks java applications in ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: Both Matlab and Scilab (which are java based) fail when using the iris graphics driver. As a workaround you can make them work using MESA_LOADER_DRIVER_OVERRIDE=i965 There is a bug open for scilab at https://bugzilla.scilab.org/show_bug.cgi?id=13830 (in fact one of the issues marked as a duplicate there does probably contain more info). On the Matlab camp, the issue is known to the Matlab developers. However, it is really not an issue in Matlab, so they can only advice to use the i965 driver. The issue may be either in the Intel Iris driver, or in jogl (the java library that all these projects use for opengl). I would tend to think that the issue is in the iris driver not providing a proper opengl 3 compatibility profile (needed by jogl), but I am unsure about it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Nov 2 16:07:33 2020 DistUpgraded: 2020-05-23 08:30:58,391 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics [1558:1403] InstallationDate: Installed on 2020-02-16 (260 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to focal on 2020-05-23 (163 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902539] [NEW] Intel iris graphic driver breaks java applications in ubuntu 20.04
Public bug reported: Both Matlab and Scilab (which are java based) fail when using the iris graphics driver. As a workaround you can make them work using MESA_LOADER_DRIVER_OVERRIDE=i965 There is a bug open for scilab at https://bugzilla.scilab.org/show_bug.cgi?id=13830 (in fact one of the issues marked as a duplicate there does probably contain more info). On the Matlab camp, the issue is known to the Matlab developers. However, it is really not an issue in Matlab, so they can only advice to use the i965 driver. The issue may be either in the Intel Iris driver, or in jogl (the java library that all these projects use for opengl). I would tend to think that the issue is in the iris driver not providing a proper opengl 3 compatibility profile (needed by jogl), but I am unsure about it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Nov 2 16:07:33 2020 DistUpgraded: 2020-05-23 08:30:58,391 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics [1558:1403] InstallationDate: Installed on 2020-02-16 (260 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to focal on 2020-05-23 (163 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902539 Title: Intel iris graphic driver breaks java applications in ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: Both Matlab and Scilab (which are java based) fail when using the iris graphics driver. As a workaround you can make them work using MESA_LOADER_DRIVER_OVERRIDE=i965 There is a bug open for scilab at https://bugzilla.scilab.org/show_bug.cgi?id=13830 (in fact one of the issues marked as a duplicate there does probably contain more info). On the Matlab camp, the issue is known to the Matlab developers. However, it is really not an issue in Matlab, so they can only advice to use the i965 driver. The issue may be either in the Intel Iris driver, or in jogl (the java library that all these projects use for opengl). I would tend to think that the issue is in the iris driver not providing a proper opengl 3 compatibility profile (needed by jogl), but I am unsure about it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Nov 2 16:07:33 2020 DistUpgraded: 2020-05-23 08:30:58,391 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes
[Touch-packages] [Bug 1798400]
The premise is that my ignorance on BT is complete. After some investigation, it is my understanding that RFCOMM channels are to RFCOMM communication a bit like ports in TCP and UDP, with the main difference that while there are really a lot of TCP/UDP ports and some of them are reserved as "well known ports", the number of channels in RFCOMM is extremely limited, so that there cannot be well known ports. Furthermore, I understand that no one should "hardwire" RFCOMM channels and that channels should be released whenever not strictly needed. If this understanding from myself is correct, there may be issues both in LibO and in PA. >From my understanding: - LibO and the Impress remote should not hardwire RFCOMM channel 3. I understand that they should dynamically allocate a channel and make it discoverable via SDP. - Impress should not keep binded to an RFCOMM channel all the time. There should be a visible option to switch on and off the binding (probably there should be a couple of impress remote related options in the "Slide Show -> Slide Show Settings" window, including one to fire up the BT rfcomm binding). - PA should probably similarly not hardwire channel 3 for its HSP role, but here the situation seems more complex, because it may be the case that PA needs to strive for compatibility with devices that do not play to the rules. - PA should probably have a DBUS interface to switch on and off the RFCOMM binding, so that to use an application needing RFCOMM channel 3, one does not need to take down the whole of PA. I have opened a bug on PA too. See it at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/827. That report is bad, because when I made it my understanding of BT was even poorer than it is now. In any case, it seems to me that the current issue could be fixed completely on the LibO side, by dynamically allocating the channel and by letting the app running on the phone discover it via SDP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not
[Touch-packages] [Bug 1798400]
Thanks for the analysis! >From it, I still wonder whether this is a pulseaudio bug, though. Why is pulseaudio ever binding to RFCOMM channel 3 *before* there is any need to do so? That is, until I am not connected to any device using channel 3, why is pulseaudio already using it up? In other words, it seems reasonable to me to have the laptop connected to the phone as a headset and in this case not to have the impress remote working. But in case I start impress before setting up a bluetooth connection to the phone, why should be the pulseaudio binding already there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
Andrzej, I am CC-ing you on this, because I believe that you were one of the original corder of the BT code for the impress remote on linux. I hope that you may able to provide some advice on this. If I'm wrong, please take my apology for the noise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
The bug is also confirmed in the ubuntu launchpad at https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400. Users there are reporting that they are experiencing the issue in ubuntu (from bionic, I think) and gentoo. This adds to the reports in fedora and to the confirmation here on arch linux. I think that this is enough to mark as "NEW" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
Issue still present in LibO 6.4.3.1. I see the bug as still unconfirmed after more than one year. I wonder if it could be confirmed, given that the same issue has also been reported for redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1581879) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
@John Poole Can you please indicate that you are also experiencing the issue in the issue tracker at the document foundation at https://bugs.documentfoundation.org/show_bug.cgi?id=120663 ? The issue is still "unconfirmed" there, and until it is "confirmed" by multiple reporters, there is little chance that it can be dealt with. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853242] Re: Regression in Eoan: cannot print to smb connected printer
Actually not a bug, for sure not the one indicated for Fedora. Just a very poor interaction of the Kyocera DEB package with the Disco->Eoan upgrade. ** Changed in: cups (Ubuntu) Status: New => Invalid ** Changed in: samba (Ubuntu) Status: New => Invalid -- 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/1853242 Title: Regression in Eoan: cannot print to smb connected printer Status in cups package in Ubuntu: Invalid Status in samba package in Ubuntu: Invalid Bug description: After upgrade from disco to eoan, notwithstanding the fact that /etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb connected printer provided by my Institution. The connection uses authentication and username, password are present in the smb url in the printers.conf file. May be the same regression as in Fedora 30 https://bugzilla.redhat.com/show_bug.cgi?id=1706090 Issue prevents upgrading to eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853242] Re: Regression in Eoan: cannot print to smb connected printer
Running cups in debug mode (cupsctl --debug-logging) in the logs I see a couple of interesting lines: [Job 1008] PID 2888 (/usr/lib/cups/backend/smb) stopped with status 2. ... [Job 1008] Unable to connect to CIFS host: NT_STATUS_INVALID_ACCOUNT_NAME ... [Job 1008] Backend returned status 2 (authentication required) -- 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/1853242 Title: Regression in Eoan: cannot print to smb connected printer Status in cups package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: After upgrade from disco to eoan, notwithstanding the fact that /etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb connected printer provided by my Institution. The connection uses authentication and username, password are present in the smb url in the printers.conf file. May be the same regression as in Fedora 30 https://bugzilla.redhat.com/show_bug.cgi?id=1706090 Issue prevents upgrading to eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853242] Re: Regression in Eoan: cannot print to smb connected printer
Sorry, could not report the issue from the machine where I have first experienced the bug. Also marked samba as a possible source for the issue (from the fedora report). If the issue is the same, it seems fixed in Fedora. ** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- 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/1853242 Title: Regression in Eoan: cannot print to smb connected printer Status in cups package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: After upgrade from disco to eoan, notwithstanding the fact that /etc/cups/printers.conf has stayed the same, I cannot print anymore to an smb connected printer provided by my Institution. The connection uses authentication and username, password are present in the smb url in the printers.conf file. May be the same regression as in Fedora 30 https://bugzilla.redhat.com/show_bug.cgi?id=1706090 Issue prevents upgrading to eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
Wonder if it could be useful to kindly ask Andrzej Hunt if he can look into the issue. If I am not wrong he is the author of the current bluez 5 code in Impress. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
Issue persists with current LibO 6.3.1.2 and most likely due to the fact that the bluetooth stack on linux (bluez) has changed in the past years and impress has not cought up. Problem is now more visible due to the startup tooltips in Impress 6.3.x which explicitly introduce the impress remote functionality inviting the users to test it. Goes like: start Impress -> see tooltip -> get interested -> download and install phone app -> try -> fail -> get disappointed and remove phone app. Because the phone based remote is one of those little things with a great wow factor that makes LibO really shine out and amaze people when used in front of an audience, it would really be great if the functionality could be restored. It is literally a little big thing helping getting a foot in the door. In fact, I suppose that if one could also add a "spotlight" and "zoom" functionality in it (in addition to the pointer) and the ability to use the phone accelerometers for moving the pointer (in place of the finger on the screen) it would make LibO a serious contender for all those coveting the "Logitech spotlight" that is currently the hot thing in presentations selling for over $100. See also https://github.com/jahnf/Projecteur . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this
[Touch-packages] [Bug 1798400]
Cannot test daily builds right now, but 6.3.0 beta 1 still has the issue. Launching impress reports: bluetoothd[1386]: RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) in the system logs and then the remote app cannot contact the host. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825402] Re: Regression. Recent updates to cosmic broke hybrid-sleep
Trying to downgrade systemd seems to be impossible. As soon as I try an apt install --reinstall systemd= apt tries to remove half of the system... I have noticed the issue in the past 15 days, I think, but only had time to look at it more closely right now. Some notes: - Trying to upgrade the kernel to latest 5.0.x via the mainline ppa seems to make no difference. - Issue is somehow erratic. Happens like 70% of the time. In some rare occasions the systems seems to save state and then suspend correctly. - When the issue occurs, the beginning of the hybrid sleep seems OK: big activity on disk to save the state, then the disk is powered down. However at this point, rather than suspending the system re-spins up the disk a couple of times and then halts. System logs show a HuHu unexpected nmi, dazed and confused, but it is unclear to me if it is related to the broken suspend - Plain suspend and plain hybernate seem to work. - Hybrid suspend has worked for years on this 2013 Haswell laptop, which is a Shenker, in fact a Clevo, substantially identical to the System 76 Galago UltraPro. -- 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/1825402 Title: Regression. Recent updates to cosmic broke hybrid-sleep Status in systemd package in Ubuntu: Incomplete Bug description: Recently, hybrid-sleep has been broken on cosmic. Calling systemctl hybrid-sleep used to work perfectly on my system. Now, after having saved the state to disk, it switches off the machine rather than suspending it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.13 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 18 19:25:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1952 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2019-01-18 (90 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825402] [NEW] Regression. Recent updates to cosmic broke hybrid-sleep
Public bug reported: Recently, hybrid-sleep has been broken on cosmic. Calling systemctl hybrid-sleep used to work perfectly on my system. Now, after having saved the state to disk, it switches off the machine rather than suspending it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.13 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 18 19:25:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1952 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2019-01-18 (90 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825402 Title: Regression. Recent updates to cosmic broke hybrid-sleep Status in systemd package in Ubuntu: New Bug description: Recently, hybrid-sleep has been broken on cosmic. Calling systemctl hybrid-sleep used to work perfectly on my system. Now, after having saved the state to disk, it switches off the machine rather than suspending it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.13 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 18 19:25:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1952 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2019-01-18 (90 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
Hi Dmitry, I've been testing the package in cosmic-proposed in the last few days. Sorry I have not reported earlier, but I encountered a little problem and I wanted to look better at it for extra safety. In fact, it was a problem with a single printer of the many I use while roaming with my laptop and got fixed by updating the printer driver. The QT packages are OK for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Status in qtbase-opensource-src source package in Cosmic: Fix Committed Bug description: [Impact] All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. [Test Case] 1) Install a printer that can duplex and configure it to do duplex with long-edge binding from the printer setup dialog. 2) Open a PDF with okular, and open the print dialog. Select the printer above. 3) Press the "Options" button to enlarge the dialog to also present the options. Select the "options" tab, right of "copies". Verify that Duplex Printing is preset to "None" This is wrong, because the printer was configured to do duplex with long-edge binding. 4) Print and close okular. 5) Reopen okular (with the same or another PDF file). Open again the print dialog and select the same printer. 6) Redo 3). Again see that Duplex Printing is preset to "None", instead of being at the default or at the previously used setup. [Regression Potential] The proposed patch only changes the default settings. The regression potential may be that the values are wrong, although they are already wrong. In case there is some bug it may lead to crashes. But this code is in the latest stable Qt release and I am not aware of any such crashes reported. [Other Info] The proposed patch is a backport of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e [Original Description] See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
Dimitri, if you can have a package for cosmic with the fix built in a PPA, I would be glad to try it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: In Progress Status in qtbase-opensource-src source package in Cosmic: Incomplete Bug description: [Impact] All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. [Test Case] 1) Install a printer that can duplex and configure it to do duplex with long-edge binding from the printer setup dialog. 2) Open a PDF with okular, and open the print dialog. Select the printer above. 3) Press the "Options" button to enlarge the dialog to also present the options. Select the "options" tab, right of "copies". Verify that Duplex Printing is preset to "None" This is wrong, because the printer was configured to do duplex with long-edge binding. 4) Print and close okular. 5) Reopen okular (with the same or another PDF file). Open again the print dialog and select the same printer. 6) Redo 3). Again see that Duplex Printing is preset to "None", instead of being at the default or at the previously used setup. [Regression Potential] The proposed patch only changes the default settings. The regression potential may be that the values are wrong, although they are already wrong. In case there is some bug it may lead to crashes. But this code is in the latest stable Qt release and I am not aware of any such crashes reported. [Other Info] The proposed patch is a backport of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e [Original Description] See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
Hi Dmitry, thanks for your message and the work as volunteers on Qt packaging. My message was merely to know if there was any need for a specific bug item about the backporting and it is great to hear that you were already planning the backport! Also, great to hear that 19.04 is going to get the Qt LTS. Reproducing the duplex issue is very easy. 1) Install a printer that can duplex and configure it to do duplex with long-edge binding from the printer setup dialog. 2) Open a PDF with okular, and open the print dialog. Select the printer above. 3) Press the "Options" button to enlarge the dialog to also present the options. Select the "options" tab, right of "copies". Verify that Duplex Printing is preset to "None" This is wrong, because the printer was configured to do duplex with long-edge binding. 4) Print and close okular. 5) Reopen okular (with the same or another PDF file). Open again the print dialog and select the same printer. 6) Redo 3). Again see that Duplex Printing is preset to "None", instead of being at the default or at the previously used setup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Status in qtbase-opensource-src source package in Cosmic: New Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
Should a specific bug be opened to ask for this to be officially backported to Bionic+Cosmic as a bug-fix? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
The issue is also present in cosmic. Wonder if someone might be kind enough to build a deb with the patch for cosmic too... Would be very much appreciated! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
1) I confirm that the gray-scale printing option is completely ignored and that the printer prints always in color (this is definitively a bug). 2) I confirm that an option to select the printer tray is missing (though I think this may be a limitation in the qt version shipped with bionic). 3) I would like to add that okular "scales down" when printing A4 pdf documents, which badly breaks some flows. For instance, pages of the same document printed on the same printer with okular and any other linux PDF viewer do not align and cannot be mixed; flows needing accurate placement of cropmarks are broken (this is also a bug). Probably these should be new bugs, though. Still I wonder if moving to the current qt 5.9.7 from the bionic 5.9.5 could improve the situation. In the end qt 5.9 is a long term release with only bugfixes applied and it should be relatively safe to track it rather than introducing downstream patches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
Still present in 6.2.0 RC 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
I think that the issue can be either a bug in the bluetooth stack or merely something that has /changed/ in the bluetooth stack, that libreoffice has not tracked properly. Hence, I have also opened a bug upstream for LibO, mentioning this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
I have stayed a long time without trying impress remote, so I do not know exactly when the issue started. However, I am sure that last year at this time (aka on 16.04) the issue did not exist. Just tried latest non-RC kernel from mainline 4.18.x and the issue is still there. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
See https://bugzilla.redhat.com/show_bug.cgi?id=1581879 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400] [NEW] Regression: cannot use impress remote over bluetooth with ubuntu bionic
Public bug reported: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: Red Hat Bugzilla #1581879 https://bugzilla.redhat.com/show_bug.cgi?id=1581879 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in bluez package in Ubuntu: New Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg
[Touch-packages] [Bug 1776173] [NEW] qt print dialog shipped with bionic ignores printer defaults
Public bug reported: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: New Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
Does not work in artful either. On 17.10, the HSP/HFP option is shown in dropdown menus (pavucontrol, kde audio config, etc.). However, selecting them does not work and when one checks again the setting has gone back automatically to a2dp sink. Please reopen. Otherwise advise whether a new identical bug should be opened for artful. -- 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/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Using the 2/14 Xenial daily build, paired bluetooth headsets' do not work in HSP/HFP mode. [Steps to reproduce] 1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build 2. In the laptop, go to sound settings > output tab > try switching mode to HSP/HFP mode 3. Press the "test sound" button and try playing sound 4. Go to the input tab and check if bluetooth headset mic is listed [Expected result] After step 3, a window for mono audio test should pop up After step 4, the input tab should list a bluetooth headset mic device [Actual result] After step 3, the window that pops up is for stereo (A2DP) audio test After step 4, the input tab does not list any bluetooth headset mic [Details] BT wireless module: * Intel 3160 BT headset: * Jabra CLI Xenial: 2/14 daily build: * Kernel: 4.4.0-6 * bluez: 5.36-0ubuntu1 * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1 * pulseaudio: 1:8.0-0ubuntu2 * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2 [Note] Also double checked with same set of hardware, but with 15.10 installed. Bluetooth headset HSP/HFP mode worked correctly in 15.10. 15.10 details: * kernel: 4.2.0-19 * bluez: 5.35-0ubuntu2 * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1 * pulseaudio: 1:6.0-0ubuntu13 * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
Made the quick check you suggested. Switching off cups, all printers disappear both in okular (QT) and firefox. So it looks like the driverless network printers come from cups. Weird enough now after the switch off - switch on sequence for cups, I do not have the driverless printers them in firefox either even with cups re-enabled which is weird. This means that there is nothing to disable in the GTK and QT dialogs which seems a good thing. Do you know if some kind of situation where stale files describing network printers could remain around explaining these inconsistent behaviors? If so where? Furthermore, it looks like cups is currently not passing the list of driverless network printers to the print dialog. May it be the case that cups (or the cups dbus notifier) happens to read the cups-browsed configuration file seeking the BrowseRemoteProtocols none configuration option if it is readable? Note that on my system the cups dbus notifier runs as lp and so it cannot read cups-browsed.conf by default since this file is owned by root.root and not readable by others. -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
@Till Thanks! This is a great explanation. I am sure that it took you some time to write it in this clear way and I would like to let you know that I really appreciate it. Things look a bit clearer to me right now. I am looking forward to seeing method (4) materialize as the current situation seems rather unsatisfactory to me. In fact, I think that when there was only (1) without (2) and (3) the situation was much better than it is right now, since you had a clear single place where to enable and disable things and consistent number and naming of printers across all dialogs. Particularly (3), with the dialogs grabbing the DNS-SD broadcasts, seems a rather poor choice leading to all sorts of inconsistencies among the different dialogs. Would it make sense to suggest that (3) is disabled in ubuntu's QT and GTK since we have cups-browsed anyway that is better (as it provides indication of the printer type)? Do you know if there is any way to disable (2) from some cups option? -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
And I think that the conclusion is the following:
- The KDE print dialog bypasses cups-browsed to list the driverless
network printers, if cups-browsed is not running. In this case it fails
to gather some information such as the "type" of the printer, though.
- For the KDE print dialog not to show the driverless printers one needs
the cups-browsed.conf file to explicitly contain the
'BrowseRemoteProtocols none' entry and must be made *readable* by
everyone, plus a desktop restart seems to be needed
- lpstat -e always shows the driverless network printers regardless of
whether the cups-browsed is active or the BrowseRemoteProtocols none is
selected.
- the firefox print dialog keeps showing /some/ (but not all) of the
driverless network printers shown by lpstat -e and so does the gimp one
and inkscape (dont't think that I have many other apps to test that do
not use the kde print dialog)
The firefox print dialog gets some weird names for some of the network
printers ("print" "printer"), and shows "rejecting jobs" for them.
All this bypassing of cups-browsed does not seem very proper to me.
--
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/1738432
Title:
Regression, poor user experience, print dialogs garbled by
unidentifiable driverless printers
Status in cups package in Ubuntu:
Incomplete
Bug description:
Recently, my print dialogs have started to include network discoverd
printers in addition to those configured in cups even if the cups-
browsed service is disabled and the BrowseRemoteProtocols option is
set to none.
There does not seem to be any way to disable this behavior apart from
disabling avahi or its ability to talk to dbus, which causes side
effects on the system.
Yet, in some environments this behavior is a definite regression over
the old one and leads to an extremely poor user experience.
On some networks:
- The print dialogs takes 3-10 sec to open which is a huge amount of
time for an action that is expected to be instantaneous and for which
there is no visual feedback.
- The print dialog contains many tens of printer entries, all
identified by weird hex strings that cannot be related to any useful
location, that do not help identifying which entry corresponds to
which printer and that only mess up the list making it hard to find
the printers that are actually useful.
For instance, suppose that you work at some office that has recently
purchased a batch of new printers all the same model. In the print
dialog you may get many entries like:
HP_Laserjet_Pro_Mxxxdw_21ACF2
which only vary in the final hex string. How is one suppose to know
what is where?
Please make it possible to disable this driverless printer madness.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libcups2 2.2.4-7ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
CurrentDesktop: KDE
Date: Fri Dec 15 16:22:07 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1463 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MachineType: Notebook W740SU
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W740SU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
One weird phenomenon is that - if cups-browsed is active, the okular print dialog shows the driverless printers and indicates their type as driverless - if cups-browsed is not active, the okular print dialog shows the driverless printers but fails to indicate their type (type is empty). -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
One weird phenomenon is that - if cups-browsed is active, the okular print dialog shows the driverless printers and indicates their type as driverless - if cups-browsed is not active, the okular print dialog shows the driverless printers but fails to indicate their type (type is empty). -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
1) cups-browsed does not appear in ps auxwww 2/3) The driverless printers appear in the print dialog of okular 4) avahi-browse -v -t -r --all returns tons of printers in forms such as = eth0 IPv4 Lexmark MS610dn _ipps._tcp local hostname = [ET0021B77DB54B.local] address = [XX.YY.ZZ.WW] port = [443] txt = ["wfds-print=T" "product=(Lexmark MS610dn)" "mopria-certified=1.3" "kind=document,envelope,label" ... 5) lpstat -e shows all the driverless printers 6) lpstat -v does not show the driverless printers 5) -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
My printing almost always happens from okular which uses a QT print dialog. -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
Thanks for the clarification in the last answer, that is helpful for me to find out which ones among the many attempts I made to disable the display of the driverless entries eventually worked (since it could be nice for me to script enabling/disabling actions to place into some network identification logic tied to network manager, to have the driverless printers disabled only where it makes no sense to show them). -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
I do not know if I am allowed to publish details of my company intranet that I expect to be collected with the avahi-browse or the lpstat -v. I'll try to find out first. In any case, I'll try to provide what I can when I am again at the office with the newer printers appearing as driverless entries. -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
Don't know what I did, but finally I have succeeded disabling the display of the driverless network printers. Right before systemd reported cups-browsed as stopped. Can it be the case that you need /both/ the process stopped /and/ the BrowseRemoteProtocols in its conf file set to none /at the same time/ plus a restart of the desktop environment? In case, I would change the bug title to "please document how to disable the display of the driverless network printers" in the print dialog. It can be a handy feature in places with just a couple of printers of different brands, but in some environments it needs to be off. -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738432] [NEW] Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
Public bug reported: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: New Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E
[Touch-packages] [Bug 1200124] Re: ubuntu bug hangs if you are already logged in launchpad
Still here as of 17.04 zesty. -- 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/1200124 Title: ubuntu bug hangs if you are already logged in launchpad Status in apport package in Ubuntu: Confirmed Bug description: On kubuntu 13.04, with firefox as the default browser. type ubuntu-bug apport collects information a web page opens saying 'You are already logged in' end of the experience. To actually be able to report a bug, you need to log-out from launchpad and repeat. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: apport 2.9.2-0ubuntu8.1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportLog: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CrashReports: 640:0:0:314932:2013-07-08 17:56:27.757302608 +0200:2013-07-08 17:56:27.757302608 +0200:/var/crash/susres.2013-07-08_17:56:27.762473.crash Date: Thu Jul 11 10:48:51 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2009-11-12 (1336 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to raring on 2013-05-25 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1200124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: a2dp skips terribly
I have occasionally seen this too, in kubuntu 17.04. What is weird is that it happens only sometimes, and I cannot recognize what triggers the issue. Last time it went away with a reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: a2dp skips terribly Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU
I see it all the time after an upgrade to 17.04. Medium priority seems
an euphemism. This is a true showstopper. It is not just systemd-
resolved taking a whole core. Dnsmasq takes half of another. The cpu
runs hot. In a laptop, batteries drain in a snap.
Has this to do with https://unix.stackexchange.com/questions/304050/how-
to-avoid-conflicts-between-dnsmasq-and-systemd-resolved? Should
DNSStubListener=no be added to /etc/systemd/resolved.conf? Should
dnsmasq not be there?
Note that this bug is now 2 months old, that is over 20% of the expected
life of zesty.
--
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/1670959
Title:
systemd-resolved using 100% CPU
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like
starting the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
I see something similar in 16.10. Weird enough, issuing an iwlist wlan0 scan seems to be enough to get the available connections again -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing
Can we safely assume that bug 1675820 is a duplicate of this one?
In that case, dnsmasq seems to operate correctly. In fact, setting the
domain server with an explicit dbus command, that is
sudo qdbus --system org.freedesktop.NetworkManager.dnsmasq
/uk/org/thekelleys/dnsmasq \
org.freedesktop.NetworkManager.dnsmasq.SetDomainServers "(" "8.8.8.8" ")"
makes the trick and gets name resolution operate correctly. It looks
like the fault is on network manager not passing the domain servers to
dnsmasq via dbus in the correct way (or at all).
Was a test of this sort practised in this case?
--
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/1675519
Title:
Network Manager w/ dnsmasq Dies when VPN-ing
Status in network-manager package in Ubuntu:
Triaged
Bug description:
Hello.
Within the past week or so, a new bug has cropped up on Network
Manager on 16.04.
When Network Manager on 16.04 is configured to use dnsmasq and not
systemd-resolved, one is expecting VPN DNS servers to be properly set
and dnsmasq to properly route DNS requests to the Internet.
However, when connecting to my OpenVPN connection, dnsmasq now fails
extremely hard and no longer replies or routes data for DNS requests
properly. This results in me having to use a fail-over workaround of
enforcing resolvconf to use my local `bind9` instance on my own system
for DNS, which is configured to route to Google for DNS requests.
This, however, prohibits me from using my own DNS on my VPN connect,
which are on the remote location and serve internal ranges and domains
that I should be permitted to access.
Given these issues, with `dnsmasq` just outright exploding in our
faces and no longer being usable for DNS request routing over the VPN,
I'm not even sure we can consider VPN DNS as a viable option anymore
with 16.04.
Note that this is only *very* recently a problem within the past few
weeks, and I can't find any updates which would have impacted this.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 23 14:04:06 2017
InstallationDate: Installed on 2016-12-20 (92 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.2.6connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675820] [NEW] Network manager fails to set domain server in some circumstances
Public bug reported: Occasionally, after a resume from an update, network manager starts behaving strangely, not setting the DomainServer for the network. This happens when resuming the laptop to a location where: - an additional ethernet card (which is the one to use) is attached via USB - configuring that ethernet card NM is set up to clone a given mac address and get addresses only from dhcp, while the dns server is set manually in the network manager configuration - there are also free wifi signals to which NM tends to connect In this setup, NM fails to set the dns name in dnsmasq The issue gets worked around by either 1) Using qdbus to call the dnsmasq dbus method to set the domain server. In this case the solution is temporary. Namely when NM is asked to disconnect from the net and then to reconnect, the issue comes again; or 2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted and everything starts working fine; or 3) Restarting NM itself. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 24 16:22:43 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1197 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev enx0050b61af5c1 proto static metric 100 10.143.0.0/19 dev enx0050b61af5c1 proto kernel scope link src 10.143.20.139 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- 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/1675820 Title: Network manager fails to set domain server in some circumstances Status in network-manager package in Ubuntu: New Bug description: Occasionally, after a resume from an update, network manager starts behaving strangely, not setting the DomainServer for the network. This happens when resuming the laptop to a location where: - an additional ethernet card (which is the one to use) is attached via USB - configuring that ethernet card NM is set up to clone a given mac address and get addresses only from dhcp, while the dns server is set manually in the network manager configuration - there are also free wifi signals to which NM tends to connect In this setup, NM fails to set the dns name in dnsmasq The issue gets worked around by either 1) Using qdbus to call the dnsmasq dbus method to set the domain server. In this case the solution is temporary. Namely when NM is asked to disconnect from the net and then to reconnect, the issue comes again; or 2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted and everything starts working fine; or 3) Restarting NM itself. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 24 16:22:43 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1197 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev enx0050b61af5c1 proto static metric 100 10.143.0.0/19 dev enx0050b61af5c1 proto kernel scope link src 10.143.20.139 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451808] Re: apport-collect error: No module named PyQt5.QtCore
Yes, but shouldn't this be a dependency of python-apport? -- 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/1451808 Title: apport-collect error: No module named PyQt5.QtCore Status in apport package in Ubuntu: Confirmed Bug description: In kubuntu vivid, apport reacts as follows: apport-collect 1451277 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:35:33 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635023] Re: Regression: quotas prevent yakkety from booting (boots once every ~4 attempts)
Sorry, I'm not understanding your comment. What I understood is that the systemd developers said "It is not our responsibility if ubuntu does not boot, this is not a systemd bug! In fact, the issue in booting is caused by some quota related units, shipped by Ubuntu, that are not part of systemd". Then, I saw that the faulty systemd units are shipped with the "quota" package, just as you say. Yet, the upstream quota package does not contain these units. The systemd quota related units and scripts are a downstream ubuntu (maybe from debian) addition (in fact, they live in the debian dir of the package). This is why I was reporting that the systemd developers suggest that this is a downstream bug (a bug in the Ubuntu distro), not an upstream bug (a bug in systemd 231). I never implied that ubuntu forgot to ship some units. I'm only saying that the quota units shipped with ubuntu evidently mistake something, because when they are masked the system boots, otherwise it doesn't. Possibly, the issue is only triggered if one has quotas+lvm2+fake or soft raid. This may explain why the mistake got unnoticed when it slipped in. I suppose that this bug should be fixed by the maintainers of the quota package in ubuntu, possibly with the help of the systemd maintainers. ** Package changed: systemd (Ubuntu) => quota (Ubuntu) -- 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/1635023 Title: Regression: quotas prevent yakkety from booting (boots once every ~4 attempts) Status in systemd: New Status in quota package in Ubuntu: New Bug description: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1635023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635023] Re: Regression: quotas prevent yakkety from booting (boots once every ~4 attempts)
Systemd devels suggest that the bug is due to downstream (ubuntu), since they do not ship the quota.service unit (whose removal makes the system boot again) at all. -- 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/1635023 Title: Regression: quotas prevent yakkety from booting (boots once every ~4 attempts) Status in systemd: New Status in systemd package in Ubuntu: New Bug description: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1635023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635023] Re: Regression: yakkety does not boot (boots once every ~4 attempts)
Got it! Sort of... Misabling quotas make the system boot reliably. No clue why. It may not be a race, rather the fact that the initial quota check is supposed to happen only in certain cases. No idea. Debugging boot with systemd is beyond my expertise. Masking the systemd quota.service (the initial quota check) seems to be sufficient to enable a reliable boot. Still I see failures on shutdown related to the disabling of the stuff in fstab. ** Bug watch added: github.com/systemd/systemd/issues #4486 https://github.com/systemd/systemd/issues/4486 ** Also affects: systemd via https://github.com/systemd/systemd/issues/4486 Importance: Unknown Status: Unknown ** Summary changed: - Regression: yakkety does not boot (boots once every ~4 attempts) + Regression: quotas prevent yakkety from booting (boots once every ~4 attempts) -- 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/1635023 Title: Regression: quotas prevent yakkety from booting (boots once every ~4 attempts) Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1635023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635023] Re: Regression: yakkety does not boot (boots once every 4 attempts)
** Summary changed: - yakkkety boot is erratic + Regression: yakkety does not boot (boots once every 4 attempts) ** Summary changed: - Regression: yakkety does not boot (boots once every 4 attempts) + Regression: yakkety does not boot (boots once every ~4 attempts) ** Attachment added: "The systemd journal when the issue is present" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+attachment/4767053/+files/journal.txt -- 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/1635023 Title: Regression: yakkety does not boot (boots once every ~4 attempts) Status in systemd package in Ubuntu: New Bug description: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635023] Re: Regression: yakkety does not boot (boots once every ~4 attempts)
** Attachment added: "The systemd units when the issue is present" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+attachment/4767054/+files/systemctl.output.txt -- 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/1635023 Title: Regression: yakkety does not boot (boots once every ~4 attempts) Status in systemd package in Ubuntu: New Bug description: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635023] Re: yakkkety boot is erratic
Issue is present also moving do mdadm (which is possible for my fake raid since it uses intel metadata). When it happens, the boot hangs for 1 minute and a half on A start job is running for dev-disk-by... with all disks appearing in turn on the line. After that the machine drops to an emergency prompt. Analyzing the systemd journal shows the corresponding jobs timing out. Interestingly: 1) *all* the items mentioned in /etc/fstab get shown here. Namely, when the issue occurs, the error is shown even for the swap partintion (that is on a plain ssd partition... 2) It is not a problem with /etc/fstab but some race: every few attempts the system succeeds to boot 3) When you get to the emergency prompt all the disks on which systemd hangs appear to be working just fine 4) Removing from the fstab the entries corresponding to stuff on the slower fake raid, the boot starts being reliable (I think) How can I debug this? How can I force systemd to wait before it tries to access the disks? Should I open a bug on systemd? Can someone provide pointers at some systemd documentation that might be releant to this issue? It seems such a complex device that I do not know where to start. -- 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/1635023 Title: yakkkety boot is erratic Status in systemd package in Ubuntu: New Bug description: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635023] [NEW] yakkkety boot is erratic
Public bug reported: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1635023 Title: yakkkety boot is erratic Status in systemd package in Ubuntu: New Bug description: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Possibly also related to 1320402 (as the unnecessary resync probably follows the incorrect stopping of the array). -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not help either. More information below: $ lsb_release -rd
[Touch-packages] [Bug 1200124] Re: ubuntu bug hangs if you are already logged in launchpad
Goes on as of 16.04 -- 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/1200124 Title: ubuntu bug hangs if you are already logged in launchpad Status in apport package in Ubuntu: New Bug description: On kubuntu 13.04, with firefox as the default browser. type ubuntu-bug apport collects information a web page opens saying 'You are already logged in' end of the experience. To actually be able to report a bug, you need to log-out from launchpad and repeat. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: apport 2.9.2-0ubuntu8.1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportLog: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CrashReports: 640:0:0:314932:2013-07-08 17:56:27.757302608 +0200:2013-07-08 17:56:27.757302608 +0200:/var/crash/susres.2013-07-08_17:56:27.762473.crash Date: Thu Jul 11 10:48:51 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2009-11-12 (1336 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to raring on 2013-05-25 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1200124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1503773] Re: Drop ondemand init script
@Steve Langasek A big issue is that the script makes quite arbitrary assumptions on the system, including the fact that there is an ondemand governor at all. A large number of modern systems use the intel p-state driver that does not have an ondemand governor at all! On this systems, the fallback mechanism in the script causes the system to always run in powersave mode, so hindering system performance for no reason. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1503773 Title: Drop ondemand init script Status in sysvinit package in Ubuntu: Confirmed Bug description: Ondemand init script is not inherited from Debian, it's an Ubuntu specific change. Some reasons to get rid of it: On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance with no ability to change frequency.. In the init script we don't run this for android Ondemand is already on by default! Why don't we just always use whatever is that kernel's default? There are a number of other reported problems with it: https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1503773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497375] Re: Remove /etc/init.d/ondemand script
Please, reopen. The ondemand script is totally broken for systems with cpu frequency scaling drivers other than acpi that do not provide an ondemand governor. Most important its quite arbitrary assumptions cause systems with the intel p-state driver to have worse performance than they should. See bug 1480320 Furthermore the ondemand governor is already set by default by the kernel on systems with the acpi driver, so there is really no need for this script at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1497375 Title: Remove /etc/init.d/ondemand script Status in sysvinit package in Ubuntu: Won't Fix Bug description: There are several issues with the /etc/init.d/ondemand script [1], and it appears to be a bad difference / addition to the upstream/Debian package. Please consider removing it. 1: https://bugs.launchpad.net/ubuntu/+source/sysvinit?field.searchtext=ondemand=Search%3Alist=NEW%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED=_reporter=_dupes=on_patch=_no_package= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1497375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480320] Re: ondemand init script sets governor "powersave" when only "powersave" and "performance" available
Since the /etc/init.d/ondemand script has many other issues, including overriding the settings prepared by /etc/init.d/cpufrequtils, I think that the best option should be removing it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1480320 Title: ondemand init script sets governor "powersave" when only "powersave" and "performance" available Status in sysvinit package in Ubuntu: Triaged Bug description: My system seems to have governors "powersave" and "performance" available. No others. So by ondemand, I end up with "powersave", which makes my workstation excruciatingly slow. I think that in this case, "performance" should be preferred. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: initscripts 2.88dsf-59.2ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jul 31 17:08:08 2015 InstallationDate: Installed on 2010-10-12 (1752 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: sysvinit UpgradeStatus: Upgraded to wily on 2014-11-11 (262 days ago) mtime.conffile..etc.init.d.ondemand: 2015-07-31T16:51:58.391407 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1480320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 911206] Re: /etc/init.d/ondemand unconditionally overrules /etc/init.d/cpufrequtils
There is another issue: /etc/init.d/ondemand tries to set the governor to ondemand unconditionally, even on intel systems with p-state. Systems with the p-state frequency scaling do not have an ondemand governor at all. This means that the /etc/init.d/ondemand falls back to the powersave governor, hindering performance. Alltogether, the /etc/init.d/ondemand looks hackish. Its operation relies on assumptions on the system setup that are just plain wrong: 1) That one does not install the cpufreq utils since, as mentioned in the original bug report, it destroys the work of /etc/init.d/cpufrequtils 2) That one is on the acpi cpu frequency driver since it is hardwired with the governors provided by such driver. I strongly recommend getting rid of /etc/init.d/ondemand -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/911206 Title: /etc/init.d/ondemand unconditionally overrules /etc/init.d/cpufrequtils Status in cpufrequtils package in Ubuntu: Confirmed Status in sysvinit package in Ubuntu: Triaged Bug description: /etc/init.d/ondemand *always* sets the cpu scaling governor to ondemand, and is executed after /etc/init.d/cpufrequtils. This causes two problems: 1. Confusion, because it seems as if /etc/init.d/cpufrequtils is being run, but has no effect 2. Possible problems down the road, because /etc/init.d/ondemand has no /etc/default/ondemand, so either editing or deleting /etc/init.d/ondemand. I just discovered that updating initscripts will fail if /etc/init.d/ondemand has been deleted (dpkg complains about this file missing and aborts) Suggested fixes: a) Remove /etc/init.d/ondemand, make the ondemand governor the default for /etc/init.d/cpufrequtils, install package cpufrequtils by default. b) If this is not desired, make absolutely sure that /etc/init.d/ondemand is executed *before* /etc/init.d/cpufrequtils, maybe by making /etc/init.d/cpufrequtils depend on /etc/init.d/ondemand. I'm looking forward to your responses, Daniel ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: initscripts 2.88dsf-13.10ubuntu4.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Jan 3 13:13:59 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sysvinit UpgradeStatus: Upgraded to oneiric on 2011-12-10 (23 days ago) modified.conffile..etc.init.d.ondemand: [modified] mtime.conffile..etc.init.d.ondemand: 2012-01-03T13:13:33.783902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/911206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 911206] Re: /etc/init.d/ondemand unconditionally overrules /etc/init.d/cpufrequtils
I am just realizing that this other problem is already listed as bug 1480320 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/911206 Title: /etc/init.d/ondemand unconditionally overrules /etc/init.d/cpufrequtils Status in cpufrequtils package in Ubuntu: Confirmed Status in sysvinit package in Ubuntu: Triaged Bug description: /etc/init.d/ondemand *always* sets the cpu scaling governor to ondemand, and is executed after /etc/init.d/cpufrequtils. This causes two problems: 1. Confusion, because it seems as if /etc/init.d/cpufrequtils is being run, but has no effect 2. Possible problems down the road, because /etc/init.d/ondemand has no /etc/default/ondemand, so either editing or deleting /etc/init.d/ondemand. I just discovered that updating initscripts will fail if /etc/init.d/ondemand has been deleted (dpkg complains about this file missing and aborts) Suggested fixes: a) Remove /etc/init.d/ondemand, make the ondemand governor the default for /etc/init.d/cpufrequtils, install package cpufrequtils by default. b) If this is not desired, make absolutely sure that /etc/init.d/ondemand is executed *before* /etc/init.d/cpufrequtils, maybe by making /etc/init.d/cpufrequtils depend on /etc/init.d/ondemand. I'm looking forward to your responses, Daniel ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: initscripts 2.88dsf-13.10ubuntu4.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Jan 3 13:13:59 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sysvinit UpgradeStatus: Upgraded to oneiric on 2011-12-10 (23 days ago) modified.conffile..etc.init.d.ondemand: [modified] mtime.conffile..etc.init.d.ondemand: 2012-01-03T13:13:33.783902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/911206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 879943] Re: Synaptic messes sources.list and sources.list.d
Thanks for the information! I am a bit surprised by this approach, which looks weird to me. It's a service basically deciding it "owns" the content of some files without telling anyone. In fact, I've always believed that the configuration is in text files and not in some private database format precisely to let it be modified by file editing. Furthermore there are tons of site including distribution official ones that instruct one to actively edit those text files to achieve some goals or to solve some problem and this gets simply broken by the approach taken by the software-properties service. Shouldn't the service at least place a watch on the files to reread them and update its vision of the configuration when the files are edited? Incidentally, where can I find info on this service, the interfaces it exposes and how to stop it from running? -- 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/879943 Title: Synaptic messes sources.list and sources.list.d Status in software-properties package in Ubuntu: Confirmed Bug description: Consider the following situation 1) I carefully edit by hand the /etc/sources.list file or the files in /etc/sources.list.d files (this is something I do to have them aligned between different machines. In fact it is not a real edit, but a copy from another machine) 2) Try the lists with apt-get update. Everything is fine. 3) Start synaptic. Go to the settings window to edit the repos. Go to the other software tab. 4) Do any possible little action. For instance activate and disactivate the source repo for ubuntu partners. Assure that your action has nothing to do with the changes you made in 1) 5) See how synaptic has horribly restored the repo list as it was before your hand edit. 6) Exit synaptic and go to the /etc/apt dir. Verify how everything has gone back exactly as it was before your hand edit. Repos that you erased are there again. Repos you edited have their changes reverted. IMHO this is not just wrong, but also very dangerous. Suppose that I had added a repo from a third party source. Suppose that I then find out that this repo is dangerous. For instance because it replaces some package with a bugged package or a package with a back door. Suppose that I consciously restore the package to the original version and I hand erase the crappled repo from my list of repos by removing the corresponding file from the /etc/apt/sources.list.d dir Now I feel safe. However, any time I use synaptic I risk having that repo back. To me this is a security vulnerability. Anyone can convince me to add a test repo to see what is in it. At the time I test that repo can be perfectly fine. I test, I remove the repo, I feel safe, the repo gets automatically added back by synaptic, the repo owner adds in a package that looks like an update to a package that I have in my system and without even realizing it I can have my system infected by a malicious package. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: synaptic 0.75.2ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Sat Oct 22 16:45:31 2011 InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: synaptic UpgradeStatus: Upgraded to oneiric on 2011-10-16 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/879943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451815] Re: lists users multiple time when requiring user authentication
Hi, thanks for the analysis. The outcome seems quite reasonable. Can you help me confirming that the Admin user is a compatibility leftover from past versions of Ubuntu and that administrators can be safely removed from it? I have found this http://askubuntu.com/questions/43317/what-is-the-difference-between- the-sudo-and-admin-group and I wonder if it covers all admin tasks or whether there may be old binaries around that still look for admin. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1451815 Title: lists users multiple time when requiring user authentication Status in policykit-1 package in Ubuntu: Incomplete Bug description: To reproduce systemctl restart some unit AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to manage system services or units. Multiple identities can be used for authentication: 1. Sergio Callegari (callegar) 2. Sergio Callegari (callegar) Choose identity to authenticate as (1-2): Why is the same identity seen as two different identities? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:50:15 2015 EcryptfsInUse: Yes MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/DISK00-root ro quiet splash nomodeset video=uvesafb:mode_option=1024x768-16,mtrr=3,scroll=ywrap nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1451815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439784] Re: [apport-kde] apport-collect: Can not import module PyQt5.QtCore
Now getting different errors and apport-collect still not working... apport-collect 1451277 ... Waiting to hear from Launchpad about your decision... (process:15275): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed dpkg-query: no packages found matching linux Traceback (most recent call last): File /usr/share/apport/apport-kde, line 530, in module sys.exit(UserInterface.run_argv()) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 652, in run_argv return self.run_update_report() File /usr/lib/python2.7/dist-packages/apport/ui.py, line 568, in run_update_report response = self.ui_present_report_details(allowed_to_report) File /usr/share/apport/apport-kde, line 367, in ui_present_report_details desktop_info) File /usr/share/apport/apport-kde, line 184, in __init__ self.ui.ui_update_view(self) File /usr/share/apport/apport-kde, line 358, in ui_update_view QTreeWidgetItem(keyitem, [str(line)]) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 21: ordinal not in range(128) -- 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/1439784 Title: [apport-kde] apport-collect: Can not import module PyQt5.QtCore Status in apport package in Ubuntu: Fix Released Bug description: I had to use apport-collect in a tty, because in kde it is not usable: benedikt@benediktZ50-70 ~ % apport-collect 1439694 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore System : Kubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439784] Re: [apport-kde] apport-collect: Can not import module PyQt5.QtCore
I confirm it does not give this error after manually installing python-pyqt5. Weird. I thought distro support was all python3 by now. -- 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/1439784 Title: [apport-kde] apport-collect: Can not import module PyQt5.QtCore Status in apport package in Ubuntu: Fix Released Bug description: I had to use apport-collect in a tty, because in kde it is not usable: benedikt@benediktZ50-70 ~ % apport-collect 1439694 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore System : Kubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451808] Re: apport-collect broken in kubuntu vivid
Seems to work launching sudo apport-collect but then starts web browser as root... -- 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/1451808 Title: apport-collect broken in kubuntu vivid Status in apport package in Ubuntu: New Bug description: In kubuntu vivid, apport reacts as follows: apport-collect 1451277 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:35:33 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451815] Re: lists users multiple time when requiring user authentication
Yes, I see the same with the graphical backend. I only reported the text one, since it was easier. getent passwd | grep callegar has a single entry for the user callegar:x:1000:1000:Sergio Callegari:/home/callegar:/bin/bash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1451815 Title: lists users multiple time when requiring user authentication Status in policykit-1 package in Ubuntu: Incomplete Bug description: To reproduce systemctl restart some unit AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to manage system services or units. Multiple identities can be used for authentication: 1. Sergio Callegari (callegar) 2. Sergio Callegari (callegar) Choose identity to authenticate as (1-2): Why is the same identity seen as two different identities? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:50:15 2015 EcryptfsInUse: Yes MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/DISK00-root ro quiet splash nomodeset video=uvesafb:mode_option=1024x768-16,mtrr=3,scroll=ywrap nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1451815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 794315] Re: lightdm forgets to source /etc/profile and ~/.profile
Same happens with kubuntu vivid and sddm. Should this be fixed individually in each session manager? -- 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/794315 Title: lightdm forgets to source /etc/profile and ~/.profile Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm package in Debian: Confirmed Bug description: Binary package hint: lightdm /etc/gdm/Xsession had this code: # First read /etc/profile and .profile test -f /etc/profile . /etc/profile test -f $HOME/.profile . $HOME/.profile # Second read /etc/xprofile and .xprofile for X specific setup test -f /etc/xprofile . /etc/xprofile test -f $HOME/.xprofile . $HOME/.xprofile so that, for example, ~/bin gets added to the path (by the default ~/.profile), and any user-customized environment setup gets run. After switching from gdm to lightdm, this no longer happens. This is going to be a regression now that lightdm is becoming the default display manager. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.3.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic x86_64 NonfreeKernelModules: openafs Architecture: amd64 Date: Tue Jun 7 19:27:11 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.utf8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/794315/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451815] [NEW] systemctl lists users multiple time when requiring user authentication
Public bug reported: To reproduce systemctl restart some unit AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to manage system services or units. Multiple identities can be used for authentication: 1. Sergio Callegari (callegar) 2. Sergio Callegari (callegar) Choose identity to authenticate as (1-2): Why is the same identity seen as two different identities? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:50:15 2015 EcryptfsInUse: Yes MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/DISK00-root ro quiet splash nomodeset video=uvesafb:mode_option=1024x768-16,mtrr=3,scroll=ywrap nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1451815 Title: systemctl lists users multiple time when requiring user authentication Status in systemd package in Ubuntu: New Bug description: To reproduce systemctl restart some unit AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to manage system services or units. Multiple identities can be used for authentication: 1. Sergio Callegari (callegar) 2. Sergio Callegari (callegar) Choose identity to authenticate as (1-2): Why is the same identity seen as two different identities? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:50:15 2015 EcryptfsInUse: Yes MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/DISK00-root ro quiet splash nomodeset video=uvesafb:mode_option=1024x768-16,mtrr=3,scroll=ywrap nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1451815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451808] [NEW] apport-collect broken in kubuntu vivid
Public bug reported: In kubuntu vivid, apport reacts as follows: apport-collect 1451277 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:35:33 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1451808 Title: apport-collect broken in kubuntu vivid Status in apport package in Ubuntu: New Bug description: In kubuntu vivid, apport reacts as follows: apport-collect 1451277 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:35:33 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451815] Re: lists users multiple time when requiring user authentication
With getent passwd | grep 1000 I get the same single entry as above. This is a test system, not only there is no NIS and LDAP, but there is a single user right now. /etc/passwd as follows root:x:0:0:root:/root:/bin/bash daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin bin:x:2:2:bin:/bin:/usr/sbin/nologin sys:x:3:3:sys:/dev:/usr/sbin/nologin sync:x:4:65534:sync:/bin:/bin/sync games:x:5:60:games:/usr/games:/usr/sbin/nologin man:x:6:12:man:/var/cache/man:/usr/sbin/nologin lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin mail:x:8:8:mail:/var/mail:/usr/sbin/nologin news:x:9:9:news:/var/spool/news:/usr/sbin/nologin uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin proxy:x:13:13:proxy:/bin:/usr/sbin/nologin www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin backup:x:34:34:backup:/var/backups:/usr/sbin/nologin list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin syslog:x:101:102::/home/syslog:/bin/false messagebus:x:103:104::/var/run/dbus:/bin/false polkituser:x:104:105:PolicyKit,,,:/var/run/PolicyKit:/bin/false hplip:x:106:7:HPLIP system user,,,:/var/run/hplip:/bin/false avahi-autoipd:x:107:113:Avahi autoip daemon,,,:/var/lib/avahi-autoipd:/bin/false avahi:x:108:114:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false saned:x:109:117::/home/saned:/bin/false callegar:x:1000:1000:Sergio Callegari:/home/callegar:/bin/bash stunnel4:x:111:123::/var/run/stunnel4:/bin/false sshd:x:110:65534::/var/run/sshd:/usr/sbin/nologin pulse:x:112:119:PulseAudio daemon,,,:/var/run/pulse:/bin/false clamav:x:113:125::/var/lib/clamav:/bin/false postfix:x:102:103::/var/spool/postfix:/bin/false usbmux:x:114:46:usbmux daemon,,,:/home/usbmux:/bin/false rtkit:x:115:126:RealtimeKit,,,:/proc:/bin/false oprofile:x:116:127:OProfile JIT user,,,:/var/lib/oprofile:/bin/bash colord:x:105:106:colord colour management daemon,,,:/var/lib/colord:/bin/false dhcpd:x:118:135::/var/run:/bin/false timidity:x:119:136:TiMidity++ MIDI sequencer service:/etc/timidity:/bin/false dnsmasq:x:121:65534:dnsmasq,,,:/var/lib/misc:/bin/false whoopsie:x:122:128::/nonexistent:/bin/false dcmtk:x:117:139::/var/lib/dcmtk/db:/bin/sh uuidd:x:100:101::/run/uuidd:/bin/false gpsd:x:123:20:GPSD system user,,,:/run/gpsd:/bin/false systemd-timesync:x:124:142:systemd Time Synchronization,,,:/run/systemd:/bin/false systemd-network:x:125:143:systemd Network Management,,,:/run/systemd/netif:/bin/false systemd-resolve:x:126:144:systemd Resolver,,,:/run/systemd/resolve:/bin/false systemd-bus-proxy:x:127:145:systemd Bus Proxy,,,:/run/systemd:/bin/false kernoops:x:129:65534:Kernel Oops Tracking Daemon,,,:/:/bin/false speech-dispatcher:x:130:29:Speech Dispatcher,,,:/var/run/speech-dispatcher:/bin/false sddm:x:120:137:Simple Desktop Display Manager:/var/lib/sddm:/bin/false Here is /etc/group root:x:0: daemon:x:1: bin:x:2: sys:x:3: adm:x:4:callegar,syslog tty:x:5: disk:x:6: lp:x:7:callegar mail:x:8: news:x:9: uucp:x:10: man:x:12: proxy:x:13: kmem:x:15: dialout:x:20:callegar fax:x:21:callegar voice:x:22: cdrom:x:24:callegar floppy:x:25:callegar tape:x:26: sudo:x:27:callegar audio:x:29:pulse,timidity dip:x:30: www-data:x:33: backup:x:34: operator:x:37: list:x:38: irc:x:39: src:x:40: gnats:x:41: shadow:x:42: utmp:x:43: video:x:44: sasl:x:45: plugdev:x:46:callegar staff:x:50:callegar games:x:60: users:x:100: nogroup:x:65534: syslog:x:102:callegar messagebus:x:104: polkituser:x:105: fuse:x:107:callegar ssl-cert:x:108: lpadmin:x:109:callegar crontab:x:110: mlocate:x:111: ssh:x:112: avahi-autoipd:x:113: avahi:x:114: netdev:x:115: admin:x:116:callegar saned:x:117: callegar:x:1000: sambashare:x:118:callegar winbindd_priv:x:122: stunnel4:x:123: vboxusers:x:124:callegar pulse:x:119: pulse-access:x:120: clamav:x:125: postfix:x:103: postdrop:x:121: rtkit:x:126: oprofile:x:127: utempter:x:129: bluetooth:x:131: powerdev:x:132: colord:x:106: scanner:x:133:colord,callegar,saned _cvsadmin:x:134: pcscd:x:130: dhcpd:x:135: timidity:x:136: nopasswdlogin:x:138: whoopsie:x:128: dcmtk:x:139: uuidd:x:101: systemd-journal:x:140: systemd-journal-remote:x:141: systemd-timesync:x:142: systemd-network:x:143: systemd-resolve:x:144: systemd-bus-proxy:x:145: input:x:146: sddm:x:137: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1451815 Title: lists users multiple time when requiring user authentication Status in policykit-1 package in Ubuntu: Incomplete Bug description: To reproduce systemctl restart some unit AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to manage system services or units. Multiple identities can be used for authentication: 1. Sergio Callegari (callegar) 2. Sergio Callegari (callegar) Choose identity
[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
The issue of the network not reconnecting after a suspend cycle is present also in utopic (14.10). Maybe it is another bug, but if this is the case, the fact that other bugs opened on the issue are made duplicate of this should be corrected. The issue completely breaks the possibility of using wake on lan. Machine is suspended Machine is waken on lan Machine is unusable because it properly wake on lan, but it is not on the lan. Please *consider* the option of adding a script to /etc/pm/sleep.d/ to wake up or restart network manager as a workaround, until the bug can addressed otherwise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
The issue of the network not reconnecting after a suspend cycle is present also in 14.10 (utopic). Maybe it is another bug, but if this is the case, the fact that other bugs opened on the issue are made duplicate of this should be corrected. The issue completely breaks the possibility of using wake on lan. Machine is suspended Machine is waken on lan Machine is unusable because it properly wake on lan, but it is not on the lan. Please consider providing a script in /etc/pm/sleep.d/ as a solution as a SRU until a better solution can be found since having the network not connecting on machines that do not have a human operator in front of them means compelling the operator to taking a trip to the machine and long down times. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
