[Desktop-packages] [Bug 1997333] [NEW] [SRU] libreoffice 7.4.3 for kinetic
Public bug reported: [Impact] * LibreOffice 7.4.3 is in its third bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.3_release * Version 7.4.2 is currently released in kinetic. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.3 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.4.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1235/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/amd64/libr/libreoffice/20221119_025653_ec91f@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/arm64/libr/libreoffice/20221119_074354_fc477@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/armhf/libr/libreoffice/20221119_023808_27800@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-libreoffice-libreoffice-prereleases/kinetic/ppc64el/libr/libreoffice/20221119_024545_1a3cc@/log.gz * [s390x] ...pending investigation... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Kinetic) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** Changed in: libreoffice (Ubuntu Kinetic) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Kinetic) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- 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/1997333 Title: [SRU] libreoffice 7.4.3 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: In Progress Bug description: [Impact] * LibreOffice 7.4.3 is in its third bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.3_release * Version 7.4.2 is currently released in kinetic. For a list of fixed bugs compared to 7.4.3 see the list of bugs fixed in the release candidates of 7.4.3 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.4.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1235/ * More information about the upstream QA tes
[Desktop-packages] [Bug 1997338] [NEW] libatk-bridge2.0-0 uninstallable on i386
Public bug reported: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz Starting pkgProblemResolver with broken count: 9 Starting 2 pkgProblemResolver with broken count: 9 Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Investigating (0) libqt5dbus5:i386 < none -> 5.15.6+dfsg-1 @un puN Ib > Broken libqt5dbus5:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Investigating (0) libpulse0:i386 < none -> 1:16.1+dfsg1-1ubuntu3 @un puN Ib > Broken libpulse0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Investigating (0) libavahi-client3:i386 < none -> 0.8-6ubuntu1 @un puN Ib > Broken libavahi-client3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Investigating (0) libatspi2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatspi2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Investigating (0) vlc-plugin-base:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken vlc-plugin-base:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Investigating (0) libfluidsynth3:i386 < none -> 2.2.8-1 @un puN Ib > Broken libfluidsynth3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Investigating (0) libatk-bridge2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatk-bridge2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Investigating (0) libdebuginfod1:i386 < none -> 0.187-4 @un puN Ib > Broken libdebuginfod1:i386 Depends on libcurl3-gnutls:i386 < none | 7.85.0-1 @un uH > (>= 7.28.0) Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libatspi2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libavahi-client3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libdebuginfod1:i386 : Depends: libcurl3-gnutls:i386 (>= 7.28.0) but it is not going to be installed libfluidsynth3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libpulse0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libqt5dbus5:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libvlccore9:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed vlc-plugin-base:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed E: Unable to correct problems, you have held broken packages. autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs Note, using file '/tmp/autopkgtest.8eagGS/3-autopkgtest-satdep.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 9 Starting 2 pkgProblemResolver with broken count: 9 Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libd
[Desktop-packages] [Bug 1997360] [NEW] Update from git snapshot to stable 1.20
Public bug reported: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. ** Affects: modemmanager (Ubuntu) Importance: High Status: Fix Released ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in modemmanager package in Ubuntu: Fix Released Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1997360/+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 1997360] Re: Update from git snapshot to stable 1.20
** Also affects: libqmi (Ubuntu) Importance: Undecided Status: New ** Changed in: libqmi (Ubuntu) Status: New => Fix Released ** Changed in: libqmi (Ubuntu) Importance: Undecided => High ** Also affects: libmbim (Ubuntu) Importance: Undecided Status: New ** Changed in: libmbim (Ubuntu) Importance: Undecided => High ** Changed in: libmbim (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 77442] Re: compiz / vnc screen updates with nVidia restricted
*** This bug is a duplicate of bug 353126 *** https://bugs.launchpad.net/bugs/353126 https://cracklot.com/xfer-serum-crack-download/ VISITE THIS SITE -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/77442 Title: compiz / vnc screen updates with nVidia restricted Status in vino: Fix Released Status in compiz package in Ubuntu: Incomplete Status in vino package in Ubuntu: Incomplete Status in vnc package in Ubuntu: Incomplete Bug description: When connecting to a VNC server (vino) on a machine using desktop- effects, the screen is never updated. Mouse/Keyboard commands still get sent but the effects are only shown after reconnecting. This is probably because of the way vnc detects changes. This has been reported into beryl: http://bugs.beryl-project.org/trac/ticket/385 It is also known for x11vnc: http://www.dslinux.org/blogs/pepsiman/?p=73 If Ubuntu wants desktop-effects to be enabled by default, vnc will have to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/77442/+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 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
In response to your request above, Version 43.1 Did fix the problem. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+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 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
Great, thank you for confirming, closing the bug! ** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Fix Released Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+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 1997360] Re: Update from git snapshot to stable 1.20
** Description changed: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. + + Details of the changes in libqmi + https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997338] Re: libatk-bridge2.0-0 uninstallable on i386
Thank you for reporting this issue. This seems to be affecting a lot more stuff than just libatk-bridge2.0-0 and more architectures than just i386. See https://lists.ubuntu.com/archives/ubuntu- devel/2022-November/042352.html ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Changed in: dbus (Ubuntu) Importance: Undecided => Critical ** Changed in: at-spi2-core (Ubuntu) Assignee: Jeremy Bicha (jbicha) => (unassigned) ** No longer affects: at-spi2-core (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1997338 Title: libdbus-1-3 uninstallable on autopkgtest Status in dbus package in Ubuntu: Confirmed Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz Starting pkgProblemResolver with broken count: 9 Starting 2 pkgProblemResolver with broken count: 9 Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Investigating (0) libqt5dbus5:i386 < none -> 5.15.6+dfsg-1 @un puN Ib > Broken libqt5dbus5:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Investigating (0) libpulse0:i386 < none -> 1:16.1+dfsg1-1ubuntu3 @un puN Ib > Broken libpulse0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Investigating (0) libavahi-client3:i386 < none -> 0.8-6ubuntu1 @un puN Ib > Broken libavahi-client3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Investigating (0) libatspi2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatspi2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Investigating (0) vlc-plugin-base:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken vlc-plugin-base:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Investigating (0) libfluidsynth3:i386 < none -> 2.2.8-1 @un puN Ib > Broken libfluidsynth3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Investigating (0) libatk-bridge2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatk-bridge2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Investigating (0) libdebuginfod1:i386 < none -> 0.187-4 @un puN Ib > Broken libdebuginfod1:i386 Depends on libcurl3-gnutls:i386 < none | 7.85.0-1 @un uH > (>= 7.28.0) Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libatspi2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libavahi-client3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libdebuginfod1:i386 : Depends: libcurl3-gnutls:i386 (>= 7.28.0) but it is not going to be installed libfluidsynth3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libpulse0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libqt5dbus5:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed
[Desktop-packages] [Bug 1997360] Re: Update from git snapshot to stable 1.20
** Description changed: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 + + Details of the changes in libmbim + https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] Re: Update from git snapshot to stable 1.20
** Description changed: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 + + Details of the changes in modemmanager + https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 + + The Kinetic SRU is an intermediate step, the goal is to update 22.04 + from 1.18 to 1.20 as part of new hardware enablement -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997360 Title: Update from git snapshot to stable 1.20 Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: * Impact We did a git snapshot before Kinetic feature freeze on oem request to add support for newer hardware but upstream didn't roll out stable tarballs before release. The stable release is available now and fixing some issues found during the serie stabilization. * Test case - install modemmanager, libmbim, and libqmi from -proposed - restart the system - try to connect from GNOME using a SIM card, ensure the top bar indicator reflects the status and that the settings panel shows the correct properties for the connection The testing should be done on a variety of hardware from 3G to 5G modems. * Regression potential The stack is limited to modems handling so if there is a regression it is to be in the handling of those devices. Details of the changes in libqmi https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775 Details of the changes in libmbim https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571 Details of the changes in modemmanager https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5 The Kinetic SRU is an intermediate step, the goal is to update 22.04 from 1.18 to 1.20 as part of new hardware enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1950094]
(In reply to Jean-Michel COSTE from comment #0)
> Description:
> On different versions of Linux. First found on Ubuntu MATE.
> Use the attached RefreshForm.odb database.
>
> The fmtBookType (List box) control is updated by the RefreshList macro,
> connected to the event "when receiving focus".
>
> The list is well updated, Choice possible but not saved.
>
> Description in the file : RefreshForm.odt
>
> Steps to Reproduce:
> 1. Open the form fBooks
> 2. click on the "…" button to edit the support table from the drop-down list.
> 3. add a row in the table
> 4. close the form that allowed the addition ("close" button)
> 5. try to change the value of the field "BookType"
>
>
> Actual Results:
> The list is well updated, the choice is possible, but it is not taken into
> account.
Do you mean there would be an additional step 6 to click "Save record"
from the bar below the form? Because if I do it, there is no problem.
Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED
WORKSFORME, if the problem went away.
Arch Linux 64-bit
Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 70987cc656f0cded915be5aa148f265a257ec791
CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 22 November 2022
--
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/1950094
Title:
libreoffice base zone liste choix impossible
Status in LibreOffice:
Incomplete
Status in libreoffice package in Ubuntu:
Triaged
Bug description:
Bonjour,
Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
UbuntuMate 21.10 afin de voir si une modification avait été apporté à
un éventuel bogue que je vous soumets.
Le souci est avec la zone de liste dans LibreOffice Base avec la macro
ci-dessous sur Événement "A réception du focus".
Sub ActualiserListe(oEv as Object)
oEv.Source.Model.Refresh
End Sub
pour mettre à jour la zone de liste après modification d'un élément.
La mise à jour fonctionne bien mais je ne peux pas choisir une
nouvelle entrée dans la liste. Alors que si je choisis un autre
événement, comme "souris déplacée alors qu'une touche est pressée"
beaucoup moins pratique, je ne rencontre pas ce problème.
Après plusieurs recherches sur le forum OpenOffice il s'avère que la
fonction marche bien mais que le problème pourrait venir de
l'environnement Ubuntu.
Sauriez-vous m'aider pour débloquer ma situation ?
Dommage que je ne puisse pas joindre mon fichier pour des essais sur
vos propres machines ce serait plus "parlant".
Merci.
Éric
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1950094/+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 1950094] Re: libreoffice base zone liste choix impossible
** Changed in: df-libreoffice Status: New => Incomplete -- 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/1950094 Title: libreoffice base zone liste choix impossible Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Triaged Bug description: Bonjour, Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé UbuntuMate 21.10 afin de voir si une modification avait été apporté à un éventuel bogue que je vous soumets. Le souci est avec la zone de liste dans LibreOffice Base avec la macro ci-dessous sur Événement "A réception du focus". Sub ActualiserListe(oEv as Object) oEv.Source.Model.Refresh End Sub pour mettre à jour la zone de liste après modification d'un élément. La mise à jour fonctionne bien mais je ne peux pas choisir une nouvelle entrée dans la liste. Alors que si je choisis un autre événement, comme "souris déplacée alors qu'une touche est pressée" beaucoup moins pratique, je ne rencontre pas ce problème. Après plusieurs recherches sur le forum OpenOffice il s'avère que la fonction marche bien mais que le problème pourrait venir de l'environnement Ubuntu. Sauriez-vous m'aider pour débloquer ma situation ? Dommage que je ne puisse pas joindre mon fichier pour des essais sur vos propres machines ce serait plus "parlant". Merci. Éric To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1950094/+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 1990200] Re: goa-daemon crashed with SIGABRT
** Also affects: librest (Ubuntu) Importance: Undecided Status: New ** Changed in: librest (Ubuntu) Importance: Undecided => High ** Changed in: librest (Ubuntu) Status: New => Fix Committed ** Changed in: librest (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: gnome-online-accounts (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Committed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+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 1990200] Re: goa-daemon crashed with SIGABRT
** Description changed: + * Impact + + The gnome-online-accounts sometime crash after resuming from suspend + + + * Test case + + Install the gnome-online-accounts update, restart your system and verify + that configured online accounts keep working. Taking a Google account + example, calendar events should show in gnome-calendar and the top panel + widget, evolution should list your email account and nautilus should be + able to browse your gdrive folder. + + + * Regression potential + + The patch makes the code better handle an empty payload. The librest + rdepends in the archive are gnome-initial-setup/gnome-online- + accounts/gnome-maps so we should verify that those keep working as + expected. + + - + Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANG=en_US.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /lib/x86_64-linux-gnu/librest-1.0.so.0 - rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 - () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /lib/x86_64-linux-gnu/librest-1.0.so.0 + rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 + () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Description changed: * Impact The gnome-online-accounts sometime crash after resuming from suspend - * Test case - Install the gnome-online-accounts update, restart your system and verify - that configured online accounts keep working. Taking a Google account + Install the librest update, restart your system and verify that + configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. - * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Description changed: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-c
[Desktop-packages] [Bug 1997278] Re: Merge tiff 4.4.0-5 (main) from Debian unstable (main)
** Changed in: tiff (Ubuntu) Assignee: (unassigned) => Amin Bandali (bandali) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1997278 Title: Merge tiff 4.4.0-5 (main) from Debian unstable (main) Status in tiff package in Ubuntu: In Progress Bug description: Please merge tiff 4.4.0-5 (main) from Debian unstable (main) Changelog entries since current kinetic version 4.4.0-4ubuntu3: tiff (4.4.0-5) unstable; urgency=high * Backport security fix for CVE-2022-3597, CVE-2022-3626 and CVE-2022-3627, out of bounds write and denial of service via a crafted TIFF file. * Backport security fix for CVE-2022-3570, multiple heap buffer overflows via crafted TIFF file. * Backport security fix for CVE-2022-3599, denial-of-service via a crafted TIFF file. * Backport security fix for CVE-2022-3598, denial-of-service via a crafted TIFF file (closes: #1022555). -- Laszlo Boszormenyi (GCS) Sun, 23 Oct 2022 22:38:15 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
Hello everyone, I applied Jeffersons version of the solution and it helped (great!), but then I reverted '/etc/apparmor.d/usr.bin.evince' to the original version and printing with evince still works, even after reboot. Is it possible that this setting has to be applied only once? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1997224] Re: [NUC12WSKi5, Realtek ALC269VB, Green Headphone Out, Left] Playback problem with startup applications
I managed to get audio output going using amixer: amixer sset Master mute unmute 1- 1+ Both parts are necessary (mute/unmute and volume adjustment). Just muting/unmuting or adjusting the volume does not bring back audio output. I can put it in my start script without adding any possibly insufficient delay prior to it. I still don't understand why this is needed. If playback is delayed long enough, the "audio system" (I don't know which component) seems to do something similar internally and it magically works. However, this is not how it is supposed to work, because a user (or a start script) can not know how long the delay actually needs to be. -- 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/1997224 Title: [NUC12WSKi5, Realtek ALC269VB, Green Headphone Out, Left] Playback problem with startup applications Status in alsa-driver package in Ubuntu: New Bug description: I am starting an audio application (a.g. aplay, paplay, any media player) automatically after login (through the "Startup Applications"). I can see that the app is playing some audio through PulseAudio by checking pavucontrol. However, no sound is output to the speaker. When I delay the startup of the app a couple of seconds (e.g. via sleep 5), the sound is played as expected. We tried to analyze the issue here: https://answers.launchpad.net/ubuntu/+question/703840 It seems that there is something wrong with the mixer when audio apps are launched very early after boot (or login?): The "Master Playback Volume" is set to 0 at the ALSA level, and it seems that PulseAudio is not able to raise it if audio playback is started so early. Attempts to automatically raise the "Master Playback Volume" through amixer also failed. The "Master Playback Volume" stays at 0. As mentioned above, when the start of the playback is delayed a bit, the "Master Playback Volume" is at 100 as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kiosk 1081 F pulseaudio /dev/snd/pcmC0D0c: kiosk 1081 F...m pulseaudio /dev/snd/pcmC0D0p: kiosk 1081 F...m pulseaudio CasperMD5CheckResult: pass Date: Mon Nov 21 10:35:48 2022 InstallationDate: Installed on 2022-11-21 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.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: Green Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [NUC12WSKi5, Realtek ALC269VB, Green Headphone Out, Left] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2022 dmi.bios.release: 5.26 dmi.bios.vendor: Intel Corp. dmi.bios.version: WSADL357.0085.2022.0718.1739 dmi.board.name: NUC12WSBi5 dmi.board.vendor: Intel Corporation dmi.board.version: M46425-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWSADL357.0085.2022.0718.1739:bd07/18/2022:br5.26:svnIntel(R)ClientSystems:pnNUC12WSKi5:pvrM46708-302:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-302:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSKi5000: dmi.product.family: WS dmi.product.name: NUC12WSKi5 dmi.product.sku: NUC12WSKi5000 dmi.product.version: M46708-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1997224/+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 1997278] Re: Merge tiff 4.4.0-5 (main) from Debian unstable (main)
Ok please disregard the two earlier debdiffs, and use the following instead. ** Patch added: "debdiff to the 4.4.0-4ubuntu3.1 version in kinetic" https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+attachment/5632153/+files/tiff_4.4.0-5ubuntu1-from-4.4.0-4ubuntu3.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1997278 Title: Merge tiff 4.4.0-5 (main) from Debian unstable (main) Status in tiff package in Ubuntu: In Progress Bug description: Please merge tiff 4.4.0-5 (main) from Debian unstable (main) Changelog entries since current kinetic version 4.4.0-4ubuntu3: tiff (4.4.0-5) unstable; urgency=high * Backport security fix for CVE-2022-3597, CVE-2022-3626 and CVE-2022-3627, out of bounds write and denial of service via a crafted TIFF file. * Backport security fix for CVE-2022-3570, multiple heap buffer overflows via crafted TIFF file. * Backport security fix for CVE-2022-3599, denial-of-service via a crafted TIFF file. * Backport security fix for CVE-2022-3598, denial-of-service via a crafted TIFF file (closes: #1022555). -- Laszlo Boszormenyi (GCS) Sun, 23 Oct 2022 22:38:15 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+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 1997278] Re: Merge tiff 4.4.0-5 (main) from Debian unstable (main)
And here's a debdiff to 4.4.0-5 from debian unstable, for reference. ** Patch added: "debdiff to the 4.4.0-5 version in debian unstable" https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+attachment/5632154/+files/tiff_4.4.0-5ubuntu1-from-4.4.0-5.debdiff ** Changed in: tiff (Ubuntu) Assignee: Amin Bandali (bandali) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1997278 Title: Merge tiff 4.4.0-5 (main) from Debian unstable (main) Status in tiff package in Ubuntu: In Progress Bug description: Please merge tiff 4.4.0-5 (main) from Debian unstable (main) Changelog entries since current kinetic version 4.4.0-4ubuntu3: tiff (4.4.0-5) unstable; urgency=high * Backport security fix for CVE-2022-3597, CVE-2022-3626 and CVE-2022-3627, out of bounds write and denial of service via a crafted TIFF file. * Backport security fix for CVE-2022-3570, multiple heap buffer overflows via crafted TIFF file. * Backport security fix for CVE-2022-3599, denial-of-service via a crafted TIFF file. * Backport security fix for CVE-2022-3598, denial-of-service via a crafted TIFF file (closes: #1022555). -- Laszlo Boszormenyi (GCS) Sun, 23 Oct 2022 22:38:15 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+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 1997278] Re: Merge tiff 4.4.0-5 (main) from Debian unstable (main)
Remaining differences with tiff from Debian unstable: * Merge from Debian unstable (LP #1997278). Also we take Debian's security fixes for the recent CVEs, except for CVE-2022-2519_2520_2521_2953.patch which is not included in Debian, at least as of now. * Don't build with LERC on i386 because it requires numpy (Closes: #1017958) In summary, we are adapting Debian's security fixes, and adding in our CVE-2022-2519_2520_2521_2953.patch as well, since they don't have in Debian yet (I'll see about opening a bug report with them on whether they want to add this patch as well), and we also don't build with LERC on i386 (Debian folks weren't interested in taking this). ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-2519 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1997278 Title: Merge tiff 4.4.0-5 (main) from Debian unstable (main) Status in tiff package in Ubuntu: In Progress Bug description: Please merge tiff 4.4.0-5 (main) from Debian unstable (main) Changelog entries since current kinetic version 4.4.0-4ubuntu3: tiff (4.4.0-5) unstable; urgency=high * Backport security fix for CVE-2022-3597, CVE-2022-3626 and CVE-2022-3627, out of bounds write and denial of service via a crafted TIFF file. * Backport security fix for CVE-2022-3570, multiple heap buffer overflows via crafted TIFF file. * Backport security fix for CVE-2022-3599, denial-of-service via a crafted TIFF file. * Backport security fix for CVE-2022-3598, denial-of-service via a crafted TIFF file (closes: #1022555). -- Laszlo Boszormenyi (GCS) Sun, 23 Oct 2022 22:38:15 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+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 1979196] Re: WIFI hotspot with no internet connection
*** This bug is a duplicate of bug 1971538 *** https://bugs.launchpad.net/bugs/1971538 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1979196 Title: WIFI hotspot with no internet connection Status in xorg package in Ubuntu: Confirmed Bug description: After the upgrade from ubuntu 20.04 to 22.04 the WIFI hotspot stopped working. Actually, the hotspot can be created, it is also possible to connect to it from external device. But the internet connection cannot be established. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Mon Jun 20 09:45:07 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1033 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (43 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000BMC dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1979196/+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 1997480] [NEW] maximized xwayland windows shift by 1 pixel when on top vs/ not on top
Public bug reported: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+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 1997481] [NEW] Update gnome-shell to 43.1
Public bug reported: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.1/NEWS Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-shell (Ubuntu) Importance: High Status: Fix Committed ** Affects: gnome-shell (Ubuntu Kinetic) Importance: High Status: Triaged ** Tags: kinetic upgrade-software-version ** Also affects: gnome-shell (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Kinetic) Status: New => Triaged -- 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/1997481 Title: Update gnome-shell to 43.1 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Kinetic: Triaged Bug description: Impact -- There is a new bugfix release in the stable 43 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.1/NEWS Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997481/+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 1997484] [NEW] ubuntu-drivers for 22.04 crashes while attempting to detect nvidia gpu
Public bug reported:
SYSTEM INFORMATION:
user@host# lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
PACKAGE VERSION INFORMATION:
user@host# apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
Installed: 1:0.9.6.1
Candidate: 1:0.9.6.1
Version table:
*** 1:0.9.6.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
EXPECTED RESULT:
Any updated/missing drivers are upgraded/installed
ACTUAL RESULT:
when using the command 'nvidia-drivers install' after a fresh installation, the
following error is produced from Python3:
==
user@hostname:~$ sudo ubuntu-drivers install
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 413, in install
command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment
==
FIX FOR THIS BUG/WORK AROUND:
This is fixed by adding the following code on line 830:
version = 0
def nvidia_desktop_pre_installation_hook(to_install):
'''Applies changes that need to happen before installing the NVIDIA
drivers'''
with_nvidia_kms = False
version = 520
# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
if with_nvidia_kms:
set_nvidia_kms(1)
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Tags: card crash critical fail failure gpu graphics install nvidia python
ubuntu-drivers video
--
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/1997484
Title:
ubuntu-drivers for 22.04 crashes while attempting to detect nvidia gpu
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
SYSTEM INFORMATION:
user@host# lsb_release -rd
Description: Ubuntu 22.04.1 LTS
Release: 22.04
PACKAGE VERSION INFORMATION:
user@host# apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
Installed: 1:0.9.6.1
Candidate: 1:0.9.6.1
Version table:
*** 1:0.9.6.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
EXPECTED RESULT:
Any updated/missing drivers are upgraded/installed
ACTUAL RESULT:
when using the command 'nvidia-drivers install' after a fresh installation,
the following error is produced from Python3:
==
user@hostname:~$ sudo ubuntu-drivers install
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/dec
[Desktop-packages] [Bug 1995743] Re: webdav error trying to connect to nextcloud
I am affected too. In my case, I am accessing Nextcloud running on Ubuntu Server 22.04 for Raspberry Pi from thunar and Gigolo on Xubuntu. Same error on both "Message recipient disconnected from message bus without replying". On my Kubuntu desktop, KDE Dolphin accesses OK (though now on Kubuntu 22.10 it prompts for wallet password but on 22.04 it didn't) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1995743 Title: webdav error trying to connect to nextcloud Status in gvfs package in Ubuntu: Confirmed Bug description: upgraded to ubuntu 22.10 from 22.04 and webdav fails to connect to nextcloud. Reimaged back to 22.04 and it worked. Error message is "Message recipient disconnected from message bus without replying Please select another viewer and try again." I have tried webdav from mate 22.10 and gnome 22.10 with same failure. Crash report fails as well but I was able to get a copy before deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1995743/+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 1995743] Re: webdav error trying to connect to nextcloud
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1995743 Title: webdav error trying to connect to nextcloud Status in gvfs package in Ubuntu: Confirmed Bug description: upgraded to ubuntu 22.10 from 22.04 and webdav fails to connect to nextcloud. Reimaged back to 22.04 and it worked. Error message is "Message recipient disconnected from message bus without replying Please select another viewer and try again." I have tried webdav from mate 22.10 and gnome 22.10 with same failure. Crash report fails as well but I was able to get a copy before deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1995743/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-1996495 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 1993545] Re: package firefox 105.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: il sottoprocesso nuovo pacchetto firefox script pre-installation ha restituito lo stato di
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1993545 Title: package firefox 105.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: il sottoprocesso nuovo pacchetto firefox script pre- installation ha restituito lo stato di errore 1 Status in firefox package in Ubuntu: Confirmed Bug description: Impossible to download this package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 105.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm 958 F pulseaudio antonionocerino 1476 F pulseaudio /dev/snd/controlC1: gdm 958 F pulseaudio antonionocerino 1476 F pulseaudio BuildID: 20220915150737 CasperMD5CheckResult: unknown Channel: Unavailable Date: Wed Oct 19 16:16:36 2022 ErrorMessage: il sottoprocesso nuovo pacchetto firefox script pre-installation ha restituito lo stato di errore 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-10-19 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.4 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 105.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: il sottoprocesso nuovo pacchetto firefox script pre-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to jammy on 2022-10-19 (0 days ago) dmi.bios.date: 12/01/2020 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 46.24 dmi.modalias: dmi:bvnInsyde:bvrF.41:bd12/01/2020:br15.41:efr46.24:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.24:cvnHP:ct10:cvrChassisVersion:sku2GG43EA#ABZ: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.sku: 2GG43EA#ABZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1993545/+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 1997512] [NEW] Ubuntu logo in About page of Settings has black text in dark mode in Ubuntu 22.10
Public bug reported: In Ubuntu 22.10, in GNOME Settings, the Ubuntu logo on the About page has some appearance issues: 1. In dark mode, the image normally should have white text. This is not the case here. The Ubuntu logo, even in dark mode still has black text. 2. Also, when maximising or enlarging the window, the Ubuntu logo becomes blurry. This might be because the logo file is a bitmap or raster image. Ideally, the image should be a vector image, so that it looks clear at all sizes, or the logo should not be made to resize with the window. The above appearance bugs are shown in the screenshot. Please fix them as soon as possible. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 23 07:42:56 2022 InstallationDate: Installed on 2022-09-24 (59 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "Screenshot showing appearance bugs in Ubuntu logo" https://bugs.launchpad.net/bugs/1997512/+attachment/5632245/+files/Screenshot%20from%202022-11-17%2015-13-50.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/1997512 Title: Ubuntu logo in About page of Settings has black text in dark mode in Ubuntu 22.10 Status in gnome-control-center package in Ubuntu: New Bug description: In Ubuntu 22.10, in GNOME Settings, the Ubuntu logo on the About page has some appearance issues: 1. In dark mode, the image normally should have white text. This is not the case here. The Ubuntu logo, even in dark mode still has black text. 2. Also, when maximising or enlarging the window, the Ubuntu logo becomes blurry. This might be because the logo file is a bitmap or raster image. Ideally, the image should be a vector image, so that it looks clear at all sizes, or the logo should not be made to resize with the window. The above appearance bugs are shown in the screenshot. Please fix them as soon as possible. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 23 07:42:56 2022 InstallationDate: Installed on 2022-09-24 (59 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1997512/+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 387957] Re: Improve Save As Dialog Box (focus issues)
Is Cody actively working on this? If not, should he be unassigned? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File -> Save As (to bring up the "Save" dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File -> Save As (to bring up the "Save" dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the "file type" dropdown), not back to the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+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 1997529] [NEW] Gnome Shell forgets settings
Public bug reported: Gnome Shell forgets that it has been told to be in dark mode. Often you log in and it has reverted to light mode. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-24.25-generic 5.19.17 Uname: Linux 5.19.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 23 07:10:39 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-17 (5 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1997529 Title: Gnome Shell forgets settings Status in gnome-shell package in Ubuntu: New Bug description: Gnome Shell forgets that it has been told to be in dark mode. Often you log in and it has reverted to light mode. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-24.25-generic 5.19.17 Uname: Linux 5.19.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 23 07:10:39 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-17 (5 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997529/+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 1753509] Re: avahi-daemon adds/installs every printer on network
I can confirm here that I have sucessfully installed only 2 local printers on cups, and I can see only them in cups admin. But on Gnome's settings printers, there are all printers on my network. I am in a corporate lan with like 30 printers in my print dialogue... So gnome is getting data from avahi instead of cups... I guess this setting should be configurable, maybe someone doesn't want printers from avahi... -- 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/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups package in Ubuntu: Triaged Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1753509/+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 1986841] Re: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1986841 Title: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command Status in cups package in Ubuntu: Confirmed Bug description: canon pixma g2010 printer connected through usb, added in printer settings when i searched for it but when i give print command to print a page it sends command and still no print out and also there is no pending jobs showing, and when i tried to print test page it is also not printing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-oem-5.17/linux-modules-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 21:37:30 2022 InstallationDate: Installed on 2022-07-11 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for G2010: usb://Canon/G2010%20series?serial=20B026&interface=1 MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511/RV711/E3411 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/G2010.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/G2010.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2011 dmi.bios.release: 4.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04PA.M006.20110615.XW dmi.board.asset.tag: Tag 12345 dmi.board.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04PA.M006.20110615.XW:bd06/15/2011:br4.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511/RV711/E3411:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511/RV711/E3411:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:sku: dmi.product.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841/+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 1986841] Re: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command
It seems the same problem. https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551 -- 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/1986841 Title: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command Status in cups package in Ubuntu: Confirmed Bug description: canon pixma g2010 printer connected through usb, added in printer settings when i searched for it but when i give print command to print a page it sends command and still no print out and also there is no pending jobs showing, and when i tried to print test page it is also not printing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-oem-5.17/linux-modules-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Aug 17 21:37:30 2022 InstallationDate: Installed on 2022-07-11 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for CUPS-BRF-Printer: cups-brf:/ device for G2010: usb://Canon/G2010%20series?serial=20B026&interface=1 MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511/RV711/E3411 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/G2010.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/G2010.ppd: Permission denied grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2011 dmi.bios.release: 4.0 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04PA.M006.20110615.XW dmi.board.asset.tag: Tag 12345 dmi.board.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04PA.M006.20110615.XW:bd06/15/2011:br4.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511/RV711/E3411:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511/RV711/E3411:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:sku: dmi.product.name: RV411/RV511/E3511/S3511/RV711/E3411 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841/+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 1997530] [NEW] package chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab
Public bug reported: it crashes on systemupgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 Uname: Linux 4.9.140+ aarch64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: arm64 Date: Wed Nov 23 08:32:22 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstalledPlugins: Load-Avg-1min: 2.46 Load-Processes-Running-Percent: 0.4% Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcKernelCmdLine: root=/dev/mmcblk0p2 rootfstype=ext4 rw firmware_class.path=/lib/firmware/ access=m2 rootlabel_retries=1 swr_dir=/switchroot/ubuntu/ boot_m=1 boot_p=1 pmc_reboot2payload.enabled=1 pmc_reboot2payload.reboot_action=bootloader pmc_reboot2payload.default_payload=reboot_payload.bin pmc_reboot2payload.hekate_config_id=SWR-UBU fbcon=primary:1 consoleblank=0 nvdec_enabled=0 vpr_resize tegra_fbmem=0x40@0xf5a0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2022-11-23 (0 days ago) modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1997530 Title: package chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in chromium-browser package in Ubuntu: New Bug description: it crashes on systemupgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 Uname: Linux 4.9.140+ aarch64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: arm64 Date: Wed Nov 23 08:32:22 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstalledPlugins: Load-Avg-1min: 2.46 Load-Processes-Running-Percent: 0.4% Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcKernelCmdLine: root=/dev/mmcblk0p2 rootfstype=ext4 rw firmware_class.path=/lib/firmware/ access=m2 rootlabel_retries=1 swr_dir=/switchroot/ubuntu/ boot_m=1 boot_p=1 pmc_reboot2payload.enabled=1 pmc_reboot2payload.reboot_action=bootloader pmc_reboot2payload.default_payload=reboot_payload.bin pmc_reboot2payload.hekate_config_id=SWR-UBU fbcon=primary:1 consoleblank=0 nvdec_enabled=0 vpr_resize tegra_fbmem=0x40@0xf5a0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2022-11-23 (0 days ago) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997530/+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 1982551] Re: Print is failed via USB
The followings seem the same problems.
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1946016
--
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/1982551
Title:
Print is failed via USB
Status in cups package in Ubuntu:
New
Bug description:
Phenomenon:
After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it
can be printed at the first time, but after the second or multiple times, the
job will be canceled.
Comment:
1.Wait a few minutes and the job still won't be printed.
2.After unplugging in and plugging in the USB cable, the job can be printed
3.The problem does not occur via network printing.
4.Other systems (such as Windows, Mac OS) do not have this problem.
Our analysis:
1.We think that part of the data was lost via USB transmission
2.In CUPS ErrorLog, the job has been delivered completely.
(refer to error_log->[Job 313])
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command:
\"printf \"%%!PS-Adobe-3.0
D [21/Jul/2022:15:21:17 +0800] [Job 313] Title:
(/home/rits/文档/17540黑白-2017.doc)
D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
D [21/Jul/2022:15:21:17 +0800] [Job 313]
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>>
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto)
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\"
(generation 1)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\"
(generation 2)
D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
D [21/Jul/2022:15:21:17 +0800] [Job 313]
I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.
3.However, I found an error on USB Request Block (URB) with Wireshark on
Ubuntu 18.04
[Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end
of file) will be ignored] appeared at [URB BULK IN]
(refer to usb2.pcapng, snapshot.pn)
4.We extracted the accepted data on the printer side, the data is really lost.
(refer to prt00016.prn,
prt00013.prn is the data of normal print)
Description: Ubuntu 18.04.5 LTS
Release: 18.04
CUPS 2.2.7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.9
ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 22 15:43:30 2022
InstallationDate: Installed on 2022-07-05 (16 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
MachineType: Dell Inc. OptiPlex 3010
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 042P49
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 3010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1946016] Re: Unable to print via usb (HP Deskjet 6980)
The followings seem the same problems. https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841 https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551 -- 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/1946016 Title: Unable to print via usb (HP Deskjet 6980) Status in cups package in Ubuntu: Confirmed Bug description: I'm unable to print documents via usb connection (HP Deskjet 6980). There is no connection problem, (lsusb: Bus 001 Device 040: ID 03f0:8804 HP, Inc DeskJet 6980 series correctly detected), it just doesn't work... ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 18:42:29 2021 InstallationDate: Installed on 2019-06-03 (853 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Deskjet-6980-series: usb://HP/Deskjet%206980%20series?serial=MY796BS11G04Q7 device for HP-Color-LaserJet-CM4540-MFP: socket://158.227.246.36:9100 MachineType: LG Electronics 13Z990-G.AA52B Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd', '/etc/cups/ppd/Deskjet-6980-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd: Permission denied grep: /etc/cups/ppd/Deskjet-6980-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=30e4f9a7-3fb6-4a39-a72e-b1a51a899771 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: W1ZD1180 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 13Z990 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrW1ZD1180X64:bd01/29/2019:br0.1:svnLGElectronics:pn13Z990-G.AA52B:pvr0.1:sku:rvnLGElectronics:rn13Z990:rvrFAB1:cvnLGElectronics:ct10:cvr0.1: dmi.product.family: Z Series dmi.product.name: 13Z990-G.AA52B dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1946016/+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 1946016] Re: Unable to print via usb (HP Deskjet 6980)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1946016 Title: Unable to print via usb (HP Deskjet 6980) Status in cups package in Ubuntu: Confirmed Bug description: I'm unable to print documents via usb connection (HP Deskjet 6980). There is no connection problem, (lsusb: Bus 001 Device 040: ID 03f0:8804 HP, Inc DeskJet 6980 series correctly detected), it just doesn't work... ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 18:42:29 2021 InstallationDate: Installed on 2019-06-03 (853 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Deskjet-6980-series: usb://HP/Deskjet%206980%20series?serial=MY796BS11G04Q7 device for HP-Color-LaserJet-CM4540-MFP: socket://158.227.246.36:9100 MachineType: LG Electronics 13Z990-G.AA52B Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd', '/etc/cups/ppd/Deskjet-6980-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-CM4540-MFP.ppd: Permission denied grep: /etc/cups/ppd/Deskjet-6980-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=30e4f9a7-3fb6-4a39-a72e-b1a51a899771 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: W1ZD1180 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 13Z990 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrW1ZD1180X64:bd01/29/2019:br0.1:svnLGElectronics:pn13Z990-G.AA52B:pvr0.1:sku:rvnLGElectronics:rn13Z990:rvrFAB1:cvnLGElectronics:ct10:cvr0.1: dmi.product.family: Z Series dmi.product.name: 13Z990-G.AA52B dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1946016/+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
