[Desktop-packages] [Bug 1931685] [NEW] Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt off at the bottom
Public bug reported: On ubuntu 21.04 and on 21.10. When I open the activities view with a few windows open the bottom edge of the windows (with the window names) get cut off, the bottom of the workspaces bar on the right side also gets cut off. When the workspaces bar is fully extended, the windows can be seen fully. So when I hover over the workspaces bar, or there are multiple workspaces with windows in them, or with an extension to always keep the workspaces open, this issue doesn't impact anything. However, the issue still exists because you can see the bottom of the workspaces bar being cut off. When I connect a second monitor, and arrange the monitors one above the other (with the top one as the permanent), I can see the cut off UI elements on the bottom monitor. With the ubuntu dock extension disabled, none of these issues are present. Here are a few screenshots that show the bug in action: https://ibb.co/album/4whv2c I could NOT spot this issue on a clean install of ubuntu 20.04. But I could see it on clean installs of both on 20.10 and on 21.04. This exists both on Wayland and Xorg. This might be related to this prior issue: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/+bug/1834967 . Maybe this issue was fixed in 20.04 but not on the later versions. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 13:05:40 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1931685 Title: Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt off at the bottom Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: On ubuntu 21.04 and on 21.10. When I open the activities view with a few windows open the bottom edge of the windows (with the window names) get cut off, the bottom of the workspaces bar on the right side also gets cut off. When the workspaces bar is fully extended, the windows can be seen fully. So when I hover over the workspaces bar, or there are multiple workspaces with windows in them, or with an extension to always keep the workspaces open, this issue doesn't impact anything. However, the issue still exists because you can see the bottom of the workspaces bar being cut off. When I connect a second monitor, and arrange the monitors one above the other (with the top one as the permanent), I can see the cut off UI elements on the bottom monitor. With the ubuntu dock extension disabled, none of these issues are present. Here are a few screenshots that show the bug in action: https://ibb.co/album/4whv2c I could NOT spot this issue on a clean install of ubuntu 20.04. But I could see it on clean installs of both on 20.10 and on 21.04. This exists both on Wayland and Xorg. This might be related to this prior issue: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- ubuntu-dock/+bug/1834967 . Maybe this issue was fixed in 20.04 but not on the later versions. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 13:05:40 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1931685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
** Tags added: fossa-edge-staging -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834967] Re: Windows in Activities might be partially off screen
Moved to bug 1931685. Thanks Anand. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1834967 Title: Windows in Activities might be partially off screen Status in ubuntu-dock: New Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-dashtodock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 20:38:43 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (0 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with an icon/logo/glyph
** Summary changed: - [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph + [enhancement] Replace/extend the "Activities" label with an icon/logo/glyph -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1707831 Title: [enhancement] Replace/extend the "Activities" label with an icon/logo/glyph Status in GNOME Shell: Unknown Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Opinion Status in yaru-theme package in Ubuntu: Opinion Bug description: I suggest replacing the "Activities" label with the Ubuntu icon/logo. "Activities" sounds awkward and misleading. It would be more suitably vague, and more consistent with the existing Unity7 experience if the Gnome Shell "Activities" label was replaced by just the Ubuntu logo. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:28:08 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1707831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931701] [NEW] autopkgtests failures on armhf of 7.1.4
Public bug reported: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz ** Affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu) Importance: High Status: New ** Affects: gcc-9 (Ubuntu Impish) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu Impish) Importance: High Status: New ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Also affects: libreoffice (Ubuntu Impish) Importance: High Status: New ** Also affects: gcc-9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/
[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
** Description changed: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz + + + Regarding 21.04/Hirsute + 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 + If was using the gcc-9 9.3.0-23ubuntu2 available at the time. + + There is no-change rebuild for testing against 9.4.0-1ubuntu1~21.04 + running + https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+sourcepub/12488216 + /+listing-archive-extra -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examp
[Desktop-packages] [Bug 1733322]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new bug report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1733322 Title: Unable to enable file or screen sharing with unmanaged network connection Status in gnome-control-center: Expired Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have installed Ubuntu Server 17.10. At request from a colleague I then tried to install ubuntu-desktop and enable screen sharing. However, this did not work as expected. When trying to enable screen sharing (same goes for file sharing), the enable button just jumps straight back to disabled when toggling it. I assumed this had something to do with the fact that the "networks" list at the bottom of the sharing dialog was empty. This appears in the syslog when trying to toggle: Nov 20 11:31:06 bcubuntu3 gnome-control-c[1054]: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be enabled on this network, status is '0' This computer has only a single wired network connection (no wifi). This connection shows in the system menu as "Wired unmanaged" which seems to be the reason that it doesn't show up in the sharing dialogs. As a workaround, I tried the following things: 1. Change "managed=false" to "managed=true" in /etc/NetworkManager/NetworkManager.conf as suggested in https://askubuntu.com/a/2905 2. Touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf as suggested in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547 3. Change renderer to NetworkManager in /etc/netplan/01-netcfg.yaml 1 and 2 was not enough to get NetworkManager to manage the wired interface, but 3, possibly together with one or both of the previous steps did the trick. When I finally got NetworkManager to manage the wired connection, it did show up in the sharing dialogs, and I was able to enable screen sharing. However, it would seem reasonable to be able to enable sharing even on unmanaged interfaces by some mechanism, especially since unmanaged interfaces seem to be the norm these days. ~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 gnome-control-center: Installed: 1:3.26.1-0ubuntu5 Candidate: 1:3.26.1-0ubuntu5 Version table: *** 1:3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.1-0ubuntu4 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1733322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451924]
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome- terminal/-/issues/7479. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1451924 Title: gnome-terminal doesn't have overlay scrollbars (that actually overlay the content) Status in GNOME Terminal: Expired Status in gnome-terminal package in Ubuntu: Triaged Bug description: With gtk 3.16, gnome-terminal's terminal widgets do not have overlay scrollbars. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1451924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733322] Re: Unable to enable file or screen sharing with unmanaged network connection
** Changed in: gnome-control-center Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1733322 Title: Unable to enable file or screen sharing with unmanaged network connection Status in gnome-control-center: Expired Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have installed Ubuntu Server 17.10. At request from a colleague I then tried to install ubuntu-desktop and enable screen sharing. However, this did not work as expected. When trying to enable screen sharing (same goes for file sharing), the enable button just jumps straight back to disabled when toggling it. I assumed this had something to do with the fact that the "networks" list at the bottom of the sharing dialog was empty. This appears in the syslog when trying to toggle: Nov 20 11:31:06 bcubuntu3 gnome-control-c[1054]: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be enabled on this network, status is '0' This computer has only a single wired network connection (no wifi). This connection shows in the system menu as "Wired unmanaged" which seems to be the reason that it doesn't show up in the sharing dialogs. As a workaround, I tried the following things: 1. Change "managed=false" to "managed=true" in /etc/NetworkManager/NetworkManager.conf as suggested in https://askubuntu.com/a/2905 2. Touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf as suggested in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547 3. Change renderer to NetworkManager in /etc/netplan/01-netcfg.yaml 1 and 2 was not enough to get NetworkManager to manage the wired interface, but 3, possibly together with one or both of the previous steps did the trick. When I finally got NetworkManager to manage the wired connection, it did show up in the sharing dialogs, and I was able to enable screen sharing. However, it would seem reasonable to be able to enable sharing even on unmanaged interfaces by some mechanism, especially since unmanaged interfaces seem to be the norm these days. ~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 gnome-control-center: Installed: 1:3.26.1-0ubuntu5 Candidate: 1:3.26.1-0ubuntu5 Version table: *** 1:3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.1-0ubuntu4 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1733322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451924] Re: gnome-terminal doesn't have overlay scrollbars (that actually overlay the content)
** Changed in: gnome-terminal Status: Confirmed => Expired ** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #7479 https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7479 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1451924 Title: gnome-terminal doesn't have overlay scrollbars (that actually overlay the content) Status in GNOME Terminal: Expired Status in gnome-terminal package in Ubuntu: Triaged Bug description: With gtk 3.16, gnome-terminal's terminal widgets do not have overlay scrollbars. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1451924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931704] [NEW] The settings show that bluetooth is turned off even after I turn it on
Public bug reported: Description:Ubuntu 21.04 Release:21.04 $apt-cache policy bluetooth bluetooth: Installed: 5.56-0ubuntu4 Candidate: 5.56-0ubuntu4 Version table: *** 5.56-0ubuntu4 500 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe i386 Packages 100 /var/lib/dpkg/status The settings show that the bluetooth is turned off even after I turn it on, and the devices are not detected. I am attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Fri Jun 11 17:24:20 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-04-24 (47 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-06-06 (4 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Screenshot from 2021-06-11 16:45:45.png" https://bugs.launchpad.net/bugs/1931704/+attachment/5504070/+files/Screenshot%20from%202021-06-11%2016%3A45%3A45.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1931704 Title: The settings show that bluetooth is turned off even after I turn it on Status in gnome-control-center package in Ubuntu: New Bug description: Description: Ubuntu 21.04 Release: 21.04 $apt-cache policy bluetooth bluetooth: Installed: 5.56-0ubuntu4 Candidate: 5.56-0ubuntu4 Version table: *** 5.56-0ubuntu4 500 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe i386 Packages 100 /var/lib/dpkg/status The settings show that the bluetooth is turned off even after I turn it on, and the devices are not detected. I am attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Fri Jun 11 17:24:20 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-04-24 (47 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-06-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1931704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931704] Re: The settings show that bluetooth is turned off even after I turn it on
Attaching some important outputs ** Attachment added: "bluetooth-report.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1931704/+attachment/5504076/+files/bluetooth-report.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1931704 Title: The settings show that bluetooth is turned off even after I turn it on Status in gnome-control-center package in Ubuntu: New Bug description: Description: Ubuntu 21.04 Release: 21.04 $apt-cache policy bluetooth bluetooth: Installed: 5.56-0ubuntu4 Candidate: 5.56-0ubuntu4 Version table: *** 5.56-0ubuntu4 500 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu hirsute/universe i386 Packages 100 /var/lib/dpkg/status The settings show that the bluetooth is turned off even after I turn it on, and the devices are not detected. I am attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Fri Jun 11 17:24:20 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-04-24 (47 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-06-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1931704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931706] [NEW] package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2
Public bug reported: Not able to install it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: install-info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 11 15:19:15 2021 DpkgTerminalLog: Setting up install-info (6.7.0.dfsg.2-5) ... /usr/sbin/update-info-dir: 2: export: : bad variable name dpkg: error processing package install-info (--configure): installed install-info package post-installation script subprocess returned error exit status 2 DuplicateSignature: package:install-info:6.7.0.dfsg.2-5 Setting up install-info (6.7.0.dfsg.2-5) ... /usr/sbin/update-info-dir: 2: export: : bad variable name dpkg: error processing package install-info (--configure): installed install-info package post-installation script subprocess returned error exit status 2 ErrorMessage: installed install-info package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-05-07 (35 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: texinfo Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1931706 Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2 Status in texinfo package in Ubuntu: New Bug description: Not able to install it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: install-info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 11 15:19:15 2021 DpkgTerminalLog: Setting up install-info (6.7.0.dfsg.2-5) ... /usr/sbin/update-info-dir: 2: export: : bad variable name dpkg: error processing package install-info (--configure): installed install-info package post-installation script subprocess returned error exit status 2 DuplicateSignature: package:install-info:6.7.0.dfsg.2-5 Setting up install-info (6.7.0.dfsg.2-5) ... /usr/sbin/update-info-dir: 2: export: : bad variable name dpkg: error processing package install-info (--configure): installed install-info package post-installation script subprocess returned error exit status 2 ErrorMessage: installed install-info package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-05-07 (35 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: texinfo Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1931706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931706] Re: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1931706 Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2 Status in texinfo package in Ubuntu: New Bug description: Not able to install it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: install-info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 11 15:19:15 2021 DpkgTerminalLog: Setting up install-info (6.7.0.dfsg.2-5) ... /usr/sbin/update-info-dir: 2: export: : bad variable name dpkg: error processing package install-info (--configure): installed install-info package post-installation script subprocess returned error exit status 2 DuplicateSignature: package:install-info:6.7.0.dfsg.2-5 Setting up install-info (6.7.0.dfsg.2-5) ... /usr/sbin/update-info-dir: 2: export: : bad variable name dpkg: error processing package install-info (--configure): installed install-info package post-installation script subprocess returned error exit status 2 ErrorMessage: installed install-info package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-05-07 (35 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: texinfo Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1931706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
This very probably not a bug in cups or any other printing package, but a GTK bug. See https://forums.linuxmint.com/viewtopic.php?f=51&t=348963 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727958]
This may work fine now on gnome40 with wayland but it is still occurring on the latest plasma 5.22 with wayland. X11 works fine of course -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727958 Title: Libreoffice writer / calc etc show as white icon in launcher when opened Status in LibreOffice: Fix Released Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Fix Released Bug description: Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with the application's icons. The individual icons show up in the list of programs, and can be docked in the launcher - but a generic white libreoffice icon also shows up in the program list, and if any of the docked, correct, icons are clicked, a new, white icon appears that is generic across all libreoffice windows (e.g. if I have open writer and calc, the white icon gets two red dots and to access either the writer or calc window I have to click on the generic icon). This is annoying but not crippling, and not solved by a purge and reinstall. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1727958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727958]
There are 3 years between comment #7 and comment #8 and a lot has changed since. I suggest a new fresh bug with the details of your libreoffice version and vclplug variant because I think the general case is now solvable (and works with e.g. gtk3 variant and mutter-40.1) so you may have a specific set of circumstances where it still fails. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727958 Title: Libreoffice writer / calc etc show as white icon in launcher when opened Status in LibreOffice: Fix Released Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Fix Released Bug description: Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with the application's icons. The individual icons show up in the list of programs, and can be docked in the launcher - but a generic white libreoffice icon also shows up in the program list, and if any of the docked, correct, icons are clicked, a new, white icon appears that is generic across all libreoffice windows (e.g. if I have open writer and calc, the white icon gets two red dots and to access either the writer or calc window I have to click on the generic icon). This is annoying but not crippling, and not solved by a purge and reinstall. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1727958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727958] Re: Libreoffice writer / calc etc show as white icon in launcher when opened
** Changed in: df-libreoffice Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727958 Title: Libreoffice writer / calc etc show as white icon in launcher when opened Status in LibreOffice: Fix Released Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Fix Released Bug description: Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with the application's icons. The individual icons show up in the list of programs, and can be docked in the launcher - but a generic white libreoffice icon also shows up in the program list, and if any of the docked, correct, icons are clicked, a new, white icon appears that is generic across all libreoffice windows (e.g. if I have open writer and calc, the white icon gets two red dots and to access either the writer or calc window I have to click on the generic icon). This is annoying but not crippling, and not solved by a purge and reinstall. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1727958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
This bug is a little different because the Printers system setting only shows one printer. See attached screenshot. So even though I have only one printer configured, it shows up twice in the actual print dialog box. Also, I'm using Kubuntu. ** Attachment added: "Screenshot of printer system settings" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+attachment/5504108/+files/Screenshot_20210611_102044.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931722] [NEW] software-properties-gtk generates python errors
Public bug reported: Launching software-properties-gtk gives all these Python errors after having upgraded to 21.04: Gtk-Message: 17:32:53.643: Failed to load module "appmenu-gtk-module" Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 196, in __init__ bus = dbus.SystemBus() File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 195, in __new__ return Bus.__new__(cls, Bus.TYPE_SYSTEM, mainloop=mainloop, File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.LimitsExceeded: The maximum number of active connections for UID 1000 has been reached Version: 0.99.10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-common 0.99.10 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Jun 11 17:36:34 2021 InstallationDate: Installed on 2020-09-06 (277 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to hirsute on 2021-06-08 (2 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1931722 Title: software-properties-gtk generates python errors Status in software-properties package in Ubuntu: New Bug description: Launching software-properties-gtk gives all these Python errors after having upgraded to 21.04: Gtk-Message: 17:32:53.643: Failed to load module "appmenu-gtk-module" Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 196, in __init__ bus = dbus.SystemBus() File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 195, in __new__ return Bus.__new__(cls, Bus.TYPE_SYSTEM, mainloop=mainloop, File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.LimitsExceeded: The maximum number of active connections for UID 1000 has been reached Version: 0.99.10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-common 0.99.10 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Jun 11 17:36:34 2021 InstallationDate: Installed on 2020-09-06 (277 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to hirsute on 2021-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1931722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
why are you using GCC 9? We default to GCC 10 for a while, and are about to switch to GCC 11. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. There is no-change rebuild for testing against 9.4.0-1ubuntu1~21.04 running https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+sourcepub/12488216 /+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1931701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
@doko As mentioned above, liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. There is no-change rebuild for testing against 9.4.0-1ubuntu1~21.04 running https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+sourcepub/12488216 /+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1931701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
indicator-sound has reverse-dependencies, so this probably needs fixed rather than removed. ** Changed in: poppler-qml-plugin (Ubuntu) Status: New => Fix Released ** Changed in: qtpowerd (Ubuntu) Status: New => Fix Released ** Changed in: qtubuntu-cameraplugin-fake (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
The print dialog box is generated GTK. The Printers system setup dialog is probably generated by Qt. Stop cups: systemctl stop cups Which entry remains in the GTK print dialog box? I would guess - the first one. Therefore cups is not involved in its display. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
Correction; the second entry disappears. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
"systemctl stop cups" removes the wrong entry -- the one that actually works. So now I can't print any more. Interestingly, "systemctl start cups" does not restore the printer. Looks like I will have to reboot now to restore printing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
> "systemctl stop cups" removes the wrong entry -- the > one that actually works. So now I can't print any more. That's because that entry is controlled by cups. The other one isn't. As I said, cups is not involved in producing the duplicate entry. File a bug against GTK. systemctl start cups-browsed to get your working entry back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931741] [NEW] Second Display Never Supports Proper Resolution
Public bug reported: I have tried cables, drivers, upgrades --no matter what I do I cannot get Ubuntu to recognize that my 32" UHD LG display supports 2560x1440. I can work around it with `cvt` and `xrandr` but this is tedious and is not saved across sessions, and xorg.conf is no longer a possibility (bricks the system). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 12:06:05 2021 DistUpgraded: 2021-06-11 10:51:25,279 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09a4] InstallationDate: Installed on 2021-03-08 (95 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. OptiPlex 7080 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-11 (0 days ago) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0J37VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/24/2020:br1.3:svnDellInc.:pnOptiPlex7080:pvr:rvnDellInc.:rn0J37VM:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7080 dmi.product.sku: 09A4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1931741 Title: Second Display Never Supports Proper Resolution Status in xorg package in Ubuntu: New Bug description: I have tried cables, drivers, upgrades --no matter what I do I cannot get Ubuntu to recognize that my 32" UHD LG display supports 2560x1440. I can work around it with `cvt` and `xrandr` but this is tedious and is not saved across sessions, and xorg.conf is no longer a possibility (bricks the system). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 12:06:05 2021 DistUpgraded: 2021-06-11 10:51:25,279 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09a4] InstallationDate: Installed on 2021-03-08 (95 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. OptiPlex 7080 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-11 (0 days ago) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0J37VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/24/2020:br1.3:svnDellInc.:pnOptiPlex7080:pvr:rvnDellInc.:rn0J37VM:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.famil
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
https://gitlab.gnome.org/GNOME/gtk/-/issues/4025 filed Thanks for triaging this bug. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4025 https://gitlab.gnome.org/GNOME/gtk/-/issues/4025 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
Today I upgraded libreoffice via PPA from version 7.1.2 to version 7.1.4 where the digital document signature function stopped working. When informed about the resolution of this bug in version 7.1.2, I didn't find the date of update of libreoffice from version 6.4.7 to 7.1.2 in ubuntu version 20.04, so I decided to test version 7.1.2 via PPA and it worked. With the update via PPA this function was now stopped working with version 7.1.4. Is there any relationship in ubuntu regarding these libreoffice versions? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1886092 Title: libreoffice doesn't list gpg private key for a digital signature due to apparmor Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Confirmed Status in libreoffice source package in Groovy: New Status in libreoffice source package in Hirsute: Fix Released Bug description: LibreOffice should be able to digitally sign a document with a GPG private key in the GPG key chain. However, the key is not listed in the list of certificates shown following the menu File - Digital Signatures - Digital Signatures... - Sign Document..., after, e.g., creating and saving a document on LibreOffice Writer. This seems to be because apparmor doesn't allow LibreOffice to communicate with GPG agent. /var/log/syslog shows lines like: Jul 1 15:15:14 misoan kernel: [20238.265212] audit: type=1400 audit(1593652514.311:333): apparmor="DENIED" operation="connect" profile="libreoffice-soffice//gpg" name="/run/user/1001/gnupg/S.gpg- agent" pid=23725 comm="gpg" requested_mask="wr" denied_mask="wr" fsuid=1001 ouid=1001 Locally, I could make LibreOffice show the GPG private key with the following change against /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin --- apparmor.d.20200702/usr.lib.libreoffice.program.soffice.bin 2019-10-03 10:31:21.0 -1000 +++ apparmor.d/usr.lib.libreoffice.program.soffice.bin2020-07-02 08:59:44.516754728 -1000 @@ -223,6 +223,7 @@ owner @{HOME}/.gnupg/* r, owner @{HOME}/.gnupg/random_seed rk, +owner /{,var/}run/user/*/** rw, } # probably should become a subprofile like gpg above, but then it doesn't Tested with the following packages on Xfce4 $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy libreoffice-common | grep Installed Installed: 1:6.4.3-0ubuntu0.20.04.1 $ apt-cache policy gpg gpg-agent | grep -B1 Installed gpg: Installed: 2.2.19-3ubuntu2 -- gpg-agent: Installed: 2.2.19-3ubuntu2 $ apt-cache policy apparmor | grep Installed Installed: 2.13.3-7ubuntu5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
Marcelo, you can see which versions of libreoffice are packaged in which Ubuntu releases via the libreoffice source package page on launchpad https://launchpad.net/ubuntu/+source/libreoffice There's a link at the bottom of that page to help you explore versions that might be published in PPAs. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1886092 Title: libreoffice doesn't list gpg private key for a digital signature due to apparmor Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Confirmed Status in libreoffice source package in Groovy: New Status in libreoffice source package in Hirsute: Fix Released Bug description: LibreOffice should be able to digitally sign a document with a GPG private key in the GPG key chain. However, the key is not listed in the list of certificates shown following the menu File - Digital Signatures - Digital Signatures... - Sign Document..., after, e.g., creating and saving a document on LibreOffice Writer. This seems to be because apparmor doesn't allow LibreOffice to communicate with GPG agent. /var/log/syslog shows lines like: Jul 1 15:15:14 misoan kernel: [20238.265212] audit: type=1400 audit(1593652514.311:333): apparmor="DENIED" operation="connect" profile="libreoffice-soffice//gpg" name="/run/user/1001/gnupg/S.gpg- agent" pid=23725 comm="gpg" requested_mask="wr" denied_mask="wr" fsuid=1001 ouid=1001 Locally, I could make LibreOffice show the GPG private key with the following change against /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin --- apparmor.d.20200702/usr.lib.libreoffice.program.soffice.bin 2019-10-03 10:31:21.0 -1000 +++ apparmor.d/usr.lib.libreoffice.program.soffice.bin2020-07-02 08:59:44.516754728 -1000 @@ -223,6 +223,7 @@ owner @{HOME}/.gnupg/* r, owner @{HOME}/.gnupg/random_seed rk, +owner /{,var/}run/user/*/** rw, } # probably should become a subprofile like gpg above, but then it doesn't Tested with the following packages on Xfce4 $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy libreoffice-common | grep Installed Installed: 1:6.4.3-0ubuntu0.20.04.1 $ apt-cache policy gpg gpg-agent | grep -B1 Installed gpg: Installed: 2.2.19-3ubuntu2 -- gpg-agent: Installed: 2.2.19-3ubuntu2 $ apt-cache policy apparmor | grep Installed Installed: 2.13.3-7ubuntu5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871644]
I can confirm this issue still exists in Fedora 34, Firefox 89, Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931685] Re: Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt off at the bottom
** Description changed: - On ubuntu 21.04 and on 21.10. When I open the activities view with a few + On ubuntu 21.04 and on 20.10. When I open the activities view with a few windows open the bottom edge of the windows (with the window names) get cut off, the bottom of the workspaces bar on the right side also gets cut off. When the workspaces bar is fully extended, the windows can be seen fully. So when I hover over the workspaces bar, or there are multiple workspaces with windows in them, or with an extension to always keep the workspaces open, this issue doesn't impact anything. However, the issue still exists because you can see the bottom of the workspaces bar being cut off. When I connect a second monitor, and arrange the monitors one above the other (with the top one as the permanent), I can see the cut off UI elements on the bottom monitor. With the ubuntu dock extension disabled, none of these issues are present. Here are a few screenshots that show the bug in action: https://ibb.co/album/4whv2c I could NOT spot this issue on a clean install of ubuntu 20.04. But I could see it on clean installs of both on 20.10 and on 21.04. This exists both on Wayland and Xorg. This might be related to this prior issue: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/+bug/1834967 . Maybe this issue was fixed in 20.04 but not on the later versions. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 13:05:40 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1931685 Title: Ubuntu 21.04: ubuntu dock causes windows in Activities view get cutt off at the bottom Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: On ubuntu 21.04 and on 20.10. When I open the activities view with a few windows open the bottom edge of the windows (with the window names) get cut off, the bottom of the workspaces bar on the right side also gets cut off. When the workspaces bar is fully extended, the windows can be seen fully. So when I hover over the workspaces bar, or there are multiple workspaces with windows in them, or with an extension to always keep the workspaces open, this issue doesn't impact anything. However, the issue still exists because you can see the bottom of the workspaces bar being cut off. When I connect a second monitor, and arrange the monitors one above the other (with the top one as the permanent), I can see the cut off UI elements on the bottom monitor. With the ubuntu dock extension disabled, none of these issues are present. Here are a few screenshots that show the bug in action: https://ibb.co/album/4whv2c I could NOT spot this issue on a clean install of ubuntu 20.04. But I could see it on clean installs of both on 20.10 and on 21.04. This exists both on Wayland and Xorg. This might be related to this prior issue: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- ubuntu-dock/+bug/1834967 . Maybe this issue was fixed in 20.04 but not on the later versions. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 13:05:40 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1931685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
This bug was fixed in the package software-properties - 0.99.13 --- software-properties (0.99.13) impish; urgency=medium * Catch exception if UA status file is not written -- Robert Ancell Fri, 11 Jun 2021 17:16:09 +1200 ** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931756] [NEW] [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
You have been subscribed to a public bug: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem https://bugs.launchpad.net/bugs/1931756 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923397] Re: Xorg freeze
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Expired Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923318] Re: Ubuntu does not detect video output devices
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923318 Title: Ubuntu does not detect video output devices Status in xorg-server package in Ubuntu: Expired Bug description: Firstly I'd like to apologize as I am a novice Ubuntu user and I am unsure as to which information I should include within this report. That being said, I have installed linux 20.04-- my system: cpu: ryzen 9 3900x, gpu: radeon rx6800. Ubuntu is detecting default display at correct resolution, which is connected via DisplayPort on rx6800 gpu. However, my second monitor, LGCX 4k OLED connected via HDMI is not detected in display properties window. xrandr does not detect outputs other than default display. I have run apt-get update and apt-get upgrade, restarted, unplugged and plugged displays back in, tried installing amd-gpu drivers separately which were downloaded from official website, i have tried updating kernal, along with many other troubleshooting strategies. I believe this to be some sort of software issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923167] Re: Screen flickering- QHD Benq
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923167 Title: Screen flickering- QHD Benq Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: The Display continuously flickers when we are using the Displayport connection with QHD (2560x1440) Benq-Monitors. The affected Hardware is: Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx) Using a DP to HDMI-Adapter solves the problem with the given resolution. This error occurs in both Ubuntu Releases 18.04 and 20.10. This is what we see in the Logs: [27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795 [27.144] (II) AMDGPU(0): Using hsync ranges from config file [27.144] (II) AMDGPU(0): Using vrefresh ranges from config file [27.144] (II) AMDGPU(0): Printing DDC gathered Modelines: [27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP) [27.144] (II) AMDGPU(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [27.144] (II) AMDGPU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e) [30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked [33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931547] Re: DisplayLink displays are black after Mesa update
I might be affected by this and am willing to test if it solves my problem. What happened was that about maybe two weeks ago the DisplayPorts from my DELL D6000 Dock stopped working (but works when connecting a Windows Laptop) Where do I find instructions on testing? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
This bug was fixed in the package libreoffice - 1:7.0.6-0ubuntu0.20.10.1 --- libreoffice (1:7.0.6-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1928642) * Update yaru icon style "2021-03-14" * apparmor: Fix signing documents with enforced apparmor * apparmor: Allow one more digit in temp files -- Rico Tzschichholz Tue, 18 May 2021 11:25:50 +0200 ** Changed in: libreoffice (Ubuntu Groovy) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1886092 Title: libreoffice doesn't list gpg private key for a digital signature due to apparmor Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Confirmed Status in libreoffice source package in Groovy: Fix Released Status in libreoffice source package in Hirsute: Fix Released Bug description: LibreOffice should be able to digitally sign a document with a GPG private key in the GPG key chain. However, the key is not listed in the list of certificates shown following the menu File - Digital Signatures - Digital Signatures... - Sign Document..., after, e.g., creating and saving a document on LibreOffice Writer. This seems to be because apparmor doesn't allow LibreOffice to communicate with GPG agent. /var/log/syslog shows lines like: Jul 1 15:15:14 misoan kernel: [20238.265212] audit: type=1400 audit(1593652514.311:333): apparmor="DENIED" operation="connect" profile="libreoffice-soffice//gpg" name="/run/user/1001/gnupg/S.gpg- agent" pid=23725 comm="gpg" requested_mask="wr" denied_mask="wr" fsuid=1001 ouid=1001 Locally, I could make LibreOffice show the GPG private key with the following change against /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin --- apparmor.d.20200702/usr.lib.libreoffice.program.soffice.bin 2019-10-03 10:31:21.0 -1000 +++ apparmor.d/usr.lib.libreoffice.program.soffice.bin2020-07-02 08:59:44.516754728 -1000 @@ -223,6 +223,7 @@ owner @{HOME}/.gnupg/* r, owner @{HOME}/.gnupg/random_seed rk, +owner /{,var/}run/user/*/** rw, } # probably should become a subprofile like gpg above, but then it doesn't Tested with the following packages on Xfce4 $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy libreoffice-common | grep Installed Installed: 1:6.4.3-0ubuntu0.20.04.1 $ apt-cache policy gpg gpg-agent | grep -B1 Installed gpg: Installed: 2.2.19-3ubuntu2 -- gpg-agent: Installed: 2.2.19-3ubuntu2 $ apt-cache policy apparmor | grep Installed Installed: 2.13.3-7ubuntu5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp